The backstory: I have no experience with rooting and or flashing custom ROMs. Prior to today my ze551ml was completely stock, running on the official android M update. I had a need to do a factory reset, but the phone would simply reboot. I assumed this was a problem with the update so I download and attempted to install the downgrade to l. Naturally it crashed mid downgrade and I thought it to be bricked. So, I started Googling and realized I was able to get into fastboot mode, but not recovery. Following a guide I located I attempted to flash the preroot ROM located at the link below:
http://forum.xda-developers.com/zenfone2/development/rom-pre-root-img-t3079590
Well, it appeared to have worked, but now the phone refused to boot at all after being turned off. So, more Googling and I proceeded to follow the full unbricking guide below:
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Partway through step 1.3 the phone restarted itself and booted right up into Android L! Success I thought to myself, but it was not to be. I proceeded to download the FOTA L update and it downloaded fine, but when I clicked to install it simply rebooted the phone. Tried a couple of other times with the same result. I realized that Supersu was installed so I did the full unroot assuming that was the problem, but to no avail. It appears that the updates can't install because the phone is incapable of entering fastboot or recover mode. Anytime I attempt to enter fastboot via hard key or through adb the phone hangs on the ASUS logo. Adb detects the phone when it's connected via USB, but of course fastboot can't because I can't get it into fastboot mode at all.
Any tips on how to get fastboot operational again so I can start applying updates again? Every guide I've located has started with "boot into fastboot/recovery" which simply isn't an option. Any help is appreciated.
Edit: Well, I think I've reached the end of the internet trying to google for a solution. The phone works, but it looks like it's stuck on build 2.13.40.13 until the end of its life. If anybody has any ideas I'm still hoping for a solution, but I can't find anything describing how to restore fastboot if the OS is intact.
kidnova said:
The backstory: I have no experience with rooting and or flashing custom ROMs. Prior to today my ze551ml was completely stock, running on the official android M update. I had a need to do a factory reset, but the phone would simply reboot. I assumed this was a problem with the update so I download and attempted to install the downgrade to l. Naturally it crashed mid downgrade and I thought it to be bricked. So, I started Googling and realized I was able to get into fastboot mode, but not recovery. Following a guide I located I attempted to flash the preroot ROM located at the link below:
http://forum.xda-developers.com/zenfone2/development/rom-pre-root-img-t3079590
Well, it appeared to have worked, but now the phone refused to boot at all after being turned off. So, more Googling and I proceeded to follow the full unbricking guide below:
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Partway through step 1.3 the phone restarted itself and booted right up into Android L! Success I thought to myself, but it was not to be. I proceeded to download the FOTA L update and it downloaded fine, but when I clicked to install it simply rebooted the phone. Tried a couple of other times with the same result. I realized that Supersu was installed so I did the full unroot assuming that was the problem, but to no avail. It appears that the updates can't install because the phone is incapable of entering fastboot or recover mode. Anytime I attempt to enter fastboot via hard key or through adb the phone hangs on the ASUS logo. Adb detects the phone when it's connected via USB, but of course fastboot can't because I can't get it into fastboot mode at all.
Any tips on how to get fastboot operational again so I can start applying updates again? Every guide I've located has started with "boot into fastboot/recovery" which simply isn't an option. Any help is appreciated.
Edit: Well, I think I've reached the end of the internet trying to google for a solution. The phone works, but it looks like it's stuck on build 2.13.40.13 until the end of its life. If anybody has any ideas I'm still hoping for a solution, but I can't find anything describing how to restore fastboot if the OS is intact.
Click to expand...
Click to collapse
You have to use full unbrick method(xfstk + raw) to restore ur device fully
xfstk will restore ur fastboot image
yakub234go said:
You have to use full unbrick method(xfstk + raw) to restore ur device fully
xfstk will restore ur fastboot image
Click to expand...
Click to collapse
Thanks for the response. I've tried this a dozen times, but unfortunately (this is going to sound weird) since it's not completely bricked it is only detected as Moorefield for a few seconds when started. This allows the xfstk tool to detect it and begin the download, but not long enough to complete the process so it times out. The only development access I have to the phone now is via adb, but since I don't have root I'm very limited in what I can do via command line. Since I can't access fastboot I can't achieve root. It's just a comedy of errors now.
kidnova said:
The backstory: I have no experience with rooting and or flashing custom ROMs. Prior to today my ze551ml was completely stock, running on the official android M update. I had a need to do a factory reset, but the phone would simply reboot. I assumed this was a problem with the update so I download and attempted to install the downgrade to l. Naturally it crashed mid downgrade and I thought it to be bricked. So, I started Googling and realized I was able to get into fastboot mode, but not recovery. Following a guide I located I attempted to flash the preroot ROM located at the link below:
http://forum.xda-developers.com/zenfone2/development/rom-pre-root-img-t3079590
Well, it appeared to have worked, but now the phone refused to boot at all after being turned off. So, more Googling and I proceeded to follow the full unbricking guide below:
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Partway through step 1.3 the phone restarted itself and booted right up into Android L! Success I thought to myself, but it was not to be. I proceeded to download the FOTA L update and it downloaded fine, but when I clicked to install it simply rebooted the phone. Tried a couple of other times with the same result. I realized that Supersu was installed so I did the full unroot assuming that was the problem, but to no avail. It appears that the updates can't install because the phone is incapable of entering fastboot or recover mode. Anytime I attempt to enter fastboot via hard key or through adb the phone hangs on the ASUS logo. Adb detects the phone when it's connected via USB, but of course fastboot can't because I can't get it into fastboot mode at all.
Any tips on how to get fastboot operational again so I can start applying updates again? Every guide I've located has started with "boot into fastboot/recovery" which simply isn't an option. Any help is appreciated.
Edit: Well, I think I've reached the end of the internet trying to google for a solution. The phone works, but it looks like it's stuck on build 2.13.40.13 until the end of its life. If anybody has any ideas I'm still hoping for a solution, but I can't find anything describing how to restore fastboot if the OS is intact.
Click to expand...
Click to collapse
seems like you did not install droidboot.bin correctly... only way is use xFSTK again.i have updated the link to latest raw firmware 2.20.40.194 and use the same guide and commands..
sukhwant717 said:
seems like you did not install droidboot.bin correctly... only way is use xFSTK again.i have updated the link to latest raw firmware 2.20.40.194 and use the same guide and commands..
Click to expand...
Click to collapse
The problem is that it's only recognized as Moorefield for a few seconds which isn't enough time for xFSTK to complete the install. Do you know of a way to force the device to stay connected as Moorefield?
kidnova said:
The problem is that it's only recognized as Moorefield for a few seconds which isn't enough time for xFSTK to complete the install. Do you know of a way to force the device to stay connected as Moorefield?
Click to expand...
Click to collapse
Plug the phone to the PC, be sure the phone is completely off and then hold power + vol- for a few seconds. You must see the "Moorefield" driver permanent in the device manager.
Btw... I got the same problem (four lines, not bootloader, not OS; xFSTK FW+OS failed) and I'm stuck in this step :/
mrperalta said:
Plug the phone to the PC, be sure the phone is completely off and then hold power + vol- for a few seconds. You must see the "Moorefield" driver permanent in the device manager.
Btw... I got the same problem (four lines, not bootloader, not OS; xFSTK FW+OS failed) and I'm stuck in this step :/
Click to expand...
Click to collapse
I've tried this many times, but it only shows Moorefield for a few seconds. I'm assuming this is because it has a fully operational OS so it doesn't stay in the generic USB device mode.
EDIT: I misread your original post. Holding power and volume DOWN does keep connect it in Moorefield. Thanks so much for that. The problem now is that once xFSTK gets to downloading the OS it reboots the phone which takes it out of USB mode and disconnects the tool. I'm still stuck where I was before, but that's a little progress. Any other thoughts?
New update. I'm able to get to the point of loading the OS from xFSTK by skipping the FW part, however it continuously fails. My assumption is because it can't overwrite the existing OS. Any other ideas?
kidnova said:
New update. I'm able to get to the point of loading the OS from xFSTK by skipping the FW part, however it continuously fails. My assumption is because it can't overwrite the existing OS. Any other ideas?
Click to expand...
Click to collapse
Kidnova, reading this post I could fixed my problem. The "issue" was in the xFSTK where you put the flag (0x800000807). A guy on the threat said to put "0x80000807" instead of "0x800000807" (note that there is "0" from difference).
"those who are not able to keep device connected. take care of few steps
1. in xFSTK option menu change the flag override value to 0x80000807 not 0x800000807 ( don't forget to click gp value over ride)
2. while connecting to xFSTK attach usb to computer. hold power button for 20 seconds to make sure it power downs completely. then hold the power button down and click power button. wait till device vibrate or computer makes detection sound. leave power button but keep holding the volume button for few seconds"
Click to expand...
Click to collapse
-sukhwant717
mrperalta said:
Kidnova, reading this post I could fixed my problem. The "issue" was in the xFSTK where you put the flag (0x800000807). A guy on the threat said to put "0x80000807" instead of "0x800000807" (note that there is "0" from difference).
-sukhwant717
Click to expand...
Click to collapse
You guys are lifesavers! I've got fast boot again. Now to see if I can continue without screwing it up.
FINAL EDIT: I have a 100% functional stock Zenfone 2. Thanks everybody for your help.
kidnova said:
You guys are lifesavers! I've got fast boot again. Now to see if I can continue without screwing it up.
FINAL EDIT: I have a 100% functional stock Zenfone 2. Thanks everybody for your help.
Click to expand...
Click to collapse
Hi, got the same issues, I've read many posts. Tried all of the million options. What was your final way of doing it, do you remember?
Hello
I tried rooting my LG H815 and it didn't go so well.
I managed to successfully unlock the bootloader following the steps on the LG developer website.
I downloaded SuperSu (UPDATE-SuperSU-v2.46.zip) and placed it in the internal storage of the phone.
Afterwards in order to root the device, I booted into TWRP with "fastboot boot twrp-3.0.2-1-h815.img".
In TWRP I flashed SuperSu. After it finished flashing I rebooted the device. After it attempted to start up again, it froze at the LG logo. I waited around 10 minutes and figured it's not successfully boot.
I removed the battery and tried to fire it up again, but it didn't get past the Logo screen again.
I managed to send "adb reboot recovery" to it, but all I get is an image of a little dead android. I guess this is because I only booted TWRP and did not flash it.
When I get it in fastboot mode, "fastboot boot twrp-3.0.2-1-h815.img" does work anymore now. I just says < waiting for any device >.
I managed to get into default recovery with power up + vol down where it prompted me to do a reset by responding Yes twice, but after it rebooted, it still got stuck on Lg logo.
If you cannot get to the recovery then follow these steps:
i) Make sure you have the LG Drivers installed from here: http://oceanhost.eu/e4h2px4e0hkd/LGMobileDriver_WHQL_Ver_4.0.4.exe.htm
ii) Download the LG Bridge software from here: http://www.lg.com/us/support/product-help/CT10000025-1438110404543-preinstall-apps
iii) Remove the battery and reinsert it so the device it is fully off.
iv) While holding the up volume button, insert your USB cable.
v) You should enter download mode. Go to the Software Update tab of the LG Bridge. It will say connecting and then should say your device is up to date. Click on the recovery text on the bottom right and then follow the instructions. The software will download the system image for you and this is roughly 1.6GB so make sure your firewall doesn't block this connection.
This shouldn't delete your data (no guarantees) but you will have to grant app permissions again and reapply any changes to system files e.g. root, viper4android, xposed ect.
If you have problems try this method instead:
http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
If successful and you're brave enough to try again. Then make sure you actually flash TWRP. I think you are right in that you only booted TWRP .
You can follow my TWRP/root guide here: https://forum.xda-developers.com/g4/general/howto-complete-guide-to-unlock-twrp-t3370003
Good luck
Thanks a lot for answering.
LG Bridge wasn't detecting my device. I don't remember if I was in download mode when I tried this, though. I might've not been.
I didn't know how to fix it and asked a friend for help. He managed to flash the h815 stock firmware through some Taiwanese/Korean flash tool (Edit: It was LGUP and he flash a kdz file with the stock firmware).
I followed a similar guide to yours when I flashed SuperSU from TWRP, except I didn't install twrp permanently after booting it from the .img file. I thought it was not possible to install twrp if the device is not rooted first.
I still kinda want to root the device since I voided my warranty by unlocking the bootloader, but I'm afraid I'll break it again if I use the same method.
Edit: Managed to successfully flash twrp. Booted into recovery again after rebooting system. I am now creating and saving a full backup with TWRP. Will try flashing SU again afterwards.
Edit2: I flashed SU after properly installing TWRP and it worked like a charm.
i own an asus zenfone 2 Ze551ml. i had installed lineage os based on android 14.1 official nightly version using twrp recovery.
everything was running fine untill i wanted to update the nightly version.
the update manager would crash whenever i tried to download the update, so i tried downloading the update manually and flashing it using twrp recovery.
i successfully flashed the zip file, but the device went into a boot loop after the install of the update.
i booted back into recovery and tried clearing cache and dalvik cache, but nothing happened.
later while trying to do the same again, i accidentally wiped system partition as well.
now, the device doesnt boot up and stays stuck on the asus boot logo. doesnt show the lineage boot animation as well.
cant boot into recovery mode using the volume button and power button.
i tried to install adb on my windows, but the device is not detected and it shows an error saying device not found.
installing device drivers manually and trying to install adb too didn't help.
someone please help me with this situation :crying:
thanks a lot in advance
If you have hard bricked your phone then this post has all of the information necessary to help you
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
plus some addition information I found on the web:
I gathered from the internet that Asus Flash tool will hang after it reloads the correct serial number. It thinks it is communicating with a phone that has SN 123456789ABC but then at some point the phone switches SN and Asus Flash Tool hangs.
You can get around this hang using several methods
1) restart computer after asus flash tool hangs
2) use second computer to load RAW image after asus flash tool hangs
3) Going into Windows Device Manager and disabling the Android bootloader device then re-enabling it (after asus flash tool hangs)
Click to expand...
Click to collapse
You can tell Asus flash tool is hanging when you run "fastboot devices" command and you see a device that is not serial number 123456789ABC
Answered this problem many times.
You should've powered off within twrp itself.
Waited 15 seconds after switch off, used hard buttons to get to bootloader.
Used giovix modder tool. Return to stock option in modder. Select boot and recovery.
Reunlock bootloader , flashed twrp 3.0.2M1. Root .then flashed 3.0.3.M4 or if possible ...
Power off in twrp itself
Used hard buttons to get to bootloader.
Reflashed new twrp in linos OP.
Reflashed linos or restored any back up
3.03.M4 twrp is in OP for lineage
Search related threads
Twrp bootloop
Phone keeps booting to twrp
I was working around to flash resurrection remix from android 5.0 stock rom.... I upgrade ifwi before unlocking bootloader which prevents me from flashing twrp. So i downgrade ifwi. And after that i was trying to flash with xfstk where my problem actually begins...while flashing it completed fw and says continuing to OS... But in between my zenfone 2 ze551ml (z00ad) booted up without splashscreen... It shows a screen with colored grains and then boots normally following boot animation... Now the strange thing is i cant reboot to bootloader or recovery mode...i tried command methods but just normal boot only.... Phone is rooted. Adb is working fine but sideload not possible... Asus flashtool gives error... Serial number shows as 0123456789××××××× xfstk keeps showing error... Sometimes it complete fw flash and gets stuck with os image flash....
Someone pls help me to get back fastboot and so that i could reflash everything back to normal... :crying:
Please need urgent help. I had unlocked bootloader. While trying to update Magisk, my phone rebooted and got stuck on fastboot loop. Then while trying to flash TWRP using fastboot this "Your device is corrupted and cannot be trusted" error occured. I can't go into recovery, it just loops into this message. And my PC can't recognise the phone now at all. Please I need help. I have been trying to resolve this issue for hours now.
This is for Google Pixel 2 XL.
SonyXperiaSP said:
Please need urgent help. I had unlocked bootloader. While trying to update Magisk, my phone rebooted and got stuck on fastboot loop. Then while trying to flash TWRP using fastboot this "Your device is corrupted and cannot be trusted" error occured. I can't go into recovery, it just loops into this message. And my PC can't recognise the phone now at all. Please I need help. I have been trying to resolve this issue for hours now.
Click to expand...
Click to collapse
As long as you can get into the bootloader you're not dead in the water. Download the last factory image - NOT OTA image - from Google and flash it while in bootloader mode using ADB and Fastboot. That will return your device to its factory state. From there you can boot - NOT install - TWRP and install a custom ROM as well as root.
Strephon Alkhalikoi said:
As long as you can get into the bootloader you're not dead in the water. Download the last factory image - NOT OTA image - from Google and flash it while in bootloader mode using ADB and Fastboot. That will return your device to its factory state. From there you can boot - NOT install - TWRP and install a custom ROM as well as root.
Click to expand...
Click to collapse
First of all thank you for the reply. I don't know but I left the phone alone for couple of hours and right before seeing your post got into bootloader by pressing volume down and power key. Tried to flash TWRP and as soon as it flashed I got the exact same error like last time. I will now be following your method and install factory image. "NOT install - TWRP and Install a custom ROM", so I will not be installing TWRP this time.
I will post updates on what goes and hopefully will be able to flash the factory image without errors.
Thank you very much for the help Strephon. Really, really appreciate it. I am now able to boot into the OS and hopefully installing custom rom or rooting afterwards won't be an issue, Again, thank you very much.