Related
TLDR: It's here and it may eat your data, and you will lose SuperSU root if currently installed. READ the install instructions carefully!
Pixel XL
Pixel
DO NOT RESTORE DATA FROM alpha builds of TWRP using RC1. You will probably lose all data including internal storage. If you need to restore a data backup from an alpha build, reinstall the alpha and restore using the alpha and make a new backup using RC1.
Note: Do not use if you have multiple users (including a guest user)
File Based Encryption (FBE) can be a bit tricky. If a restore doesn't work correctly, it can trigger an automatic wipe of your data. Sometimes TWRP will fail to prompt you to enter your password or otherwise fail to set up decrypt properly. If this happens, reboot TWRP. It seems to be some kind of timing issue and I haven't had time to track it down yet.
Pixel devices have 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore. There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring. You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B. Changing the slot in TWRP also tells the bootloader to boot that slot.
The zip install method installs TWRP to both slots.
Installation:
If you already have TWRP installed: Download the latest zip and install the zip using TWRP.
If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. If you are currently rooted with SuperSU, you will need to reflash the stock boot image before installing TWRP. After installing the stock boot image, follow the instructions for installing TWRP. Once TWRP is installed, grab the very latest SuperSU released on 2015-11-15 or later and install SuperSU.
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
NOTE about 3.2.1-0: This version will decrypt Android 8.1, however the new image is built in Android 8.1 and may not be compatible with SuperSU and/or Magisk until they update their stuff. I have not tested. Good luck.
3.2.1-1 has working decrypt with the February security patch!
3.2.1-2 fixes some zip install errors
3.2.3-1 supports decrypting Android 9.0 Pie even with a pin / pattern / password set
How to install SuperSU SR5 on TWRP RC1: In TWRP tap on Advanced -> File Manager and scroll to and select the fstab.marlin or fstab.sailfish file and then delete it.
You're the man! Props for all the hard work you've put into this.
TY!!!!
Awesome. I might have to wait a bit to install but glad to see the Pixel getting twrp.
Sent from my Pixel XL using Tapatalk
Wow, and so it begins. Thanks!
Thank you!!
Nice!!! Awesome job @Dees_Troy
Sent from my Pixel XL using Tapatalk
I just installed the IMG w/out issue.
I can't find the zip in TWRP file manager to flash though.
Everything looks encrypted.
EDIT: It went through on the 4th try of flashing the IMG, now I can see my /sdcard and install the zip.
But somehow this killed my OS.
Just flashed the flash-all.bat after removing -w so it doesn't wipe.
Now I'll try TWRP install again.
EDIT 2: Okay, after restoring to stock, the TWRP install went fine.
Maybe it didn't like my elementalx kernel or the existing root. The OP did mention something about root conflicts, I guess it may prevent TWRP installs too? But now I have OS *and* TWRP.
And I'm getting "Unspecified Error" when trying to copy my EFS backup from /sdcard/twrp/backup to my local computer. I am able to copy other non-TWRP files though.
.
.
.
Does a full backup on Pixel include System Image and Vendor Image? I don't recall seeing these on other devices.
Or do I just back up boot, system and data like usual?
***Hey ya'll, don't forget to back up EFS at least once and copy it to your computers!
Yea! Worked perfect!!!
Would the flashable SuperSU v2.78 SR3 zip work?
Looked it up and because of conflicting init binaries between TWRP and the current root method, it just wouldn't work.
While we're still on or near the first page of the thread, I'd like to clarify the whole EFS backup thing.
It's completely unnecessary. You don't need to do it. But the option is there (so no one asks where it went!)
Both the modemst1 and modemst2 partitions are merely a caching area for your modem firmware. They do not contain sensitive data like IMEI, or anything important. You can wipe them and they will be regenerated from scratch! Have no fear, your IMEI cannot be destroyed through means of bad flashes!
The issue with these partitions however is that should they ever become corrupt, the modem firmware will panic and fail to load - this is why you see your IMEI missing in such a case. The modem firmware simply refused to load due to encountering corrupt data. By clearing your modemst partitions (writing zeros to them), your modem firmware would happily load and regenerate the partitions, bringing back full call support & a visible IMEI.
Okay, I have TWRP + OS working fine after restoring to stock (getting rid of kernel + root).
Now to just wait for custom ROM's to drop. Thanks guys.
The ability to restore EFS was pretty important on some older phones.
Yep just want to let ya guys know might want return to stock before doing this. Besides that all good. Good job TWRP team! :good:
CZ Eddie said:
Okay, I have TWRP + OS working fine after restoring to stock (getting rid of kernel + root).
Now to just wait for custom ROM's to drop. Thanks guys.
The ability to restore EFS was pretty important on some older phones.
Click to expand...
Click to collapse
Are you rerooting after getting TWRP to work? Have you tried a backup and restore yet?
kirschdog1 said:
Are you rerooting after getting TWRP to work? Have you tried a backup and restore yet?
Click to expand...
Click to collapse
FYI on OP - A SuperSU update will be required to allow TWRP and SuperSU to co-exist.
kirschdog1 said:
Are you rerooting after getting TWRP to work? Have you tried a backup and restore yet?
Click to expand...
Click to collapse
yes
no
I stubbornly flashed v2 root and got boot hang so I put the phone up for the night.
delete
CZ Eddie said:
yes
no
I stubbornly flashed v2 root and got boot hang so I put the phone up for the night.
Click to expand...
Click to collapse
Do we still flash root the same way after we install TWRP? Or is there an su zip to flash?
Hooray! Cheers!
Hello folks!
Apparently the official TWRP recovery 3.0.2 has some sort of problems with android 7.1.1 Nougat, so this unofficial recovery was created to work around those issues in the meantime.
The official hosting of this unofficial recovery is in this thread: http://forum.xda-developers.com/nex...recovery-twrp-2-8-7-0-touch-recovery-t3234976
It is buried almost all the way at the end.
For sake of convenience, I am making it available here for those that wish to get going with it quickly. Note that I am not the developer of this nor am I the maintainer. This is here for easy reference only. You should speak with TWRP Grand Poobah Dees_Troy in the above thread for further details.
twrp-3.0.2-3-angler.zip 14.2 MB
https://mega.nz/#!tdcUAa4a!G-bGMWznEUAkE3Ih3ioaHq2Fx0NdzGnIlhY-nuPg__s
Installation instructions are straightforward:
1. Decompress the zip file so you have the .img file. Do not flash the zip file!
2. Place the recovery image in the same folder as your ADB / fastboot apps.
3. Put your phone in boot loader mode: Power button + volume down button.
4. Pull open a console in this directory and type fastboot devices. Proceed when you a serial number and "fastboot" next to it.
5. Type fastboot flash recovery twrp-3.0.2-3-angler.img. If all goes well you should see a success message of some sort.
6. Reboot and enjoy!
I've been using this for a few ROM installs already and haven't seen any problems.
Best of luck to you!
Guess I'll give this a go and report back later on heh. Will this recovery actually stay after a restart?
Sent from my Nexus 6P using XDA-Developers mobile app
Hmm, seems to be working ok for me on the 7.1.1 DP2 release.
Sent from my Pixel XL using Tapatalk
PearsonDKA said:
Guess I'll give this a go and report back later on heh. Will this recovery actually stay after a restart?
Click to expand...
Click to collapse
Like some others have mentioned, I keep seeing it disappear after restarting the phone once, twice or a few times, so I have to re-flash it almost every time I need it.
Not sure what the hangup is. Size-related?
CaptShaft said:
Like some others have mentioned, I keep seeing it disappear after restarting the phone once, twice or a few times, so I have to re-flash it almost every time I need it.
Not sure what the hangup is. Size-related?
Click to expand...
Click to collapse
You need to flash either Root or a modified boot image for it to stay
jaytv said:
You need to flash either Root or a modified boot image for it to stay
Click to expand...
Click to collapse
Good to know. 2 questions:
1) What modifications to a regular boot image do we need to make to keep it?
2) Are all boot images the same? Can we all use the same modified boot image or does it differ depending on the ROM?
CaptShaft said:
Good to know. 2 questions:
1) What modifications to a regular boot image do we need to make to keep it?
2) Are all boot images the same? Can we all use the same modified boot image or does it differ depending on the ROM?
Click to expand...
Click to collapse
Sounds like time for you to do some reading as to what root and boot images are. Search works great. I suggest the threads on SuperSU (a form of root) and also looking at the many wonderful custom boot images and Roms that are floating around in this forum.
The simple answer is flash Super Su or find a modified boot image for the current release and flash that.
Also, Heisenberg's excellent beginner's thread in Nexus 6p general is a great place to start.
Enjoy!
Just what I was looking for.
I was in TWRP loop forever and couldn't figure it out till this thread. No issues now
I've installed the one from the main thread and it's working for me.
I just wanted to mention what the bugs are:
shadowstep said:
TWRP versions 3.0.2-1 and above work with Android Nougat 7.0's encryption, TWRP 3.0.2-0 and below don't. Also, both versions 3.0.2-1 and 3.0.2-2 are buggy at the moment, but none of those bugs are along the lines of encryption. Read the end of this post for more information.
(Replies snipped)
EFS partition is never needed to be restored under any general circumstance. It is the partition where the phone stores its IMEI information, MAC address, product code, etc. and will never be needed to be modified or changed in any way. Even if you're flashing a stock factory image (be it of 6.0.1 or 7.0, whenever it is out), it would never touch this partition. You should just backup it once, store it away for emergency purposes and never backup or restore it again.
Okay now moving onto important notes and the bugs:
1. TWRP 3.0.2-0: Is stable and has no known bugs. However, it has not been updated to handle Android Nougat 7.0's encryption. Hence, if you're on 7.0 and you're encrypted, it will keep asking for an encryption password even if you don't have one or if you have one and are inputting it correctly, it will refuse to accept it. If you're on 7.0 and you're unencrypted, then this version should be fine.
2. TWRP 3.0.2-1: Is not stable and has a known bug. The bug would affect those who are restoring their EFS partition using this version of TWRP. The EFS partition has two subparts to it, i.e. /efs1 and /efs2. So, when you check EFS at the backup option menu in TWRP, it backups /efs1 to efs1.emmc.win and /efs2 to efs2.emmc.win, which is fine. However, while restoring (and here is when the bug comes in), it restores efs1.emmc.win to /efs1 but restores the same backup of efs1.emmc.win to /efs2 as well (which it shouldn't be doing and instead it should be restoring the corresponding efs2emmc.win to /efs2). This can brick your phone. Hence, the fatal bug.
This version, however, supports Android Nougat 7.0's encryption. Therefore, as long as you don't backup/restore EFS with this version, you should be good using it with either Android Marshmallow 6.0.1 or Android Nougat 7.0, encrypted or unencrypted.
3. TWRP 3.0.2-2: Is not stable and has a known bug (with the EFS bug most likely fixed in this version, but this is unconfirmed since there is no changelog available yet). The bug would affect those who are backing up their data using this version. TWRP creates the backups of your selected partitions as tar files. The bug that is present in this version would give you an error (most likely the one that @stankyou got) as it is unable to write the second tar file after processing approximately 1 GB of data and would cancel the backup. Hence, the bug.
This version, however, also supports Android Nougat 7.0's encryption. Therefore, as long as you don't create backups with this version, you should be good using it with either Android Marshmallow 6.0.1 or Android Nougat 7.0, encrypted or unencrypted.
4. @jcadduono has created unofficial builds (versions 3.0.2-3) for the Nexus 6P (Angler) and Nexus 5X (Bullhead) without the broken patches. They are up-to-date, but have the adb backup patches rebased out until the bugs are solved. These builds are untested, and he recommends sticking with 3.0.2-0 instead for the time being.
Click to expand...
Click to collapse
TL;DR 3.0.2-0 doesn't support Nougat encryption. 3.0.2-1 has bug restoring EFS. 3.0.2-2 has bug creating backups over 1GB.
ADB sideload is not working in TWRP 3.0.2-3 (twrp-3.0.2-3-angler.img - MD5 2fcc19da388ab727aac69b6165ac7888), not sure if this is @jcadduono or not. It's working in previous build IIRC. Is this expected? Thank you.
vibranze said:
ADB sideload is not working in TWRP 3.0.2-3 (twrp-3.0.2-3-angler.img - MD5 2fcc19da388ab727aac69b6165ac7888), not sure if this is @jcadduono or not. It's working in previous build IIRC. Is this expected? Thank you.
Click to expand...
Click to collapse
I had a few failures with it in TWRP, yes.
Until fixed, you'll have to do ADB push instead and then load from TWRP install.
Alternately, you can do fastboot flash commands while in the bootloader.
Grospolina said:
I've installed the one from the main thread and it's working for me.
I just wanted to mention what the bugs are:
TL;DR 3.0.2-0 doesn't support Nougat encryption. 3.0.2-1 has bug restoring EFS. 3.0.2-2 has bug creating backups over 1GB.
Click to expand...
Click to collapse
I noticed that bug yesterday restoring a backup. TWRP appeared to hang whilst restoring, I left it a further five minutes, then hard reset the power button. When the phone loaded up, I found it had restored correctly.
3.0.2-4 twrp ?
Anybody have the capabilities to roll the 3.0.2-3 version in with The Flash's 3.0.2-0_F2FS version lol; and make a version compatible with Nougat encryption as well as F2FS (and without EMS restore problem, nor backup error issue) ?
I know I sure don't, and now that I'm on christmas break I am just sitting around - in fact if anybody could point me to a resource, I have the time and I'm sure I could pick it up quick, I could try and compile it! I've been wanting to give back to this great community since I joined; maybe now that I've done a couple years of engineering school and been searching thru the forums, I can help throw this together.
I'm going to assume that I look up those two builds sources on GitHub, then use Parallels Windows to use a Linux distro (because I'm on a Macbook Pro) to combine the sources and make a build? Honestly, if I could get any advice, I'd love to jump on it.
3.0.3.0 is out. Anyone know the changelog ?
Here's the link: https://dl.twrp.me/angler/twrp-3.0.3-0-angler.img.html
Would be nice to know a changelog
ariefabuzaky said:
3.0.3.0 is out. Anyone know the changelog ?
Click to expand...
Click to collapse
Unfortunately, the answer is here. I did not expect to see a nag screen after making a backup!
bkkzak said:
Here's the link: https://dl.twrp.me/angler/twrp-3.0.3-0-angler.img.html
Would be nice to know a changelog
Click to expand...
Click to collapse
You can always look at their repository
Since 2016-09-01:
- Change version to 3.0.3 to support the app release - 27 hours ago
- Update Ukraine language translation (via jemmini) - 27 hours ago
- Add TWRP app install via TWRP recovery - 29 hours ago
- TWRP Language Update - 7 days ago
- Change handling of /cache due to AB devices not having cache - 7 days ago
- Support backup/restore of FBE policies - 8 days ago
- Support File Based Encryption - 10 days ago
- Add boot slot support - 12 days ago
- Support new AB OTA zips - 12 days ago
- Copy Kernel Logs - 5 months ago
- Improve backup & wipe exclusion handling - 2 weeks ago
- Fix adb shell in 7.0 tree - 6 weeks ago
- Check if mount point is dir during startup - 6 weeks ago
- MD5 verification sanity - 8 weeks ago
- Fix image flashing: attempt 2 - 8 weeks ago
- Fix image flashing - 3 months ago
- Update to android-7.1 - 4 weeks ago
- Fix libcrypto dependency in 6.0 trees - 3 months ago
- Clean up PartitionSettings - 3 months ago
- Fix compressed backups with split archives - 3 months ago
- Fix restore of subpartitions - 4 months ago
Unfortunately for me, I still have issues decrypting an encrypted phone on TWRP 3.0.2-3 and 3.0.3-0. TWRP prompts for a password and won't take my PIN.
Running the latest ResurrectionRemix (CM-based), which enables device encryption. I'm still searching around to see what I need to do about this.
Edit: Update: Huh, weird, got it to mount.
I rebooted back into Android, went in to Security and set a device encryption password with "Change encryption password".
I hadn't set one before. It requests my screen lock PIN then to enter an alphanumeric encryption password.
Attempted to remove it again immediately (it doesn't show any feedback when I tap "Replace encryption password" then enter my screen lock PIN), and rebooted into recovery.
TWRP prompted again for an encryption password but now accepts my device lock PIN and it mounts!
Rebooted again, and now the phone requests a PIN unlock during boot >.<
Went back in to Security and went straight to "Replace encryption password", entered my PIN, and saw no feedback again. Rebooted back into Recovery.
TWRP prompts again but accepts my PIN. Rebooting to Android again, I am prompted again on boot to enter my screen PIN to finish the boot process. Sooo now I guess I have to figure out how to disable the device encryption PIN, or something. Oh well. I'll update if I make progress.
The end goal is to reach a point where TWRP will mount (even if it's manually with an entered PIN), and to not have a phone that requires a PIN unlock during boot. But I guess that's still safer and I can live with it. It's just different from how the ROM originally behaved, is all.
Edit: Update again!
Disabled my PIN/security altogether, rebooted into recovery. TWRP mounts without any prompts. Nice. Reboot int system, it boots fine. Also nice.
Set a new screen lock PIN, do not select to use it on bootup, and set my fingerprints again. Apps work immediately fine after, I did not have to reset them to use that auth method. Woot, nice.
Restart into TWRP, no prompt, good. Restart into System again, no prompt during boot.
So I guess in the end you have to disable and re-enable device screen locking security if you hit this issue in TWRP on a 6P? It could be my ROM as well.
CaptShaft said:
Hello folks!
Apparently the official TWRP recovery 3.0.2 has some sort of problems with android 7.1.1 Nougat, so this unofficial recovery was created to work around those issues in the meantime.
The official hosting of this unofficial recovery is in this thread: http://forum.xda-developers.com/nex...recovery-twrp-2-8-7-0-touch-recovery-t3234976
It is buried almost all the way at the end.
For sake of convenience, I am making it available here for those that wish to get going with it quickly. Note that I am not the developer of this nor am I the maintainer. This is here for easy reference only. You should speak with TWRP Grand Poobah Dees_Troy in the above thread for further details.
twrp-3.0.2-3-angler.zip 14.2 MB
https://mega.nz/#!tdcUAa4a!G-bGMWznEUAkE3Ih3ioaHq2Fx0NdzGnIlhY-nuPg__s
Installation instructions are straightforward:
1. Decompress the zip file so you have the .img file. Do not flash the zip file!
2. Place the recovery image in the same folder as your ADB / fastboot apps.
3. Put your phone in boot loader mode: Power button + volume down button.
4. Pull open a console in this directory and type fastboot devices. Proceed when you a serial number and "fastboot" next to it.
5. Type fastboot flash recovery twrp-3.0.2-3-angler.img. If all goes well you should see a success message of some sort.
6. Reboot and enjoy!
I've been using this for a few ROM installs already and haven't seen any problems.
Best of luck to you!
Click to expand...
Click to collapse
tu 2: is that recovery image the same as under point one? and where is the ADB /fastbootfolder? these not exist
Unofficial TWRP for Moto G5S Plus (Sanders)
Additional Features over Official TWRP:
Supports flashing of both 32bit and 64bit ROMs and Kernels.
OREO Images/ROMs support.
Decryption and Encryption support.
No SuperSU by default.
No TWRP app.
No HTC Dumlock cruft.
Updated pigz compressor (slightly faster and more tolerant of corruption).
NTFS support(Both Read and Write).
Covers more partitions for nandroid backup (OEM, FSG and FSC).
Experimental support for SD cards that are partitioned for partial adopted storage and partial removable storage.
Faster I/O performance.
Fixed Gapps/aroma freeze issues.
IMPORTANT!!! : READ INSTRUCTIONS CAREFULLY BEFORE PROCEEDING TO FLASHING PROCESS..!!
At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) . To avoid this you have to flash either Magisk or flash any of the verity disabler zips available on xda.
Force encryption is enabled by default in stock OS and twrp will successfully decrypt /data at first boot if all goes well
If in case decryption doesn't go fine, twrp will popup a dialog box asking for password and that means decryption went wrong and you would need to wipe data once via twrp wipe options and reboot back to twrp for functioning of /data
Flashing Instructions:
Using Existing TWRP:
Reboot to recovery > Click on Install > Install Image > recovery > select recovery image and flash > reboot to recovery
Other Methods(Fastboot) :
Make sure you have unlocked bootloader
Reboot to bootloader
Enter following command in terminal: fastboot flash recovery twrp-****.img (if you want permanent flash) or fastboot boot twrp-****.img (if you want temporary boot)
Incase your device is encrypted (while coming from stock rom), Follow these steps to decrypt:
Reboot to recovery > cancel the password prompt > mount all partitions > Format Data/Userdata (on f2fs) > Reboot Recovery > Mount all partitions again > Flash Magisk > Reboot
Now you are free to use Stock ROM (Decrypted) or Flash any custom rom you want.
Download Links: https://www.androidfilehost.com/?w=files&flid=216298
TWRP Themes: Check 3rd post
Known Issues: None || Report if you find any.
XDA:DevDB Information
[RECOVERY][UNOFFICIAL][Sanders] TWRP-3.2.1-r20 (64bit Supported!), Tool/Utility for the Moto G5S Plus
Contributors
CheckYourScreen
Source Code: https://github.com/CheckYourScreen/twrp_device_motorola_sanders
Version Information
Status: Stable
Current Stable Version: r20
Stable Release Date: 2018-04-04
Created 2017-10-26
Last Updated 2018-04-04
|| Changelog ||
r20:
Fixed Encryption support on custom roms.
Updated kernel
Updated build fingerprint for latest bootloader support.
Reverted pigz changes.
Switched back to original twrp themes. (TWRP Themes can be found in 3rd post )
Various bug fixes and improvements.
r16:
Fixed compatibility with New Bootloader (C2.07-December patch)
Merged october patches in kernel.
Various twrp upstream patches and fixes.
Fixed remote wipe process (Earlier remote wipe issued from play account wasnt processed due to twrp)
r15:
Added 64bit Support (You can flash both 32bit/64bit roms or kernels with it).
Fixed Encryption Support! (No need to format data to decrypt and mount).
Updated to 3.2.1 upstream changes with full oreo support.
Remove android reboot during password check on multiple wrong inputs.
r9:
Fixed F2FS mount issues(You can flash magisk modules or SuperSu now).
Enabled NTFS Write Support (You can make backups on sdcard/pendrives formatted on NTFS).
Fixed size of various partitions.
Switched to LZMA compression to decrease size.
r7: Initial Public Release
|| Themes ||
Here are some of the twrp themes:
Preview images: https://photos.app.goo.gl/DLrfDseGzfxE8Uq93
Download link: https://androidfilehost.com/?w=files&flid=233551
:good:
Only one that has actually be working for me ever since I got the phone. Thank you for your efforts.
this seems to suffer from the same thing the stock rom/kernel suffers from, the weird f2fs bug that makes certain mounts fail. geneticengineer has shared a kernel that fixes this in stock rom , maybe you could get in touch with him about how he updated f2fs
Thank you for your work, this seems to work well on my device. If you would like to swap the kernel, I posted a newer firmware NPS26.116-45 here:https://forum.xda-developers.com/showpost.php?p=74325160&postcount=33
revengineer said:
Thank you for your work, this seems to work well on my device. If you would like to swap the kernel, I posted a newer firmware NPS26.116-45 here:https://forum.xda-developers.com/showpost.php?p=74325160&postcount=33
Click to expand...
Click to collapse
But its for xt1806 only i think. Not real help. The most user here are outside usa.
Schrotty35 said:
But its for xt1806 only i think. Not real help. The most user here are outside usa.
Click to expand...
Click to collapse
Well my guess is that the kernel in the present twrp is from the -26 firmware posted in the other thread. That firmware was US Retail also. The OP in the other thread states in can be used on other models. But I am not going to tell you that because I do not know. I have not found any other firmware for the sanders model.
Ae3NerdGod said:
this seems to suffer from the same thing the stock rom/kernel suffers from, the weird f2fs bug that makes certain mounts fail. geneticengineer has shared a kernel that fixes this in stock rom , maybe you could get in touch with him about how he updated f2fs
Click to expand...
Click to collapse
Afaik it doesnt affect TWRP, you just need to be on a custom kernel if you are running stock rom.
Twrp has nothing to do with it.
If you face any problem flashing anything then post a screenshot or log.
revengineer said:
Thank you for your work, this seems to work well on my device. If you would like to swap the kernel, I posted a newer firmware NPS26.116-45 here:https://forum.xda-developers.com/showpost.php?p=74325160&postcount=33
Click to expand...
Click to collapse
Schrotty35 said:
But its for xt1806 only i think. Not real help. The most user here are outside usa.
Click to expand...
Click to collapse
Stock kernel is same in both the firmwares.
-45 is just for US variant, i dont recommend you to even flash that firmware on other variants.
CheckYourScreen said:
Afaik it doesnt affect TWRP, you just need to be on a custom kernel if you are running stock rom.
Twrp has nothing to do with it.
If you face any problem flashing anything then post a screenshot or log.
Click to expand...
Click to collapse
but i have a custom stock kernel, and things that fail in TWRP work in flashfire or magiskmanager
its mostly magisk modules im having problems with, ill reproduce an error when i get the chance
Ae3NerdGod said:
but i have a custom stock kernel, and things that fail in TWRP work in flashfire or magiskmanager
its mostly magisk modules im having problems with, ill reproduce an error when i get the chance
Click to expand...
Click to collapse
Flash the magisk module via twrp > take screenshot when flashing completes > go to advance section of twrp and take recovery log > reboot system > send that screenshot and recovery log here.
CheckYourScreen said:
Flash the magisk module via twrp > take screenshot when flashing completes > go to advance section of twrp and take recovery log > reboot system > send that screenshot and recovery log here.
Click to expand...
Click to collapse
will do, it happens with every magisk package i try. they used to fail in stock too till i used geneticengineers kernel from telegram now they work
didnt know you could screenshot in recovery, i assume its the same buttons
Ae3NerdGod said:
will do, it happens with every magisk package i try. they used to fail in stock too till i used geneticengineers kernel from telegram now they work
didnt know you could screenshot in recovery, i assume its the same buttons
Click to expand...
Click to collapse
Yes, same buttons to take a screenshot in TWRP
TWRP backup is frozen at 13% completed. The progress bar is still showing its animation.
I unlocked the bootloader, and then rebooted. Android came up with the language selection screen. I powered off, connected the phone to the PC, and booted into TWRP (not flashed yet):
Code:
fastboot boot twrp-3.1.1-sanders-r7.img
I did not let TWRP format /data.
Then I started a backup, selecting all partitions, so that I could always go back after flashing TWRP and Magisk.
Does anyone know why backup is stuck at 13%? Last log line says "Backing up System..."
I tapped "Cancel" after two hours. That stopped the progress bar animation, but not the backup itself.
BTW: I used TWRP from this thread, the one in another thread freezes at the TWRP boot logo.
Edit: after two hours I killed the backup by powering down (the only way it seemed). On retry it froze at 21%.
Edit 2: Retried, this time backing up everything except system. No problem. I then tried to backup system. Frozen at 1%. What is the problem here?
Edit 3: Finally, a complete backup of system! Only one to go: system_image. But unfortunately that froze at 0%. Every subsequent try freezes at 1666MB (40%). The card has over 30GB free. I tried backup to USB-OTG, but that also froze.
gewe said:
TWRP backup is frozen at 13% completed. The progress bar is still showing its animation.
I unlocked the bootloader, and then rebooted. Android came up with the language selection screen. I powered off, connected the phone to the PC, and booted into TWRP (not flashed yet):
Code:
fastboot boot twrp-3.1.1-sanders-r7.img
I did not let TWRP format /data.
Then I started a backup, selecting all partitions, so that I could always go back after flashing TWRP and Magisk.
Does anyone know why backup is stuck at 13%? Last log line says "Backing up System..."
I tapped "Cancel" after two hours. That stopped the progress bar animation, but not the backup itself.
BTW: I used TWRP from this thread, the one in another thread freezes at the TWRP boot logo.
Edit: after two hours I killed the backup by powering down (the only way it seemed). On retry it froze at 21%.
Edit 2: Retried, this time backing up everything except system. No problem. I then tried to backup system. Frozen at 1%. What is the problem here?
Edit 3: Finally, a complete backup of system! Only one to go: system_image. But unfortunately that froze at 0%. Every subsequent try freezes at 1666MB (40%). The card has over 30GB free. I tried backup to USB-OTG, but that also froze.
Click to expand...
Click to collapse
Might be due to data partition being encrypted, you cant write anything in it without decrypting it first.
Format data and reboot recovery, then make the backup. You can flash magisk after taking the backup.
Btw r9 new release on its way with some really important changes
CheckYourScreen said:
Might be due to data partition being encrypted, you cant write anything in it without decrypting it first.
Format data and reboot recovery, then make the backup. You can flash magisk after taking the backup.
Btw r9 new release on its way with some really important changes
Click to expand...
Click to collapse
I was not trying to write the backup to the data partition, but to external SD card (tried OTG-USB as well without success).
I have flashed TWRP, formatted the data partition, and flashed Magisk. I have not tried to create a new backup yet. First I want to find out why Magisk does not pass the Safetynet check.
Can't wait to see what r9 brings. Thanks for your efforts. :good:
gewe said:
I was not trying to write the backup to the data partition, but to external SD card (tried OTG-USB as well without success).
I have flashed TWRP, formatted the data partition, and flashed Magisk. I have not tried to create a new backup yet. First I want to find out why Magisk does not pass the Safetynet check.
Can't wait to see what r9 brings. Thanks for your efforts. :good:
Click to expand...
Click to collapse
Magisk won't pass safety net with stock boot.img (kernel). Here is a modified kernel.
https://forum.xda-developers.com/showthread.php?p=73930507
After flashing new kernel Magisk passes no problem.
Sent by way of magic
lilcdroid said:
Magisk won't pass safety net with stock boot.img (kernel). Here is a modified kernel.
https://forum.xda-developers.com/showthread.php?p=73930507
After flashing new kernel Magisk passes no problem.
Sent by way of magic
Click to expand...
Click to collapse
When I flash this my WiFi stops working completely. I'm running aosp extended rom. I'm not sure if I can achieve battery life as good as I can on the stock ROM as I can on this one so im not sure what I should do about that..
Brycearuuni said:
When I flash this my WiFi stops working completely. I'm running aosp extended rom. I'm not sure if I can achieve battery life as good as I can on the stock ROM as I can on this one so im not sure what I should do about that..
Click to expand...
Click to collapse
Sorry I wasn't aware you weren't still on stock. That kernel will only work on stock. I would verify with the maintainer of AOSP extended ROM that the kernel is patched to work with Magisk.
Sent by way of magic
Official TWRP For Moto G5 Cedric
Post 1 - Instructions
Post 2 - FAQs
For full details and notes see
Official TWRP for Cedric Site
For TWRP news change logs etc see
TWRP Official Site
Instructions
For non rooted and rooted phones
Requirements
Unlocked bootloader
Fastboot drivers installed on PC
Download Official TWRP Image
Rename the downloaded img file recovery.img
Put phone into fastboot mode (hold vol down + power button)
Connect phone to PC
Open a command prompt where you have fastboot and the TWRP image file located
Type the following in command prompt (recovery.img is the name of your twrp img you downloaded & renamed)
To permanently flash twrp replacing stock recovery
Code:
fastboot flash recovery recovery.img
To only boot to twrp temporarily keeping stock recovery
Code:
fastboot boot recovery.img
Select recovery using the volume keys and power button to select
Now read important notes section For Stock Rom Users at the end of this post and the FAQs in the 2nd post
Note for Windows 10 users who use the powershell and not cmd
The command will become
Code:
./ fastboot flash recovery recovery.img
Or
Code:
./ fastboot boot recovery recovery.img
For rooted phones only
If you are already rooted you can upgrade your TWRP version using the official TWRP app
Download TWRP App
Select Cedric as your device
Download the TWRP image
Select the TWRP to flash
Now read the FAQs in the 2nd post
Important Notes For Stock Rom Users
When you first start TWRP it will ask you to swipe to allow modifications - If you do this your stock rom will no longer boot unless you disable dm-verity.
This can be done either by flashing a disable dm-verity zip or by flashing Magisk zip which will disable it for you
Source Code
TWRP 32bit For Cedric Github Source
TWRP 64bit For Cedric Github Source
XDA:DevDB Information
[Official] TWRP 3.5.2_9-0 Moto G5 Cedric [32/64bit Roms], Tool/Utility for the Moto G5
Contributors
TheFixItMan, JarlPenguin
Source Code: https://github.com/TeamWin/android_device_motorola_cedric
Version Information
Status: Stable
Current Stable Version: TWRP 3.5.2_9-0
Stable Release Date: 2021-04-05
Created 2017-11-03
Last Updated 2021-04-05
FAQs
Q - Does the official twrp version support 64bit roms?
A - Yes - as of version 3.4.0-1
Q - I get error 255 when trying to flash a rom
A - You are using a 32bit twrp version. Please update to the latest 64bit version
Q - Can I use the 64bit version on 32bit roms?
A - Yes the 64bit version supports both 64bit & 32bit roms
Q - Does the official twrp version support treble rom?
A - Yes - as of version 3.4.0-1
Q - Does this recovery support decryption of data
A - Yes on all current 32/64bit roms - If you swap roms you will need to format data first to remove encryption before flashing the new rom then you can encrypt again
Q - My phone keeps booting to recovery on restart and can only be started normally through the bootloader
A - First try removing your SD card and see if your phone boots - If that doesn't work see This Post
Q - Where is the disable dm-verity zip?
A - You can download it Here
or old version can be found Here
Q - Where is the Magisk zip
A - See Magisk Thread
You may need to manually install the magisk manager app apk depending on which rom you are using
Q - It says "image not signed or corrupt" when I flashed image
A - This is normal as the image is not signed by Motorola
Q - When restoring backup I get an error starting Extracttarfork
A - Sometimes you need to format data before restoring backup - In fastboot mode enter the command
fastboot erase userdata
This will format all data on internal storage (pictures music documents downloads etc) so backup first!
Reserved
Thanks
Happy to hear that we got the official twrp support
I have a cedric device. I unlocked my bootloader. Then through fastboot i tried to install twrp-3.1.1-0-cedric.img.
But it says "image not signed or corrupt".
As on the other threads, they said that to directly go into recovery mode ignoring other things. But that did not work. It said "no command".
Please help with flashing twrp.
Edit- It worked after 5-6 attempts.
aashaydesh said:
I have a cedric device. I unlocked my bootloader. Then through fastboot i tried to install twrp-3.1.1-0-cedric.img.
But it says "image not signed or corrupt".
As on the other threads, they said that to directly go into recovery mode ignoring other things. But that did not work. It said "no command".
Please help with flashing twrp.
Click to expand...
Click to collapse
It will always say that because the image is not signed by Motorola
As long as it says write OK at the end
The easiest way is to type
fastboot flash recovery then drag the recovery image into the terminal window - this will automatically complete the rest of the command
I'll also write a note for Windows 10 users who use the power shell
You need to put ./ first
Just to let everyone know about encryption on oreo roms
If you have previously encrypted your phone you must remove encryption before flashing an oreo rom by doing format data from the wipe menu (different from wipe data) & booting the phone fully to check encryption has been removed
You can then flash the oreo rom
After flashing this rom you can encrypt the phone again if you want
Encryption is fully supported
My TWRP (official) can decrypt data of lineageos 15 rom (32bit) as Iv just tested it
bootloop to recovery and SD-ext
I went through all this procedure of unlocking and installing twrp yesterday. As I nearly experienced a heart attack, I would like to kindly ask you to expand your Q/A-section for the mental safety of my fellow G5 users.
If you follow each step, you still can run into the bootloop-to-recovery trouble. My system was formatted with an SD-card as extended internal memory, and I formatted everything exept SD-ext, which I might have done. Clearing the misc partition had no success until I removed the SD-card, and rebooted TWRP.
So basically my recommendation is: remove your SD-card before the procedure.
Happy flashing and thank you for your guide.
TheFixItMan said:
FAQs
Q - My phone keeps booting to recovery on restart and can only be started normally through the bootloader
A - See This Post
Click to expand...
Click to collapse
No-New-Phone said:
I went through all this procedure of unlocking and installing twrp yesterday. As I nearly experienced a heart attack, I would like to kindly ask you to expand your Q/A-section for the mental safety of my fellow G5 users.
If you follow each step, you still can run into the bootloop-to-recovery trouble. My system was formatted with an SD-card as extended internal memory, and I formatted everything exept SD-ext, which I might have done. Clearing the misc partition had no success until I removed the SD-card, and rebooted TWRP.
So basically my recommendation is: remove your SD-card before the procedure.
Happy flashing and thank you for your guide.
Click to expand...
Click to collapse
Added to Faq and guide
Hi, sorry if this is a silly question, but just thought I'd ask to be on the safe side... Is it safe to flash TWRP 3.2.0 that is now available for cedric through the TWRP app or would it be better to give it a miss for now?
RaddingtonBear said:
Hi, sorry if this is a silly question, but just thought I'd ask to be on the safe side... Is it safe to flash TWRP 3.2.0 that is now available for cedric through the TWRP app or would it be better to give it a miss for now?
Click to expand...
Click to collapse
Should be fine - changelog on twrp site
New twrp version available
What's new in 3.2.0-0:
Allow restoring adb backups in the TWRP GUI (bigbiff)
Fix gzip backup error in adb backups (bigbiff)
Fix a bug in TWRP's backup routines that occasionally corrupted backup files (nkk71)
Better support for installing Android 8.0 based zips due to legacy props (nkk71)
Support vold decrypt with keymaster 3.0 in 8.0 firmwares (nkk71)
Decrypt of synthetic passwords for Pixel 2 (Dees_Troy)
Support newer ext4 FBE policies for backup and restore in libtar (Dees_Troy)
v2 fstab support (Dees_Troy)
Bring TWRP forward to android 8.0 AOSP base (Dees_Troy)
Various other minor bugfixes and tweaks
Boot
Twrp 3.2 problem not shutdown phone always restart system
Go twrp and shutdown always restart system.Use Android 8 Oreo Rom
What's new in 3.2.1-0:
* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
TheFixItMan said:
What's new in 3.2.1-0:
* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
Click to expand...
Click to collapse
Thanks a lot for maintaining cedric, you are king man
I unlocked the bootloader and flashed the twrp on my friends Moto g5 and after that if I restart it boots up to recovery only. I did all that's said in the xda forums and still the problem exists.i then wiped away all partitions and installed lineage 14.1. even now the problem exists. After lots of trying I found that going to bootloader and pressing start boots the phone normally. But it's tough to to it always he has to power on the phone. Can someone help me solve this problem
Sent from my Motorola Moto G 2014 using XDA Labs
ProGamer02224 said:
I unlocked the bootloader and flashed the twrp on my friends Moto g5 and after that if I restart it boots up to recovery only. I did all that's said in the xda forums and still the problem exists.i then wiped away all partitions and installed lineage 14.1. even now the problem exists. After lots of trying I found that going to bootloader and pressing start boots the phone normally. But it's tough to to it always he has to power on the phone. Can someone help me solve this problem
Sent from my Motorola Moto G 2014 using XDA Labs
Click to expand...
Click to collapse
Read the faq!
Nice
Thanks Men
Does it have support for 64 bit roms?
Disclaimer:
The use and installation of this software product is at the exclusive responsibility of the user.I am not responsible for any damage that may occur to your device resulting from the use of this software.This software product is "as is". Its first goal is to allow the xiaomi.eu Rom be installed via recovery.If you have any doubts regarding the above lines, you should not use or install it.
Recovery:
Unofficial release 3.7.0 for Xiaomi Mi 10T Lite and Redmi Note 9 Pro 5G devices. Status : StableVersion : 3.7.0.4GRelease Date : 2022.12.26Features:
Android 12 decryptionAndroid 13 decryption (Not tested by myself)FlashingAdbOtg (Not tested by myself)MtpBackup / Restore to / from microSDBackup / Restore through adbSideloadDevice boot Logo changerMagisk tools and theme from @ Brigudav (Not tested by myself)
Notes:
I concluded that custom roms (without Miui) are unable to decrypt /data with this recovery.Checking LineageOS and ArrowOS, it seems that they use a different encryption mode than Miui.I haven't found how to check on Twrp booting what encryption mode /data uses and adjust to it.Therefore, I have uploaded another release for non Miui devices.Can't tested by myself, I don't know if it decrypts fine.However, it is likely the Miui variant will work correctly on the rest.
About official TWRP: The current official release https://twrp.me/xiaomi/xiaomimi10i.html does not work anymore since Miui 13. Use instead this TWRP.
Twrp not decryping on miui 14: Please, read this post
Downloads:
Last release from Xda (Post #2)
Older releases from androidfilehost
Release 3.7.0.3F for CUSTOM NOT Miui rom from Xda (Post #2)
Installation:
Updating this Twrp release:Downloaded to phone:Click on Install and locate the .zip file.Downloaded to PC (no need to copy it to the phone): On phone: start install via ADB (sideload). On PC execute: adb sideload file_name.zip
Try without installing: (does not alter the phone unless you want to do)Extract recovery.img from .zip file downloadedEnter fastboot mode.Execute: fastboot boot recovery.img
Installing this for the first time:
Your bootloader must be open. Extract recovery.img from downloaded .zip file. Enter fastboot mode Execute: fastboot flash recovery recovery.imgCredits:
Team Win RecoveryMinimal Manifest PlatformAlexander Brigudav
Latest release 3.7.0.4G for MIUI rom
Release 3.7.0.3F for CUSTOM Non Miui rom
Nice work
Flashed R2 release, but it doesn't decrypt my data (it doesn't ask about my PIN). I am Polish xiaomi.eu translator and tester, and will ask Xiaomi.eu team about recovery ROM if the storage is decrypted... but can't for now...
Also, I was unable to boot to system after flash that TWRP, I had to use OrangeFox to be able to boot.
kacskrz said:
Flashed R2 release, but it doesn't decrypt my data (it doesn't ask about my PIN). I am Polish xiaomi.eu translator and tester, and will ask Xiaomi.eu team about recovery ROM if the storage is decrypted... but can't for now...
Also, I was unable to boot to system after flash that TWRP, I had to use OrangeFox to be able to boot.
Click to expand...
Click to collapse
Hello. I'm Spanish xiaomi.eu translator and user.
I don't understand how is possible your issue...
When I boot TWRP it asks me for the PIN to decrypt.
I would not have uploaded the image without testing it first.
Also the reboot buttons do what they say..
I have so far tested it without installing, because I have not yet dumped the Stock Recovery partition.
In theory, it is supposed to work exactly the same in boot mode as in flash mode.
Can you try it without installing?
As stated in the third disclaimer lines:
"Its intention is to allow the Rom xiaomi.eu be installed via recovery."
I retired here due to lack of free time and have only become involved now for this reason.
Best regards
tuxafgmur said:
Can you try it without installing?
Click to expand...
Click to collapse
Same situation, unfortunately... (except the reboot button which boots system, as i've just booted recovery, not flashed).
Edit: removed all screen lock methods I've set, still same. Looks like it isn't able to decrypt my data even without screen lock... Maybe something works differently between beta (which I use) and stable (which you use) release?
Edit2: logs there with set PIN as screen lock method https://miuipolska.pl/d/Orjon/gauguin_twrp.zip
Edit 3 24.07. 9:00am CEST: reboot to system works fine now after flashing your recovery, maybe the fact i've used "fastboot reboot-recovery" command was the reason to fail before...
kacskrz said:
Same situation, unfortunately... (except the reboot button which boots system, as i've just booted recovery, not flashed).
Edit: removed all screen lock methods I've set, still same. Looks like it isn't able to decrypt my data even without screen lock... Maybe something works differently between beta (which I use) and stable (which you use) release?
Edit2: logs there with set PIN as screen lock method https://miuipolska.pl/d/Orjon/gauguin_twrp.zip
Click to expand...
Click to collapse
Your logs do not seem to give relevant information about the issue.
It is clear that booting are completely ignoring the security lockout..
During the night I dumped and unpacked the stock recovery.
After studying it, I found nothing significant except that the kernel is not exactly the same as in boot.img.
I'm now downloading the latest weekly release to unpack it and compare vs stable release.
kacskrz said:
Edit 3 24.07. 9:00am CEST: reboot to system works fine now after flashing your recovery, maybe the fact i've used "fastboot reboot-recovery" command was the reason to fail before...
Click to expand...
Click to collapse
I'm not sure I understand what this paragraph means..
Regards.
Pixel Experience 12 data decrypted successfully.
Thanks
Lineage os data decrypted successfully.
Unfortunately, the weekly xiaomi.eu does not decipher the date.
For @kacskrz , @nolan2112 and anyone else using weekly xiaomi.eu:
I would appreciate the test of the new Release 3 I just uploaded.
Thanks in advance.
@tuxafgmur Unfortunately, nothing changed. I've posted logs on the xiaomi.eu thread.
The latest version also cannot decode the date. firmware weekly 22.7.21
New release 3.6.2.1B uploaded
In addition to some other minor changes,
fixed decryption on xiaomi.eu weekly.
New release 3.6.2.1B-R2 uploaded
No relevant changes.
Tested to flash xiaomi.eu from storage and sideload.
tuxafgmur said:
New release 3.6.2.1B-R2 uploaded
No relevant changes.
Click to expand...
Click to collapse
Everything is fine, the recovery is fully working. Thanks Amigo!
New release 3.6.2.1B-R3 uploaded
Revision
New release 3.6.2.1C uploaded
Format: Zip file to install from TWRP.
Some reviews.
Since xiaomi.eu rom replaces boot Logo on global devices, showing "Redmi"
this release includes options to switch logo between "MI" and "Redmi".
Each has two versions to choose from:
1 - Factory stock.2 - Like stock but hiding the padlock shown when bootloader is open.
The only recovery that works (and decrypts) on the newest MIUI 13 Android 12. Thank you!
Fantastic work, congratulations!