I have searched here and Google but can't seem to find the exact problem that I am having. Most similar issues are with different phones and I haven't found any solutions for the HTC Hero. I have been rooted for a couple of months and using CM6 (stable and nightlys) without any problems whatsoever. I have (had?) Clockwork recovery. My phone was running perfectly this morning and the battery was pretty low (down to 10%) so I pulled it and put in a fully charged battery. Now my phone won't boot past the HTC white screen. I can boot into HBoot ONLY (three skateboarding androids) and the screen shows:
HERC XC SHIP S-ON
HBOOT-1.47.0000 (HERO20000)
TOUCH PANEL-SYN0104
RADIO-2.42.01.04.27
Mar 1 2010, 16:02:39
I have tried all the options on HBOOT and can get into FASTBOOT but am unable to reset device, go into recovery, etc. It just goes back to the white HTC Screen after choosing one of these options and never boots up. I've tried with the SD card in and with it out. I even tried to RUU with the .5 Sprint official release but when I run it, the program said my phone was not found and told me to make sure it was plugged into the computer which of course it was. I also tried to run the RUU in FASTBOOT USB mode but still receive the same error.
When I run adb shell on my PC it says the device was not found. When I'm stuck on the white HTC screen if the phone is plugged in to the computer and I unplug the usb from the phone it vibrates 5 times quickly and the screen goes off, but the green notification light is blinking. From this state I am unable to power up the phone at all without a battery pull.
I just don't understand how my phone can go from being PERFECT to FUBAR when the only thing I did was replace the battery. I'm hoping someone can help me. I am eligible for an upgrade but really don't want to spend the $$ right now for an EVO or Epic when my area will never see 4g and the extra $10 is ridiculous.
My setup prior to this morning when I pulled the battery:
Clockworkmod Recovery
CM 6 nightly (Full-73)
BFS #11 kernel
FireRat custom data partitions
And I was rooted with Universal Androot
Have you tried booting into recovery by holding Home and pressing Power? From there you could try wiping everything then reflashing the ROM of your choice.
Have you tried putting the original battery back in and just recharging it fully, then trying to boot?
chromiumleaf said:
Have you tried booting into recovery by holding Home and pressing Power? From there you could try wiping everything then reflashing the ROM of your choice.
Have you tried putting the original battery back in and just recharging it fully, then trying to boot?
Click to expand...
Click to collapse
When I hold home and press power, I just get the white HTC screen of death. When I hold volume down and press power, I get the HBOOT screen and when I try to boot into recovery from that screen it again gives me the HTC screen of death. There is no way past the HTC Screen other than HBOOT and Fastboot. I also charged the phone with the original battery as you suggested and it still did not boot up beyond the HTC screen.
This afternoon I was in the FastBoot screen and plugged my phone into the USB that was connected to my computer. It changed to FastBootUSB and I was able to run the RUU. The program said that the ROM was successfully updated but I sat there for an hour with another white HTC screen before I unplugged the USB and then the phone shut off and I got the 5 quick vibrates. I really think it's toast. RIP, it was such a good phone!
debh945 said:
When I hold home and press power, I just get the white HTC screen of death. When I hold volume down and press power, I get the HBOOT screen and when I try to boot into recovery from that screen it again gives me the HTC screen of death. There is no way past the HTC Screen other than HBOOT and Fastboot. I also charged the phone with the original battery as you suggested and it still did not boot up beyond the HTC screen.
This afternoon I was in the FastBoot screen and plugged my phone into the USB that was connected to my computer. It changed to FastBootUSB and I was able to run the RUU. The program said that the ROM was successfully updated but I sat there for an hour with another white HTC screen before I unplugged the USB and then the phone shut off and I got the 5 quick vibrates. I really think it's toast. RIP, it was such a good phone!
Click to expand...
Click to collapse
Well you'll be the first to kill it this way but I'm sorry to here that and my touch screen is almost toast so ima start a first to
Sent from my HERO200 using XDA App
rulyskull said:
Well you'll be the first to kill it this way but I'm sorry to here that and my touch screen is almost toast so ima start a first to
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Dang, that sucks. I was torn between getting an upgrade or buying a used Hero on Ebay until I find a phone I want. Turns out my phone was only 11 months and 10 days old so I'm still under warranty. My new Hero will be here Tuesday. I'm hoping it doesn't come with the .7 update but if so, I'm hoping I can RUU back to the .5 and re-root. Anyone know if this is possible? Thanks.
debh945 said:
Dang, that sucks. I was torn between getting an upgrade or buying a used Hero on Ebay until I find a phone I want. Turns out my phone was only 11 months and 10 days old so I'm still under warranty. My new Hero will be here Tuesday. I'm hoping it doesn't come with the .7 update but if so, I'm hoping I can RUU back to the .5 and re-root. Anyone know if this is possible? Thanks.
Click to expand...
Click to collapse
Try the one click root(forget What section in here) but ima wait to get the epic or something better
Sent from my HERO200 using XDA App
Have you tried ruu'ing it?
Sent from my HERO200 using XDA App
Vandelay007 said:
Have you tried ruu'ing it?
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Yep, I was finally able to RUU while the phone was in FASTBOOTUSB mode and the program on the PC said the ROM was updated successfully but it still never got past the HTC white screen. When I boot into HBoot by holding the volume down/power button the screen flashes a bunch of things so fast I can't read them but it seems like it says something about HCERMG Image Not Found.
The Sprint tech(?) hooked it up and tried to diagnose, install the software but couldn't either. Anyway, since it is under warranty I get a new Hero on Tuesday. I am just baffled at how this happened when all I did was change the battery. You don't realize how much you love something until it's gone. I'm currently using my old Instinct and I find myself constantly turning the screen sideways and wondering why the display won't turn.
Same issue here, (2nd time actually). Last time I was able to put the HERCIMG.zip on the root of my SD Card and then load it with HBOOT, and then I was back to stock and all was good. However since then my HBOOT was updated to 1.47 and now the HERCIMG.zip doesn't work, it says "Main Version is older!" Update Fail!
I haven't figured anything else out yet. Is there an updated HERCIMG.zip for 1.47?
SportsPT said:
Same issue here, (2nd time actually). Last time I was able to put the HERCIMG.zip on the root of my SD Card and then load it with HBOOT, and then I was back to stock and all was good. However since then my HBOOT was updated to 1.47 and now the HERCIMG.zip doesn't work, it says "Main Version is older!" Update Fail!
I haven't figured anything else out yet. Is there an updated HERCIMG.zip for 1.47?
Click to expand...
Click to collapse
Do you mind telling me what you did (twice lol) that put your phone in this unusable state? Like I said I'm not sure how this happened and don't want to repeat it with a replacement phone!
Ok, I put the HERCIMG.zip on the root of my SD Card (found it through Google and had updated 1.47 HBOOT). I booted up holding the volume down and power and the blue progress bar filled up on the right side and when it was finished it went back to the HBOOT screen. I rebooted the system and still have the white screen of death. I'm convinced there's really nothing else I can do to get it running again and must painfully wait until my new phone comes in on Tuesday.
Couldn't tell you how it happened, may have to do with the battery completely dying, but not sure. I tried what you did but got the same results. I think what we need as an updated HERCIMG.zip that works with HBOOT 1.47
While in fastboot, did you try
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash data data.img
unCoRrUpTeD said:
While in fastboot, did you try
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash data data.img
Click to expand...
Click to collapse
I tried all kinds of fastboot commands in FASTBOOTUSB mode through adb but always received the error "remote not allowed" or something to that effect.
debh945 said:
I tried all kinds of fastboot commands in FASTBOOTUSB mode through adb but always received the error "remote not allowed" or something to that effect.
Click to expand...
Click to collapse
What about when you power on the phone normally. You should be able to get into adb shell when it is booting up.
I am going to try fastboot flash boot.img right now on mine and see if I can't get something.
Edit:Haven't tried. Working on a multiboot and now I only have one more obstacle.
unCoRrUpTeD said:
What about when you power on the phone normally. You should be able to get into adb shell when it is booting up.
I am going to try fastboot flash boot.img right now on mine and see if I can't get something.
Edit:Haven't tried. Working on a multiboot and now I only have one more obstacle.
Click to expand...
Click to collapse
If I was not in the FastbootUSB mode, there was only the white HTC screen and adb showed "no devices". I appreciate your help but I can't troubleshoot any longer as I had to turn my phone in to get the new one via warranty replacement. Your efforts might help someone else though with the same problem.
ps, I've been following the multiboot thread very closely and can't wait until this becomes a reality!! That will be so awesome!
debh945 said:
If I was not in the FastbootUSB mode, there was only the white HTC screen and adb showed "no devices". I appreciate your help but I can't troubleshoot any longer as I had to turn my phone in to get the new one via warranty replacement. Your efforts might help someone else though with the same problem.
ps, I've been following the multiboot thread very closely and can't wait until this becomes a reality!! That will be so awesome!
Click to expand...
Click to collapse
Did you pay the extra for warranty or are all heros on warranty for 12 months? Who did you sent the phone to or did you just go to the sprint store?
obsanity said:
Did you pay the extra for warranty or are all heros on warranty for 12 months? Who did you sent the phone to or did you just go to the sprint store?
Click to expand...
Click to collapse
All Heros have a 12 month warranty, I didn't pay extra. I first called Sprint Customer service and since it wouldn't boot for them to troubleshoot on the phone she gave me an Eticket number and the location of the nearest Sprint store with a repair center. I took it in and the tech (?) hooked it up to his computer and could not fix it either so he said he would order me another and it would be here on Tuesday. This was Saturday evening. I received a call today (Monday) from the Sprint Store that my replacement phone was in. Picked it up and rooted it in 5 minutes with Universal Androot, installed Clockwork Mod Recovery, Nandroid restored a backup from the old phone's SD card and I was back in business in 1/2 an hour! Probably TMI, I realize you only asked how I got a new phone but I'm thrilled to have my Froyo back!
Awesome! Makes me feel better trying different ROMs
Funny thing I found this thread, this exact same thing happened to me today.. Hero is completely done.. Getting a replacement tomorrow... I was running firerats also which I can't blame but I'm not running firerats on my new device... Since I installed firerats I've lost 2 8gb sd cards and a phone...
Weird thing is, I had applied the unrevoked-forever and eng spl mod/hack, now when I boot into bootloader it says s-on like what the hell happened? How did I lose s-off and root all together after restarting my phone.
Related
Just received my G1 today. Haven't changed anything, went through first boot, got everything setup to my liking, downloaded a few apps from the market.
Rebooted the phone since it looked like I lost data connectivity, and it's now stuck at the bootloader screen. It doesn't seem that the camera button is stuck, I can push it and feel actually depress. Booted into recovery and did a factory reset/wipe, still no good.
Should I be able to reflash an original ROM image from recovery to get going again? (After I hunt down an SD card)
... how can you be "stuck" at the bootloader if you can already access the recovery?
Couple of things you can try:
1) Reflashing the ROM (since you can access recovery right?)
2) If you're actually stuck in the bootloader and can't get to any other screen, you can try:
Code:
fastboot reboot
3. If that doesn't work, you can try reflashing DREAIMG.nbh (RC29) and starting over.
Yea, it boots right to the bootloader. If I hold power + home it goes into recovery, but that doesn't get me anywhere.
Tried reflashing RC29 via the bootloader. After it's complete, I press the action key to reboot, and it goes right back into the bootloader.
Where am I supposed to enter in "fastboot reboot"?
Is there anything I should try updating at the recovery screen via SD card?
if you just got the G1 recently and you haven't installed any custom software on it and you're already having theese issues why not just exchange it for one that actually works instead of going through the headache of trying to fix it? Especially if the software hasn't been modified and you keep getting thrown into the bootloader
That'll be the next step. I didn't buy it locally tho, through the web, so I'd like to see what I can do before I go that route.
if you use the rc29 DREAIMG.nbh it writes over everything, so if your phone still dosn't load you may have a more serious problem, exchange may be your best bet
I've sent an email to the vendor I bought it from about exchanging it.
I've noticed that when booting into recovery, after pressing alt - L, the top of the screen says :
Android system recovery utility
E:Can't open /cache/recoverfy/command
Then it lists out the Alt commands.
possibly try downloading the DREAIMG.nbh file again, format your sdcard to fat32 once more, let your phone boot into the bootloader and apply the update and cross your fingers and pray to wich ever god you believe in
I've left the battery out all night. I was in the process of formatting the sd at the computer again, and tried powering on the G1. Holy crap it boots up!
Now I'm back to the problem of no data services. I can surf the web all I want on the dash, I know I have a data plan. I'll have to give t-mo a call I guess, since I can't get the G1 registered now.
laszlo462 said:
I've left the battery out all night. I was in the process of formatting the sd at the computer again, and tried powering on the G1. Holy crap it boots up!
Now I'm back to the problem of no data services. I can surf the web all I want on the dash, I know I have a data plan. I'll have to give t-mo a call I guess, since I can't get the G1 registered now.
Click to expand...
Click to collapse
ya i would call t mobile .they would prob replace for ya sounds like some thing weird going on!good luck
Ok, definently sending this back. It has stopped working again. I'd turn it off from the menu, swap out the SIM, and when I go to turn it back on, it'll boot to bootloader again. Reflashed later today for kicks, booted bootloader 1st time, booted up correctly the 2nd time (but didn't have SIM in), booted a 3rd time with SIM in to try to activate, but it went to bootloader again. Any subsequent boots are all to bootloader.
I'm thinking it's crappy hardware.
Still intermittent booting. Until I get the goahead to send it back for an exchange, what else do we think I should try. Could it be the radio version? I tried to update with an HTC radio, but the signature didn't let it load. What, if any, radio downloads will work with a stock G1?
I'll try a few more things tonight, and post up what happens. Maybe check out tmobile's downloads for firmware updates.
If I didn't buy the phone directly from t-mobile, would they be able to do anything for me if I take it in to a store?
laszlo462 said:
If I didn't buy the phone directly from t-mobile, would they be able to do anything for me if I take it in to a store?
Click to expand...
Click to collapse
No they won't. Your best bet is to contact HTC cause the phone is still under warranty, but you better contact them soon cause the phone is about to be a year old on Oct. 20th I believe.
I'll try that then, since all I got for a response from the seller was "has the issue been resolved yet?" I'll check with HTC today about the manuf. warranty.
Hi guys,
UK G1 (Dream) phone recently updated to the 1.6 build, all working fine.
Yesterday I tried installing the free app Shop Savvy. the phone resetted itself after install and sat on the G1 boot screen permanently.
Now phone will pass this boot screen (Tmobile G1)
Tried:
Recovery mode - will not work at all
Quick boot - brings up the multicolour screen but does nothing after.
**PHONE IS NOT ROOTED**
looks like I have had the phone JUST over a year, not looking good...
Any ideas?
You can boot in to the SPL/bootloader so thankfully you haven't bricked
If you're on a contract with tmo you could take it back to the store and they should give you a replacement, but where's the fun in that?
If you want to fix the problem yourself, all you need to do is downgrade to firmware 1.1, then accept the OTA update to 1.6.
Here's the procedure:
1)Put the phones SD card in to a card reader and format as fat32
2) Extract this file and copy it to your SD card as 'DREAIMG.nbh'
3) Put the card back in the phone and hold down power and camera to boot in to the bootloader.
4) Flash it. (Action button is the trackball).
It's a good idea to leave the charger plugged in and have a decent amount of charge in the battery (eg 40%+).
Afterwards the phone will restart and you will need to re-enter your google account info. All your apps and data will be gone, but there's not much we can do about. You can set things up and install apps while you wait for the prompt to update.
Thanks alot AdrianK,
Really appreciate the steps and info, nice one
I have done some flashing on other phones etc so I have no problem with this. However, I am wondering how a normal app such as Shop Savvy could corrupt my ROM and am wondering if it might not be better to get a new phone as this one could have hardware fault?
What do you think?
Silver.
OK,
did exactly as you said Adrian. Phone went through all the flashing routine then, right at the end said press action button to continue (trackball) every time I press the trackball phone returns to the bootloader screen
What now?
SilverfoxUK said:
OK,
did exactly as you said Adrian. Phone went through all the flashing routine then, right at the end said press action button to continue (trackball) every time I press the trackball phone returns to the bootloader screen
What now?
Click to expand...
Click to collapse
I think you can take the battery out restart the phone
Thanks but unfortunately I have already tried that.
Phone just sits on the G1 boot screen as before...
Any other Ideas?
is that ROM you linked for me a UK ROM Adrian?
Once you get to RC7 use these to build back upto 1.6
http://code.google.com/p/official-android-firmware/downloads/list
SilverfoxUK said:
Thanks but unfortunately I have already tried that.
Phone just sits on the G1 boot screen as before...
Any other Ideas?
is that ROM you linked for me a UK ROM Adrian?
Click to expand...
Click to collapse
Yeah that's the RC7 ROM, the UK ROM for 1.1. RC29 is 1.1 for US phones.
This is all very odd, especially that it was an app that caused it, or as you suggested possible hardward failure. Oh well, I guess all you can do now is take it back to tmo.
ok so i got my hands on my sisters old G1 and it was unrooted and with rc30.
so i was able to downgrade it to rc29, flash it with RA recovery 1.7.0, and i was applying the the spl next. i booted into recovery and flashed the spl, and when i rebooted the g1 i just got suck at the tmobile g1 screen, i left it there for like 10 minutes thinking its gonna do its thing but it was still stuck there.
i pulled the battery out and pressed home and the power button, and it still didnt wanna go into recovery. so i pulled the battery again. so pressed and held the camera button and power button and it booted into the g1 screen instead!
so at this point i think i bricked it since im just stuck at the g1 screen and cant do nothing from there and i wanted a 2nd opinion to confirm it, or for a possible solution.
im thinking i messed up with the spl, but the one i have DL is the same one i used with my old G1 and its still kicking some (this one has a problem with the flex ribbon cable i believe, but completely usable.)
Im pretty sure when a phone is bricked, you cant even boot your phone, so im pretty sure ur phone is not bricked.
sorry, idk how to fix this, but im sure someone does.
You have to flash a rom, of coursebit would get stuck at g1 screen bcuz it had no direction(no rom)
Sent from my HTC HD2
the situation is you can get into hboot but not recovery nor system,right?
you could flash radio/spl via fastboot ,then flash recovery, rom at last.
read this thread:http://forum.xda-developers.com/showthread.php?t=532719,try to fix it
edward0119 said:
the situation is you can get into hboot but not recovery nor system,right?
you could flash radio/spl via fastboot ,then flash recovery, rom at last.
read this thread:http://forum.xda-developers.com/showthread.php?t=532719,try to fix it
Click to expand...
Click to collapse
no i cant access recovery, or hboot.
when i hooked it up to the computer hoping that it might recognize it, nothing happened either when i tried to boot into hboot, or recovery.
so ive been doin some more digging into the internet and yep i did end up bricking it.
looks like im gonna perform some phone operation between the two g1s to have a fully working one.
so pressed and held the camera button and power button and it booted into the g1 screen instead!
you said this last day,it doesn't work now?
edward0119 said:
you said this last day,it doesn't work now?
Click to expand...
Click to collapse
no it doesnt.
i have no access to hboot, or recovery. and it doesnt get recognized by my computer if i try to have it hooked up with the usb, so i cant even use adb or nothing.
so like i said, i could pretty much confirm myself that i bricked it. so right now im like phoneless because my original g1 has an issue with it not showing nothing if the keyboard is CLOSED (yes closed, not open! lol) and it ended up closing on me when i tossed it in my bed (doh!)
damm that sucks man.. sorry for your loss lol
ldrifta said:
damm that sucks man.. sorry for your loss lol
Click to expand...
Click to collapse
haha its alright, only option right now is phone operation with the two g1s i have, but i need to buy a torx screwdriver for it since the one i got is the wrong size.
but its not such a bad thing because ive been hearing that i might end up getting a new HTC phone as a graduation present. so heres to hoping thats true! lol
I guess it is bricked,maybe it can be fixed by a serviceman
Well seeing it's screwed lol try out JTAG used it before to unbrick a phone once ^^ that should be a solution for you
xillius200 said:
Well seeing it's screwed lol try out JTAG used it before to unbrick a phone once ^^ that should be a solution for you
Click to expand...
Click to collapse
yeah i was looking into that, but idk it seemed wierd for me.
but last night i opened up the g1s and replaced the motherboards from eachother. and now i got a working g1!
I recently bought this Nexus off eBay and it worked fine.
Owner said it had problems with the SD card, but it seemed to be working, for they said it wouldnt read, when it does.
Anyway, it had cyanogen mod 6.1.1 on it, and I hate the setup...so i changed roms. That was a success, but when i flashed a sense rom thru clockwork(most updated) it said:
E:Error in /sdcard/N1Sensation_v0.4.zip
(Status 0)
Installation aborted.
Now, when i flash any roms, whether it says it installed correctly, it doesnt change anything. Now it's stuck at the 4 color x with the unlock icon. Any advice is good advice!
In my hboot, it says:
*** UNLOCKED ***
NEXUSONE PVT SHIP S-ON
HBOOT-0.35.0017
MICROP-0b15
TOUCH PANAL-SYNT0103
RADIO-5.00.00.04
Oct 12 2010, 14:33:16
HBOOT
Etc. Etc. Etc.
Thanks for any help!
Edit: I fixed the issue with why it failed, was my fault, didnt partition the card...but i was flashing a stock rom and it said complete and when i rebooted it stayed at the X and then powered off. Since then has never turned on. I don't know what to do. Nothing will turn it back on. I have a universal charger that charges the battery and it said the battery is full. I need help!
Ok lets see here try this plug in the charger then pull the battery place it back in wait a few seconds and repeat until you see the splash screen (the static X). This could get the phone to at least boot.
But just to check did you flash a radio in all that stuff??
Dude Random21 said:
Ok lets see here try this plug in the charger then pull the battery place it back in wait a few seconds and repeat until you see the splash screen (the static X). This could get the phone to at least boot.
But just to check did you flash a radio in all that stuff??
Click to expand...
Click to collapse
That did not work. I work at a cellphone repair store, but im yet to open it up. But i flashed a sensation rom...
http://forum.xda-developers.com/showthread.php?t=1083035
After then i got stuck on the X
Then i used... well i cant find the link, but it's PureGoogleMod.
From what I saw, there was no radio or kernal being flashed. I just know i flashed a rom, it said completed, then went to the X, rebooted, but never turned on. And ive tried other batteries.
matistight said:
That did not work. I work at a cellphone repair store, but im yet to open it up. But i flashed a sensation rom...
http://forum.xda-developers.com/showthread.php?t=1083035
After then i got stuck on the X
Then i used... well i cant find the link, but it's PureGoogleMod.
From what I saw, there was no radio or kernal being flashed. I just know i flashed a rom, it said completed, then went to the X, rebooted, but never turned on. And ive tried other batteries.
Click to expand...
Click to collapse
Try flashing CM7. Also...before you do...you may want to search for a format.zip from a member named temasek. It'll wipe your phone...clean. Real clean. Then flash CM7. try that.
also....those sense roms sometimes take at least 5 minutes to boot. Sometimes it'll stay on the X screen for 5 minutes or it'll stay on the bootanimation screen for 5 minutes. FYI.
SiNJiN76 said:
Try flashing CM7.
those sense roms sometimes take at least 5 minutes to boot. Sometimes it'll stay on the X screen for 5 minutes or it'll stay on the bootanimation screen for 5 minutes. FYI.
Click to expand...
Click to collapse
I can't flash anything. Phone wont react to anything anymore. Hoping one of my family members can fix it. But if I get it on I will try that.
I am pretty sure i waited long enough, but who knows. I didn't partition my card, which may have been the problem. And also it was S-On....which i thought was odd when it had a custom firmware.
Unlock bootloader. Flash recovery. Boot into recovery. Wipe everything. Flash rom.
Why do you guys keep suggesting software stuff when it's probably a hardware problem he can't get the phone to boot up so he can't do any of that.
Although there is one thing I want you to try before your family take a crack at it to take it apart and what not, it's a long shot but it's your last chance if it's software. Hold down trackball and press power keep holding trackball for another 5-10 seconds (better to long then to short) then connect it to the computer via USB you could see a popup notification saying that it's looking for driver software if you do then it's software and we need to reflash everything and might need to unlock the bootloader. Now if you don't see a popup notification I would still go check in the device manager and check for an unidentified device probably in other (it should be extracted so that you can see it).
If this doesn't work then sorry but I think it's a brick
Because in order to find out if its truly a hardware problem you need to try every software fix first.
Op mentioned nothing of trying fastboot as well. Software fix is free hw is not. That is why we suggest software fixes.
Sent from my Nexus S using XDA App
Let me remind you guys, THE PHONE WONT TURN ON AT ALL REGARDLESS OF WHAT I DO. I can post a YouTube video to show everything. It'd be very random for it to be hardware because it just turned off and will not turn back on. If there is any software like an RUU out there, that would help, if not, ill have to buy a bottom piece and warranty it out. But I'd feel bad because that isn't the right thing to do.
I don't expect you guys to fix it and I and very thankful of your help! But the phone won't turn on at all. So telling me to flash roms doesn't work. Imagine it as flashing a rom with the battery out of your phone. I am wondering if there's an adb way or something to get it to turn on and restore to stock?
With all that said, any help is amazing help and I am very grateful that this isn't a post I have to bump! Thank you so much, when I go on the PC, ill thank the helpful posts
Sent from my (finally) permanent root Sensation 4G
Then it is a brick if it won't turn on at all. The entire getting stuck at the x thing confused me to think it was powering on.
You have me confused sir, I'm not quite sure what good it is your looking for a RUU for. If the phone truly won't turn on/go past the X screen and you have it on a charger with no LED notification, then the phone is bricked. When you said you flashed a Sensation rom, I truly hope you just meant a Sense rom. If you can still get to the bootloader screen then you are not bricked and should retry everything from scratch.
Thread Closed
xsnipuhx said:
When you said you flashed a Sensation rom, I truly hope you just meant a Sense rom.
Click to expand...
Click to collapse
Sensation based, but it was a Sense rom
Confirmed it is bricked.
Sold on eBay for $100
Bought for $77
Semi-Winning.
Thread Closed
I apologize in advance if this has been discussed in the past, but my searching here hasn't helped so I gotta ask for help.
Having a problem with me wife's HTC Vivid. It's bone stock. Nothing has been messed with other than whatever updates may have been installed automatically over the air. She wouldn't let me touch it to root it, mod it, nothing.....
Anyway. Problem happened Saturday night. Phone shut down due to dead battery. Put it on charger overnight. Tried to boot it up Sunday morning and it stops at the white HTC screen. Period. Just sits there. Forever.
I did some reading, learned how to hold power and vol down buttons to get to HBOOT. Tried navigating to recovery. It goes to white HTC screen, then to a black screen with a green circle arrow icon, then to a red triangle with an exclamation point.
I downloaded drivers and the HTC RUU and was going to try fastboot usb, but when it said all data will be lost I stopped.
My wife has tons of pics and stuff on her phone (that she has failed to back up ) and really doesn't want to loose them.
Before I wipe the phone and try to reinstall the stock rom do any of you have any suggestions on a way to get it back up and running and recover her pics and stuff?
Or are we screwed? :crying:
Ginther said:
I apologize in advance if this has been discussed in the past, but my searching here hasn't helped so I gotta ask for help.
Having a problem with me wife's HTC Vivid. It's bone stock. Nothing has been messed with other than whatever updates may have been installed automatically over the air. She wouldn't let me touch it to root it, mod it, nothing.....
Anyway. Problem happened Saturday night. Phone shut down due to dead battery. Put it on charger overnight. Tried to boot it up Sunday morning and it stops at the white HTC screen. Period. Just sits there. Forever.
I did some reading, learned how to hold power and vol down buttons to get to HBOOT. Tried navigating to recovery. It goes to white HTC screen, then to a black screen with a green circle arrow icon, then to a red triangle with an exclamation point.
I downloaded drivers and the HTC RUU and was going to try fastboot usb, but when it said all data will be lost I stopped.
My wife has tons of pics and stuff on her phone (that she has failed to back up ) and really doesn't want to loose them.
Before I wipe the phone and try to reinstall the stock rom do any of you have any suggestions on a way to get it back up and running and recover her pics and stuff?
Or are we screwed? :crying:
Click to expand...
Click to collapse
You get the red triangle/exclamation point because you dont have a custom recovery installed if Im correct. Using the all in one here is the most user friendly way of installing -
http://forum.xda-developers.com/showthread.php?t=1498003
Install twrp and you should be able to recover your pics/vids by selecting "mount/mount sdcard" in the twrp ui with your phone plugged in to your pc. Then opening the storage located under computer. Navigating to the appropriate folder & cut/pastting to a folder on your pc.
I dont know how technology savvy you are but it sounds like flashing the stock kernel will repair your phone hanging on the htc logo. This is the stock ICS kernel - http://d-h.st/rHX
You can flash it through the all in one. Or follow up here -
http://forum.xda-developers.com/showthread.php?t=1416836
Hope this helps. Good luck!
Sent from my HTC Raider X710e using xda premium
yosoywilson78 said:
You get the red triangle/exclamation point because you dont have a custom recovery installed if Im correct. Using the all in one here is the most user friendly way of installing -
http://forum.xda-developers.com/showthread.php?t=1498003
Install twrp and you should be able to recover your pics/vids by selecting "mount/mount sdcard" in the twrp ui with your phone plugged in to your pc. Then opening the storage located under computer. Navigating to the appropriate folder & cut/pastting to a folder on your pc.
I dont know how technology savvy you are but it sounds like flashing the stock kernel will repair your phone hanging on the htc logo. This is the stock ICS kernel - http://d-h.st/rHX
You can flash it through the all in one. Or follow up here -
http://forum.xda-developers.com/showthread.php?t=1416836
Hope this helps. Good luck!
Sent from my HTC Raider X710e using xda premium
Click to expand...
Click to collapse
Thanks for the help. I was able to get the bootloder unlocked with the all-in-one but when I tried to install the kernel it kept failing. I tried several different things over and over again but no luck.
I finally got frustrated and tried the HTC RUU from their website to see what would happen. I had to relock the bootloader before it would work though. It finally ran successfully and the phone is back up and running now.
Only bad news is that I wasn't able to recover any of her files.
Now she understands the importance of backing up files and getting stuff OFF the phone to another form of long term storage. :good:
Thanks again for the help.
Ginther said:
Thanks for the help. I was able to get the bootloder unlocked with the all-in-one but when I tried to install the kernel it kept failing. I tried several different things over and over again but no luck.
I finally got frustrated and tried the HTC RUU from their website to see what would happen. I had to relock the bootloader before it would work though. It finally ran successfully and the phone is back up and running now.
Only bad news is that I wasn't able to recover any of her files.
Now she understands the importance of backing up files and getting stuff OFF the phone to another form of long term storage. :good:
Thanks again for the help.
Click to expand...
Click to collapse
You probably could have recovered your media. Just by mounting the internal memory like I said in my original post. You really should invest in an SD card that way no matter what happens your stuff is accessible. You can use up to 32GB. People also say 64GB SDXC cards work too. But glad its up and running again.
HTC VIVID ICS 4.0.4 SENSE 4.1
yosoywilson78 said:
You probably could have recovered your media. Just by mounting the internal memory like I said in my original post. You really should invest in an SD card that way no matter what happens your stuff is accessible. You can use up to 32GB. People also say 64GB SDXC cards work too. But glad its up and running again.
HTC VIVID ICS 4.0.4 SENSE 4.1
Click to expand...
Click to collapse
I got into CWM recovery and tried mounting the sdcard but kept getting "error mounting sdcard"
No mater what I did I could not get it to mount and become visible on my pc. I could see the disk drive(s) for the phone, but they were shaded and when I'd try to access them it would say insert disk into drive. When using the all-in-one it would try to push the kernel to the phone, but it got errors too. I tried putting the kernel on a micro sdcard and installing it from cwm with no luck. Couldn't get that to show/mount/work either.
I've done modding to my Samsung phones and build my own pc's so I'm not too technologically challenged.... but, Something was just wrong with this phone and it didn't want to cooperate.
And/or I didn't have the time and patience to keep jacking with it.
Switch to twrp
Sent from my Vivid 4G using Tapatalk 2