Related
Hey guys,
I was wondering if someone could shed some light on my problem. I have a rooted EVO (rooted using the SimpleRoot program) running the Cyanogen Froyo RC.
I want to return the phone back to factory default since the official Froyo comes out this week anyways, and I don't want to have problems upgrading to the official version.
I attempted to run the RUU_Supersonic_1.47.651.1_Radio_2.05.00.06.10_release_CL195459 from shippedroms.com, but at first I was getting:
ERROR [170]: USB CONNECTION ERROR
Thinking it was probably a driver issue, I uninstalled HTC Sync, HTC Driver Installer, and PDANet (just for good measure), rebooted, and reinstalled (making sure virusscan was disabled).
I then connected my phone and reran the RUU. To my surprise, I got past the recognition and it got past the original error. As it attempts to flash the stock image, however, the first thing it does is reboot to the bootloader. The first thing I get is "waiting for bootloader..." and then after a timeout, I get:
ERROR [171]: USB CONNECTION ERROR
I just want to get this thing back to stock. Can anyone help me, please!?
EDIT: Maybe check this post out...I think this is actually what I did, but I already had nand unlocked.
http://forum.xda-developers.com/showthread.php?t=737447
with phone off: hold down power and vol-up, plug the phone in to the computer, now run your stock RUU. i believe that's what i had to do.
personally i would'nt do this, as you'll most likely lose your root, maybe for good. wait a 1/2 day for a rooted update to come out.
OneStepAhead said:
with phone off: hold down power and vol-up, plug the phone in to the computer, now run your stock RUU. i believe that's what i had to do.
personally i would'nt do this, as you'll most likely lose your root, maybe for good. wait a 1/2 day for a rooted update to come out.
Click to expand...
Click to collapse
I do agree everybody is so ready to unroot there EVO instead of just waiting till the devs say its ok or a good working 2. 2 Rooted Rom is here. Then you guys going to flooding the forums askinghow to get root back or how they lost root. I say if your phone is working great and you have uncap fps and a2sd work then just wait it out.
Sent from my PC36100 using Tapatalk
Ok I'm lost. I'm working today and my phone tries to reboot for no apparent reason and is put into a boot loop that I cannot get out of no matter what. In boot loader I have no recovery. Downloaded amon ra recovery's PC36IMG.zip. Booted into bootloader it said it updated the recovery but after I've rebooted I still have no recovery. I don't think this is very good.
Bootloader asked you to update and reboot and it went through completely?
Yeah, it said update was succesful. Thats why I'm so confused.
So when you go into recovery from the bootloader, do you see the triangle?
Nope just back to white screen boot loop. Trying to flash sprint lovers with the pcm36img over it maybe that will bring me back to stock rooted stat.
Edit: Back to white screen boot loop.
this same thing happened to me a week ago. were u running a cm7 rom?
yeah ex10 i was going to switch last night guess its too late
Damn I feel bad for you
I had that same problem when i first rooted and flashed my evo. I suddenly got into an infinite boot loop where i no longer had a recovery. Sorry man i had to take it to a sprint store after i tried flashing a different bootloader and then retry flashing a different recovery from clockwork to amon. and then even tried to flash the stock rom none work. if none of those work then you most likely is going to have to go to a sprint store.
Well, you could try running an RUU. This will leave you unrooted and completely stock so you will need to root again.
Here's a how-to over on Android Central.
http://forum.androidcentral.com/htc-evo-4g-rooting-roms-hacks/19278-how-unroot-return-stock.html
when this happened to me last friday i looked around xda and i found a couple other people who had this problem as well. everyone i found (myself included) was running a cm7 rom. i still cannot get any farther than bootloader without a white screen loop. sprint sent me a replacement on warranty because i live too far from the sprint store for them to make me drive there but i have to send my old one back. its still s-off tho and even running the stock ruu does nothing to fix that. anyone know of how to get s-on without the ability to enter recovery or anything else? or a way to brick it completely so it wont boot to bootloader where they can see s-off?
Threw mine out of the window of my car and called sprint and told them I lost it. Cost me $100 to get a replacement and now I'm going to have to spend forever getting back to root and eng boot ect... sucks.
Has this only happened with the magnus cm7 or is the happening with the official cyanogen rc1 and nightlies? Because I'm really wanting to go to the CM7 nightlies but not if the chance this is going to happen again.
ChacocII said:
when this happened to me last friday i looked around xda and i found a couple other people who had this problem as well. everyone i found (myself included) was running a cm7 rom. i still cannot get any farther than bootloader without a white screen loop. sprint sent me a replacement on warranty because i live too far from the sprint store for them to make me drive there but i have to send my old one back. its still s-off tho and even running the stock ruu does nothing to fix that. anyone know of how to get s-on without the ability to enter recovery or anything else? or a way to brick it completely so it wont boot to bootloader where they can see s-off?
Click to expand...
Click to collapse
Does the bootloader let you run a PC36IMG.zip? If so, try running one (of a factory unrooted ROM), and when it goes to reboot and shows the green arrow facing down (if it gets that far) yank the battery at that point. I think that is when it's writing the radio image. If you can get it to that point, and then pull the battery, I'm pretty sure you'll have a brick. Aside from a battery pull during the radio flash, I'm not sure how to make a brick, without it being obvious of what you've done. You could rig your phone charger up to a 230 volt outlet from a drier or something, and plug it in. haha. maybe that would fry it, tell sprint you got a power surge when it was charging, and then it wouldnt turn on. (only 1/8 serious on that last part )
Has this only happened with the magnus cm7 or is the happening with the official cyanogen rc1 and nightlies?
Happened to me with official cm7 rc1
Does the bootloader let you run a PC36IMG.zip?
yes, but it doesn't actually do anything. it will go thru the whole update process but still goes back to a white screen loop and no recovery. tried a battery pull during the radio update a couple hours ago (i thought the same thing) but it did nothing. i think its because its not actually doing anything when u run the pc36img other than going thru the motions on the screen.
maybe i can microwave it hahaha
edit: after a couple battery pulls during the radio update in the pc36img im using, it will no longer go thru the full radio update when running the zip so i definately screwed up the phone. it still gets to bootloader no problem tho so ive accomplished nothing.
ChacocII said:
Has this only happened with the magnus cm7 or is the happening with the official cyanogen rc1 and nightlies?
Happened to me with official cm7 rc1
Does the bootloader let you run a PC36IMG.zip?
yes, but it doesn't actually do anything. it will go thru the whole update process but still goes back to a white screen loop and no recovery. tried a battery pull during the radio update a couple hours ago (i thought the same thing) but it did nothing. i think its because its not actually doing anything when u run the pc36img other than going thru the motions on the screen.
maybe i can microwave it hahaha
edit: after a couple battery pulls during the radio update in the pc36img im using, it will no longer go thru the full radio update when running the zip so i definately screwed up the phone. it still gets to bootloader no problem tho so ive accomplished nothing.
Click to expand...
Click to collapse
Damn, so you can still see s off? I have no clue how to get it to s on then, or make it so you can't even get to the bootloader. Yea, if you microwaved it (haha) i'm sure it wouldnt ever turn on again. However, whoever looks at it would be able to tell that something went very, very wrong, and it wasn't the phone's fault. ha. Maybe it won't even matter that it's s off. I've heard of people having luck with sprint looking at a phone that is s off, but I've also heard the oppositte (more often).
i actually told the sprint tech on the phone that i had rooted it and he still warranty replaced mine. im just hoping they dont change their minds when they get it back and see s-off and try to charge me 500 bucks for my new one.
Wow. Yeah, if it won't even run a PC36.img from bootloader, you're kinda SOL. That's pretty much a last resort. Granted, you should try a few different img's (different d/l sources) before assuming it's screwed. Sometimes, you can get a bad download. I had a stock Evo that wouldn't go into recovery, so I flashed a RUU from bootloader, and everything was fine. Best of luck with your replacement though, brother.
well i have 14 more days before i have to send it back. there must be some way to get it to not turn on at all without physical damage, just gotta figure it out.
So I just rooted using the latest unrevoked, but now my phone locks up after about 30 seconds or so, then vibrates 5 times. More troubling: It cannot see an SD card, will not mount or format.
Hoping someone can help me get back to stock.
I did not take the gingerbread OTA, FWIW.
OK, well ,the obvious first question is gonna be are you s-on or s-off.
Turn your phone on while holding the power button down to see what it says at the top when Hboot starts up.
HipKat said:
OK, well ,the obvious first question is gonna be are you s-on or s-off.
Turn your phone on while holding the power button down to see what it says at the top when Hboot starts up.
Click to expand...
Click to collapse
It says S-ON
dsf3g said:
It says S-ON
Click to expand...
Click to collapse
Boot into the bootloader, then select clear storage, then try to boot up normally.
OK, so I managed to flash PC36IMG.zip. So now I'm back to stock and the EVO runs fine without rebooting. Wheeew! I was already scanning eBay for a replacement, LOL! Only issue I have now is that my Evo does not recognize the SD Card (won't let me mount, format, nothing.) I'm seeing some threads on this sort of thing, but if anyone has a quick fix I'd love o hear it. I've got a 16 GB card full of music that's just sittin' there.
Oh, now this is bad: the battery does not seem to charge after restoring... at least the charging symbol is not coming on!
UPDATE: OK, the red light is coming on now when I plug in, but battery status shows "discharging." I don't know at this point whether it's charging or not.
OK, just verified. Phone isn't charging. Down to 50%. Shutting off so I'll have enough juice to fix ti when I figure our what needs to be done. I don't have a separate battery charger, so I'm SOL if I can't get this thing working again.
Any help would be much appreciated!
http://forum.xda-developers.com/showthread.php?t=695243
sd card fix. Also, turn the phone off as you have, but leave it plugged in charged over night and see what happens for now.
Make sure you have the hboot drivers downloaded, then install, then uninstall htc sync, enable usb debugging from applications > development, then run unrevoked again.
teh roxxorz said:
http://forum.xda-developers.com/showthread.php?t=695243
sd card fix. Also, turn the phone off as you have, but leave it plugged in charged over night and see what happens for now.
Make sure you have the hboot drivers downloaded, then install, then uninstall htc sync, enable usb debugging from applications > development, then run unrevoked again.
Click to expand...
Click to collapse
Thanks, I'll give it a try this weekend. Right now I've got a spare battery charger on order with Amazon. Should be in this Friday. Don't want to mess with anything until I can start with a fully charged battery.
You're S-On. There's nothing you can, or could have messed with, unless you don't have the new update on your phone, which was going to be my next question
HipKat said:
You're S-On. There's nothing you can, or could have messed with, unless you don't have the new update on your phone, which was going to be my next question
Click to expand...
Click to collapse
I don't have the new update on my phone. It's still showing Android 2.2 and I never approved the OTA.
One suggestion that seems to work for some people is to flash a new radio. I wonder if someone could help me with this:
1) What do I need to know choose the appropriate radio to flash?
2) Do I need to be rooted to do so, because it seems I'm not.
I'm browsing eBay for cheapie Oprimus S phones... please help me not have to buy a used $100 Optimus S because I murdered by Evo :-(
Yes, you need to be rooted to flash the radios fro ma zip file.
you don't to flash form PC36IMG.zip file, and there is the choice to do it either way.
I'm curious, you said in your OP that you rooted, and the phone went into maintenance mode (The vibrates 5 times thing is maintenance Mode).
Are you sure the root took? I would do this, reinstall HTC-Sync, then install just the program, not the drivers, and try Unrevoked again, make sure it goes through the root process and the flash of clockwork recovery.
If it boots up, then you're good.
From there, I would flash Amon Ra, as it's a better recovery, and then try a ROM.
Radios is the least important thing you can flash, and I'd save that for last, and make sure you know in detail what you're doing, when it comes to radio flashing.
HipKat said:
Yes, you need to be rooted to flash the radios fro ma zip file.
you don't to flash form PC36IMG.zip file, and there is the choice to do it either way.
I'm curious, you said in your OP that you rooted, and the phone went into maintenance mode (The vibrates 5 times thing is maintenance Mode).
Are you sure the root took? I would do this, reinstall HTC-Sync, then install just the program, not the drivers, and try Unrevoked again, make sure it goes through the root process and the flash of clockwork recovery.
If it boots up, then you're good.
From there, I would flash Amon Ra, as it's a better recovery, and then try a ROM.
Radios is the least important thing you can flash, and I'd save that for last, and make sure you know in detail what you're doing, when it comes to radio flashing.
Click to expand...
Click to collapse
I can't be sure I rooted. I'm just going by what Unrevoked reported. Superuser was installed, but the phone would die before I had much time to verify that I was actually rooted.
I've never installed HTC Sync, BTW. According to the unrevoked instructions you shouldn't have it installed on your PC because it causes problems.
OK, so I got home and the phone says battery is 100% charged. So that's good. It appears to charge when turned off, at least.
Sadly, it does not recognize USB at all. The computer beeps when I plug the phone in, but the phone shows no popups or anything.
I tried running "unrevoked" again, but unrevoked just kept waiting for me to plug in the phone. I did not install HTC Sync.
The phone does not recognize micro sd cards from within Android, but I can flash signed ROMs. I did that today, flashing what I think is a newer ROM than I had before, but alas it did me no good. The phone still does not see the micro SD card or realize that I'm plugged in and charging.
The ROM I sintalled this time was the third link on this page:
http://forum.xda-developers.com/showthread.php?t=884060
It corresponds to the software version I was running before running UNREVOKED the first time.
I'm getting pretty worried here. I don't see how I'm supposed to fix this phone if I cannot communicate via USB.
Installing HTC Sync will install the drivers on your computer, which you need for unrevoked to work, but then, you need to uninstall the program (not the drivers).
Ugh, now I've discovered another problem. With this latest stock ROM I've lost bluetooth!
I'm losing hope here. My last best hope seems to be to accept the Gingerbread OTA, and if that doesn't solve the problem throw myself on the mercy of our local Sprint repair store. Anyone know what their policy is on this?
Will they repair something like this for a fee if it's not under warranty? I imagine even completely brcked Evos can be repaired with a new motherboard, right?
Should I try telling them that the OTA screwed it up? Will they be able to tell what I've done to the phone?
At this point I just want to get back to stock. No longer interested in rooting. I need a cell phone just for daily living.
i bought this Defy+ just a couple of days ago and i was trying to get CM7. I struggled to root it but i achieved it. I wiped and did all the procedure before installing it, but i didn't had enough space on my SD, so i rebooted and booted like a brand new defy, going through the Blur config and everything... So i went to Recovery again, but at this time i forgot to do the wiping - which, i guess, led to a brick.
So i managed to get a .sbf to flash it.. What i didn't realized is that the .sbf was a custom, so i guess this ****ed up my phone even more. And so i went on trying to rescue my phone but this time i couldn't complete the flashing process, i wasn't able to perform a downgrade - i guess. After this, i got a non-rootable .sbf and began the flashing. The process got stuck on some message at 0%, then i disconnected the phone.
When i was able to download a stock firmware, from the .sbf thread, the phone wouldn't reboot when RSD asked, it didn't turn on again. So i tried to re-flash it, same .sbf and now i'm stuck with this situation: the pc is not recognizing my phone, i have a black screen - not even the Bootloader error screen is appearing and i'm here, begging, for someone to help me. is it dead? can i get it back?
HELP, PLZ
Is there any juice in the battery left? Does the phone even turn on or did you just drain all of your battery? If so, you have a couple of options - do McGyver or find somebody with the same phone and ask him to charge your battery and then start over. I would strongly recommend you take the second option.
Auris 1.6 vvt-i said:
Is there any juice in the battery left? Does the phone even turn on or did you just drain all of your battery? If so, you have a couple of options - do McGyver or find somebody with the same phone and ask him to charge your battery and then start over. I would strongly recommend you take the second option.
Click to expand...
Click to collapse
it doesn't turn on, but i guess it does have battery, i can see the led on when i connect it to the pc
Led is always on when connected to the PC - it means nothing. If it doesn't turn on, then your battery's dead. Find someone who has the same phone and can charge it for you.
I think there is no problem, but you flash older firmware, which is probably due to the 7 bootloader does not go up.
try to be flash with one of these (2.3.6 GB)
http://forum.xda-developers.com/showthread.php?t=966537
begins with the 139-ended, if it is not going to work with the 188-ended
Sorry for bad English
"As of today there is no a full SBF** for the Defy+ (found here).
This full SBF is a new CG Version**, with Android 2.3.6. You wont be able to go back to your Stock Defy+ Rom, but at least you wont kill it if something goes wrong."
i successfully flashed it but still it won't turn on, i'm almost giving up on this one
caiowatanabe said:
i successfully flashed it but still it won't turn on, i'm almost giving up on this one
Click to expand...
Click to collapse
If it gets past the red m and just keeps playing the android animation then simply pull battery hold volume - put battery in and keep volume - held when you get the android and the triangle press volume + and - and wipe all, should boot, unfortunately you've just flashed the un root able sbf and are stuck on moto standard
teamwork makes the dream work
nevermind, i flashed other sbf version and it is now working; too bad this version isn't rootable
anyway, many many thanks for all the help
caiowatanabe said:
nevermind, i flashed other sbf version and it is now working; too bad this version isn't rootable
anyway, many many thanks for all the help
Click to expand...
Click to collapse
Feel free to keep an eye on the dev section for the bl7 rooting thread you may get lucky
teamwork makes the dream work
Hi all,
I was having some random reboots on my HTC desire Z lately and decided it was time to try a custom rom. I followed the right steps to first downgrade to froyo, which was successful and next rooted the phone, which seem to have worked as well.
The next step was to get into recovery mode to install the rom, but I did not get to that. I took out the battery while it was still on to power it off, but then it did not power on anymore. Also connecting the charger has no effect at all, so it sure seems to be bricked.
Does anyone have a suggestion on what I can try, or what happened to it?
The way I downgraded and rooted was by using Strawmetals guide which can be found here:
http://minus.com/mu9vZ3P38
and was suggested in this thread:
http://forum.xda-developers.com/showthread.php?t=1178912
I carefully completed all the steps, checked the MD5's etc. and made sure the notifications/verifications I got back in the process were correct..
Also, I wonder if I would run into problems if I send it back in for warranty. If I can't get it to boot, will they? And next they will probably blame me for rooting, right?
Regards & TIA
Yes they gonna blame you for rooting. I was had a same problem, no boot to recovery. I solved the problem with install 4Ext updater and fromit install 4ext tuch,and now I can flash roms. Try to find a charged battery or put yours into another phone and charge it. If I understand right your battery died?!
Sent from my HTC Vision using xda app-developers app
Sounds like it might be bricked mate, same thing happened to me... 3 times. They probably won't be able to get the phone to boot, where did you buy the phone from? My second one was from Vodafone with a warranty, when it bricked I took it in, they plugged the phone in and left it for a few minutes and tried to power it on, tried a different battery (All things I already tried) to see if the device was showing any signs of life, it wasn't and I walked out with a new phone. I doubt they'd be able to bring it back to life to see that it's been rooted. You COULD connect your phone to a car battery and fry it, tell them you went to sleep and woke up and the phone was very very hot and it burnt your hand and melted the charger cable, not sure if I could recommend this, never done it myself... but if you have no other option.
These were also the options I considered. Got to give it a try with a different battery, if I can find one. If that doesn't make a difference, I'll just hand it in and see what they have to say, as there's nothing else I can do without being able to power on the phone..
All of a sudden the phone started working again . And afterwards I was able to complete the update to Mimicry 1.5.
Strange problem, as the phone seemed to be dead for hours.. Hope it doesn't happen again!