Related
Hi, ever since last night my wife's Amaze has been stuck in a boot loop. The white HTC logo screen comes up and then it reboots and the same thing happens over and over. It was running firmware 2.14.531.3. I was able to boot into hboot and re-lock the bootloader with fastboot to flash the RUU and I flashed the latest one which is RUBY_ICS_35_S_TMOUS_2.14.531.3_R2 but still the same thing happens I even flashed it a second time but no dice. I'm really not sure what to do here. Did some other things too like take out the battery put it back in after a few minutes, charged it while the phone was off. If anyone has any ideas please help. Thank you
So no one has any ideas?
Sent from my Nexus 7 using Tapatalk 2
rock7632 said:
So no one has any ideas?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Try factory resetting in the stock recovery, then reloading the ruu via hboot.
(reboot into stock recovery from hboot, volume up and power button to bring the menu up so you can wipe the device)
Though reloading a stock ruu should wipe everything, are you getting any errors when reloading the stock ruu? And which one of the ruu files are you using to reload?
rock7632 said:
So no one has any ideas?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
You don't flash the ruu.. you need to put the file in root of ur SD and rename it to ph85img or something like that and reboot in the bootloader
Sent from my HTC_Amaze_4G using xda app-developers app
Dark Nightmare said:
Try factory resetting in the stock recovery, then reloading the ruu via hboot.
(reboot into stock recovery from hboot, volume up and power button to bring the menu up so you can wipe the device)
Though reloading a stock ruu should wipe everything, are you getting any errors when reloading the stock ruu? And which one of the ruu files are you using to reload?
Click to expand...
Click to collapse
I can try that. and no I didn't get any errors when loading the ruu. the one I did was the latest one for T-Mobile us 2.14.531.3_R2.
Perry977 said:
You don't flash the ruu.. you need to put the file in root of ur SD and rename it to ph85img or something like that and reboot in the bootloader
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
uhh yes that's what I did
Sent from my Galaxy Nexus using Tapatalk 2
rock7632 said:
I can try that. and no I didn't get any errors when loading the ruu. the one I did was the latest one for T-Mobile us 2.14.531.3_R2.
uhh yes that's what I did
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Did you try different kernel?
Sent from my HTC_Amaze_4G using xda app-developers app
Perry977 said:
Did you try different kernel?
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
RUU flashed the stock kernel when he reloaded.
Dark Nightmare said:
RUU flashed the stock kernel when he reloaded.
Click to expand...
Click to collapse
yeah and even prior to that I had the stock kernel
Sent from my Nexus 7 using Tapatalk 2
rock7632 said:
yeah and even prior to that I had the stock kernel
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Do u still have the custom recovery?
Sent from my HTC_Amaze_4G using xda app-developers app
Are you s-off? SuperCID? you need to set both back to the original values and reflash stock ROM from bootloader.
Perry977 said:
Do u still have the custom recovery?
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
no i flashed the stock recovery before i loaded the RUU.
olegy said:
Are you s-off? SuperCID? you need to set both back to the original values and reflash stock ROM from bootloader.
Click to expand...
Click to collapse
I'm s-on
Sent from my Nexus 7 using Tapatalk 2
rock7632 said:
no i flashed the stock recovery before i loaded the RUU.
I'm s-on
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Even if, you didn't need to reflash anything, apparently the fact that the ruu wipes and restores everything to stock still hasn't sunk in yet, anyways, we're missing some info here, what else happened before this issue that you're not telling me, since bootloop issues are easily resolved by a stock reload via hboot but yours seems to be on the same loop no matter what, are you giving it the time to boot after reloading via hboot? First boot takes a bit of time, patience is very vital.
Dark Nightmare said:
Even if, you didn't need to reflash anything, apparently the fact that the ruu wipes and restores everything to stock still hasn't sunk in yet, anyways, we're missing some info here, what else happened before this issue that you're not telling me, since bootloop issues are easily resolved by a stock reload via hboot but yours seems to be on the same loop no matter what, are you giving it the time to boot after reloading via hboot? First boot takes a bit of time, patience is very vital.
Click to expand...
Click to collapse
Ya like he^^ said, it does take a very long to boot up after flashing an ruu, could take a good 10 mins or maybe more...
Now if you did wait and it still just bootlooped after flashing the ruu, either the ruu is bad, or u did something wrong, OR u got some serious software problems going on
Due to the fact, atleast from reading your first post, it sounds like it was running fine then suddenly just started bootlooping. And then flashing an ruu didn't fix it. Sounds to me like ur phone has some serious issues
sent from my NRGized Amaze,
powered by faux kernel v.13
Dark Nightmare said:
Even if, you didn't need to reflash anything, apparently the fact that the ruu wipes and restores everything to stock still hasn't sunk in yet, anyways, we're missing some info here, what else happened before this issue that you're not telling me, since bootloop issues are easily resolved by a stock reload via hboot but yours seems to be on the same loop no matter what, are you giving it the time to boot after reloading via hboot? First boot takes a bit of time, patience is very vital.
Click to expand...
Click to collapse
That's just it, after loading the ruu via hboot the phone asks for a reboot and when I do it it barely takes 5 seconds on the HTC logo white screen then the phone reboots again and the same thing happens. And as far as anything happening before, nothing really happened. The battery died a couple of days ago and the when we charged it and tried to turn on the phone this started happening
Sent from my Galaxy Nexus using Tapatalk 2
I've tried everything I could think of. Loaded 2 different ruu's, manually wiped everything from recovery and nothing has worked, its still doing the exact same thing. I really don't understand how it can be bricked just out of nowhere
Sent from my Nexus 7 using Tapatalk 2
rock7632 said:
I've tried everything I could think of. Loaded 2 different ruu's, manually wiped everything from recovery and nothing has worked, its still doing the exact same thing. I really don't understand how it can be bricked just out of nowhere
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I think Im having an issue similar to yours. Is there any interaction after it begins to flash the RUU? I found a video for the thunderbolt where it asks you to approve the update before it finishes. My phone does the update then jumps back to the fastboot screen.
I seem to be stuck in the bootloader.
This is what happened. Was running Bootloader 1.4 S-OFF via Revolutionary, tried updating Firmware following this:
http://forum.xda-developers.com/showthread.php?t=1808150
Downloaded Stock Firmware zip put it on my MicroSD card, rebooted the phone into Bootloader ran the update. Rebooted phone after the update into the bootloader and now it keeps loading up the update and says "Do you want to Start Update?"
So now I'm unable to get into recovery to flash a new ROM as I'm having bootloops.
Best is if you have an alternate micro sd card reader on a computer. Pull the sd, Change the pgm86 file to a different name, address any other files you need such as a rom, then replace.
Sent from my PG86100 using Tapatalk 2
greeg32 said:
Best is if you have an alternate micro sd card reader on a computer. Pull the sd, Change the pgm86 file to a different name, address any other files you need such as a rom, then replace.
Sent from my PG86100 using Tapatalk 2
Click to expand...
Click to collapse
Ya, this is what I figured I would need to do. Is there any other alternatives to this?
Take out the battery and put it back in and restart your phone normally or don't reboot, boot into recovery after firmware flash and reboot from recovery
Sent from my HTC EVO 3D X515m using xda premium
flashallthetime said:
Take out the battery and put it back in and restart your phone normally or don't reboot, boot into recovery after firmware flash and reboot from recovery
Sent from my HTC EVO 3D X515m using xda premium
Click to expand...
Click to collapse
I'm unable to start it normally because of bootloops unfortunately. So currently the only thing I can access seems to be the Bootloader which is instantly asking me to update, or reboot.
dmasteRR said:
I'm unable to start it normally because of bootloops unfortunately. So currently the only thing I can access seems to be the Bootloader which is instantly asking me to update, or reboot.
Click to expand...
Click to collapse
If you hit volume down, it should cancel the update, then you can reboot into recovery
Sent from my PG86100 using xda app-developers app
Can I ask are you gsm or cdma? I believe cdma so atleast you haven't flashed the wrong firmware
Sent from my HTC EVO 3D X515m using xda premium
Pop out the sd and remount it after you go into recovery? assuming u have it available...
if not, take out the card, use fastboot from the computer to boot a recovery image and proceed from there?
Just like what the subject line says "I cannot boot into 4ext recovery." i tried re flashing 4ext using Hasoons tool but it still does not work. I tied booting into recovery but it just leads me into the white HTC logo.
I know flashing two ROMS on top of each other was a bad idea. I flashed nightmare 1.6 and cm10 on top of that then i just started having problems. I tried going into recovery in order to flash my backup but failed because I cannot even access it. BTW i can still boot into OS but cannot do anything because it keeps saying HTC sense has stopped working. I cannot go pass the lock screen. If anyone has come into this problem please help me. IDK if my phone is bricked or not. =(
Power off, pull the battery. Whole down the the power and the volume down button then select RECOVERY. tell us what happens.
Sent from my HTC_Amaze_4G using xda app-developers app
No your phone is not bricked.
Are you S-Off ??
Beamed from my HTC Amaze 4G using xda premium
Lol that's funny
Sent from my HTC_Amaze_4G using xda app-developers app
lamortcroix said:
Power off, pull the battery. Whole down the the power and the volume down button then select RECOVERY. tell us what happens.
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
Well when i did that the phone tries to go into recovery then it just shuts off. Then it re boots again into the white htc logo and just stuck there.
anasmunir said:
No your phone is not bricked.
Are you S-Off ??
Beamed from my HTC Amaze 4G using xda premium
Click to expand...
Click to collapse
I am on S-on
That's weird. Your last option ever would be to Flash RUU. Hmm, you can use Hasoon's tool kit but you need to download the latest .img unless someone else has a better idea. Or if anything flash a different recovery(say clockworkmod) just so you can just wipe data and boot into the OS to re flash 4ext. And if you can't boot into the OS then re flash the last ROM whose boot.img you over wrote.
I think. But if you do go with the RUU you might wanna take the time to S-OFF.
Sent from my HTC_Amaze_4G using xda app-developers app
lamortcroix said:
That's weird. Your last option ever would be to Flash RUU. Hmm, you can use Hasoon's tool kit but you need to download the latest .img unless someone else has a better idea. Or if anything flash a different recovery(say clockworkmod) just so you can just wipe data and boot into the OS to re flash 4ext. And if you can't boot into the OS then re flash the last ROM whose boot.img you over wrote.
I think. But if you do go with the RUU you might wanna take the time to S-OFF.
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
I did try to flash clockwork and also TWRP but its still the same scenario. I will try to s-off and install the new RUU.
radsuara8591 said:
I did try to flash clockwork and also TWRP but its still the same scenario. I will try to s-off and install the new RUU.
Click to expand...
Click to collapse
I tried going S-off but now the phone wont even go to the OS. Do you another suggestion?
Flash the RUU first. Then S-OFF if you want to.
Sent from my HTC_Amaze_4G using xda app-developers app
lamortcroix said:
Flash the RUU first. Then S-OFF if you want to.
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
Thanks. I did what you said and flashed the RUU. When I did that it seem to work and now my problem is fixed. Now just have to flash my back up. Thank you for the help
lamortcroix said:
Power off, pull the battery. Whole down the the power and the volume down button then select RECOVERY. tell us what happens.
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
I have a Desire HD and it won't boot. It just gets stuck with the Jelly Time logo. Upon trying to boot into RECOVERY by holding down the volume and power button, the screen turns black and the power LED blinks. Anyone have any ideas? Help is appreciated.
raczyk said:
I have a Desire HD and it won't boot. It just gets stuck with the Jelly Time logo. Upon trying to boot into RECOVERY by holding down the volume and power button, the screen turns black and the power LED blinks. Anyone have any ideas? Help is appreciated.
Click to expand...
Click to collapse
Yes, post this in the desire hd section.
Sent from my Nexus 7 using xda premium
Hi all,
I'm very new to this all, and read a lot of your threads.
But still, I haven't got a clue what is wrong.
Earlier this day I was in my recovery (TWRP), and now I can't acces it. (HBOOT - recovery). It just shuts down when I try to acces.
Also , my sd card isnt visible on the PC.
Pff, i'm getting crazy over here, seemed a good idea to root my phone, but bah, can't seem to work it out.
Please help me fellas, thanks a lot.
Peter.
fastboot erase cache
Then enter the recovery.
Sent from my HTC One X+ using Tapatalk 4
sixcarnage said:
fastboot erase cache
Then enter the recovery.
Sent from my HTC One X+ using Tapatalk 4
Click to expand...
Click to collapse
Thanks a lot for the reply man, but can you give some more information?
I'm a noob, a total noob in this.
I only see 4 options:
HBOOT
REBOOT
REBOOT BOOTLOADER
POWER DOWN
Thanks man.
If you see those options you are in fastboot mode.
Now plug in to the computer and open command or terminal.
Make sure you have the adb and fastboot tools from android sdk.
In the cammand window type fastboot erase cache. Wait till it says it's done.
On the phone go to hboot and then recovery.
Sent from my HTC One X+ using Tapatalk 4
kreatiir said:
Thanks a lot for the reply man, but can you give some more information?
I'm a noob, a total noob in this.
I only see 4 options:
HBOOT
REBOOT
REBOOT BOOTLOADER
POWER DOWN
Thanks man.
Click to expand...
Click to collapse
select HBOOT and then you can chose RECOVERY
sixcarnage said:
If you see those options you are in fastboot mode.
Now plug in to the computer and open command or terminal.
Make sure you have the adb and fastboot tools from android sdk.
In the cammand window type fastboot erase cache. Wait till it says it's done.
On the phone go to hboot and then recovery.
Sent from my HTC One X+ using Tapatalk 4
Click to expand...
Click to collapse
Thanks man, I did that, but still no succes.
It even shuts my phone down when I try to acces recovery mode.
When I acces my phone, I don't have service nor I can acces wifi (the airplane mode is always on, shutting himself down).
Would be great if I know how to get back to the old system.
Never trying this again hehe
Flash the recovery again and make sure it's the right one. Then try the steps again.
Sent from my HTC One X+ using Tapatalk 4
sixcarnage said:
Flash the recovery again and make sure it's the right one. Then try the steps again.
Sent from my HTC One X+ using Tapatalk 4
Click to expand...
Click to collapse
Did it, but no succes.
I also can't acces the sd card on my computer, I feel like i'm missing a step.
I've been over and over the guide, so I really don't have a clue.
Ok.
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot erase cache
Enter the recovery.
Sent from my HTC One X+ using Tapatalk 4
sixcarnage said:
Ok.
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot erase cache
Enter the recovery.
Sent from my HTC One X+ using Tapatalk 4
Click to expand...
Click to collapse
I'm doing this in HBOOT mode and with the cmd prompt, but I get this error:
unknown partition 'recovery.img'
error: cannot determine image filename for 'recovery.img'
I'm so sorry man, these questions must drive you bloody crazy.
Thanks a lot for helping me out though..
Peter
sixcarnage said:
Ok.
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot erase cache
Enter the recovery.
Sent from my HTC One X+ using Tapatalk 4
Click to expand...
Click to collapse
I've downloaded a recovery from here at XDA (don't know it's the right one?)
I've got an IMG file in my root of C.
C:\recovery5.5.0.4, any idea how to write that down in cmd?
Thanks.
You must be in fastboot mode
Some might say I'm crazy already so..
Sent from my HTC One X+ using Tapatalk 4
---------- Post added at 02:03 PM ---------- Previous post was at 02:01 PM ----------
Do you have international ?
Sent from my HTC One X+ using Tapatalk 4
sixcarnage said:
You must be in fastboot mode
Some might say I'm crazy already so..
Sent from my HTC One X+ using Tapatalk 4
---------- Post added at 02:03 PM ---------- Previous post was at 02:01 PM ----------
Do you have international ?
Sent from my HTC One X+ using Tapatalk 4
Click to expand...
Click to collapse
I don't know, I guess?
I'm living in belgum.
Yup. Here's the international twrp
http://techerrata.com/browse/twrp2/enrc2b
Sent from my HTC One X+ using Tapatalk 4
sixcarnage said:
Yup. Here's the international twrp
http://techerrata.com/browse/twrp2/enrc2b
Sent from my HTC One X+ using Tapatalk 4
Click to expand...
Click to collapse
Alright, got the first step ready, but what boot.img do I have to mount?
Peter.
The Rom that you are on has a boot.img in the zip. Flash that.
Sent from my HTC One X+ using Tapatalk 4
sixcarnage said:
The Rom that you are on has a boot.img in the zip. Flash that.
Sent from my HTC One X+ using Tapatalk 4
Click to expand...
Click to collapse
Where can I find that zip?
If your stock you need to find the stock boot.img
Sent from my HTC One X+ using Tapatalk 4
sixcarnage said:
If your stock you need to find the stock boot.img
Sent from my HTC One X+ using Tapatalk 4
Click to expand...
Click to collapse
How? I don't know how to acces my SDcard man.
kreatiir said:
How? I don't know how to acces my SDcard man.
Click to expand...
Click to collapse
Download root browser or something similar to browse the SD card.
Sent from my HTC One X+ using Tapatalk 4
Hello everyone,
I rooted my One X+ a while ago. I have now relocked the bootloader for OAT purpose. The update was downloaded to the phone, but the update progress would not get pass the bootloader.
I learnt quite a lot about similar problems via various threads. It seems like a problem with the recovery, or rather the recovery is not present, because I am not able to go into the recovery from the bootloader.
I have tried to search a correct stock recovery image but have not had any luck for a while now.
Any advice would be much appreciated: am I right in assessing that the problem is with the recovery? or it is actually something else that I need to fix.
The software version is 1.17.206.1, cid is O2__001. HBoot 1.35.
Many thanks...
Look in the TWRP thread in original Android dev. I'm sure Lloir posted a stock recovery for both the International & AT&T devices
Sent from my HTC One X+ using Tapatalk
AndroHero said:
Look in the TWRP thread in original Android dev. I'm sure Lloir posted a stock recovery for both the International & AT&T devices
Sent from my HTC One X+ using Tapatalk
Click to expand...
Click to collapse
Thanks for pointing this out. Am I right in thinking that a specific stock recovery corresponding to the software version and cid would be needed? because I have actually tried flash the international version of the TWRP recovery as well as the CWM recovery, but neither made a difference to resovling the symptom.
No any international stock recovery will do. There all the same. Have you tried erasing /cache/ before and after you flash recovery? You can use the command "fastboot erase cache"
Sent from my HTC One X+ using Tapatalk
AndroHero said:
No any international stock recovery will do. There all the same. Have you tried erasing /cache/ before and after you flash recovery? You can use the command "fastboot erase cache"
Sent from my HTC One X+ using Tapatalk
Click to expand...
Click to collapse
Thanks for the tip off. I have just tried it but it didn't make a difference. Running the update from the phone still rebooted straight to the bootloader, and recovery is not accessible from the hboot menu either.
It could be a corrupt misc partition. This kind of error is usually fixed by running an RUU. Do you know if there is one for you CID/Hboot version?
Sent from my HTC One X+ using Tapatalk
AndroHero said:
It could be a corrupt misc partition. This kind of error is usually fixed by running an RUU. Do you know if there is one for you CID/Hboot version?
Sent from my HTC One X+ using Tapatalk
Click to expand...
Click to collapse
Thanks. I thought of this approach too, but my search for a correct RUU (i.e. O2 UK, software version 1.17.206.1) has not been fruitful. I did try an unmatched RUU (Europe_1.17.401.1) but it understandably failed.
Just a quick thought tho, the recovery images that I tried were both flashed successfully; i.e. no error messages. This seems to suggest that data were written into the disk successfully. But I am very puzzled...