[Android 4.2+][ROOT][2017.09.21] FlashFire v0.73

[Chainfire]

@Chainfire, as I did not receive your reply, I will repost.

I looked in all my logs after black screen and reboot and other people who posted logs here with the same problem and everyone has the following error:

c: echo flashfire > /sys/power/wake_lock: No such file or directory

I checked with file manager and the file exists. It appears just after getprop lines. Maybe you did not notice that?
Although the ">" (overwrite), The command is working as ">>" (append), Is that right?

This is normal behavior since 5.0 or so.

 

[StupidIdea]

I found a possible issue going through the code again, I sent you a link to a test version through PM.

Let me know if that one works for you.

First it showed a pop up "OTA update failed". After that the app deleted the OTA so I had to re-download it.
I started the app the second time and the decryption passed and it rebooted to your custom bootloader. It restored bootloader and recovery. And then showed "Flashing update.zip" (or something similar) for a really short time (~1sec). After that it rebooted to broken robot page with "No command" message. It had 3 circles on the bottom (2 filled, 1 empty) if that means anything. It keeps rebooting to the same screen about every 10sec but I can boot to stock bootloader/recovery so it's all fine.
Let me know if you want me to get something with TWRP now. If not then I can fastboot flash 7.1.1 and try it again.

 

[Chainfire]

First it showed a pop up "OTA update failed". After that the app deleted the OTA so I had to re-download it.
I started the app the second time and the decryption passed and it rebooted to your custom bootloader. It restored bootloader and recovery. And then showed "Flashing update.zip" (or something similar) for a really short time (~1sec). After that it rebooted to broken robot page with "No command" message. It had 3 circles on the bottom (2 filled, 1 empty) if that means anything. It keeps rebooting to the same screen about every 10sec but I can boot to stock bootloader/recovery so it's all fine.
Let me know if you want me to get something with TWRP now. If not then I can fastboot flash 7.1.1 and try it again.

Can you grab /sdcard/FlashFire/lastlog ?

 

[KaMyKaSii]

This is normal behavior since 5.0 or so.

I had already posted a continuous logcat where I tried to back up by adb (to keep adb active and to be able to capture the log). Could you take a look at it? As it is at the end of the log, the SurfaceFlinger service has died, I hope you can find the solution. Thank you

https://drive.google.com/file/d/0B1uvONk-jlRiU3AyLWVncEdab1E/view?usp=drivesdk

 

[StupidIdea]

Attached. Renamed to .txt so I can attach uncompressed.

Edit: I'm still on TWRP. /system is empty.

Can you grab /sdcard/FlashFire/lastlog ?

 

[g0d0fmischief]

Reproduce is a big word - while I've seen the issue occur a few times, I cannot reproduce it at will, which makes debugging it very difficult. For example, I just did 4 monthly updates in a row on my 6P without any issue.

The contents of /cache/recovery may help me diagnose.

I'm one of the one who absolutely can't get it to work without crashing during uncrypting if there's any info I can give you to help I will

Sent from my Nexus 5X using Tapatalk

 

[StupidIdea]

@Chainfire
1) Flashed again 7.1.1 and CFAutoRoot
2) At first FlashFire didn't see the OTA so I started system update, that restarted the phone and failed to update (obviously). Then FlashFire showed OTA too
3) FlashFire showed red error that updater.zip.uncoded (or something like that) is not ZIP file, patcher bootloader, injected root and phone booted again to 7.1.1.
4) OTA was gone so I redownloaded it.
5) Started update with FlashFire and the result was the same as the previous time (no ZIP error this time): short message about flashing update.zip and phone rebooted to No command.

I'm flashing 7.1.1 back so I should be at step 2.

 

[Chainfire]

So things are getting a bit tricky.

- It seems I have solved the uncryption problem itself.

- However, the latest OTAs are doing a multi-stage update that isn't (yet) compatible with FlashFire. I'm trying to figure out how this works exactly, this might be tricky to actually fix. This is what causes the reboot and getting stuck in recovery (reflashing a working boot image should let you boot again).

