• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

TWRP 3.5.2-11 for Sunfish[Testing]

Search This thread

mangokm40

Senior Member
Jan 13, 2019
102
46
I'm on LOS18.1 08-12-2021 & Lineage recovery 08-12-2021. I've no custom kernel. I've no GApps. Magisk was not installed during this test.

I used "fastboot boot test5.img" and booted successfully to TWRP.

However, I also got the 255 error.
I don't have the 999 folders. I attached a screenshot showing the "multiple users" setting is off.

I've attached the recovery.log, in case it helps @nikamura in any way.
 

Attachments

  • Screenshot.png
    Screenshot.png
    47.9 KB · Views: 39
Last edited:

TheSayaMan

Senior Member
Sep 12, 2016
242
117
I'm on LOS18.1 08-12-2021 & Lineage recovery 08-12-2021. I've no custom kernel. I've no GApps. Magisk was not installed during this test.

I used "fastboot boot test5.img" and booted successfully to TWRP.

However, I also got the 255 error.
I don't have the 999 folders. I attached a screenshot showing the "multiple users" setting is off.

I've attached the recovery.log, in case it help @nikamura in any way.
It's possible but unlikely that some parallel apps could go in folders other than 999. There are no parallel apps installed on your device? Parallel apps would also be referred to as clone apps which are apps that clone another. Basically you could clone any app with a cloner and log into two different accounts. This would cause problems. If this is not the case than it would need to be addressed with the dev for a fix.
 
  • Like
Reactions: mangokm40

mangokm40

Senior Member
Jan 13, 2019
102
46
It's possible but unlikely that some parallel apps could go in folders other than 999. There are no parallel apps installed on your device? Parallel apps would also be referred to as clone apps which are apps that clone another. Basically you could clone any app with a cloner and log into two different accounts. This would cause problems. If this is not the case than it would need to be addressed with the dev for a fix.
Pardon my neophyte's ignorance.
I did not clone any apps, as I wouldn't know how to do it. If it's of any use,
the only account I have in "Settings->Accounts" is for Signal Messenger.

I also noticed that my recovery.log attachment is gone. I hope I didn't break a rule by attaching that. :) I thought it would be useful for nikamura.

Thanks for all the time you've taken trying to help us in this thread.
 
I built and test TWRP for stock ROM A10 and A11 version.
I didn't test it on custom ROMs.

I would like to test it on latest version, but my pixel4a dosen't have enough storage changing firmware from stock ROM to custom ROM.

Can anyone test TWRP test6 build?

https://drive.google.com/file/d/1mB73pX_0UQQA4PNPvqBBWqSZ6TixZfho/view?usp=sharing
Booted. Installed. Took a backup. Did not try to restore. Seems to work fine though.
Kernel - Blu_spark r117
Magisk v23
LSPosed v153
 
  • Like
Reactions: mangokm40

JohnC

Senior Member
May 5, 2007
572
117
Amazon Fire TV
Google Pixel 4a
This might sound like a newbie question, but are these new builds of TWRP OS independent?

Meaning can I use the above test6 build on my A10 Pixel 4a?

Or do I have to wait until a build is made specifically for Pixel 4a Sunfish FM QD4A.200805.003?
 

mangokm40

Senior Member
Jan 13, 2019
102
46
This might sound like a newbie question, but are these new builds of TWRP OS independent?

Meaning can I use the above test6 build on my A10 Pixel 4a?

Or do I have to wait until a build is made specifically for Pixel 4a Sunfish FM QD4A.200805.003?
1. TWRP is not an OS.

2. If you look at post #1 of this topic, you'll see:

"Android11 FW
test6"

This is to let us know that test 6 is for Android11.

3. In that same, first post, you'll see a link to:

"Andriod10 FW https://drive.google.com/file/d/1PZaU9PpYmdcAHlyi0zhNwEGnBsAHDW_E/view?usp=sharing
It's tested both FW version QD4A.200805.001 and QD4A.200805.003."

This is from last year, though. You'll have to read the early posts in this topic to find out if it was working well.

Hope this helps.
 
  • Like
Reactions: JohnC

JohnC

