Nokia 2720 Flip (nokia-beatles): Difference between revisions
paritition layout and wlan sections |
m type = Feature Phone |
||
(15 intermediate revisions by 10 users not shown) | |||
Line 1: | Line 1: | ||
{{Infobox device | {{Infobox device | ||
| manufacturer = Nokia | | manufacturer = Nokia | ||
| name = | | name = 2720 Flip | ||
| codename = nokia-beatles | | codename = nokia-beatles | ||
| image = File:Nokia-2720-open-angle-black.png | | image = File:Nokia-2720-open-angle-black.png | ||
| releaseyear = 2019 | | releaseyear = 2019 | ||
| originalsoftware = KaiOS 2.5.2 | | originalsoftware = KaiOS | ||
| chipset = Qualcomm | | originalversion = 2.5.2 | ||
| cpu = | | chipset = Qualcomm Snapdragon 205 (MSM8905) | ||
| cpu = 2x 1.1 GHz Cortex-A7 | |||
| gpu = Adreno 304 | | gpu = Adreno 304 | ||
| storage = 4 GB | | storage = 4 GB | ||
Line 13: | Line 14: | ||
| memory = 512 MB | | memory = 512 MB | ||
| architecture = armv7 | | architecture = armv7 | ||
| type = Feature Phone | |||
<!-- the following status_* questions should be answered with Y - yes, P - partial, N - no, or left blank (for untested or unknown) --> | <!-- the following status_* questions should be answered with Y - yes, P - partial, N - no, or left blank (for untested or unknown) --> | ||
| status_usbnet = Y | | status_usbnet = Y | ||
Line 48: | Line 50: | ||
== Installation == | == Installation == | ||
{{note|The only method tested assumes flashing <code>boot.img</code> to the <code>recovery</code> partition and <code>rootfs</code> to the microSD card}} | {{note|The only method tested assumes flashing <code>boot.img</code> to the <code>recovery</code> partition and <code>rootfs</code> to the microSD card}} | ||
<code>fastboot</code> reported to be locked on this phone, you will need to flash everything from the KaiOS directly instead | <code>fastboot</code> reported to be locked on this phone, you will need to flash everything from the KaiOS directly instead: | ||
* install <code>rootfs</code> to the microSD with <code>pmbootstrap install --sdcard=/dev/sdX</code> | * install <code>rootfs</code> to the microSD with <code>pmbootstrap install --sdcard=/dev/sdX</code> | ||
* put the card into the phone and boot it to the KaiOS | * put the card into the phone and boot it to the KaiOS | ||
* export <code>boot.img</code> to the <code>/tmp</code> on your host machine: <code>pmbootstrap export</code> | * export <code>boot.img</code> to the <code>/tmp</code> on your host machine: <code>pmbootstrap export</code> | ||
* push <code>boot.img</code> to the <code>/sdcard</code>: <code>adb push /tmp/postmarketOS-export/boot.img-nokia-beatles /sdcard/</code> | * push <code>boot.img</code> to the <code>/sdcard</code>: <code>adb push /tmp/postmarketOS-export/boot.img-nokia-beatles /sdcard/</code> | ||
* (optional) backup <code>recovery</code> partition: <code>adb shell "dd if=/dev/block/bootdevice/by-name/recovery of=/sdcard/backup_recovery.img bs=2048"</code> | |||
* flash <code>recovery</code> partition: <code>adb shell "dd if=/sdcard/boot.img-nokia-beatles of=/dev/block/bootdevice/by-name/recovery bs=2048"</code> | * flash <code>recovery</code> partition: <code>adb shell "dd if=/sdcard/boot.img-nokia-beatles of=/dev/block/bootdevice/by-name/recovery bs=2048"</code> | ||
* reboot to the freshly flashed pmOS: <code>adb reboot recovery</code> | * reboot to the freshly flashed pmOS: <code>adb reboot recovery</code> | ||
You will be able to boot to pmOS by turning on the phone while holding the <code>Volume Up</code> button. | You will be able to boot to pmOS by turning on the phone while holding the <code>Volume Up</code> button. | ||
== Display == | |||
Main display works fine with <code>msm-fb-refresher</code>. | |||
External display seems to use custom <code>mdss-spi-panel</code> driver which is not publicly available. | |||
== WLAN == | == WLAN == | ||
Out-of-tree <code>prima</code> wlan kernel module available [https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/prima/tree/?h=LF.BR.1.2.8 here]. | Out-of-tree <code>prima</code> wlan kernel module available [https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/prima/tree/?h=LF.BR.1.2.8 here]. | ||
Firmware can be extracted from the following | Firmware can be extracted from the following mount points: | ||
<syntaxhighlight lang="shell-session"> | <syntaxhighlight lang="shell-session"> | ||
system => /system/etc/firmware/wlan/prima/WCNSS_cfg.dat | system => /system/etc/firmware/wlan/prima/WCNSS_cfg.dat | ||
Line 72: | Line 80: | ||
# echo sta > /sys/module/wlan/parameters/fwpath | # echo sta > /sys/module/wlan/parameters/fwpath | ||
</syntaxhighlight> | </syntaxhighlight> | ||
Unfortunately, <code>nmcli</code> didn't work for me, but <code>iw dev wlan0 scan</code> did the trick. | Unfortunately, <code>nmcli</code> didn't work for me, but <code>iw dev wlan0 scan</code> did the trick. Won't connect to any network though. | ||
== Modem == | |||
Followed an approach described [https://wiki.postmarketos.org/wiki/Modem#Qualcomm_Modems here] with no luck: getting <code>smd_pkt_open: DATA5_CNTL open failed -19</code> in <code>dmesg</code> while trying to access the modem. | |||
With <code>echo 1 > /sys/kernel/boot_adsp/boot</code> modem at least boots up (using <code>rmt_storage</code> binary ripped out of KaiOS), but <code>DATA5_CNTL</code> is still unavailable. | |||
Allocation tables (output of <code>/sys/kernel/debug/smd/ch</code>) is [https://pastebin.com/WBciafqR here]. | |||
According to the following lines in <code>dmesg</code>, it looks like something tries to reach USB diag device which is not available: | |||
<syntaxhighlight lang="shell-session"> | |||
[ 502.693072] diag: USB ch diag is not connected | |||
[ 502.693080] diag: In diag_process_smd_read_data, diag_device_write error: -19 | |||
</syntaxhighlight> | |||
Tried to set the following USB configuration options with no luck as well: | |||
<syntaxhighlight lang="shell-session"> | |||
# echo "0" > /sys/class/android_usb/android0/enable | |||
# echo "diag" > /sys/class/android_usb/android0/f_diag/clients | |||
# echo "smd" > /sys/class/android_usb/android0/f_serial/transports | |||
# echo "qti,bam" > /sys/class/android_usb/android0/f_rmnet/transports | |||
# echo "diag,serial_smd,rmnet_qti_bam" > /sys/class/android_usb/android0/functions | |||
# echo "1" > /sys/class/android_usb/android0/enable | |||
</syntaxhighlight> | |||
It is possible that the modem requires sending a DPM (data port management) QMI command to open up the <code>DATA5_CNTL</code> channel, as done [https://git.abscue.de/bananian/device-modem-qcom/-/blob/devel/bootmodem.c#L12 here] for the Nokia 8110 4G. | |||
== Partition layout == | == Partition layout == | ||
Line 112: | Line 144: | ||
== See also == | == See also == | ||
* {{ | * {{Device package|nokia-beatles}} | ||
* {{Kernel package|nokia-beatles}} | |||
* | |||
- |
Latest revision as of 05:26, 1 October 2023
![]() | |
Manufacturer | Nokia |
---|---|
Name | 2720 Flip |
Codename | nokia-beatles |
Released | 2019 |
Type | feature phone |
Hardware | |
Chipset | Qualcomm Snapdragon 205 (MSM8905) |
CPU | 2x 1.1 GHz Cortex-A7 |
GPU | Adreno 304 |
Display | 240x320 TFT |
Storage | 4 GB |
Memory | 512 MB |
Architecture | armv7 |
Software | |
Original software | KaiOS |
Original version | 2.5.2 |
postmarketOS | |
Category | testing |
Pre-built images | no |
postmarketOS kernel | 3.10.49 |
Flashing |
Broken |
---|---|
USB Networking |
Works |
Internal storage |
No data |
SD card |
No data |
Battery |
No data |
Screen |
Works |
Multimedia | |
3D Acceleration |
No data |
Audio |
No data |
Camera |
No data |
Camera Flash |
No data |
Connectivity | |
WiFi |
No data |
Bluetooth |
No data |
GPS |
No data |
NFC |
No data |
Modem | |
Calls |
No data |
SMS |
No data |
Mobile data |
No data |
Miscellaneous | |
FDE |
No data |
USB OTG |
No data |
HDMI/DP |
No data |
Sensors | |
Magnetometer |
No data |
Ambient Light |
No data |
Proximity |
No data |
Hall Effect |
No data |
Haptics |
No data |
Barometer |
No data |
Contributors
Users owning this device
- DolphinChips (Notes: Mainline soon I hope)
- GloomyJD (Notes: Works)
- Huevo5050 (Notes: Flashing)
- UltrasonicMadness
Prerequisites
- rooted phone
- microSD card
Installation
The only method tested assumes flashing boot.img to the recovery partition and rootfs to the microSD card |
fastboot
reported to be locked on this phone, you will need to flash everything from the KaiOS directly instead:
- install
rootfs
to the microSD withpmbootstrap install --sdcard=/dev/sdX
- put the card into the phone and boot it to the KaiOS
- export
boot.img
to the/tmp
on your host machine:pmbootstrap export
- push
boot.img
to the/sdcard
:adb push /tmp/postmarketOS-export/boot.img-nokia-beatles /sdcard/
- (optional) backup
recovery
partition:adb shell "dd if=/dev/block/bootdevice/by-name/recovery of=/sdcard/backup_recovery.img bs=2048"
- flash
recovery
partition:adb shell "dd if=/sdcard/boot.img-nokia-beatles of=/dev/block/bootdevice/by-name/recovery bs=2048"
- reboot to the freshly flashed pmOS:
adb reboot recovery
You will be able to boot to pmOS by turning on the phone while holding the Volume Up
button.
Display
Main display works fine with msm-fb-refresher
.
External display seems to use custom mdss-spi-panel
driver which is not publicly available.
WLAN
Out-of-tree prima
wlan kernel module available here.
Firmware can be extracted from the following mount points:
system => /system/etc/firmware/wlan/prima/WCNSS_cfg.dat
userdata => /misc/wifi/WCNSS_qcom_cfg.ini
persist => /WCNSS_qcom_wlan_nv.bin
persist => /WCNSS_wlan_dictionary.dat
To enable the module in pmOS run the following (as root):
# echo 1 > /dev/wcnss_wlan
# echo sta > /sys/module/wlan/parameters/fwpath
Unfortunately, nmcli
didn't work for me, but iw dev wlan0 scan
did the trick. Won't connect to any network though.
Modem
Followed an approach described here with no luck: getting smd_pkt_open: DATA5_CNTL open failed -19
in dmesg
while trying to access the modem.
With echo 1 > /sys/kernel/boot_adsp/boot
modem at least boots up (using rmt_storage
binary ripped out of KaiOS), but DATA5_CNTL
is still unavailable.
Allocation tables (output of /sys/kernel/debug/smd/ch
) is here.
According to the following lines in dmesg
, it looks like something tries to reach USB diag device which is not available:
[ 502.693072] diag: USB ch diag is not connected
[ 502.693080] diag: In diag_process_smd_read_data, diag_device_write error: -19
Tried to set the following USB configuration options with no luck as well:
# echo "0" > /sys/class/android_usb/android0/enable
# echo "diag" > /sys/class/android_usb/android0/f_diag/clients
# echo "smd" > /sys/class/android_usb/android0/f_serial/transports
# echo "qti,bam" > /sys/class/android_usb/android0/f_rmnet/transports
# echo "diag,serial_smd,rmnet_qti_bam" > /sys/class/android_usb/android0/functions
# echo "1" > /sys/class/android_usb/android0/enable
It is possible that the modem requires sending a DPM (data port management) QMI command to open up the DATA5_CNTL
channel, as done here for the Nokia 8110 4G.
Partition layout
DDR -> /dev/block/mmcblk0p24
aboot -> /dev/block/mmcblk0p9
abootbak -> /dev/block/mmcblk0p10
boot -> /dev/block/mmcblk0p27
cache -> /dev/block/mmcblk0p31
config -> /dev/block/mmcblk0p19
devinfo -> /dev/block/mmcblk0p23
fsc -> /dev/block/mmcblk0p5
fsg -> /dev/block/mmcblk0p25
hwcfg -> /dev/block/mmcblk0p21
keystore -> /dev/block/mmcblk0p18
misc -> /dev/block/mmcblk0p16
modem -> /dev/block/mmcblk0p22
modemst1 -> /dev/block/mmcblk0p3
modemst2 -> /dev/block/mmcblk0p4
oem -> /dev/block/mmcblk0p32
pad -> /dev/block/mmcblk0p15
persist -> /dev/block/mmcblk0p29
recovery -> /dev/block/mmcblk0p28
rpm -> /dev/block/mmcblk0p11
rpmbak -> /dev/block/mmcblk0p12
sbl1 -> /dev/block/mmcblk0p7
sbl1bak -> /dev/block/mmcblk0p8
sec -> /dev/block/mmcblk0p26
simlock -> /dev/block/mmcblk0p20
splash -> /dev/block/mmcblk0p17
ssd -> /dev/block/mmcblk0p6
system -> /dev/block/mmcblk0p30
traceability -> /dev/block/mmcblk0p1
tunning -> /dev/block/mmcblk0p2
tz -> /dev/block/mmcblk0p13
tzbak -> /dev/block/mmcblk0p14
userdata -> /dev/block/mmcblk0p33