Related
followed a tutorial (Cnncted's youtube clip - How to root the ASUS ZenFone 2 ) to root
Accidentally (very stupid) pressed the update option when an OTA update showed up yesterday (Jul 8 2015), and after that the phone won't start properly - stopped at in search of incredible...
No luck with trying to boot into recovery mode (power + volume up). It just vibrates once and the screen is black. Trying to flash recovery image with ADB and flashtool etc, but the MTP usb connection failed. If I connect it to the PC using the USB cable and then press the power button to turn it on (stuck in that ..."incredible" screen), device manager shows the Z200AD name with a yellow exclamation mark beside, and Asus ZenUI software will automatically start. But it's not really recognized by the PC.
So...if you have any suggestions for me to try, please let me know and that would be greatly appreciated!
Harry
p.s. This is a US version, so the it's the WW sku?
Same problem here. I have a rooted 551ML and on July 6th I received an OTA update. I installed it and I'm stuck in boot loop. I have hundreds of family pictures in the internal memory.
The good news is that I have access to boot loader and recovery.
I could not find any custom recovery for Zenfone 2. They are not out yet, right? Is there any way to copy the internal memory of the phone (that doesnt load the OS) to the SD card? Or to paste a file img.boot taken from a downloaded official rom and copy it over the corrupted one on the phone's memory?
If you can access the bootloader, you can do this:
http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
Btw, there is a custom recovery out there (TWRP, check the Development section), but you will need an unlocked bootloader to use it in your state (I think).
US version is the WW SKU btw. Hope this helps.
joel.maxuel said:
If you can access the bootloader, you can do this:
http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
Btw, there is a custom recovery out there (TWRP, check the Development section), but you will need an unlocked bootloader to use it in your state (I think).
US version is the WW SKU btw. Hope this helps.
Click to expand...
Click to collapse
Joel, thanks a lot! I will give it a try.
fingers and toes crossed...
I faced this problem too. All I did was to flash the boot.img of my version using fastboot,
Then I flashed the firmware, without factory reset I started the phone.
I was continiously getting an error "com.android.process has stopped". Ignoring that, I just backed up my whole data. Did a factory reset. Updated
Boom!! Everything was normal... I hope this helps
Just a quick update - followed the method in the link that Joel referred to, and everything worked beautifully. I did get two error messages like “the contact stopped working..." “The process android.process.acore has stopped working.” I fixed this problem by clearing the data/cache from the "contact" app, and that did the trick without a factory reset etc.
I unrooted the device using SuperSU. The fastboot screen, however, still shows a random serial number 0123456789ABCDEF. Is there a way to revert it back to the real one? I do see the real one from settings - about - status.
xxmmx said:
Joel, thanks a lot! I will give it a try.
fingers and toes crossed...
Click to expand...
Click to collapse
xxmmx said:
Just a quick update - followed the method in the link that Joel referred to, and everything worked beautifully. I did get two error messages like “the contact stopped working..." “The process android.process.acore has stopped working.” I fixed this problem by clearing the data/cache from the "contact" app, and that did the trick without a factory reset etc.
I unrooted the device using SuperSU. The fastboot screen, however, still shows a random serial number 0123456789ABCDEF. Is there a way to revert it back to the real one? I do see the real one from settings - about - status.
Click to expand...
Click to collapse
Isn't everyone serial number the same? mine is.
This is something that I am not sure of. Yours has been rooted as well?
I would like to know what the fastboot screen looks like before rooting.
GGL-Daz said:
Isn't everyone serial number the same? mine is.
Click to expand...
Click to collapse
xxmmx said:
This is something that I am not sure of. Yours has been rooted as well?
I would like to know what the fastboot screen looks like before rooting.
Click to expand...
Click to collapse
Pretty sure rooting didn't affect my fastboot screen at all.
actually i rooted my zenfone 2 and there was an OTA and i tried to install it without un-rooting my phone. the phone would not turn on and it gets stuck in the boot animation.
the phone wasn't detected by the ADB in my pc so i thought of installing some custom recovery, thought that could help.
i tried installing TWRP but i did not unlock the bootloader and now i am not able to enter in recovery mode either, everytime i try to get in the recovery modethe phone restarts and goes to fastboot mode.
please help.
dip_anker said:
actually i rooted my zenfone 2 and there was an OTA and i tried to install it without un-rooting my phone. the phone would not turn on and it gets stuck in the boot animation.
the phone wasn't detected by the ADB in my pc so i thought of installing some custom recovery, thought that could help.
i tried installing TWRP but i did not unlock the bootloader and now i am not able to enter in recovery mode either, everytime i try to get in the recovery modethe phone restarts and goes to fastboot mode.
please help.
Click to expand...
Click to collapse
I was having a similar issue where adb wouldn't recognize my phone but fastboot was detecting it. What I ended up doing was grabbing the latest stock firmware zip from asus, transferring it to my external sd card via adapter and renamed it to MOFD_SDUPDATE.zip. Then go into fastboot (restart with volume up key) and proceed to recovery. It should automatically update your system from there. The only bummer is having to re-configure everything.
5ifty1 said:
I was having a similar issue where adb wouldn't recognize my phone but fastboot was detecting it. What I ended up doing was grabbing the latest stock firmware zip from asus, transferring it to my external sd card via adapter and renamed it to MOFD_SDUPDATE.zip. Then go into fastboot (restart with volume up key) and proceed to recovery. It should automatically update your system from there. The only bummer is having to re-configure everything.
Click to expand...
Click to collapse
i tried it with prerooted as well as the stock rom, it did not work for me. isn't there any way to flash CM12.1 using the fastboot ?
Hello everyone, need a little help if possible .
The say curiosity killed the cat, well… it killed my phone. To be more precise I wanted to know if my 550ml (with unlocked bootloader and running cm12.1) could run a 551ml firmware so… I did install thru TWRP the superzen firmware and after that the screen turned black. Can’t see anything . Not even in fastbootmode, no logo, no nothing. If I turn it on and plug it to the pc it shows, I see the internal memory and the sdcard. It’s gotta be from the different resolution that 550 and 551 have but how do I change it since I can’t see anything?
I did a userdata reset thru fastboot, wiped cache , reinstalled stock recovery ,boot recovery, tried to install stock firmware, still no change. I even managed to enter stock recovery and did an adb sideload of the latest firmware from the asus site.
As for now the phone boots, the capacitive buttons respond, the led indicates that it charges, the pc sees it but no matter what I do the screen remains black. Most likely I’m on the setup wizard but like I said I don’t see anything.
So… What can I do now? To the Asus service with it or …?
I'm not much of a forum user so go easy on me. Thank you.
Not sure if it's going to make a difference but here is an idea, try sideloading a cm recovery and flash a cm rom and see what it does...
fastmix said:
Not sure if it's going to make a difference but here is an idea, try sideloading a cm recovery and flash a cm rom and see what it does...
Click to expand...
Click to collapse
Unfortunately it does not work, when i try to sideload a rom with twrp it gives this: error closed. Probably because usb debugging is not enabled... and in cwm different error: Device unauthorized...
Are you sure bootloader is unlocked?
It has to be unlocked cause i can flash permanent TWRP and when I enter TWRP recovery i can touch the buttons, even tried to do a restore in the dark... But nothing... Still the black screen persists... Thank you anyways.
PS: Well it looks like I've managed to resolve my problem. Thanx to user helroz i have found in his google drive a Raw firmware and I was able to flash it via fastboot with Asus Flash tool and now the phone booted, no more black screen for me. Lesson learned.
Hi all,
Maybe you've read my previous post, but I encountered the next problem
My phone was running HDMaximus 7.1.0, no problems. Just reinstalled it last week since I got some Google Play Services errors. Now, my phone rebooted suddenly, and after that it stated: Your phone has been encrypted. Well, I entered my PIN, which was correct, but my data is corrupt.
Tried some things, also with TWRP, and now I'm stuck with the M9, with TWRP, without OS and my internal storage is saying 0mb. Repairing that partition didn't help.
I've tried to sideload it, to push it, nothing helps, because of the internal storage. But the connection with the device is there, so that's not the problem.
Is there a way to recover from this? Maybe with a stock RUU from the SD card, or to rewrite the partitions?
Help is appreciated!
Regards,
Jacco
Fryslanboy said:
Hi all,
Maybe you've read my previous post, but I encountered the next problem
My phone was running HDMaximus 7.1.0, no problems. Just reinstalled it last week since I got some Google Play Services errors. Now, my phone rebooted suddenly, and after that it stated: Your phone has been encrypted. Well, I entered my PIN, which was correct, but my data is corrupt.
Tried some things, also with TWRP, and now I'm stuck with the M9, with TWRP, without OS and my internal storage is saying 0mb. Repairing that partition didn't help.
I've tried to sideload it, to push it, nothing helps, because of the internal storage. But the connection with the device is there, so that's not the problem.
Is there a way to recover from this? Maybe with a stock RUU from the SD card, or to rewrite the partitions?
Help is appreciated!
Regards,
Jacco
Click to expand...
Click to collapse
https://forum.xda-developers.com/verizon-one-m9/help/bricked-issues-return-to-100-stock-t3547433
Read my thread hope this helps.
Thats helping me a lot. I tried it with a stock RUU, 3.35.401.12, but when I start the download mode to flash it, it reboots just as soon when I push the Vol Up button. Weird.
(Phone is doing the whole sequence in about a second, then reboots and nothing happens)
Fryslanboy said:
Thats helping me a lot. I tried it with a stock RUU, 3.35.401.12, but when I start the download mode to flash it, it reboots just as soon when I push the Vol Up button. Weird.
(Phone is doing the whole sequence in about a second, then reboots and nothing happens)
Click to expand...
Click to collapse
That is weird. Did u format data in TWRP by typing Yes, not just factory reset?
Well, I can't get into TWRP anymore. When I select Recovery in the fastboot menu, it goes to the black HTC screen, after that quick flash of the TWRP screen (it worked before) and then it goes to it's white HTC screen.
I'll try to install TWRP via fastboot, maybe that'll help
Just tried to flash TWRP through fastboot, which was finished, but I still can't access Recovery. Weird..
You haven't stated if you are s-off. Have you made sure the stock rom matches your sku?.
Beamed in by telepathy.
Yes,
I am S-OFF. I tried several rom's, but I'll double check that. Good point!
HONOR 7X ( indian variant )
Phone is in a boot loop.
It shows Honor Logo and then the Error screen with the following message :
ERROR MODE
Attention!
Please update system again
Error!
Func NO : 15 (bl31 image)
Error NO : 1 (security verify failed!)
I tried to manually update to Oreo and was successful.
But VoLTE was not working properly.
So, i decided to roll back to EMUI 5.0 (Nougat) and got stuck in Boot Loop.
Initially both twrp and fastboot was working.
I tried to flash Stock recovery for oreo using fastboot.
But it didn't work.
At that point i lost both twrp and stock recovery.
It went into ERROR mode with different error codes saying "No Recovery Image" and "Load Failed"
I tried to Erase recovery and re-flash it.
I tried erasing System and flashing the system.img for oreo which was extracted from UPDATE.APP
I tried Multi tools.
I tried dload method.
Nothing worked. Same error mode.
Then i finally tried flashing the stock recovery again and relocked the oem.
Now, I can't even get into Fastboot.
It just displays the ERROR Screen.
I tried draining the battery to 0% and restarting it.
I tried all button combinations.
No luck.
Nothing works.
Now, i have a bricked phone with no recovery and no fastboot.
And i don't know whether they will accept this in the service center.
Is there someone who could really help me get my phone back?
rahulrk.2303 said:
HONOR 7X ( indian variant )
Phone is in a boot loop.
It shows Honor Logo and then the Error screen with the following message :
ERROR MODE
Attention!
Please update system again
Error!
Func NO : 15 (bl31 image)
Error NO : 1 (security verify failed!)
I tried to manually update to Oreo and was successful.
But VoLTE was not working properly.
So, i decided to roll back to EMUI 5.0 (Nougat) and got stuck in Boot Loop.
Initially both twrp and fastboot was working.
I tried to flash Stock recovery for oreo using fastboot.
But it didn't work.
At that point i lost both twrp and stock recovery.
It went into ERROR mode with different error codes saying "No Recovery Image" and "Load Failed"
I tried to Erase recovery and re-flash it.
I tried erasing System and flashing the system.img for oreo which was extracted from UPDATE.APP
I tried Multi tools.
I tried dload method.
Nothing worked. Same error mode.
Then i finally tried flashing the stock recovery again and relocked the oem.
Now, I can't even get into Fastboot.
It just displays the ERROR Screen.
I tried draining the battery to 0% and restarting it.
I tried all button combinations.
No luck.
Nothing works.
Now, i have a bricked phone with no recovery and no fastboot.
And i don't know whether they will accept this in the service center.
Is there someone who could really help me get my phone back?
Click to expand...
Click to collapse
I was gonna do a roll back too. Maybe I need to re exam your problem first.
Like why did you flash the Oreo system image after you rolled back?
Sorry, but I don't know of any steps forward for you, but can you tell the steps you did in the "Roll-back" and try to be detailed.
Please take a full back up before you roll back.
mrmazak said:
I was gonna do a roll back too. Maybe I need to re exam your problem first.
Like why did you flash the Oreo system image after you rolled back?
Sorry, but I don't know of any steps forward for you, but can you tell the steps you did in the "Roll-back" and try to be detailed.
Click to expand...
Click to collapse
I didn't succeed rolling back. I flashed the system.img and stock recovery of emui 5.0. But it got me the error.
Maybe the system partitions of emui 8.0 and 5.0 are different.
For example, The recovery partition has changed to recovery_ramdisk in emui 8.0.
Then, I tried flashing system.img and recovery of emui 8.0.
I got stuck in a bootloop.
But fastboot was accessible.
I tried flashing twrp for 8.0 by openkirin. It didn't work too.
Then i thought maybe i should flash the stock recovery and relock the oem and i did it.
Now i ended up with a locked bootloader, no recovery. Just the error message and the bootloop.
Somebody please help.
rahulrk.2303 said:
I didn't succeed rolling back. I flashed the system.img and stock recovery of emui 5.0. But it got me the error.
Maybe the system partitions of emui 8.0 and 5.0 are different.
For example, The recovery partition has changed to recovery_ramdisk in emui 8.0.
Then, I tried flashing system.img and recovery of emui 8.0.
I got stuck in a bootloop.
But fastboot was accessible.
I tried flashing twrp for 8.0 by openkirin. It didn't work too.
Then i thought maybe i should flash the stock recovery and relock the oem and i did it.
Now i ended up with a locked bootloader, no recovery. Just the error message and the bootloop.
Somebody please help.
Click to expand...
Click to collapse
OK, yes there is different partition table for oreo, so more that those partitions was needed.
one thing you might be able to try, is a manuael update.
put the oreo update.zip in the root of sd card. put card in phone, and hold both volume buttons together with power button.
mrmazak said:
OK, yes there is different partition table for oreo, so more that those partitions was needed.
one thing you might be able to try, is a manuael update.
put the oreo update.zip in the root of sd card. put card in phone, and hold both volume buttons together with power button.
Click to expand...
Click to collapse
I've already tried the dload method. But holding both volume buttons + power button didn't work. It loads into the error mode screen again. Maybe I'll copy the update.zip into the root of SD card and try again. But i think the phone won't boot into software update mode.
Is it hard bricked or soft bricked?
Should i try taking it to the service center?
People
Dont try to roll back from Oreo to Nougat on update ZIPs...
Partitions changed on Oreo System. The available update to Oreo it must read the previous partitions and configure the new partitions.
If you try to do it AFTER installing the update, the installation will get error cause can't read the Nougat partitions.
rahulrk.2303
With the phone powered off, press Vol Down key and insert the USB cable.
What happens?
RSGI said:
People
Dont try to roll back from Oreo to Nougat on update ZIPs...
Partitions changed on Oreo System. The available update to Oreo it must read the previous partitions and configure the new partitions.
If you try to do it AFTER installing the update, the installation will get error cause can't read the Nougat partitions.
rahulrk.2303
With the phone powered off, press Vol Down key and insert the USB cable.
What happens?
Click to expand...
Click to collapse
Nothing. It vibrates. Honor logo. Again the same error screen. I know it's supposed to go into fastboot mode. But unfortunately, it doesn't.
rahulrk.2303 said:
Nothing. It vibrates. Honor logo. Again the same error screen. I know it's supposed to go into fastboot mode. But unfortunately, it doesn't.
Click to expand...
Click to collapse
There is Oreo downgrade proceedure on Chinese huiwei club website. But your device needs full firmware package available.
There is full downgrade packages for al00 al10 and tl10.
rahulrk.2303 said:
Nothing. It vibrates. Honor logo. Again the same error screen. I know it's supposed to go into fastboot mode. But unfortunately, it doesn't.
Click to expand...
Click to collapse
Man... The FASTBOOT partiton is also screwed up...
The only change you got, other take the phone to the Huawei Service Center, is the dload method.
But for that you'lll need full packages.
mrmazak
Can you share a link to those packages?
RSGI said:
Man... The FASTBOOT partiton is also screwed up...
The only change you got, other take the phone to the Huawei Service Center, is the dload method.
But for that you'lll need full packages.
mrmazak
Can you share a link to those packages?
Click to expand...
Click to collapse
I have downloaded updateL22.zip for oreo and tried the dload method. It didn't work. It still boots to the same error mode. Is this condition hard brick or soft brick? I don't think there is a problem with the motherboard because the screen is turning on and it's in a bootloop. But i can't access recovery or fastboot. I'm confused. Maybe it's a software issue. But there is no way i could access the phone in order to flash something. I'm planning to take it to the service center and act innocent. Any suggestions? Will they find out that i unlocked or rooted and messed with the partitions. Is there any chance they could fix it?
RSGI said:
Man... The FASTBOOT partiton is also screwed up...
The only change you got, other take the phone to the Huawei Service Center, is the dload method.
But for that you'lll need full packages.
mrmazak
Can you share a link to those packages?
Click to expand...
Click to collapse
the three marked as full
b192
dated 3-28
http://pro-teammt.ru/firmware-database/?firmware_model=bnd-&firmware_page=0
mrmazak said:
the three marked as full
b192
dated 3-28
http://pro-teammt.ru/firmware-database/?firmware_model=bnd-&firmware_page=0
Click to expand...
Click to collapse
That's the one i tried.
The BNDAL10 one.
rahulrk.2303 said:
I have downloaded updateL22.zip for oreo and tried the dload method. It didn't work. It still boots to the same error mode. Is this condition hard brick or soft brick? I don't think there is a problem with the motherboard because the screen is turning on and it's in a bootloop. But i can't access recovery or fastboot. I'm confused. Maybe it's a software issue. But there is no way i could access the phone in order to flash something. I'm planning to take it to the service center and act innocent. Any suggestions? Will they find out that i unlocked or rooted and messed with the partitions. Is there any chance they could fix it?
Click to expand...
Click to collapse
If you take it to the service center, it wont matter how you play it...
The phone just dont get that way unless, somehow, the warranty was voided...
The less you say, the less you will pay for they to fix it... I believe that over those Service Centers they can fix almost everythng.
That package is not a full package! you need a Full Package
mrmazak said:
the three marked as full
b192
dated 3-28
http://pro-teammt.ru/firmware-database/?firmware_model=bnd-&firmware_page=0
Click to expand...
Click to collapse
Here´s a noob question:
What update.zip should i download?
1 - The one in the filelist section
2 - The one at the update section
Please, dont tell me that they're the same....
RSGI said:
If you take it to the service center, it wont matter how you play it...
The phone just dont get that way unless, somehow, the warranty was voided...
The less you say, the less you will pay for they to fix it... I believe that over those Service Centers they can fix almost everythng.
That package is not a full package! you need a Full Package
Click to expand...
Click to collapse
Is there nothing more i could do?
And what do you think the problem is?
Software issue or Hardware?
rahulrk.2303 said:
Is there nothing more i could do?
And what do you think the problem is?
Software issue or Hardware?
Click to expand...
Click to collapse
How the phone end up this way?
What were you trying to do?
How the heck you screw Fastboot? just kidding
If were trying to update, flash something to the device, its most likely a software issue.
If the phone fell down, bumped into something... well this increases the change that some hardware may by screwed also...
RSGI said:
If you take it to the service center, it wont matter how you play it...
The phone just dont get that way unless, somehow, the warranty was voided...
The less you say, the less you will pay for they to fix it... I believe that over those Service Centers they can fix almost everythng.
That package is not a full package! you need a Full Package
Here´s a noob question:
What update.zip should i download?
1 - The one in the filelist section
2 - The one at the update section
Please, dont tell me that they're the same....
Click to expand...
Click to collapse
but i think the update.zip listed in file list is same , don't really know.
all three are needed for full package.
RSGI said:
How the phone end up this way?
What were you trying to do?
How the heck you screw Fastboot? just kidding
If were trying to update, flash something to the device, its most likely a software issue.
If the phone fell down, bumped into something... well this increases the change that some hardware may by screwed also...
Click to expand...
Click to collapse
I flashed Oreo update successfully.
I wanted to Rollback.
I flashed system and recovery of nougat and locked the oem.
The problem is that we can't rollback from oreo to nougat because of different partitions.
I realized that only after locking the oem.
And now there's nothing i could do.
Btw, this is only due to flashing. So, i hope it's not a Motherboard problem.
The cost of flashing Software from service center is very less, even if my warranty is void.
rahulrk.2303 said:
I flashed Oreo update successfully.
I wanted to Rollback.
I flashed system and recovery of nougat and locked the oem.
**The problem is that we can't rollback from oreo to nougat because of different partitions.
Click to expand...
Click to collapse
???Well to be true you did not flash a roll-back(did you?) you only replaced system and recovery. The true roll-back "update.zip" should do more than that.???
I realized that only after locking the oem.
And now there's nothing i could do.
Btw, this is only due to flashing. So, i hope it's not a Motherboard problem.
The cost of flashing Software from service center is very less, even if my warranty is void.
Click to expand...
Click to collapse
mrmazak said:
???Well to be true you did not flash a roll-back(did you) you only replaced system and recovery. The true roll-back "update.zip" should do more than that.???
Click to expand...
Click to collapse
Tbh, i did everything one by one because nothing seems working.
I've tried every single method, trust me.
Hey! Need a little help. I updated to Android 11 Beta 2. Now my phone is stuck on a boot loop. A li'l different though, phone boots up normally and stays on the lockscreen and alive. Can receive calls. But once I unlock with the pattern it shows ' Phone is starting' works for a good 2 seconds and then ends up on infinite bootloop until I Power down. How do I access my files on PC ? If I can get just few files out of it then maybe I can perform a factory reset . Please HELP!
kkrazzyyguy said:
Hey! Need a little help. I updated to Android 11 Beta 2. Now my phone is stuck on a boot loop. A li'l different though, phone boots up normally and stays on the lockscreen and alive. Can receive calls. But once I unlock with the pattern it shows ' Phone is starting' works for a good 2 seconds and then ends up on infinite bootloop until I Power down. How do I access my files on PC ? If I can get just few files out of it then maybe I can perform a factory reset . Please HELP!
Click to expand...
Click to collapse
some older app is causing the loop you mayneed to factory reset through recovery or flash factory images to ur devices ,( please backup your all data and i will advice you to remove the screen lock if possible as it may cause issues after flashing older or newer images
That's what I am asking. How do I backup?
kkrazzyyguy said:
That's what I am asking. How do I backup?
Click to expand...
Click to collapse
I use this tool in my computer to update my phone.
Make sure to follow and read the instructions.
Since you're phone is in boot loop, put your phone in into bootloader
https://flash.android.com/welcome?continue=/custom
Facing the same trouble, did it help?
Hi, I finally managed to solve this!! Was able to get the phone working with data intact.
So I got exactly the same problem yesterday and was looking around for a solution when I bumped on this thread, the solution suggested to use Android Flash Tool can work only if the bootloader is already unlocked, USB debugging is on and you edit the flash.bat file to remove -w from the command line, which would not work in my case since my bootloader is locked and unlocking through ADB would wipe all data
So the only good solution is to do an OTA UPDATE USING ADB SIDELOAD, I just downloaded the OTA file, connected the phone to computer, booted into recovery and used ADB to sideload the OTA and boom, the phone is its pristine self again, with ALL DATA intact