I just flashed this rom http://forum.xda-developers.com/showthread.php?t=2752956 (odexed) but something went wrong and the phone won't boot. I
If i let it boot past the bootloader, all i get is a dark screen. I can tell the screen is on but nothing else happens. If i reboot with volup/power and then press voldown I only get the hboot screen. Pc does not recognize the phone in ether mode. HTC sync just says no device connected as well as adb commands. cmd promts just get stuck on "waiting for device"
Any help would be appreciated
ok, i was able to fix it. I hadn't tried adb while on the blank screen. It responded to adb commands then and was able to reboot into recovery that way. This thread can be deleted or left for future reference.
Thanks Alliance!!!
Related
Hi,
I hope someone here can help me! I was trying to upgrade the recovery image and radio on my UK Orange HTC Hero but something has gone horribly wrong.
The phone no longer boots any further than the "HERO" logo splash screen. I've tried leaving it for 10mins+ but no change.
I can't get to the recovery menu
If I have the USB cable plugged in and hold down HOME while putting in the battery in, it shows "FASTBOOT USB" in red at the top left
I've tried using fastboot to flash/update/updateall/boot various signed images but all return "Remote: not allow"
I've tried various RUU recoveries which all seem to work up until the phone tries to reboot into bootloader mode and then just hang with "Waiting for bootloader"
Is it bricked? :-(
Thanks,
Paul
Some more info...
Using fastboot getvar I've got the following version numbers:
Bootloader: 1.76.0007
Baseband: 6.35.09.26
Main: 2.73.61.5
cid: ORANG00§♠Å
Try this
Try booting without the SD card in. Worked for me once.
Nope, still no joy
A logcat would be good.
Sorry, should have been a bit clearer.
The phone doesn't boot, it hangs at the HERO splash screen and won't even enter recovery mode - therefore no ADB access.
All I have access to is fastboot, but anything I try and flash from fastboot fails with "Remote: not allow", presumably because my SPL won't allow fastboot stuff.
Unless there is another way of doing a logcat?
If you are able to get to the fastboot screen then can you still get to the stock recovery and reset your factory then see what happens.
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
How would I do that?
Holding down Home while powering on just hangs on the Hero splash screen too.
Thanks!
Edit:
I've also tried VOL-DOWN + Trackball + Power to enter the bootloader, nothing - again it just hangs on the HERO splash screen
A shameless bump...
Anyone have any ideas?
I've tried making a goldcard but I'm not sure how it's going to help.
pejaym said:
A shameless bump...
Anyone have any ideas?
I've tried making a goldcard but I'm not sure how it's going to help.
Click to expand...
Click to collapse
If you have a gold card you should be able to flash any of the HTC hero rru exe files.
That's what I thought.
Same as before though, the RUU detects the phone/versions but when it goes to flash it, the phone reboots but instead of going to the bootloader it goes straight back to the HERO logo splash with "FASTBOOT USB" in red in the top left corner (ie: What it was like when starting the RUU procedure, and all I ever see).
That's when the RUU says "Waiting for bootloader..." and eventually times out.
I've also tried extracting the RUU rom.zip and flashing that manually with fastboot (with and withhout the goldcard in place) but that doesn't work either. If I just do the rom.zip it says invalid signature (like it doesn't detect it as a valid ZIP).
If I extract the various .img files from the ZIP and try and fastboot flash them individually then I get the "remote: not allow" with or without the goldcard.
Any luck... I'm in the same situation... trapped in the fastboot..
I found the solution!
Downloaded the RUU (ftp://xda:[email protected]_2.73.405.5_WWE_release_signed_NoDriver.exe) and while in fastboot usb run the wizard!
And the hero is working again!
Sorry but you'd bricked your phone I think.
I was on Neutrino 2.5, I flashed to 2.5p (without wiping).
It wasn't working as I wanted so I went in to recovery to reflash the google apps zip.
After that I'm now stuck in a boot cycle loop and I can't even boot in to recovery mode. When I try to enter recovery it says "Entering Android Recovery Mode" then the screen just goes blank.
Really sorry to make this my first post but I'm kinda freaking out right now. Don't have any idea how to recover from this.
rodabi said:
I was on Neutrino 2.5, I flashed to 2.5p (without wiping).
It wasn't working as I wanted so I went in to recovery to reflash the google apps zip.
After that I'm now stuck in a boot cycle loop and I can't even boot in to recovery mode. When I try to enter recovery it says "Entering Android Recovery Mode" then the screen just goes blank.
Really sorry to make this my first post but I'm kinda freaking out right now. Don't have any idea how to recover from this.
Click to expand...
Click to collapse
flash the recovery again using fastboot
Thanks for the reply. So my problem so is that I'm trying to boot in to RSD mode but it get the message "Battery is too low to flash".
I'm trying to charge the battery but whenever i plug it in to charge phone starts up and ends up in the boot cycle, and the battery doesn't end up charging.
How can i force the phone not to turn on when I plug it in to the wall charger?
Ok, I was able to McGyver a usb charger from an old cable and I got the battery charged enough where it would enter fastboot.
However... now I can't get either of my laptops to recognize the phone in fastboot.
I attach the phone to the usb port, turn the phone on and hold the volume down button. I press the volume up button when fastboot appears, the message "Starting Fastboot protocol support" appears and then nothing happens. Windows just sits there, the phone just sits there...
If I do moto-fastboot devices at the command prompt there is no serial.
Any thoughts?
Well, normally nothing happens until you issue a fastboot command. I usually boot into fastboot mode first, THEN connect the phone & open a command line, etc.
What happens if you do the above and type "fastboot devices"? Does it see your phone then?
Ok, so I tried your method, and installing some different windows drivers and now windows does recognize the phone!
For the record, I am on windows xp and currently i'm using driver version 2.0.40 (same problem with 2.0.53).
Now windows isn't able to install the fastboot drivers, it comes up as an unrecognized device. Is there a way to manually install the fastboot drivers?
Although it's recognized by windows, issuing the moto-fastboot devices command still returns blank.
Should I be able to find my adb device while my phone is only booting to HBOOT 0.93.0001?
Been stuck on this for days...and it's killing me!
PS. When I plug my phone in to
PC it says "Android ADB interface installed" "Ready to use"
But when I cmd the adb to find devices "adb devices" it shows blank
P.S. Phone: HTC Desire
Unrooted
S-ON
Unable to boot, can only get to HBOOT.(so cant turn debugging on)
Trying to get a goldcard to flash a new rom and see if i can unbrick
Reason for unable to boot is - It had been rebooting itself for weeks, slowly getting worse, until now, when I cant get it booted at all.
budron said:
Should I be able to find my adb device while my phone is only booting to HBOOT 0.93.0001?
Been stuck on this for days...and it's killing me!
PS. When I plug my phone in to
PC it says "Android ADB interface installed" "Ready to use"
But when I cmd the adb to find devices "adb devices" it shows blank
P.S. Phone: HTC Desire
Unrooted
S-ON
Unable to boot, can only get to HBOOT.(so cant turn debugging on)
Trying to get a goldcard to flash a new rom and see if i can unbrick
Reason for unable to boot is - It had been rebooting itself for weeks, slowly getting worse, until now, when I cant get it booted at all.
Click to expand...
Click to collapse
adb won't work when you are in bootloader (It won't work until Linux is up). "fastboot" will work over USB in bootloader->Fastboot.
I believe RUU will work on fastboot mode.
My phone has banished me from using it for about 3 months now. I repeatedly apologized for upsetting it, and begged of it to allow me back in. But it's a cold machine, which feels no empathy and cares not for my well-intentioned promises of never angering it again.
I understand it's reluctance to believe my words, as this is not the first time I've committed such atrocities. You see, I bricked it doing the same thing once before. Likewise, I was never able to fix it. Instead, I pawned it off to an Android developer in the office and he was able to fix it after a few hours of struggling. I've since moved to a different office on the other side of the country, and he was unable to remember exactly what he did that finally fixed it.
On to the important things:
What happened exactly?
I was installing a ROM (I can't remember which one at this point, it's been a while). Something counterproductive happened during the install, and sent it into a bootloop.
Symptoms?
1. It starts booting as normal. HTC logo for a few seconds, goes black as if it's going to the next screen, then it reboots.
2. This time it has the HTC logo with "Entering Recovery..." in pink above it.
3. I get a very quick (a few milliseconds, tops) glimpse of the CWM loading screen, then it reboots and goes back to step 1.
4. It repeats indefinitely, and would probably do so for eternity.
What can I actually do?
I can get to the bootloader screen, and cycle through the options (Fasboot, Recovery, Factory Reset, Simlock, Image CRC, Show Barcode), and I can drill into each section and see their child options. However anything I try to do, just sends me into the bootloop.
However, it does still say it's Unlocked in the bootloader. It has the "Tampered" and "Unlocked" alerts at the top.
What have I tried?
I've tried more random things than I can possibly recite right now. I even went to the extremes of dual booting Windows 8 on my Macbook, so I could start trying some of the Windows-only suggestions, like using the All-In-One Toolkit. The biggest issue, is that nothing I use can find the device. Not ADB or Fastboot on Mac, not ADB or Fasboot on Windows, and not the All-In-On-Toolkit. The only thing I ever get is "Waiting for device" or "Device not found".
Any help would be much appreciated. Thanks in advance guys!
rvrzl said:
My phone has banished me from using it for about 3 months now. I repeatedly apologized for upsetting it, and begged of it to allow me back in. But it's a cold machine, which feels no empathy and cares not for my well-intentioned promises of never angering it again.
I understand it's reluctance to believe my words, as this is not the first time I've committed such atrocities. You see, I bricked it doing the same thing once before. Likewise, I was never able to fix it. Instead, I pawned it off to an Android developer in the office and he was able to fix it after a few hours of struggling. I've since moved to a different office on the other side of the country, and he was unable to remember exactly what he did that finally fixed it.
On to the important things:
What happened exactly?
I was installing a ROM (I can't remember which one at this point, it's been a while). Something counterproductive happened during the install, and sent it into a bootloop.
Symptoms?
1. It starts booting as normal. HTC logo for a few seconds, goes black as if it's going to the next screen, then it reboots.
2. This time it has the HTC logo with "Entering Recovery..." in pink above it.
3. I get a very quick (a few milliseconds, tops) glimpse of the CWM loading screen, then it reboots and goes back to step 1.
4. It repeats indefinitely, and would probably do so for eternity.
What can I actually do?
I can get to the bootloader screen, and cycle through the options (Fasboot, Recovery, Factory Reset, Simlock, Image CRC, Show Barcode), and I can drill into each section and see their child options. However anything I try to do, just sends me into the bootloop.
However, it does still say it's Unlocked in the bootloader. It has the "Tampered" and "Unlocked" alerts at the top.
What have I tried?
I've tried more random things than I can possibly recite right now. I even went to the extremes of dual booting Windows 8 on my Macbook, so I could start trying some of the Windows-only suggestions, like using the All-In-One Toolkit. The biggest issue, is that nothing I use can find the device. Not ADB or Fastboot on Mac, not ADB or Fasboot on Windows, and not the All-In-On-Toolkit. The only thing I ever get is "Waiting for device" or "Device not found".
Any help would be much appreciated. Thanks in advance guys!
Click to expand...
Click to collapse
Sorry I don't know how drivers work on a Mac.
the procedure from a PC would be
boot to bootloader
choose fastboot
plug in usb to phone
you now see fastboot usb in bootloader
from command prompt type "fastboot erase cache" then fastboot reboot
try to boot phone.
if it fails
reboot to bootloader
reflash recovery
fastboot flash recovery TWRP.img
fastboot erase cache
fastboot reboot
make sure your recovery is named like above and in the same folder as fastboot
clsA said:
Sorry I don't know how drivers work on a Mac.
the procedure from a PC would be
boot to bootloader
choose fastboot
plug in usb to phone
you now see fastboot usb in bootloader
from command prompt type "fastboot erase cache" then fastboot reboot
try to boot phone.
if it fails
reboot to bootloader
reflash recovery
fastboot flash recovery TWRP.img
fastboot erase cache
fastboot reboot
make sure your recovery is named like above and in the same folder as fastboot
Click to expand...
Click to collapse
Thanks for the help clsA
I gave this a try, but like I expected I'm just getting a "waiting for device" message from fastboot.
This time around (in Windows), I did notice that I'm also getting an error about the USB device not being recognized. I don't think it's initializing correctly because Windows says it's malfunctioning. Nothing has happened to the device itself (no bangs, drops, water, etc), and this wasn't a problem until after it was bricked, so I doubt it's hardware related.
Interestingly, under the Device Manager, it is listed under "Android USB Devices" as "My HTC" so it seems to know what it is. My drivers appear to be up to date. Any other suggestions? Thanks again.
rvrzl said:
Thanks for the help clsA
I gave this a try, but like I expected I'm just getting a "waiting for device" message from fastboot.
This time around (in Windows), I did notice that I'm also getting an error about the USB device not being recognized. I don't think it's initializing correctly because Windows says it's malfunctioning. Nothing has happened to the device itself (no bangs, drops, water, etc), and this wasn't a problem until after it was bricked, so I doubt it's hardware related.
Interestingly, under the Device Manager, it is listed under "Android USB Devices" as "My HTC" so it seems to know what it is. My drivers appear to be up to date. Any other suggestions? Thanks again.
Click to expand...
Click to collapse
Install the drivers included in the All in one kit or install HTC sync (not recommended)
Sent from my TouchPad using xda app-developers app
[RESOLVED!]
For anyone else who might be having this problem
1. I was finally able to resolve this by downloading the archive provided by Esau Silva, which (I'm assuming) had updated versions of adb, and fastboot for Mac/OSX: http://esausilva.com/2010/10/02/how-to-set-up-adb-android-debug-bridge-in-mac-osx
2. I booted to the bootloader (power + volume down for 10 seconds), went to the Fastboot option, then plugged my phone into my Macbook; enabling Fastboot USB.
3. I opened terminal, CD'd into the directory containing adb/fastboot, and then ran "./fastboot devices" to see if it recognized my device. Sure enough, with Fastboot USB on and the updated adb, it recognized the device.
4. Then I ran "./fastboot erase cache" which allowed me to boot back into the bootload, and then properly boot into recovery, finally seeing ClockworkMod Recovery again.
5. From CWMR I erased the cache again, erased the dalvik cache, and then did a full wipe/factory reset.
6. Then I booted back into CWMR once again, and chose sideload. Then back on my Macbook I was able to run "./adb devices" to make sure adb could see my HTC One. Once I confirmed it could see it, I ran "./adb sideload nameofrom.zip"
After the sideload was complete, I was back up and running.
Big thanks to clsA who got me Googling fastboot a bit more. Hopefully this helps someone else!
hi. I have prime and it is stuck into twrp screen with just teamwin screen keep on flashing. nothing happens and it doesn't boot into recovery(twrp) also. tried to boot into bootloader by holding power button and volume down but nothing happens. then tried adb. used abd reboot bootloader and also adb fastboot recovery. but nothing happens, only shown "waiting for any device". thought adb not working but when I type adb devices.....it shows device serial number and recovery written next to it. I think adb works but I am not able to boot into recovery or bootloader....
earlier I was using cayanogen rom and twrp as recovery... tried to falsh another rom and from that day had this problem. if anyone knows what should do or what's the problem.. I be very thankful... please if you have any idea tell me what to do??
fastboot devices ?