Senior Member
May 5, 2007
572
117
Amazon Fire TV
Google Pixel 4a
Thanks for the info. That is what I thought, but when nikamura said in a recent post "I built and test TWRP for stock ROM A10 and A11 version." it seemed to suggest that he might have "recently" rebuilt the A10 version (because his post was from the other day).

But when I checked, the A10 file in the OP didn't look like it was updated, so that made me think maybe the latest build he did recently post might work on A10 (if TWRP was not OS dependent), hence my question for clarification.

So, the end result is that I will need to wait for an A10 version to be built using the newer 3.5.2-11 version of TWRP.
 

mangokm40

Senior Member
Jan 13, 2019
102
46
I built and test TWRP for stock ROM A10 and A11 version.
I didn't test it on custom ROMs.

I would like to test it on latest version, but my pixel4a dosen't have enough storage changing firmware from stock ROM to custom ROM.

Can anyone test TWRP test6 build?

https://drive.google.com/file/d/1mB73pX_0UQQA4PNPvqBBWqSZ6TixZfho/view?usp=sharing
I'm on LineageOS 18 09.16.2021. I have LOS recovery 09.16.2021. There's no GApps, Magisk, or custom kernel.
I used "fastboot boot twrp6.img" to start TWRP.

It booted fine. The backup started this time. There was no error 255. :)
However, the backup failed. It created 5 files. "data.f2fs.win000, data.f2fs.win001, data.f2fs.win002, data.f2fs.win003, data.f2fs.win004" are their filenames.

I don't know if it's OK to post from the recovery.log file. These lines are at the bottom:


I:createTarFork() process ended with RC=0
* Generating digest...
I:SHA2 Digest: 559c094062948f2be7dc9090f7a8ad45b4cc8c8a3c67437cfbdc2dcc76a92f47 data.f2fs.win000
I:digest_filename: /data/media/0/TWRP/BACKUPS/0C251JEC201764/1970-09-30--06-59-08_lineage_sunfish-userdebug_11_RQ3A210905001/data.f2fs.win000.sha2
* Digest Error!
Backup Failed. Cleaning Backup Folder.


As you can see, the createTarFork() didn't return an error with test6. However, I don't get any details for the generic "Digest Error!"

Thanks for your continued time on this. I imagine custom ROMs are a nuisance.
 

Attachments

  • recovery.log.zip
    378.5 KB · Views: 1
Last edited:
  • Like
Reactions: DiamondJohn

nikamura

Member
May 18, 2010
37
91
Google Pixel 4a
Thanks for the info. That is what I thought, but when nikamura said in a recent post "I built and test TWRP for stock ROM A10 and A11 version." it seemed to suggest that he might have "recently" rebuilt the A10 version (because his post was from the other day).

But when I checked, the A10 file in the OP didn't look like it was updated, so that made me think maybe the latest build he did recently post might work on A10 (if TWRP was not OS dependent), hence my question for clarification.

So, the end result is that I will need to wait for an A10 version to be built using the newer 3.5.2-11 version of TWRP.

I’m sorry if I caused a misunderstanding.
I'm building TWRP for A11 version now.

I'll build TWRP for A10 new version, if I have time.
 

nikamura

Member
May 18, 2010
37
91
Google Pixel 4a
I'm on LineageOS 18 09.16.2021. I have LOS recovery 09.16.2021. There's no GApps, Magisk, or custom kernel.
I used "fastboot boot twrp6.img" to start TWRP.

It booted fine. The backup started this time. There was no error 255. :)
However, the backup failed. It created 5 files. "data.f2fs.win000, data.f2fs.win001, data.f2fs.win002, data.f2fs.win003, data.f2fs.win004" are their filenames.

I don't know if it's OK to post from the recovery.log file. These lines are at the bottom:


I:createTarFork() process ended with RC=0
* Generating digest...
I:SHA2 Digest: 559c094062948f2be7dc9090f7a8ad45b4cc8c8a3c67437cfbdc2dcc76a92f47 data.f2fs.win000
I:digest_filename: /data/media/0/TWRP/BACKUPS/0C251JEC201764/1970-09-30--06-59-08_lineage_sunfish-userdebug_11_RQ3A210905001/data.f2fs.win000.sha2
* Digest Error!
Backup Failed. Cleaning Backup Folder.


