Device: Zenfone 2 ZE551ML (WW Z00A)
Current Firmware: UL-Z00A-WW-2.20.40.206-user
Bootloader version: unknown + unlocked
I've seen several tutorials about using fastboot to flash recovery back to normal, but nothing seems to be working for my device. For context, I played around with LineageOS and Mokee for a while until I decided to go back to stock firmware. I had TWRP working, so I just downloaded the original stock, formated all partitions with TWRP and reflashed UL-Z00A-WW-2.20.40.206.
That worked well, but I just realized I am unable to boot into recovery. Everytime I use adb reboot recovery, the device goes into a bootloop. The ASUS logo shows up, then recovery silently fails to load, and finally the phone reboots. This keeps going until I force the device to turn off and reboot into normal mode.
I can adb reboot bootloader and use fastboot to flash recovery images. I have tried several stock recoveries I found in the forum and blog posts. I also tried a recovery.img extracted from the official ASUS firmware package (UL-Z00A-WW-4.21.40.352-user). I also tried different versions of TWRP, most recent and one that was working on my device. No matter which one I flash, the device just won't reach recovery.
I am willing to flash the stock fimware back to the phone and recreate all partitions, if necessary... except I can't even do that because... well... I can't get into recovery!
Does anyone have any tips for a manual fastboot flash of the entire firmware? Can I somehow format and recreate this partition?
I'm thinking about improvising from the steps outlined here, but I just want to make sure I'm not missing anything.
Quick update: after house into the night, I found a way around it!
I eventually came across this post, which has links to a complete list of all Z00A firmwares in RAW format. So I could get a hold of the latest stock firmwares for Android L (2.x) and M (4.x).
Turns out, a RAW image is just a zip file. It's different in the sense that it contains several *.img files that compose the firmware in state ready to be flashed using tools like fastboot. Inside WW_ZE551ML_2.20.40.206_20170627.raw I found a recovery_sign.img, which I was able to flash and use successfully. Great! That recovered the original stock recovery.
After that, I was able to update my firwmare to Asus's latest android M. Strangely enough, I also reflashed TWRP after that and it also works again.
Hopefully, this can help any lost soul in the future.
Best regards to all!
Hello, My Zenfone 2 model Z00AD has stopped at recovery screen and can't get into TWRP. I have used fastboot flash recovery followed by fastboot boot for various img files including 9 of 12 TWRP image files available for this phone. I have tried the recovery file that you obtained from RAW files, but it did not work for my phone.
Any suggestions welcome!
Related
I was switching back to stock ROM from Resurrection Remix M on my ZE550ML because I wanted to update the firmware so that I can install Cyanogenmod 14.1. After I downloaded the firmware zip file from Asus, I copied the recovery.img, boot.img, and droidboot.img files. I rebooted my phone into the bootloader and flashed each file using fastboot flash. After this was done, I rebooted into recovery, but it never got to that point. Now my phone's stuck on the Asus Logo screen. I tried the key combination to boot into bootloader or recovery, but that didn't work. Neither adb nor fastboot can detect my phone. I don't know what to do. I looked at tons of posts, but nothing can help me. Any ideas that can help are appreciated. I'm in a pickle right now.
Hello Everyone I am hoping there is a solution to this however I have been unable to find anything.
I flashed the latest OTA image via sideload and everything was fine until I tried to install TWRP. When trying to install the latest TWRP I could find ( 3.1.0-0RC2 ) my phone would then boot loop. I tried this process several times and each time after installing my phone would boot loop for 10 minutes until I forced it into fastboot, fast booted the TWRP image, and finally sideload the OTA once again.
I have seen a couple threads which I believe indicate that May update changed/broke something with the bootloader but I will be honest I
haven't read into it much.
This is on a Google version of the device with the bootloader unlocked. (failed to mention that).
Thanks in advance.
Bijiont said:
Hello Everyone I am hoping there is a solution to this however I have been unable to find anything.
I flashed the latest OTA image via sideload and everything was fine until I tried to install TWRP. When trying to install the latest TWRP I could find ( 3.1.0-0RC2 ) my phone would then boot loop. I tried this process several times and each time after installing my phone would boot loop for 10 minutes until I forced it into fastboot, fast booted the TWRP image, and finally sideload the OTA once again.
I have seen a couple threads which I believe indicate that May update changed/broke something with the bootloader but I will be honest I
haven't read into it much.
This is on a Google version of the device with the bootloader unlocked. (failed to mention that).
Thanks in advance.
Click to expand...
Click to collapse
Please read the other Posts about this
Flash the bootloader from april.
****************************
Download last months 7.1.2 factory image.
Extract it and find "bootloader-marlin-xxxxblahblah.img".
Rename it to "bootloader.img" for simplicity's sake, then move it to the side.
:Flash-all" the latest factory image, after its done stay in fastboot.
Run "fastboot flash bootloader_a bootloader.img" from wherever you moved the file to
Disregard if "partition_a" isnt your primary, once the command is ran it will auto flash to the primary partition.
Boot and setup, reboot back to bootloader.
Boot and install twrp, then reboot to recovery.
Delete fstab.marlin in main directory, then flash preferred supersu (i use 2.79 sr3).
Reboot to system and your done. from here reboot to recovery or bootloader to flash your preferred kernel and mods.
Was able to get this all sorted out.
If anyone else happens to see this thread with the same issues and missed the April bootloader deal you can find a good overview Here
To get the April bootloader image which is something I have never loaded myself you need to download the Factory Image from April then extract it. Inside there you will see the bootloader image.
Hope this helps anyone else who didn't read far enough into this issue.
Hi, I flashed the FOTA Kernel with TWRP 2.8.7 onto my phone and inside TWRP I flashed the recovery with the 3.0.2 TWRP image (telling me "Successfully flashed")
But after rebooting I still have TWRP 2.8.7
Using windows command line and "fastboot flash recovery "TWRP.....img" I get this "FAILED" message.
What am I doing wrong?
I even flashed the phone back to stock and then followed these instructions but same result.
Is my phone broken or sth?
Hi H4NNE5, the Xperia M does not have a recovery partition. The TWRP recovery is included in the boot partition when flashing the kernel. Try to upgrade with the TWRP-Manager if your phone is rooted.
Hi Lightningsfire, Thanks for you answer.
Ok, that's weird because I read a lot of threads but none said anything like that. I'm more confused right now.
Anyhow the LineageOS is not properly working on my phone anyhow so I set it back to Stock Rom and check back in a few months if it improved
One more question:
So if I flash the whole software package the boot partition is overwritten then, right? Because I noticed that the Recovery was a different one, after I flashed the system.
H4NNE5 said:
Hi Lightningsfire, Thanks for you answer.
Ok, that's weird because I read a lot of threads but none said anything like that. I'm more confused right now.
Anyhow the LineageOS is not properly working on my phone anyhow so I set it back to Stock Rom and check back in a few months if it improved
One more question:
So if I flash the whole software package the boot partition is overwritten then, right? Because I noticed that the Recovery was a different one, after I flashed the system.
Click to expand...
Click to collapse
Try this command
fastboot flash boot twrp_name.img
Hi all I have been tinkering away and destrying my setup left right and centre to sort this process out but if you're unable to run the latest TWRP for your note from Ian and get stuck at SAMSUNG screen on boot then this process will fix that if followed correctly. This is due to the device's roll back protection.
This process will reset everything back to current date and get everything working on the new Oneui 2.1 base
Process for getting round SAMSUNG screen issue - please read through first and get the files you need before starting. I did this on my N976B but in theory it should work for other 10-range devices, notes indeed!
UNLESS YOUR RUNNING CRUEL KERNEL OR A SPIN OFF, YOU'LL NEED VOL UP AND POWER TO ACTIVATE MAGISK ON EACH BOOT
Needed:
Stock firnware
Magisk app
Twrp image
Pc and odin also patience and a brain lol
-Return to stock by flashing AP/BL/CP&CSC in odin
-Reboot and confirm oem unlocking greyed out, install magisk app and patch twrp image from Ian, also patch your ap file.
-reboot to download, meanwhile get the magisk_patched.tar and insert TWRP renamed as recovery.img in place of the stock patched recovery (keep this one for later)
-In download mode and with auto reboot off in odin, flash BL, Magisk_patched.tar(with the TWRP from Ian in), CP & HOMECSC.
-When flashing is complete exit download mode and immediately hold power and vol up and hold until on TWRP slider screen. swipe to allow modifications, format internal storage and flash multidisabler.
-Reboot TWRP and backup your current patched stock rom. FLASH THE STOCK PATCHED RECOVERY YOU SAVED EARLIER AND THEN FLASH MULTIDISABLER (THIS IS IMPORTANT AS YOU WILL THEN BE ABLE TO INSTALL TWRP VIA THE APP WITHOUT HAVING TO REFORMAT INTERNAL)
-Reboot straight to stock recovery (reboot from TWRP and hold Vol up and power until in stock recovery) and factory reset then reboot.
-You should now boot up as normal, setup your device, in particular have TWRP app and Magisk set up and running.
-Flash the Unpatched TWRP for your device in the TWRP app - reboot TWRP and check the box to kill that annoying swipe to allow modifications and then you are good to flash whatever rom or kernel you want for your device!
Flash the stock patch recovery as boot??
orbital_71 said:
Flash the stock patch recovery as boot??
Click to expand...
Click to collapse
yes then immediately flash multidisabler before you reboot to set up
i have just helped someone through this on TG so it defo works :good::good::good:
It can also confirm this is working. Just followed this guide on my Note 10+ (N975F with CTD1) and happy flashing now.
drexxie1962 said:
It can also confirm this is working. Just followed this guide on my Note 10+ and happy flashing now.
Click to expand...
Click to collapse
Excellent, thanks for testing!!!!!!!
@askmydas
you may find this useful - follow this to get your sec date reset then follow the process spelt out in the thread of the rom you want to use as you may need a different TWRP depending on what sec date the chef of your chosen rom uses.
Hey, when I get to " FLASH THE STOCK PATCHED RECOVERY YOU SAVED EARLIER" I try to do this and it tells me I don't have enough space. Any ideas?
KiwiNote+ said:
Hey, when I get to " FLASH THE STOCK PATCHED RECOVERY YOU SAVED EARLIER" I try to do this and it tells me I don't have enough space. Any ideas?
Click to expand...
Click to collapse
I worked it out, I was trying to install "recovery.img" to boot partition, "recovery.img" needs to be installed to RECOVERY partition. Silly me. Fixed it now, but have a new issue:
After I flash unpatched twrp image through the app, now my phone will only boot into TWRP. I don't even boot with recovery button presses, but it will still boot into TWRP only. Any ideas?
I know this is an old thread, but it may be that my solution could help someone who is locked on the outside of the device (softbrick)
TD,DR: If you have softbrick and you can't boot the device at all, try flashing via Odin the BL, CP, CSC from a stock rom and the AP of another completely different stock rom.
I had an IMEI 0000 issue on my Galaxy Note 8 (SM-N950F), using Hades Rom (custom), and I needed to install the stock rom. As I was on the F(15) binary, there were only two roms (SamMobile and Stockrom.net) available for my country (Brazil) with this binary:
N950FXXUFDUD6_N950FOXMFDUD6_ZTO
stockrom.net_N950FXXUFDUG5_N950FOXMFDUG4_ZTO
And a via Frija:
SM-N950F_1_20210717024140_0wmgsx8iwf_fac
And no Combination Rom for that binary
After flashing these roms several times, I was always stuck on the “Powered by Google” screen, even doing cache wipe and factory reset through stock recovery several times. So I flashed the N950FOXMFDUD6, flashed the CF-Auto-Root and was able to boot the device. Once inside I noticed that it didn't solve the problem of IMEI 0000. I tried a few more procedures, ended up restarting to install TWRP, and the OEM is closed!!! (OEM OFF, Prenormal). I start getting the message “only official binaries are allowed to be flashed(recovery)”. I flash the stock rom, but it gets stuck on “Powered by Google” again. I tryed to install CF-Auto-Root and I get the message “only official binaries…” I can't log into the device anymore. So after four days of desperation, trying every technique possible, trying to create the Combination Rom by unzipping the AP file from the stock Rom and modifying the files inside, without success, I finally try a procedure I haven't seen anywhere else: I go to the modified Odin: Odin3_v3.14.1_3B_PatcheD, I selected the BL, CP, CSC files from the N950FOXMFDUD6 rom and the AP file from the rom SM-N950F_1_20210717024140_0wmgsx8iwf_fac
And it worked! I can boot the device
Hello, the names Braadliiah,
I am having excessive difficulty figuring out how to flash any Rom that is beyond Kitkat, even though they, supposedly are "designed" for an "SM-T217s". As I had success flashing Cyanogen mod[cm-12.1-20160706-UNOFFICIAL-lt02ltespr], which is not even for my model of tablet, which is bizarre due to the fact that other ROM's of the same model do not successfully flash. The most recent custom Rom I had attempted to install with no avail, was the Ressurection Remix[[ROM][8.1.0]ResurrectionRemix v6.2.1[Official]]. This ROM was linked into google, under "SM-T217s" compatibility, but for the model "It02ltespr".
The way that I flash these ROM's are through TWRP, namely, version "2.7.0.0". The TWRP dialogue within the flash window, usually says something like, "failed to zip" and "Zip error". The reason I have not done the flashing via ADB & Fastboot is because I have not done this successfully yet, and truth be told, I am not sure it is even possible given the TWRP can't do it? Also, I do not use Odin, because this will remove TWRP, and there is no guaranty that the ROM will work, and then, I will have to re-install Stock Firmware and TWRP. I lack any desire doing double the work, as I have already done a bit of that through trial and error recently.
So is there any method, via TWRP, ADB, or ODIN, which will in fact work? Should I install another version of say, Cyanogenmod, to be able to install this ROM? I am looking for experienced, tech savvy people, as I am a curious noob, who wants a ressurected tablet that can do all modern conveniences via wifi, and be my study tab. Furthermore, I would like, say, Magisk Manager to Install Modules, but can not do so, without a newer Kernel, that is Lolipop and forward. And again, Lolipop and forward do not seem to Install.
I shall be ever greatful for anybody's help. Thank you. :angel:
Update:
Today I experimented with ODIN some more. I had a small victory, because I happened to take the TWRP v.3.1 flash Image, and converted him into a TAR file, and luckily ODIN managed to successfully install this update. However, when it came to TWRP v.3.2, there became an error installing. TWRP still failed to instal zip files from the below ROMs. Furthermore, ODIN seemed to flash the boot images of Custom ROMs well, when converted to TAR files. Yet, when I booted the ROM, this device remained on the Boot screen.
My process by which I installed these ROMs, went like so:
First, extract zip, then convert to TAR via 7zip
Open ODIN, flash TAR in PDA, Boot down android
Boot to Download Mode again, in PDA flash TWRP v3.1 TAR, Boot down android
Boot to Custom recovery, and install proper Gapps
Boot on, and Stuck.
I did this three times, while starting off with a full wipe, to rule some things out. When I tried to fix context, it said Error1
The Roms I attempted to flash were, Cyanogenmod 12, which worked entirely; Cyanogenmod 13 which was stuck on Boot screen, tried twice; Lineage OS 15, which I tried three times, and was stuck on Boot screen.
Do I need to apply more than one file? for instance, CSC, Phone, and PDA? Because I was only flashing boot Image as a TAR file in PDA.