- The red error of the update not being a ZIP file is normal if uncrypted updates fail. This is due to a left-over mapping file that is now pointing to incorrect data, which results in garbage rather than the update ZIP we want to flash.

- After failed attempts, wipe cache and re-download the OTA.

 

[StupidIdea]

So things are getting a bit tricky.

- It seems I have solved the uncryption problem itself.

- However, the latest OTAs are doing a multi-stage update that isn't (yet) compatible with FlashFire. I'm trying to figure out how this works exactly, this might be tricky to actually fix. This is what causes the reboot and getting stuck in recovery (reflashing a working boot image should let you boot again).

- The red error of the update not being a ZIP file is normal if uncrypted updates fail. This is due to a left-over mapping file that is now pointing to incorrect data, which results in garbage rather than the update ZIP we want to flash.

- After failed attempts, wipe cache and re-download the OTA.

Thank you. It was fun while it lasted . PM or mention me if you want me to test something (I will keep 7.1.1 for now) but I understand you can reproduce it with 7.1.2 ota.

 

[Ch3vr0n]

We all have faith you'll fix things. The weird thing though @Chainfire if you manually download the incremental (or full) OTA (from the Google servers directly via browser) it goes through the what you call 'multi stage' process absolutely fine. And that's exactly what I've been doing since I first reported me having that uncrypting error.

Verstuurd vanaf mijn Nexus 6P met Tapatalk

 

[Chainfire]

We all have faith you'll fix things. The weird thing though @Chainfire if you manually download the incremental (or full) OTA (from the Google servers directly via browser) it goes through the what you call 'multi stage' process absolutely fine. And that's exactly what I've been doing since I first reported me having that uncrypting error.

The full OTAs aren't multi-stage as far as I know. At least the latest 5X and 6P full OTA's aren't - I just downloaded them to check.

 

[Ch3vr0n]

I only flashed a full one once Sunday far, cause the Feb OTA was stuck in a download loop

Verstuurd vanaf mijn Nexus 6P met Tapatalk

 

[Chainfire]

@KaMyKaSii do you still have those devices without names in /dev/block/... ?

Does this device have /proc/dumchar_info and if so, what are the contents?

 

[KaMyKaSii]

@KaMyKaSii do you still have those devices without names in /dev/block/... ?

Does this device have /proc/dumchar_info and if so, what are the contents?

No, my device has partitions listed by names. FlashFire recognizes the partitions without any workaround or something. In roms based on Lollipop, FlashFire worked perfectly (until the time I used it). In Marshmallow it rarely worked but mostly not. And my device does not have the /proc/dumchar_info file. Below is the contents of my /dev/block, informe me of any other information you may need.

