ASUS - ZenFone 4 Pro - Z01G
TWRP Version: 3.3.1-0
Kernel Version: WW-15.0410.1904.104
*** WARNING ***
This image is NOT compatible with other ZenFones. If flashing is initiated on an unsupported device it COULD and/or WILL brick the device.
YOU ASSUME ALL RESPONSIBILITY!!
Notes:
This image was built from the official TWRP Minimal Manifest source for Android 8.1 and uses the prebuilt kernel from the WW-15.0410.1904.104 update posted on the ASUS website.
- The kernel has been patched to disable DM-Verity.
Installation:
Using fastboot from a command line or terminal you need to do-
fastboot flash recovery twrp-3.3.1-0-O8.1-PrebuiltKernel-15.0410.1904.104.img
fastboot oem reboot-recovery
Enjoy
Download Link
Thanks to shakalaca for his efforts in getting TWRP to our devices and his Device Tree!!
Hi, thanks for contributing to development on this phone!
So if I have my ZS551KL updated to the latest firmware version, and the bootloader is unlocked, can I flash this without wiping anything, and go on to flash Magisk v19.3?
Yes, you should be able to. Magisk should patch your bootloader for DM-verity.
Should i upgrade my twrp 3.2.1 to this version? what is the difference between twrp 3.2.1 and twrp 3.3.1?
So I went into fastboot mode, and flashed this image, then I went into recovery and flashed Magisk, rebooted into system and it worked.
Then I did a factory reset from the system settings, and now it only boots into TWRP. I just wanted to add TWRP and Magisk and start anew. What should I do?
At this point I would start fresh. Sounds like something went amiss. So from TWRP, I would wipe Dalvik, System, Data and Cache. Then back up to the reboot screen and tell it to reboot to recovery. At this point the system will warn that no OS is installed. Tell it to go ahead. It should reboot and bring you back to the recovery. From a PC download the zip below. Then transfer it to your phone while it's still in TWRP recovery. After it's transferred use TWRP to install it. It's my full update that also includes TWRP and the patched bootloader. Then tell the device to reboot. You should be completely fresh then. At that point of you want to install Magisk, go ahead. There isn't any reason to wipe it after installing Magisk.
https://mega.nz/#!BegyVKiB!zxgzNBr_XJ4WnlJBwqMq1oqbQgnuECkdClcZLNVIPz8
Okay, thanks. I am gonna try that tomarrow.
That image you gave me has TWRP 3.2.1 right? Right now I have the latest, 3.3.1.
Can I have TWRP update itself , or should I reflash the 3.3.1 from your other post again?
Sorry to all the questions, I'm relatively new and you seem like you know how everything works.
Okay, I did what you said. I noticed the phone hanging up in some parts of first-time-setup that it wasn't before, but it might be nothing. I also keep having a popup say "FOTAService keeps stopping" with a Close app option. Closing the app doesn't fix it, it returns maybe a minute or two later. The only way I can stop it is by force stopping the app, but It restarts the next time my phone is rebooted. I've cleared its data/cache and it didn't help. I've seen some people say to 'freeze' the service to fix it. How would you fix it?
Also, on another side note: did you add the google assistant to this update, or was it added by ASUS? I don't recall it being there when I first started, but its a nice surprise to see its included.
---------- Post added at 05:46 PM ---------- Previous post was at 05:31 PM ----------
Welp, I just answered my own question. I went into TWRP and wiped Davlik again, and FOTA stopped stopping :good:
As for it being slow during first-time-setup, it might just be Davlik optimizing everything since the cache was cleared.
So I'm gonna try to update TWRP from that image you gave me, because it bothers me not having the newest version lol
Thanks so much! Very helpful
Cool, after flashing your image, I flashed your TWRP image from your other thread and i have the lateat version.
I also wanted to add that the FOTAService thing kept happening for a while. I am not sure exactly what did the trick, but some combonation of force stopping the FOTAService, clearing all data for the app, and then botting into TWRP and clearing Davlik, and then possibly letting the phone do its work reoptimizing apps finally stopped it for good. Just wanted to post that incase anybody else was having the same issue.
bobs50000 said:
So I went into fastboot mode, and flashed this image, then I went into recovery and flashed Magisk, rebooted into system and it worked.
Then I did a factory reset from the system settings, and now it only boots into TWRP. I just wanted to add TWRP and Magisk and start anew. What should I do?
Click to expand...
Click to collapse
bobs50000 said:
Cool, after flashing your image, I flashed your TWRP image from your other thread and i have the lateat version.
I also wanted to add that the FOTAService thing kept happening for a while. I am not sure exactly what did the trick, but some combonation of force stopping the FOTAService, clearing all data for the app, and then botting into TWRP and clearing Davlik, and then possibly letting the phone do its work reoptimizing apps finally stopped it for good. Just wanted to post that incase anybody else was having the same issue.
Click to expand...
Click to collapse
I'm sorry I didn't respond sooner, it's been daughters birthday. I'm glad you go everything lined out. The FOTA issue is kinda odd. Never had it. I've probably flashed and reflashed this phone close to a hundred times. Heck because I was bored the other night I even went back to 7.1.1 to play around. I'm not sure which version I like better, lol. I'm probably going to end up posting pure OEM zips for those that want to be 99% stock. We just can't relock the bootloader. Cheers!
TheCapesCrew said:
ASUS - ZenFone 4 Pro - Z01G
TWRP Version: 3.3.1-0
Kernel Version: WW-15.0410.1904.104
*** WARNING ***
This image is NOT compatible with other ZenFones. If flashing is initiated on an unsupported device it COULD and/or WILL brick the device.
YOU ASSUME ALL RESPONSIBILITY!!
Notes:
This image was built from the official TWRP Minimal Manifest source for Android 8.1 and uses the prebuilt kernel from the WW-15.0410.1904.104 update posted on the ASUS website.
- The kernel has been patched to disable DM-Verity.
Installation:
Using fastboot from a command line or terminal you need to do-
fastboot flash recovery twrp-3.3.1-0-O8.1-PrebuiltKernel-15.0410.1904.104.img
fastboot oem reboot-recovery
Enjoy
Download Link
Thanks to shakalaca for his efforts in getting TWRP to our devices and his Device Tree!!
Click to expand...
Click to collapse
Hello everyone!
Can I get a NEW download link? or if there is a new further version ... the link in the post has expired ... THANKS
Related
Welcome everyone!
This thread has been created for extreme newbies/noobs and for their benefit. Not only noobs, but everyone is free to post questions and also give answers to those questions. Any type of question is allowed as long as it is related about the device. No off-topic discussions are allowed!
Hit Thanks if I Helped You!
Regards,
PoseidonKing
Hello,
I've installed a custom recovery, SuperSU and the xposed framework on my Wileyfox Swift 2 Plus and yesterday I've received an OTA update with wich I was (as expected) unable to update my phone. (it just rebooted to TWRP and did nothing) On their website I was only able to find an older build. I think what I have to do is install the stock recovery(to install the update then switch back to a custom one), but I don't know where to get it from.
boa05 said:
Hello,
I've installed a custom recovery, SuperSU and the xposed framework on my Wileyfox Swift 2 Plus and yesterday I've received an OTA update with wich I was (as expected) unable to update my phone. (it just rebooted to TWRP and did nothing) On their website I was only able to find an older build. I think what I have to do is install the stock recovery(to install the update then switch back to a custom one), but I don't know where to get it from.
Click to expand...
Click to collapse
Here you go. https://drive.google.com/file/d/0B1k2IwBoVgfFVVF1UEY3cUVVY28/view?usp=sharing
I grabbed this from cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87 - flash it via Fastboot preferably.
linuxct said:
Here you go. https://drive.google.com/file/d/0B1k2IwBoVgfFVVF1UEY3cUVVY28/view?usp=sharing
I grabbed this from cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87 - flash it via Fastboot preferably.
Click to expand...
Click to collapse
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
boa05 said:
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
Click to expand...
Click to collapse
You mean, a Cid face? LOL
You can revert by flashing the system.img via fastboot from the very same zip I mentioned before. You can get it here: http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
boa05 said:
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
Click to expand...
Click to collapse
Exactly the same here. I flashed TWRP so I can install SuperSU for root access, now I've flashed back the stock recovery to apply the update and it ends in "Error".
It's also not possible to apply the downloaded zip-package manually (not via TWRP and not via Cyanogen recovery).
Log file says:
E: footer is wrong
E: Signatur verification failed
Installation aborted.
Click to expand...
Click to collapse
It's not an option for me to do a full reset each time they (who ever it might be in the future) release an update.
I bought this phone because I thought it might be easier to update/ get root access compared with e.g. Samsung devices, but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
zerospaced said:
Exactly the same here. I flashed TWRP so I can install SuperSU for root access, now I've flashed back the stock recovery to apply the update and it ends in "Error".
It's also not possible to apply the downloaded zip-package manually (not via TWRP and not via Cyanogen recovery).
Log file says:
It's not an option for me to do a full reset each time they (who ever it might be in the future) release an update.
I bought this phone because I thought it might be easier to update/ get root access compared with e.g. Samsung devices, but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
Click to expand...
Click to collapse
I haven't checked myself but linuxct seems to say its an img file. You need to flash img files with fastboot. Have you tried unziping the .zip file and seeing if there are img files (e.g system.img, recovery.img)
If you don't know how to use fastboot here is a good tutorial: https://forum.xda-developers.com/showthread.php?t=2277112
Hope this helps.
zerospaced said:
I flashed TWRP so I can install SuperSU for root access
Click to expand...
Click to collapse
You can enable that inside Developer options > Root access. There's no need to either alter your system nor unlock your bootloader if your only concern is root privileges.
zerospaced said:
... but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
Click to expand...
Click to collapse
Cyanogen is no more, Wileyfox's switching to an AOSP-based ROM through the following OTAs, which will be Android 7.0 Nougat and will start rolling on february. You've more info here: https://forum.xda-developers.com/swift-2/how-to/official-wileyfox-statement-regarding-t3528844
linuxct said:
You can enable that inside Developer options > Root access. There's no need to either alter your system nor unlock your bootloader if your only concern is root privileges.
Click to expand...
Click to collapse
No, I think that is only there in CyanogenMod (the community based custom rom) not in the Cyanogen OS (the proprietary OS for businesses). As far as I know no OEM can release an android phone with Gapps and root. We have an option there called "OEM unlock" which will allow you to unlock your bootloader (from a computer) but nothing else that would grant root out of box.
zerospaced said:
Exactly the same here. I flashed TWRP so I can install SuperSU for root access, now I've flashed back the stock recovery to apply the update and it ends in "Error".
It's also not possible to apply the downloaded zip-package manually (not via TWRP and not via Cyanogen recovery).
Log file says:
It's not an option for me to do a full reset each time they (who ever it might be in the future) release an update.
I bought this phone because I thought it might be easier to update/ get root access compared with e.g. Samsung devices, but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
Click to expand...
Click to collapse
Just flashing back to the stock recovery does not remove SuperSU. Due to your error I'm assuming you have a non-systemless root. In order to remove SuperSU you must flash http://downloadmirror.co/Uot/UPDATE-unSU.zip (with TWRP), and if that doesn't work I would recommend flashing back to full stock cyngn from: https://cyngn.com/support.
Cheers!
linuxct said:
You mean, a Cid face? LOL
You can revert by flashing the system.img via fastboot from the very same zip I mentioned before. You can get it here: http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
Click to expand...
Click to collapse
Thank you very much, flashing the system.img with
Code:
fastboot flash system system.img
fixed the issue and I was able to update my system to the latest version and since it only changed the system partition, no data (files from internal/external storage) nor apps (not even their data) were deleted. After the update I had to flash TWRP, SuperSU and Xposed again.
boa05 said:
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
Click to expand...
Click to collapse
boa05 said:
Thank you very much, flashing the system.img with
Code:
fastboot flash system system.img
fixed the issue and I was able to update my system to the latest version and since it only changed the system partition, no data (files from internal/external storage) nor apps (not even their data) were deleted. After the update I had to flash TWRP, SuperSU and Xposed again.
Click to expand...
Click to collapse
Thank you, but unfortunately I've read this hint after trying the unsu method described here:
https://forum.xda-developers.com/showpost.php?p=63615067
I've installed the unsu-zip package and flashed the original boot.img via TWRP. It did not help, but since I did this I have another warning message when booting: "The dm-verity is not started in enforcing mode."
In the end I managed to get the update by installing the original zip package again and after this the OTA update worked.
What still remains is the new "dm-verity error message" right after booting....
Does anyone know if there is anywhere I can find the files to manually update to the new AOSP based ROM. Or has Wileyfox not released it?
(Or has anyone captured the PTA link?)
There is currently no new AOSP ROM. I've received only Cyanogen OS update (probably the last one?). According the Wileyfox statement on facebook, the new ROM (Nougat) will be released in the february...
rivierakid said:
There is currently no new AOSP ROM. I've received only Cyanogen OS update (probably the last one?). According the Wileyfox statement on facebook, the new ROM (Nougat) will be released in the february...
Click to expand...
Click to collapse
Nah they are releasing an update first to transition to their new rom.
"We have been ruthlessly testing this and planning a distribution for this update, with a rollout to be released beginning today with immediate effect." -Wileyfox Facebook
Click to expand...
Click to collapse
Then later (between February and end of Q1) they will release nougat. Its an easy mistake to make as they aren't too clear about it.
Thanks anyway.
It is unclear what kind of ROM will they release. According the statement it should be bloatware free OS
AOSP, Lineage OS, something else?
I really like cyanogenmod, so I hope there will be Lineage OS ROM in the future...
The new update
Hi, I'm not in the least technologically minded so please don't take the mick when I ask, will the new update delete the cyanogen os? Or is that something I will have to do? If so, what is safe to delete without damaging my phone?
Wow, that was a couple more questions then I had thought!
Thanks all.
Hello,
iam very frustrated by this OTA thing..
I had TWRP and SuperSU installed and i've tried everything but I can't install this OTA -.-" everytime i've tried it it gives me just an "ERROR".
1. I flashed the unSU zip in twrp.
2. I set the switch for stock recovery in developer options.
3 I fastboot flashed the stock recovery.img
4 I fastboot flashed the stock system.img
Then rebooted and did the update it just runs to like 20% and stops and then it shows me "ERROR" ..
Can somebody experienced help me pls This update is annoying I had to block it out of my mobile data use because it would eat up all my mobile data
EDIT: Maybe I have to relock my bootloader?
MCPoppa said:
Hello,
iam very frustrated by this OTA thing..
I had TWRP and SuperSU installed and i've tried everything but I can't install this OTA -.-" everytime i've tried it it gives me just an "ERROR".
1. I flashed the unSU zip in twrp.
2. I set the switch for stock recovery in developer options.
3 I fastboot flashed the stock recovery.img
4 I fastboot flashed the stock system.img
Then rebooted and did the update it just runs to like 20% and stops and then it shows me "ERROR" ..
Can somebody experienced help me pls This update is annoying I had to block it out of my mobile data use because it would eat up all my mobile data
EDIT: Maybe I have to relock my bootloader?
Click to expand...
Click to collapse
I don't think it'd be a good idea to mess with the bootloader for now. Also, I uninstalled SuperSU from the app. If you have xposed I suggest you uninstall that too (At least that's what I did). Sorry I can't help more I 'm still a little newby myself.
rivierakid said:
It is unclear what kind of ROM will they release. According the statement it should be bloatware free OS
AOSP, Lineage OS, something else?
I really like cyanogenmod, so I hope there will be Lineage OS ROM in the future...
Click to expand...
Click to collapse
Sadly, an OEM cannot rely on community-driven software, so it surely won't be CyanogenMod/Lineage. But, that doesn't mean that in the future we wouldn't be able to enjoy it thanks to custom ROM development
Jahane said:
Hi, I'm not in the least technologically minded so please don't take the mick when I ask, will the new update delete the cyanogen os? Or is that something I will have to do? If so, what is safe to delete without damaging my phone?
Wow, that was a couple more questions then I had thought!
Thanks all.
Click to expand...
Click to collapse
Welcome to the community!
This depends on what you understand about 'new update'. If the new update you're talking about is the currently rolling OTA, the one that's getting prompted on every phone right now, no, that won't delete CyanogenOS yet, but prepare the device to upgrade to a CyanogenOS-free Android 7.0 ROM, which will happen in a month or so. You won't have to do anything but let the phone update each and every single time it requests it. Cyanogen itself is not something you can remove as a user, unless you install what's called a custom ROM (this means, a different ROM software than the one provided by Wileyfox), so, you don't need to worry about it but keeping your device up-to-date as soon as it prompts you with an update ^_^
MCPoppa said:
Hello,
iam very frustrated by this OTA thing..
I had TWRP and SuperSU installed and i've tried everything but I can't install this OTA -.-" everytime i've tried it it gives me just an "ERROR".
1. I flashed the unSU zip in twrp.
2. I set the switch for stock recovery in developer options.
3 I fastboot flashed the stock recovery.img
4 I fastboot flashed the stock system.img
Then rebooted and did the update it just runs to like 20% and stops and then it shows me "ERROR" ..
Can somebody experienced help me pls This update is annoying I had to block it out of my mobile data use because it would eat up all my mobile data
EDIT: Maybe I have to relock my bootloader?
Click to expand...
Click to collapse
Try relocking like you said, but before, flash everything included in the latest CyanogenOS fasboot image zip (from here). To flash all of them at once, execute each and every of the following commands:
Code:
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash modem NON-HLOS.bin
fastboot flash dsp adspso.bin
fastboot flash devcfg devcfg.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash keymaster keymaster.mbn
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash splash splash.img
fastboot flash tz tz.mbn
Once done, relock your bootloader by doing:
Code:
fastboot oem lock
Please note, this probably doesn't fully lock your bootloader, as some propietary DRM keys might've been lost during the unlock process...
Good luck and please, keep us posted!
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.
MTP does not work in TWRP on the Pixel 3 and will not work until we have time to update the TWRP MTP implementation. You may still use adb to push and pull files.
Pixel devices have 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore. There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring. You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B. Changing the slot in TWRP also tells the bootloader to boot that slot.
The zip install method installs TWRP to both slots.
Installation:
If you already have TWRP installed: Download the latest zip and install the zip using TWRP.
If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. If you are currently rooted, you will need to reflash the stock boot image before installing TWRP. After installing the stock boot image, follow the instructions for installing TWRP. Once TWRP is installed, you will need to reflash root.
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
3.2.3-0: Initial release for the Pixel 3 devices
Pixel 3:
https://twrp.me/google/googlepixel3.html
https://dl.twrp.me/blueline/
Pixel 3 XL:
https://twrp.me/google/googlepixel3xl.html
https://dl.twrp.me/crosshatch/
Reserved.
You are the man! Cant believe we have TWRP this early! Just in time for the next OTA!
Thank you for this! Great work, it feels like an early Christmas!
All set up with TWRP and rooted again,,even made a back up,,,awesome job to the dev!
Thanks you!
Is anyone having the touchscreen not work after a reboot?
Archangel said:
All set up with TWRP and rooted again,,even made a back up,,,awesome job to the dev!
Click to expand...
Click to collapse
I got twrp up and running on my Pixel 3, but when try to install magisk 17.3 via twrp it says it completes but just bootloops. And I have to restore again. How did you go about it?
code_311 said:
Is anyone having the touchscreen not work after a reboot?
Click to expand...
Click to collapse
On the Pixel 2 XL touch was broken unless you used a custom kernel. I guess it's the same on 3. If you boot TWRP using fastboot it should allow touchscreen.
You would think after buying the Pixel 1, 2 and 3 I would have this whole A/B slot thing down pat but I dont LOL. That did the same thing for me too. I just rebooted into recovery and flashed TWRP again and it has been fine since. I think sometimes it switches slots and that causes the bootloop. I messed around with changing slots and I think I am on slot A and all if fine for me.
Mrnicgeuy633 said:
I got twrp up and running on my Pixel 3, but when try to install magisk 17.3 via twrp it says it completes but just bootloops. And I have to restore again. How did you go about it?
Click to expand...
Click to collapse
---------- Post added at 02:53 PM ---------- Previous post was at 02:52 PM ----------
I had that happen I think once and I just rebooted back into TWRP and it was fine.
code_311 said:
Is anyone having the touchscreen not work after a reboot?
Click to expand...
Click to collapse
Hey guys - I'm a pixel noob and have a quick question about TWRP/Magisk.
I was rooted before TWRP came out so I flashed the stock boot images back to slots A and B. Then I followed steps 2-12 of the following article to install both Magisk and TWRP using temp TWRP. https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
My question is... when I was temp booted into TWRP, and installed the Magisk zip file, it only said that it installed to slot A. But when I was rooted before TWRP released I remember I had to flash the patched boot image to both slots. So using the process I followed, do I have one slot rooted and the other not? If so, is that a problem? Phone seems to work perfectly and root is working.
Sorry if this is a dumb question. I've always been a HTC guy but I'm trying
ktdt00 said:
Hey guys - I'm a pixel noob and have a quick question about TWRP/Magisk.
I was rooted before TWRP came out so I flashed the stock boot images back to slots A and B. Then I followed steps 2-12 of the following article to install both Magisk and TWRP using temp TWRP. https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
My question is... when I was temp booted into TWRP, and installed the Magisk zip file, it only said that it installed to slot A. But when I was rooted before TWRP released I remember I had to flash the patched boot image to both slots. So using the process I followed, do I have one slot rooted and the other not? If so, is that a problem? Phone seems to work perfectly and root is working.
Sorry if this is a dumb question. I've always been a HTC guy but I'm trying
Click to expand...
Click to collapse
No, only the current slot needs to be rooted.
Hello,
I apparently have one of these Pixel 3's that are not working with the current version of TWRP (twrp-3.2.3-0-blueline.img). Yes, I have a 3, not a 3XL. I have done these a hundred times before so I am fairly confident I am not doing anything wrong either. I get the file to load through ADB but on the reboot, it just hangs on the Google screen forever. I have left it for an hour. I have tried everything I can think of. Does anyone have any advice or is in the same situation? I just got my Pixel 3 in the mail on Friday so it's as fresh as they come. I was thinking of fully flashing the TWRP image, but I really don't think it's going to make any difference and I don't want the extra hassle of tracking down the official boot.img from the repo. I guess I will just have to wait until someone who really knows how to debug these comes across one like mine. Clearly, something has changed in what Google is sending out.
For reference:
Android security patch level: September 5,2018
Baseband version: g845-00023-180815-B-4956438
Kernel Version: 4.9.96-g340a9aaf92bc-ab4959234 #0 Thu Aug 16 23:24:20 UTC 2018
Build number: PD1A.180720.031
Much appreciated! $50 donation to anyone who can get me past this and rooted. I'm an old-time Verizon unlimited data planner and I need that tether check disabled.
Is root
To Pixel 3 owners that succesfully rooted, can you share the build.prop here? /system/build.prop
when i booted in to twrp it was encrypted! but i didnt have a PW.... so for everyone to whom that happens, boot up normally and disable your pin ! then you can see your storage in twrp!
i almost flipped this morning hahahaha
Carmenlove said:
Hello,
I apparently have one of these Pixel 3's that are not working with the current version of TWRP (twrp-3.2.3-0-blueline.img). Yes, I have a 3, not a 3XL. I have done these a hundred times before so I am fairly confident I am not doing anything wrong either. I get the file to load through ADB but on the reboot, it just hangs on the Google screen forever. I have left it for an hour. I have tried everything I can think of. Does anyone have any advice or is in the same situation? I just got my Pixel 3 in the mail on Friday so it's as fresh as they come. I was thinking of fully flashing the TWRP image, but I really don't think it's going to make any difference and I don't want the extra hassle of tracking down the official boot.img from the repo. I guess I will just have to wait until someone who really knows how to debug these comes across one like mine. Clearly, something has changed in what Google is sending out.
For reference:
Android security patch level: September 5,2018
Baseband version: g845-00023-180815-B-4956438
Kernel Version: 4.9.96-g340a9aaf92bc-ab4959234 #0 Thu Aug 16 23:24:20 UTC 2018
Build number: PD1A.180720.031
Much appreciated! $50 donation to anyone who can get me past this and rooted. I'm an old-time Verizon unlimited data planner and I need that tether check disabled.
Click to expand...
Click to collapse
Flash the stock boot image. Then try to fastboot boot "path to TWRP". If it still hangs, redownload TWRP and try again. Here's the stock boot for Pixel 3... https://drive.google.com/file/d/1EMkcRkH7n-1bGlVbbzcEJKKPJeE4l9mB/view?usp=drivesdk
jsauder2 said:
Flash the stock boot image. Then try to fastboot boot "path to TWRP". If it still hangs, redownload TWRP and try again. Here's the stock boot for Pixel 3... https://drive.google.com/file/d/1EMkcRkH7n-1bGlVbbzcEJKKPJeE4l9mB/view?usp=drivesdk
Click to expand...
Click to collapse
Thanks! I will give it a try this morning after some coffee. I learned a cool trick last night to get my hotspot to work un-rooted, so I am less desperate than I was last night.
Carm
freebordjunky said:
when i booted in to twrp it was encrypted! but i didnt have a PW.... so for everyone to whom that happens, boot up normally and disable your pin ! then you can see your storage in twrp!
i almost flipped this morning hahahaha
Click to expand...
Click to collapse
Just enter your PIN at the TWRP prompt and it will work.
Mrnicgeuy633 said:
I got twrp up and running on my Pixel 3, but when try to install magisk 17.3 via twrp it says it completes but just bootloops. And I have to restore again. How did you go about it?
Click to expand...
Click to collapse
I have a similar problem. After installing twrp, I can boot to the OS, but Magisk isn't installed and I don't have root. After going back to Twrp and flashing the magisk zip, i can't get past the bootloader screen with a error saying something about failed to load boot.img.
Re-fastboot flashing the patched boot img to both slots brings me back to a rooted state with all magisk modules loaded and applied, but no more twrp. I technically don't need twrp for anything except for nandroid backups, but I guess i could just backup using the adb backup commands and get similar results, right?
Either way, I'm open to suggestions for how to get twrp and magisk working at the same time.
Hello,
Since MIUI 10.3.1.0 (PEIMIXM) was launched, I tried to update my device. After the update, when the smartphone rebooted it kept stuck in Mi logo sreen (Android loading wasn't also appearing). I tried to use MiFlash to reflash the ROM and the same happended.
Thinking it was a random problem of MIUI I decided to move to Pixel Experience because I had used it before and I liked. In the same day of MIUI 10.3.1.0 (PEIMIXM) launch, Pixel Experience also launched a new whyred version (in the beggining of June, i think).
I did what was needed to successfully install the ROM according to the dev's thread:
-I downloaded all the needed files (MIUI 10.3.1.0 PEIMIXM firmware, Pixel Experience ROM, recommended modified TWRP version of the developer);
-Initially, I installed TWRP via fastboot mode;
-I flashed the firmware;
-I wiped the partitions Cache Dalvik / ART, System, Cache, Data, vendor;
-I flashed Pixel Experience ROM;
-I wiped Internal Storage;
-I rebooted the device.
After those steps, I couldn't get access to my "homescreen". Basically, my phone stays stuck at the Mi logo screen. And nothing happens.
Considering it could be a recovery problem, I tried to use Pitch Black Recovery (the latest version available for whyred) that supports Oreo and Pie. I used TWRP to flash this one, and after that I made all the steps above again and the same happened.
I'm now only available to flash MIUI (if it is Android 8.1). I can only flash Pixel experience versions that were released before the MIUI Pie stable for this device.
I really appreciate if you could help me!
Hi,
Copy:
- the full name of the firmware file you used
-The full name of the rom file you use
-The full name of the recovery file you use/intend to use.
The name and version of current recovery installed.
Cheers,
htchd2sucks said:
Hi,
Copy:
- the full name of the firmware file you used
-The full name of the rom file you use
-The full name of the recovery file you use/intend to use.
The name and version of current recovery installed.
Cheers,
Click to expand...
Click to collapse
Firmware file: fw_whyred_miui_HMNote5Global_V10.3.1.0.PEIMIXM_d4d2c9f2aa_9.0
ROM: PixelExperience_caf_whyred-9.0-20190709-1819-OFFICIAL
Recovery I wanna use: PitchBlack-whyred-2.9.0-20190501-1030-OFFICIAL
Recovery I have installed to install the previous one: twrp-3.3.1-0-whyred.img
floater3 said:
Firmware file: fw_whyred_miui_HMNote5Global_V10.3.1.0.PEIMIXM_d4d2c9f2aa_9.0
ROM: PixelExperience_caf_whyred-9.0-20190709-1819-OFFICIAL
Recovery I wanna use: PitchBlack-whyred-2.9.0-20190501-1030-OFFICIAL
Recovery I have installed to install the previous one: twrp-3.3.1-0-whyred.img
Click to expand...
Click to collapse
You have a problem because of the firmware (likely).
The order was supposed to be something like this, from an OREO recovery and OREO FW:
In the recovery flash Pie firmware MIUI V10.3.1.0.PEIMIXM first and hit reboot to recovery. (so that firmware is really updated)
Now flash latest PIE rom (PixelExperience_whyred-9.0-20190604-1615-OFFICIAL.zip at time of writing). Do not reboot
Flash OrangeFox-R9.0-2-whyred-MIUI-Pie.zip. It will automatically reboot into recovery again.
I would:
-Flash the orange fox recovery from here (OrangeFox-R10.0_1-Stable-whyred.zip):
https://forum.xda-developers.com/re...ment/twrp-orangefox-recovery-project-t3837547
It's supposed to support both oreo and pie. It should reboot in recovery again after flashing.
-Flash the FW (fw_whyred_miui_HMNote5Global_V10.3.1.0.PEIMIXM_d4d 2c9f2aa_9.0.zip), hit reboot to recovery
-Flash your PixelExperience_caf_whyred-9.0-20190709-1819-OFFICIAL.
Reboot into system and check.
If not, I would try reflashing the recovery with a proper OREO firmware and then
In the recovery flash Pie firmware MIUI V10.3.1.0.PEIMIXM first and hit reboot to recovery. (so that firmware is really updated)
Now flash latest PIE rom. Do not reboot
Flash Flash OrangeFox-R9.0-2-whyred-MIUI-Pie.zip (pie) or V10 which is supposed to be oreo/pie. It will automatically reboot into recovery again.
Based on whatever mess it is now, you might have to do some wipes, try first the above then report.
htchd2sucks said:
You have a problem because of the firmware (likely).
The order was supposed to be something like this, from an OREO recovery and OREO FW:
In the recovery flash Pie firmware MIUI V10.3.1.0.PEIMIXM first and hit reboot to recovery. (so that firmware is really updated)
Now flash latest PIE rom (PixelExperience_whyred-9.0-20190604-1615-OFFICIAL.zip at time of writing). Do not reboot
Flash OrangeFox-R9.0-2-whyred-MIUI-Pie.zip. It will automatically reboot into recovery again.
I would:
-Flash the orange fox recovery from here (OrangeFox-R10.0_1-Stable-whyred.zip):
https://forum.xda-developers.com/re...ment/twrp-orangefox-recovery-project-t3837547
It's supposed to support both oreo and pie. It should reboot in recovery again after flashing.
-Flash the FW (fw_whyred_miui_HMNote5Global_V10.3.1.0.PEIMIXM_d4d 2c9f2aa_9.0.zip), hit reboot to recovery
-Flash your PixelExperience_caf_whyred-9.0-20190709-1819-OFFICIAL.
Reboot into system and check.
If not, I would try reflashing the recovery with a proper OREO firmware and then
In the recovery flash Pie firmware MIUI V10.3.1.0.PEIMIXM first and hit reboot to recovery. (so that firmware is really updated)
Now flash latest PIE rom. Do not reboot
Flash Flash OrangeFox-R9.0-2-whyred-MIUI-Pie.zip (pie) or V10 which is supposed to be oreo/pie. It will automatically reboot into recovery again.
Based on whatever mess it is now, you might have to do some wipes, try first the above then report.
Click to expand...
Click to collapse
Hummm. it's happening a suspect thing! I made all the steps above, and I'm now flashing the ROM itself, and recovery is stuck at "Unpacking the original boot image".
floater3 said:
Hummm. it's happening a suspect thing! I made all the steps above, and I'm now flashing the ROM itself, and recovery is stuck at "Unpacking the original boot image".
Click to expand...
Click to collapse
Wait a bit maybe.
Just to make sure, verify the checksum of your downloaded files or redownload them again and compare the size. Just to be sure you have the proper files and they are completed.
htchd2sucks said:
Wait a bit maybe.
Just to make sure, verify the checksum of your downloaded files or redownload them again and compare the size. Just to be sure you have the proper files and they are completed.
Click to expand...
Click to collapse
It's everything right with files.
I'm still waiting... And it's strange because it's stuck on "Unpacking boot image" and the problem I was facing was associated with booting the system.
floater3 said:
It's everything right with files.
I'm still waiting... And it's strange because it's stuck on "Unpacking boot image" and the problem I was facing was associated with booting the system.
Click to expand...
Click to collapse
Can you check /tmp/recovery.log? ideally copying that in a pastebin.
We should look into doing the proper cleaning from recovery as well, (wipe, advanced wipes).
Do you have any data to save or can you clean flash all without problem?
htchd2sucks said:
Can you check /tmp/recovery.log? ideally copying that in a pastebin.
We should look into doing the proper cleaning from recovery as well, (wipe, advanced wipes).
Do you have any data to save or can you clean flash all without problem?
Click to expand...
Click to collapse
I can flash all. The need files are on the SD card. How do I check /tmp/recovery.log?
floater3 said:
I can flash all. The need files are on the SD card. How do I check /tmp/recovery.log?
Click to expand...
Click to collapse
You're supposed to adb pull /tmp/recovery.log.
Might not be needed, if you can simply do a wipe/advanced wipe, and a format of /data.
Note: it might not be necessary and you will delete things, it's just " the fastest way".
then you have to go through the flashing, again, I would even redo the fw as described earlier.
htchd2sucks said:
You're supposed to adb pull /tmp/recovery.log.
Might not be needed, if you can simply do a wipe/advanced wipe, and a format of /data.
Note: it might not be necessary and you will delete things, it's just " the fastest way".
then you have to go through the flashing, again, I would even redo the fw as described earlier.
Click to expand...
Click to collapse
I could flash the ROM but, still in bootloop... But it's curious! If I let my smartphone turned off for 10-15 minutes and then turn it on, Pixel Experience works and boots successfully but after some minutes of using, starts crashing, and reboots, again in bootloop
floater3 said:
I could flash the ROM but, still in bootloop... But it's curious! If I let my smartphone turned off for 10-15 minutes and then turn it on, Pixel Experience works and boots successfully but after some minutes of using, starts crashing, and reboots, again in bootloop
Click to expand...
Click to collapse
Hm it is indeed strange, as if something is corrupted...
What's the status now?
Any changes?
htchd2sucks said:
Hm it is indeed strange, as if something is corrupted...
What's the status now?
Any changes?
Click to expand...
Click to collapse
Still the same.... I tried again, with other recoveries.... Always the same thing! Bootloop.
But if I let it turned off for some time I can boot it (but after some minutes it automatically restarts and gets in bootloop again )
floater3 said:
Still the same.... I tried again, with other recoveries.... Always the same thing! Bootloop.
But if I let it turned off for some time I can boot it (but after some minutes it automatically restarts and gets in bootloop again )
Click to expand...
Click to collapse
It's clearly not related to recovery, at least, not directly.
-Check what "wipes" you have done, and ideally do all of them + format data (you can always reencrypt later). Then, reboot, and redo the flashing of everything.
-Another option would be to flash with "miflash" which I think will also restore some boot things. In that scenario, you are on your own because I don't know about ARB in your case and all potential issues.
I can only say that I did a "miflash" when I used to have ARBv3, and it went fine (I had to redo the recovery, etc... after).
Already opened an issue on GitHub but looks like the dev got a long backlog. If anyone has a fix I'd really appreciate it.
I experienced the following when updating TWRP to 3.5.0_90:
- long loading time: takes ~20s to finish initialization
- when I deal with anything that supposedly work with the /system partition the device will freeze and shutdown. Tried: wipe system+data; flash magisk; flash gapps. Somehow dirty flashing a rom worked just fine (manipulating /data is fine I guess?)
Tried reversing to 3.4.0 and won't be able to properly mount existing partitions. Guess I should just wait for a fix. For those who look to update - proceed with caution!
bloomfielderic said:
Already opened an issue on GitHub but looks like the dev got a long backlog. If anyone has a fix I'd really appreciate it.
I experienced the following when updating TWRP to 3.5.0_90:
- long loading time: takes ~20s to finish initialization
- when I deal with anything that supposedly work with the /system partition the device will freeze and shutdown. Tried: wipe system+data; flash magisk; flash gapps. Somehow dirty flashing a rom worked just fine (manipulating /data is fine I guess?)
Tried reversing to 3.4.0 and won't be able to properly mount existing partitions. Guess I should just wait for a fix. For those who look to update - proceed with caution!
Click to expand...
Click to collapse
Only install twrp-3.5.0_90. It does not work! twrp-3.4.0-0-clover. The same is true. Only twrp-3.3.1-0-clover can be returned
agreed... v3.5.0-9 just boot to black screen recovery... this is a bug...
v3.4.0 need to format data to be able to read it properly.... this is not bug...
I installed latest twrp on mi pad 4 and now it gets stuck on the twrp logo screen also i cannot boot my system just keeps going to the twrp screen ive tried installing different recoveries but same issue just gets stuck on recovery logo screen is there a fix for this ?
bloomfielderic said:
Already opened an issue on GitHub but looks like the dev got a long backlog. If anyone has a fix I'd really appreciate it.
I experienced the following when updating TWRP to 3.5.0_90:
- long loading time: takes ~20s to finish initialization
- when I deal with anything that supposedly work with the /system partition the device will freeze and shutdown. Tried: wipe system+data; flash magisk; flash gapps. Somehow dirty flashing a rom worked just fine (manipulating /data is fine I guess?)
Click to expand...
Click to collapse
Can confirm, just experienced the same with v3.5.1_9-0 coming from v3.3.1. And when I tried to proceed flashing RR, was dumped into shutdown and then fastboot.
Used fastboot to re-flash recovery and upon issuing 'fastboot reboot recovery' was again dumped into shutdown (and then back to fastboot).
UPDATE: tried flashing different TWRP versions (the ones linked in the LineageOS 17.1 and crDroid threads, plus an old Mokee I had on file) without success. Fastboot doesn't throw any errors, but the copying phase appears to me overly fast and upon reboot all it does is go back to fastboot. Well, the device is soft-bricked as it is, looks like I'll have to try the MiFlash route.
UPDATE2: I did use MiFlash succesfully and am now on LOS 17.1. OrangeFox (found here, as well as the TWRP linked in the LOS 17.1 thread) were the ones that worked for me in the end...