Related
ok so i flashed cynogenmod 7 today and i decided that i really wasnt that into it. I want to flash back to stock and when i did it the progress bar flashed red halfway through and the screen went to HTC black and silver with triangle with exclamation points in them. I tried getting tot he bootloader screen but when i push power and volume down button it just stays on the htc with triangles screen. Please help!
Bump. I can't help you but I feel so bad when people are desperate for help and don't get it. So here's a bump to get it noticed
Sent from my Optimus V
96camarors said:
ok so i flashed cynogenmod 7 today and i decided that i really wasnt that into it. I want to flash back to stock and when i did it the progress bar flashed red halfway through and the screen went to HTC black and silver with triangle with exclamation points in them. I tried getting tot he bootloader screen but when i push power and volume down button it just stays on the htc with triangles screen. Please help!
Click to expand...
Click to collapse
Were you running an RUU when thus happened? Was that how you were getting back to stock? How long has it been on that screen? If your sure its stuck, and is idle, I would do a battery pull, and then see if you can get to the bootloader. If you can, try running the RUU again, but put the phone in fastbood mode when you run the RUU. See if a second time gets it.
Sent from my PC36100 using XDA App
k2buckley said:
Were you running an RUU when thus happened? Was that how you were getting back to stock? How long has it been on that screen? If your sure its stuck, and is idle, I would do a battery pull, and then see if you can get to the bootloader. If you can, try running the RUU again, but put the phone in fastbood mode when you run the RUU. See if a second time gets it.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I was running ruu and it failed. i have tried several times since including battery pulls and no luck. I keep trying to get to the bootloader but its stuck at that screen. It does not show up in my computer either when i plug it in but using an ruu still works.
When trying to get to bootloader, did you push power / volume down after phone was off? If not, pull battery. Put back in and then power/volume down.
You probably already did this but it sort of sounded like you tried getting to bootloader from the screen you were stuck on.
J
Bump
Sent from my PC36100 using XDA Premium App
The error i get when ruu fails is error 110 file open error. The rom update utility cannot open the requested files or the files are damaged. the ruu cannot continue with the update. Please get a complete ruu package and try again.
96camarors said:
I was running ruu and it failed. i have tried several times since including battery pulls and no luck. I keep trying to get to the bootloader but its stuck at that screen. It does not show up in my computer either when i plug it in but using an ruu still works.
Click to expand...
Click to collapse
When you shut your Evo off, and plug it into a wall (AC) plug, do you get a charging led? If you can still run an RUU, it sounds like maybe the one you are using is corrupt, or the wrong one all together. Do you know your bootloader version, software version, and radio versions? Likely you need to download the RUU that matches (or is very close to) your current versions.
I'm on the app, but would otherwise link you to a thread. In the dev section, search for "supersonic shipped roms", thread started by Esp28
Sent from my PC36100 using XDA App
ferfy67 said:
When trying to get to bootloader, did you push power / volume down after phone was off? If not, pull battery. Put back in and then power/volume down.
You probably already did this but it sort of sounded like you tried getting to bootloader from the screen you were stuck on.
J
Bump
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
yeah i did that and nothing just stays at the screen
k2buckley said:
When you shut your Evo off, and plug it into a wall (AC) plug, do you get a charging led? If you can still run an RUU, it sounds like maybe the one you are using is corrupt, or the wrong one all together. Do you know your bootloader version, software version, and radio versions? Likely you need to download the RUU that matches (or is very close to) your current versions.
I'm on the app, but would otherwise link you to a thread. In the dev section, search for "supersonic shipped roms", thread started by Esp28
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
i am currently trying to download the 3.7 ruu but it keeps canceling itself. i do get a chargin led when plugged into wall. radio is 2.15
96camarors said:
i am currently trying to download the 3.7 ruu but it keeps canceling itself. i do get a chargin led when plugged into wall. radio is 2.15
Click to expand...
Click to collapse
Charging led is good. Find a good copy of the 3.70 RUU, make sure its a good download, and run again. When I get home ill link you to my RUU copy in my dropbox if you haven't found one yet.
Sent from my PC36100 using XDA App
k2buckley said:
Charging led is good. Find a good copy of the 3.70 RUU, make sure its a good download, and run again. When I get home ill link you to my RUU copy in my dropbox if you haven't found one yet.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
i found one that works and i have 46min to go. i found a good step-by-step fix for my problem http://androidforums.com/evo-4g-support-troubleshooting/254695-black-error-screen-when-updating-rooted-phone-supersonic-ruu.html and i am praying that it works for me. and thank you for your help so far!
96camarors said:
i found one that works and i have 46min to go. i found a good step-by-step fix for my problem http://androidforums.com/evo-4g-sup...hen-updating-rooted-phone-supersonic-ruu.html and i am praying that it works for me. and thank you for your help so far!
Click to expand...
Click to collapse
Cool, your welcome. I bet the good RUU will work. And yes, the other thread looked good. Did u run unrevoked forever? If so, did u flash the s on tool before running RUU?
Sent from my PC36100 using XDA App
k2buckley said:
Cool, your welcome. I bet the good RUU will work. And yes, the other thread looked good. Did u run unrevoked forever? If so, did u flash the s on tool before running RUU?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
i didnt flash s on tool. and that was my problem, i am new to the evo world (just got it sunday) and i had motorola before so the rooting i am used to is way different than htc haha
You get it fixed yet?
Sent from my PC36100 using Tapatalk
96camarors said:
i didnt flash s on tool. and that was my problem, i am new to the evo world (just got it sunday) and i had motorola before so the rooting i am used to is way different than htc haha
Click to expand...
Click to collapse
Yea, the rooting world between different manufacturers differs greatly, apparently. The state you're currently in, you probably have no choice but to run the RUU again. Once you get it to successfully run, and you boot up, back to stock, you'll most likely still be S-off. Now, that's not necessarily bad, unless you're going to take your evo into sprint for any reason. If you leave it S off, if you ever want to reroot, all you'd have to do is flash a PC36IMG of a custom recovery, using the bootloader. At that point, you could flash a ROM or whatever. Also, if you do want to return it to S on, once the RUU completes and you can boot, flash a PC36IMG of a recovery, using the bootloader. At that point, flash the unrevoked S on tool, using recovery. Once you confirm that S is back to ON, then run the RUU again. Then you'll be back to stock, unrooted, S on.
RileyGrant said:
You get it fixed yet?
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
not fixed yet 5min left on download
k2buckley said:
Yea, the rooting world between different manufacturers differs greatly, apparently. The state you're currently in, you probably have no choice but to run the RUU again. Once you get it to successfully run, and you boot up, back to stock, you'll most likely still be S-off. Now, that's not necessarily bad, unless you're going to take your evo into sprint for any reason. If you leave it S off, if you ever want to reroot, all you'd have to do is flash a PC36IMG of a custom recovery, using the bootloader. At that point, you could flash a ROM or whatever. Also, if you do want to return it to S on, once the RUU completes and you can boot, flash a PC36IMG of a recovery, using the bootloader. At that point, flash the unrevoked S on tool, using recovery. Once you confirm that S is back to ON, then run the RUU again. Then you'll be back to stock, unrooted, S on.
Click to expand...
Click to collapse
ok thanks for the advice. ill probly go back to stock for awhile until i get used to the phone. so if i leave s off then nothing bad while happen with the ruu while im sleeping? i really need to get to sleep asap, got a full day of classes tomorrow haha.
96camarors said:
not fixed yet 5min left on download
ok thanks for the advice. ill probly go back to stock for awhile until i get used to the phone. so if i leave s off then nothing bad while happen with the ruu while im sleeping? i really need to get to sleep asap, got a full day of classes tomorrow haha.
Click to expand...
Click to collapse
I'm confused, haha. Nothing bad will happen with the RUU when you're sleeping? I think you do need some sleep brotha! Once you successfully run the RUU, and return to stock, you'll most likely still be S off, since you didn't flash the S on tool. This mean's you'll be on a stock ROM, with S off, and no recovery. Nothing bad will happen by leaving it like this, so long as you don't take it to Sprint with S off. Now, if you do just plan on staying stock for a while, you may want to return to S-on, just in case any unpredictable catastrophic events occur, you're better off having S-on, in case you need to take it back to Sprint. You can always root again rather easily. So I guess my suggestion is to flash a recovery once you're up and running, flash the S on tool, and then run the RUU again. Just to be safe. If you want to root again, you know how
Edit: ^^^^All that is providing you get the RUU to run successfully, which I think you will. You just need a good copy of the right version. If that doesn't work, don't forget you have other options. Such as flashing an RUU as a PC36IMG from the bootloader. Also, you can run an RUU with fastboot. So there is a plan B and C if that doesn't work.
k2buckley said:
I'm confused, haha. Nothing bad will happen with the RUU when you're sleeping? I think you do need some sleep brotha! Once you successfully run the RUU, and return to stock, you'll most likely still be S off, since you didn't flash the S on tool. This mean's you'll be on a stock ROM, with S off, and no recovery. Nothing bad will happen by leaving it like this, so long as you don't take it to Sprint with S off. Now, if you do just plan on staying stock for a while, you may want to return to S-on, just in case any unpredictable catastrophic events occur, you're better off having S-on, in case you need to take it back to Sprint. You can always root again rather easily. So I guess my suggestion is to flash a recovery once you're up and running, flash the S on tool, and then run the RUU again. Just to be safe. If you want to root again, you know how
Edit: ^^^^All that is providing you get the RUU to run successfully, which I think you will. You just need a good copy of the right version. If that doesn't work, don't forget you have other options. Such as flashing an RUU as a PC36IMG from the bootloader. Also, you can run an RUU with fastboot. So there is a plan B and C if that doesn't work.
Click to expand...
Click to collapse
ok thank you very much. it worked. thanks for all your help!
96camarors said:
ok thank you very much. it worked. thanks for all your help!
Click to expand...
Click to collapse
Sweet, glad to hear it worked. Take care.
Oh yea, are you S on or S off? My guess is S off, if you did use unrevoked forever before.
k2buckley said:
Sweet, glad to hear it worked. Take care.
Oh yea, are you S on or S off? My guess is S off, if you did use unrevoked forever before.
Click to expand...
Click to collapse
Yes I am currently s off
EDIT: Not even close to a brick. Removing SD solved it. Able to boot into cwm recovery now.
OTA wiped out Dinc2. When booting to recovery - holding volume button down - I get HBOOT but it won't let me scroll through menu. HBOOT proceeds directly to an update, and reboots phone. Only have about 20 seconds when phone is up, so not enough time to freeze com.smithmicro.dm or rename otacerts.zip.
Windows is not recognizing the phone whatsoever. Shows "unknown device". Re-installed drivers from here: http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe but no love.
Is this a full brick?
Is there an ODIN like tool for the Dinc2?
Do you have radio on your sd card? If you do you need to delete it or pull your sd before booting into bootloader. This way you can get into recovery
Sent from my Incredible 2 using Tapatalk
Fear not you are far from bricked Do exactly as the post above mine says
Sent from my ADR6350 using xda premium
I don't think you understand the definition of bricked...
Sent from my ADR6350 using Tapatalk
bangdrum said:
Do you have radio on your sd card? If you do you need to delete it or pull your sd before booting into bootloader. This way you can get into recovery
Click to expand...
Click to collapse
Thank you.
I feel like a complete retard. Having used the Nexus S primarily over the last few months, I thought this phone had an internal HD like the Nexus S does. Doh!! Found SD, removed it, and was able to boot into clockwork.
I think I can take it from here.
Yeah... dumb... thanks all.
cheesiepoof said:
Thank you.
I feel like a complete retard. Having used the Nexus S primarily over the last few months, I thought this phone had an internal HD like the Nexus S does. Doh!! Found SD, removed it, and was able to boot into clockwork.
I think I can take it from here.
Yeah... dumb... thanks all.
Click to expand...
Click to collapse
Your welcome bro
Sent from my Incredible 2 using Tapatalk
glad you got it resolved. This thread should be deleted, as to not scare away future root users of being bricked.(or change the title) this was FAR from it. OP just needs some more time with HTC phones and root and you'll be a pro in no time!
Hey everyone!
Ok so heres the issue im in...i bought an htc to repair. the guy said the issue is he couldnt get it to turn on it turned on fine with me, but the touch wasnt working. Bootloader said Touchpanel- Fail. so i assumed this means its an LCD or digitizer problem! well i ended up getting another horrible HTC Evo, but one with a motherboard that works, just with broken usb. anyway, when i did this switch, surprisingly enough it worked, the touch was excellent, all ran perfectly!
So i guess the issue was neither LCD nor digitizer, so now it brings up a seperate question; software issue or motherboard issue?
if software i hold out hope that somehow id be able to fix it, expect the phone isnt rooted, so its with s-on and i cant so much as unlock the screen, and there is no custom recovery.
if motherboard, just let me know so i can give up.
Any and all help and advice appreciated!
Thanks!
~ Ramy
I would try and run a ruu on the phone and see if everything works after that. If it does work that means it was software related.
Support TrevE!
but see even ruus don't work, it errors out and says to get the right ruu, and on phone it says main is older....
It could be a bad motherboard it also could have been that the flex cables coming from the TSP/LCD were not fully connected, that being the issue you could see touch screen failure or a black screen when the device comes on. But from the sounds of it I think it might be bad software. Even though you've probably already thought about this I would suggest trying to do a full wipe and hard reset it.
ok but HOW? Without USB debugging I can't use adb with ruus I'm getting the aforemntiond error, and HTC does not have a stock recovery. Is there any other way to do it?
Take your battery out put it back in then hold volume down and power once it comes on go to the recovery option and should be able to wipe and hard reset
Sent from my PC36100 using xda premium
What is your hboot version and radio version?
Support TrevE!!
Riz3n said:
Take your battery out put it back in then hold volume down and power once it comes on go to the recovery option and should be able to wipe and hard reset
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
Again, this is an unrooted, s-off evo. HTC does not have a stock recovery, therefore pressing the recovery option takes me to the page with the triangle and exclamation mark.
I will respond with radio and hboot version soon, right now i gotta finish this preping for a test tomorrow ill let u know asap tho, thanks for your help so far all of you btw.
Hboot version is 2.16.0001, Radio is 2.15.00.05.02
When you get to the page with the triangle try pressing volume down and power again or volume up and power one of those combos should bring it up I believe mess around with it a little.
Sent from my PC36100 using xda premium
Riz3n said:
When you get to the page with the triangle try pressing volume down and power again or volume up and power one of those combos should bring it up I believe mess around with it a little.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
alright so i figured that part out thanks, i wiped and...nothing different...is it possible to flash an older update.zip or something to try and fix it? cause this just does factory restore, but if the drivers are messed up or something, restore wont do, reflash is needed...if i understand correctly..
Yes you can try and flash a different update zip from the recovery just put it in on your SD card and then apply update from zip.
Sent from my PC36100 using xda premium
Riz3n said:
Yes you can try and flash a different update zip from the recovery just put it in on your SD card and then apply update from zip.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
Any particular update.zip you recommend that should work? i tried a signed PC3600 or whatever its called but it gave the same error as the RUU, Main is Older.
Click this link and then go to section 3. There are a few different zips you can try maybe one of them will work... hopefully lol.
*edit*
You could also try this as it has a bunch of different zips and a step by step walk through that might help out.
Riz3n said:
Click this link and then go to section 3. There are a few different zips you can try maybe one of them will work... hopefully lol.
*edit*
You could also try this as it has a bunch of different zips and a step by step walk through that might help out.
Click to expand...
Click to collapse
Nope none of those worked, they installed but didn't fix issue, any other ideas? I'm gonna try to take it to sprint..
Sent from my Nexus S 4G using XDA Premium App
If they figure anything out let me know. If they dont they will just replace it lol
Sent from my synergized Evo using xda premium
My wife purchased a used EVO 4g on ebay. Clean esn but rooted. She took it to Sprint and they activated it for her no problems. She received notice today of an update. She tried to update the phone, but shortly after starting she gets the android character with the white triangle and yellow exclamation point and the update won't finish. When she bought the phone she asked him to replace it back to stock before shipping. He stated that he did. I can't get into bootloader to check the S-on/off.
First rule of thumb with a rooted phone: never accept an OTA update, as this is a sure-fire way to lose root. What ROM was on the phone when she received the phone? Also, when you try to power up the phone, what happens? Will the phone boot up or what?
Sent using my HTC EVO 4G and a magic wand
Not sure which ROM is on the phone. I will check and post it in a few. The phone works fine. Starts up and shuts down like it is supposed to. Just won't go into bootloader so i can check to see if it is still rooted. She was told he put it back to stock. Is there another way to tell for this phone?
Sent from my SPH-D710 using xda app-developers app
Depending upon what ROM is on the phone, the 'Fastboot' setting may be checked (Fastboot is an option that allows you to power on the phone more quickly when it's off, but to me it always was more trouble than it's worth and won't let you load into the bootloader when you use the volume down+power option). You can go to Menu>Settings>Application Settings and see if Fastboot is on. If it's on, turn it off, power the phone down, then press volume down+power to get into the bootloader. To see what ROM the phone is on, let the phone boot up and go to Menu>Settings>About Phone and scroll through there to see see what software is on the phone.
The phone is probably on Hboot 2.18, which can be rooted using the HTCDev method, if you're not familiar with it. Here's a link to the guide here on XDA:
http://forum.xda-developers.com/showthread.php?t=1473373
Ok, i have attached a picture of the bootloader screen i was able to get to after turning off the fastboot. If i read this right it is still rooted. The software number is 4.67.651.3 Android Version 2.3.5. It has H-Boot 2.10. We would like to put it back to complete stock. Which thread do i need to go to get that info? Thank you for your help.
Sent from my SPH-D710 using xda app-developers app
I found this Thread on unrooting the Evo. Just double checking, this one should work for the hboot version 2.10 correct?
http://forum.xda-developers.com/showthread.php?t=780141&highlight=hboot+2+10
Don't unroot just use captain throwbacks stock Rom its the newest version and if she doesn't like the Rom switch her to CM7 or if she doesn't like messing with stuff and want something simple let her try the mookee Rom.
Sorry if I'm spelling things wrong I'm just getting back to a sense Rom and using the stock keyboard is hard to get used to.
Sent from my PC36100 using xda premium
She has noticed several things going on with this phone. Out of nowhere it will reboot. If she makes a call it will reboot after she hangs up. If she puts the phone in vibrate, it will continuously vibrate until you turn it off. That is why I'm wanting to go back to stock.
Sent from my SPH-D710 using xda app-developers app
gtalkalot24 said:
She has noticed several things going on with this phone. Out of nowhere it will reboot. If she makes a call it will reboot after she hangs up. If she puts the phone in vibrate, it will continuously vibrate until you turn it off. That is why I'm wanting to go back to stock.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
As suggested above, I would go with a stock rooted ROM, which will allow you to keep root but give you pretty much everything the stock ROM has. The issues most likely lie within the current ROM on the phone and may be alleviated by going to another ROM.
Sent using my HTC EVO 4G and a magic wand
it seems that my friend has bricked his phone by installing a verizon boot loader in a at&t gs3 i tried going into recovery and download but nothing the phone wont boot or anything seems to be dead.
question is is there any way to fix it I tried many methods but all failed ):
Why would he install a verizon bootloader? He might have to get a jtag service to fix it. Bummer
Sent from my SGH-I747M using xda premium
undecided323 said:
it seems that my friend has bricked his phone by installing a verizon boot loader in a at&t gs3 i tried going into recovery and download but nothing the phone wont boot or anything seems to be dead.
question is is there any way to fix it I tried many methods but all failed ):
Click to expand...
Click to collapse
Jtag once i was having same issue with my brothers phone tried tiresly but no go
Sent from my SGH-I747M using xda premium
1) Charge battery & phone for an hour.
2) Pull battery for five minutes
3) Put battery back in
4) Press and hold VolumeDown+Power+Home
If that doesn't get you ANY display at all, not even a splash screen, then it's a "hard brick" and he'll need to send his phone out for "JTAG" repair. They are available on eBay for ~$50.
If you do get display, then come back and let us know for the next step (odin).
Some people think the phone is bootloader Locked. When they see that verizon version has bootloader unlock, they flash that.
I almost made that mistake, but I read and re-read everything for a week before even downloading stuff to try
Sent from my SGH-I747M using xda app-developers app
Is it possible for a usb jig to fix my problem?
undecided323 said:
Is it possible for a usb jig to fix my problem?
Click to expand...
Click to collapse
HIGHLY doubtful at the moment. Have you tried the above listed options?
Deoxlar said:
Some people think the phone is bootloader Locked. When they see that verizon version has bootloader unlock, they flash that.
I almost made that mistake, but I read and re-read everything for a week before even downloading stuff to try
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
Deoxlea...... WHAT.... HOW DARE YOU..... You mean you READ stickies? What are you trying to do. Set a good example?
My only option for the phone to start working is a jtag or a usb jig. I I ordered a usb jig and will report back if it fixes my phone
I have a jig from my old captivate that has worked both times I've tried to get into download.