/dev/block/:
total 0
drwxr-xr-x    4 0        0              840 Apr  1 03:39 .
drwxr-xr-x   15 0        0             3340 Apr  1 03:39 ..
brw-------    1 0        0           7,   0 Apr  1 03:39 loop0
brw-------    1 0        0           7,   1 Apr  1 03:39 loop1
brw-------    1 0        0           7,   2 Apr  1 03:39 loop2
brw-------    1 0        0           7,   3 Apr  1 03:39 loop3
brw-------    1 0        0           7,   4 Apr  1 03:39 loop4
brw-------    1 0        0           7,   5 Apr  1 03:39 loop5
brw-------    1 0        0           7,   6 Apr  1 03:39 loop6
brw-------    1 0        0           7,   7 Apr  1 03:39 loop7
brw-rw----    1 0        1000      179,   0 Apr  1 03:39 mmcblk0
brw-rw----    1 0        1000      179,  32 Apr  1 03:39 mmcblk0boot0
brw-rw----    1 0        1000      179,  64 Apr  1 03:39 mmcblk0boot1
brw-rw----    1 0        1000      179,   1 Apr  1 03:39 mmcblk0p1
brw-------    1 0        0         179,  10 Apr  1 03:39 mmcblk0p10
brw-rw----    1 0        1000      179,  11 Apr  1 03:39 mmcblk0p11
brw-------    1 0        0         179,  12 Apr  1 03:39 mmcblk0p12
brw-r-----    1 0        1000      179,  13 Apr  1 03:39 mmcblk0p13
brw-------    1 0        0         179,  14 Apr  1 03:39 mmcblk0p14
brw-------    1 0        0         179,  15 Apr  1 03:39 mmcblk0p15
brw-------    1 0        0         179,  16 Apr  1 03:39 mmcblk0p16
brw-rw----    1 0        1000      179,  17 Apr  1 03:42 mmcblk0p17
brw-------    1 0        0         179,  18 Apr  1 03:39 mmcblk0p18
brw-------    1 0        0         179,  19 Apr  1 03:39 mmcblk0p19
brw-rw----    1 0        1000      179,   2 Apr  1 03:39 mmcblk0p2
brw-------    1 0        0         179,  20 Apr  1 03:39 mmcblk0p20
brw-------    1 0        0         179,  21 Apr  1 03:39 mmcblk0p21
brw-------    1 0        0         179,  22 Apr  1 03:39 mmcblk0p22
brw-------    1 0        0         179,  23 Apr  1 03:39 mmcblk0p23
brw-------    1 0        0         179,   3 Apr  1 03:39 mmcblk0p3
brw-------    1 0        0         179,   4 Apr  1 03:39 mmcblk0p4
brw-------    1 0        0         179,   5 Apr  1 03:39 mmcblk0p5
brw-rw----    1 0        1000      179,   6 Apr  1 03:39 mmcblk0p6
brw-r-----    1 0        1000      179,   7 Apr  1 03:39 mmcblk0p7
brw-r-----    1 0        1000      179,   8 Apr  1 03:39 mmcblk0p8
brw-rw----    1 0        1000      179,   9 Apr  1 03:39 mmcblk0p9
brw-------    1 0        0         179,  96 Apr  1 03:39 mmcblk0rpmb
brw-------    1 0        0         179, 128 Apr  1 03:39 mmcblk1
brw-------    1 0        0         179, 129 Apr  1 03:39 mmcblk1p1
drwxr-xr-x    3 0        0               60 Apr  1 03:39 platform
drwx------    2 0        0               80 Apr  1 03:40 vold
brw-------    1 0        0         254,   0 Apr  1 03:39 zram0

/dev/block/platform:
total 0
drwxr-xr-x    3 0        0               60 Apr  1 03:39 .
drwxr-xr-x    4 0        0              840 Apr  1 03:39 ..
drwxr-xr-x    4 0        0               80 Apr  1 03:39 mtk-msdc.0

/dev/block/platform/mtk-msdc.0:
total 0
drwxr-xr-x    4 0        0               80 Apr  1 03:39 .
drwxr-xr-x    3 0        0               60 Apr  1 03:39 ..
drwxr-xr-x    4 0        0              620 Apr  1 03:39 11230000.msdc0
drwxr-xr-x    3 0        0              100 Apr  1 03:39 11240000.msdc1

