Related
F2FS for ACE
AOSP only!
S-ON USERS SEE ADDITIONAL INSTRUCTIONS BELOW
Should work on all current CM12 or most any of our LP-based AOSP ROMs around here that use a current CM based kernel/trees
THIS IS EXPERIMENTAL AND HAS POTENTIAL FOR DATA LOSS IF DONE IMPROPERLY. IF YOU ARE NOT COMFORTABLE WITH THAT PLEASE DO NOT ATTEMPT. I CANNOT BE AVAILABLE FOR 24/7 SUPPORT ON THIS.
These mods will provide the ability to format /data and /cache in F2FS format instead of EXT4. Use extreme caution. The will erase your entire /data partition just like a clean flash. I cannot and will not be held responsible for your failure to keep backups handy. F2FS is still considered experimental by Samsung and should be by you the user as well.
What is F2FS?
F2FS wiki
Why F2FS?
F2FS put to the test vs EXT4
How to switch?
PLEASE READ INSTRUCTIONS CAREFULLY. IF NOT FOLLOWED YOU WILL LIKELY BOOTLOOP!!
F2FS capable TWRP Recovery This is the same link the current 2.8.1.1 TWRP built with the added F2FS support commits. When wiping a partition you will have the option to reformat in F2FS now as well.
Fstab conversion zip Fstab is the file used by the kernel to determine how to mount all partitions. CM default is all EXT4. To utilize F2FS we need to modify your fstab. This installer is for use only when you are already running a F2FS kernel and only need to update fstab after switching to/from F2FS/EXT4. This installer will only unpack, edit the fstab according to your current partitions and repack the boot.img. This will not replace the kernel, you must already be using an F2FS kernel or be returning to EXT4 only to make use of this zip.
DOWNLOADS NOW HOSTED @ CODEFI.RE
http://downloads.codefi.re/jrior001/Ace
Procedure for fresh conversion including new Rom flashing:
1. Backup everthing you want to keep with titanium backup or whatever backup you choose.
2. Fastboot flash the new TWRP recovery img if you are not already on it.
3. Run a twrp backup in case things get ugly!
4. Flash new ROM now if desired.
5. Still in recovery...Goto wipe -> hit Advanced wipe. Select data and hit "Repair or change filesystem". Convert to F2FS. Repeat for cache.
6. Flash the fstab conversion zip.
7. Reboot and profit. Any partition app on market can confirm new format changes.
Procedure for nightly ROM updates after F2FS conversion:
1. Flaah nightly ( manually, do not let OTA update flash on its own, you will not be given the chance to flash fstab zip and you WILL BOOTLOOP. Should this happen return to recovery and perform step 2)
2. Flash fstab conversion zip.
3. Reboot and profit.
Procedure if you want to convert back and forth after initial conversion for testing purposes:
1. Change formats of data/cache as desired (only ext4 and f2fs supported).
2. Flash fstab conversion zip to update format types before attempting boot.
S-ON USERS
Code:
If someone has S-ON device, you still can use it like this:
After flashing ROM, reboot to bootloader and fastboot flash boot.IMG provided in ROM.zip as normal. This is required to get any new kernel updates. Return to recovery and make your desired f2fs changes and flash the f2fs script.
After you flashed this f2fs script, the modified boot image will be located at: /tmp/newboot.img
Now we need to download it by using adb in recovery: adb pull /tmp/newboot.img boot.img
After that, you can flash boot.img via fastboot and reboot as usual. (fastboot flash boot boot.img)
Code:
CHANGELOG
V1.0 - Initial release
V2 - switch to by-name fstab entries to go with cm12 nightlies after 1/9/15
V2.1 - typo fix
V3 - corrects fstab name after file name change introduced in 1/14 nightlies and beyond
Source:
Kernel: https://github.com/OpenDesireProject/android_kernel_htc_msm7x30/tree/cm-12.0
Device tree: https://github.com/OpenDesireProject/android_device_htc_ace
Fstab scripts: https://github.com/jrior001/f2fs_fstab_convert_script
Devs, feel free to use or modify any of this for your own work just give thanks to where it came from. It was not all my original work, I must give thanks to Metallice and a few other devs in the grouper forum whose scripts I adapted for my own work.
Contributors
jrior001 @Mustaavalkosta, @paulb-nl and any others that have helped keep msm7x30 alive
Kernel Special Features: f2fs support
Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2015-01-06
Created 2015-01-06
Last Updated 2015-01-06
Important to note, all issues related to f2fs need to stay here and out of the cm12 thread. This is a experimental tweak and mustaa has enough to deal with, without unsupported drama. Please be respectful of this. Thanks and enjoy!
Cant find Convert to F2FS in recovery
hey thanks for your great effort.
I decided to do a test alongside today's [cm-12-20150107-UNOFFICIAL-ace] nightly but, unfortunately for me, I couldn't identify convert to f2fs after under change file system on the recovery [openrecovery-TWRP-ace-2.8.1.1-unofficial].
What will be the issue....
A few of you should test and let's see what happens.
Maybe am not doing something right.
am on TWRP v2.8.1.1 and S-FF with bootloader unlocked
Thanks :good:
xdagee said:
hey thanks for your great effort.
I decided to do a test alongside today's [cm-12-20150107-UNOFFICIAL-ace] nightly but, unfortunately for me, I couldn't identify convert to f2fs after under change file system on the recovery [openrecovery-TWRP-ace-2.8.1.1-unofficial].
What will be the issue....
A few of you should test and let's see what happens.
Maybe am not doing something right.
am on TWRP v2.8.1.1 and S-FF with bootloader unlocked
Thanks :good:
Click to expand...
Click to collapse
You need to go to Advanced Wipe and select data or cache partition and choose Repair or Change File System > Change File System > F2FS. This will format the partition so make sure you don't lose anything important.
Mustaavalkosta said:
You need to go to Advanced Wipe and select data or cache partition and choose Repair or Change File System > Change File System > F2FS. This will format the partition so make sure you don't lose anything important.
Click to expand...
Click to collapse
Thanks got it to work . I haven't done any major testing though but i believe i will do, will be back with my takes.
xdagee said:
Thanks got it to work . I haven't done any major testing though but i believe i will do, will be back with my takes.
Click to expand...
Click to collapse
Very good, interested what your experience is. I ran a bunch of tests when I got this working on my One XL(Evita) and found f2fs to be slightly better for heavy read/write action things like installing apps(especially that initial Google restore of apps on first boot) and more less the same or slightly better in daily use.
First of all- every next restart is rom more responsive. (it has it's own limitations, of course ) I'm not testing very much, but using as usually. Second- Gallery app doesn't show pictures until i enabled root access.. this is new problem, ringtone was unknown too, 0103 release was fine with this. So..don't know where is problem, but i see that this is good step. Thank you!!!
edit: @Mustaavalkosta , @jrior001 : this is not very good that your threads are separated. Because I see new problems that i never seen before, so I think this is problem of F2FS. In my previous installed nightly (it was one of those "smaller", so no 0103 as I wrote before, but maybe 0101?) was calculator OK, media player too, gallery too and ringtones too. Now I have problem with all - direct after restart i see pictures in gallery but after (what?) again i can't see it. Ringtone - i set ringtone and it was ok, but later it changes to "unknown" - so no ringtone. Audio player has similar problem.
...on other side - it is really good. (Musta's ROMS and this too). Thanks for your work!
Updated OP with S-ON flashing instructions courtesy of @kib0rg
..bad evening... after trying to install app- it ends in reset, system no more started..
I've just uploaded a new v2 script to go with tomorrow's nightly. There are significant changes to the fstab that warranted this new version.
can i use this only in clean new installation? I have installed 0111 version.Can i use it with dirty flash of new nightly?
I don't know what i'm doing wrong. After flashing F2FS v2 phone stuck on black screen - no cm bootscreen appears..
Edit:
after flashing v1 phone normally booting. So there is problem with v2 or after (dirty) flashing new rom I use v2 instead of v1?
Phone stacked after flashing nightly.
As much testing hasn't be done on this; which we know the reason. being that if we are able to get a much more daily driver like ROM then more people will try testing f2fs. But for yesterday as I try to update my recovery, i found out that ace_f2fs_fstab_script_cm12_v2.zip has been uploaded. I downloaded flashed alongside 20150110's nightly. After flashing, phone get stacked just after boot screen appears.
@xdagee - what CM12 nightly do you use? I think last two has problem with dialer/phone. Do you use F2FS script v1?
For clarity, v1 should be used on night lies prior to 1/10, v2 should be used for 1/10 and beyond. 1/10 and beyond will also require the latest twrp update as well.
There was a major change to the fstab in mustaa's CM repos file that determines what partitions to mount that required everything be updated to match.
jrior001 said:
For clarity, v1 should be used on night lies prior to 1/10, v2 should be used for 1/10 and beyond. 1/10 and beyond will also require the latest twrp update as well.
There was a major change to the fstab in mustaa's CM repos file that determines what partitions to mount that required everything be updated to match.
Click to expand...
Click to collapse
problem is that v2 isn't working. I have same problem as Xdagee. Of course new twrp.
danvo01 said:
problem is that v2 isn't working. I have same problem as Xdagee. Of course new twrp.
Click to expand...
Click to collapse
Hmm...I tested before I uploaded but I'll check it out tonight.
Sorrys folks, there was a typo in one of the f2fs entries that was killing it, all fixed up now. I've uploaded a v2.1 zip that's corrected.
working fine, thanks
jrior001 said:
Sorrys folks, there was a typo in one of the f2fs entries that was killing it, all fixed up now. I've uploaded a v2.1 zip that's corrected.
Click to expand...
Click to collapse
thats okay, we've got your back
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its 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.
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
CHANGELOG for 2.8.7.0:
-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option – more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
DOWNLOAD:
You can find more information and download links on our NEW website! NOTE that the 2.8.6.0 version is ONLY available on our new site and is not available on our other, older mirrors!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM Dees_Troy directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
XDA:DevDB Information
TWRP Recovery, Tool/Utility for the Sony Xperia Z3 Compact
Contributors
someone755
Version Information
Status: Stable
Stable Release Date: 2015-08-18
Created 2015-08-18
Last Updated 2016-02-17
Device page on the TWRP website:
Mirror 1
There is no Mirror 2.
Due to the way Sony devices function, you will need to have an unlocked bootloader.
Your options, as far as ROMs go, are the following:
Any ROM with this commit
OR just use the new bootloader (with a proper recovery partition)
All credit goes to the TWRP team. I just annoyed the fools until they built the recovery.
Awesome! Very glad to see this.
After flashing through fastboot, its impossible for me to boot into recovery, my phone stays stuck on the Sony screen with the pink/orange led.
Running resurrection remix and m5 kernel, theme has been updated for 2.8.7, previously was on 2.6.0
Can this be install on LB?
rich2007 said:
Can this be install on LB?
Click to expand...
Click to collapse
it should work with andropluskernel, not with stock
omnomnomkimiiee said:
After flashing through fastboot, its impossible for me to boot into recovery, my phone stays stuck on the Sony screen with the pink/orange led.
Running resurrection remix and m5 kernel, theme has been updated for 2.8.7, previously was on 2.6.0
Click to expand...
Click to collapse
Works fine here. Did you check the md5 before installing? Does it work without the theme?
rich2007 said:
Can this be install on LB?
Click to expand...
Click to collapse
You need a custom boot image to boot into it (since our bootloaders don't really support a separate recovery partition, and we rely on a boot.img script to boot into one), which means you'd have to unlock the bootloader.
funiewski said:
it should work with andropluskernel, not with stock
Click to expand...
Click to collapse
On this note, if anyone can provide me with stock boot images, I'll try and keep them up-to-date with the extract_elf_ramdisk utility, so that users on stock may still boot into TWRP if they don't opt for the AndroPlus kernel.
Hello everyone,
Flashed this with "fastboot flash recovery", still getting the cm12.1 recovery.
BL unlocked, USB debugging enabled, CM 12.1 installed.
Anyone have a solution?
Thanks
Edit:
tried the twrp manager, no Z3C here, aswell the dd method, nothing changed.
pityu100 said:
Hello everyone,
Flashed this with "fastboot flash recovery", still getting the cm12.1 recovery.
BL unlocked, USB debugging enabled, CM 12.1 installed.
Anyone have a solution?
Thanks
Edit:
tried the twrp manager, no Z3C here, aswell the dd method, nothing changed.
Click to expand...
Click to collapse
Same here, there is no Z3C in the list on TWRP Manager, and the 'dd' method leaves an unusable recovery (stuck on orange led). I'm happy with official TWRP support, but do you guys even test your stuff before releasing it.....? The steps with TWRP manager app don't even exist (there is no 'advanced' to tap).
Flashed twrp.img as boot: fastboot flash boot twrp.img. -> TWRP starts every time i power on the phone. Flashed CM12.1 from this state, and TWRP got overwrited again with CM12.1 recovery. /sigh
Is the CM kernel counts as "Any custom kernel" ?
pityu100 said:
text
Click to expand...
Click to collapse
Menubalk said:
Same here, there is no Z3C in the list on TWRP Manager, and the 'dd' method leaves an unusable recovery (stuck on orange led). I'm happy with official TWRP support, but do you guys even test your stuff before releasing it.....? The steps with TWRP manager app don't even exist (there is no 'advanced' to tap).
Click to expand...
Click to collapse
Thanks both of you for reporting your issues. Your reports sparked an investigation, and we were able to identify several issues that have thus far been overlooked (for whatever reason).
The "stuff" was tested before it was released, yes, but we're now facing limitations in the form of unmerged patches to the CM device trees. The issues should have been resolved several years ago, but instead they are now wreaking havoc on Sony msm8974 recovery setups. I've gotten some of the elite TWRP and CM people on this, as well as smaller fellow rhine and shinano developers (though Myself5 and oshomun could hardly be classified as small nowadays).
I personally have already uploaded four changes to the CM gerrit (that should have been applied years ago); One of them got denied (though is now being discussed for the near future (possibly as soon as cm-13.0); the result of that discussion is, among others, that the Cyanogen Recovery is now available for download alongside the ROM zip over at https://download.cyanogenmod.org/?device=z3c ), two are still pending any input whatsoever, and the last one was promised a merge, but the device maintainers have gone quiet, at least on the outside.
(If you wish, you can view the patches and their progress at their links: patch1, patch2, patch3, patch4, patch5.)
However, both teams are also having issues with other matters (such as Z3 not building, or adding new features to TWRP), and there is also the fact that school starts around this time of year (which impacts both the younger developers as well as those who already have children).
To conclude, there really isn't a unified guide I can give you to get to TWRP. It works, and you can use it if you have the correct setup. However achieving that setup is not a simple walkthrough away, and it would differ ever so slightly for every person's preferences, not to mention it would be overwritten with each new ROM update.
Such is the state of affairs at this point in time. This may or may not change, but be assured that everything we can do about this, we will do.
EDIT: A quick note that some ROMs may already include fixes for these issues. I don't know which those ROMs could be, so I won't go into listing them, but the possibility exists.
someone755,
thanks for your quick reply and your investigation.
Hope for the best, but time will tell.
Thanks again
Someone, here is a build that actually works, maybe you guys can base on that?: http://forum.xda-developers.com/z3-compact/development/recovery-twrp-2-8-6-0-fota-recovery-t3093537
I'm on Cyanogen 12.1 nightlies with M5 (=Cyanogen-based) kernel btw.
Menubalk said:
Someone, here is a build that actually works, maybe you guys can base on that?: http://forum.xda-developers.com/z3-compact/development/recovery-twrp-2-8-6-0-fota-recovery-t3093537
I'm on Cyanogen 12.1 nightlies with M5 (=Cyanogen-based) kernel btw.
Click to expand...
Click to collapse
The thing is that if you flash a cm-12.1 boot image (completely stock, without kernel or ramdisk modifications that M5 or Kernel12 perform), it won't work. It works with some setups, but not with others, and is, for some reason, very specific -- to get rid of these errors, CyanogenMod would have to (at the very least) accept my changes.
If you feel like you have to try this for yourself, here's a link to the boot image: https://www.androidfilehost.com/?fid=24052804347797955 Getting out of the mess created once you flash this can be a pickle though, so unless you have a boot image on hand with which you know TWRP works, do not flash the file I linked.
I've had somebody say it started working for him after flashing r_02 of Kernel12, though sadly I'm not very sure that's a permanent solution (it is, however, a working temporary one).
Unfortunately the man who was supposed to review the changes is on leave from development, so waiting is the only option available right now (unless we come up with a zip file to flash after each nightly install, but that would only increase the chaos of this already-confusing situation).
someone755 said:
The thing is that if you flash a cm-12.1 boot image (completely stock, without kernel or ramdisk modifications that M5 or Kernel12 perform), it won't work. It works with some setups, but not with others, and is, for some reason, very specific -- to get rid of these errors, CyanogenMod would have to (at the very least) accept my changes.
If you feel like you have to try this for yourself, here's a link to the boot image: https://www.androidfilehost.com/?fid=24052804347797955 Getting out of the mess created once you flash this can be a pickle though, so unless you have a boot image on hand with which you know TWRP works, do not flash the file I linked.
I've had somebody say it started working for him after flashing r_02 of Kernel12, though sadly I'm not very sure that's a permanent solution (it is, however, a working temporary one).
Unfortunately the man who was supposed to review the changes is on leave from development, so waiting is the only option available right now (unless we come up with a zip file to flash after each nightly install, but that would only increase the chaos of this already-confusing situation).
Click to expand...
Click to collapse
Had no issues with my 2.8.7.0 twrp built into my ROMs boot.img been working with no issues so far
Sent from my Z3 Compact using Tapatalk
jenkins-84 said:
Had no issues with my 2.8.7.0 twrp built into my ROMs boot.img been working with no issues so far
Sent from my Z3 Compact using Tapatalk
Click to expand...
Click to collapse
The goal of FOTA recoveries was to let the user boot into a recovery regardless of what recovery is in the boot image. If you flash a CM nightly over your setup, you won't be able to get to TWRP again unless you perform various modifications to the CM boot image.
Packing recovery inside boot is what's causing all these issues in the first place, so doing what you suggest would be a step forward, but two steps back as well.
someone755 said:
The goal of FOTA recoveries was to let the user boot into a recovery regardless of what recovery is in the boot image. If you flash a CM nightly over your setup, you won't be able to get to TWRP again unless you perform various modifications to the CM boot image.
Packing recovery inside boot is what's causing all these issues in the first place, so doing what you suggest would be a step forward, but two steps back as well.
Click to expand...
Click to collapse
Yeah maybe but I don't care to much for CM based ROMs was for people using slimlp based mainly
Sent from my Z3 Compact using Tapatalk
jenkins-84 said:
Yeah maybe but I don't care to much for CM based ROMs was for people using slimlp based mainly
Sent from my Z3 Compact using Tapatalk
Click to expand...
Click to collapse
That's all fine and dandy until you realize most people are sticking with CM (for some unexplainable reason). Other ROM gerrits are much more likely to have already merged the needed changes (and are much more lenient and open when it comes to accepting new changes in general, and all this is the only reason this waiting game is now on).
someone755 said:
That's all fine and dandy until you realize most people are sticking with CM (for some unexplainable reason). Other ROM gerrits are much more likely to have already merged the needed changes (and are much more lenient and open when it comes to accepting new changes in general, and all this is the only reason this waiting game is now on).
Click to expand...
Click to collapse
Yeah but I don't wait on slim or use its device trees etc I build for my own and use commits I want, I don't really care what people use or do. I build ROMs for myself and a friend. I just happened to share a ROM that I don't care if people use or not. If I'm happy with what I build and use then that's all I care about
Sent from my Z3 Compact using Tapatalk
jenkins-84 said:
Yeah but I don't wait on slim or use its device trees etc I build for my own and use commits I want, I don't really care what people use or do. I build ROMs for myself and a friend. I just happened to share a ROM that I don't care if people use or not. If I'm happy with what I build and use then that's all I care about
Sent from my Z3 Compact using Tapatalk
Click to expand...
Click to collapse
You do realize TWRP is meant to work for everyone, not just for 'me and my bros'?
On topic:
Someone, that FOTA TWRP I linked does (or at the very least did, I've been on M5 Kernel for a few weeks now) work with a stock Cyanogenmod boot image. Before M5 kernel I could already reach TWRP. I really think it worth a closer look to see what that guy did because it works/worked for some reason..
My full sequence (the first time anyway):
Unlock Bootloader
Unpack boot.img from Cyanogenmod nightly zip
Flash boot.img in fastboot
Boot to Cyanogenrecovery
Wipe
Flash Cyanogenmod in recovery
Boot Cyanogenmod, Setup Wizard yadda yadda
Shut down and go to fastboot
Flash FOTA TWRP from said link
Test FOTA TWRP, Be happy
----Few days later----
Flash M5 through FOTA TWRP
Team Win Recovery Project
WHAT IS TWRP?
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
Read more about TWRP here: https://twrp.me/about/
WHAT THIS THREAD IS ABOUT?
This thread is about a serious TWRP development for the Xiaomi Redmi Note 6 Pro. By serious I mean a development which isn't using device tree which was just badly kanged from another device or it's a dirty port without any direct compilation from source. That means that issues like a low brightness, which is caused by a maintainer not being able to set the real maximum brightness which is supported by the device, aren't here.
FEATURES:
MTP support
USB OTG storage support
Hardware Qualcomm-based full-disk encryption support ( ext4 & f2fs )
ext4, f2fs, NTFS, fat file system support (read, write, format, backup & restore)
Covers more partitions for nandroid backup and the backup/restore of them really works!
Covers more partitions for image installation, including System, Vendor, Cust, Cache, Userdata, persist, persistbak, boot logo, modem firmware, and even Bluetooth firmware
ADB root
Always synced with signatures from Android platform, so you don't have to worry about the signature mismatch on MIUI incremental OTA installation
Full SELinux support
Support for Asian languages
Included logd/logcat support
Support for mounting USB storage - Mount -> Mount USB Storage in recovery menu.
ISSUE?
If you face any problem then just let me know and i will fix it asap. I'm not a magician to know everything, so if you won't report it then it's probably not gonna be fixed.
CHANGELOG
3.2.3.0, 18.1.2019
- initial release
3.2.3.1, 19.1.2019
- Fixed USB storage, from now on you can mount it
by clicking on Mount -> Mount USB Storage in the recovery menu.
3.2.3.2, 21.1.2019
- Imported selinux service contexts
- Added ability to backup/restore system/vendor images
- increased platform security values to override anti-rollback features to something rather insane
- Added system vold decryption support, since a process of getting keystore to work
on this device was a pure hell for me, but still this is in testing, just let me know if it works for you, but be careful and better backup your data before trying this...
3.3.0.1, 15.4.2019
- Slightly modified screen offset, so you can now see clock in the statusbar.
- Updated decryption blobs to pie, decryption should now work properly, after that there is also slightly improved vold decryption in case that default decryption fails
- Updated kernel to Android 9.0
DOWNLOAD LINK
3.2.3.0, 18.1.2019
Download
3.2.3.1, 19.1.2019
Download
3.2.3.2, 21.1.2019 - warning: this is test build!
Download
3.3.0.1, 15.4.2019
Download
DECRYPTION Builds (ported builds without source)
3.2.3.0, 27.4.2019
Changelog: Initial release
Download
XDA:DevDB Information
TWRP, Tool/Utility for the Xiaomi Redmi Note 6 Pro
Contributors
ATG Droid
Version Information
Status: Stable
Current Stable Version: 3.2.3.1
Stable Release Date: 2019-01-19
Created 2019-01-18
Last Updated 2019-01-19
Reserved
Device tree sources will be up later, don't worry about that. For kernel, I used prebuilt, so there isn't even what to publish.
Reserved
I'm using AOSP Extended, and data decryption does not work.
vdng9338 said:
I'm using AOSP Extended, and data decryption does not work.
Click to expand...
Click to collapse
Ok, will push a test build for it soon...
Edit: Here it is, someone test it please
https://www.androidfilehost.com/?fid=11410963190603903670
Thank You for this Serious development. Really Appreciate.
Ok, just pushed another update..
3.2.3.1 - 19.1.2019
Changelog: Fixed USB storage, from now on you can mount it by clicking on Mount -> Mount USB Storage in the recovery menu.
https://www.androidfilehost.com/?fid=11410963190603903811
Also tell me if the /data decryption works now
Finally, true TWRP builds there
with 3.2.3.1 it still cannot decrypt the data partition (I have entered the numbers that corresponds to the unlock pattern I have defined in Miui)
clemenza011 said:
with 3.2.3.1 it still cannot decrypt the data partition (I have entered the numbers that corresponds to the unlock pattern I have defined in Miui)
Click to expand...
Click to collapse
Here is another test build for it, in this one I switched to a decryption using vold, which should finally work i hope. Anyway, send me a log once you guys try it.
https://www.androidfilehost.com/?fid=11410963190603904132
ATG Droid said:
Here is another test build for it, in this one I switched to a decryption using vold, which should finally work i hope. Anyway, send me a log once you guys try it.
https://www.androidfilehost.com/?fid=11410963190603904132
Click to expand...
Click to collapse
another failed decrypt with the latest version - recovery log attached. Thanks!
edit: I have removed fingerprints, then switched from pattern to pure Pin unlock, and yet again decrypt failed - recovery2.log attached
ATG Droid said:
Team Win Recovery Project
WHAT IS TWRP?
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
Read more about TWRP here: https://twrp.me/about/
WHAT THIS THREAD IS ABOUT?
This thread is about a serious TWRP development for the Xiaomi Redmi Note 6 Pro. By serious I mean a development which isn't using device tree which was just badly kanged from another device or it's a dirty port without any direct compilation from source. That means that issues like a low brightness, which is caused by the maintainer not being able to set real maximum brightness which is supported by the device, aren't here.
FEATURES:
MTP support
USB OTG storage support
Hardware Qualcomm-based full-disk encryption support ( ext4 & f2fs )
ext4, f2fs, NTFS, fat file system support (read, write, format, backup & restore)
Covers more partitions for nandroid backup and the backup/restore of them really works!
Covers more partitions for image installation, including System, Vendor, Cust, Cache, Userdata, persist, persistbak, boot logo, modem firmware, and even Bluetooth firmware
ADB root
Always synced with signatures from Android platform, so you don't have to worry about the signature mismatch on MIUI incremental OTA installation
Full SELinux support
Support for Asian languages
Included logd/logcat support
Support for mounting USB storage - Mount -> Mount USB Storage in recovery menu.
ISSUE?
If you face any problem then just let me know and i will fix it asap. I'm not a magician to know everything, so if you won't report it then it's probably not gonna be fixed.
CHANGELOG
3.2.3.0, 18.1.2019
- initial release
3.2.3.1, 19.1.2019
- Fixed USB storage, from now on you can mount it
by clicking on Mount -> Mount USB Storage in the recovery menu.
DOWNLOAD LINK
3.2.3.0, 18.1.2019
Download
3.2.3.1, 19.1.2019
Download
XDA:DevDB Information
TWRP, Tool/Utility for the Xiaomi Redmi Note 6 Pro
Contributors
ATG Droid
Version Information
Status: Stable
Current Stable Version: 3.2.3.1
Stable Release Date: 2019-01-19
Created 2019-01-18
Last Updated 2019-01-19
Click to expand...
Click to collapse
Thank you for your commitment with serious development and hard work.
Hope to see soon a final and official TWRP based on your version.
Keep debugging. Regards,
I'm also having trouble decrypting the date, no password is correct.
gostavovinicius said:
I'm also having trouble decrypting the date, no password is correct.
Click to expand...
Click to collapse
Decryption is always the most complicated thing to fix on every device. Anyway, I already encrypted my device and I'm trying to fix it, it will just take some time...
Ayyy, new update is out.
Changelog:
- Imported selinux service contexts
- Added ability to backup/restore system/vendor images
- increased platform security values to override anti-rollback features to something rather insane
- Added system vold decryption support, since a process of getting keystore to work
on this device was a pure hell for me, but still this is in testing, just let me know if it works for you, but be careful and better backup your data before trying this...
Download link:
https://www.androidfilehost.com/?fid=11410963190603905629
does this one have non anti rollback protecion?
bornlivedie said:
does this one have non anti rollback protecion?
Click to expand...
Click to collapse
Yep, that's what I mentioned in a changelog. And if you're talking about that "anti rollback" protection which is here promoted by the guy who compiled that fork of a TWRP called pitch black, then don't believe it. He didn't changed the required properties for it in his device tree. So it's actually just a clickbait and his recovery build doesn't really support that.
Actually his build doesn't even include the proper max. brightness which is supported by the LCD driver of this device. That's why I mentioned in a OP that compared to other TWRP builds here this thread is meant to be a serious development and not just a joke.
ATG Droid said:
Yep, that's what I mentioned in a changelog. And if you're talking about that "anti rollback" protection which is here promoted by the guy who compiled that fork of a TWRP called pitch black, then don't believe it. He didn't changed the required properties for it in his device tree. So it's actually just a clickbait and his recovery build doesn't really support that.
Actually his build doesn't even include the proper max. brightness which is supported by the LCD driver of this device. That's why I mentioned in a OP that compared to other TWRP builds here this thread is meant to be a serious development and not just a joke.
Click to expand...
Click to collapse
My bad, I read the entire changelog and yet somehow missed that line... I feel like a dumbass.
Thanks for the clarification, that's actually very important.
ouch, I have removed fingerprints, set pin protection, flashed latest twrp. When I rebooted to recovery, got just the twrp background, frozen, no any options. Worseover, I have turned the phone off, then on, and it asks me for password. I tried with the pin I have set before, yet it says - wrong password. so I cannot get my phone started and I do not know what else to do.
clemenza011 said:
ouch, I have removed fingerprints, set pin protection, flashed latest twrp. When I rebooted to recovery, got just the twrp background, frozen, no any options. Worseover, I have turned the phone off, then on, and it asks me for password. I tried with the pin I have set before, yet it says - wrong password. so I cannot get my phone started and I do not know what else to do.
Click to expand...
Click to collapse
It definetely wasn't frozen. Services would time-out. Just reboot back to the recovery, backup data, backup files in internal memory (sdcard). Format data, restore the previous backup of data and copy back the previous files from /sdcard again. After that flash the 3.2.3.1 version of a recovery and everything will be ok.
[RECOVERY] TWRP 3.5.0_10-0 - TeamWin Recovery Project [/B]
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:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
coral Device Config: https://github.com/bigbiff/android_device_google_coral
A11 Testing:
https://build.twrp.me/test/coral/twrp-3.5.0-0-test1-coral.img
Please test and let me know if anything isn't working.
DOWNLOAD:
Please go to https://twrp.me to download the recovery image.
Old info:
Hello, this is a test build for coral users (will work on crosshatch/blueline later).
So far I have 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.
TWRP seems to be pretty stable now as of test 5. Missing features include adb sideload and repacking recovery which I will be working on in the upcoming months. Android 11 will be supported when stable APIs have been release and we have time to update to that release.
June FW Date https://build.twrp.me/test/coral/twrp-3.4.0-0-test1-coral.img
July FW Date https://build.twrp.me/test/coral/twrp-3.4.0-0-test4-coral.img
July FW Date https://build.twrp.me/test/coral/twrp-3.4.0-0-test5-coral.img
- fix restoring of persist partition
- fix restoring of super partition
July FW Date https://build.twrp.me/test/coral/twrp-3.4.0-0-test6-coral.img
- allow repacking of TWRP from boot.img
- magisk not working currently on repacked image
August FW Date https://build.twrp.me/test/coral/twrp-3.4.0-0-test7-coral.img
August FW Date https://build.twrp.me/test/coral/twrp-3.4.0-0-test8-coral.img
- fix repacking magisk with TWRP
- Credit to @Freak07 https://github.com/freak07/FLORAL - using his kernel as a base for Coral/Flame TWRP
http://twrp.me
What to backup
* super
* data
* persist
* boot
* any other partition desired
What to restore
* super
* data
* boot - depending on ROM support
Please just restore persist if you have a failed partition. I do not recommend restoring backups from phone to phone unless you know what you are doing.
These devices do not have a recovery partition. You will not be able to flash the img file directly to the phone. Make sure you use fastboot boot to temporarily boot TWRP and use adb to push it to the /sdcard folder for repacking.
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. Select your TWRP boot.img from /sdcard
5. Touch Install Image Recovery Ramdisk
6. Swipe to confirm flash
7. Reboot to recovery and android to verify installation
Glad to see this!
Finally TWRPified! Thanks for bringing this to us!
bigbiff said:
[RECOVERY] TWRP 3.4.0-0 - 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:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
coral Device Config: https://github.com/bigbiff/android_device_google_coral
DOWNLOAD:
Hello, this is a test build for coral users (will work on crosshatch/blueline later). I was hoping adventurous people would try this fastbootable image out for testing.
So far I have 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. Will check back later to see feedback. Don't try if you are unable to reset back to stock. Only try if you are curious to kick the tires.
June FW Date https://build.twrp.me/test/coral/twrp-3.4.0-0-test1-coral.img
http://twrp.me
Click to expand...
Click to collapse
When trying to boot the image it gets stuck on the TWRP flash screen. I'm on a rooted custom rom. Sorry to sound stupid if I'm missing something obvious.
Daisymae said:
When trying to boot the image it gets stuck on the TWRP flash screen. I'm on a rooted custom rom. Sorry to sound stupid if I'm missing something obvious.
Click to expand...
Click to collapse
Same here ?
I'm stuck on splash screen as well, but I'm gonna try to push this thread in a more helpful direction with a detailed description and a logcat:
I'm on June radio/bootloader, running AOSiP, rooted with Magisk, build # QQ3A.200605.001
Here's the logcat of stuck @ splash
https://pastebin.com/sAMURQKw
If anything else you need tested or logged please don't be shy to tag me - I'm excited to see TWRP making its way here and I know it's been hard work. Hope the log helps and will gladly take more if it doesn't show the pertinent info you need.:good:
I'll follow in Wrong Ways example.
Build: du_coral-userdebug 10 QQ3A.200605.002.A1 eng.surge.20200605.155815 release-keys
Probs wont do much more than this for now. But figured id upload to help the cause
Few things I thought I might add.
-manually adding libion.so to /system/lib64 allows you to get further but then it requests libandroidicu.so which is an apex/android runtime lib which isn't available since system isn't mounted
-toybox missing pigz always shows up
Surge1223 said:
I'll follow in Wrong Ways example.
Build: du_coral-userdebug 10 QQ3A.200605.002.A1 eng.surge.20200605.155815 release-keys
Probs wont do much more than this for now. But figured id upload to help the cause
Few things I thought I might add.
-manually adding libion.so to /system/lib64 allows you to get further but then it requests libandroidicu.so which is an apex/android runtime lib which isn't available since system isn't mounted
-toybox missing pigz always shows up
Click to expand...
Click to collapse
Thanks for the logs, I am working on getting our relink process working better so I hope to get that done soon to get all the built objects into the right space.
Apex files should be mounted and available before the decryption process happens. init is then configured to use these apex libraries for loading. It works locally but not on your pixels for some reason.
Can you post the results of mount -v?
Here is a new test image as well, I verified it on my own coral and it decrypted with pin: https://build.twrp.me/test/coral/twrp-3.4.0-0-test2-coral.img
Also this image is fastboot only. I need to work on installing into the ramdisk.
bigbiff said:
Thanks for the logs, I am working on getting our relink process working better so I hope to get that done soon to get all the built objects into the right space.
Apex files should be mounted and available before the decryption process happens. init is then configured to use these apex libraries for loading. It works locally but not on your pixels for some reason.
Can you post the results of mount -v?
Here is a new test image as well, I verified it on my own coral and it decrypted with pin: https://build.twrp.me/test/coral/twrp-3.4.0-0-test2-coral.img
Also this image is fastboot only. I need to work on installing into the ramdisk.
Click to expand...
Click to collapse
Sure, no problem. logs attached
Surge1223 said:
Sure, no problem. logs attached
Click to expand...
Click to collapse
Thanks, did you try test2?
bigbiff said:
Thanks, did you try test2?
Click to expand...
Click to collapse
yep
fastboot boot /Users/surge/Downloads/twrp-3.4.0-0-test2-coral.img
---------- Post added at 02:02 AM ---------- Previous post was at 01:58 AM ----------
bigbiff said:
Thanks, did you try test2?
Click to expand...
Click to collapse
BTW, im stuck on splash whenever I try to do this, I thought decryption only took place when attempting to enter pin/pattern?
Surge1223 said:
yep
fastboot boot /Users/surge/Downloads/twrp-3.4.0-0-test2-coral.img
---------- Post added at 02:02 AM ---------- Previous post was at 01:58 AM ----------
BTW, im stuck on splash whenever I try to do this, I thought decryption only took place when attempting to enter pin/pattern?
Click to expand...
Click to collapse
Boggling my mind that it works on my coral with out linking issues.
Can you post the results of getprop please?
Surge1223 said:
yep
fastboot boot /Users/surge/Downloads/twrp-3.4.0-0-test2-coral.img
---------- Post added at 02:02 AM ---------- Previous post was at 01:58 AM ----------
BTW, im stuck on splash whenever I try to do this, I thought decryption only took place when attempting to enter pin/pattern?
Click to expand...
Click to collapse
It might be something funky happening with qsecomd starting up. There is a whole orchestration of steps that might cause an issue unfortunately. Until we get things ironed out you might have to wipe via stock recovery a few times. I assume by splash you mean the white G screen?
bigbiff said:
It might be something funky happening with qsecomd starting up. There is a whole orchestration of steps that might cause an issue unfortunately. Until we get things ironed out you might have to wipe via stock recovery a few times. I assume by splash you mean the white G screen?
Click to expand...
Click to collapse
I meant the twrp splash screen.
https://hastebin.com/ovamadoken.md
Could it have to do with the interface_start in relation to keymaster4?
---------- Post added at 02:23 AM ---------- Previous post was at 02:20 AM ----------
Surge1223 said:
I meant the twrp splash screen.
https://hastebin.com/ovamadoken.md
Could it have to do with the interface_start in relation to keymaster4?
Click to expand...
Click to collapse
Wait did you want getprop while in recovery or booted?
Surge1223 said:
I meant the twrp splash screen.
https://hastebin.com/ovamadoken.md
Could it have to do with the interface_start in relation to keymaster4?
---------- Post added at 02:23 AM ---------- Previous post was at 02:20 AM ----------
Wait did you want getprop while in recovery or booted?
Click to expand...
Click to collapse
Sorry, I would like it executed in recovery. I want to try and find out why it seems as when apex libraries are mounted, they do not seem to be added to the library search path in init.
Since some of the decryption programs don't find libion.so, they cannot start up.
bigbiff said:
Sorry, I would like it executed in recovery. I want to try and find out why it seems as when apex libraries are mounted, they do not seem to be added to the library search path in init.
Since some of the decryption programs don't find libion.so, they cannot start up.
Click to expand...
Click to collapse
heres getprop
https://hastebin.com/eluqagolub.md
heres list of files in /system/lib64
https://hastebin.com/uqoxuheqef.pl
Got some $$ coming your way Monday OP.
Thank you for this. It could not have been easy
@bigbiff,
i tested the test2 img, too and i have the same result as wrongway213 and Surge1223. It hangs on the twrp Splash Screen.
I'm on AOSiP Official (no Gapps) from june (=> latest build) so my factory image is on june, too (i don't know which slot is active atm).
Just a theory: Can it have to do with the fact that on the other slot is still the old AOSiP build with may factory image installed? Mayby this makes a crash on the decryption. I'm not a dev so it's just a assumption.
If you need logs i'm glad to give them to you but i know only the logcat from adb. So for more i would need guides/help.
dhacke said:
@bigbiff,
i tested the test2 img, too and i have the same result as wrongway213 and Surge1223. It hangs on the twrp Splash Screen.
I'm on AOSiP Official (no Gapps) from june (=> latest build) so my factory image is on june, too (i don't know which slot is active atm).
Just a theory: Can it have to do with the fact that on the other slot is still the old AOSiP build with may factory image installed? Mayby this makes a crash on the decryption. I'm not a dev so it's just a assumption.
If you need logs i'm glad to give them to you but i know only the logcat from adb. So for more i would need guides/help.
Click to expand...
Click to collapse
No, it seems to be related to trying to load libion.so from apex images. Can you post a URL to the exact build you are using? I can test it on flame locally.
[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
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
Why is there a custom kernel needed?
Taobaibai said:
Why is there a custom kernel needed?
Click to expand...
Click to collapse
Because stock kernel doesn't support LZMA ramdisk.
It's needed to install TWRP.
https://forum.xda-developers.com/showpost.php?p=83255125&postcount=207
Taobaibai said:
Why is there a custom kernel needed?
Click to expand...
Click to collapse
nikamura said:
Because stock kernel doesn't support LZMA ramdisk.
It's needed to install TWRP.
https://forum.xda-developers.com/showpost.php?p=83255125&postcount=207
Click to expand...
Click to collapse
Better to boot vs install until build is proven. Yep, a bit annoying but keeps options open while allowing fluid OTA updates if that's your preference. In boot scenario custom kernel should not be needed.
This is big news and so awesome!
Nice!! Congrats on getting it built and posted! Thank you for the mention
The kernel gived me a bootloop
Theodor0504 said:
The kernel gived me a bootloop
Click to expand...
Click to collapse
Witch FW version you use?
Has anyone used this to create a back up and then restore it properly without problems?
nikamura said:
Witch FW version you use?[/QUOTE
I don't remember actually
Click to expand...
Click to collapse
https://forum.xda-developers.com/pixel-4a/development/kernel-holydragon-kernel-t4155283
This kernel is good or no?
My apologies if this has been asked/answered before, but could someone ELI5 on why it's so difficult to get custom recoveries running on Pixel devices?
Lada333 said:
My apologies if this has been asked/answered before, but could someone ELI5 on why it's so difficult to get custom recoveries running on Pixel devices?
Click to expand...
Click to collapse
The short answer is - recovery is no longer its own independent partition. Instead it's embedded into boot.img which also contains the kernel for the OS itself.
Recovery used to be its own partition because OS updates looked like this:
- OS downloads new OTA file
- OS boots into recovery
- Recovery installs the OTA
- Reboots back to OS
Now on "A/B" devices OS updates look like this:
- OS boots from "partition A".
- OS downloads new OTA file.
- OS installs OTA on "partition B" which it's not currently booting from.
- OS switches the active partition to B and reboots from that.
No recovery needed anymore. So it's no longer a partition of its own. Which is great for Google but harder for Android do-it-yourselfers.
cmstlist said:
The short answer is - recovery is no longer its own independent partition. Instead it's embedded into boot.img which also contains the kernel for the OS itself.
Recovery used to be its own partition because OS updates looked like this:
- OS downloads new OTA file
- OS boots into recovery
- Recovery installs the OTA
- Reboots back to OS
Now on "A/B" devices OS updates look like this:
- OS boots from "partition A".
- OS downloads new OTA file.
- OS installs OTA on "partition B" which it's not currently booting from.
- OS switches the active partition to B and reboots from that.
No recovery needed anymore. So it's no longer a partition of its own. Which is great for Google but harder for Android do-it-yourselfers.
Click to expand...
Click to collapse
The only A/B phone I've ever worked on was my Dad's Mi A1, but that had TWRP running just fine.
I remember reading a few things about Project Treble back then, is that related to this?
Theodor0504 said:
nikamura said:
Witch FW version you use?[/QUOTE
I don't remember actually
Click to expand...
Click to collapse
It's for android 10 version.
I tested QD4A.200805.001 version.
It may work QD4A.200805.003 version(it used same boot.img), but I didn't test.
Click to expand...
Click to collapse
bursug said:
https://forum.xda-developers.com/pixel-4a/development/kernel-holydragon-kernel-t4155283
This kernel is good or no?
Click to expand...
Click to collapse
I used his kernel as a reference, and I added LZMA ramdisk support.
So, his kernel isn't fit TWRP install.
nikamura said:
Because stock kernel doesn't support LZMA ramdisk.
It's needed to install TWRP.
https://forum.xda-developers.com/showpost.php?p=83255125&postcount=207
Click to expand...
Click to collapse
Did you use LZMA compression because the partition where the ram disk is has very little room like the pixel 3A? The pixel 3A did not have enough room in the partition so TWRP was stripped down of features and compressed with LZMA to get it small enough to fit. I believe, but could be wrong, LZMA was used because it yielded the smallest image.
Does the Pixel 4A have the same space issues as the Pixel 3A?
I'm only asking because on the Pixel 3A TWRP never became functional enough to use much because of lack of partition space to reside even after uniquely compressed with LZMA. If the pixel 4A has more space maybe LZMA compression and a specific kernel that requires lcma might not be necessary?
I've never had an a/b phone before and am thinking of getting this one.
A couple of questions :
What is sunfish
Does anyone regret getting this phone
Is it a pain in the azz to deal with a/b
12paq said:
Did you use LZMA compression because the partition where the ram disk is has very little room like the pixel 3A? The pixel 3A did not have enough room in the partition so TWRP was stripped down of features and compressed with LZMA to get it small enough to fit. I believe, but could be wrong, LZMA was used because it yielded the smallest image.
Does the Pixel 4A have the same space issues as the Pixel 3A?
I'm only asking because on the Pixel 3A TWRP never became functional enough to use much because of lack of partition space to reside even after uniquely compressed with LZMA. If the pixel 4A has more space maybe LZMA compression and a specific kernel that requires lcma might not be necessary?
Click to expand...
Click to collapse
Sorry, I don't know it's needed LZMA compression.
I used pixel4 TWRP made by @bigbiff as a reference, and I used LZMA compression as he did.