As you can see, the createTarFork() didn't return an error with test6. However, I don't get any details for the generic "Digest Error!"

Thanks for your continued time on this. I imagine custom ROMs are a nuisance.

Thank you for testing.
Do you check Backup Option "Skip Digest~"?

Could you upload the recovery.log?
 
  • Like
Reactions: mangokm40

mangokm40

Senior Member
Jan 13, 2019
102
46
I attached the previous "recovery.log" to my prior message.

I booted with "fastboot boot twrp.img"
The setting: Settings->"Skip Digest generation during backup" was not checked. I checked it.
I started a backup and it completed successfully.
Unfortunately, this phone has become my daily-driver. I didn't dare test a restore. :)

I attached the recovery.log file from this, successful backup.
 

Attachments

  • recovery.log.zip
    378.7 KB · Views: 4
  • Like
Reactions: DiamondJohn

nikamura

Member
May 18, 2010
37
91
Google Pixel 4a
I attached the previous "recovery.log" to my prior message.

I booted with "fastboot boot twrp.img"
The setting: Settings->"Skip Digest generation during backup" was not checked. I checked it.
I started a backup and it completed successfully.
Unfortunately, this phone has become my daily-driver. I didn't dare test a restore. :)

I attached the recovery.log file from this, successful backup.

Sorry, I missed previous "recovery.log"

Thank you for testing.
I don't know why "Digest Error" has occurred.
 

mangokm40

Senior Member
Jan 13, 2019
102
46
Sorry, I missed previous "recovery.log"

Thank you for testing.
I don't know why "Digest Error" has occurred.
No!!! Please don't apologize to us. We appreciate your work on this. Thank you very much.

To be clear, you missed nothing. My English was poor. I meant, I attached the recovery.log with the error to the message about the error AFTER you asked me to do it. I thought it would make it easier to distinguish from the new recover.log file. I'm sorry I created a confusion about the timing.
You did nothing wrong.

If I get a few hours, I will test a restore. It's just that I need to have everything ready, in case I have to reinstall from scratch. :)
 

psc-m3

Member
Nov 8, 2017
16
2
Well, I did a Backup running "lineage-18.1-20210930-nightly-sunfish" and tried to update to "lineage-18.1-20211007-nightly-sunfish" this didn't worked so I tried to restore my TWRP Backup.
The Restore completes, but the Phone hangs in a bootloop. The lineageOS animation shows up shortly and the it reboots. After some time the (I think) LOS-Recovery shows up and says something like "Can't load Android System. Your data may be corrupt. If you continue to get this message, you may need to perform a factory reset" - which indeed works. At least I get a naked lineageOS without any data.

Unfortunately I can not get any log messages while it hangs in the boot loop. adb logcat does not connect at that stage and "/proc/last_kmsg" or so is not available on my phone. Only restoring "data" results in the same bootloop. In my experience with TWRP nothing like that happened to me.
 

psc-m3

Member
Nov 8, 2017
16
2
When you boot into TWRP, does anyone else notice that the time at the top center is wrong - and when you enable the backupname to include the date/time - it has an invalid date of 1970?
true, but this is not limited to TWRP it seems to me. If you do a "date" via adb shell in the LOS-Recovery it also shows 1970. TWRP seems to have a fix for that:
I:TWFunc::Fixup_Time: Pre-fix date and time: 1970-02-27--02-49-25
I:TWFunc::Fixup_Time: Setting time offset from file /sys/class/rtc/rtc0/since_epoch
I:TWFunc::Fixup_Time: will attempt to use the ats files now.
I:TWFunc::Fixup_Time: Setting time offset from file /persist/time/ats_2, offset 1628873940189
I:TWFunc::Fixup_Time: Date and time corrected: 2021-10-09--19-48-25
But it seems this value is not used.
 
  • Like
Reactions: JohnC