/dev/block/platform/mtk-msdc.0/11230000.msdc0:
total 0
drwxr-xr-x    4 0        0              620 Apr  1 03:39 .
drwxr-xr-x    4 0        0               80 Apr  1 03:39 ..
drwxr-xr-x    2 0        0              500 Apr  1 03:39 by-name
drwxr-xr-x    2 0        0              500 Apr  1 03:39 by-num
lrwxrwxrwx    1 0        0               18 Apr  1 03:39 mmcblk0 -> /dev/block/mmcblk0
lrwxrwxrwx    1 0        0               23 Apr  1 03:39 mmcblk0boot0 -> /dev/block/mmcblk0boot0
lrwxrwxrwx    1 0        0               23 Apr  1 03:39 mmcblk0boot1 -> /dev/block/mmcblk0boot1
lrwxrwxrwx    1 0        0               20 Apr  1 03:39 mmcblk0p1 -> /dev/block/mmcblk0p1
lrwxrwxrwx    1 0        0               21 Apr  1 03:39 mmcblk0p10 -> /dev/block/mmcblk0p10
lrwxrwxrwx    1 0        0               21 Apr  1 03:39 mmcblk0p11 -> /dev/block/mmcblk0p11
lrwxrwxrwx    1 0        0               21 Apr  1 03:39 mmcblk0p12 -> /dev/block/mmcblk0p12
lrwxrwxrwx    1 0        0               21 Apr  1 03:39 mmcblk0p13 -> /dev/block/mmcblk0p13
lrwxrwxrwx    1 0        0               21 Apr  1 03:39 mmcblk0p14 -> /dev/block/mmcblk0p14
lrwxrwxrwx    1 0        0               21 Apr  1 03:39 mmcblk0p15 -> /dev/block/mmcblk0p15
lrwxrwxrwx    1 0        0               21 Apr  1 03:39 mmcblk0p16 -> /dev/block/mmcblk0p16
lrwxrwxrwx    1 0        0               21 Apr  1 03:39 mmcblk0p17 -> /dev/block/mmcblk0p17
lrwxrwxrwx    1 0        0               21 Apr  1 03:39 mmcblk0p18 -> /dev/block/mmcblk0p18
lrwxrwxrwx    1 0        0               21 Apr  1 03:39 mmcblk0p19 -> /dev/block/mmcblk0p19
lrwxrwxrwx    1 0        0               20 Apr  1 03:39 mmcblk0p2 -> /dev/block/mmcblk0p2
lrwxrwxrwx    1 0        0               21 Apr  1 03:39 mmcblk0p20 -> /dev/block/mmcblk0p20
lrwxrwxrwx    1 0        0               21 Apr  1 03:39 mmcblk0p21 -> /dev/block/mmcblk0p21
lrwxrwxrwx    1 0        0               21 Apr  1 03:39 mmcblk0p22 -> /dev/block/mmcblk0p22
lrwxrwxrwx    1 0        0               21 Apr  1 03:39 mmcblk0p23 -> /dev/block/mmcblk0p23
lrwxrwxrwx    1 0        0               20 Apr  1 03:39 mmcblk0p3 -> /dev/block/mmcblk0p3
lrwxrwxrwx    1 0        0               20 Apr  1 03:39 mmcblk0p4 -> /dev/block/mmcblk0p4
lrwxrwxrwx    1 0        0               20 Apr  1 03:39 mmcblk0p5 -> /dev/block/mmcblk0p5
lrwxrwxrwx    1 0        0               20 Apr  1 03:39 mmcblk0p6 -> /dev/block/mmcblk0p6
lrwxrwxrwx    1 0        0               20 Apr  1 03:39 mmcblk0p7 -> /dev/block/mmcblk0p7
lrwxrwxrwx    1 0        0               20 Apr  1 03:39 mmcblk0p8 -> /dev/block/mmcblk0p8
lrwxrwxrwx    1 0        0               20 Apr  1 03:39 mmcblk0p9 -> /dev/block/mmcblk0p9
lrwxrwxrwx    1 0        0               22 Apr  1 03:39 mmcblk0rpmb -> /dev/block/mmcblk0rpmb

