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?
Related
For LTE model only!
Usual disclaimers apply (i.e., I am not responsible for bricking your device).
Version: 2.8.6.0-12-gf746dbb
Rationale: CM 12 uses the hardware encryption capabilities of the Qualcomm SoC to strengthen the derived encryption key. To be able to decrypt the data partition, the recovery needs a proprietary daemon blob (qseecomd).
Image available in the Downloads section. Install with
Code:
fastboot flash recovery recovery.img
Known issues:
Date is plain wrong
fastboot boot recovery.img breaks hardware encryption. Please flash the image.
Inspiration/Thanks:
cybojenix's recovery
scritch007's CM12.1 ROM
TeamWin's work on qcom hw encryption for the OnePlus One
XDA:DevDB Information
TWRP with hardware encryption, Tool/Utility for the Moto E 2015
Contributors
vlcdsm
Source Code: https://github.com/vianney/android_device_motorola_surnia
Version Information
Status: Testing
Created 2015-05-25
Last Updated 2015-05-28
Great!
Date is wrong! This is unacceptable!
Just playing. Thanks a ton for the updated recovery. You might want to put which version of TWRP in the subject of the OP
Does this make it to where my Stock Backup will restore and boot properly?? After installing CM12.1 my phone won't boot the backup of my Stock 5.0.2 for some reason
jahrule said:
You might want to put which version of TWRP in the subject of the OP
Click to expand...
Click to collapse
Added in the description (it would make the title too long for my taste ).
goldeneagle1972 said:
Does this make it to where my Stock Backup will restore and boot properly?? After installing CM12.1 my phone won't boot the backup of my Stock 5.0.2 for some reason
Click to expand...
Click to collapse
There should be no reason why this recovery works better than another when it comes to restoring a previous backup. How did you make your backup (which recovery, which version, which format/compression)? Was your device encrypted when you took the backup? Can you read the backup files from a desktop computer?
Just bought the Virgin Mobile Moto E this evening and wanted to make sure I could root before I activated. I use Google Authenticator, and I can't backup and restore my keys without Titanium Backup, so root is essential. Not sure if it's a new BL or what, but not a single damn one of the recoveries I have been trying to flash would open. No errors in flashing, just nothing at all would happen when I try to enter recovery after flashing. Finally this worked. I was pretty close to giving up. Thanks so much for the hard work it takes to create these recoveries for the rest of us.
After flashing this recovery I was unable to flash cm12.1 unified. Any ideas? Reverting back to the other version without encryption enabled me to flash custom ROM again.
Is this intended to allow encryption with stock 5.0.* firmware, or is it just for cyanogenmod etc? I've installed this recovery with stock firmware, but hangs on reboot with a black screen after selecting 'encrypt' from security menu.
I have my device encrypted. After installing this recovery, it asks for a password when I enter recovery mode. However, it only asks for a 3x3 pattern - which is not the size of my pattern. So I'm unable to actually use the encryption support :-/ . Is there any way to change the size of the pattern?
(For now, I'll just switch to a PIN, but still...)
Unofficial TWRP 3.1.0-0 Moto G5 (cedric)
Latest TWRP changelog :
New features of 3.1.1-0 (adb backup, tweaked MTP startup routines and plenty of bug fixes - for full changelog)
Download Link
twrp-3.1.1-0-cedric.img
Working/Bugs
I have just tested on 16 GB variant and all seems to be working. If something is broken lemme know.
IMPORTANT NOTE :
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 SuperSU or flash any of the verity disabler zips there in 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
Installation Guide
Make sure you have unlocked bootloader
Reboot to bootloader
fastboot flash recovery twrp-****.img (if you want permanent flash) or fastboot boot twrp-****.img (if you want temporary
boot)
XDA:DevDB Information
[Unofficial] TWRP 3.1.1-0 Moto G5, Tool/Utility for the Moto G5
Contributors
Santhosh M
Source Code: http://Using prebuilt stock kernel and hence no kernel source available
Version Information
Status: Stable
Stable Release Date: 2017-10-05
Created 2017-03-17
Last Updated 2017-10-05
Reserved
Reserved
Even though I have the plus variant, it's cool to see these features popping up.
Johny Cipeli said:
Even though I have the plus variant, it's cool to see these features popping up.
Click to expand...
Click to collapse
+1
Grt @Santhosh M
Santhosh M said:
Reserved
Click to expand...
Click to collapse
Gonna get that g5+ Bro? it would be awesome if you will be there for support too.
xt1670 model
Hi Santhosh
Will this TWRP work on Moto G5 model xt1670?
If so, can it be rooted using twrp temporary boot?
EDIT: I have tried this several time, I'm always getting stuck at boot, after the first data wipe, only solution is to install stock system again.
I have the Modem Version: M8937_8000.122.02.40R, 32GB
I'm offering to test
Thanks
Works fine for the most part, though reboot options Bootloader and Power Off doesn't work, just restarts normally.
XT1676
KawaiiNeko said:
Works fine for the most part, though reboot options Bootloader and Power Off doesn't work, just restarts normally.
XT1676
Click to expand...
Click to collapse
Plz share the procedure you had followed.
Did you able to achieve root access?
fAIyaZ said:
Plz share the procedure you had followed.
Did you able to achieve root access?
Click to expand...
Click to collapse
Unlocked bootloader, flashed twrp, factory reset, good to go. Sadly no root though.
KawaiiNeko said:
Unlocked bootloader, flashed twrp, factory reset, good to go. Sadly no root though.
Click to expand...
Click to collapse
Try phh su.
Flash it through twrp: https://superuser.phh.me/superuser.zip
Then installed the phh superuser app: https://play.google.com/store/apps/d....phh.superuser
fAIyaZ said:
Try phh su.
Flash it through twrp: https://superuser.phh.me/superuser.zip
Then installed the phh superuser app: https://play.google.com/store/apps/d....phh.superuser
Click to expand...
Click to collapse
worked perfectly! https://i.imgur.com/71G0cN2.png
I'll get my G5 16gb lunar grey tomorrow and can't wait to root
Thanks for testing out
Bootlooping
Hi guys, I got bootloop in my moto g5 after TWRP boot/install, should I open a new thread or somebody can help here?
linsspinho said:
Hi guys, I got bootloop in my moto g5 after TWRP boot/install, should I open a new thread or somebody can help here?
Click to expand...
Click to collapse
Depending on your phone version, you might need to flash system using fastboot.
KawaiiNeko said:
worked perfectly! https://i.imgur.com/71G0cN2.png
Click to expand...
Click to collapse
So i believe TWRP works as intended and root is also achieved via phh/whatever?
If all works fine for you would like you to make reply in the thread with detailed flashing instructions as i am not sure why few in thread have issues
can this version of twrp be used for POTTER version of moto G5 plus?
After installing TWRP my Phone stucks at the "Your device has been unlocked" screen. My system seems to be gone. I've downloaded the image from the other thread and tried to sideload it, but twrp says it's in the wrong format. TWRP boots fine
(Anyone who can upload a fully working NANDROID or sth like that?)
What can i do :/?
Edit: Solved. Unzipped the firmware and flashed manually via fastboot. Working fine!
But then again at the startup of the recovery, there's the encryption message. What to wipe now, that it'll work? Wiping /data ends in boot loop...
.sirhc said:
After installing TWRP my Phone stucks at the "Your device has been unlocked" screen. My system seems to be gone. I've downloaded the image from the other thread and tried to sideload it, but twrp says it's in the wrong format. TWRP boots fine
(Anyone who can upload a fully working NANDROID or sth like that?)
What can i do :/?
Edit: Solved. Unzipped the firmware and flashed manually via fastboot. Working fine!
But then again at the startup of the recovery, there's the encryption message. What to wipe now, that it'll work? Wiping /data ends in boot loop...
Click to expand...
Click to collapse
Did you tried wiping data, and formatting data? Remember that wiping /data is where your apps and settings are stored, and formatting /data/media is the massive storage... Maybe if you wipe both it would work
Enviado desde mi Moto G (5) Plus mediante Tapatalk
After
fastboot flash recovery twrp.img
I'm booting into recovery, cancel the encryption password verification, swipe to allow modification, wipe & format data -> Bootloop
Flashing system (and only system, not recovery etc) -> Phone boots normally, twrp ist gone ...
Greetings
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
LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Wiki.
Recovery
The LineageOS 17.1 reovery is recommended
If you still want to use TWRP never install the TWRP app as system app. Otherwise your device won't boot
Current lineage 17.1 shamu nightlies are based on the N6F27M October 2017 update from google.
So you should be using the radio and bootloader img from that update.
Before you flash a bootloader or radio image please boot to bootloader and check what you have currently installed. You might already have the right one and don't need to flash it again.
They can be extracted from the factory image on google's site here.
Or you can use the ones linked below that I already extracted:
radio-shamu-d4.01-9625-05.45+fsg-9625-02.117.img
bootloader-shamu-moto-apq8084-72.04.img
IMPORTANT NOTE FOR VERIZON USERS: Google released a separate October 2017 security update (NGI77B) just for verizon users that has a different radio. So you'll want to flash it. I repeat, THIS RADIO IS JUST FOR VERIZON USERS.
radio-shamu-d4.01-9625-05.51+fsg-9625-02.118.img
You can use fastboot to flash the bootloader and radio.
More information and installation instructions can be found on the LineageOS wiki here.
Download Links
LineageOS: https://download.lineageos.org/shamu
Google apps: Opengapps Use an ARM (not ARM64) package for Android 10
HEADS UP: When you initially install LineageOS, be sure you flash the gapps package with your ROM. If you boot your ROM, then go back and try to flash gapps after, you're gonna have a bad time.
Changelog
Builddate: 2020.06.17
Changes:
[new] June security updates
[new] LineageOS clock
Builddate: 2020.05.29
Changes:
[new] May security updates
[fix] ULL audio fixes
[new] Add back serif fonts
[fix] Screen turning itself on when no lockscreen is set
[new] Etar calendar
Builddate: 2020.04.12
Changes:
[new] April security updates ROM & kernel
Builddate: 2020.04.08
Changes:
[new] Initial LineagOS 17.1 release
Known Issues:
[bug] Trusted voice is not working and probably never will
[bug] TWRP is not able do decrypt your data if you encrypted it with lineage-16.0
[bug] IMS is not working - if you need it you have to stay on lineage-15.1
XDA:DevDB Information
LineageOS, ROM for the Nexus 6
Contributors
Elektroschmock, elektroschmock, npjohnson
Source Code: http://github.com/lineagos
ROM OS Version: Android 10
ROM Kernel: Linux 3.10.x
Version Information
Status: Nightly
Created 2020-04-08
Last Updated 2020-04-08
Reserved
First build isn't out yet, but I don't want the LineageOS 16.0 thread to be spammed with 17.1 questions
Will waiting for the build you might want to read the Changlog for the first LineageOS 17.1 release:
Changelog 24
Will there be a possibility to root?
Should we wait for 17.1 to flash the radio and bootloader or can we do it now to get it out of the way?
What are the commands for flashing those two images?
Thanks @Elektroschmock and @npjohnson for keeping the Nexus 6 alive in 2020. :good:
Eazy said:
Will there be a possibility to root?
Click to expand...
Click to collapse
Yes you can use your root solution of choice.
Only thing coming with the ROM is adb root.
dlbarron said:
Should we wait for 17.1 to flash the radio and bootloader or can we do it now to get it out of the way?
What are the commands for flashing those two images?
Click to expand...
Click to collapse
Actually you should already have those radio and bootloader images if you had the latest stock image installed at one point.
Commands are:
fastboot flash bootlader [name_of_the_bootloader_image]
and
fastboot flash radio [name_of_the_radio_image]
Elektroschmock said:
Actually you should already have those radio and bootloader images if you had the latest stock image installed at one point.
Commands are:
fastboot flash bootlader [name_of_the_bootloader_image]
and
fastboot flash radio [name_of_the_radio_image]
Click to expand...
Click to collapse
Actually, I've been running Lineage and CM before that since I brought the phone home. So there's no way I had the latest stock image installed ever.
Thanks, I'm all set
Welp I did a stupid.
Flashed the new 17.1 recovery via fastboot. Then I tried to sideload via adb (based on the instructions) but Linux machine kept complaining about needs adb root. Tried with root permission nothing, Then came the stupid. Rebooted into recovery and tried to apply the update. Well that went how I expected, badly. Stuck on LOS loading screen.
Needed a fresh install anyway.
Stick to the instructions, guys.
BootloopedMillennials said:
Welp I did a stupid.
Flashed the new 17.1 recovery via fastboot. Then I tried to sideload via adb (based on the instructions) but Linux machine kept complaining about needs adb root. Tried with root permission nothing, Then came the stupid. Rebooted into recovery and tried to apply the update. Well that went how I expected, badly. Stuck on LOS loading screen.
Needed a fresh install anyway.
Stick to the instructions, guys.
Click to expand...
Click to collapse
Hello you can flash twrp with your pc after boot in twrp flash 17.1 + gapps micro + magisk 20.4 + wipe data + wipe dalvik + wipe cache reboot and it work perfectly ! Ps no intall twrp app in twrp recovery before reboot or you have bootloop Cordialy
BIG THANKS @Elektroschmock very Nice work
xrenoix said:
Hello you can flash twrp with your pc after boot in twrp flash 17.1 + gapps micro + magisk 20.4 + wipe data + wipe dalvik + wipe cache reboot and it work perfectly ! Ps no intall twrp app in twrp recovery before reboot or you have bootloop Cordialy
BIG THANKS @Elektroschmock very Nice work
Click to expand...
Click to collapse
My system got corrupted by the previous process. So I had to do a fresh install.
BootloopedMillennials said:
My system got corrupted by the previous process. So I had to do a fresh install.
Click to expand...
Click to collapse
Hello you have test wipe system with twrp ? Or test repair ? And use pico gapps for trébuchet launcher not work with mirco gapps but pixel launcher work ? !
whats the exact steps to do in twrp.as i stated in los 16 thread i am blind and require twrp open script command line to flash my lineage builds in the past as i have to also enable accessibility services and talkback and google text to speech . so can that also be done with lineage recovery or am i just stuck with twrp and then install lineage 17.1 and open gapps . What's the best advice in my situation .
mrk2815 said:
whats the exact steps to do in twrp.as i stated in los 16 thread i am blind and require twrp open script command line to flash my lineage builds in the past as i have to also enable accessibility services and talkback and google text to speech . so can that also be done with lineage recovery or am i just stuck with twrp and then install lineage 17.1 and open gapps . What's the best advice in my situation .
Click to expand...
Click to collapse
Best would be to use built in update. Unless you want to do a clean install, there's no reason to do it.
the update inside of lineage is blocking updating to lineage 17.1 , i tried tha earlier and i jsut tried it again. then it gives the link to the wiki page.so thats not going to work.i will have to do the old method of flashing through twrp or hoping that there is a command line approach to flashing lineage through lineage recovery.
mrk2815 said:
whats the exact steps to do in twrp.as i stated in los 16 thread i am blind and require twrp open script command line to flash my lineage builds in the past as i have to also enable accessibility services and talkback and google text to speech . so can that also be done with lineage recovery or am i just stuck with twrp and then install lineage 17.1 and open gapps . What's the best advice in my situation .
Click to expand...
Click to collapse
Sorry, I didn't ignore your question, but I first had to check.
It's kind of hard to imagine how a blind person would do it if you can see.
If you have Lineage recovery installed and are able to boot into recovery do the following steps:
Press the Volume Down button 1 time
Press the power button two times
You are now in the adb apply update mode.
There you can install all the zip files you want. I guess you script does the rebooting to system itself.
If you need further help just ask.
@Elektroschmock
Thanks for your hard work!
I have two questions, if lineage recovery wipe the internal storage every time when I wipe the data or system? and when I flash the boot animation it seems not work. May you give some suggestion? Thank you!
s_dino said:
@Elektroschmock
Thanks for your hard work!
I have two questions, if lineage recovery wipe the internal storage every time when I wipe the data or system? and when I flash the boot animation it seems not work. May you give some suggestion? Thank you!
Click to expand...
Click to collapse
The recovery doesn't do anything on it's own. If you want to wipe any partition you need to select the corrosponding entry in the recovery.
I don't know about which bootanimation you are talking about. Do you mean the bootloader?
Before you flash bootloader or radio image please boot to bootloader and check what you have currently installed. You might already have the right one.
Elektroschmock said:
The recovery doesn't do anything on it's own. If you want to wipe any partition you need to select the corrosponding entry in the recovery.
I don't know about which bootanimation you are talking about. Do you mean the bootloader?
Before you flash bootloader or radio image please boot to bootloader and check what you have currently installed. You might already have the right one.
Click to expand...
Click to collapse
In TWRP I can select only wipe data/cache/system, the internal storage can be retained. The lineage recovery haven't the "wipe internal storage" option, so how can I wipe the data/system and keep the internal storage at the same time? Do I need to update the recovery version when I update the system daily build?
I mean I want use the google original boot animation to replace the lineage boot animation, but not success.
I noticed this: "disable audio rotation tracking"
https://review.lineageos.org/c/LineageOS/android_device_moto_shamu/+/272403
Is that the end of stereo sound in landscape? (Of course if that is necessary to fix the loss of sound in calls, it is totally worth it, just curious).
s_dino said:
In TWRP I can select only wipe data/cache/system, the internal storage can be retained. The lineage recovery haven't the "wipe internal storage" option, so how can I wipe the data/system and keep the internal storage at the same time? Do I need to update the recovery version when I update the system daily build?
I mean I want use the google original boot animation to replace the lineage boot animation, but not success.
Click to expand...
Click to collapse
You still have those options:
Go to "Factory Reset"
There you can choose which partition you want to wipe.
- Wipe data/factory reset
- Wipe cache
- Wipe system
I guess you want the "wipe system" option
Sorry we don't support modifying our builds for obvius reasons. If you want to do that you are on your own. Sorry.
runekock said:
I noticed this: "disable audio rotation tracking"
https://review.lineageos.org/c/LineageOS/android_device_moto_shamu/+/272403
Is that the end of stereo sound in landscape? (Of course if that is necessary to fix the loss of sound in calls, it is totally worth it, just curious).
Click to expand...
Click to collapse
It's just a test. Non of us was able to trigger the loss of audio. Youl'll still have stereo but it won't switch channels if you turn your device.
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
Code:
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Features:
- Decryption work
- Otg work
-Vibrator
- Zip Flash
- Mtp/adb
- F2FS support
- Fastbootd
- Adb sideload
- Backup restore and images flash
Not working:
-Tell me
INSTALLATION:
1. Download the TWRP image file to your PC.
2. Put your device into fastboot.
3. Type the following command to flash the recovery:-
Code:
fastboot flash recovery "name_of_recovery.img"
4. On installation of TWRP , to boot the recovery do:-
Code:
fastboot boot "name_of_recovery.img"
The device will automatically reboot into TWRP.
5-A. You are using Xiaomi.eu Miui or custom Rom?
You can enjoy with a functional Data Decrypt
5-B You are using Miui EEA - Global -Cn or any custom rom that doesn't ship custom vbmeta.
6. Download this zip, copy by pc or using otg and flash this zip that will prevent twrp replacing.7. Download VbMeta and flash by fastboot
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img"
7. Reboot into twrp (Take longer Time)
Code:
fastboot boot "name_of_recovery.img"
8. Format Data and Reboot
NOTES:
By Command fastboot boot, recovery will decrypt everytimes you need, also with Global Rom and without patched vbmeta.
Download:
TWRP
VbMeta
(Version tag will follow vendor, a lower version tag than your vendor does not mean that recovery will not work)
Kernel Source: HERE
Donation:
PayPal: paypal.me/manuelbiancodev
Telegram Group: @MBsRoom
One user reported that MTP doesn't work after formatting data, and reboot back to recovery also doesn't make it work again.
Personally I haven't tried it, but the mentioned issue is kinda similar to the last build of mauro's twrp for the phone, so just want to let you know and hope someone else can confirm.
I didn't find how to decrypt data using schema.
huyhung411991 said:
One user reported that MTP doesn't work after formatting data, and reboot back to recovery also doesn't make it work again.
Personally I haven't tried it, but the mentioned issue is kinda similar to the last build of mauro's twrp for the phone, so just want to let you know and hope someone else can confirm.
Click to expand...
Click to collapse
doesn't work after formatting data
zeduck said:
I didn't find how to decrypt data using schema.
Click to expand...
Click to collapse
there are problem to decrypt with 12.2.4 such as umi have to fastboot boot the recovery to decrypt
Thank you.
thought id give it a try...formatting data does indeed make the sdcard inaccessible via mtp; seems the necessary directories isnt created after formatting. if you have a rom installed, you will need to boot back into the rom then reboot to twrp which will now be mtp accessible. tested only on crdroid.
edit: managed to get mtp to work after formatting. after format data reboot to system but on the poco bootscreen, hold down vol up and power key to re-enter twrp, mtp then seems to work
New instructions for eea and global user, post updated.
Decryption works for both PIN and Pattern on EU weekly beta.
PIN didn't work with TWRP3.4.2b but now it is OK with your TWRP. Thank you!
okay.. finally can use my pin again..
cant mount /vendor /product /ODM
With this recovery we don't need anymore to format internal storage every time we change rom?
Redmi K30 Pro Zoom Edition: longer boot into recovery, than LR.Team's TWRP, but PIN decryption works (on mine it worked with LR.Team's too, but I had to cancel password input).
cerealguy said:
With this recovery we don't need anymore to format internal storage every time we change rom?
Click to expand...
Click to collapse
This is rom dependant, if you flash stock global or eaa for example, Yes is needed
New Release!
-Merged 3.5.1 teamwin recovery changes
-Cleaned and ordered twrp flags
-Support to system_ext ro mount
-Improvements into usb managing
manuelbianco said:
New Release!
-Merged 3.5.1 teamwin recovery changes
-Cleaned and ordered twrp flags
-Support to system_ext ro mount
-Improvements into usb managing
Click to expand...
Click to collapse
Touchscreen not working on this version.
karnasw said:
Touchscreen not working on this version.
Click to expand...
Click to collapse
Maybe you clicked into download latest but so dowloaded umi version download this https://sourceforge.net/projects/mbroms/files/TWRPLMI/MBTWRP_08-03-2021.img/download
manuelbianco said:
New Release!
-Merged 3.5.1 teamwin recovery changes
-Cleaned and ordered twrp flags
-Support to system_ext ro mount
-Improvements into usb managing
Click to expand...
Click to collapse
All fine on my Poco F2 Pro. Touchscreen works.
manuelbianco said:
Maybe you clicked into download latest but so dowloaded umi version download this https://sourceforge.net/projects/mbroms/files/TWRPLMI/MBTWRP_08-03-2021.img/download
Click to expand...
Click to collapse
You're right. I downloaded latest not LMI. My bad, sorry.
Do I have to do something special to backup and restore? I want to try some roms but I hate having to config back everything after rollback to the previous ROM.