Hi everyone,
Yesterday I made a Radio update to version 63.18.55.06_6.35.07.08. I made it putting the update.zip (radio rom) file in the SD Card.
All worked fine until the htc hero restarted (after appears the box with the orange arrow). Thereafter the Hero only shows the Hero logo when I turn on.
I tried to init the fastboot pressing home+power and home+back+power buttons (without SD Card and without SIM card) but always the result is the same, the logo appears and nothing happens.
The computer doesn't detects the Hero's USB connection and I can't run adb commands because it raises the "device not found" error.
Someone can help me?
Thanks in advance!
Did you let the screen with the box run its course?
Did the recovery console come back up saying formatting cache?
Have you tryed holding just back+power? ive never heard of using back+home+power
And also, i think your supposed to enter recovery with the sd in.
If that works then in that state is should be found by adb.
But yes, as the poster before me said, it should show the "unpacking" image, and then it should reboot. It should then go straight back into the recovery and the recovery will format the cache. If you tryed to turn it off at any point then, then something is badly mucked up. But it isnt bricked, and probably can be saved. Its only bricked when no logos at all come up on boot. If you managed to get it reconised by adb, you could probs format the cache manualy, though i dont know the command
All the previous steps after the breack are as you say, but after the "unpacking" image, the htc hero restarted and showed the hero logo instead the correct menu.
The problem with the adb is that the computer doesn't recognize the htc hero across usb. When I write the adb command ("adb devices") doesn't displays any device, and I can't run any adb shell for the same reason. How can I run any adb command if the device isn't recognized by the computer?
Have you tryed just taking the battery out, waiting 30 seconds, putting it back in, then booting the phone holding back+power?
And adb is very strange i find... Sometimes it reconises a phone, sometimes it doesnt, for no apparent reason. Have you tryed leaving it on the hero logo for a while then running adb commands?
If he has flashed, wouldnt the USB Debugging setting be reset also, wouldnt this be why he cannot access via adb.
Hi.
I habe exactly the same problem. I have updated radion.
Now ther come only the T-Mobile Logo and that's all.
I can not enter neither Recovery Mode nor fasbtoot does do something.
Any suggestions?
Lado
this problem shud be fixed asap because i think its a threat for all hero modders and owners as our phones get killed at anytime with this process. so guys lets try to find a solution for this problem. cheers
Updated Radio to 63.18.55.06JU_6.35.09.26 and it killed my hero.
first the box with the orange arrow came up and then the whole phone died... now it wont even turn on the screen.
please fix?????????????????
I had the box with the orange arrow yesterday after flashing radio.
The phone isn't dead, I think it's just working.
I kinda paniced also when it happend but I got into recovery eventually.
When you flash a radio it does not actually install that image until your first boot (when you see that phone out the box image).
At this point DO NOT DO ANYTHING WITH THE PHONE just wait and it will install the image and reboot for you. IT CAN TAKE UP TO 10 MINUTES.
If you turn it off or otherwise interrupt this process it can really mess up your phone. however the general rule is so long as you can see the HTC logo when you turn on i.e. it still turns on you can in theory always recover, its just a matter of finding the way that works.
Related
First off id like to say thanks in advance to any replies and also apologize if this has been posted previously (i searched and could not find anything that was helpful) I lurked around these forums when i had my x1 and im hoping you guys can be as helpful for me as you are for everyone else. anyway onto the issue
I used the superboot method to root my ATT US Streak. My intentions were to update to 2.1 following the steps in the "eclair working on my u.s. unlocked streak!" thread (wont let me put a link since its my first post)
after using fastboot to root the phone will boot up and function fine but recovery and fastboot no longer work. i tried flashing Koush's custom recovery and other things that require fastboot and the terminal just says "sending..." nothing happens no errors or anything, the cmd prompt just sits there and i need to remove the battery to reboot the device.
i then downloaded the Rom Manager apk from the market and flashed the clockwork recovery from there (it said i did anyway). when i load the recovery from boot (volume keys + power and its the stock recovery) and chose option 2 to flash modaco custom rom or even the stock dell rom it just goes to a black screen and i once again need to remove the battery to reboot.
the phone itself is still functioning fine when it boots up and everything works the way it should other than the home, menu, and back button lights flash in random orders, thats just annoying though. again any help is appreciated
so what should i try next?
EDIT: woke up this morning and now the device will not turn on. i tried starting to fastboot and recovery but still nothing. plug it into my pc and i get the "found new hardware wizard" for a Qualcomm CDMA Technologies MSM.
first real brick? ha that would be my luck
EDIT 2: a kid just ran through my work, grabbed my phone and threw it on the ground. it screwed up the 30 pin connector on the phone and the charger. im going to hurt somebody. phone is booting again though... put sd card back in and still boots fine
SOLVED: Dont know the technical reasons behind it but i had to reinstall the drivers and switch usb ports for every fastboot and recovery procedure
removed SD card and its booting up normally. any thoughts?
Hello, dear xda users. I am kinda new in Android world- i bought HTC phone month ago and i tried to get used for it. My phone is polish version of T-Mobile G2 and its called ERA G2. I rooted it, installed Amon-Ra and tried a lot of custom ROMs. After month of using different kind of Android and HTC ROMs i stayed with RCMix 2.3, because of his speed and 2.1 Sense on it. And now my problem begins:
Today my menu button stoped working in some applications so i decided to reboot device. Everything went fine with getting off, but when phone vibrated and Era initializing screen appeared, nothing happened after that.
-I tried with removing SIM, SD and all other options but still it is frozen. After couple minutes its vibrating again and restarts.
-When i plug charger for turned off phone, charging led is on but at the same time i am turning on phone, led disappears (phone is still plugged to charger).
-I cannot go to recovery by holding Home+Power... nothing happens.
-When i am holding VOL Down and Power this unknown for me HTC/Android window appears but automatically starts some kind of loading, and when its in Simlock and opening FAT32 something it restarts and Era initialization screen is on again.
-Unfortunately i dont have any warranty for this phone and i am from Poland so professional technical support is the worst way of helping for me right now.
I really enjoyed HTC Hero and i want to enjoy it more, so please if you know any way or kind of solution, please reply ; ) [sorry for my english]
Do You have adb set up?
By nothing happends You mean it wont turn on, or it wont run recovery?
Sent from my Hero using XDA App
remove battery and put it back again. This will turn off the phone. Then try Power it up. Do you get into bootloop again?
What about recovery? Replace battery and power up into recovery. 2 things might happen. You can get into your recovery normally and reflash the rom. Or you might get a screen with a phone and a big red exclamation mark. In this case you've lost your recovery and need ruu install.
brat.haneq---> i ment that i cant go to recovery- i have initialization screen and nothing happens.
So, first of all i restarted my phone a lot of times in different combinations (with SIM, without SD etc.). I cannot get to recovery when i am pressing power+home buttons and nothing happens, no exclamation mark like arvan said. I just see blue initialization screen from Era (it says Era G2 Touch)as always. Normally after some seconds it dissapears and normal bootscreen from ROM shows up, but not this time. Any thoughts?
Oh, and what is adb set up? Cheers ; )
So I guess You've really lost the recovery.... And as I said, RUU install will help...
Okay, but how i can install RUU? I tried from PC but Windows doesnt see my device... Any other option?
have you got the drivers? they come with htc sence. what does your pc see instead of hero? there might be some unknown device in the device manager if it's a driver problem.
Install RUU form SDcard (extract ROM.zip from RUU, rename it to HEROIMG.zip and put it to root of SDcard) using HBOOT mode.
There's a guide explaining the steps here http://forum.xda-developers.com/showthread.php?t=714519
Hey guys, Today I just finished downgrading to HBOOT 1.4 and got up and running fine on TWRP 1.1.1 and ViperRom's new ICS build. I wasn't having any issues at all. I started reading about TWRP2 though, and felt like checking it out. So I downloaded GooManager and searched for TWRP and got openrecovery-twrp-2.1.3.blob. I touched it to download and it immediately went into recovery to install. However, as soon as it rebooted, it came up with TWRP 1.1.1's logo and a scrolling status bar. This lasted about 2 seconds and then the phone shut off. I left it as is hoping it would come back for about 10 min but nothing. I removed the battery and put it back in and tried to reboot. Booting to system and booting to recovery give zero response and ADB controls don't seem to recognize the device when plugged into USB. Can anybody help? TWRP2 doesn't seem to have a thread here and their site has limited resources for help.
thanks.
Can you boot into the bootloader (hold power and down on startup)?
no I cannot. Phone is completely unresponsive. I didn't think trying to flash a recovery would cause complete system failure.. wth
Just to be clear, before you call it a brick, did you remover battery for 10 seconds and then try to get to the bootloader. Hold down the volume first then the power button and keep holding both until the bootloader pops up. Just making sure...
yeah I did. Pulled the battery, left it out while I went and ate something, then plugged in the HTC charger and tried to reboot and nothing. Tried putting the battery back in and doing the same thing. I guess It's time to go to sprint and beg for mercy
Same thing happened to me. My phone is completely unresponsive after I tried to update to TWRP 2.1. I was on AOKP milestone 5a. The computer responds when I connect the USB, but the phone will not boot at all.
EDIT: Computer doesn't respond either. Think I'm headed to the nearest Sprint store ASAP.
Connect your device to your computer then go into your adb directory in cmd and type. "adb reboot-bootloader" (without the quotation marks)
Are you s-off ? And does the phone show up as qhusb_dload in device manager ? If it does it is bricked. If you still have s-on it can be fixed if you are s-off i am sorry to say you have to get a new phone. I have a phone now that is s-off and bricked and i cant recover it as of now but i am working on it, if i succeed i will post how to do it.
I would recommend trying to keep the bricked phone in case there is a way to unbrick eventually then you have another phone to play with. I just claimed my insurance and told them i dropped the phone in a porta-john at work and i wasn't about to fish it out. So they told me dont worry about sending the bricked phone in and i got my new one next day.
Hello there i need some help this is what happened.
I had this phone with purple screen so i download the room and flash it tru the sd card with the method of the buttoms (voluime up+ volumne - and power) the phone start doing the proces finish but never boot up it stay on a black screen.
After a while checking what when wrong i find out that i flashed a wrong firmware i used y210-0100 when i had to use y210-0151, so i download the new sofware and tried again but this time the phone does not go in to the flash mode wiith the botom (or any other mode)at least does not show nothing on the screen.
Right now the phone vibrates when i turn it on but does not show nothing on the screen only a black screen adb system in the computer recognize the phone but only when i conected in recovery mode (but nothing shows in the screen).
I have tried to flash it again with adb but nothing has work yet even thought to flash it tru the sdcard with adb but nohting has work yet, actually i am not an expert with the adb thing maybe you can recomend some comands that may work.
When i trien comands like "fasrboot -w" adb says waitng for device and get stuck there forever also with "fasboot flash file" or something likes that
So i will like to know if some one has any suggestion please let me know it may help me to fix this problem.
Y210-0100 Black Screen
Same thing happen to me after upgrading. HELP!!!
I was trying to flash a ROM (not sure exactly which one - I did this like a month or two ago) but I did something wrong and the phone is now in a boot loop. It gets to HTC logo and reboots constantly. When I try booting into recovery, it show CWM on the screen for a split second and then reboots (back into the bootloop). I am, however, able to get into fastboot. It says "tampered" and "unlocked" at the top. It's hboot version 1.44. When I select the factory reset or recovery option, it goes back into the bootloop.
I have read several posts about connecting it to a computer and using adb to reset it while in fastboot but I can't do that. Whenever I connect it to a computer, the phone does not get recognized on the computer whatsoever. When I plug it in, it starts charging but nothing happens on the computer. I have tried installing the drivers on multiple PCs (both Windows 7 and 8) and I have tried using several different USB cables. This was the case long before it was stuck in the boot loop too so it's not a new issue. It just doesn't get recognized on a computer. I've tried going into device manager and everything, nothing shows up. Is there any way I can fix this issue since I seemingly can't use adb?
Thanks in advance for any help!