/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name:
total 0
drwxr-xr-x    2 0        0              500 Apr  1 03:39 .
drwxr-xr-x    4 0        0              620 Apr  1 03:39 ..
lrwxrwxrwx    1 0        0               20 Apr  1 03:39 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx    1 0        0               21 Apr  1 03:39 cache -> /dev/block/mmcblk0p21
lrwxrwxrwx    1 0        0               21 Apr  1 03:39 expdb -> /dev/block/mmcblk0p10
lrwxrwxrwx    1 0        0               21 Apr  1 03:39 flashinfo -> /dev/block/mmcblk0p23
lrwxrwxrwx    1 0        0               21 Apr  1 03:39 frp -> /dev/block/mmcblk0p17
lrwxrwxrwx    1 0        0               21 Apr  1 03:39 keystore -> /dev/block/mmcblk0p14
lrwxrwxrwx    1 0        0               20 Apr  1 03:39 lk -> /dev/block/mmcblk0p5
lrwxrwxrwx    1 0        0               20 Apr  1 03:39 logo -> /dev/block/mmcblk0p9
lrwxrwxrwx    1 0        0               21 Apr  1 03:39 metadata -> /dev/block/mmcblk0p19
lrwxrwxrwx    1 0        0               21 Apr  1 03:39 nvdata -> /dev/block/mmcblk0p18
lrwxrwxrwx    1 0        0               20 Apr  1 03:39 nvram -> /dev/block/mmcblk0p2
lrwxrwxrwx    1 0        0               21 Apr  1 03:39 oemkeystore -> /dev/block/mmcblk0p12
lrwxrwxrwx    1 0        0               20 Apr  1 03:39 para -> /dev/block/mmcblk0p6
lrwxrwxrwx    1 0        0               20 Apr  1 03:39 proinfo -> /dev/block/mmcblk0p1
lrwxrwxrwx    1 0        0               20 Apr  1 03:39 protect1 -> /dev/block/mmcblk0p3
lrwxrwxrwx    1 0        0               20 Apr  1 03:39 protect2 -> /dev/block/mmcblk0p4
lrwxrwxrwx    1 0        0               20 Apr  1 03:39 recovery -> /dev/block/mmcblk0p8
lrwxrwxrwx    1 0        0               21 Apr  1 03:39 seccfg -> /dev/block/mmcblk0p11
lrwxrwxrwx    1 0        0               21 Apr  1 03:39 secro -> /dev/block/mmcblk0p13
lrwxrwxrwx    1 0        0               21 Apr  1 03:39 system -> /dev/block/mmcblk0p20
lrwxrwxrwx    1 0        0               21 Apr  1 03:39 tee1 -> /dev/block/mmcblk0p15
lrwxrwxrwx    1 0        0               21 Apr  1 03:39 tee2 -> /dev/block/mmcblk0p16
lrwxrwxrwx    1 0        0               21 Apr  1 03:39 userdata -> /dev/block/mmcblk0p22

/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-num:
total 0
drwxr-xr-x    2 0        0              500 Apr  1 03:39 .
drwxr-xr-x    4 0        0              620 Apr  1 03:39 ..
lrwxrwxrwx    1 0        0               20 Apr  1 03:39 p1 -> /dev/block/mmcblk0p1
lrwxrwxrwx    1 0        0               21 Apr  1 03:39 p10 -> /dev/block/mmcblk0p10
lrwxrwxrwx    1 0        0               21 Apr  1 03:39 p11 -> /dev/block/mmcblk0p11
lrwxrwxrwx    1 0        0               21 Apr  1 03:39 p12 -> /dev/block/mmcblk0p12
lrwxrwxrwx    1 0        0               21 Apr  1 03:39 p13 -> /dev/block/mmcblk0p13
lrwxrwxrwx    1 0        0               21 Apr  1 03:39 p14 -> /dev/block/mmcblk0p14
lrwxrwxrwx    1 0        0               21 Apr  1 03:39 p15 -> /dev/block/mmcblk0p15
lrwxrwxrwx    1 0        0               21 Apr  1 03:39 p16 -> /dev/block/mmcblk0p16
lrwxrwxrwx    1 0        0               21 Apr  1 03:39 p17 -> /dev/block/mmcblk0p17
lrwxrwxrwx    1 0        0               21 Apr  1 03:39 p18 -> /dev/block/mmcblk0p18
lrwxrwxrwx    1 0        0               21 Apr  1 03:39 p19 -> /dev/block/mmcblk0p19
lrwxrwxrwx    1 0        0               20 Apr  1 03:39 p2 -> /dev/block/mmcblk0p2
lrwxrwxrwx    1 0        0               21 Apr  1 03:39 p20 -> /dev/block/mmcblk0p20
lrwxrwxrwx    1 0        0               21 Apr  1 03:39 p21 -> /dev/block/mmcblk0p21
lrwxrwxrwx    1 0        0               21 Apr  1 03:39 p22 -> /dev/block/mmcblk0p22
lrwxrwxrwx    1 0        0               21 Apr  1 03:39 p23 -> /dev/block/mmcblk0p23
lrwxrwxrwx    1 0        0               20 Apr  1 03:39 p3 -> /dev/block/mmcblk0p3
lrwxrwxrwx    1 0        0               20 Apr  1 03:39 p4 -> /dev/block/mmcblk0p4
lrwxrwxrwx    1 0        0               20 Apr  1 03:39 p5 -> /dev/block/mmcblk0p5
lrwxrwxrwx    1 0        0               20 Apr  1 03:39 p6 -> /dev/block/mmcblk0p6
lrwxrwxrwx    1 0        0               20 Apr  1 03:39 p7 -> /dev/block/mmcblk0p7
lrwxrwxrwx    1 0        0               20 Apr  1 03:39 p8 -> /dev/block/mmcblk0p8
lrwxrwxrwx    1 0        0               20 Apr  1 03:39 p9 -> /dev/block/mmcblk0p9

