Unable to boot in recovery (tried erase cache, after flashing stock recovery) - One (M8) Q&A, Help & Troubleshooting

Hi everyone,
I'm now rather paranoid after my last phone died during what should've been a safe operation (RUU flash).
My phone was rooted and unlocked (done via adb and fastboot this time, no toolkits), running stock 2.22.531.5. Had TWRP installed for recovery. OTA got pushed, tried it and obviously that failed because our phones will only update w/ stock recovery.
Waited until I had some time (this morning). Downloaded stock 2.22.231.5 recovery, placed in my Minimal ADB and Fastboot folder (latest version, downloaded only a week or two ago).
Code:
adb reboot bootloader
fastboot flash recovery (filename)
(worked?)
fastboot reboot
adb reboot recovery
Phone in the middle of the screen with a red exclamation mark in a triangle. Wouldn't shut down holding power, did restart back into the stock ROM using Vol + and Power.
Oh, I forgot to erase cache (per FAQ)!
Code:
adb reboot bootloader
fastboot erase cache
(did you mean to format this partition? Otherwise worked)
fastboot reboot
adb reboot recovery
Same problem.
What am I missing? Should I flash TWRP and try to flash the stock recovery again? Should I just try to flash stock recovery again? I broke my last phone trying to flash things that weren't flashing right multiple times...
Thanks for the help!
PDD
edit: Double-checked the md5 on the stock recovery that I was trying to flash, it checks out.
edit 2: Sorry if this is a common question. I've tried googling all the combinations of red exclamation phone bootloader recovery I can, but it's all completely irrelevant hits.

PasDeDeux said:
Hi everyone,
I'm now rather paranoid after my last phone died during what should've been a safe operation (RUU flash).
My phone was rooted and unlocked (done via adb and fastboot this time, no toolkits), running stock 2.22.531.5. Had TWRP installed for recovery. OTA got pushed, tried it and obviously that failed because our phones will only update w/ stock recovery.
Waited until I had some time (this morning). Downloaded stock 2.22.231.5 recovery, placed in my Minimal ADB and Fastboot folder (latest version, downloaded only a week or two ago).
Code:
adb reboot bootloader
fastboot flash recovery (filename)
(worked?)
fastboot reboot
adb reboot recovery
Phone in the middle of the screen with a red exclamation mark in a triangle. Wouldn't shut down holding power, did restart back into the stock ROM using Vol + and Power.
Oh, I forgot to erase cache (per FAQ)!
Code:
adb reboot bootloader
fastboot erase cache
(did you mean to format this partition? Otherwise worked)
fastboot reboot
adb reboot recovery
Same problem.
What am I missing? Should I flash TWRP and try to flash the stock recovery again? Should I just try to flash stock recovery again? I broke my last phone trying to flash things that weren't flashing right multiple times...
Thanks for the help!
PDD
Click to expand...
Click to collapse
Phone with a triangle and an upside down exclamation mark in it... That's stock recovery. Hold Volume Up and TAP (TAP don't HOLD) the power button. That'll take you into stock recovery menu.

BerndM14 said:
Phone with a triangle and an upside down exclamation mark in it... That's stock recovery. Hold Volume Up and TAP (TAP don't HOLD) the power button. That'll take you into stock recovery menu.
Click to expand...
Click to collapse
Haha, thank you, adb wasn't recognizing the phone the first time so I didn't realize that I was in stock recovery. The exclamation is right-side-up, but that's not really super important. Thanks again!
Just in case you happen to know... I don't need to do anything else to apply the OTA do I? I see some people reflashing stock RUU over their stock ROM or people trying to relock bootloader, but that seems like overkill?

PasDeDeux said:
Haha, thank you, adb wasn't recognizing the phone the first time so I didn't realize that I was in stock recovery. The exclamation is right-side-up, but that's not really super important. Thanks again!
Just in case you happen to know... I don't need to do anything else to apply the OTA do I? I see some people reflashing stock RUU over their stock ROM or people trying to relock bootloader, but that seems like overkill?
Click to expand...
Click to collapse
I also always thought that you need to lock bootloader if you're S-ON but it seems not to be the case. You just need to be stock ROM and stock recovery.

BerndM14 said:
I also always thought that you need to lock bootloader if you're S-ON but it seems not to be the case. You just need to be stock ROM and stock recovery.
Click to expand...
Click to collapse
Thanks again for the help! I'm S-ON, but I guess I'll give it a go and see what happens, haha.

Related

Boot Loop

