Related
Currently, all official CyanogenMod ROMs use loki tool to install the kernel on the LG G Pad 8.3 v500. Unfortunately, using loki tool causes a benign "secure boot error message" upon startup.
Here are some scripts that can be flashed in the recovery to convert a loki kernel to a bumped (permissive) kernel. The kernel will remain permissive until a new ROM or kernel is flashed again.
When making a kernel permissive, the following commands will be appended to the kernel boot command line:
Code:
androidboot.selinux=permissive selinux=0
Note: Only apply these scripts one time when setting the kernel to permissive mode or the command line above will be appended twice.
Instructions:
1) Flash ROM
2) Flash one of the scripts below, depending on what you want.
1) Convert a loki kernel to a bumped kernel
v500-loki-kernel-to-bumped-kernel-signed.zip
2) Convert a loki kernel to a bumped permissive kernel (turns off selinux)
v500-loki-kernel-to-bumped-permissive-kernel-signed.zip
3) Convert an already bumped kernel to a permissive bumped kernel (turns off selinux)
v500-bumped-kernel-to-bumped-permissive-kernel-signed.zip
Thanks to @Skin1980 for the bash bump code.
Thanks to @aicjofs for the script base.
This is amazing, thanks for your work.
This is really great, we all love what your doing for us - thanks again. I'm gonna take a stab in the dark and guess that its probably a bad idea to use the CM updater due to these having to be flashed along with an update?
annoyingduck said:
This is really great, we all love what your doing for us - thanks again. I'm gonna take a stab in the dark and guess that its probably a bad idea to use the CM updater due to these having to be flashed along with an update?
Click to expand...
Click to collapse
It's fine to use the cm updater, but you will have to reboot into the recovery twice to apply the patch. Also, if you want your Bluetooth pairings to remain intact, then you want to keep the kernel in permissive mode and never let it boot with selinux enabled (at least until the selinux denials are fixed).
@annoyingduck
You can let cm updater download and verify the update and then hit cancel when it asks to install it. Then manually reboot to recovery and install from the cm updater download directory.
Amazing job @Deltadroid! I applied the first patch, rebooted and the warning message was gone!
Thank you very much for your outstanding work!
[]'s
So... This just removes the warning message when booting?
jesuita said:
So... This just removes the warning message when booting?
Click to expand...
Click to collapse
Yes
jesuita said:
So... This just removes the warning message when booting?
Click to expand...
Click to collapse
That is the only visible effect. It provides a cleaner way of mounting the boot.img
Ok thanks
Works fine with last Infected build.
I assume we have to flash this script after each update.
ledabe974 said:
Works fine with last Infected build.
I assume we have to flash this script after each update.
Click to expand...
Click to collapse
Yes, after each rom or kernel you flash.
Yay! thanks to the permissive script, SuperSU works on CM13! =)
nytral said:
Yay! thanks to the permissive script, SuperSU works on CM13! =)
Click to expand...
Click to collapse
That is good to hear.
The reason systemless supersu does not work with our device is because it breaks the signature on our bumped boot image.
If you choose option #1 on the op after flashing supersu, you should be able to keep selinux in enforcing mode and just rebump the boot image to fix the signature that supersu breaks.
Edit: you will need to dirty flash the rom again to put the device back into enforcing mode.. Then flash supersu and finally the script to bump the boot image over again.
Deltadroid said:
That is good to hear.
The reason systemless supersu does not work with our device is because it breaks the signature on our bumped boot image.
If you choose option #1 on the op after flashing supersu, you should be able to keep selinux in enforcing mode and just rebump the boot image to fix the signature that supersu breaks.
Edit: you will need to dirty flash the rom again to put the device back into enforcing mode.. Then flash supersu and finally the script to bump the boot image over again.
Click to expand...
Click to collapse
Well, that's what I thought and what I did first, but actually latest beta SuperSU (2.68) is not breaking the boot sig for some reason (no bootloader error as with previous builds). Looking at logcat during the stuck boot I noticed some zygote process failing because of selinux and that's when I decided to try to disable it -> success! Now a cleaner way would probably be to give the logs to @Chainfire so he can have a look but given the non-popularity of V500 he probably won't care/not be able to fix it without one. Oh well, at least I have something working although not as secure as it should be. So thank you for this :good:
Thank you for this great job!!! I was stuck on the LG logo with the know loki message... I though that my v500 was bricked for good.
I used the first file after cleaning everything in twrp 3.0.0 (not usb and external) and installing a)6.0 mmb29v, b) su v2.65 and c) your 1st file.
2 questions. 1) whenever I flash and update should I flash it through twrp with the above mentioned order? 2) Should I flash other version (older like 2..8.7.x) and philz zip?
Thank you again for your great job!!!
glyrakos said:
Thank you for this great job!!! I was stuck on the LG logo with the know loki message... I though that my v500 was bricked for good.
I used the first file after cleaning everything in twrp 3.0.0 (not usb and external) and installing a)6.0 mmb29v, b) su v2.65 and c) your 1st file.
2 questions. 1) whenever I flash and update should I flash it through twrp with the above mentioned order? 2) Should I flash other version (older like 2..8.7.x) and philz zip?
Thank you again for your great job!!!
Click to expand...
Click to collapse
You did it correctly. Every time you flash SuperSU over again, you will need to flash this script directly after that to bump the kernel over again and fix the boot signature. Any recovery should work, but I recommend using the latest official TWRP.
Deltadroid said:
You did it correctly. Every time you flash SuperSU over again, you will need to flash this script directly after that to bump the kernel over again and fix the boot signature. Any recovery should work, but I recommend using the latest official TWRP.
Click to expand...
Click to collapse
Sorry, but as a nobbie let me ask you something more. Do you have a link for the latest official TWRP. How to flash it? Through TWRP 3.0.0 that I have now, or through sideload? Also I cannot enter TWRP with the combination of the 3 buttons. I get Factory Reset menu.
Thank you.
glyrakos said:
Sorry, but as a nobbie let me ask you something more. Do you have a link for the latest official TWRP. How to flash it? Through TWRP 3.0.0 that I have now, or through sideload? Also I cannot enter TWRP with the combination of the 3 buttons. I get Factory Reset menu.
Thank you.
Click to expand...
Click to collapse
The official TWRP for device is here
http://forum.xda-developers.com/showthread.php?p=61363260
You can flash the new recovery image from within TWRP.
When you use the 3 buttons to get to recovery, it asks to factory reset, but it goes to TWRP instead. It is a hack because our recoveries were never actually unlocked. Just say, yes and TWRP will open.
Deltadroid said:
The official TWRP for device is here
http://forum.xda-developers.com/showthread.php?p=61363260
You can flash the new recovery image from within TWRP.
When you use the 3 buttons to get to recovery, it asks to factory reset, but it goes to TWRP instead. It is a hack because our recoveries were never actually unlocked. Just say, yes and TWRP will open.
Click to expand...
Click to collapse
Maybe I am not doing something good but when using the 3 button method it goes to factory reset and stays there endless if I do not press something .... but power whipes everything (i've re-setup my v500 for about 15 times already....) ... and volume up/down exits the menu and reboots......
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
Return to Un-modded Stock:
Bootloader unlocked and TWRP and Root included
The file is 4gb compressed to 2gb. Depending on your connection it will probably take 20 to 45 minutes to download.
Be Advised
Do your research before flashing anything, I am not responsible for any damage caused to your device, due to impatience and missed steps. However, rest assured this recovery is solid and will absolutely return your X720 or X727 to stock 5.8.21s (with the bootloader already unlocked, TWRP installed and rooted)
I was asked by several people if I would be willing to share a link to my Stock X727 recovery, I created this thread to provide the 5.8.21s recovery for anyone who is experiencing dire issues or is simply wanting to restore the last official x727 recovery, as a daily driver or as a means to troubleshoot their issues by returning to the fully stock rom, stock partitions and ready to start over.
Attached is my full stock TWRP Recovery for my Le Eco Pro 3, version: 5.8.21s (X727)
It is a clean TWRP backup recovery that I did not mod in any way other than unlocking the bootloader.
The link is to my Google Drive account. https://drive.google.com/open?id=19dtLHmE5bsx5mdtEXOns4Z5drpeY79Em
The file is compressed
Ensure that you perform a full wipe before applying this recovery, and that you know what you are doing before attempting to install.
Please note that any changes that you make to your device is done at your own risk.
Please use caution and make sure that you have TWRP recovery installed.
Be in the habit of booting back to recovery before booting to system....This is a good practice for ensuring TWRP stays installed
You must unpack the downloaded 7zip file, before it will be useable.
As long as you can boot into TWRP and have root access you will have the full permissions needed to install anything , and reverse any actions that do not workout as planned.
Personally, I make a backup of my existing installation prior to making any changes. I recommend that you do the same. If you buy an OTG adapter and a USB 3.0 drive it takes 5 minutes.
The steps provided on the following link can be used to install my recovery file. https://forum.xda-developers.com/le-pro3/how-to/guide-return-to-stock-lock-bootloader-t3539513
When clicking the link, Google will attempt to scan. Click download to see the file, and then choose download if wanted.
Flash the appropriate files below for which ever device you own. ( X727 - Not needed, I provided the files anyway just in case.)
Firmware - X720
https://mega.nz/#F!kDgFQJ6R!MDhxCFw5KjfB0CfxAWwr9w
Firmware - X727
https://drive.google.com/open?id=136-4UpUUsj3exNsTc3d5n2iQuYUxr00H
Modems
X720: https://mega.nz/#F!pZ4WGARZ
Key : !2oG3Z2LS_wP8BzcWUQjfHg
X727: https://mega.nz/#F!NJ5VHS7Z
Key : !p0iO7bDiZ4kXny03EiAlWw
Build Prop Fix Device ID Tool ( Credit to @Ascertion )
https://mega.nz/#F!oAZ3yC4b
Key: !MDwbHXNTRdrpgMvQ42yviw
EFS:
Warning : Use this only if you have unrepairable IMEI Issues! Otherwise its not needed, and you could forever lose your original IMEI info.
https://drive.google.com/open?id=10n2VjwBYHmrq_PllcWmTaGUtMIeYynZ7
[B ]Just for Fun[/B] - Boot Screens and Boot Animations -
https://mega.nz/#F!JB51zbwR
Key: !sG_wXTPqyKpugg5QIZFo9w
These splash-screens and animations came from various sources. If you created them contact me so i can give you credit.
The Red Splash came from the Couco modified EUI : version 5.9.028s VR4
Other Helpful Hints and Tips More to Come!
Unlock Bootloader and Flash Roms, Gapps and Magisk https://forum.xda-developers.com/showpost.php?p=75009966&postcount=692 ( If using original Stock
Viper Settings : https://forum.xda-developers.com/showpost.php?p=75449097
Installing Viper and Dolby: https://forum.xda-developers.com/showpost.php?p=76362493&postcount=19
Edit
October 8, 2018:
I uploaded the Leeco Full Stock Rom 5.8.26s to my MegaDrive.
If you are selling your phone and want it to have stock without TWRP and without root , just flash this Rom and your stock radio driver "firmware" for your device
Link for EUI 21S : https://mega.nz/#!FRhh1ArL
Key: V5ua3oj91kFtgvLYBhl1X6Oq3bsScyDFruN3UptkWN0
A late reply to my issue but I just got around to restoring my Pro3. This worked while the last backup did not! Thanks!
Soul0Reaper said:
A late reply to my issue but I just got around to restoring my Pro3. This worked while the last backup did not! Thanks!
Click to expand...
Click to collapse
Thats Awesome! I am glad that it helped you.
Great work just what I needed only one problem for me after I flash rom reboot system and then go back into TWRP there seems to be encryption on it and I can't install or backup or do much. Is there a password or way around this TWRP encryption?
dunas2331 said:
Great work just what I needed only one problem for me after I flash rom reboot system and then go back into TWRP there seems to be encryption on it and I can't install or backup or do much. Is there a password or way around this TWRP encryption?
Click to expand...
Click to collapse
Sorry, I didn't get a notification for your message. The encryption is your storage.
Follow the instructions here to resolve: https://www.google.com/amp/s/forum....return-to-stock-lock-bootloader-t3539513/amp/
The link has instructions for getting past and removing encryption.
tsongming said:
Sorry, I didn't get a notification for your message. The encryption is your storage.
Follow the instructions here to resolve: https://www.google.com/amp/s/forum....return-to-stock-lock-bootloader-t3539513/amp/
The link has instructions for getting past and removing encryption.
Click to expand...
Click to collapse
Can you elaborate on what to do here I keep getting encryption password too and can't do anything in twrp
Hi tsongming, you know if can work on a x720?
thanks
Toni Moon said:
Hi tsongming, you know if can work on a x720?
thanks
Click to expand...
Click to collapse
Yes x720 and x727 are practically identical phones.
Sent from my LEX720 using XDA Labs
Scruffdog1978 said:
Can you elaborate on what to do here I keep getting encryption password too and can't do anything in twrp
Click to expand...
Click to collapse
I don't have time at the moment to provide lengthy instructions. With respect, I am providing a working, clean unlocked recovery file and pointing the way to instructions already that exist all throughout the LeEco forums.
But here's a quick answer
First use TWRP to reset your phone with a clean wipe, like you would for any ROM. Set developer options to the standard settings.
Next, your storage is encrypted. So it needs to be formatted. Use TWRP format the storage only. Then reboot to recovery.
****Important****
Don't ever format the storage without ensuring that you have a TWRP recovery. Always check the boxes to check if TWRP is installed before swiping. If you don't have a recovery you have a soft brick.
For you information, TWRP recovery is installed on it's on it very own partition. Formatting the storage does not affect the TWRP partition. Nonetheless, if you see the check box option, make sure they are checked.
I would suggest that you install the all in one tool : https://www.google.com/amp/s/forum....pment/tool-tool-one-mauronofrio-t3580611/amp/
This tool helps a lot and makes this stuff easier if are new to flashing custom Roms.. The all in one tool will update the Google driver and ADB installation on your computer.
After you format your drive you will have to flash the recovery from the PC. The links provided show all of the steps, or you can use the all for one tool. When your storage is encrypted you have no choice but to format.
If you use the all in one tool , see their page for instructions.
Read the instructions, then read them again. when learning something new it's a good idea to take notes.
Do not deviate from those steps or you could brick your phone.
There have been many people that have messaged me by PM who successfully returned to stock using my recovery, so it will work as long as you are careful and follow the instructions verbatim and you will be fine. Plus, It's a great idea to create your own working recovery before you begin.
Reminder, you are restoring to stock under you own discretion, I am not responsible if you miss a key step, have a power outage, use faulty cables or brick your device.
One final suggestion, when you install the recovery make sure your phone is fully charged. Unplug all unneeded external peripherals from your desktop computer.
Temporarily, disable antivirus, insert USB cable into the back of your desktop PC. Those outlets provide more power.
Please look past any typos, I typed this on little keys.
One last suggestion
Read this
http://www.androidtipsz.com/top-5-things-to-do-before-installing-a-custom-rom-on-your-android-device
Sent from my LEX720 using XDA Labs
Will I keep twrp after restore? Thanks
---------- Post added at 03:29 PM ---------- Previous post was at 02:53 PM ----------
meh4life321 said:
Will I keep twrp after restore? Thanks
Click to expand...
Click to collapse
Also, could I just restore the system?
Could I just flash this in TWRP and keep twrp as my recovery?
meh4life321 said:
Will I keep twrp after restore? Thanks
---------- Post added at 03:29 PM ---------- Previous post was at 02:53 PM ----------
Also, could I just restore the system?
Click to expand...
Click to collapse
No it will not keep twrp. follow the instructions in the link I provided above, there was no reason to duplicate the instructions on my post.
The difference is that my backup will restore your phone to Eui 5.8.21s with bootloader unlocked. You will need to reflash Twrp and root the phone with Magisk if you want to keep Twrp recovery ( that is what I would do) You will not be able to get OTA updates. But that doesn't matter because there probably not be any more OTA updates for the x727
Thank you, sir! This is great work. I was able to restore back to stock.
On the strange side of thing, my TWRP was saved. Previously, I was running AICP, but having multiple sound issues with it.
Here are the steps I followed to restore:
1) Move the file to OTG flash drive
2) Restore through TWRP via Restore
For my 727, it just reboot on logo, and doesn't go past it.
rob_z11 said:
For my 727, it just reboot on logo, and doesn't go past it.
Click to expand...
Click to collapse
It takes a while.
For me, I had the quickest experience by flashing Magisk afterwards. The stock Rom , Rooted, and with Xposed is actually pretty sweet.
tsongming said:
It takes a while.
For me, I had the quickest experience by flashing Magisk afterwards. The stock Rom , Rooted, and with Xposed is actually pretty sweet.
Click to expand...
Click to collapse
Will try again. How long is while? ?
rob_z11 said:
Will try again. How long is while?
Click to expand...
Click to collapse
It should not take more than 10 minutes, and will usually startup in 5. I just now restored one of my X727's with this recovery, using the OTG method that the last person used and viola in worked so there's no doubt. I have always used ADB until now.
However, unlike the other poster, I did lose Twrp and had to reinstall it.
Always, Always Ensure Twrp is permanently installed
Make sure that you are on the latest version of Twrp : https://twrp.me/leeco/leecolepro3.html
Run Magisk, install Rom, Install Magisk again
Personally, I use the latest version of Magisk : https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
You want a fully clean install before you flash.
Instructions are redundant of XDA: if you want something other than what you have read already: Click on my account history to find detailed instructions, ( I type too much, too often) Under most thanked, you can quickly find detailed instructions for installing , Roms, Rooting, Installing Twrp, How to wipe to avoid any issues.
Finally, if for some reason it still doesn't work, the file may have been corrupted.
Worst Case scenario : there are other recoveries available on XDA. Beware of the edited versions, they do not work as well as an unadulterated recovery.
tsongming said:
It should not take more than 10 minutes, and will usually startup in 5. I just now restored one of my X727's with this recovery, using the OTG method that the last person used and viola in worked so there's no doubt. I have always used ADB until now.
However, unlike the other poster, I did lose Twrp and had to reinstall it.
Always, Always Ensure Twrp is permanently installed
Make sure that you are on the latest version of Twrp : https://twrp.me/leeco/leecolepro3.html
Run Magisk, install Rom, Install Magisk again
Personally, I use the latest version of Magisk : https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
You want a fully clean install before you flash.
Instructions are redundant of XDA: if you want something other than what you have read already: Click on my account history to find detailed instructions, ( I type too much, too often) Under most thanked, you can quickly find detailed instructions for installing , Roms, Rooting, Installing Twrp, How to wipe to avoid any issues.
Finally, if for some reason it still doesn't work, the file may have been corrupted.
Worst Case scenario : there are other recoveries available on XDA. Beware of the edited versions, they do not work as well as an unadulterated recovery.
Click to expand...
Click to collapse
It actually worked for second time without any issues. Just can't get the root, but will follow your instructions.
Hi just wondering does this rom pass safetynet out of the box?
what is the date of the security patch of this rom?
thanks
blanktape said:
Hi just wondering does this rom pass safetynet out of the box?
what is the date of the security patch of this rom?
thanks
Click to expand...
Click to collapse
This recovery is stock EUI 5.8.21s. The exception is that the bootloader is unlocked, and it has TWRP Recovery instead of EUI Recovery. I do not remember which version of Magisk I Installed. I would advise that you flash the newest version of Magisk and you will not have any safety net issues.
If you are wanting a complete return to stock, you should instead reflash the stock Full Rom, which will reinstall EUI recovery and lockdown the bootloader.
Hi Everyone,
With all of the hype around the Exynos phone its finally time for the TGY/CHC Snapdragon variants to get some attention.
No this won't work with US variants, please don't ask. This is tested on my normal s10 (SM-G9730). I'm not sure if the s10+ would work.
I've worked with a few key people to get this working. So credit goes to Flatty, Ianmacd and the creators of tomatolei rom.
This setup will let the user do the following:
-Boot/Restart phone without holding any odd button combos to boot into rooted rom.
-Hold the recovery buttons to get into TWRP.
-Not having to worry about losing root when restarting if you forget to hold your buttons, you don't need to hold anything once properly setup.
The following steps below will help you achieve a stock rom with TWRP:
1. You must be on stock rom, ideally non rooted. If you are rooted, flash your stock rom (The rom version is important, this was completed using the ASH2 version of the TGY firmware.) using ODIN (CSC HOME).
2. Once flashed boot into android and ensure OEM unlocking is enabled in developer settings.
3. Boot to download mode by turning the phone off, then press and hold the volume down button along with the Bixby key just beneath it, then press and hold the power button.
4. Flash attached TWRP from download mode. (This led my phone to boot looping). https://www.mediafire.com/file/cg8bcrf78v66v8j/LatestTomato.tar/file
5. Flash the second attached TWRP (you may have to restart and re-enter download mode again). (I believe the above flash is required too, as it likely contains vendor info). https://www.mediafire.com/file/21akg54uxqk3eix/G9730_TWRP_3.3.1-1_tomatolei-0831-v4.0.tar/file
6. Reboot phone to recovery mode (Volume up, bixby and power upon restart) which will now boot you to TWRP.
7. Flash Snapdragon muti disabler from TWRP. https://www.mediafire.com/file/opbsc7wrcr69b2v/multidisabler-samsung-1.6.zip/file *Per @FlatOutRU After flashing multidisabler you must Wipe Data (if you didn't do that before with twrp - Thanks for the clarification.
8. Boot to your rom and ensure all is well.
9. Feel free to download the latest Magisk zip and flash root from TWRP by using the recovery mode button sequence upon restart.
Sidenote: The G9730_TWRP_3.3.1-1_tomatolei-0831-v4.0.tar and tomatolei ROM also let me install PHH AOSP and PHH LineageOS
PHH AOSP microG: https://forum.xda-developers.com/pr...arm64aosp-9-0-0r21-microg-ufofficial-t3878115
PHH LineageOS: https://forum.xda-developers.com/pr...i-lineageos-16-0-gsi-arm64-ab-how-to-t3908029
Hopefully this gets a few nice Stock ROMs being produced.
Download links are added.
Fznwolf: congrat for this thread, well explained.
some question:
1) what's bring latestomato.tar ? , because no need this for me
2)magisk work for you even if you don't flash magisk_patched.tar?
3)are you able to make backup into twrp because for me it's failed. i think it work if use tomato rom but i prefer stay to tgy rom
pixiebob said:
Fznwolf: congrat for this thread, well explained.
some question:
1) what's bring latestomato.tar ? , because no need this for me
2)magisk work for you even if you don't flash magisk_patched.tar?
3)are you able to make backup into twrp because for me it's failed. i think it work if use tomato rom but i prefer stay to tgy rom
Click to expand...
Click to collapse
Thanks for the compliment @pixiebob
1) I believe the latestomato.tar has some pieces of tomato rom that allow for booting.
2) Yes, i didnt use magisk_patched.tar. I used the official magisk zip after all of my original steps as the last step.
3) I have several backups, I'm on TGY. Try start from scratch and follow my above steps using a TGY rom. Sounds like you may need to wipe and start over using the original steps provided, make sure to use the multidisabler originally attached.
Fznwolf said:
Thanks for the compliment @pixiebob
1) I believe the latestomato.tar has some pieces of tomato rom that allow for booting.
2) Yes, i didnt use magisk_patched.tar. I used the official magisk zip after all of my original steps as the last step.
3) I have several backups, I'm on TGY. Try start from scratch and follow my above steps using a TGY rom. Sounds like you may need to wipe and start over using the original steps provided, make sure to use the multidisabler originally attached.
Click to expand...
Click to collapse
you are right once multidisabler attached to your first post is installed i'm able in Twrp to backup ending without error, fantastic
pixiebob said:
you are right once multidisabler attached to your first post is installed i'm able in Twrp to backup ending without error, fantastic
Click to expand...
Click to collapse
Great to hear it's working out.
Once we root and install twrp, how we can update the phone ?
Otherwise, thanks for your work !
Yay dude thanks for using my instruction and my modified zips without asking me first
You've got an attempt before - trying to post my 9730 overlay for AOSP
Fznwolf said:
I've worked with a few key people to get this working. So credit goes to Flatty, Ianmacd and the creators of tomatolei rom.
Click to expand...
Click to collapse
No, you didn't work with other people. You just spammed me ,my pm here and in telegram to get explanation and posted it here without permission
You've also forgot one important step. After flashing multidisabler you must Wipe Data (if didn't do that before with twrp)
Multidisabler - i've just changed a few lines in @ianmacd code to get it working on our Snapdragon variant.
Twrp.tar - extracted boot.img and recovery.img from @tomatolei ROM for S10+ 9750
Thanks again @FlatOutRU I've updated the initial description to include the wipe after the muti-disabler flash as per your comments.
Hopefully this allows more work to be done on the Snap s10s!
FlatOutRU said:
Yay dude thanks for using my instruction and my modified zips without asking me first
You've got an attempt before - trying to post my 9730 overlay for AOSP
No, you didn't work with other people. You just spammed me ,my pm here and in telegram to get explanation and posted it here without permission
You've also forgot one important step. After flashing multidisabler you must Wipe Data (if didn't do that before with twrp)
Multidisabler - i've just changed a few lines in @ianmacd code to get it working on our Snapdragon variant.
Twrp.tar - extracted boot.img and recovery.img from @tomatolei ROM for S10+ 9750
Click to expand...
Click to collapse
Thank you, it works perfectly.
what Magisk version do you use ?
Is it working with magisk v20 ?
Vuska said:
what Magisk version do you use ?
Is it working with magisk v20 ?
Click to expand...
Click to collapse
I'm on 19.3, I don't see why 20 wouldn't work.
Fznwolf said:
I'm on 19.3, I don't see why 20 wouldn't work.
Click to expand...
Click to collapse
Not work in G9750 ... dont know why...
Sent from my SM-G9750 using Tapatalk
When you say flash (with only stock recovery installed) do you mean with Odin? Which boxes in odin would this tar files go to (e.g. AP, boot?). My phone is s10+ 9750. has it been tested on that? thanks a lot.
Any chance for 9700 (s10E) support?
NisseGurra said:
Any chance for 9700 (s10E) support?
Click to expand...
Click to collapse
Lets consider my method superseded by https://forum.xda-developers.com/s1...p-3-3-1-v3-t3980463/post80569455#post80569455
Thank you @Mentalmuso
heavenly86 said:
When you say flash (with only stock recovery installed) do you mean with Odin? Which boxes in odin would this tar files go to (e.g. AP, boot?). My phone is s10+ 9750. has it been tested on that? thanks a lot.
Click to expand...
Click to collapse
This would be AP, please use https://forum.xda-developers.com/s1...p-3-3-1-v3-t3980463/post80569455#post80569455
Vuska said:
Not work in G9750 ... dont know why...
Sent from my SM-G9750 using Tapatalk
Click to expand...
Click to collapse
https://forum.xda-developers.com/s1...p-3-3-1-v3-t3980463/post80569455#post80569455 will work.
Fznwolf said:
I'm on 19.3, I don't see why 20 wouldn't work.
Click to expand...
Click to collapse
Please do not use 20, it is not found to be working. Stick with 19.3.
Any luck on the 975U. I have e an unlocked VZW 975U running Android Q
Blackweiser35 said:
Any luck on the 975U. I have e an unlocked VZW 975U running Android Q
Click to expand...
Click to collapse
I see no one's responded to you in the last few days, probably because the OP says to not bother asking if it works with US variants. No there's no known way to get root on one of the 97_U variants. The bootloader is locked, and it would take a miracle to bypass that.
Cannot use Dex for PC function.
Could you upload tomatolei's twrp v6, which updated the kernel to support the Dex funtion? Many thanks!
Official TWRP is now available: https://twrp.me/asus/zenfone9.html
IMPORTANT NOTES:
CleanSlate custom kernel is not currently compatible with TWRP for this device (Kirisakura is compatible as of v2.0.6).
This device has a recovery partition (2, in fact), and fastboot boot is disabled in the bootloader. Flashing TWRP to the recovery partition is the only way to use it.
If you attempt to fastboot boot the TWRP image, your device may end up unbootable. YOU'VE BEEN WARNED.
Any questions, comments, feedback, or concerns should always be accompanied by logs (recovery log, logcat, dmesg)
TWRP Trees
Common: https://github.com/TeamWin/android_device_asus_sm84xx-common
Device: https://github.com/TeamWin/android_device_asus_AI2202
Thanks for your work!
Installed as on twrp.me described wont boot (https://twrp.me/asus/zenfone9.html)
Had to flash stock recovery again.
Rooted device on 32.2050.2050.29 with kirisakura-kernel.
Any idea what im doing wrong?
Hermann2306 said:
Thanks for your work!
Installed as on twrp.me described wont boot (https://twrp.me/asus/zenfone9.html)
Had to flash stock recovery again.
Rooted device on 32.2050.2050.29 with kirisakura-kernel.
Any idea what im doing wrong?
Click to expand...
Click to collapse
If you're not on stock kernel, then that's probably the problem. I know the custom kernel situation is different on this device than previous ones. This may be something that @Freak07 & I have to look into together. In the meantime, can you restore back to stock kernel and confirm that TWRP works, and then install Kirisakura and see if everything still works?
Restored stock kernel with kernelflasher but now it wont boot. Tried to change the slot to a but isnt allowed in fastboot.
Have to find out now how to change the slot or install stock kernel via fastboot...
Hermann2306 said:
Restored stock kernel with kernelflasher but now it wont boot. Tried to change the slot to a but isnt allowed in fastboot.
Have to find out now how to change the slot or install stock kernel via fastboot...
Click to expand...
Click to collapse
It doesn't sound like you followed the procedure in the Kirisakura thread FAQ to fully return to stock. Can you confirm exactly what you did?
just restored the backup i made with kernelflasher befor i installed the custom kernel and rebooted.
Hermann2306 said:
just restored the backup i made with kernelflasher befor i installed the custom kernel and rebooted.
Click to expand...
Click to collapse
I'm not familiar with that app, sorry. I just know that's not the process mentioned in his thread, so until you do that, I can't really confirm what the problem could be.
ok, im back on stock. flashing following files helped. i will test twrp again later and report. thanks for your replies.
fastboot flash boot boot.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash dtbo dtbo.img
fastboot reboot fastboot
fastboot flash vendor_dlkm vendor_dlkm.img
fastboot reboot
With stock kernel twrp works. Just installed as described on twrp.me. The official twrp app from playstore crashes after root allowing.
For everyone who comes from custom kernel flash the files from your actual firmware (payload-dumper) as described in the post above.
Are you working on custom kernel support?
Hermann2306 said:
With stock kernel twrp works. Just installed as described on twrp.me. The official twrp app from playstore crashes after root allowing.
For everyone who comes from custom kernel flash the files from your actual firmware (payload-dumper) as described in the post above.
Are you working on custom kernel support?
Click to expand...
Click to collapse
From stock, I just flashed the Kirisakura zip in TWRP and my device booted up fine.
EDIT: While the above is true, TWRP no longer functions after installing the kernel, and the device won't reboot again after installing it. So something is definitely wrong somewhere.
For now, I can only suggest not using it with a custom kernel until we figure this out.
Ok, flashing with EXKernelManager works also.
update
I can do reboots but twrp doesnt work anymore
Hermann2306 said:
Ok, flashing with EXKernelManager works also.
update
I can do reboots but twrp doesnt work anymore
Click to expand...
Click to collapse
Yes, there seems to be an issue in the kernel that's preventing TWRP from working. I'm not sure what the issue is, unfortunately.
So every time I restore a back up, do I have to delete all lock screen requirements ?
If that's the case, I would have to redo my fingerprints every time
c19932 said:
So every time I restore a back up, do I have to delete all lock screen requirements ?
If that's the case, I would have to redo my fingerprints every time
Click to expand...
Click to collapse
Yes.
Quick PSA for anyone using this TWRP that also wants to use a custom kernel:
As of Kirisakura 2.0.6, the custom kernel and TWRP can now co-exist. This is due to the changes that allowed a monolithic kernel build. Presently, CleanSlate has not adopted those changes, but if/when it does, I will remove that disclaimer from the OP.
Thanks to @arter97, @Freak07, & @tbalden for supporting this device!
Is the twrp compatible with android 13?
NisseGurra said:
Is the twrp compatible with android 13?
Click to expand...
Click to collapse
There's a really easy way to find out...
Captain_Throwback said:
There's a really easy way to find out...
Click to expand...
Click to collapse
I getting decrypt errors that why the q
NisseGurra said:
I getting decrypt errors that why the q
Click to expand...
Click to collapse
Then you should post some logs
Will do