/dev/block/platform/mtk-msdc.0/11240000.msdc1:
total 0
drwxr-xr-x    3 0        0              100 Apr  1 03:39 .
drwxr-xr-x    4 0        0               80 Apr  1 03:39 ..
drwxr-xr-x    2 0        0               60 Apr  1 03:39 by-num
lrwxrwxrwx    1 0        0               18 Apr  1 03:39 mmcblk1 -> /dev/block/mmcblk1
lrwxrwxrwx    1 0        0               20 Apr  1 03:39 mmcblk1p1 -> /dev/block/mmcblk1p1

/dev/block/platform/mtk-msdc.0/11240000.msdc1/by-num:
total 0
drwxr-xr-x    2 0        0               60 Apr  1 03:39 .
drwxr-xr-x    3 0        0              100 Apr  1 03:39 ..
lrwxrwxrwx    1 0        0               20 Apr  1 03:39 p1 -> /dev/block/mmcblk1p1

/dev/block/vold:
total 0
drwx------    2 0        0               80 Apr  1 03:40 .
drwxr-xr-x    4 0        0              840 Apr  1 03:39 ..
brw-------    1 0        0         179, 128 Apr  1 03:39 disk:179,128
brw-------    1 0        0         179, 129 Apr  1 03:40 public:179,129

