Picked up an inspire 4g off of cl.Paid 20 for it because it had no battery. Put a batter in it and it boots to the htc screen, black screen, then reboots. Volume down was broken but I fixed it and am able to enter hboot. Phone had already been unlocked through htcdev. So I relocked it and ran the newest 3.20 RUU. It completed successfully and rebooted. However, it does the same thing. So I tried to factory reset it through bootloader. Again it just reboots and does the same thing. So I decided to try to htc dev unlock it and flash a custom recovery. Everything went smooth and recovery flashed. But when I select recovery in bootloader it does the same bootloop over again. Again I've tried using the latest RUU to no avail. Ive tried everything I know of to do. I'm out of ideas. It seems like a great phone and I really want to fix this so any help would be greatly appreciated.
If the bootloader is unlocked and you can flash a ROM, fastboot flash the boot.img from the ROM zip and see if it works. Detailed instructions in my signature.
bananagranola said:
If the bootloader is unlocked and you can flash a ROM, fastboot flash the boot.img from the ROM zip and see if it works. Detailed instructions in my signature.
Click to expand...
Click to collapse
Unfortunately I can't enter recovery to flash a rom. It just reboots at the white screen. The only thing I was able to flash was the stock RUU. And it still didn't boot. I've also tried flashing recoveries but that doesn't work either. It flashes successfully but never boots into it.
Sent from my XT897 using xda app-developers app
No one knows what to do? I really want to fix this.
Sent from my XT897 using xda app-developers app
Related
Hi everyone,
i am so very new to this. here it goes. I tried to root my HTC One S and install cm9. well the root worked. I installed the cm9 rom. that looked like it worked too. so i went to turn the phone on and it booted up ok, showed the cm9 boot up animation, then the screen went completly white and stayed like that. well i booted up into clockworkmod recovery, did a factory reset (i also did a factory reset/clear storage in bootloader), and accidentally erased everything, i think. stock rom, cm9 everything. now i can only get the phone to boot up into the bootloader or clockworkmod recovery. so i think its bricked. it tried to install the tmobile ruu and that failed. idk what to do, im really nervous i wont be able to get my phone back. cwmr also says it cant mount sd card..when i plugged the phone in to the computer, devices menu says android and sometimes it says ville. If someone is able to give me step by step instructions on how to fix this, i would greatly appreciate it because i am freaking out. I have seen the term flash around the forums idk what that means or how to do it. i also tried forcing a new rom thru adb and that didnt work. i really dont know what to do at this point. I would greatly appreciate it, if someone can help me with this.
Thanks
Frank
My guess would be: flash the stock recovery via fastboot.
Then get a RUU and install it. (and you probably just had the white screen because u didn´t flash boot.img).
southkill said:
My guess would be: flash the stock recovery via fastboot.
Then get a RUU and install it. (and you probably just had the white screen because u didn´t flash boot.img).
Click to expand...
Click to collapse
stupid question, but i am really not sure how to do that. where would i get the stock recovery? and what would the comand be in fastboot?
do i install the RUU while its locked, or unlocked?
flost0590 said:
Hi everyone,
i am so very new to this. here it goes. I tried to root my HTC One S and install cm9. well the root worked. I installed the cm9 rom. that looked like it worked too. so i went to turn the phone on and it booted up ok, showed the cm9 boot up animation, then the screen went completly white and stayed like that. well i booted up into clockworkmod recovery, did a factory reset (i also did a factory reset/clear storage in bootloader), and accidentally erased everything, i think. stock rom, cm9 everything. now i can only get the phone to boot up into the bootloader or clockworkmod recovery. so i think its bricked. it tried to install the tmobile ruu and that failed. idk what to do, im really nervous i wont be able to get my phone back. cwmr also says it cant mount sd card..when i plugged the phone in to the computer, devices menu says android and sometimes it says ville. If someone is able to give me step by step instructions on how to fix this, i would greatly appreciate it because i am freaking out. I have seen the term flash around the forums idk what that means or how to do it. i also tried forcing a new rom thru adb and that didnt work. i really dont know what to do at this point. I would greatly appreciate it, if someone can help me with this.
Thanks
Frank
Click to expand...
Click to collapse
try to relock your bootloader with the all in one toolkit and after that, while your phone is in fastboot usb mode with the bootloader reloked, install the offial ruu for your phone. Try to find the download of the original ruu, it is an exe file, when you run it the phone must be connected in fastboot usb, if everything goes fine the phone should be back to stock.
Ok I will try tonight. Hopefully it works.
Sent from my HTC_A510c using xda app-developers app
Will the code be fastboot flash push filename.exe /sdcard? If not what would the code be in fastboot?
Sent from my HTC_A510c using xda app-developers app
flost0590 said:
Will the code be fastboot flash push filename.exe /sdcard? If not what would the code be in fastboot?
Sent from my HTC_A510c using xda app-developers app
Click to expand...
Click to collapse
well i tried this method and this is what i got. it said bootloader signature failed. can someone help me with this
c:\fastboot>fastboot flash push RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501
S.16_2_10.22.31501S.10L_release_263233_signed.exe
sending 'push' (578821 KB)...
OKAY [ 24.679s]
writing 'push'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 71.776s
flost0590 said:
Will the code be fastboot flash push filename.exe /sdcard? If not what would the code be in fastboot?
Sent from my HTC_A510c using xda app-developers app
Click to expand...
Click to collapse
.EXE are run on your Windows PC. Connect phone to PC in fastboot mode. Click on.exe file on PC and follow directions on PC screen.
ok what if RUU fails with error 155?
i even extracted rom.zip from the RUU and tried to push it. both no go.
Yes I get the sane thing.
Sent from my HTC_A510c using xda app-developers app
Well I ended up funding a way to fix it. What I did was, relocked it, updated the drivers, then installed the stock rom
Sent from my Nexus 7 using xda app-developers app
flost0590 said:
Well I ended up funding a way to fix it. What I did was, relocked it, updated the drivers, then installed the stock rom
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Well I have a simular situation as I flashed the viper rom everything worked fine fof about a week now it will only boot straight to recovert but it wont mojnt sd card and I can also get to bootloader but thats it and I can get ig to ruu ??? So just so you know im rooted CWM and its unlocked sOff thanks PLEASE ADVISE
Please help with patients
sorry
i cannot boot phone into recovery nor can i boot phone normally... I had just installed Viper one S rom on my phone and rebooted into recovery because my wifi wasnt working , so i was just going to revert back to an old rom. After clicking reboot to recovery from Viper rom the screen just went white . I had to power it down manually, after powering it up it would stop at htc screen with the red development lines... tried to go into recovery and it will come up for a second then disapear then phone reboots.... any ideas? oh I also had installed Latest radio in CWM after installing rom.. I hear its buggy in CWM...
I had the same problem. Did you flash the boot.IMG in recovery or fastboot? If you flashed in recovery and its not supported by your hboot version. That could be the issue. Try re flashing the boot.IMG using fastboot. If you still cannot get it to work. I would try reinstalling a custom recovery manually and restarting the Rom flashing process. There are forums all over the place to help with that. Try twrp. Ps this is all assuming you are able to get into your boot loader.
Sent from my HTC One S using xda app-developers app
Problem fixed. Don't ask me how lol. All I did was relock boot loader and flash stock ROM. Stock ROM would not load so I just decided to unlocked boot loader and phone rebooted fine. Recover works to.. crazy.
Sent from my HTC One S using xda premium
That happened to me when I didn't fast boot flash the boot.IMG file, but only the latest Viper has given me grief with that.
Sent from my HTC One S using xda app-developers app
MrPickleFicker said:
That happened to me when I didn't fast boot flash the boot.IMG file, but only the latest Viper has given me grief with that.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Good to know so I won't make the same mistake twice.
Sent from my HTC One S using xda premium
ok soooooo on my first attempt ever to install a rom i get a shiny brick.
i unlocked it but im still s-on.
trying to power on just gets the t-mo splash screen and then black screen
can get into hboot but if i select recovery i just get a reboot.
tried several times to install cm9 through fastboot but i always get some damn error.
tried everything i could find on
nevermind, perserveriance pays off agin.
runnin 4.04 Woooooooooooooooooooo
1) Flash a stock-based ROM.
2) Follow the instructions for juopunutbear.
3) Flash the ROM.
4) Enjoy s-off.
If you don't want to risk juopunutbear, you can flash twrp or cwm recovery in fastboot. I'm pretty sure you can't flash custom ROMs from fastboot...
Sent from my myTouch_4G_Slide using xda app-developers app
I was using the all in one root kit, thought i followed everything correctly.
If I boot the phone up, it get's stuck on the HTC screen.
When I go to bootloader and select recovery it goes to TWRP. When I select a .zip rom to install it always fails.
Suggestions?
I rooted my phone yesterday and got a boot loop. I fix that by downloading the official RUU for the phone from HTC website and relock bootloader, flash the RUU. I don't know what happened to you though
Sent from my HTC One X using xda app-developers app
marsyeti said:
I rooted my phone yesterday and got a boot loop. I fix that by downloading the official RUU for the phone from HTC website and relock bootloader, flash the RUU. I don't know what happened to you though
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I think I managed to delete the OS that was on the phone, so now it has no OS. But I'm not sure. I'm hoping one of these smart guys can tell me the problem/solution
.
whec716 said:
I was using the all in one root kit, thought i followed everything correctly.
If I boot the phone up, it get's stuck on the HTC screen.
When I go to bootloader and select recovery it goes to TWRP. When I select a .zip rom to install it always fails.
Suggestions?
Click to expand...
Click to collapse
what does it say when it fails installing the rom? are you sure the rom is for the right device?
also, maybe the rom is corrupt? you could try downloading it again (if you are sure it's for your device).
Turn off md5 check in twrp. Then try flashing again. If your on Hboot 1.14 you'll need to flash that boot IMG for that rom in adb first.
Sent from my One X using xda premium
Just got the HTC One S( HTC branded S4 edition). I unlocked the boot loader, rooted , flash a recovery , and then installed CM10. Everything went well until the final install , when the Cyanogen Boot was stuck. I have no idea what I did afterwards, but now the SD is unmounted. It doesn't boot up to HTC stock , the HTC developer pages just open and stays on .. I could fastboot. I backed up everything, but somehow everything got deleted.
What to do? I need help!
Sent from my Nexus 4 using xda app-developers app
Sounds to me like you forgot to flash the kernel, then did something else wrong afterwards in the attempt to fix. I have the S3 version, but I had a similar problem with the ROM getting stuck, then my recovery was unable to mount the SD. There are 2 options, one is to use fastboot to re-lock your device, and flash the latest RUU for your CID, or you can adb sideload a ROM if you are using TWRP. I would probably go for the RUU anyway because it is the easiest. Just go into the bootloader, choose 'fastboot', use the command to re-lock the bootloader (I just use the All-In-One Tool) and then run the RUU when the phone is in fastboot mode, the phone will then be good as new (except for the Tampered warning in bootloader, but that can be remedied with the S4 version)
This happened to me just flash TWRP wipe everything and get another ROM on there
Sent from my One S using xda app-developers app
I'll try tonight when I get a chance.. And let you know how it went. Thank you.
Sent from my Nexus 4 using xda app-developers app
ferndom said:
I'll try tonight when I get a chance.. And let you know how it went. Thank you.
Click to expand...
Click to collapse
I was in the exact same situation as you, it worked for me (on the second repeat). If it doesn't work the first time, then just try again.
Ami007 said:
Sounds to me like you forgot to flash the kernel, then did something else wrong afterwards in the attempt to fix. I have the S3 version, but I had a similar problem with the ROM getting stuck, then my recovery was unable to mount the SD. There are 2 options, one is to use fastboot to re-lock your device, and flash the latest RUU for your CID, or you can adb sideload a ROM if you are using TWRP. I would probably go for the RUU anyway because it is the easiest. Just go into the bootloader, choose 'fastboot', use the command to re-lock the bootloader (I just use the All-In-One Tool) and then run the RUU when the phone is in fastboot mode, the phone will then be good as new (except for the Tampered warning in bootloader, but that can be remedied with the S4 version)
Click to expand...
Click to collapse
Thanks to all, especially to member Ami007. Im back and running again. I relocked the bootloader using fastboot, downloaded the correct RUU file that corresponds to my phone, and run the program.. Kudos to all!!!