So I decided to do a factory reset, erase all data. During the process, it got stuck on "erasing". Left it overnight, for NINE HOURS, still stuck.
I can boot into fastboot mode, but I CAN'T GO INTO RECOVERY MODE. When I select "recovery mode" (by choosing the option with volume keys and then selecting with power button), it just boots back into the "erasing" dialog.
I've installed the driver from Intel, but I can't get ADB to recognize my device. Does it have to be in recovery mode to recognize the device, or should it recognize in just fastboot mode?
Kind of at a loss here. Honestly, this kind of sounds like the dreaded Nexus 7 brick problem from earlier this year.
P.S. am I using the correct vocabulary here? Fastboot is the menu where you choose the boot method, and recovery mode is where you can choose to restore to factory settings or flash a new image?
EDIT: IT FIXED ITSELF. I just had to let it sit for like 15 hours. It's ridiculous that it took that long.
xlaxplaya said:
So I decided to do a factory reset, erase all data. During the process, it got stuck on "erasing". Left it overnight, for NINE HOURS, still stuck.
I can boot into fastboot mode, but I CAN'T GO INTO RECOVERY MODE. When I select "recovery mode" (by choosing the option with volume keys and then selecting with power button), it just boots back into the "erasing" dialog.
I've installed the driver from Intel, but I can't get ADB to recognize my device. Does it have to be in recovery mode to recognize the device, or should it recognize in just fastboot mode?
Kind of at a loss here. Honestly, this kind of sounds like the dreaded Nexus 7 brick problem from earlier this year.
P.S. am I using the correct vocabulary here? Fastboot is the menu where you choose the boot method, and recovery mode is where you can choose to restore to factory settings or flash a new image?
Click to expand...
Click to collapse
Same thing happened for me. Had to wait 14 hours and it finally completed.
LiquidPlacidity said:
Same thing happened for me. Had to wait 14 hours and it finally completed.
Click to expand...
Click to collapse
Haha whaaaat? 14? That's crazy. I might try it though, I'm running out of options. I'm trying to clear the bootloader cache and reflash the firmware via fastboot, but I keep getting "FAILED" messages that say I don't have permission. I can't do **** with this phone right now.
xlaxplaya said:
So I decided to do a factory reset, erase all data. During the process, it got stuck on "erasing". Left it overnight, for NINE HOURS, still stuck.
I can boot into fastboot mode, but I CAN'T GO INTO RECOVERY MODE. When I select "recovery mode" (by choosing the option with volume keys and then selecting with power button), it just boots back into the "erasing" dialog.
I've installed the driver from Intel, but I can't get ADB to recognize my device. Does it have to be in recovery mode to recognize the device, or should it recognize in just fastboot mode?
Kind of at a loss here. Honestly, this kind of sounds like the dreaded Nexus 7 brick problem from earlier this year.
P.S. am I using the correct vocabulary here? Fastboot is the menu where you choose the boot method, and recovery mode is where you can choose to restore to factory settings or flash a new image?
Click to expand...
Click to collapse
The same happened to me. In htcmania (an Spanish web like xda) there's a tutorial that worked for me:
ht tp://w ww.htcmania. com/showthread. php?t=1028393 (erase the spaces)
You don't have to follow all the steps. Just run the indicated cwm bat, wipe cache and reboot. It worked for me and without losing any data. I hope it helps you. If you have any question about the language, send me a message.
The solution for the OP and me was to simply wait it out. As LiquidPlacidity said, it can take over 12 hours for this to complete, it seems to take longer the more data you have on the device. OP messaged me saying it took them 12 hours, as LiquidPlacidity said it took them 14 hours, and for me it took a total of 22 hours to complete. My device was nearly full, but this is unforgivable on the part of Asus, they really need to fix this.
This happened to me I flashed recovery.img stock firmware recovery I downgraded to unlock bootloader then tried it again and it done it in 10mins
Just an update for anybody that finds this thread: I just had to let it sit for a stupidly long time. Like, maybe fifteen hours. I found somebody else that had to let it sit for 22 hours.
Any update to this problem !
xlaxplaya said:
Just an update for anybody that finds this thread: I just had to let it sit for a stupidly long time. Like, maybe fifteen hours. I found somebody else that had to let it sit for 22 hours.
Click to expand...
Click to collapse
I bought an Asus phone same like you and the same problem is happening ! USB debugging < I satule you
Solution found !
I've found a solution for this problem
All you need to find is a same device which is normal or BUY a new one ! OR BEG,Borrow, or steal from a friend
Find a asus zenfone 2 from a friend and enable usb debugging
Download intel driver
Just google it
Download Abd driver installer from the link bellow
Just google it
Just enable the usb debugging mode from the phone which you found
Open the adb driver intaller and fetch the abd driver directly from the installer for your asus phone
After that, download the following adb interface
Google it like " Abd interface for asus fastboot"
Then, extract the file , hold shift and right click the folder you will see a option in cmd option
Click that and a cmd window will be opened
Turn off your phone
Hold volume up and power button
After the phone vibrates realease from power button and keep holding volume up button
Boot loader will open and press volume up until you see "continue in fastboot mode"
Keep it the mode and connect your device to pc
It will directly intstall usb driver and adb driver after that
Just go back to your pc and type "fastboot format cache" and the process will continue
You will know when the process is over from the cmd in your pc
After that reboot your phone and you will still see the error
Click power and volume up button and the recovery mode will apear
Just wipe your data and every thing is going to be ALRIGHT
It is turning off after 10 minutes, how can I make it to 15 hours if it is turning off.. ?
have the same problem with my device too... i removed my battery once because i couldnt boot into recovery mode without turning it off...but its still in the erasing screen...will removing the battery cause any problem?
It's actually helps
xlaxplaya said:
So I decided to do a factory reset, erase all data. During the process, it got stuck on "erasing". Left it overnight, for NINE HOURS, still stuck.
I can boot into fastboot mode, but I CAN'T GO INTO RECOVERY MODE. When I select "recovery mode" (by choosing the option with volume keys and then selecting with power button), it just boots back into the "erasing" dialog.
I've installed the driver from Intel, but I can't get ADB to recognize my device. Does it have to be in recovery mode to recognize the device, or should it recognize in just fastboot mode?
Kind of at a loss here. Honestly, this kind of sounds like the dreaded Nexus 7 brick problem from earlier this year.
P.S. am I using the correct vocabulary here? Fastboot is the menu where you choose the boot method, and recovery mode is where you can choose to restore to factory settings or flash a new image?
EDIT: IT FIXED ITSELF. I just had to let it sit for like 15 hours. It's ridiculous that it took that long.
Click to expand...
Click to collapse
Same happened to me, but i found the way to fix it quickly. First of all i have find out that to properly wipe zenfone 2 , you have to firs wipe it from android software by going to Settings - Backup & reset - Factory data reset, and then wipe it from recovery menu and it will wipe it with normal speed it still will take 10-15 minutes but it's not 22 damn hours!!!
SO, The thing is that you still can get in fastboot mode and if you'll connect device to PC it will detect it. To get in fastboot you have to turn off your device(to do that you need to hold button "volume up" + "power" button, hold them untill phone is turned off,while you doing that the phone must be disconnectet from PC or it woun't turn off) then you press and hold "volume up" button and press and hold "power" button untill you feel the double vibrating and then you gonna let go the "power" button but still hold "volume up" button and then the menu will apear on the screen, you are in fastboot mode.
At this moment i'm sure that you have all Android (and official asus)drivers installed and all platfom-tools installed so i'm not gonna tell how to install it and i'm expecting that you know how to use platform-tools.
So... you go to cmd and from there to adb(usualy you do it by typing: cd c:\adb ) make sure that fastboot.exe is in adb folder, if not then download fastboot.exe and copy it in adb folder, then you type : ' fastboot devices' to see if PC deteced device you'll get 'F4AZFG04X560 fastboot' and it means that device is detected, then you type :
- ' fastboot format cache' wait till it's done
- 'fastboot erase userdata -w' wait till it's done
- 'fastboot erase system' wait till it's done
- 'fastboot erase recovery' wait till it's done
By doing all of these commands you're kind of doing factory reset by yourself.
Then you put recovery.img(recovery.img from OTA "older" than you had... if you had 165 then you take 164 or 139, or even OTA 97, it worked for me fine) and last firmware, for zenfone2 (from official asus site) in folder with adb and rename firware to 'update.zip' then run cmd from this folder and you can check if PC detected your device, by using command ' fastboot devices' and you'll see something like 'F4AZFG04X560 fastdoot' than you type command: ' fastboot flash recovery recovery.img' than you'll see :
" C:\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16384 KB)...
OKAY [ 0.684s]
writing 'recovery'...
OKAY [ 0.506s]
finished. total time: 1.193s'
then you choose recovery menu, by pressing "volume down" button, then phone boots it recovery mode and you see little droidbot "error", then you press and hold "power" button and press "volume up" button apears recovery menu, choose "apply update from adb", device is still connected to PC(if not, connect it), type in adb : ' adb sideload update.zip' wait till it's done(about 20-30 mitutes you'll see load in cmd)when it's done choose reboot in recovery menu... that's all.
P.S. sorry for my English it's not my native language.
The erasing has already started.
Now what should i do to make it quick?
It is really really bad. It is taking very long time.
Please advice
---------- Post added at 01:42 PM ---------- Previous post was at 01:22 PM ----------
I spent too much money on this useless phone. There are so many companies who give quality phones with quick os updates.
agriz said:
The erasing has already started.
Now what should i do to make it quick?
It is really really bad. It is taking very long time.
Please advice
---------- Post added at 01:42 PM ---------- Previous post was at 01:22 PM ----------
I spent too much money on this useless phone. There are so many companies who give quality phones with quick os updates.
Click to expand...
Click to collapse
Turn off device and follow by steps o described
what i do when the phone stuck on erasing :
1. At least wait for 30 minutes and make sure you have 60%+ battery before resetting or erasing the phone.
2. Turn off by pressing power till the phone turn off
3. Go to recovery mode by pressing volume + and power button together, and then select recovery by pressing volume + or volume -, the press power button to confirm it.
4. Done. It will continue erasing, but it just take 1-2 minutes then the phone will reboot.
I'm just sharing what i have done when this happen. If something happen to your phone, don't blame me
Testerov23 said:
Same happened to me, but i found the way to fix it quickly. First of all i have find out that to properly wipe zenfone 2 , you have to firs wipe it from android software by going to Settings - Backup & reset - Factory data reset, and then wipe it from recovery menu and it will wipe it with normal speed it still will take 10-15 minutes but it's not 22 damn hours!!!
SO, The thing is that you still can get in fastboot mode and if you'll connect device to PC it will detect it. To get in fastboot you have to turn off your device(to do that you need to hold button "volume up" + "power" button, hold them untill phone is turned off,while you doing that the phone must be disconnectet from PC or it woun't turn off) then you press and hold "volume up" button and press and hold "power" button untill you feel the double vibrating and then you gonna let go the "power" button but still hold "volume up" button and then the menu will apear on the screen, you are in fastboot mode.
At this moment i'm sure that you have all Android (and official asus)drivers installed and all platfom-tools installed so i'm not gonna tell how to install it and i'm expecting that you know how to use platform-tools.
So... you go to cmd and from there to adb(usualy you do it by typing: cd c:\adb ) make sure that fastboot.exe is in adb folder, if not then download fastboot.exe and copy it in adb folder, then you type : ' fastboot devices' to see if PC deteced device you'll get 'F4AZFG04X560 fastboot' and it means that device is detected, then you type :
- ' fastboot format cache' wait till it's done
- 'fastboot erase userdata -w' wait till it's done
- 'fastboot erase system' wait till it's done
- 'fastboot erase recovery' wait till it's done
By doing all of these commands you're kind of doing factory reset by yourself.
Then you put recovery.img(recovery.img from OTA "older" than you had... if you had 165 then you take 164 or 139, or even OTA 97, it worked for me fine) and last firmware, for zenfone2 (from official asus site) in folder with adb and rename firware to 'update.zip' then run cmd from this folder and you can check if PC detected your device, by using command ' fastboot devices' and you'll see something like 'F4AZFG04X560 fastdoot' than you type command: ' fastboot flash recovery recovery.img' than you'll see :
" C:\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16384 KB)...
OKAY [ 0.684s]
writing 'recovery'...
OKAY [ 0.506s]
finished. total time: 1.193s'
then you choose recovery menu, by pressing "volume down" button, then phone boots it recovery mode and you see little droidbot "error", then you press and hold "power" button and press "volume up" button apears recovery menu, choose "apply update from adb", device is still connected to PC(if not, connect it), type in adb : ' adb sideload update.zip' wait till it's done(about 20-30 mitutes you'll see load in cmd)when it's done choose reboot in recovery menu... that's all.
P.S. sorry for my English it's not my native language.
Click to expand...
Click to collapse
Hi, im having different issue than what was originally posted, but thought to give it a try the steps you described.
my problem is that my son forgot his pin code on the phone and has not a secondary method to unlock it, so i knew that i can just do a hard reset thru recovery mode and will be ok. but when i access to recovery mode only shows 3 options -reboot system -update via adb and -update via sd card. and is not showing the wipe/erase data option.
so i tried to follow your steps here all was good until writing on command
'fastboot erase recovery'
this is what i get back :
erasing 'recovery' ...
FAILED (remote: unable to format)
finished. total time : 0.891s
what can i do? either to continue with your steps or to do the hard reset on the phone?
thanks for any response
xlaxplaya said:
So I decided to do a factory reset, erase all data. During the process, it got stuck on "erasing". Left it overnight, for NINE HOURS, still stuck.
I can boot into fastboot mode, but I CAN'T GO INTO RECOVERY MODE. When I select "recovery mode" (by choosing the option with volume keys and then selecting with power button), it just boots back into the "erasing" dialog.
I've installed the driver from Intel, but I can't get ADB to recognize my device. Does it have to be in recovery mode to recognize the device, or should it recognize in just fastboot mode?
Kind of at a loss here. Honestly, this kind of sounds like the dreaded Nexus 7 brick problem from earlier this year.
P.S. am I using the correct vocabulary here? Fastboot is the menu where you choose the boot method, and recovery mode is where you can choose to restore to factory settings or flash a new image?
EDIT: IT FIXED ITSELF. I just had to let it sit for like 15 hours. It's ridiculous that it took that long.
Click to expand...
Click to collapse
Guys? My phone didn't fix itself. It has been 29 HOURS. And nothing is happening.
domrocks1337 said:
Guys? My phone didn't fix itself. It has been 29 HOURS. And nothing is happening.
Click to expand...
Click to collapse
Somebody else said it took 22 hours. So as ridiculous as it sounds, I think you should keep waiting. Try not to interrupt the process by restarting, we're not sure if it picks up where it left off.
If you don't have a backup phone or can't stand waiting, I would check to see if it's still under warranty and maybe do an RMA. You could just buy a phone with a 30 day return policy and just return it if this phone finally starts working again.
Hi
I have the same problem. It has been 28 Hours!
I can't access to Recovery Mode
Testerov23 said:
Same happened to me, but i found the way to fix it quickly. First of all i have find out that to properly wipe zenfone 2 , you have to firs wipe it from android software by going to Settings - Backup & reset - Factory data reset, and then wipe it from recovery menu and it will wipe it with normal speed it still will take 10-15 minutes but it's not 22 damn hours!!!
SO, The thing is that you still can get in fastboot mode and if you'll connect device to PC it will detect it. To get in fastboot you have to turn off your device(to do that you need to hold button "volume up" + "power" button, hold them untill phone is turned off,while you doing that the phone must be disconnectet from PC or it woun't turn off) then you press and hold "volume up" button and press and hold "power" button untill you feel the double vibrating and then you gonna let go the "power" button but still hold "volume up" button and then the menu will apear on the screen, you are in fastboot mode.
At this moment i'm sure that you have all Android (and official asus)drivers installed and all platfom-tools installed so i'm not gonna tell how to install it and i'm expecting that you know how to use platform-tools.
So... you go to cmd and from there to adb(usualy you do it by typing: cd c:\adb ) make sure that fastboot.exe is in adb folder, if not then download fastboot.exe and copy it in adb folder, then you type : ' fastboot devices' to see if PC deteced device you'll get 'F4AZFG04X560 fastboot' and it means that device is detected, then you type :
- ' fastboot format cache' wait till it's done
- 'fastboot erase userdata -w' wait till it's done
- 'fastboot erase system' wait till it's done
- 'fastboot erase recovery' wait till it's done
By doing all of these commands you're kind of doing factory reset by yourself.
Then you put recovery.img(recovery.img from OTA "older" than you had... if you had 165 then you take 164 or 139, or even OTA 97, it worked for me fine) and last firmware, for zenfone2 (from official asus site) in folder with adb and rename firware to 'update.zip' then run cmd from this folder and you can check if PC detected your device, by using command ' fastboot devices' and you'll see something like 'F4AZFG04X560 fastdoot' than you type command: ' fastboot flash recovery recovery.img' than you'll see :
" C:\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16384 KB)...
OKAY [ 0.684s]
writing 'recovery'...
OKAY [ 0.506s]
finished. total time: 1.193s'
then you choose recovery menu, by pressing "volume down" button, then phone boots it recovery mode and you see little droidbot "error", then you press and hold "power" button and press "volume up" button apears recovery menu, choose "apply update from adb", device is still connected to PC(if not, connect it), type in adb : ' adb sideload update.zip' wait till it's done(about 20-30 mitutes you'll see load in cmd)when it's done choose reboot in recovery menu... that's all.
P.S. sorry for my English it's not my native language.
Click to expand...
Click to collapse
I'm into the multi hour format thing of hell, i wonder why u must have to erase system and recovery, shouldnt it be enough to format userdata and cache? why do u do everything else? , in any case where do u get the official recovery? i dont wanna mod the phone, i wanna get OTA updates in the future.
Hello,
Yesterday, doing noting special, I took my phone from my pocket and saw it was stucked on "fastboot".
Ok, no problem, I made a hard reset (power button 20s-30s): it reboots and immediately the screen fastboot appears.
I tried a fastboot reboot from my PC: idem: it reboots and immediately shows "Fastboot".
I tried vol UP + power button: a menu shows me just 2 options: wipe cache or reboot. I tried wipe cache: nothing better. I reboot in fastboot mode. It's weird because I had TWRP menu before (I rooted it a few months ago).
In summary, I cannot leave from the Fastboot screen. Whatever I do, I always come back to "fastboot" menu.
Could you help me please?
You can try to flash your device with the latest fastboot ROM witch can be found there
Flash MIUI fastboot ROM using MiFlash software..
Note : Do not relock bootloader for safer side
isterios said:
Hello,
Yesterday, doing noting special, I took my phone from my pocket and saw it was stucked on "fastboot".
Ok, no problem, I made a hard reset (power button 20s-30s): it reboots and immediately the screen fastboot appears.
I tried a fastboot reboot from my PC: idem: it reboots and immediately shows "Fastboot".
I tried vol UP + power button: a menu shows me just 2 options: wipe cache or reboot. I tried wipe cache: nothing better. I reboot in fastboot mode. It's weird because I had TWRP menu before (I rooted it a few months ago).
In summary, I cannot leave from the Fastboot screen. Whatever I do, I always come back to "fastboot" menu.
Could you help me please?
Click to expand...
Click to collapse
I had a similar problem like that and I thought all was hopeless and then I tried the simplest thing. Fastboot boot recovery instead of trying to flash it and then I flash the recovery through recovery to make sure everything was okay but it happened when using Orange ? recovery. I have not used it since. I hope this helps.
so ive flashed liquid remix but forgot that adb doesnt work on that rom.
and i dont have flashed twrp installer aswell since i use to boot into rom first.
so im stuck in this rom without twrp, root so am i kinda bricked now?
krabban said:
so ive flashed liquid remix but forgot that adb doesnt work on that rom.
and i dont have flashed twrp installer aswell since i use to boot into rom first.
so im stuck in this rom without twrp, root so am i kinda bricked now?
Click to expand...
Click to collapse
Does fastboot devices see the phone if you key combo into bootloader? Do a flash-all (minus -w so you at least can save user data) of whatever monthly security patch you were on before.
sliding_billy said:
Does fastboot devices see the phone if you key combo into bootloader? Do a flash-all (minus -w so you at least can save user data) of whatever monthly security patch you were on before.
Click to expand...
Click to collapse
No it does not. That's the problem. Need to take out a new on ensurance
krabban said:
No it does not. That's the problem. Need to take out a new on ensurance
Click to expand...
Click to collapse
Are you sure about that. It is clear from your other post that you Re confusing fastboot and adb. adb works from a booted phone, while fastboot works from bootloader. Also, can you get to recovery? I highly doubt you are bricked, but there is definitely some confusion.
Turn off your Google Pixel 3 XL.
Press and hold the Power+Volume Down buttons until bootloader mode (image of an Android with Start above it) appears, then release.
Select Recovery mode. You can use the Volume buttons to cycle through the available options and the Power button to select. The device will flash the Google start screen momentarily and then restarts in Recovery mode.
If presented with an image of a broken Android with “No Command” printed on the screen, press and hold the Power button. Press the Volume Up button once. Then release the Power button.
From the Android Recovery screen, select Wipe data/factory reset.
Select Yes. Wait for several minutes for the factory data reset process to complete.
Select Reboot system now. Allow several minutes for the factory data reset and reboot processes to complete.
Set the phone up again.
sliding_billy said:
Are you sure about that. It is clear from your other post that you Re confusing fastboot and adb. adb works from a booted phone, while fastboot works from bootloader. Also, can you get to recovery? I highly doubt you are bricked, but there is definitely some confusion.
Turn off your Google Pixel 3 XL.
Press and hold the Power+Volume Down buttons until bootloader mode (image of an Android with Start above it) appears, then release.
Select Recovery mode. You can use the Volume buttons to cycle through the available options and the Power button to select. The device will flash the Google start screen momentarily and then restarts in Recovery mode.
If presented with an image of a broken Android with “No Command” printed on the screen, press and hold the Power button. Press the Volume Up button once. Then release the Power button.
From the Android Recovery screen, select Wipe data/factory reset.
Select Yes. Wait for several minutes for the factory data reset process to complete.
Select Reboot system now. Allow several minutes for the factory data reset and reboot processes to complete.
Set the phone up again.
Click to expand...
Click to collapse
Gonna try tonight. I just get no command when select recovery mode from os
krabban said:
Gonna try tonight. I just get no command when select recovery mode from os
Click to expand...
Click to collapse
"No command" is normal. It is the power and volume key combo from there that actually get you into the recovery menu. That combo timing can be a little tricky. Power, then quickly press and release volume up then release power. You should then see the recovery menu. You might even see your phone with adb devices and have the ability to sideload an OTA (to save user data), but given your current situation I think a factory reset is best,
sliding_billy said:
"No command" is normal. It is the power and volume key combo from there that actually get you into the recovery menu. That combo timing can be a little tricky. Power, then quickly press and release volume up then release power. You should then see the recovery menu. You might even see your phone with adb devices and have the ability to sideload an OTA (to save user data), but given your current situation I think a factory reset is best,
Click to expand...
Click to collapse
Thanks buddy. Gonna try I'll report back
your the man, thanks alot. was able to run flash all script in sideload . now im back at android 10
krabban said:
your the man, thanks alot. was able to run flash all script in sideload . now im back at android 10
Click to expand...
Click to collapse
Not sure what you mean by running flash-all in sideload (I assume you ran adb sideload from recovery or flash-all from bootloader), but I'm glad you are up and running.