Useless information for the black screen case but maybe important for compatibility with by-num devices:
There are two variants of my device: one with MT6753 arm64, which I have. And one with MT6592M armv-7. The second one does have the /proc/dumchar_info file but it did not have its partitions recognized by FlashFire (since it is not a by-name device). As another user pointed out [URL='https://forum.xda-developers.com/general/paid-software/flashfire-t3075433/post70420203]here[/URL], you can make FlashFire recognize the main partitions (recovery, system, cache, data) by doing symlinks (like creating /dev/block/platform/by-name directory and then ln -s /dev/recovery /dev/block/platform/by-name/recovery). A friend tested this and the backup functions in FlashFire worked perfectly except for boot partition (/dev/bootimg)

 

[Sczar]

@KaMyKaSii do you still have those devices without names in /dev/block/... ?

Does this device have /proc/dumchar_info and if so, what are the contents?

No, my device has partitions listed by names. FlashFire recognizes the partitions without any workaround or something. In roms based on Lollipop, FlashFire worked perfectly (until the time I used it). In Marshmallow it rarely worked but mostly not. And my device does not have the /proc/dumchar_info file. Below is the contents of my /dev/block, informe me of any other information you may need.



Useless information for the black screen case but maybe important for compatibility with by-num devices:
There are two variants of my device: one with MT6753 arm64, which I have. And one with MT6592M armv-7. The second one does have the /proc/dumchar_info file but it did not have its partitions recognized by FlashFire (since it is not a by-name device). As another user pointed out here, you can make FlashFire recognize the main partitions (recovery, system, cache, data) by doing symlinks (like creating /dev/block/platform/by-name directory and then ln -s /dev/recovery /dev/block/platform/by-name/recovery). A friend tested this and the backup functions in FlashFire worked perfectly except for boot partition (/dev/bootimg)

@Chainfire

Similar problem with my device. N900v

In LP works fine but when I flashed MM. Flashfire seems to be not working.

c: echo flashfire > /sys/power/wake_lock: No such file or directory

If I attend to flash recovery or simple as wiping anything. The screen will go off then the device will reboot normally. Nothing been done.

Thanks in advance

 

[Chainfire]

The second one does have the /proc/dumchar_info file but it did not have its partitions recognized by FlashFire (since it is not a by-name device). As another user pointed out here, you can make FlashFire recognize the main partitions (recovery, system, cache, data) by doing symlinks (like creating /dev/block/platform/by-name directory and then ln -s /dev/recovery /dev/block/platform/by-name/recovery). A friend tested this and the backup functions in FlashFire worked perfectly except for boot partition (/dev/bootimg)

I see and understand. After some further reading, it appears common for boot partition to not even have a numbered partition. This makes it hard for FlashFire to deal with - it is not designed to write index into the parent block device, which would be required in this case.

 

[KaMyKaSii]

I see and understand. After some further reading, it appears common for boot partition to not even have a numbered partition. This makes it hard for FlashFire to deal with - it is not designed to write index into the parent block device, which would be required in this case.

Well, in the case of my friend's cell phone, the only numbered partitions are those with ext4 file system. Then system, cache, data. Although the recovery partition is not numbered, it is present in dev/recovery so you can make changes to it without resorting to modifying the whole device block (/dev/block/mmcblk0). Although the boot partition (/dev/bootimg) is also present, it can not be backed up. This in Android booted (trying to copy the "file" or by FlashFire). TWRP works perfectly. Below is the TWRP fstab of my friend's device.

# mount point fstype device [device2]

/boot emmc /dev/bootimg
/system ext4 /[email protected]
/cache ext4 /[email protected]
/data ext4 /[email protected]
/external_sd auto /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=display="SD Card";storage;removable
/sd-ext auto /dev/block/mmcblk1p2

These "[email protected]" I think are symlinks pointing to the respective partition. Also below is some links in the Magisk topic where I tell how changes to the partition of these devices without the numbered boot partition can be made .

https://forum.xda-developers.com/ap...v1-universal-systemless-t3432382/post68909842

https://forum.xda-developers.com/ap...v1-universal-systemless-t3432382/post68910624

And about the logcat of my device, you had already explained to me about the SurfaceFlinger service activate the bootanimation on the screen to keep all the pixels alive and considering that he died before the mobile reboot, does not that mean he is the problem?

 

[Chainfire]

Thank you. It was fun while it lasted . PM or mention me if you want me to test something (I will keep 7.1.1 for now) but I understand you can reproduce it with 7.1.2 ota.

Have you had a chance to test the last version I sent you in PM ?

 

[Chainfire]

Well, in the case of my friend's cell phone, the only numbered partitions are those with ext4 file system. Then system, cache, data. Although the recovery partition is not numbered, it is present in dev/recovery so you can make changes to it without resorting to modifying the whole device block (/dev/block/mmcblk0). Although the boot partition (/dev/bootimg) is also present, it can not be backed up. This in Android booted (trying to copy the "file" or by FlashFire). TWRP works perfectly. Below is the TWRP fstab of my friend's device.

These "[email protected]" I think are symlinks pointing to the respective partition. Also below is some links in the Magisk topic where I tell how changes to the partition of these devices without the numbered boot partition can be made .

https://forum.xda-developers.com/ap...v1-universal-systemless-t3432382/post68909842

https://forum.xda-developers.com/ap...v1-universal-systemless-t3432382/post68910624

Yes, I understand fully how this works. Apparently, TWRP has code to cope with this, but FlashFire wasn't built for it. It does support reading this sort of partition, but not writing. The code changes required to support this are too large (and risky) to perform without a test-device in-hand, though.

And about the logcat of my device, you had already explained to me about the SurfaceFlinger service activate the bootanimation on the screen to keep all the pixels alive and considering that he died before the mobile reboot, does not that mean he is the problem?

Not necessarily. It might, but it is very difficult to tell.

 

[Chainfire]

RE: Android O

I did some playing with Android O, but they changed some important things in SurfaceFlinger. I'm probably going to have to wait for the O sources before I can fix compatibility.