Top Liked Posts

  • There are no posts matching your filters.
  • 6
    Sorry, I missed previous "recovery.log"

    Thank you for testing.
    I don't know why "Digest Error" has occurred.
    No!!! Please don't apologize to us. We appreciate your work on this. Thank you very much.

    To be clear, you missed nothing. My English was poor. I meant, I attached the recovery.log with the error to the message about the error AFTER you asked me to do it. I thought it would make it easier to distinguish from the new recover.log file. I'm sorry I created a confusion about the timing.
    You did nothing wrong.

    If I get a few hours, I will test a restore. It's just that I need to have everything ready, in case I have to reinstall from scratch. :)
    3
    I built and test TWRP for stock ROM A10 and A11 version.
    I didn't test it on custom ROMs.

    I would like to test it on latest version, but my pixel4a dosen't have enough storage changing firmware from stock ROM to custom ROM.

    Can anyone test TWRP test6 build?

    https://drive.google.com/file/d/1mB73pX_0UQQA4PNPvqBBWqSZ6TixZfho/view?usp=sharing
    3
    Thanks for the info. That is what I thought, but when nikamura said in a recent post "I built and test TWRP for stock ROM A10 and A11 version." it seemed to suggest that he might have "recently" rebuilt the A10 version (because his post was from the other day).

    But when I checked, the A10 file in the OP didn't look like it was updated, so that made me think maybe the latest build he did recently post might work on A10 (if TWRP was not OS dependent), hence my question for clarification.

    So, the end result is that I will need to wait for an A10 version to be built using the newer 3.5.2-11 version of TWRP.

    I’m sorry if I caused a misunderstanding.
    I'm building TWRP for A11 version now.

    I'll build TWRP for A10 new version, if I have time.
    1
    I'm on LOS18.1 08-12-2021 & Lineage recovery 08-12-2021. I've no custom kernel. I've no GApps. Magisk was not installed during this test.

    I used "fastboot boot test5.img" and booted successfully to TWRP.

    However, I also got the 255 error.
    I don't have the 999 folders. I attached a screenshot showing the "multiple users" setting is off.

    I've attached the recovery.log, in case it help @nikamura in any way.
    It's possible but unlikely that some parallel apps could go in folders other than 999. There are no parallel apps installed on your device? Parallel apps would also be referred to as clone apps which are apps that clone another. Basically you could clone any app with a cloner and log into two different accounts. This would cause problems. If this is not the case than it would need to be addressed with the dev for a fix.
    1
    I built and test TWRP for stock ROM A10 and A11 version.
    I didn't test it on custom ROMs.

    I would like to test it on latest version, but my pixel4a dosen't have enough storage changing firmware from stock ROM to custom ROM.

    Can anyone test TWRP test6 build?

    https://drive.google.com/file/d/1mB73pX_0UQQA4PNPvqBBWqSZ6TixZfho/view?usp=sharing
    Booted. Installed. Took a backup. Did not try to restore. Seems to work fine though.
    Kernel - Blu_spark r117
    Magisk v23
    LSPosed v153
  • 17
    [RECOVERY] TWRP 3.5.2-11 - TeamWin Recovery Project




    Introduction:

    Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.

    Key Features:

    Touchscreen driven with real buttons and drag-to-scroll
    XML-based GUI that allows full customization of the layout true theming!
    Settings are saved to the sdcard and persist through reboots
    Ability to choose which partitions to back up and which to restore
    Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
    Onscreen keyboard
    Easy selection of internal/external storage

    In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.

    We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.

    Source Code:

    sunfish Device Config: https://github.com/tnakamur/android_device_google_sunfish


    DOWNLOAD:
    Hello, this is a test build for sunfish users.

    It has decryption working, touch, adb and backup and restore seems to work. Super partition volumes can be mounted, and the super partition can be backed up.

    Android11 FW
    test6
    https://drive.google.com/file/d/1mB73pX_0UQQA4PNPvqBBWqSZ6TixZfho/view?usp=sharing
    I built it with September firmware.
    I tested it with September firmware.
    It needs custom kernel with LZMA ramdisk support.

    test5
    https://drive.google.com/file/d/1dabH0e0xkgZOldmnoWD8ZrvPV-IXGUf-/view?usp=sharing
    I built it with August firmware.
    I tested it with August firmware.
    It needs custom kernel with LZMA ramdisk support.

    test3
    https://drive.google.com/file/d/1xhyIrLohcVY3xKHCeBoFAUzCmfBupibk/view?usp=sharing
    I built it with June firmware.
    I tested it with June firmware.
    It needs custom kernel with LZMA ramdisk support.
    I built my custom kernel, and link is below.
    https://drive.google.com/file/d/1e8xFI5SuR8ty5X6R8WXVqrKLDOxprJcF/view?usp=sharing
    Maybe, some other custom kernel works fine.

    test2
    https://drive.google.com/file/d/1t0VOZK2XlyxvC8a_o9XWI7ETy6XMS6bT/view?usp=sharing
    I fix repack ramdisk problem.
    It works 'Install Recovery Ramdisk'.
    It needs custom kernel with LZMA ramdisk support.
    I built my custom kernel, and link is below.
    https://drive.google.com/file/d/1e8xFI5SuR8ty5X6R8WXVqrKLDOxprJcF/view?usp=sharing
    Maybe, some other custom kernel works fine.

    test1
    https://drive.google.com/file/d/1EJhdSTbstkjVqx3YaowC-glWD6kJCN9Q/view?usp=sharing
    It's tested FW version RQ1A.RQ1A.210205.004(Feb FW).
    I don't test any other FW version.
    It doesn't work 'Install Recovery Ramdisk'. It's only for fastboot mode.
    I'm working fixing it and build TWRP with June FW.

    Andriod10 FW https://drive.google.com/file/d/1PZaU9PpYmdcAHlyi0zhNwEGnBsAHDW_E/view?usp=sharing
    It's tested both FW version QD4A.200805.001 and QD4A.200805.003.
    And my custom kernel is OK too.

    What to backup
    * super
    * data
    * boot

    What to restore
    * super
    * data
    * boot

    Repacking TWRP into Boot partition
    To repack TWRP into the boot partition to override stock recovery when rebooting to recovery, perform the following steps
    1. adb push <latest_twrp_boot.img> /sdcard/
    2. reboot to bootloader and fastboot latest boot.img of TWRP
    3. Go to Install
    4. Touch Install Image
    5. Select your TWRP boot.img from /sdcard
    6. Install recovery ramdisk
    7. Swipe to confirm flash
    8. Reboot to recovery and android to verify installation
    9. Reinstall magisk, if you want

    Credit and Thanks
    @bigbiff - his big work for TWRP
    @HolyAngel - I refer his kernel commit
    @wrongway213 - I refer his kernel commit, too

    If you like my work, donations are always welcome.
    Don't forget to hit thanks and rate the thread nicely, it's free:)
    12
    I built TWRP for android11.
    There is link at OP.

    I tested it with android11 FW(RQ1A.210205.004 Feb 2021).
    It doesn't work 'Install Recovery Ramdisk'.
    I'm working fixing it and build with June FW.
    9
    Use TWRP temporary
    ①Test TWRP, 'fastboot boot twrp.img'


    If you use TWRP permanently(install recovery ramdisk), you use custom kernel
    that supports TWRP(LZMA ramdisk).
    I use my custom kernel(TKernel), some other kernels maybe OK.
    My custom kernel download link is OP.

    ①Test my custom kernel, 'fastboot boot boot.img'
    ②If you don't find any problem, flash custom kernel, 'fastboot flash boot boot.img'
    ③adb push <twrp.img> /sdcard/
    ④reboot to bootloader and fastboot latest boot.img of TWRP
    ⑤Go to Install
    ⑥Touch Install Image
    ⑦Select your TWRP boot.img from /sdcard
    ⑧Install recovery ramdisk
    ⑨Swipe to confirm flash
    ⑩Reboot to recovery and android to verify installation
    ⑪Reinstall magisk, if you want
    8
    I built TWRP for android11 test3 build with June firmware.
    There is link at OP.

    I tested it with android11 FW(RQ3A.210605.005 Jun 2021).
    7
    To install TWRP, you need LZMA support kernel.
    My custom kernel is here
    https://drive.google.com/file/d/1nuXc88t0Iokc0ha-AicOtZEUeGCGwQ-R/view?usp=sharing