I was running the latest TRON ROM from Neo with no issues for several days. Tonight, I went to use the camera and it FC'd. It kept doing it so I tried rebooting. It flashed the white screen with the green HTC logo and thats it, it won't go any farther.
I can get to recovery by pulling the battery and using the hard buttons, but recovery is not able to mount the internal or external memory. I cant backup, restore, flash a zip, or do anything really. How could this have happened? Am I bricked?
HELP!
If the phone does anything at all, it is not bricked. (The state it's in is sometimes called a soft brick, though). I believe there are two things you can do: either get an RUU (PH98IMG.zip) onto your SD with a computer (and an SD card reader EDIT: Or the Incredible you mentioned in the ROM thread), then boot up to hboot and let it flash, or try flashing a kernel (boot.img), ROM, or RUU using adb/fastboot.
If you have questions about the first of these processes, I may be able to answer them, but I probably won't be too helpful about the latter since I haven't flashed anything with adb/fastboot in quite a while.
HERE is the latest RUU, by the way.
Thanks, I'll try this out tomorrow.
s-on? Can you boot into the bootloader? Try reflashing the kernel via fastboot.
So I was able to get the latest RUU and flash it using Hboot. The phone booted up into stock. Great news!
However, I am now trying to get custom recovery installed again, but when I try to flash amon ra using "fastboot flash recovery recovery.img" I get the following error:
sending 'recovery' (7074 KB)..
OKAY [ 1.503s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.831s
trud9340 said:
So I was able to get the latest RUU and flash it using Hboot. The phone booted up into stock. Great news!
However, I am now trying to get custom recovery installed again, but when I try to flash amon ra using "fastboot flash recovery recovery.img" I get the following error:
sending 'recovery' (7074 KB)..
OKAY [ 1.503s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.831s
Click to expand...
Click to collapse
Did you re-unlock after running the RUU?
trud9340 said:
So I was able to get the latest RUU and flash it using Hboot. The phone booted up into stock. Great news!
However, I am now trying to get custom recovery installed again, but when I try to flash amon ra using "fastboot flash recovery recovery.img" I get the following error:
sending 'recovery' (7074 KB)..
OKAY [ 1.503s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.831s
Click to expand...
Click to collapse
download this zip and place it on the root of your sd card. it will flash Amon RA through hboot. no need for fastboot commands.
http://androidfilehost.com/?fid=9390248398092764223
mjones73 said:
Did you re-unlock after running the RUU?
Click to expand...
Click to collapse
Just realized that, after doing some research...DOH!
Unlocked and good to go. Thanks!
Related
This is not for my phone, but a friends...
Got an HTC EVO 3D with HBoot 1.5 that was unlocked with the HTC Unlocker Tool (from the HTC website). User had clockworkmod touch installed and tried to install ViperROM. Getting an error message (status 1) that looks like it is due to the ClockWorkMOD Touch version. He tried to downgrade the version to 5.0.2.0 and in doing so (did it from ROM Manager), he can no longer get in CWM. When booting to recovery via hboot, ROM Manager or Quick Boot, it shows the white HTC screen, then a plain black screen, then just reboots his phone back to the white HTC screen again.
Now he can't get into any CWM recovery. He's tried several different versions and can't get anything to work. I tried to flash the recovery 5.0.2.0 via fastboot and it says it was successful but it still won't boot into it.
Not sure where else to look for this one.
Just tried to flash via fastboot TWRP and no dice either. It said it was successful too.
Did you check to see if 'fastboot' is unchecked. Its in settings, power.
We're comin from a pure power source.
metalfan78 said:
Did you check to see if 'fastboot' is unchecked. Its in settings, power.
We're comin from a pure power source.
Click to expand...
Click to collapse
It is unchecked. I had todo that first. Fastboot sdes seem to be working.
Code:
C:\Program Files\Android\android-sdk\platform-tools>fastboot flash recovery y:\recovery-clockwork-5.0.2.0-shooter.img
sending 'recovery' (4726 KB)...
OKAY [ 1.187s]
writing 'recovery'...
OKAY [ 1.687s]
finished. total time: 2.875s
C:\Program Files\Android\android-sdk\platform-tools>fastboot flash recovery Y:\recovery-twrp-shooter-1.0.3.img
sending 'recovery' (5068 KB)...
OKAY [ 1.203s]
writing 'recovery'...
OKAY [ 1.703s]
finished. total time: 2.937s
Are u trying to get into recovery after starting fast boot and it not working? Or just rebooting the phone into recovery? Since there is still no s off for 1.5 the only way to get to recovery is through fastboot
Sent from my ADR6400L using Tapatalk
dachef3184 said:
Are u trying to get into recovery after starting fast boot and it not working? Or just rebooting the phone into recovery? Since there is still no s off for 1.5 the only way to get to recovery is through fastboot
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
I'm not sure that's correct.
He had CWM 5.0.2.0 that worked fine and he had the Touch CWM and it worked minus flashing ViperROM (possibly more, we did not try). He was able to launch CWM with a recovery reboot in ROM Manager, PowerButton and Quick Boot.
Holy crap this guy's phone sucks ass...
So, he flashed CWM back on 09/11/11 (which i think he was on hboot 1.4 or 1.3). He then flashed Synergy via CWM. He then tried to take an OTA update which failed but updated his hboot to 1.5. He hasn't flashed another ROM until just now.
He had the old CWM from before, and he is able to get the touch version (but it's usage is limited due to S-ON).
I'm just going to get him to flash a new ROM through fastboot and use 5.8.0.1 CWM Touch for nandroids, which still do work. I was able to get that CWM installed back on his device without a problem.
See the Guide/Flashing notes in my signature, i think it will help you out. Fyi, I've found only a few specific recovery versions work on my Hboot 1.50, Unlocked, S-On Evo3d.
I have hboot 1.5 and the only CWMs I've been able to get to boot properly are 4.0.1.4 and 5.8.0.1...the others I have tried always failed the same way yours did.
Please try the attached CWM or TWRP (both old versions/no touch screen) and tell if they work for you.....
OR
Try the touch CWM from here -> http://www.clockworkmod.com/rommanager
OR touch TWRP 2.0 from here -> http://teamw.in/project/twrp2
Current state:
Hboot 1.50 Unlocked S-ON
Boots into stock ROM
I was stuck in a boot loop and couldn't get into recovery so I relocked my phone and ran RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed.
Phone booted correctly after the RRU and was able to unlock the device. I went back and followed the instructions HERE to flash TWRP recovery. The exact same way that I had originally flashed.
When I was trying to Flash my recovery I received this:
Code:
C:\Android>fastboot flash recovery recovery.img
sending 'recovery' (5068 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.011s
1. Am I screwed?
2. What can I do to prevent this in the future?
3. How do I fix it?
franciumgoesboom said:
Current state:
Hboot 1.50 Unlocked S-ON
Boots into stock ROM
I was stuck in a boot loop and couldn't get into recovery so I relocked my phone and ran RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed.
Phone booted correctly after the RRU and was able to unlock the device. I went back and followed the instructions HERE to flash TWRP recovery. The exact same way that I had originally flashed.
When I was trying to Flash my recovery I received this:
Code:
C:\Android>fastboot flash recovery recovery.img
sending 'recovery' (5068 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.011s
1. Am I screwed?
2. What can I do to prevent this in the future?
3. How do I fix it?
Click to expand...
Click to collapse
1. No.
2. Nothing, it happens sometimes.
3. Maybe a corrupt download? Try again with a new copy of recovery.
If that doesn't work, try a different recovery.
I receive that error no matter which recovery I try.
The first file I tried in the OP was the same file that I had used when I originally started flashing. I just tried with twrp 2.0 and the same thing happens.
Code:
C:\Android>fastboot flash recovery twrp-shooter-2.0.0RC0.img
sending 'recovery' (5122 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.012s
Maybe it is time to start looking at the downgrade process.
I have been researching the white HTC screen boot loop for the past 3 days trying to figure out how to fix my Evo3d. After today i have finally given up.
On HBOOT my phone says:
*Locked*
Shooter XC SHIP S-OFF RL
HBOOT-1.50
Steps taken to try and fix:
-Flashed stock RUU and it completes, but reboots into the bootloop
-Upload PG86IMG,zip onto phone. Updates fine and reboots back into bootloop as well
-Don't have a nandroid backup and can't get into recovery anyway. When i flash recovery through CMD i get the message:
sending 'recovery' (4706 KB).
OKAY [ 1.160s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.170s
Not sure what else to do or what to try. Any help would be greatly appreciated.
Thanks
milkycoins said:
I have been researching the white HTC screen boot loop for the past 3 days trying to figure out how to fix my Evo3d. After today i have finally given up.
On HBOOT my phone says:
*Locked*
Shooter XC SHIP S-OFF RL
HBOOT-1.50
Steps taken to try and fix:
-Flashed stock RUU and it completes, but reboots into the bootloop
-Upload PG86IMG,zip onto phone. Updates fine and reboots back into bootloop as well
-Don't have a nandroid backup and can't get into recovery anyway. When i flash recovery through CMD i get the message:
sending 'recovery' (4706 KB).
OKAY [ 1.160s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.170s
Not sure what else to do or what to try. Any help would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
you still have to unlock your bootloader.... http://www.htcdev.com.... go to that site and follow the steps to unloack your bootloader... THEN try to install your roms and you should be ok ....
wloftus said:
you still have to unlock your bootloader.... http://www.htcdev.com.... go to that site and follow the steps to unloack your bootloader... THEN try to install your roms and you should be ok ....
Click to expand...
Click to collapse
Tried this and get " error: cannot load 'Unlock_code.bin' " on the last step
milkycoins said:
Tried this and get " error: cannot load 'Unlock_code.bin' " on the last step
Click to expand...
Click to collapse
Have you tried to downgrade your h-boot to 1.4? You could use the live CD or unknownforce's method (see my signature).
Sent from my ICS 3VO with Tapatalk 2
milkycoins said:
Tried this and get " error: cannot load 'Unlock_code.bin' " on the last step
Click to expand...
Click to collapse
what operating system on your computer are you using?
and just exactly how are you typing in the command?
wloftus said:
what operating system on your computer are you using?
and just exactly how are you typing in the command?
Click to expand...
Click to collapse
Okay so I got the Unlock code to work and now my phones HBOOT says:
*UNLOCKED*
SHOOTER XC SHIP S-OFF RL
HBOOT-1.50
I was able to then flash ClockWorkMod recovery and install a new rom. The install completed and when i went to reboot...
Same thing happens, white htc screen loop.
Feeling pretty hopeless right now, ha
milkycoins said:
Okay so I got the Unlock code to work and now my phones HBOOT says:
*UNLOCKED*
SHOOTER XC SHIP S-OFF RL
HBOOT-1.50
I was able to then flash ClockWorkMod recovery and install a new rom. The install completed and when i went to reboot...
Same thing happens, white htc screen loop.
Feeling pretty hopeless right now, ha
Click to expand...
Click to collapse
ok now you take the rom and open it up on your computer and extract the file boot.img
copy it to the same place where fastboot.exe and adb.exe are located
go to your phone and hold in the volume down button and press power to get to your bootloader
select fastboot
then plug it into your computer
open up a terminal window on your computer and go to the directory with fast boot and type in
fastboot flash boot boot.img
wloftus said:
ok now you take the rom and open it up on your computer and extract the file boot.img
copy it to the same place where fastboot.exe and adb.exe are located
go to your phone and hold in the volume down button and press power to get to your bootloader
select fastboot
then plug it into your computer
open up a terminal window on your computer and go to the directory with fast boot and type in
fastboot flash boot boot.img
Click to expand...
Click to collapse
Okay so i did this, flashed the boot.img and it said
sending 'boot' (3622 KB)...
OKAY [ 1.013s]
writing 'boot'...
OKAY [ 8.993s]
finished. total time: 10.007s
It completed and didnt do anything. So i just chose Reboot System in HBOOT and hoped it would restart normally, but went back to the HTC loop.
Thank you so much for your help on this i really appreciate it!
milkycoins said:
Okay so i did this, flashed the boot.img and it said
sending 'boot' (3622 KB)...
OKAY [ 1.013s]
writing 'boot'...
OKAY [ 8.993s]
finished. total time: 10.007s
It completed and didnt do anything. So i just chose Reboot System in HBOOT and hoped it would restart normally, but went back to the HTC loop.
Thank you so much for your help on this i really appreciate it!
Click to expand...
Click to collapse
go to cwm and wipe everything, that's what worked for me
milkycoins said:
Okay so i did this, flashed the boot.img and it said
sending 'boot' (3622 KB)...
OKAY [ 1.013s]
writing 'boot'...
OKAY [ 8.993s]
finished. total time: 10.007s
It completed and didnt do anything. So i just chose Reboot System in HBOOT and hoped it would restart normally, but went back to the HTC loop.
Thank you so much for your help on this i really appreciate it!
Click to expand...
Click to collapse
just like the last post says...try to boot into recovery now...wipe your dalvik cache and then reinstall the rom through recovery ...with the unlocked bootloader and s-off combo you should be ok... post back and let me know... and youre welcome
milkycoins said:
Okay so I got the Unlock code to work and now my phones HBOOT says:
*UNLOCKED*
SHOOTER XC SHIP S-OFF RL
HBOOT-1.50
I was able to then flash ClockWorkMod recovery and install a new rom. The install completed and when i went to reboot...
Same thing happens, white htc screen loop.
Feeling pretty hopeless right now, ha
Click to expand...
Click to collapse
Interesting. You used the HTC unlock method and your phone is showing s-off. I was always under the impression that the HTC method leaves you s-on.
The reason I say that is because your phone is showing symptoms of being s-on. If you use 4ext set to s-on and try to flash a GB Rom, does it work?
Sent from my ICS 3VO with Tapatalk 2
wloftus said:
ok now you take the rom and open it up on your computer and extract the file boot.img
copy it to the same place where fastboot.exe and adb.exe are located
go to your phone and hold in the volume down button and press power to get to your bootloader
select fastboot
then plug it into your computer
open up a terminal window on your computer and go to the directory with fast boot and type in
fastboot flash boot boot.img
Click to expand...
Click to collapse
wloftus said:
just like the last post says...try to boot into recovery now...wipe your dalvik cache and then reinstall the rom through recovery ...with the unlocked bootloader and s-off combo you should be ok... post back and let me know... and youre welcome
Click to expand...
Click to collapse
Man i just tried this 3 times and no luck. I dont know what else to do. This is so wild.
Hello!
I installed Munjeni's special hboot partition (to increase usable space) and wanted to update the phone back to stock (to take back to att).
The RUU utility failed with code of 152.
The partition failed.
Now the phone is "stuck" at the black HTC screen with four warning triangles in each corner.
Any ideas?
I can fastboot and issue some commands...
I am s-on, hboot 1.02.
Thanks in advance!
DanGeorges said:
Hello!
I installed Munjeni's special hboot partition (to increase usable space) and wanted to update the phone back to stock (to take back to att).
The RUU utility failed with code of 152.
The partition failed.
Now the phone is "stuck" at the black HTC screen with four warning triangles in each corner.
Any ideas?
I can fastboot and issue some commands...
I am s-on, hboot 1.02.
Thanks in advance!
Click to expand...
Click to collapse
If the bootloader is accessible, you can try grabbing the rom.zip out of the RUU (run it & let it load, then search in Windows' temporary folder for "rom.zip". If not there's probably a download somewhere), and rename it to "LIBEIMG.zip" on the root of the SD card.
Then boot into the bootloader (vol down) and it should pick it up and start flashing (might be a confirmation before it does)
Edit: Well I looked at the title again... does this mean its not accessible?
It should be if fastboot is, but I've never had the bad triangles so not completely sure..
If not, alternate option that may work: extract the hboot image from rom.zip and flash it with fastboot (if its allowed)
This is the RUU zip: http://www.mediafire.com/?tay1j415ymvukh5
drumist said:
This is the RUU zip: http://www.mediafire.com/?tay1j415ymvukh5
Click to expand...
Click to collapse
Thank you for the link. I'm downloading it now.
I can fastboot, but I'm S-on (from one of my flashes).
What's the fastboot command for flashing the hboot? Will this even let me?
I'll give this a try. Thanks again!
When I try to fastboot flash a recovery, here's what I get:
C:\Mobile\Android\Fastboot and ADB Tool>fastboot flash recovery recovery.img
sending 'recovery' (3716 KB)... OKAY [ 0.875s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 1.578s
C:\Mobile\Android\Fastboot and ADB Tool>
For hboot - does anyone have an idea which hboot I can try flashing?
WinSuk said:
If the bootloader is accessible, you can try grabbing the rom.zip out of the RUU (run it & let it load, then search in Windows' temporary folder for "rom.zip". If not there's probably a download somewhere), and rename it to "LIBEIMG.zip" on the root of the SD card.
Then boot into the bootloader (vol down) and it should pick it up and start flashing (might be a confirmation before it does)
Edit: Well I looked at the title again... does this mean its not accessible?
It should be if fastboot is, but I've never had the bad triangles so not completely sure..
If not, alternate option that may work: extract the hboot image from rom.zip and flash it with fastboot (if its allowed)
Click to expand...
Click to collapse
I'll try the hboot image and see what happens.
What's the fastboot command?
I tried:
fastboot flash hboot
and
fastboot flash boot
Both gave me an invalid signature:
C:\>fastboot flash hboot hboot_liberty_7227_1.02.0000_101104.nb0
sending 'hboot' (512 KB)... OKAY [ 0.234s]
writing 'hboot'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 0.328s
C:\>fastboot flash boot hboot_liberty_7227_1.02.0000_101104.nb0
sending 'boot' (512 KB)... OKAY [ 0.234s]
writing 'boot'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 0.328s
I had niles business rom on my phone and it kept messing up on me. so i downloaded the toolkit for s-off. After many tries i was able to get s-off. Now here is where my problem is there is no recovery on my phone now and when i try and do a fastboot in the cmd for my phone it will not write the Amon Ra recovery file. I now get this.
C:\Android\sdk-tools>fastboot flash boot boot.img
sending 'boot' (3896 KB)... OKAY [ 0.814s]
writing 'boot'... FAILED (remote: not allowed)
finished. total time: 1.130s
what should i do?
eggbert81 said:
I had niles business rom on my phone and it kept messing up on me. so i downloaded the toolkit for s-off. After many tries i was able to get s-off. Now here is where my problem is there is no recovery on my phone now and when i try and do a fastboot in the cmd for my phone it will not write the Amon Ra recovery file. I now get this.
C:\Android\sdk-tools>fastboot flash boot boot.img
sending 'boot' (3896 KB)... OKAY [ 0.814s]
writing 'boot'... FAILED (remote: not allowed)
finished. total time: 1.130s
what should i do?
Click to expand...
Click to collapse
So your trying to flash it as a boot.img? Amon Ra should be flashed as fastboot flash recovery recovery.img. Also if your on stock HBoot i think you need a modified HBoot for fastboot commands or unlocked eve on S-Off
sorry should have been
C:\Users\jamie\Desktop\Fastboot>fastboot flash recovery recovery-ra-vigor-3.15-gnm.img
sending 'recovery' (7078 KB)... OKAY [ 1.426s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 1.742s
eggbert81 said:
sorry should have been
C:\Users\jamie\Desktop\Fastboot>fastboot flash recovery recovery-ra-vigor-3.15-gnm.img
sending 'recovery' (7078 KB)... OKAY [ 1.426s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 1.742s
Click to expand...
Click to collapse
Do you have a stock HBoot? if so i think it has to be unlocked for fastboot commands even on s-off unless you have a modified Hboot that allows for fastboot commands while locked.
jon7701 said:
So your trying to flash it as a boot.img? Amon Ra should be flashed as fastboot flash recovery recovery.img. Also if your on stock HBoot i think you need a modified HBoot for fastboot commands or unlocked eve on S-Off
Click to expand...
Click to collapse
i was reading about flashing the boot image so i also tried to take the boot.img out of CleanROM Standard 4.5 and tried to flash the boot and that didnt work either
i do have s-off and i can get my phone to say FASTBOOT USB but everything i try and write to it says sending OKAY then writing FAILED ( remote: not allowed)
eggbert81 said:
i was reading about flashing the boot image so i also tried to take the boot.img out of CleanROM Standard 4.5 and tried to flash the boot and that didnt work either
i do have s-off and i can get my phone to say FASTBOOT USB but everything i try and write to it says sending OKAY then writing FAILED ( remote: not allowed)
Click to expand...
Click to collapse
Well if your bootloader is locked i would unlock it or get a modified bootloader that allows fastboot commands while locked. If those dont work then youll have to ask a dev
somehow i didnt even notice that was locked. ok got recovery on. now going to try and get a rom on it. with all this headache i almost miss my GNex but it has tons of issues
eggbert81 said:
somehow i didnt even notice that was locked. ok got recovery on. now going to try and get a rom on it. with all this headache i almost miss my GNex but it has tons of issues
Click to expand...
Click to collapse
Glad i could help :highfive:
got it all to work. Thanks
eggbert81 said:
got it all to work. Thanks
Click to expand...
Click to collapse
i didt understand much
still a newbie
first how do u know if the bootloader is locked or not
and how did u workout the problem
im having the same issue please help
& thnx:good:
When your in bootloader there will be a big pink highlight that says locked or unlocked
Sent from my ADR6425LVW using xda app-developers app
Deleted