I think is related to the A/B partition scheme that merge recovery into boot.img and than you have to have a boot image for Android 11 with twrp in it to use it. Not a real twrp issue but more of a partition problem.
TWRP 3.7.0-12 for Sunfish[Testing]
- Thread starter nikamura
- Start date
A/B partition scheme and merged partition phones on 11 have TWRP, see oneplus 7 pro. It is a custom TWRP though so maybe more work was needed that TWRP devs didn't do (yet)?
The biggest front-facing change in 10 vs 11 re partitions is Enable DSU Loader in dev options. No idea what having this capability changed in the file system but if OP7Pro on 11 can run TWRP than surely the 4a can too.
im on qd4a.200805.003 on resurrection remix, i flashed your custom kernel using FKM, and then it gave me a bootloop, so i then tried to flash the sunfish_twrp201017-test5.img assuming i have the custom kernel installed, and it gave an error "FAILED (remote: 'Not allowed to flash (recovery)')". my bootloader is unlocked.
I also tried using the official factory image qd4a.200805.003 from google, still gave that error
I also tried using the official factory image qd4a.200805.003 from google, still gave that error
Last edited:
it doesn't flash recovery.
try 'fastboot boot twrp.img'.
then install twrp.img to recovery ramdisk.
I'm on qd4a.200805.003 with DU 14.7.
I did "fastboot boot sunfish-qd4a-twrp201017-test5.img" and it booted into twrp.
When I try to backup super, data, and boot it tells me it cannot mount /data.
Isn't there supposed to be a step to decrypt data first?
BTW, I did not install anything with twrp and only have pattern unlock setup, if that matters.
I did "fastboot boot sunfish-qd4a-twrp201017-test5.img" and it booted into twrp.
When I try to backup super, data, and boot it tells me it cannot mount /data.
Isn't there supposed to be a step to decrypt data first?
BTW, I did not install anything with twrp and only have pattern unlock setup, if that matters.
Last edited:
Please upload the recovery.log, if you can.
It appears PIN or password input screen after TWRP splash scree.
Please try again after change pattern unlock to PIN or password.
thank you i managed to get twrp working only on the official factory image. now i think the adb sideload is broken on twrp because on twrp menu, adb recognises device. but when you press adb sideload, adb stops recognising device. also when i flash a custom rom using twrp, for some reason twrp goes away and is replaced by the custom rom's recovery (resurrection remix), i think this replaces your custom kernel too. i flashed the custom kernel and twrp.img and magisk.zip after flashing the rom.zip, but still not working. when i tried installing the zip i got the error "size of image is larger than target device" so maybe thats what caused the problem. i also couldnt flash opengapps, it gave me error 70, which is due to insufficient space, even though i have 110gb free.
Last edited:
Has nothing to do with the amount of space available in the user/data partition. If it truly is a space issue (error could also be a red herring) it will be in what is commonly referred to as the 'system' partition.
I switched from pattern to pin.
Tried again and it looks like the same issue (I never was prompted for my pin).
I put the twrp recovery log on AFH here: https://www.androidfilehost.com/?fid=10763459528675582382
I tested TWRP only on the official factory image.
adb sideload is not supported.
@bigbiff will support adb sideload, then I try to support it, too.
It couldn't decrypt metadata encryption, but I do'nt know why.
You use DU 14.7, I didn't test any custom rom.
I try to test with DU 14.7 when time allows.
Cool, thanks! Now being able to back up my phone was really annoying. I will flash this when I get a chance since I am still on android 10.
Lack of response should be telling. Ya really want to take that chance given partition resizing is a dicey proposition; a borked attempt can yield an unusable device. For what gain?
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
26[RECOVERY] TWRP 3.7.0-12 - 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.
Android12 FW
TWRP3.7.0-12
https://github.com/tnakamur/Action-Recovery-Builder/releases/tag/3485414024
I built it with TWRP3.7.0 source code.
It needs custom kernel with LZMA ramdisk support.
Android11 FW
TWRP3.6.1-11
https://drive.google.com/file/d/1lmz3rvegCcGif-jFck7tfH7tT-RzcFWa/view?usp=sharing
I built it with TWRP3.6.1 source code.
Fix time stamp problem.
It needs custom kernel with LZMA ramdisk support.
test10
https://drive.google.com/file/d/16aTC8w0YUYBS_lqcA3KL0kz5mq7NsxxG/view?usp=sharing
I rebuilt it base Pixel4.
I tested it with October firmware.
It needs custom kernel with LZMA ramdisk support.
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
9To install TWRP, you need LZMA support kernel.
My custom kernel is here
https://drive.google.com/file/d/1nuXc88t0Iokc0ha-AicOtZEUeGCGwQ-R/view?usp=sharing9Use 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