Where to begin...
I have had ARHD GSM 2.1.2 working flawlessly since I have had the phone. I put the charger in the phone, pulled it out straight away and the Wave Secure app tried to initiate (data backup on charger only). When I put the charger back in the battery (Circles Mod by Hoolm) was stuck flashing battery percentage and charge bolt even when not charging.
I thought it was a good time to do a fresh install anyway so I superwiped lite and flashed ARHD 2.1.5. Reinstalled all my apps from the market fresh and then tried to perform a titanium backup...
The phone turned off and is now stuck in a permanent boot loop. I managed to use mskip toolkit to put it in recovery once and ran superwipe, wipe dalvik, fix permissions, re-flash ARHD 2.1.5 and then reboot.
Now it is stuck in a permanent boot loop and I cannot get it into recovery...HELP!
The only alternate screen I can get to is the ODIN screen by holding vol down and power....it says downloading but nothing happens.
Can you use fastboot from the mobil odin screen?
Flash the recovery.img maybe.
But can you not get into the bootloader menu at all?
Unfortunately, no. It just says "downloading - do not turn off target" where the option to enter fastboot should be.
Jubakuba said:
Can you use fastboot from the mobil odin screen?
Flash the recovery.img maybe.
But can you not get into the bootloader menu at all?
Click to expand...
Click to collapse
dont use odin.
turn pull the battery, put it back in, press and hold both vol up and down and press and hold the power button.
that's fastboot mode.
HUGE thank you.
I am in recovery! Now what is best practice to get phone back into working order???
Zepius said:
dont use odin.
turn pull the battery, put it back in, press and hold both vol up and down and press and hold the power button.
that's fastboot mode.
Click to expand...
Click to collapse
do you have a nandroid backup? if so, restore that. if you still bootloop, get back to recovery, wipe data and cache.
When I try and go to recovery I get the android bot with a red exclamation point coming out of it. It won't let me get to recovery.
Is this the point where something is definitely wrong and I have to send it to samsung for warranty repair?
I am pretty sure I can flash ICL53f and relock the bootloader.
Zepius said:
do you have a nandroid backup? if so, restore that. if you still bootloop, get back to recovery, wipe data and cache.
Click to expand...
Click to collapse
sacksyboy said:
When I try and go to recovery I get the android bot with a red exclamation point coming out of it. It won't let me get to recovery.
Is this the point where something is definitely wrong and I have to send it to samsung for warranty repair?
I am pretty sure I can flash ICL53f and relock the bootloader.
Click to expand...
Click to collapse
You don't have the green android with the belly open that has 16 blue squares inside it? If you do, use the volume keys to move between Power off, Start, Restart bootloader, and Recovery mode. Press the power button in the "Recovery mode option." If you don't have this screen, then use fastboot commands, and flash Google Factory Images. You don't need to send it into Samsung for warranty, nothing is wrong. Lol.
I do have the recovery option from fastboot mode.
It is when I select recovery that I get the green android with the belly open and a exclamation point. It will not go any further once I select recovery.
I flashed ICL53F and I still get the exclamation when trying to get to recovery.
anton2009 said:
You don't have the green android with the belly open that has 16 blue squares inside it? If you do, use the volume keys to move between Power off, Start, Restart bootloader, and Recovery mode. Press the power button in the "Recovery mode option." If you don't have this screen, then use fastboot commands, and flash Google Factory Images. You don't need to send it into Samsung for warranty, nothing is wrong. Lol.
Click to expand...
Click to collapse
sacksyboy said:
I do have the recovery option from fastboot mode.
It is when I select recovery that I get the green android with the belly open and a exclamation point. It will not go any further once I select recovery.
I flashed ICL53F and I still get the exclamation when trying to get to recovery.
Click to expand...
Click to collapse
That is Stock recovery. Are you rooted? Are you on a Stock ROM?
When you hit the volume down or up button you should get some options..., which are they?
Sent from my Galaxy Nexus using xda premium
Yeah you have to flash a custom recovery.
fastboot flash recovery (recoveryname)
Here's an awesome custom recovery for CDMA
Went to recovery (when it was working) from fastboot. Flashed stock ICL53F.
Options are reboot, recovery etc.
I am not trying to wipe and flash ARHD 2.1.5 GSM but cannot access recovery from fastboot. I get an android robot with an exclamation point.
Diger36 said:
That is Stock recovery. Are you rooted? Are you on a Stock ROM?
When you hit the volume down or up button you should get sonme options..., which are they?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I've done this.
Used mskip tool to do so and md5 confirms stock download came through okay. Still stuck with trying to access recovery from fastboot to flash ARHD.
anton2009 said:
Yeah you have to flash a custom recovery.
fastboot flash recovery (recoveryname)
Click to expand...
Click to collapse
sacksyboy said:
I've done this.
Used mskip tool to do so and md5 confirms stock download came through okay. Still stuck with trying to access recovery from fastboot to flash ARHD.
Click to expand...
Click to collapse
Try doing it manually?
Done that too (vol up + vol down + power). No dice.
anton2009 said:
Try doing it manually?
Click to expand...
Click to collapse
sacksyboy said:
I've done this.
Used mskip tool to do so and md5 confirms stock download came through okay. Still stuck with trying to access recovery from fastboot to flash ARHD.
Click to expand...
Click to collapse
I've lost ya... What is your situation now?
Do you have:
a: Stock recovery (droid on its back with red exclamation mark)
b: CWM recovery through MSKIP's tool
1. ARHD ROM
2. Stock ICL53F
x. a Boot loop
y. Not?
I think I see the disconnect now...
I have "droid on its back with red exclamation mark" (ICL53F - from http://code.google.com/android/nexus/images.html)
I did not realise that a "droid on its back with red exclamation mark" was an indicator of stock recovery. So I guess I have that. I only used mskip to flash stock ICL53F not CWM recovery. I no longer have a boot loop but get the droid on back with exclamation (stock recovery).
So I should flash CWM, add ARHD zip and flash???
Diger36 said:
I've lost ya... What is your situation now?
Do you have:
a: Stock recovery (droid on its back with red exclamation mark)
b: CWM recovery through MSKIP's tool
1. ARHD ROM
2. Stock ICL53F
x. a Boot loop
y. Not?
Click to expand...
Click to collapse
sacksyboy said:
I think I see the disconnect now...
I have "droid on its back with red exclamation mark" (ICL53F - from http://code.google.com/android/nexus/images.html)
I did not realise that a "droid on its back with red exclamation mark" was an indicator of stock recovery. So I guess I have that. I only used mskip to flash stock ICL53F not CWM recovery. I no longer have a boot loop but get the droid on back with exclamation (stock recovery).
So I should flash CWM, add ARHD zip and flash???
Click to expand...
Click to collapse
Yes flash CWM, see if you can boot into custom recovery, and then flash ARHD.
Okay...I'll give it a shot.
I will reply back with results.
anton2009 said:
Yes flash CWM, see if you can boot into custom recovery, and then flash ARHD.
Click to expand...
Click to collapse

[Q] Has Android Revolution HD install bricked my phone? [Solved]

Hello All.
This is the first time I have tried to put a custom ROM on an HTC so I am still learning the ropes.
I tried to follow the instructions in the first post. So... In sequence, this is what I did...
HTC One X unlocked with htcdev.com (S-ON) or S-OFF (coming soon)
This seemed to go without a hitch. On the HBoot screen (I think that is what it is called) it tells me I am now unlocked.
ClockworkMod Recovery or 4EXT Touch Recovery (coming soon)
I installed the official version as per the instructions here.
The last instruction that seemed to work successfully was this:
Code:
fastboot flash boot recovery-clockwork-touch-5.8.2.4-endeavouru.img
Then I tried
Code:
fastboot reboot
which put me into recovery mode.
<EDIT> The instructions here have now been corrected to:
Code:
fastboot flash recovery recovery-clockwork-touch-5.8.2.4-endeavouru.img
</EDIT>
Choosing the reboot option from recovery just bounces me back into recovery mode but I understand from the instructions I should be able to boot into a working phone!
Has something gone wrong?
If I use the volume down + power button I can enter HBoot mode. From here I can select Fastboot. Connecting via USB to my computer seems to work fine, as I see Fastboot USB on my phone, and I when I execute this...
Code:
fastboot devices
I get something like this
Code:
List of devices attached
HTXXXXXXXXXX device
I am now unsure how to continue because I think something has gone wrong and I should have a working phone at this point.
Do I press ahead and try to install the Firmware package from here? Unless this lets me boot into a working phone (which I don’t believe it will), it still leaves me with the problem that for a One X, without a removable SD card I don’t know how to transfer and run the "Super Wipe" script, nor transfer and flash Android Revolution ROM via recovery.
Do I need to do something with
Code:
fastboot flash
?
Please help as she is threatening to dump me for destroying her 2-day-old phone.
It's
Code:
fastboot flash [B]recovery[/B] recovery-clockwork-touch-5.8.2.4-endeavouru.img
not boot..
Solution for you is to go into bootloader, flash recovery with the command i gave you and then reboot into recovery and install the rom..
After that everything should be ok and your phone will boot into ARHD without any problem.
delete please
anko184 said:
It's
Code:
fastboot flash [B]recovery[/B] recovery-clockwork-touch-5.8.2.4-endeavouru.img
not boot..
Solution for you is to go into bootloader, flash recovery with the command i gave you and then reboot into recovery and install the rom..
After that everything should be ok and your phone will boot into ARHD without any problem.
Click to expand...
Click to collapse
Thanks
It looks like the instructions I followed previously had an error then.
<EDIT> The instructions were incorrect, but have now been corrected </EDIT>
I will follow your instructions. But what about the RUU that is mentioned in the instructions? It is not clear how or when I should flash it. Presumably I flash the RUU before I do the ARHD flash... ???
mwhincup said:
Thanks
It looks like the instructions I followed previously had an error then.
I will follow your instructions. But what about the RUU that is mentioned in the instructions? It is not clear how or when I should flash it. Presumably I flash the RUU before I do the ARHD flash... ???
Click to expand...
Click to collapse
You don't need to flash any RUU or firmware unless your phone wasn't shipped with 1.26, which i don't think it was.
Just try flashing the recovery with the correct command and then the rom. If your phone doesn't boot after that then you may try the firmware but i'm sure you won't need it.
anko184 said:
You don't need to flash any RUU or firmware unless your phone wasn't shipped with 1.26, which i don't think it was.
Just try flashing the recovery with the correct command and then the rom. If your phone doesn't boot after that then you may try the firmware but i'm sure you won't need it.
Click to expand...
Click to collapse
So, I understand that you are telling me:
Flashing CWM recovery will rectify my current problem and restore my phone to a workable state.
Booted normally, I can copy the ARHD ROM to the internal SD (not sure what the location for this will be).
I then reboot into recovery and 'Install Zip from SD card'.
Click to expand...
Click to collapse
Is this correct?
mwhincup said:
So, I understand that you are telling me:
Is this correct?
Click to expand...
Click to collapse
Wait before you flash anything, if you don'talready have arhd on your internal sd you may be in trouble if you do superwipe
Sent from my HTC One X using XDA
mwhincup said:
So, I understand that you are telling me:
Is this correct?
Click to expand...
Click to collapse
Without trying to sound like a ****, if you don't understand what you are doing you should read more to understand the whole process before attempting it.
bagofcrap24 said:
Wait before you flash anything, if you don'talready have arhd on your internal sd you may be in trouble if you do superwipe
Click to expand...
Click to collapse
Good advice, I am sure. However my problem now is getting into a working phone so that I can transfer the ROM onto the internal SD.
Can't wait to get home and try it!
what you have done is replaced your boot sector with a recovery image, that is the reason why you cant boot your phone as normal so even flashing the recovery correctly will not allow your phone to boot up.
as your phone cannot boot up you cannot transfer any files to the internal memory of your phone in order to flash ARHD
at present there is a problem with the official version of ClockworkMod Recovery so i personally would reccommend using the interim version HERE
and flash with fastboot flash recovery r1-modaco-recovery-clockwork-touch-endeavoru.img
As you have [email protected]$ked your boot partition up you will also want to download THIS
this is an insecure boot image (thanks to paul from modaco) I have just extracted the part you will need from his package
with this you will need to be in fastboot again and type fastboot flash boot boot.img
obviously you will need to copy both of the files to the same directory as fastboot is on your PC in order to send them
by flashing the boot section with the insecure boot here it will allow your phone to boot up normally again, once it has booted normally you can then copy the ARHD and superwipe to your internal SD card
to access recovery
power off phone by holding power button for 10seconds
power on with power+voldown
select recovery from hboot screen with voldown then power to select
your phone will reboot and then you will be in recovery
do a nandroid backup incase anything goes wrong
then flash the superwipe script
then flash ARHD 1.2.2
all is good
animaleyes76 said:
Without trying to sound like a ****, if you don't understand what you are doing you should read more to understand the whole process before attempting it.
Click to expand...
Click to collapse
You are correct of course, however, there comes a point where the only way to learn is to actually do something. I have flashed numerous ROMS on my Galaxy S, and before doing this I have read numerous guides trying to better understand the procedures for HTC devices.
I have tried to follow what appeared to be a step-by-step guide, however, either there has been a malfunction, or it appears there may be two important bits of information missing from that guide:
Flashing CWM recovery leaves the phone in a state that it won't boot normally, and consequently...
The ARHD ROM should be loaded onto the internal SD at the very beginning of the procedure
Click to expand...
Click to collapse
Thanks all of you so much for your effort. It's much appreciated.
bagofcrap24 said:
what you have done is replaced your boot sector with a recovery image, that is the reason why you cant boot your phone as normal so even flashing the recovery correctly will not allow your phone to boot up.
Click to expand...
Click to collapse
@bagofcrap24 I may have misled you with a typo in the first post. (See my edit)
d'oh
edit : just read updated info
so what happens when you choose recovery and press power from the hboot screen
i'm understanding that when doing a normal reboot it just sends you straight into hboot?
power on with voldown
press voldown to select recovery
press power to select recovery
you should either see CWM or the stock recovery
again looking at what you have written, if you just do a normal reboot and its putting you straight into recovery then you probably have flashed recovery onto the boot partition
bagofcrap24 said:
edit : just read updated info
so what happens when you choose recovery and press power from the hboot screen
i'm understanding that when doing a normal reboot it just sends you straight into hboot?
power on with voldown
press voldown to select recovery
press power to select recovery
you should either see CWM or the stock recovery
again looking at what you have written, if you just do a normal reboot and its putting you straight into recovery then you probably have flashed recovery onto the boot partition
Click to expand...
Click to collapse
I'll get back to you with some definitive answers in 3 hours or so. Sorry, I'm at work now.
bagofcrap24 said:
so what happens when you choose recovery and press power from the hboot screen
Click to expand...
Click to collapse
power on with voldown
press voldown to select recovery
press power to select recovery
Click to expand...
Click to collapse
I get a circular yellow 'recycling' symbol, followed a few seconds later by a magenta triangle with an exclamation mark. (Is this the stock recovery?). Then the phone restarts and I end up back in the Clockworkmod recovery.
i'm understanding that when doing a normal reboot it just sends you straight into hboot?
Click to expand...
Click to collapse
No. A normal reboot (without holding the Vol down key) sends me straight to clockworkmod recovery.
I can get to HBoot with Vol down+Power on startup.
mwhincup said:
I get a circular yellow 'recycling' symbol, followed a few seconds later by a magenta triangle with an exclamation mark. (Is this the stock recovery?). Then the phone restarts and I end up back in the Clockworkmod recovery.
No. A normal reboot (without holding the Vol down key) sends me straight to clockworkmod recovery.
I can get to HBoot with Vol down+Power on startup.
Click to expand...
Click to collapse
Right this means you did mess up the boot and recovery partitions, the one where you have the exclamation mark is the stock recovery which means you didn't flash cwm to the recovery partition.
the fact that you get to recovery on a normal boot also suggests as I suspected that you have flashed recovery on to the boot partition, follow the instructions I put up earlier about flashing the boot.IMG and redo the recovery.IMG and you should be fine
Sent from my HTC One X using XDA
bagofcrap24 said:
what you have done is replaced your boot sector with a recovery image, that is the reason why you cant boot your phone as normal so even flashing the recovery correctly will not allow your phone to boot up.
as your phone cannot boot up you cannot transfer any files to the internal memory of your phone in order to flash ARHD
at present there is a problem with the official version of ClockworkMod Recovery so i personally would reccommend using the interim version HERE
and flash with fastboot flash recovery r1-modaco-recovery-clockwork-touch-endeavoru.img
As you have [email protected]$ked your boot partition up you will also want to download THIS
this is an insecure boot image (thanks to paul from modaco) I have just extracted the part you will need from his package
with this you will need to be in fastboot again and type fastboot flash boot boot.img
obviously you will need to copy both of the files to the same directory as fastboot is on your PC in order to send them
by flashing the boot section with the insecure boot here it will allow your phone to boot up normally again, once it has booted normally you can then copy the ARHD and superwipe to your internal SD card
to access recovery
power off phone by holding power button for 10seconds
power on with power+voldown
select recovery from hboot screen with voldown then power to select
your phone will reboot and then you will be in recovery
do a nandroid backup incase anything goes wrong
then flash the superwipe script
then flash ARHD 1.2.2
all is good
Click to expand...
Click to collapse
Your analysis is quite correct. All is indeed good! Thanks very much. The boot image worked as described. I will now transfer Superwipe and the ROM.
Make sure you do a nandroid backup first, it was lucky this time but if you mess up your system partition you may find yourself with no way of putting files on without unrooting and restoring the ruu
Sent from my HTC One X using XDA
bagofcrap24 said:
Make sure you do a nandroid backup first, it was lucky this time but if you mess up your system partition you may find yourself with no way of putting files on without unrooting and restoring the ruu
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
Done!
Everything worked as you said it would.
I now have ARHD installed and running brilliantly.
Thanks again
mwhincup said:
Done!
Everything worked as you said it would.
I now have ARHD installed and running brilliantly.
Thanks again
Click to expand...
Click to collapse
Glad you fixed it and sorry for being a bit harsh earlier.. was having a bad day

Jelly Bean animation locked

Need some help. I have a Verizon Galaxy Nexus and did bootloader and rooted my phone. Yeah!! Tried to install JellyBean and ran into a problem. The animation of Jellybean is locked what do I do? Need some serious help. I am able to get to Fastboot mode.
coachv said:
Need some help. I have a Verizon Galaxy Nexus and did bootloader and rooted my phone. Yeah!! Tried to install JellyBean and ran into a problem. The animation of Jellybean is locked what do I do? Need some serious help. I am able to get to Fastboot mode.
Click to expand...
Click to collapse
The animation is locked? I don't understand what you mean. Are you stuck at the boot logo (Google screen) or the boot animation (flashing X)? Either way, you can just go into your custom recovery, wipe data, and try flashing again if you are waiting on it to boot for that long. Some users have experienced waiting 5 minutes before it actually started up.
Agreed.
Initial boot on my Toro took 5-6 minutes.
It was butter ever since, however.
Give it a minute.
And make sure you're properly installing a rom (post 2 from the link in my signature).
Edit:
Anton&Juba.
Tag-teaming 'ze noobs until it goes out of style.
It's flashing X on Boot animation. It has stayed in that mode for hours. I am confused and can not back into my phone. Reading other posts, I am able to get back to Fastboot mode. What do I do next? I appreciate your help. Thanks
coachv said:
It's flashing X on Boot animation. It has stayed in that mode for hours. I am confused and can not back into my phone. Reading other posts, I am able to get back to Fastboot mode. What do I do next? I appreciate your help. Thanks
Click to expand...
Click to collapse
I see. So you're in a bootloop. What do you mean fastboot mode? Because I know some users get confused with the terms... I'm assuming you're able to enter the Bootloader (screen with android belly open, where you are able to move through some menu options with your up and down volume keys)? Note, this is not the screen with the Android and red exclamation point. If you are able to boot into bootloader, you should be able to enter your custom recovery (Clockworkmod Recovery?) and wipe data and either flash a rom (same one or new one) and try again, or restore a backup you made. If you're set on using fastboot commands, you can always flash Nexus Factory Images, although this will wipe your SD card. I recommend getting into your custom recovery and wiping and flashing or restoring. If you don't have a custom recovery, you can always flash a custom recovery (fastboot flash recovery recoveryname.img) and flash a custom rom or restore from there. Here is CWM recovery incase you don't have a custom recovery, or you have reverted back to stock (Android with red exclamation point).
yes the android belly is open. I just don't the steps that I need to do from here. This is where I get lost.
coachv said:
yes the android belly is open. I just don't the steps that I need to do from here. This is where I get lost.
Click to expand...
Click to collapse
Can you scroll through the menu options with your volume keys? And one of the options should be "reboot recovery." Do that one.
Yes I can scroll with volume controls. Here are my options: start, restart bootloader, recovery mode and power off
coachv said:
Yes I can scroll with volume controls. Here are my options: start, restart bootloader, recovery mode and power off
Click to expand...
Click to collapse
Okay dude.
1.) Move your volume keys to select recovery mode
2.) press the power button to actually select that option
3.) You will boot into your custom recovery
4.) EITHER Wipe Data, wipe cache, wipe dalvik, and then flash a new rom (or try re-flashing this jellybean rom you're having problems with) OR restore from a backup you have previously made (which I hope you did just incase something worse happens in the future).
You do know how to navigate through your custom recovery, right?

Cannot access flashboot / recovery - RESOLVED

Hi,
I've looked through a lot of threads but can't match the symptoms to mine (this could be a lack of knowledge on my part) so any help is appreciated.
I've previously flashed ARHD a number of times successfully including a new boot image. I flashed 9.2 today with CD Tools Suite and this was fine. I later decided that I wanted to re-flash without the CD Suite Tools and did this by going into recovery and re-flashing the ARHD zip.
The update ran successfully (per CWM) but I can't boot into it. All I get to is the HTC One white screen with a beats audio logo beneath it. I also can't get the phone to reboot into flashboot / recovery so that I can do anything with it (I've tried holding the power button and either vol up or down but this just reboots the phone and it goes back to the white screen again).
I'm sure there is a way out of this. Could anyone please help me?
Many thanks.
Hi, you wrote,
I later decided that I wanted to re-flash without the CD Suite Tools and did this by going into recovery and re-flashing the ARHD zip.
Click to expand...
Click to collapse
Did you use fastboot to flash the correct boot.img file first? It's my understanding that anytime you flash a rom you must flash via fastboot the correct boot.img file for that rom followed by erasing cache before entering recovery and flashing the rom.
Didn't someone say holding volume up & power can brick your phone?
Fastboot is volume down & power.
Press them at the exact same time, keep them held till fastboot loads up (even if it does another reboot)
Sent from my HTC One X using Tapatalk 2
phase sdeyou
Bit Banger said:
Hi, you wrote,
Did you use fastboot to flash the correct boot.img file first? It's my understanding that anytime you flash a rom you must flash via fastboot the correct boot.img file for that rom followed by erasing cache before entering recovery and flashing the rom.
Click to expand...
Click to collapse
They both use the same boot image so no need to re-flash that.
chrisjcks said:
keep them held till fastboot loads up (even if it does another reboot)
Click to expand...
Click to collapse
This was the key for me. It rebooted a couple of times then went into fastboot.
Thank you very much!

Soft bricked

Hello everyone, today I installed TWRP recovery, it went fine and I am not new to install custom roms, custom recoveries, etc. but this got my phone messed up. It was working perfectly fine and then I turned it off in the night and in the morning, it just got stuck in a bootloop, and knowing me of course, I forgot to create a backup as I installed TWRp. So, is there any kind fellow out there that has a TWRP backup at hand for the ZE551ML?
Just to get the order correct...
Flashed TWRP - No problem
Rebooted to system - No problem
System worked?
Turned off phone
Bootloop on power on?
Is this a bootloop, or does it just sit on the Asus screen? Does it get to the actual boot animation, or are you on the splash screen?
Harfainx said:
Just to get the order correct...
Flashed TWRP - No problem
Rebooted to system - No problem
System worked?
Turned off phone
Bootloop on power on?
Is this a bootloop, or does it just sit on the Asus screen? Does it get to the actual boot animation, or are you on the splash screen?
Click to expand...
Click to collapse
I am getting to the boot animation with the gears turning and then error comes up and boots me into TWRP. The problem is, the Bootloader will not come up so I can do the fastboot flashing, TWRP comes up instead. It comes up and I didn't overwrite the bootloader with TWRP. Problem is I can't access fastboot commands.
Lurkingintheshadows said:
I am getting to the boot animation with the gears turning and then error comes up and boots me into TWRP. The problem is, the Bootloader will not come up so I can do the fastboot flashing, TWRP comes up instead. It comes up and I didn't overwrite the bootloader with TWRP. Problem is I can't access fastboot commands.
Click to expand...
Click to collapse
Give me a few minutes. I'll get you a TWRP flashable boot.img zip.
Try flashing this in TWRP. You might need to sideload it onto your phone if you can't boot into system.
Harfainx said:
Try flashing this in TWRP. You might need to sideload it onto your phone if you can't boot into system.
Click to expand...
Click to collapse
Thank you. But, it won't flash, I've tried about every option now. I think I'm just going to see if I can get a replacement. 2.19 was always causing me problems to install and then now that I finally got it on my phone, I couldn't install another 2.19 on top of it or downgrade. Guess this phone is done for until CM12 gets released. Thanks for the help but it seems it can't be recovered at this point.
Lurkingintheshadows said:
Thank you. But, it won't flash, I've tried about every option now. I think I'm just going to see if I can get a replacement. 2.19 was always causing me problems to install and then now that I finally got it on my phone, I couldn't install another 2.19 on top of it or downgrade. Guess this phone is done for until CM12 gets released. Thanks for the help but it seems it can't be recovered at this point.
Click to expand...
Click to collapse
If you lurk on these forums, there are some Intel flashing tools I've seen that can help you recover from a soft brick.
I am stuck too!
I was in stock recovery and did a cache wipe. It took forever and wouldn't come out of it so i powered it off and tried booting. It got stuck on bootloop. phone is asus zenfone 2 Z00A. It is intel chipset. please help me out.
the worst part is that i cant get into fastboot or recovery modes so i am completely stuck! please help me out.
when i try to get into fastboot mode with vol up+ power key it vibrates but nothing is displayed.
if i just power it on its stuck on bootloop.
i can't get into recovery and fastboot bcoz its at the same place.
can i use adb commands or fastboot commands somehow?
i can maybe use adb reboot recovery to get into recovery and then i can do a wipe and flash new stuff.
please help me out.
UPDATE: I found out u can use adb reboot recovery while on the asus bootanimation.
i tried adb reboot recovery and now getting a flashing android sleeping bot with error!
can't use adb or fastboot commands now though
now in even bigger mess. after using adb reboot recovery, i can't get to bootanimation either.
just stuck at flashing android sleeping bot with error.
can't get to bootloader or fastboot or anything!
Please any suggestions. I'm dying here to fix it.
I have a adb backup.
i couldn't take a nandroid backup. i just entred recovery and wiped cache first. after doing that i was going to flash twrp and then using twrp take a nandroid backup and flash a custom rom. but it got stuck at cache wipe and i powered it off and the whole mess.:
Finally entered bootloader with fastboot now working!
Content and satisfied
I_am_sid said:
I was in stock recovery and did a cache wipe. It took forever and wouldn't come out of it so i powered it off and tried booting. It got stuck on bootloop. phone is asus zenfone 2 Z00A. It is intel chipset. please help me out.
the worst part is that i cant get into fastboot or recovery modes so i am completely stuck! please help me out.
when i try to get into fastboot mode with vol up+ power key it vibrates but nothing is displayed.
if i just power it on its stuck on bootloop.
i can't get into recovery and fastboot bcoz its at the same place.
can i use adb commands or fastboot commands somehow?
i can maybe use adb reboot recovery to get into recovery and then i can do a wipe and flash new stuff.
please help me out.
UPDATE: I found out u can use adb reboot recovery while on the asus bootanimation.
i tried adb reboot recovery and now getting a flashing android sleeping bot with error!
can't use adb or fastboot commands now though
now in even bigger mess. after using adb reboot recovery, i can't get to bootanimation either.
just stuck at flashing android sleeping bot with error.
can't get to bootloader or fastboot or anything!
Please any suggestions. I'm dying here to fix it.
I have a adb backup.
i couldn't take a nandroid backup. i just entred recovery and wiped cache first. after doing that i was going to flash twrp and then using twrp take a nandroid backup and flash a custom rom. but it got stuck at cache wipe and i powered it off and the whole mess.:
Finally entered bootloader with fastboot now working!
Content and satisfied
Click to expand...
Click to collapse
how did you get fastboot working? I can get into bootloader, but cant get my pc to connect with my zenfone2. can't use any adb cmd it would just say "error: can't find devices"
I_am_sid said:
I was in stock recovery and did a cache wipe. It took forever and wouldn't come out of it so i powered it off and tried booting.
Click to expand...
Click to collapse
Just a reminder to everyone, never force shutdown the Phone during a cache wipe procedure, it takes a long time but it finishes.
When I did it on my ZF2, I thought it was taking too long, but I did a search here and found out about it taking long before it was too late.
I'm glad you could recover yours. :good:
I shut mine down because it took too long. Wouldn't start up again. Had to send it in for RMA. Asus Canada reset the OS. I'll never do that again.
Sent from my ASUS_Z00AD using XDA-Developers mobile app
ikkuy said:
how did you get fastboot working? I can get into bootloader, but cant get my pc to connect with my zenfone2. can't use any adb cmd it would just say "error: can't find devices"
Click to expand...
Click to collapse
Dude you can never use adb when in bootloader.
That's why you have fastboot.
just type
fastboot devices
you will get your device.
if you don't then download intel drivers. You will get them in asus website.
if you are stuck without custom recovery i would suggest you to download system image (~1.5Gb) from asus website.
just search for asus zenfone 2 and go to official asus site. in downloads tab you should find both drivers and system image.
download the latest one.
See if you can get into stock recovery.
when in bootloader press vol down and go to recovery mode.
you will see a sleeping android bot with error.
press power key + vol down you will get a list.
choose factory reset and then after wipe is complete choose sideload from adb.
connect your phone and then in adb type
adb sideload filename.zip
obviously place file in your platform-tools folder and replace filename with whatever its name is.
it will take a while and you will get back your system.
---------- Post added at 07:37 PM ---------- Previous post was at 07:21 PM ----------
Marteicos said:
Just a reminder to everyone, never force shutdown the Phone during a cache wipe procedure, it takes a long time but it finishes.
When I did it on my ZF2, I thought it was taking too long, but I did a search here and found out about it taking long before it was too late.
I'm glad you could recover yours. :good:
Click to expand...
Click to collapse
Thanks!
It took a lot of time though.
For anyone stuck,
I first got fastboot working. and then i flashed stock recovery and boot.
got into stock recovery and sideloaded system img into it.
After it booted back into asus stock rom i unlocked bootloader, placed twrp in sdcard and got straight into fastboot again installed twrp and then did a wipe and went ahead and flashed ROM and Gapps. Working fine.
Update:
To get to bootloader:
i was stuck in a bootloop.
When at asus boot animation i connected USB cable and quickly typed
adb reboot bootloader
which seemed to work for me. Though i couldn't get into recovery.
So i had to flash stock recovery again.

Categories

Resources