Related
TWRP Recovery
For Galaxy Fit
Team Win Recovery Project 2.x, or twrp2 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.
BUGS:
If you have found a bug, please consider posting it here.
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
SPECIAL NOTE:
This is the first build of TWRP and may have some unknown bugs. I take no responsibility of your devices. This is "testing" phase (for some days only). Help in testing if you wish to otherwise stay away until a final release. Don't post back here that: "You destroyed my phone", "You are cheating", "You are playing with my device".
One more thing, we are using androidarmv6 sources and if you are asking for help on IRC channel mentioned above then please mention there that: "we are not using CM or OMNI sources, we are using androidarmv6 sources".
CREDITS:
TeamWin: For this awesome open-source recovery.
androidarmv6 team: To make all these possible.
@chraso: Hosting & for providing Compatible flags
Me: Compiling
CHANGELOG for 2.7.0.0:
-Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
-Allow sideloading from /tmp on encrypted devices
-Check for a crypto footer before asking for a password to prevent user confusion
-Additional checks for validity to auto generated backup names
-Text wrap in the console output
-Proper caps lock support in the keyboard
-Mouse support via USB OTG for devices with a broken digitizer
-Improve scanning of storage locations for OpenRecoveryScript
-Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
-Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
-Update SuperSU to 1.93 and improve installation process
-Added selinux contexts restoration to fix permissions
-Load RTC offset on Qualcomm devices to fix the date/time in recovery
-USB Mass Storage fixes Add SELinux support checking
-Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
-Add 4.4 decrypt support
-Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
-Various SELinux fixes and bug fixes.
DOWNLOAD:
http://www.mediafire.com/view/?xum64uit9a43q6s
INSTALLATION / UPDATING:
-From the above download link, you'll get a 'recovery.img' file.
-Put that file at the root of sdcard (means, not in any folder)
-Now, open Terminal Emulator and give this command:
Code:
su
You'll be asked to grant superuser permissions, grant them.
-Now, give this command:
Code:
flash_image recoveryonly /sdcard/recovery.img
And wait for 2-3 seconds until it jumps to a new line. Now, close Terminal Emulator.
-Now, normally reboot to recovery and enjoy new recovery!
About the current build:
STABLE.
Reboot to system bug now fixed.
Well...thanks...One problem that i found..it doesn't reboot to system,just goes back to recovery..I didn't try anything else..Flashing zip works..just went back to cwm
Sent from my GT-S5670 using Tapatalk 2
TpupLpasa said:
One problem that i found..it doesn't reboot to system,just goes back to recovery..I didn't try anything else..Flashing zip works.
Click to expand...
Click to collapse
Confirmed. Reboot System reboots to TWRP Recovery not System.
Flashing zips works.
Back Up and Restore of Nandroid ROM images works.
@Bhargav97
Any progress on reboot to recovery bug?
jemail
TpupLpasa said:
Well...thanks...One problem that i found..it doesn't reboot to system,just goes back to recovery..I didn't try anything else..Flashing zip works..just went back to cwm
Sent from my GT-S5670 using Tapatalk 2
Click to expand...
Click to collapse
jemail said:
Confirmed. Reboot System reboots to TWRP Recovery not System.
Flashing zips works.
Back Up and Restore of Nandroid ROM images works.
@Bhargav97
Any progress on reboot to recovery bug?
jemail
Click to expand...
Click to collapse
1st - install PhilZ Touch Recovery 6.40.1.
2nd - install twrp.
My PC is busy again and I can't say when I'll get time but I'll be releasing update soon.
If you want it badly then just do:
Unpack the recovery.img (of this TWRP)
Now, unpack the recovery.img of PhilZ Touch Recovery.
Now, replace the "KERNEL" file in TWRP's unpack from the PhilZ Touch Recovery's unpack.
Now, repack the TWRP's unpack.
Note: If you don't know how to unpack/repack recovery.img file, just Google and you'll learn it in few minutes. It's very easy.
You can use that until my official release.
Ok, thanks.
update
Bhargav97 said:
My PC is busy again and I can't say when I'll get time but I'll be releasing update soon.
If you want it badly then just do:
Unpack the recovery.img (of this TWRP)
Now, unpack the recovery.img of PhilZ Touch Recovery.
Now, replace the "KERNEL" file in TWRP's unpack from the PhilZ Touch Recovery's unpack.
Now, repack the TWRP's unpack.
Note: If you don't know how to unpack/repack recovery.img file, just Google and you'll learn it in few minutes. It's very easy.
You can use that until my official release.
Click to expand...
Click to collapse
heh, doesn't work. I just use Windows 8.1 with the latest updates. Maybe this is a problem... Maybe not...:crying:
Bhargav97 said:
My PC is busy again and I can't say when I'll get time but I'll be releasing update soon.
If you want it badly then just do:
Unpack the recovery.img (of this TWRP)
Now, unpack the recovery.img of PhilZ Touch Recovery.
Now, replace the "KERNEL" file in TWRP's unpack from the PhilZ Touch Recovery's unpack.
Now, repack the TWRP's unpack.
Note: If you don't know how to unpack/repack recovery.img file, just Google and you'll learn it in few minutes. It's very easy.
You can use that until my official release.
Click to expand...
Click to collapse
I would advise against this. I tried it and it soft bricked my phone.
I will wait for the official release, which I hope will be soon. I really like TWRP.
jemail
TpupLpasa said:
Well...thanks...One problem that i found..it doesn't reboot to system,just goes back to recovery..I didn't try anything else..Flashing zip works..just went back to cwm
Sent from my GT-S5670 using Tapatalk 2
Click to expand...
Click to collapse
jemail said:
Confirmed. Reboot System reboots to TWRP Recovery not System.
Flashing zips works.
Back Up and Restore of Nandroid ROM images works.
@Bhargav97
Any progress on reboot to recovery bug?
jemail
Click to expand...
Click to collapse
iSanechek said:
Ok, thanks.
update
heh, doesn't work. I just use Windows 8.1 with the latest updates. Maybe this is a problem... Maybe not...:crying:
Click to expand...
Click to collapse
@Bhargav97, as you kindly asked me I tried to complete the recovery image.
Guys, as I don't own any Fit device, you'll have to flash this at your own risk. Though I've done this before for my device. If anything will not work - let me know. Good Luck!
DL Link: remooved
belyava said:
@Bhargav97, as you kindly asked me I tried to complete the recovery image.
Guys, as I don't own any Fit device, you'll have to flash this at your own risk. Though I've done this before for my device. If anything will not work - let me know. Good Luck!
DL Link: http://yadi.sk/d/IAr6Z_OvQohqq
Click to expand...
Click to collapse
The recovery image you supplied causes a long boot freeze at initial Samsung Logo followed by reboot and long boot freeze and reboot.... etc.
Boot to recovery using hardware keys produces the same result.
This image completely screws the boot image too, you cannot normal boot after flashing the recovery image. Reflashing the previous working recovery image does not help. I have to restore a recovery image using ODIN to get back to a functional recovery.
No success I am afraid.
jemail
jemail said:
The recovery image you supplied causes a long boot freeze at initial Samsung Logo followed by reboot and long boot freeze and reboot.... etc.
Boot to recovery using hardware keys produces the same result.
No success I am afraid.
jemail
Click to expand...
Click to collapse
sorry, I must have made a mistake. I''ll check tomorrow. Sorry for the inconvenience
jemail said:
The recovery image you supplied causes a long boot freeze at initial Samsung Logo followed by reboot and long boot freeze and reboot.... etc.
Boot to recovery using hardware keys produces the same result.
This image completely screws the boot image too, you cannot normal boot after flashing the recovery image. Reflashing the previous working recovery image does not help. I have to restore a recovery image using ODIN to get back to a functional recovery.
No success I am afraid.
jemail
Click to expand...
Click to collapse
Ok, try this one
belyava said:
Ok, try this one
Click to expand...
Click to collapse
Success!
Install Zip -> works.
Back up -> works.
Wipe -> works.
Restore -> works.
Reboot System -> works.
Reboot Recovery -> works.
Great work.:good:
Will continue to test and report any bugs.
jemail
jemail said:
Success!
Install Zip -> works.
Back up -> works.
Wipe -> works.
Restore -> works.
Reboot System -> works.
Reboot Recovery -> works.
Great work.:good:
Will continue to test and report any bugs.
jemail
Click to expand...
Click to collapse
There are a lot of method nowadays for unpack-repack and most of them fails to make a proper repack, so you'll have booting problems like you had when you tried to do it yourself. I just told @belyava to do unpack-repack because he did this with the recovery (TWRP - had same reboot to system issue) of his device successfully. Thanks @belyava for this help.
Everything expected to work. However, you can always report bugs with a proper recovery logfile.
Updated download link with a new mediafire link. The latest build can be now labelled as STABLE build.
hi anyone have got it if possible in rar zip for this recovery.
ahmetakin said:
hi anyone have got it if possible in rar zip for this recovery.
Click to expand...
Click to collapse
Why do u need a flashable package when u can install it simply via terminal emulator?
@jemail will u kindly check the time taken while backup and restoring rom? Just to know whether this is better than CWM.
swat4samp said:
Why do u need a flashable package when u can install it simply via terminal emulator?
@jemail will u kindly check the time taken while backup and restoring rom? Just to know whether this is better than CWM.
Click to expand...
Click to collapse
I can't speak for your ROM, but for me back up ( 3 1/2 mins max) and restore (3 1/2 mins max).
jemail
Ok yesterdeay install with terminal emulator thanks.
Don't forget to thank me and Radii it means a lot to us!
Click to expand...
Click to collapse
Upon discovering the reason people being given an error trying to flash OTAs in my TWRP recovery image I decided I would come up with a work around while I work out a way to fix it.
The following solution is group work between me and Radii.
If you came here just for OTA links then click HERE
Click below spoiler if you haven't installed TWRP on your device and you want to OTA update and then install TWRP.
First you need to download the version you would like, in theory you could backdate although this hasn't been tested and it may misbehave. For example the latest version as of 16/10/2015, build number cm-12.1-YOG4PAS38J.
On the spread sheet you will need two files, the fastboot and the signed. In the fastboot ZIP there is a file called recovery.img. Copy this to your android SDK platform tools folder. Now with the signed ZIP you either copy that to the same folder (platform-tools). Put your phone into fastboot mode and type.
Code:
fastboot -i 0x2b4c boot recovery.img
Or the name of the recovery if you renamed it.
Your phone will boot into Cyanogen OS Recovery. From there click Apply Update (Top option) and click ADB Sideload. Then type,
Code:
adb sideload cm-12.1-YOG4PAS38J-ham-signed.zip
Or whatever you renamed it to.
Reboot and you're done! Now you'll need to install TWRP to flash things like SuperSU and Xposed.
To install TWRP you need to download the latest TWRP image from HERE move that to platform-tools and type (with your phone in fastboot mode/bootloader mode of course)
Code:
fastboot -i 0x2b4c flash recovery "recovery.img"
Changing the name in the quotations to the name of the recovery and removing the quotes.
Click below spoiler if you have installed TWRP on your device and you want to OTA update and restore/preserve TWRP
Do the same as above, I have discovered it's impossible to preserve because Cyanogen will auto-write it's own recovery to the recovery parition.
Nerdy stuff
If you're wondering why you can't OTA without going through all this then it's because Cyanogen OS will do checks to see if the System has been r/w mounted. If so then it will stop all OTAs from installing. Simple when you think about it.
FAQ
Q: Why isn't TWRP still installed after installing the OTA? A: Because Cyanogen OS will write over the recovery partition with Cyanogen Recovery
Q: Will I lose all my data? A: Don't wipe and no, you can dirty flash to preserve data.
Thanks for your work, really appreciated.
However, it sucks a bit that we have tons of work just for the OTA updates if we want root, i guess we should annoy Cyanogen to add a Superuser option to CyanogenOS...
othe01 said:
Thanks for your work, really appreciated.
However, it sucks a bit that we have tons of work just for the OTA updates if we want root, i guess we should annoy Cyanogen to add a Superuser option to CyanogenOS...
Click to expand...
Click to collapse
It's designed to be shipped with devices like Samsung or LG's ROMs they'll never add that option.
Sent from my Z1 using Tapatalk
Breadcrust said:
It's designed to be shipped with devices like Samsung or LG's ROMs they'll never add that option.
Sent from my Z1 using Tapatalk
Click to expand...
Click to collapse
Why not? root is a normal option in CyanogenMod, why wouldn´t the "commercial" edition not support it? I see no reason they can´t add it to PrivacyGuard.
Here one of the forum admins said hes telling the team to add it -> http://community.cyngn.com/t/reques...-thethering-and-inbuilt-superuser-access/97/2
Breadcrust,
did you try this method used for oneplus one phones with CyanogenOS?
https://forums.oneplus.net/threads/flashable-zip-cm12-enable-integrated-superuser.297089/
https://github.com/julian-klode/bacon-superuser/
From what i´ve read OTA updates are working with it and all we need to do is update the recovery after installing a new ota, the script on github creates the patched boot files automatically, we just have to change the config to use the ZUK files.
All theory tho...as i don´t have my phone yet.
othe01 said:
Breadcrust,
did you try this method used for oneplus one phones with CyanogenOS?
https://forums.oneplus.net/threads/flashable-zip-cm12-enable-integrated-superuser.297089/
https://github.com/julian-klode/bacon-superuser/
From what i´ve read OTA updates are working with it and all we need to do is update the recovery after installing a new ota, the script on github creates the patched boot files automatically, we just have to change the config to use the ZUK files.
All theory tho...as i don´t have my phone yet.
Click to expand...
Click to collapse
I'll look into it at sunrise it currently 3:23AM here so can't do it now
P.s thanks for waking me :3
Sent from my Z1 using Tapatalk
@othe01
No COS device allows you to flash incremental OTA if your /system partition is modified. Your quoted package puts compatible su binary in /system & flashes boot-debuggable kernel so that root can be achieved from both app & ADB. It has nothing to do with OTA. Your only choice is to get the signed zip & flash it manually.
@Breadcrust
It would be nice to put incremental OTA zip links too. My posts regarding OTA links also contain them.
:highfive:
Titokhan said:
@othe01
No COS device allows you to flash incremental OTA if your /system partition is modified. Your quoted package puts compatible su binary in /system & flashes boot-debuggable kernel so that root can be achieved from both app & ADB. It has nothing to do with OTA. Your only choice is to get the signed zip & flash it manually.
@Breadcrust
It would be nice to put incremental OTA zip links too. My posts regarding OTA links also contain them.
:highfive:
Click to expand...
Click to collapse
sounded different here: [FLASHABLE ZIP] [CM12] Enable integrated superuser
But is prolly just a misunderstanding from my side.
How exactly does CyanogenOS check if System is modified and can´t we patch the check with an xposed module?
@othe01
He must used the signed zip to update. Regarding OTA faliure, I've discussed the issue here: http://forums.yuplaygod.com/index.php?threads/15124/
You need to registered in the forum to read, so I've uploaded a PDF of the same: https://drive.google.com/file/d/0B9zZIJPXbMsubkFBYmZ4eGtMQjQ/view?usp=sharing
I personally own OnePlus One & YU Yureka so already have a good experience with these things.
The whole procedure is clearly explained - no 'Xposed' module can bypass it. You can, in theory, deploy a file based OTA (I've already requested it through YU developers) instead of block based OTA or patch the update-binary to return always true (unmodified) value while checking the state of partitions.
:good:
@Titokhan I will post them later
Sent from my Z1 using Tapatalk
@Breadcrust can you please help me if you can, I have problem flashing any ota (increments or full), it return error " this package is for device:Z1 this device is k9", all ota was installed directly till unlocked bootloader and root .
aaswar said:
@Breadcrust can you please help me if you can, I have problem flashing any ota (increments or full), it return error " this package is for device:Z1 this device is k9", all ota was installed directly till unlocked bootloader and root .
Click to expand...
Click to collapse
Issue is noted method is in post
Sent from my Z1 using Tapatalk
@Breadcrust
cm-12.1-20150805-EXPERIMENTAL-YOG4PAP1CG-ham: http://forum.xda-developers.com/showpost.php?p=63390843&postcount=223
@Breadcrust
for clarification:
-isn't "cm-12.1-YOG4PAS38J-ham-signed-fastboot.zip" is the same as "cm-12.1-YOG4PAS38J-ham-signed.zip", but with the recovery image include, can sideload this file using the same process you mentioned?
-if the phone is rooted, boot with the COS recovery and sideload the "cm-12.1-YOG4PAS38J-ham-signed.zip" will not work as the system partition is already been modified by the root process, am I right?
aaswar said:
@Breadcrust
for clarification:
-isn't "cm-12.1-YOG4PAS38J-ham-signed-fastboot.zip" is the same as "cm-12.1-YOG4PAS38J-ham-signed.zip", but with the recovery image include, can sideload this file using the same process you mentioned?
-if the phone is rooted, boot with the COS recovery and sideload the "cm-12.1-YOG4PAS38J-ham-signed.zip" will not work as the system partition is already been modified by the root process, am I right?
Click to expand...
Click to collapse
re: above
if using cos recovery and sideload via abd or from file the full signed version , and your have root, it will work, root will be lost though.
fastboot zip has recovery signed doesn't. you need to flash recovery extracted from the fastboot zip and then flash the signed full zip using cos either using abd or sideload file onto system
I flash the rom, but when I insert CDMA SIM into slot one, there is no signal
and there is no option to choose band from the menu.
would you please instruct on how to get CMDA works?
@taitai
As you can see here, it is not an CDMA device.
As regards technical faults as well we're unable to help in most cases as ROMs are from Cyanogen and unedited.
Sent from my Z1 using Tapatalk
I have a chinese version of Z1 and it has CDMA capability
None of them do. They're the exactly the same under the hood.
Sent from my Z1 using Tapatalk
History...
I originally wrote this guide to upgrade from 10.0.4.0 to 10.0.7.0.
I have also used this same guide to install every OTA from 10.0.7.0 to 11.0.11.0.
This guide assumes you have both Magisk and TWRP, that Magisk cannot "uninstall" (because of TWRP installation) and that you want to keep both Magisk and TWRP after installation. Parts of this guide may still be useful if you aren't in this exact situation.
If you only have Magisk, you should be able to follow these much simpler instructions: https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
Things to have on hand:
- vanilla_boot.img (for the version you currently have)
- patched_boot.img (your current boot image with Magisk)
- TWRP img and zip (see version info below)
I think that TWRP also causes the vendor partition to be modified. It may also touch system but I have a modified bootanimation.zip which modifies system, so I can't be sure. In any case, I also have a backup of system.img and vendor.img.
Because Magisk is installed after TWRP, Magisk's "backup" of the "stock boot image" is not vanilla. This means that in order to take the OTA, I have to flash the vanilla boot image.
0 - Update your patched_boot.img
If you don't have a patched_boot.img for your current Magisk (eg. my patched_boot.img was old, since I had installed several Magisk updates), you should build a new patched_boot.img so that when you boot it, the system will continue to work.
Push the vanilla image to the phone.
Code:
adb push vanilla_boot.img /sdcard
Then get Magisk to install using the "Select and Patch a File" method, select the file you uploaded. Then pull down the patched image.
Code:
adb pull /sdcard/Download/magisk_patched.img patched_boot.img
1 - Prepare to OTA
For some reason, my carrier does not like the OTA process so I always turn on Airplane mode + Wifi.
Get to fastboot and check the current slot.
Code:
adb reboot bootloader
fastboot getvar current-slot
My current slot was b
Flash the system and vendor partitions (if necessary).
Code:
fastboot flash system_b vanilla_system.img
fastboot flash vendor_b vanilla_vendor.img
Flash vanilla and boot the patched image (so that Magisk is active and the OTA can be applied).
Code:
fastboot flash boot_b vanilla_boot.img
fastboot boot patched_boot.img
2 - Do the OTA
Install OTA (DO NOT REBOOT)
If the OTA fails
If the OTA fails, you can find out which partitions it doesn't like from the logcat. If you have a fastboot image, you can reflash the affected partitions. As previously mentioned, I've had to flash all of boot, vendor and system for each OTA.
Code:
adb logcat | grep update_engine
...
07-01 06:52:38.470 E/update_engine(935): [0701/065238.470683:ERROR:delta_performer.cc(990)] The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
07-01 06:52:38.470 E/update_engine(935): [0701/065238.470931:ERROR:delta_performer.cc(995)] Expected: sha256|hex = A4AD686D7BF628486668446221D0089BF5915DBC1158C83D30A06222FE7D2ACB
07-01 06:52:38.471 E/update_engine(935): [0701/065238.471002:ERROR:delta_performer.cc(998)] Calculated: sha256|hex = 4CADBE88EC1C019913A0B416EB9031840D4BA6B2287A3FC814A2B8B7F9871F7D
07-01 06:52:38.473 E/update_engine(935): [0701/065238.471072:ERROR:delta_performer.cc(1009)] Operation source (offset:size) in blocks: 0:5221,5461:405,5869:1,5873:343,6221:589
07-01 06:52:38.473 E/update_engine(935): [0701/065238.473233:ERROR:delta_performer.cc(1191)] ValidateSourceHash(source_hash, operation, source_fd_, error) failed.
07-01 06:52:38.473 E/update_engine(935): [0701/065238.473340:ERROR:delta_performer.cc(298)] Failed to perform BROTLI_BSDIFF operation 187, which is the operation 0 in partition "boot"
07-01 06:52:38.473 E/update_engine(935): [0701/065238.473411:ERROR:download_action.cc(337)] Error ErrorCode::kDownloadStateInitializationError (20) in DeltaPerformer's Write method when processing the received payload -- Terminating processing
07-01 06:52:38.739 E/SystemUpdate(15410): [Execution,NonStreamingAbApplyAction] Installation failed with error code: 20.
3 - Backup the vanilla boot image
Note that you need to pull from the other slot (in my case, a).
Code:
adb shell
su
dd if=/dev/block/by-name/boot_a of=/sdcard/vanilla_boot.img bs=1024k
Backup system.img and vendor.img too (if required).
Code:
dd if=/dev/block/by-name/system_a of=/sdcard/vanilla_system.img bs=1024k
dd if=/dev/block/by-name/vendor_a of=/sdcard/vanilla_vendor.img bs=1024k
4 - Magisk patch the other slot
Use Magisk to "Install to Inactive Slot (After OTA)" (DO NOT REBOOT)
5 - Backup the patched boot image
Note that you need to pull from the other slot (in my case, a).
Code:
dd if=/dev/block/by-name/boot_a of=/sdcard/patched_boot.img bs=1024k
exit
exit
# back on your computer
adb pull /sdcard/vanilla_boot.img
adb pull /sdcard/patched_boot.img
Pull down system and vendor images too (if required).
Code:
adb pull /sdcard/vanilla_system.img
adb pull /sdcard/vanilla_vendor.img
Now you can let Magisk reboot. This is the moment of truth...
At this point you should have an upgraded, Magisk-enabled system and backups of the vanilla and patched boot images. Congratulations on completing the OTA!
If the system fails to boot
There's a few things to try before giving up if the system fails to boot...
1) Boot without Magisk (fastboot boot vanilla_boot.img). Probably indicates that a Magisk module you have is no longer compatible.
2) Boot TWRP (fastboot boot twrp.img) and poke at things. As an example, I used the /sdcard/mm program (part of Magisk Manager for recovery) to disable EdXposed when the OTA to Android 10 failed to boot.
6 - Restore TWRP
It is possible to boot TWRP from fastboot so you don't strictly need to install TWRP. I like to have it available anyway.
Old version info...
I had been using the official TWRP 3.2.3, which worked great up until 10.0.9.0. With 10.0.9.0, I couldn't get to TWRP, I just got the system destroyed screen. I could fastboot boot it, but it couldn't mount /data (a problem it has always had).
I figured out that TWRP 3.3.1-dees_troy (from the official TWRP site) works with 10.0.9.0 and up. What's more, it works (can decrypt /data) if you fastboot boot it, not just after install. So you could in theory simply not install TWRP and fastboot boot if in the event that you actually need it.
I know that people have their own favourite versions, with the offain version being popular (didn't work for me). There's OrangeFox too (also didn't work for me).
In summary, I recommend Official TWRP 3.3.1-dees_troy but if you have a favourite alternative, feel free to use it instead.
TWRP thread: https://forum.xda-developers.com/mi-a2-lite/development/official-twrp-daisy-t3855396
Download link: https://dl.twrp.me/daisy/
Restoring TWRP is the same as installing it the first time. This is the process that I use.
Flash vanilla boot, then install TWRP to it.
Code:
adb reboot bootloader
fastboot boot twrp-3.3.1-dees_troy-daisy.img
Install TWRP
Code:
adb push twrp-installer-3.3.1-dees_troy-daisy.zip /sdcard
Use TWRP to install twrp-installer-3.3.1-dees_troy-daisy.zip
I install my modified bootanimation.zip at this time.
Mount System from TWRP (it is normally already mounted for me).
From a shell:
Code:
adb shell
cd /sdcard
cp bootanimation.zip /system/system/media/bootanimation.zip
Umount System
You must re-install Magisk after installing TWRP.
Code:
adb reboot bootloader
fastboot boot patched_boot.img
Use Magisk to "Direct Install (Recommended)"
Reboot
For some reason, my carrier does not like the OTA process so at this point I normally power off the phone rather than just rebooting. When the phone boots, I can turn off airplane mode and check that a mobile data connection can be made.
7 - Confirm that everything works
Make sure the system comes up and Magisk Manager says that Magisk is installed.
Make sure you can get to TWRP. Boot while holding VOL+ or
Code:
adb reboot recovery
Make sure TWRP can see your files.
Congratulations! You have installed an OTA while keeping Magisk and TWRP!
8 - Backup boot.img with TWRP + Magisk (optional)
If you want a copy of the boot.img with both Magisk and TWRP. This pulls from the now-current slot (in my case, a). I'm not totally sure of the value of this, since I can't get fastboot to boot this image. It may come in handy if you upgrade TWRP and that breaks (since you can flash this back rather than having to install the old TWRP again).
Code:
adb shell
su
cd /sdcard
dd if=/dev/block/by-name/boot_a of=twrp_boot.img bs=1024k
exit
exit
# back on the computer
adb pull /sdcard/twrp_boot.img
Thanks. Could you upload or indicate where we can get the necessary files?
Will i loose all user data and internal storage wiped if i do this?
Thanks for sharing, looks complicated, also i think you should use a fixed twrp, since the official dont have acces to sdcard.
rossarnie said:
Thanks. Could you upload or indicate where we can get the necessary files?
Click to expand...
Click to collapse
If you have Magisk, you should already have the vanilla and patched boot.img files.
Of you don't already have Magisk, just follow the install procedure here. https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
If you're running 10.0.4.0 without magisk and need to extract your vanilla boot.img. Use fastboot to boot into twrp and then you can do the DD command to extract boot. Use adb pull to save it to PC.
I used official TWRP from here.
https://forum.xda-developers.com/mi-a2-lite/development/official-twrp-daisy-t3855396
Apparently there's a different twrp that can access the external SD card. I don't have an external SD card so I don't need it.
dr.bahaeddin said:
Will i loose all user data and internal storage wiped if i do this?
Click to expand...
Click to collapse
I didn't lose any data.
I've never had a problem with Magisk. TWRP does tend to bootloop after install, which is why I install magisk again.
You should be able to flash the patched or vanilla boot if twrp is boot looping to fix it too. Just won't have twrp anymore.
a1291762 said:
I didn't lose any data.
Click to expand...
Click to collapse
Mind you. I have a backup of my apps and data that's off of my phone so even if I do need to factory reset I can get it back. That's a longer and more complicated guide.
Txatxiquesi said:
looks complicated.
Click to expand...
Click to collapse
Before I had twrp the standard Magisk ota process was enough. But that loses twrp and with twrp in my magsik backup, the uninstall didn't work. So extra steps are needed. Plus some extra steps to make backups of important files for the next OTA
a1291762 said:
If you have Magisk, you should already have the vanilla and patched boot.img files.
Click to expand...
Click to collapse
Hmm... This may not be the case. I'm careful to make backups but it's easy to skip this.
If you don't have a patched boot image you can backup your current boot partition from a root shell. You need to find out if you are booting a or b slot. Then
dd if=/dev/block/by-name/boot_a of=/sdcard/patched_boot.img bs=1024k
Magisk puts old stock backups into /data. I had 4 files in there which makes it hard to know what each file is.
That's why I made sure to backup my vanilla boot image immediately.
If you're stuck without a vanilla 10.0.4.0 boot you can't do the OTA. I can upload mine somewhere when I get home tonight if it's not already online.
a1291762 said:
...If you're stuck without a vanilla 10.0.4.0 boot you can't do the OTA. I can upload mine somewhere when I get home tonight if it's not already online.
Click to expand...
Click to collapse
This would be very helpful, please
FunkmasterC said:
This would be very helpful, please
Click to expand...
Click to collapse
Here is the backup I made of the 10.0.4.0 vanilla boot.img. You'll need to decompress this before flashing.
URL REMOVED
What's new on 10.0.7.0 bro? Should me wait for 10.1 update if im on 10.0.4.0 rooted?
10.0.7.0 has the March security patches. I haven't noticed any actual changes.
Thank you, your Linux commands are sick, I never know I can get the vanilla and patched boot.img like that.
Cheer~
is there an update for file version 10.0.8.0??
I only just got the notification this morning. I'll do the upgrade tonight but I expect the same process will work.
I just used the same process to go from 10.0.7.0 to 10.0.8.0. This time I was installing to slot b instead of slot a, but otherwise, things were the same.
A side note... I hadn't got around to installing TWRP 3.3.0 so I did that but it couldn't mount /data. TWRP 3.2.3 can mount /data, so I installed that again.
a1291762 said:
I just used the same process to go from 10.0.7.0 to 10.0.8.0. This time I was installing to slot b instead of slot a, but otherwise, things were the same.
A side note... I hadn't got around to installing TWRP 3.3.0 so I did that but it couldn't mount /data. TWRP 3.2.3 can mount /data, so I installed that again.
Click to expand...
Click to collapse
I have successfully updated to 10.0.8.0 with Magisk 18.1, now on Magisk 19.1, everything is running fine. I'd like to also install TWRP but refrain from doing so because of the problems (bootloops, crashes, etc) the official TWRP 3.2.3 shows with decryption in Pie and mounting external or even internal sdcard. I wonder if the latter is fixed in the inofficial fixed version. I think the benefit of TWRP is not worth the effort of repeating a1291762 wonderful tricky procedure on the monthly OTA update basis.
However the procedure is very smart, a back-to-the-roots approach of former days... great, I like it.
But I don't understand how a patched_boot.img can be created from an empty file (boot_a)?
[dd if=/dev/block/by-name/boot_a of=patched_boot.img bs=1024k] Locating the boot_a in </dev/block/by-name/> reveals a boot_a file with 0 bytes. Moreover, to unzip the zipped stock boot Image in </data/stock_boot*.img> or </sbin/.magisk/mirror/data/> I am looking for a command that just returns the boot file rather than expanding it to the full partition. Weird, can anybody help?
Thanks again to a1291762
grufty47
It appears that it is not possible to add some boot.img as attachment
grufty47 said:
I'd like to also install TWRP but refrain from doing so because of the problems (bootloops, crashes, etc) the official TWRP 3.2.3 shows with decryption in Pie and mounting external or even internal sdcard.
Click to expand...
Click to collapse
I use official TWRP 3.2.3. Only really to fix bootloop problems.
I don't have a SD and no problems mounting data.
Lots of people following the TWRP install guide seem to get bootloop. I solve that by patching boot with Magisk. Some people recommend installing an old about image.
If you have a backup of boot you can at least restore that if you have problems.
grufty47 said:
But I don't understand how a patched_boot.img can be created from an empty file (boot_a)?
Click to expand...
Click to collapse
Welcome to Unix, where nearly everything is a file.
Hard disk? /dev/sda
Partition? /dev/sda1
File? /mnt/sda1/file.txt
In this case, boot_a is a way to access a partition on the phone's flash. Actually a link (shortcut) to /dev/mmcblk0p52. Partition number 53 on flash chip 1. The size can't be seen because it's a device and not a file.
grufty47 said:
I am looking for a command that just returns the boot file rather than expanding it to the full partition.
Click to expand...
Click to collapse
dd is a command to read a device. The partition is 64M big so that's the size of the file. gzip can compress well because the actual image is only 24M big and the rest is empty.
Magisk knows how to do it. A tool called magiskboot but I don't know where it lives or how to run it.
I found this header from magiskboot. It shows how the boot.img is structured.
https://github.com/topjohnwu/Magisk/blob/master/native/jni/magiskboot/bootimg.h
I just did the 10.0.9.0 OTA. I added a section of updating your patched_boot.img (since the Magisk updates I did made my old one useless) and I changed the backup instructions due to changes in Magisk 19. If you know where the stock boot lives before reboot, please let me know.
I'm trying to install the OpenGapps package for LineageOS 16 on my new Oneplus 7 Pro, but have a problem installing it.
First I tried the "open_gapps-arm64-9.0-micro-20190827.zip" package, but it told me its the wrong platform. Is it not arm64?
Second I tried to install the "open_gapps-arm-9.0-micro-20190827.zip", but gives me an error 70, saying I do not have enough space.
Maybe someone have a solution for this?
Thanks
Try MindtheGapps. I've seen this work for some.
http://downloads.codefi.re/jdcteam/javelinanddart/gapps
oryanh said:
Try MindtheGapps. I've seen this work for some.
http://downloads.codefi.re/jdcteam/javelinanddart/gapps
Click to expand...
Click to collapse
Tried it. Still does not work.
I got it semi, but still not working. Seems like the problem is within the way the partitions getting handled. My old Oneplus 5t had a boot, recovery, system partitions. The new one includes the recovery inside the boot it seems instead.
Here's how far I am now:
1) Unlocked the phone
2) Installed TWRP
3) Install Lineage ( This overwrites the TWRP so you have to install it again )
4) Reboot straight from TWRP after flashing the Lineage... back into the Bootloader/Fastboot mode and install the TWRP again.
5) Boot back into TWRP recovery and now I'm able to install OpenGapps ARM64 version.
But after this I cant boot the OS anymore...
cbadk said:
Tried it. Still does not work.
I got it semi, but still not working. Seems like the problem is within the way the partitions getting handled. My old Oneplus 5t had a boot, recovery, system partitions. The new one includes the recovery inside the boot it seems instead.
Here's how far I am now:
1) Unlocked the phone
2) Installed TWRP
3) Install Lineage ( This overwrites the TWRP so you have to install it again )
4) Reboot straight from TWRP after flashing the Lineage... back into the Bootloader/Fastboot mode and install the TWRP again.
5) Boot back into TWRP recovery and now I'm able to install OpenGapps ARM64 version.
But after this I cant boot the OS anymore...
Click to expand...
Click to collapse
Format data in twrp then try boot again should work
liam_davenport said:
Format data in twrp then try boot again should work
Click to expand...
Click to collapse
Still no luck. Tried many things now... but here's what happens:
1) Installing the TWRP
2) Format data partition and everything else
3) Reboot back into TWRP
4) Install Lineage ( At this point I'm able to boot into Lineage just fine )
5) Trying to install Open GApps at this point gives me:
Code:
# Begin Open GApps Install Log
------------------------------------------------------------------
------------------------------------------------------------------
# End Open GApps Install Log
INSTALLATION FAILURE: This Open GApps package cannot be installed on this
device's architecture. Please download the correct version for your device.
# Begin User's gapps-config
# End User's gapps-config
It says I need to install the ARM instead of ARM64...
But if I go back into the bootloader and flash the twrp and boot back into the recovery, I'm able to install Open GApps ARM64 just fine. Seems like a weird "device's architecture" detection problem in the Open Gapps or maybe it could be the TWRP... not sure...
Also after this it will no longer boot.
Kinda weird problem....
cbadk said:
Still no luck. Tried many things now... but here's what happens:
1) Installing the TWRP
2) Format data partition and everything else
3) Reboot back into TWRP
4) Install Lineage ( At this point I'm able to boot into Lineage just fine )
5) Trying to install Open GApps at this point gives me:
Code:
# Begin Open GApps Install Log
------------------------------------------------------------------
------------------------------------------------------------------
# End Open GApps Install Log
INSTALLATION FAILURE: This Open GApps package cannot be installed on this
device's architecture. Please download the correct version for your device.
# Begin User's gapps-config
# End User's gapps-config
It says I need to install the ARM instead of ARM64...
But if I go back into the bootloader and flash the twrp and boot back into the recovery, I'm able to install Open GApps ARM64 just fine. Seems like a weird "device's architecture" detection problem in the Open Gapps or maybe it could be the TWRP... not sure...
Also after this it will no longer boot.
Kinda weird problem....
Click to expand...
Click to collapse
Don't wipe system afaik vendor LOS generates it's own, Also might be in the wrong slot make sure the slot changed when rebooting back to recovery to install gapps, I used MindTheGapps latest version from OP worked great.
liam_davenport said:
Don't wipe system afaik vendor LOS generates it's own, Also might be in the wrong slot make sure the slot changed when rebooting back to recovery to install gapps, I used MindTheGapps latest version from OP worked great.
Click to expand...
Click to collapse
Have not wiped the System and Vendor partition after I installed Lineage... It boots just fine... just not if I install Open GApps....
Tried MindTheGapps latest version, but still no luck.
Okay got it working. The problem was the A/B partition layout they have in this phone... Was not aware of this.
This article describes it pretty well: https://lineageos.org/Changelog-19/
So yeah this is what I did:
1) Boot into Bootloader/Fastboot mode
2) Flash the boot partition with fastboot flash boot twrp-3.3.1-52-guacamole-unified.img
3) Restart into TWRP - Format the data partition and clean the system partition etc.
3) Restart into recovery TWRP once more to get the data partition ready
4) Now you can transfer the lineage-16.0-20190827-nightly-guacamole-signed.zip over to memory.
5) Now flash the zip file and let it complete. This will overwrite the boot partition with TWRP and replace it with Lineage's own boot/recovery image.
6) Now reboot into Lineage's recovery. Now select Apply update > Apply from ADB and send the "MindTheGapps-9.0.0-arm64-20190615_031441.zip" file to the phone with "adb sideload MindTheGapps-9.0.0-arm64-20190615_031441.zip" - You might have to confirm the zip file....
After this is done, the phone should be ready for use.
cbadk said:
Okay got it working. The problem was the A/B partition layout they have in this phone... Was not aware of this.
This article describes it pretty well: https://lineageos.org/Changelog-19/
So yeah this is what I did:
1) Boot into Bootloader/Fastboot mode
2) Flash the boot partition with fastboot flash boot twrp-3.3.1-52-guacamole-unified.img
3) Restart into TWRP - Format the data partition and clean the system partition etc.
3) Restart into recovery TWRP once more to get the data partition ready
4) Now you can transfer the lineage-16.0-20190827-nightly-guacamole-signed.zip over to memory.
5) Now flash the zip file and let it complete. This will overwrite the boot partition with TWRP and replace it with Lineage's own boot/recovery image.
6) Now reboot into Lineage's recovery. Now select Apply update > Apply from ADB and send the "MindTheGapps-9.0.0-arm64-20190615_031441.zip" file to the phone with "adb sideload MindTheGapps-9.0.0-arm64-20190615_031441.zip" - You might have to confirm the zip file....
After this is done, the phone should be ready for use.
Click to expand...
Click to collapse
I am facing the same A/B slot problem with my Moto Z2.
After setp 5), did you let the lineage OS fist then reboot into recovery, or did you go straight to the lineage recovery?
Thank you so much for this. I finally fot it sorted. I did find that sometimes you have to ubplug the USB cable and plug it in again to be recognised, but I got it going. Goodby Google!!!!
I am using Gentoo Linux with adb to do this.
How to root:
You have two options for this, 1 is the recommended way and 2 is the lazy but works way.
Option 1 (RECOMMENDED):
Download the latest factory image from: https://developers.google.com/android/images#cheetah (at the time of writing this, it's TD1A.220804.031
Unlock bootloader (If you don't know how to do this, do not proceed further)
From the downloaded image file, extract the init_boot.img file and copy it to your phone (directory shouldn't matter)
Install the Magisk apk from: https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-release.apk
Launch the app, select install, patch a file, select the init_boot file you placed in your phone
After it's done, it should place a file in your phone's download folder called magisk_patched-<VERSION>_<XYXYXYXYXY>.img
Copy that over to your PC and now boot to bootloader
Run the following commands from Powershell/commandline:
Code:
fastboot flash init_boot magisk_init_patched-25205_EfWOu.img
And then reboot, you'll be rooted
Option 2 (LAZY BUT WORKS):
I'm sharing my magisk patched init_boot from the TD1A.220804.031 build (post 73MB update). Instructions are:
Unlock bootloader (If you don't know how to do this, do not proceed further)
Boot to bootloader
Download the patched init_boot from: https://sourceforge.net/projects/ag.../magisk_init_patched-25205_EfWOu.img/download
Run the following commands from Powershell/commandline:
Code:
fastboot flash init_boot magisk_init_patched-25205_EfWOu.img
And then reboot, you'll be rooted
Install Magisk apk from here: https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-release.apk
To get SafteyNet working:
Open the Magisk app
Open the settings from top right, Enable Zygisk
Reboot
Flash the MODIFIED SafteyNet fix module by @kdrag0n from the attached files on this thread from within Magisk Modules
Clear Play store data and you should be good!
Voila!
FASTBOOT IMAGES:
I'm sharing the stock extracted images of the TD1A.220804.031 build, should be a good reset point from fastboot incase any of you get stuck somehwere:
DO NOT MIRROR THIS PLEASE!!!!
VERIFY THE MD5 OF THE FILE AFTER DOWNLOADING!!!!!!!
Mirror 1 | Mirror 2
MD5: 43613f520697722840ded6a15eb27459
Massive shoutout to @Some_Random_Username for Mirror 1 and @akhilnarang for Mirror 2 since SourceForge was facing issues!
Now documentation on how to do it yourself (which I'd highly recommend since you should never trust any file given, always try to do it yourself!):
How to dump your own device:
1. Download a GSI which is userdebug/eng and equal/newer Security Patch of the current build on your device from any of the unofficial community builds here: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
2. Install the DSU Sideloader app from: https://github.com/VegaBobo/DSU-Sideloader/releases/latest
3. Follow instructions in the DSU sideloader app readme here: https://github.com/VegaBobo/DSU-Sideloader/blob/master/README.md
I'd recommend enabling the userdata toggle and typing 32GB as the size
4. Reboot into the DSU from the notification
5. When the device boots up, type the following in the terminal:
Code:
adb root
adb shell
mkdir -p /sdcard/dump
for file in /dev/block/bootdevice/by-name/*; do
if [ "${file##*/}" != "userdata" ]
then
echo Dumping "${file##*/}"
dd if=$file of=/sdcard/dump/"${file##*/}".img
fi
done
6. Once the dump is done, you'll have files in /sdcard/dump/
7. Copy those over to a PC
8. Voila
A massive thanks to @AndyYan @Some_Random_Username for their help (well hand holding) throughout the entire process <3
Also thanks to @OmkarTheAndroid for the re-brush up of the Android basics I forgot
Reserved
Thanks!
Have you had any luck with SafetyNet yet? People on another thread are saying that even the Modded version by @Displax isn't working on P7P with Canary Magisk
I'd like to remind all that, 1) the DSU method requires some Android/shell knowledge to correctly carry out, and 2) you're discouraged from actually flashing/using those GSIs (TD-based Android 13 GSIs are still in early phase, and P7/P will almost certainly get proper, fully functional device-specific ROMs shortly anyway).
Thanks for the dump! Could you maybe mirror it yourself to be sure? At least until Google's facory images are up Sourceforge is incredibly slow for me (and probably for others too).
so looks like vendor_dlkm has been replaced by vendor_kernel_boot and the init_boot is just the first-stage init. This will be interesting moving forward with AVB and custom images. I will start working on something when source drops. I will likely need to have some testers to see how much this requires to get a custom image up and running.
EDIT: vendor_boot is actually the one that has been separated out a bit between vendor_boot (holding modules) and vendor_kernel_boot, which has some ramdisk stuff like the vendor_boot has on Pixel 6 devices.
Kernel now consists of 6 images. init_boot, vendor_boot, vendor_kernel_boot, vendor_dlkm, dtbo and boot.img
I downloaded the init_boot.img file then got a big problem bricked my pixel 7 oro
mrteii1 said:
I downloaded the init_boot.img file then got a big problem bricked my pixel 7 oro
Click to expand...
Click to collapse
this is a soft brick, just flash the correct partition back using the stock image
Tahnks forbyour reply. How to get the stock image? Now it brickes. Im panicking
I think i'll hold fire on rooting until things are a little clearer. unlocking the bootloader in the usual fashion should be ok tho right?
whatsisnametake2 said:
I think i'll hold fire on rooting until things are a little clearer. unlocking the bootloader in the usual fashion should be ok tho right?
Click to expand...
Click to collapse
Yes, unlocking the bootloader is still the same and will wipe data.
Current SafetyNet Status (with modded universal SafetyNet Fix + Magisk Props):
Play Integrity API Checker:
MEETS_DEVICE_INTEGRITY: fail
MEETS_BASIC_INTEGRITY: pass
MEETS_STRONG_INTEGRITY: fail
YASNAC:
Basic integrity: pass
CTS profile match: fail
Edit: GPay does work on the Pixel Watch, even though it doesn't on the phone (when rooted).
Make sure to add your cards there if you're using the Pixel Watch and can't use GPay on your phone.
zetsumeikuro said:
Yes, unlocking the bootloader is still the same and will wipe data.
Click to expand...
Click to collapse
If you can boot to recovery try a factory reset from there or you will have to power it off and wait until Google releases the image.
mrteii1 said:
Tahnks forbyour reply. How to get the stock image? Now it brickes. Im panicking
Click to expand...
Click to collapse
In the OP, the part with:
"FASTBOOT IMAGES:
I'm sharing the stock extracted images of the TD1A.220804.031 build, should be a good reset point from fastboot incase any of you get stuck somehwere:
DO NOT MIRROR THIS PLEASE!!!!"
Misterxtc said:
If you can boot to recovery try a factory reset from there or you will have to power it off and wait until Google releases the image.
Click to expand...
Click to collapse
? unlocking is just going to do a data wipe/factory reset anyway. not sure why I would need the factory image for that? or to do an additional factory reset from recovery?
Misterxtc said:
If you can boot to recovery try a factory reset from there or you will have to power it off and wait until Google releases the image.
Click to expand...
Click to collapse
Maybe you replied to the wrong user?
Hey everyone, a slight update on the website for the image dump, SourceForge was giving people incomplete files so @Some_Random_Username is generously hosting it on his servers <3
please verify the MD5 of the downloaded zip before trying to modify any parititons using the following commands:
On windows:
Code:
certutil -hashfile cheetah-TD1A.220804.031-compressed.zip MD5
On Linux/MacOS:
Code:
md5sum cheetah-TD1A.220804.031-compressed.zip
The MD5 should be: 43613f520697722840ded6a15eb27459
whatsisnametake2 said:
? unlocking is just going to do a data wipe/factory reset anyway. not sure why I would need the factory image for that? or to do an additional factory reset from recovery?
Click to expand...
Click to collapse
I was thinking the reset would force it to boot off the other slot.