Hello,
I was trying to return my phone to stock, I ran a RUU (latest out there from shipped roms) which gives me a error 110 after the install. It lays down the rom it appears because if I used the ADB command "fastboot oem boot" I can actually use the phone, If I turn off the phone and turn it back on trying to boot up normal I get the HTC logo with the triangles on each side like my boot up script is screwed.
Anyone know how to fix this?
Please help!!
Any solution
I am having the exact same problem with my magic 32A, and was just wondering if you have a solution to the problem ?
Same situation here, mate. Anyone have some guidance?
Did you try flashing a stock pc36img.zip? If you can get your hBoot to come up that should fix it
Found a fix! Some reported this to not work, but it worked the first time for me.
http://forum.xda-developers.com/showpost.php?p=8487229&postcount=37
Related
While once again needlessly flashing stuff on my phone I lost SMS with the Cyanogen6 Snap kernel with Snap Turbo. From what I read I decided I had to reflash a stock rom to regain my ability to receive SMS. A flash of the update file has left me stuck in the bootloader. I had thought I good having used Unrevoked a few weeks ago. My Hboot was updated and is -S. When I turn the phone on it gets stuck on the white htc screen. Same when I try to boot into recovery. So I need to know how to reflash my phone with a stock rooted rom so I can start over. Shell commands work for fastboot but I am getting remote:not allowed responses when I try and flash recovery.
Please can you help me? I am going to sleep and letting the Evo get a full charge. Please do not delete this and link me to a solution.
Came here for the same, Did you fix this? my problem got worse, since adb doesn't seem to recognize the device, and none of Caulkin's methods here: seemed to work either. Somehow, along the way, Clockworkmod recovery got lost too, and I can't even flash a different rom.
shogun26 said:
Came here for the same, Did you fix this? my problem got worse, since adb doesn't seem to recognize the device, and none of Caulkin's methods here: seemed to work either. Somehow, along the way, Clockworkmod recovery got lost too, and I can't even flash a different rom.
Click to expand...
Click to collapse
I'd like to add a "me too" here.
I'm stuck with only fastboot available for getting the phone to work again.
I have a nandroid backup on my PC, that I could put on it. But I don't know the
fastboot command to use, or if there's even one available to use for a nandroid.
I also have a complete PC36IMG.zip. But again, I don't know the fastboot command
to use, or whether it's even possible.
Please help.
Thank you.
--Chris
I have the SAME PROBLEM! What's going on guys? Any fix?
I hope someone in this community is able to help. I've already been scouring Google this morning for people with a similar issue and haven't been successful in getting my phone to come back so I suspect there may be a hardware issue.
Here's a summary of the problem:
My phone shutdown this morning while I was listening to a podcast. It got stuck in a boot loop at the splash screen, constantly rebooting itself. A battery pull would not solve the problem. I was able to get it into HBOOT (version 0.92) but when I tried going into recovery from there, It got stuck on the splash screen (no looping). Before all this I had been running Nils Business Gingersense for quite a while and things were working fine, in case anyone needs that detail.
After failing to boot to recovery, here are some of the things I have tried to fix this issue:
1. Factory reset in HBOOT
2. Flashed RUU 2.2 and then tried RUU 2.3.4 through HBOOT. Though neither of these would get the phone to come up, the splash screen reboots stopped and the phone just freezes in splash screen now (over 30 minutes with no change).
3. Tried to reflash CWM 5.0.2.0 through Fastboot. Although the phone is recognized by 'fastboot device', it says 'remote: not allowed' when try to flash the .IMG file.
4. Tried to flash an older CWM recovery from when I originally rooted my phone --same 'not allowed' error
5. Ran the official RUU for Froyo on my PC and it looked promising but I never got past the splash screen afterward a reboot.
6. I don't know a ton about ADB but ADB does not recognize my device even though Fastboot does.
At this point I'm not sure what else to try. It seems promising that I can get into HBOOT and that Fastboot will recognize my phone but what can I do with that now?
Thanks for any ideas you might have.
Have you tried flashing cwm thru hboot as a PB31IMG.zip? http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip. If that dosent work you could try to update hboot to 1.02 and htcdev unlock it. This will allow extended fastboot commands. You can do this on the htcdev website. Or you could downgrade hboot to the 0.77 engineering bootloader http://dinc.does-it.net/Hboots/ENG_Hboot_0.77/PB31IMG.zip which basicly does the same thing, and might be a better option than upgrading. You are s-off right?
Yes, I still have S-OFF. I did try flashing several recoveries through hboot and they all acted like they updated fine but I wasn't able to boot into any of them because I kept getting frozen at the white screen after choosing recovery from hboot. I will try another hboot and see if that makes any difference. Thanks.
Cmlusco, I tried the CWM version you posted with hboot .92 and .77 but had no luck. I also tried walking through the hboot upgrade steps on the htcdev site but I couldn't get the RUU exe to find my phone. This is odd because an older RUU found the phone just fine earlier today.
Friend sent me his phone after trying to update to CM and it's getting stuck on the HTC White boot screen. Not sure if it is rooted or not, but was in the processes of rooting when it broke.
Phone is:
HTCDev unlocked
S-On
HBOOT-0.98.0000
RAIDO-1.09.01.0312
Phone will not:
Boot into recovery - HTC White screen
Boot normally - HTC White screen
Update with stock RUU - Bar on the right side fills up and goes back to normal bootloader screen.
Update new recovery - States it takes it but gets stuck on HTC white screen.
ADB Will not show device with "adb devices"
"fastboot oem lock" "FAILED (status read failed (Unknown error)) - "fastboot devices" does find device.
Factory reset - locks up bootloader.
"fastboot clear cache" runs for 30+ minutes phone is unresponsive.
That is about the only information I have any one got any ideas besides use it for a personal safety device and throw it at people?
TheHeffNerr said:
Friend sent me his phone after trying to update to CM and it's getting stuck on the HTC White boot screen. Not sure if it is rooted or not, but was in the processes of rooting when it broke.
Phone is:
HTCDev unlocked
S-On
HBOOT-0.98.0000
RAIDO-1.09.01.0312
Phone will not:
Boot into recovery - HTC White screen
Boot normally - HTC White screen
Update with stock RUU - Bar on the right side fills up and goes back to normal bootloader screen.
Update new recovery - States it takes it but gets stuck on HTC white screen.
ADB Will not show device with "adb devices"
"fastboot oem lock" "FAILED (status read failed (Unknown error)) - "fastboot devices" does find device.
Factory reset - locks up bootloader.
"fastboot clear cache" runs for 30+ minutes phone is unresponsive.
That is about the only information I have any one got any ideas besides use it for a personal safety device and throw it at people?
Click to expand...
Click to collapse
Not exactly sure because I didn't use the HTC DevUnlucky/Unlock, but you can try to S-Off with this: http://forum.xda-developers.com/showpost.php?p=28290187&postcount=2 and see if you can flash a custom rom after gaining S-Off. If you have tried that you will have to wait on someone with a little more experience can help you.
ThePhantom97 said:
Not exactly sure because I didn't use the HTC DevUnlucky/Unlock, but you can try to S-Off with this: http://forum.xda-developers.com/showpost.php?p=28290187&postcount=2 and see if you can flash a custom rom after gaining S-Off. If you have tried that you will have to wait on someone with a little more experience can help you.
Click to expand...
Click to collapse
Oops forgot to put that in there. I've tried the revo s-off but as far as I know the device needs to boot into android to take it. It just sits there waiting for device when I run it. And that needs HBOOT 97 and I'm unable to downgrade
TACOROOT needs ADB and I can't connect with ADB
TheHeffNerr said:
Oops forgot to put that in there. I've tried the revo s-off but as far as I know the device needs to boot into android to take it. It just sits there waiting for device when I run it. And that needs HBOOT 97 and I'm unable to downgrade
TACOROOT needs ADB and I can't connect with ADB
Click to expand...
Click to collapse
Ah, sorry m8, you will have to wait on one of the other more knowledgeable guys jump on to give better advise.
All good, thanks for giving it a shot. If it would lock again stock RUU might work... but no this device hates me lol.
ThePhantom97 said:
Ah, sorry m8, you will have to wait on one of the other more knowledgeable guys jump on to give better advise.
Click to expand...
Click to collapse
Any ideas?
I'm no expert but try re downloading the ruu with the hboot 97 and try it again if you haven't already maybe it was a bad download. I remember when I downgraded mine I tried 3 different files before I got it to work. If you can't find any other ruu flies I'll look on my PC tomorrow and see if I still have the one I got to work and if you're transferring the file to the sd card from a PC leave off the
.zip or it will name it .zip.zip
Sent from my Incredible 2 using xda app-developers app
I think because I can't relock the boot loader it won't let me flash a RUU. But if you could upload the one you got to work that would be amazing none that I find work even with redownloading them
ps I hate that spider....
If the person is htc dev unlock they need to flash a kernal via fastboot for the phone to boot. That's more than likely the reason they are bootlooping. There is a thread in android development about how to flash via htc dev unlock. I would have them read that and proceed.
TheHeffNerr said:
Friend sent me his phone after trying to update to CM and it's getting stuck on the HTC White boot screen. Not sure if it is rooted or not, but was in the processes of rooting when it broke.
Phone is:
HTCDev unlocked
S-On
HBOOT-0.98.0000
RAIDO-1.09.01.0312
Phone will not:
Boot into recovery - HTC White screen
Boot normally - HTC White screen
Update with stock RUU - Bar on the right side fills up and goes back to normal bootloader screen.
Update new recovery - States it takes it but gets stuck on HTC white screen.
ADB Will not show device with "adb devices"
"fastboot oem lock" "FAILED (status read failed (Unknown error)) - "fastboot devices" does find device.
Factory reset - locks up bootloader.
"fastboot clear cache" runs for 30+ minutes phone is unresponsive.
That is about the only information I have any one got any ideas besides use it for a personal safety device and throw it at people?
Click to expand...
Click to collapse
go to bootloader and flash your kernel (stock kernel/custom kernel )
you can get it from your rom.zip
the command would be
fastboot flash boot boot.img
hehehehe i answered after 3 years ! im sure youve solved the problem !
A week or so after upgrading from Pacman v15 to v15.3 I began having my phone drop into roaming for a really long time. I restarted my phone to see if it would fix the issue, and I got a bootloop, nothing past the white HTC screen I had issues flashing to fastboot, so I got a new unlocktoken and now I can flash. At least... it will send, write, and "okay" me on it, but then nothing will work. I will "successfully" flash a recovery (i've tried twrp and cwm) and then when I try and get into them through bootloader it just sends me on the same old bootloop.
Please help... I guess I should flash an RUU but I've never done that before, and I'm curious as to whether or not this will even work since nothing else is "taking."
UPDATE... DL'ed the RUU and followed directions of...
flashing recovery_signed.img
fastboot oem lock
then running RUU in fastboot usb.
Everything SEEMED to take fine, and then when I go to reboot I get a loop again. grr...
hi,
can anyone please advise how to recover a Fire phone stuck in fastboot as in my attached photo ?
I have read the forums, but cannot find a solution to my specific problem, the nearest thing was this unresolved thread:
http://forum.xda-developers.com/fire-phone/help/fire-phone-stuck-fastboot-how-to-recover-t3171944
at this time I'm not bothered what OS it was on before the fault, nor what OS or Rom I may be have to use to get it up and running again.
thanks,
Kevin
same problem
I also get same problem with my Fire Phone 3.6.8 GSM unlocked since March, still don't know how to solve, somebody, Please Help!!!!
Are you able to boot in to recovery?
Connected to a computer with adb fasfboot use following command: 'fastboot reboot recovery'
In recoverymode choose sideload via adb and flash stock rom with adb sideload 'stockrom'.zip
Is this resolved or not I am facing same issue never even rooted/installed stock rom on that device