So I'm trying to install a custom rom on a friends sprint evo 3d.
We unlocked it the HTC method btw.
We can't install any Rom onto it. I've wiped it completley multiple times. When I try to start any rom it, it just sits on the HTC screen.
Could I get some help please?
Sent from my Galaxy Nexus
Anybody?
Sent from my Galaxy Nexus
I recommend getting s-off since it makes flashing roms substantially easier. This thread by ramjet73 is the easiest way to do it. http://forum.xda-developers.com/showthread.php?t=1889438
Imagika FTW... with Tapatalk 2
What do you do if the ruu doesn't see the phone and it won't install any roms
Sent from my Galaxy Nexus
Garridon said:
What do you do if the ruu doesn't see the phone and it won't install any roms
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Do you have the drivers installed if you're on a windows PC? If not, download HTC sync and install it. Then uninstall it but leave the drivers installed.
Imagika FTW... with Tapatalk 2
Well I felt pretty dumb finding out these ruu programs need you to be booted into android for it to start the process. I tryed one of the pg85img zip files and it got to the part where it said checking, when it finished it did nothing, no errors or anything just went back to the main boot loader screen.
I've never had a bricked phone before, could this be possible? Any Roms installed, they don't even show a boot animation, just stays on the HTC screen.
My brother said before all this was happening, he tryed using an ruu and it failed saying something about check your USB cable.
Sent from my Nexus 7 using XDA Premium HD app
Garridon said:
Well I felt pretty dumb finding out these ruu programs need you to be booted into android for it to start the process. I tryed one of the pg85img zip files and it got to the part where it said checking, when it finished it did nothing, no errors or anything just went back to the main boot loader screen.
I've never had a bricked phone before, could this be possible? Any Roms installed, they don't even show a boot animation, just stays on the HTC screen.
My brother said before all this was happening, he tryed using an ruu and it failed saying something about check your USB cable.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
you didn't brick it.
However if I'm not severely mistaken PG85IMG is for the Amaze 4G and not the Evo 3D... so don't try that again... as it will likely brick your phone if you force it.
you say your phone goes into a bootloop whichever rom you install? did you wipe data/cache/dalvik?
I second coal686's suggestion about S-OFF as some (a LOT) of roms have problems with higher hboot versions.
I don't even get to the boot animation, it is stuck on the HTC screen.
Sent from my Galaxy Nexus
Garridon said:
I don't even get to the boot animation, it is stuck on the HTC screen.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
can you boot into recovery? (vol down+ power)
if so flash the contents of a RUU through fastboot
Thanks anyways guys, he ended up selling the phone. I fixed the galaxy s 2 his friend gave him, so he has that now.
But boy do I miss sense. I never got to fully use sense 4
Sent from my Galaxy Nexus
Related
Hi, ever since last night my wife's Amaze has been stuck in a boot loop. The white HTC logo screen comes up and then it reboots and the same thing happens over and over. It was running firmware 2.14.531.3. I was able to boot into hboot and re-lock the bootloader with fastboot to flash the RUU and I flashed the latest one which is RUBY_ICS_35_S_TMOUS_2.14.531.3_R2 but still the same thing happens I even flashed it a second time but no dice. I'm really not sure what to do here. Did some other things too like take out the battery put it back in after a few minutes, charged it while the phone was off. If anyone has any ideas please help. Thank you
So no one has any ideas?
Sent from my Nexus 7 using Tapatalk 2
rock7632 said:
So no one has any ideas?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Try factory resetting in the stock recovery, then reloading the ruu via hboot.
(reboot into stock recovery from hboot, volume up and power button to bring the menu up so you can wipe the device)
Though reloading a stock ruu should wipe everything, are you getting any errors when reloading the stock ruu? And which one of the ruu files are you using to reload?
rock7632 said:
So no one has any ideas?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
You don't flash the ruu.. you need to put the file in root of ur SD and rename it to ph85img or something like that and reboot in the bootloader
Sent from my HTC_Amaze_4G using xda app-developers app
Dark Nightmare said:
Try factory resetting in the stock recovery, then reloading the ruu via hboot.
(reboot into stock recovery from hboot, volume up and power button to bring the menu up so you can wipe the device)
Though reloading a stock ruu should wipe everything, are you getting any errors when reloading the stock ruu? And which one of the ruu files are you using to reload?
Click to expand...
Click to collapse
I can try that. and no I didn't get any errors when loading the ruu. the one I did was the latest one for T-Mobile us 2.14.531.3_R2.
Perry977 said:
You don't flash the ruu.. you need to put the file in root of ur SD and rename it to ph85img or something like that and reboot in the bootloader
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
uhh yes that's what I did
Sent from my Galaxy Nexus using Tapatalk 2
rock7632 said:
I can try that. and no I didn't get any errors when loading the ruu. the one I did was the latest one for T-Mobile us 2.14.531.3_R2.
uhh yes that's what I did
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Did you try different kernel?
Sent from my HTC_Amaze_4G using xda app-developers app
Perry977 said:
Did you try different kernel?
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
RUU flashed the stock kernel when he reloaded.
Dark Nightmare said:
RUU flashed the stock kernel when he reloaded.
Click to expand...
Click to collapse
yeah and even prior to that I had the stock kernel
Sent from my Nexus 7 using Tapatalk 2
rock7632 said:
yeah and even prior to that I had the stock kernel
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Do u still have the custom recovery?
Sent from my HTC_Amaze_4G using xda app-developers app
Are you s-off? SuperCID? you need to set both back to the original values and reflash stock ROM from bootloader.
Perry977 said:
Do u still have the custom recovery?
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
no i flashed the stock recovery before i loaded the RUU.
olegy said:
Are you s-off? SuperCID? you need to set both back to the original values and reflash stock ROM from bootloader.
Click to expand...
Click to collapse
I'm s-on
Sent from my Nexus 7 using Tapatalk 2
rock7632 said:
no i flashed the stock recovery before i loaded the RUU.
I'm s-on
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Even if, you didn't need to reflash anything, apparently the fact that the ruu wipes and restores everything to stock still hasn't sunk in yet, anyways, we're missing some info here, what else happened before this issue that you're not telling me, since bootloop issues are easily resolved by a stock reload via hboot but yours seems to be on the same loop no matter what, are you giving it the time to boot after reloading via hboot? First boot takes a bit of time, patience is very vital.
Dark Nightmare said:
Even if, you didn't need to reflash anything, apparently the fact that the ruu wipes and restores everything to stock still hasn't sunk in yet, anyways, we're missing some info here, what else happened before this issue that you're not telling me, since bootloop issues are easily resolved by a stock reload via hboot but yours seems to be on the same loop no matter what, are you giving it the time to boot after reloading via hboot? First boot takes a bit of time, patience is very vital.
Click to expand...
Click to collapse
Ya like he^^ said, it does take a very long to boot up after flashing an ruu, could take a good 10 mins or maybe more...
Now if you did wait and it still just bootlooped after flashing the ruu, either the ruu is bad, or u did something wrong, OR u got some serious software problems going on
Due to the fact, atleast from reading your first post, it sounds like it was running fine then suddenly just started bootlooping. And then flashing an ruu didn't fix it. Sounds to me like ur phone has some serious issues
sent from my NRGized Amaze,
powered by faux kernel v.13
Dark Nightmare said:
Even if, you didn't need to reflash anything, apparently the fact that the ruu wipes and restores everything to stock still hasn't sunk in yet, anyways, we're missing some info here, what else happened before this issue that you're not telling me, since bootloop issues are easily resolved by a stock reload via hboot but yours seems to be on the same loop no matter what, are you giving it the time to boot after reloading via hboot? First boot takes a bit of time, patience is very vital.
Click to expand...
Click to collapse
That's just it, after loading the ruu via hboot the phone asks for a reboot and when I do it it barely takes 5 seconds on the HTC logo white screen then the phone reboots again and the same thing happens. And as far as anything happening before, nothing really happened. The battery died a couple of days ago and the when we charged it and tried to turn on the phone this started happening
Sent from my Galaxy Nexus using Tapatalk 2
I've tried everything I could think of. Loaded 2 different ruu's, manually wiped everything from recovery and nothing has worked, its still doing the exact same thing. I really don't understand how it can be bricked just out of nowhere
Sent from my Nexus 7 using Tapatalk 2
rock7632 said:
I've tried everything I could think of. Loaded 2 different ruu's, manually wiped everything from recovery and nothing has worked, its still doing the exact same thing. I really don't understand how it can be bricked just out of nowhere
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I think Im having an issue similar to yours. Is there any interaction after it begins to flash the RUU? I found a video for the thunderbolt where it asks you to approve the update before it finishes. My phone does the update then jumps back to the fastboot screen.
Me and my friend have been trying to root his HTC Thunderbolt and we thought everything was going pretty smoothly. We found one of the versions of the Liquid ICS and moved that to his SD card and we unlocked the bootloader using the HTC dev site and everything was working just fine. We even got to the point where we could flash CWM onto the device and even that seemed to go smoothly. But after we flashed clockwork onto the phone we were only able to get to recovery. Anytime we try to boot into the rom that we installed it just sits on the white HTC screen. We've wiped data, dalvik and cache, which is a common cause for bootlooping and common errors as such. Any help with this would be greatly appreciated, my friend is concerned about not having a phone and is actually considering purchasing a phone for retail price off of amazon, and I really think thats a waist considering this phone isn't bricked, and I think the geniuses here at XDA can definitely help us out of this pickle. Thanks in advanced - Randy
Coldfusion94 said:
Me and my friend have been trying to root his HTC Thunderbolt and we thought everything was going pretty smoothly. We found one of the versions of the Liquid ICS and moved that to his SD card and we unlocked the bootloader using the HTC dev site and everything was working just fine. We even got to the point where we could flash CWM onto the device and even that seemed to go smoothly. But after we flashed clockwork onto the phone we were only able to get to recovery. Anytime we try to boot into the rom that we installed it just sits on the white HTC screen. We've wiped data, dalvik and cache, which is a common cause for bootlooping and common errors as such. Any help with this would be greatly appreciated, my friend is concerned about not having a phone and is actually considering purchasing a phone for retail price off of amazon, and I really think thats a waist considering this phone isn't bricked, and I think the geniuses here at XDA can definitely help us out of this pickle. Thanks in advanced - Randy
Click to expand...
Click to collapse
Your first problem is that you used HTC dev. You need to relock the bootloader and use the allinone tool to unlock get root and s off. The problem is that liquid ice has a custom kernel and you can't flash those with a locked bootloader.
Sent from my ThunderBolt using Tapatalk 2
Could you link me to a thread on how to do that without getting your computer to recognize the phone? Because as is, the phone can't be recognized seeing as it won't boot and its either stuck at a white screen, on HTC's boot loader *which is unlocked*, or clockwork recovery mod.
Before you setup your phone you need to fast boot flash a stock ruu. You should have made a nand in cwm before you ever attempted to flash a rom. If you did you wouldn't have this problem right now. You could just restore that backup in recovery and you would be rooted stock. Then you could follow the relock procedure and use the allinone tool to unlock and get s off.
Sent from my ThunderBolt using Tapatalk 2
Well that would be where we screwed up. we never made the nandroid back up and we kept trying to flash the RUU onto the phone via HBOOT but that doesn't work either. It says that is radio version 1.49.etc. inside of the bootloader.
You will need to give me more info about your radios. What baseband are you running?
Sent from my ADR6400L using Tapatalk 2
Alright so I dropped it off with my good friend Ryan and he was able to manually flash the RUU onto the phone and got it to boot stock. So we are done with our phone adventures for a little while. Thanks for offering to help, but we got it all solved
Now that you're root stock you can relock and then use the all in one tool.
Sent from my ADR6400L using Tapatalk 2
Was unlocking my bootloader which I did, but still in S on. Now I can not get past the HTC screen. I have tried wiping my device and loading cm10.1 but still can not get past the htc screen.
I know I'm missing something.
I have been installing roms on my original incredible for years and never run into this.
Raven2m said:
Was unlocking my bootloader which I did, but still in S on. Now I can not get past the HTC screen. I have tried wiping my device and loading cm10.1 but still can not get past the htc screen.
I know I'm missing something.
I have been installing roms on my original incredible for years and never run into this.
Click to expand...
Click to collapse
did you pull the boot image from the zip and flash that?
Yup you gotta flash the boot image.
Sent from my Incredible 4G LTE using Tapatalk 2
Feeling like a rookie here, I can't see the boot image file on my sd from twrp.
Did some searching and found some post about that and some command but not sure where to run them.
http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
Once you have that setup, pull the "boot.img" from the zip and save it on your PC, boot into bootloader, fastboot, open command prompt on PC, cd to the directory on your PC where you saved "boot.img" and do:
Code:
fastboot flash boot boot.img
You can use the boot image from this post.
http://forum.xda-developers.com/showthread.php?p=31717351
Sent from my Incredible 4G LTE using Tapatalk 2
MJL99 said:
You can use the boot image from this post.
http://forum.xda-developers.com/showthread.php?p=31717351
Sent from my Incredible 4G LTE using Tapatalk 2
Click to expand...
Click to collapse
??? He said he's flashing Cyanogenmod
Edit: oops ignore
Raven2m said:
Was unlocking my bootloader which I did, but still in S on. Now I can not get past the HTC screen. I have tried wiping my device and loading cm10.1 but still can not get past the htc screen.
I know I'm missing something.
I have been installing roms on my original incredible for years and never run into this.
Click to expand...
Click to collapse
Did you wipe davlik cache?
Thanks for all the help, been busy, going to try to get it working tonight.
I wanted to unroot my phone i was running nusense's desensed custom ics rom and had the ics radio. I stupidly flashed the original RUU hoping that it will unroot and bring me to stock. This wasn't the case it only locked my bootloader, gave me s-on, and downgraded the radio and failed the rest of the update. The phone is stuck in the bootloader, i tried getting it connect to adb it is not reading my phone. On windows it says unrecognized usb device sometimes and other times it doesnt read it at all. I tried flashing the RUU for froyo and gingerbread but both say update failed main version is older! ....Can anybody help me please! Thank you
Do a battery pull and let it sit, same thing happened to me trying to run the unroot tool from rooted stock. After sitting for ~1 hr, it rebooted fine.
Tiezane said:
Do a battery pull and let it sit, same thing happened to me trying to run the unroot tool from rooted stock. After sitting for ~1 hr, it rebooted fine.
Click to expand...
Click to collapse
I don't think thats the case because I flashed the froyo RUU when i was rooted and had an ics official custom rom with radio. I can't get past the s-on with **locked** and **security warning** in pink bootloader and cannot get my phone to get recognized in fastboot. so i cant do anything in adb, i think my solution would be to get my phone to correctly register in my computer so i can use htc dev to root again but i cannot get it to get recognized. Any other ideas?
jcip17 said:
I don't think thats the case because I flashed the froyo RUU when i was rooted and had an ics official custom rom with radio. I can't get past the s-on with **locked** and **security warning** in pink bootloader and cannot get my phone to get recognized in fastboot. so i cant do anything in adb, i think my solution would be to get my phone to correctly register in my computer so i can use htc dev to root again but i cannot get it to get recognized. Any other ideas?
Click to expand...
Click to collapse
http://www.thunderboltforums.com/forum/htc-thunderbolt-help/7853-how-fix-security-warning.html
If I put the RUU in the root of my sd card it checks it twice, the first loading bar is blue the second one is green then it says update failed main version is older then asks to reboot and will do the same thing everytime
Try this
http://www.forums.infectedrom.com/showthread.php?p=67914
The reason you can't Ruu is because your main version is higher than that of the Ruu you're trying to use. This needs to be changed so that you can downgrade to flash an Ruu. This may not work since it sounds like a bad flash
Sent from my ADR6400L using Tapatalk 2
my problem really is to get my phone to get recognized by my computer so i can do the htc dev unlock, i followed all the steps but all it says is waiting for device when i type fastboot oem get_identifier_token....If i can get past this i should be golden, if you have any ideas to force my phone to get recognized i should be able to fix this...Thanks for you advice and time
What os are you running?
Sent from my Nexus 7 using Tapatalk 2
disconnecktie said:
What os are you running?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I'm using windows 7 home edition 64-bit
Have you tried uninstalling any drivers you have currently installed and then installed the drivers that are included with the guide?
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
Have you tried uninstalling any drivers you have currently installed and then installed the drivers that are included with the guide?
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
I will try that and get back to you, thank you
so ya it doesn't work....
Hmmm I'm at a loss but it sounds like you might have ever bricked. Since there isn't anymore ruus.
Sent from my Nexus 7 using Tapatalk 2
disconnecktie said:
Hmmm I'm at a loss but it sounds like you might have ever bricked. Since there isn't anymore ruus.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
so you don't think there will be an ics official ruu? lol
jcip17 said:
so you don't think there will be an ics official ruu? lol
Click to expand...
Click to collapse
The update came in the form of a patch that patches 2.3.6 into ics 4.0.4. HTC is also stopping the distribution of ruus and has even went so far as shutting down sites that distribute them. There will not be an Ruu for the ics ota.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
The update came in the form of a patch that patches 2.3.6 into ics 4.0.4. HTC is also stopping the distribution of ruus and has even went so far as shutting down sites that distribute them. There will not be an Ruu for the ics ota.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Bummer :crying:
disconnecktie said:
HTC is also stopping the distribution of ruus and has even went so far as shutting down sites that distribute them. There will not be an Ruu for the ics ota.
Click to expand...
Click to collapse
I wouldn't normally correct you, but you do have this a little wrong. They didn't ask him to take down the site because he was hosting RUUs, but because he had a) a domain name that included HTC's name in it (http://htcruu.com), and b) he unknowingly had unreleased RUUs on there. HTC requested he give up the domain name and remove the unreleased RUUs, but they let him continue to host the others, including the custom Sense-based roms. The story is here: http://rootzwiki.com/news/_/article...p-the-ruus-just-give-us-the-domain-name-r1365. Football hadn't leaked anything in a while, but I would bet we still see full RUUs released.
Sent from my Sega Master System via Carrier Pigeon.
I'll give you that but why would they make every other update an Ruu except this one? Doesn't make sense unless they intend on phasing the Ruu out.
Sent from my ADR6400L using Tapatalk 2
I'd wait to see, maybe they'll start releasing them along with source.
Sent from my Sega Master System via Carrier Pigeon.
Maybe but this patched style of updating is way smaller than pushing an ota to everyone. Easily half the size of an ruu.
Sent from my Nexus 7 using Tapatalk 2
Hey guys I had to send my HTC One back to ATT. So I stupidly tried to get it back to stock, so I first flashed an Odex-ed Stock Rooted Rom, then flashed stock recovery in fastboot, then locked the bootloader and am now trying to run the RUU. And it doesnt seem to be working..what do I do? I just keep booting into the bootloader straight. Im so lost.
So your bootloader is locked, you start the ruu and what happens?
I had a similar issue. For some resason all of my laptops had issues with drivers. If you go in device manager in windows, check to see if you see exclamation mark on my HTC.
I tried different drivers, sync app from HTC and even fresh virtual box environments on MacBook to no avail. It always shows that yellow exclamation when in bootloader.
Anyways, didn't mean to hijack your thread but just trying to see what's in your device manager. Try hansoon HTC one app?
Sent from my HTC One using xda app-developers app
it either says "Phone not found" or the RUU wont even open .. will say issues with drivers
Damn, I hope you get it figured out. I wish I could help. I know I better keep my htc one stock for the time being. This could of happened to me.
Sent from my HTC One using Tapatalk 2
Packer2058 said:
Hey guys I had to send my HTC One back to ATT. So I stupidly tried to get it back to stock, so I first flashed an Odex-ed Stock Rooted Rom, then flashed stock recovery in fastboot, then locked the bootloader and am now trying to run the RUU. And it doesnt seem to be working..what do I do? I just keep booting into the bootloader straight. Im so lost.
Click to expand...
Click to collapse
Lol u can't just lock ur boot loader u have to run the firmware first and u must unroot all he had to do is unlock bootloader again and it would of booted
Sent from my HTC Butterfly using xda premium
Packer2058 said:
it either says "Phone not found" or the RUU wont even open .. will say issues with drivers
Click to expand...
Click to collapse
Reinstall the drivers
daorderdillon said:
Lol u can't just lock ur boot loader u have to run the firmware first and u must unroot all he had to do is unlock bootloader again and it would of booted
Sent from my HTC Butterfly using xda premium
Click to expand...
Click to collapse
yea i unlocked bootloader and it booted...what to do now
Packer2058 said:
yea i unlocked bootloader and it booted...what to do now
Click to expand...
Click to collapse
Flash a Rom like android revolutionary
Sent from my HTC Butterfly using xda premium