Hello.
I have problem. My hero dont want to start. I dont know what to do.
When my phone is starting display shows me an operator logo and it turns off in about 20secs.
What can i do? When I'm trying to open recovery or fastboot it turns off in 0,5sec.
What now?
Probably dead 100%, if you cant get in fastboot then it's either a bad HBooT flash if you flashed it, if not then it's a hardware failture
Related
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.
so i received two htc eris' from a buddy of mine yesterday so my girlfriend could finally make the move up to a smart phone. neither were ever rooted and were running stock software. one of them works perfect but the other was stuck in an infinite boot cycle so i tried to hard reset it but it gets stuck at the screen with the red triangle and exclamation point.
so i figure maybe ill just try rooting it or at least getting the stock software back on it. im new to rooting but even if i mess up and brick the phone its a brocken spare so who cares. well i got to the point that i try to put it into fastboot usb mode to push a new recovery image to it but it wouldnt load into fastboot usb, the screen just had the red fastboot showing. so i try the working eris and it loads it up no problem. i also tried my htc hero and it didnt have a problem either.
so whats going on with this phone? any ideas why only it cant be loaded into fastboot usb?
goatxxmastr said:
so i figure maybe ill just try rooting it or at least getting the stock software back on it. im new to rooting but even if i mess up and brick the phone its a brocken spare so who cares. well i got to the point that i try to put it into fastboot usb mode to push a new recovery image to it but it wouldnt load into fastboot usb, the screen just had the red fastboot showing. so i try the working eris and it loads it up no problem. i also tried my htc hero and it didnt have a problem either.
so whats going on with this phone? any ideas why only it cant be loaded into fastboot usb?
Click to expand...
Click to collapse
You can only push a new Recovery image using Fastboot if the Eris has the S-OFF bootloader (HBOOT version 1.47.2000 S-OFF). Most Erises are HBOOT 1.46.0000, 1.47.0000, or 1.49.0000 with S-ON.
One method is to install HTC's latest 1.51.0000 bootloader, unlock it, which should allow fastboot to push the recovery image. See http://forum.xda-developers.com/showpost.php?p=23034380&postcount=3 for a more elaborate procedure that you can follow if pushing the recovery image still doesn't work.
I strongly recommend using Scary Alien's version of Amon_RA. Stay away from ClockworkMod Recovery as the default recovery on an Eris - it is problematic if flashes fail. Amon_RA is safer and there are no documented bricked phones from people with Amon_RA. See http://androidforums.com/eris-all-t...2-custom-recovery-trackball-not-required.html
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!!!
So I rooted my HTC ONE S (villec2) today, and I wanted to flash a custom rom on it. I got a recovery (turned out to be a bad one, but it worked either way.... I noticed way too late it was made for HTC One M8) I got TWRP 2.7.1.0 and I got it working on my phone. I then backed up the system, and realized I messed up the recovery. In the meantime I got a CM 12.1 img on it and wiped the thing. The wipe removed the old Android system and the CM I downloaded was a bad download. If I go to recovery in the bootloader, it will just do the HTC white screen with "Entering Recovery" and the red warning logo but it won't get anywhere. It's just stuck there. So now, I'm stuck with a device that won't boot normally - just stuck on the white HTC screen, will boot into bootloader, and I want to know if there's a way of accessing the internal storage without being in the operating system. The worst thing is, there's no external SD Card, all just internal... Please god help me. I'm really stressing out about this since it's the only phone I have and if I lose it.... well I'm practically f-ed.... :crying: I know that I messed a few things up really badly and I'm not sure what state the phone is in.
Also just to add, the phone is barely loading up right now. I'm really scared since it's my only phone and it won't even boot normally right now. It's really acting strange, it was on 90% battery but now it might just be dead... i don't know.... someone please help
I honestly think I screwed it up.... All it does now is just a white flash / flicker when I hold the power button (both only power button and vol down) and that's it. I'm really disappointed right now but oh well.... Maybe just because the battery is not charged.... Also been looking around the other threads and looks like a lot of people had the same issue but with 0 replies...
hi friend
i ve bricked a phone once and i recover it with flashing stock rom
did you try the stock rom ?
cazawiman said:
hi friend
i ve bricked a phone once and i recover it with flashing stock rom
did you try the stock rom ?
Click to expand...
Click to collapse
I have no way of trying the stock rom. I cannot access the phone itself because I deleted the OS. There's a weird thing, that if I plug the USB to the computer, it does the connect windows sound but the phone's internal storage is still not accessible.... So as it turns out I can get to the freaking bootloader but then it just turns off with a white flicker a second later.... I have no clue what to do :crying:
try to hook your device with windows and hold the Volume Down and Power
to see if it can detect it
cazawiman said:
try to hook your device with windows and hold the Volume Down and Power
to see if it can detect it
Click to expand...
Click to collapse
Alright. I slept through the night and now I'm here trying to resolve this again. Status now, is that when I try to boot it up, it just shows a white flicker and won't turn on. no matter if i try to boot in bootloader or normally. The device doesn't appear to be charging when I plug it in because it doesn't show the LED light for charging. I think it's hard bricked. I tried other threads, showing bright light to the proximity sensor, but nothing happened.
//edit// - My bootloader was unlocked, and I was on S-ON (HTC ONE S, S3 villec2) that might change on your phone and might make the process different
So I fixed it. I will leave the tutorial for anyone in the future that might be having the same issue. If you "locked yourself out" of your system, eg. no OS, and broken recovery just plug it into the computer, try somehow getting into bootloader, go into fastboot and plug the usb cable to your computer so you're in Fastboot USB. Then you can flash a recovery on the phone using a fastboot command. I believe it's fastboot flash recovery _filename_. Just google that, there'll be plenty. Then you have the recovery and you're back on track. After that you can get the rom you wanted. Just don't make my mistake, and check if your device is exactly the same as the files you're downloading for it. I messed up there . Anyway, good luck everyone!
t
yea
Happy to hear that u have fixed your phone add "solved " to the title and add a fast tutorial for help purpose
Sent from my thl T6 pro using XDA Free mobile app
Hi so I know people use the term brick wrong but I’m pretty sure I’m bricked and I want to know from you guys if there’s anything I can do. My phone shows the charging light and it turns on when I plug it in but it just says your device has been unlocked and can’t be trusted you will boot in 5 seconds then it says your device has been unlocked and the boot image is not working then it turns off. I can’t boot into recovery either it just does the same. I think it’s because I flashed a wrong boot.img to recovery and boot. Please tell me if I can do anything!
Have you tried the flashtool to flash stock rom? Same happened to me and flashtool worked for me.
try it because flashtool flashes stock rom via adb and it will replace the custom recovery and boot to in the process
Pvt_Phantom said:
Hi so I know people use the term brick wrong but I’m pretty sure I’m bricked and I want to know from you guys if there’s anything I can do. My phone shows the charging light and it turns on when I plug it in but it just says your device has been unlocked and can’t be trusted you will boot in 5 seconds then it says your device has been unlocked and the boot image is not working then it turns off. I can’t boot into recovery either it just does the same. I think it’s because I flashed a wrong boot.img to recovery and boot. Please tell me if I can do anything!
Click to expand...
Click to collapse
3 solution
1 use emma flashtool sony : https://developer.sony.com/develop/open-devices/get-started/flash-tool/ easy
2 use flashtool : www.flashtool.net meduim
3 use newflasher : https://forum.xda-developers.com/cr...gress-newflasher-xperia-command-line-t3619426 hard lol