Ok I need some help, I unrooted my phone because I had to take into sprint to get a new screen. The problem is this. After unrooting the Evo it constantly reboots itself and on top of that it will not recognize the SD card. Any ideas on how to fix this.
First, being that the phone is no longer rooted, take it to Sprint and have them troubleshoot it. If you don't want to do that, you can try booting into recovery to see if the card will mount there.
dougjamal said:
First, being that the phone is no longer rooted, take it to Sprint and have them troubleshoot it. If you don't want to do that, you can try booting into recovery to see if the card will mount there.
Click to expand...
Click to collapse
If the phone is *properly* unrooted (s-on zip, RUU) there shouldn't be a recovery to boot into.
OP, did you unroot the way I mentioned?
(from... Evo/MIUI/Tapatalk)
plainjane said:
If the phone is *properly* unrooted (s-on zip, RUU) there shouldn't be a recovery to boot into.
OP, did you unroot the way I mentioned?
(from... Evo/MIUI/Tapatalk)
Click to expand...
Click to collapse
I was under the impression that there is a stock recovery.
dougjamal said:
I was under the impression that there is a stock recovery.
Click to expand...
Click to collapse
From what I understand, the stock recovery is no recovery. On a brand new not rooted phone, if you try to go into recovery, you get the black screen with red triangle.
At least that's what I've always heard. The Evo I had before this one was freaking out - it had never been rooted. I went into the bootloader to clear storage and out of curiosity chose recovery afterwards. I got the no recovery screen.
Running the RUU should give you the same result.
(from... Evo/MIUI/Tapatalk)
plainjane said:
From what I understand, the stock recovery is no recovery. On a brand new not rooted phone, if you try to go into recovery, you get the black screen with red triangle.
At least that's what I've always heard. The Evo I had before this one was freaking out - it had never been rooted. I went into the bootloader to clear storage and out of curiosity chose recovery afterwards. I got the no recovery screen.
Running the RUU should give you the same result.
(from... Evo/MIUI/Tapatalk)
Click to expand...
Click to collapse
Oh Okay. Thanks for clearing that up for me. Take care, my friend...
Thanks for the info, I did unroot it the way you mentioned in the thread. And it is unrooted the s zip is on and when I try to get into recovery I do get the red triangle warning. So I guess my best bet is to take it to Sprint. Is there a way to root the phone thru bootloader or do I have to have the phone turned on to root it. As far as the SD card issue any ideas.
killwrath said:
Thanks for the info, I did unroot it the way you mentioned in the thread. And it is unrooted the s zip is on and when I try to get into recovery I do get the red triangle warning. So I guess my best bet is to take it to Sprint. Is there a way to root the phone thru bootloader or do I have to have the phone turned on to root it. As far as the SD card issue any ideas.
Click to expand...
Click to collapse
so you didnt run an RUU? Did you just flash a PC36IMG.zip from the bootloader? The problem with that method is that you dont know what all was in the zip, or if it included everything. Theres a lot of PC36IMG.zip's out there that all serve different purposes. Go download the official RUU on your computer, plug your phone in and boot into fastboot (or just bootloader, not sure), wait for the process to finish, and your phone will be back to stock 100% no matter what. This is what sprint will do to restore a phone, so its official.
Ok one more quick question, how do I get my computer to recognize my phone after I plug it in. I found the official RUU and when I plugged my phone in and booted to bootloader the computer did not find it. As a result running the RUU did nothing. I went thru all the warning screens and then when it was searching for the phone and then gave me a warning that no phone was connected. So if I could get the phone connected to the computer then I am sure I can run the RUU and see if that helps. Any ideas?
killwrath said:
Ok one more quick question, how do I get my computer to recognize my phone after I plug it in. I found the official RUU and when I plugged my phone in and booted to bootloader the computer did not find it. As a result running the RUU did nothing. I went thru all the warning screens and then when it was searching for the phone and then gave me a warning that no phone was connected. So if I could get the phone connected to the computer then I am sure I can run the RUU and see if that helps. Any ideas?
Click to expand...
Click to collapse
check my guide have a link to the ruu you need just place it PC36IMG.ZIP on SD card and run get into boot loader mode and there you go.
Ok the phone wins. It is going back to sprint to see what they can do. All of your suggestions have been great, thanks for them. I just cant get the computer to recognize the phone when its plugged in. And the phone cant detect the SD card even in bootloader. And it will only charge when its is turned off. DAMN YOU TECHNOLOGY!!! hahahaha
Again thanks a ton for all your help. Warms the heart to know there are lots of fellow phone hackers willing to help out.
First thing is Thank You Everyone for all your help and suggestions.
Here is the update. The phone won and I had to take it to Sprint. And much to my suprise and honestly relief, they could not get the software reinstalled, it was stuck in a boot cycle is what they said. Ok if you say so. So they are going to send me a new phone. WOO HOO!!!!!
Thanks again for everything. Guess I get to try out Auto Root this time.
Yeah Rooting.
Related
Let me preface this by saying yes I know there are dozens if not more threads on boot loop problems. I have recovered from boot loops before. This is very different.
I rooted my incredible with unrevokedForever and had cyanogen 6 on it. Everything was fine until yesterday I woke up to it in a boot loop, but not the cyanogen boot animation, the white HTC Incredible screen. I can only get to HBOOT, once I try to enter recovery, use an update.zip, or anything after the HBOOT page it goes into its loop. Should I pursue the RUU and find a windows computer or will that not help me?
I think I may have to bite the bullet and buy a new phone. As obviously they will not replace an S-OFF phone. Any help is appreciated.
jenic said:
Let me preface this by saying yes I know there are dozens if not more threads on boot loop problems. I have recovered from boot loops before. This is very different.
I rooted my incredible with unrevokedForever and had cyanogen 6 on it. Everything was fine until yesterday I woke up to it in a boot loop, but not the cyanogen boot animation, the white HTC Incredible screen. I can only get to HBOOT, once I try to enter recovery, use an update.zip, or anything after the HBOOT page it goes into its loop. Should I pursue the RUU and find a windows computer or will that not help me?
I think I may have to bite the bullet and buy a new phone. As obviously they will not replace an S-OFF phone. Any help is appreciated.
Click to expand...
Click to collapse
As long as you can still get into HBOOT and Recovery, you should be okay. Your best bet is to get the RUU and go back to stock/s-on, then re-root/s-off (if you want). I had to do this once, and it's pretty straight forward. Just do a search for Bezerker7's Ultimate Get Back to Stock Thread. It has all the info you'll need on how to do it.
RMarkwald said:
As long as you can still get into HBOOT and Recovery, you should be okay. Your best bet is to get the RUU and go back to stock/s-on, then re-root/s-off (if you want). I had to do this once, and it's pretty straight forward. Just do a search for Bezerker7's Ultimate Get Back to Stock Thread. It has all the info you'll need on how to do it.
Click to expand...
Click to collapse
The problem is I can only get into HBOOT, not recovery. It would be a fairly simple matter if I had access to recovery features. Would RUU work without access to recovery?
jenic said:
The problem is I can only get into HBOOT, not recovery. It would be a fairly simple matter if I had access to recovery features. Would RUU work without access to recovery?
Click to expand...
Click to collapse
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.
RMarkwald said:
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.
Click to expand...
Click to collapse
Your concise post is most appreciated. I will do as you instruct and post results back here when finished.
RMarkwald said:
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.
Click to expand...
Click to collapse
Hit an unfortunate snag right away. fastboot (nor adb) is detecting the device. Screen is showing XC SHIP S-OFF as it should, it is in FASTBOOT USB mode and my computer detects the USB itself just fine.
dmesg output:
[346853.772041] usb 2-6: new high speed USB device using ehci_hcd and address 17
[346853.922917] usb 2-6: configuration #1 chosen from 1 choice
Click to expand...
Click to collapse
Thank you though that was a great suggestion! (Was very hopeful for a second there
I've never used the fastboot command before, but I seem to recall that sometimes my PC's don't report connection from ADB, but I haven't checked recently... Hmmm...
Just checked and it does report a device using ADB. Did you try typing the fastboot command to flash the recovery image file: fastboot flash recovery /path/to/<recovery.img file> anyways to see what happens? I am assuming if it isn't detecting the connection, it may fail...
EDIT: Did you pull the battery out, put it back in and try to get into recovery again? If you, try doing a user/factory reset + dalvik cache before trying to install a ROM from your SD card.
This may or may not help, but I had a similar issue of not having the phone recognized by fastboot while playing with a friends EVO Shift. I was able to use the program described in this thread to uninstall all HTC drivers. Then, when the phone was recognized and new drivers installed automatically, fastboot worked as expected.
http://forum.xda-developers.com/showthread.php?t=532719
RMarkwald said:
I've never used the fastboot command before, but I seem to recall that sometimes my PC's don't report connection from ADB, but I haven't checked recently... Hmmm...
Just checked and it does report a device using ADB. Did you try typing the fastboot command to flash the recovery image file: fastboot flash recovery /path/to/<recovery.img file> anyways to see what happens? I am assuming if it isn't detecting the connection, it may fail...
Click to expand...
Click to collapse
My ADB daemon would always recognize it in the past, when the phone was working. Yes I tried the command anyway, even though fastboot devices did not return anything. It hung there waiting for the device to be connected.
RMarkwald said:
EDIT: Did you pull the battery out, put it back in and try to get into recovery again? If you, try doing a user/factory reset + dalvik cache before trying to install a ROM from your SD card.
Click to expand...
Click to collapse
Yes, I pulled battery out multiple times, and when installing the rom I factory reset, cleared dalvik and normal cache through Clockwork. Cyanogen was working fine for weeks, this is a freak concurrence that happened without warning. I woke up to find it this way, or rather, it woke me up with its constant rebooting. lol.
cf9182 said:
This may or may not help, but I had a similar issue of not having the phone recognized by fastboot while playing with a friends EVO Shift. I was able to use the program described in this thread to uninstall all HTC drivers. Then, when the phone was recognized and new drivers installed automatically, fastboot worked as expected.
http://forum.xda-developers.com/showthread.php?t=532719
Click to expand...
Click to collapse
I appreciate the help however I am using Linux, and that seems to be a windows issue. I have not had issue detecting the device until this problem arouse. The sentiment is of course appreciated though, please do not feel that I am ungrateful! You have both been very supportive. I think I have just about resigned to dump money on a new phone. This time I will leave it stock for awhile and see if this occurs a third time.
jenic said:
My ADB daemon would always recognize it in the past, when the phone was working. Yes I tried the command anyway, even though fastboot devices did not return anything. It hung there waiting for the device to be connected.
Yes, I pulled battery out multiple times, and when installing the rom I factory reset, cleared dalvik and normal cache through Clockwork. Cyanogen was working fine for weeks, this is a freak concurrence that happened without warning. I woke up to find it this way, or rather, it woke me up with its constant rebooting. lol.
I appreciate the help however I am using Linux, and that seems to be a windows issue. I have not had issue detecting the device until this problem arouse. The sentiment is of course appreciated though, please do not feel that I am ungrateful! You have both been very supportive. I think I have just about resigned to dump money on a new phone. This time I will leave it stock for awhile and see if this occurs a third time.
Click to expand...
Click to collapse
This happened to me and many other people. It has nothing to do with the fact that you rooted as my replacement from verizon did the same thing even before I rooted. Finally on my 2nd replacement (my 3rd DINC), it has stopped happening.
You're going to have to take it to the store. The guy who looked at my phone looked right at the HBOOT (where it says s-OFF) and then said "we're going to have to send you another one."
So you may get lucky. Your other option (if you're nervous about the store seeing the s-OFF) is just to call Verizon and ask them to send you a replacement. My experience has been that the folks in the Verizon store have no idea what the f they're doing, and you'll probably be just fine taking it in.
jaba14 said:
This happened to me and many other people. It has nothing to do with the fact that you rooted as my replacement from verizon did the same thing even before I rooted. Finally on my 2nd replacement (my 3rd DINC), it has stopped happening.
You're going to have to take it to the store. The guy who looked at my phone looked right at the HBOOT (where it says s-OFF) and then said "we're going to have to send you another one."
So you may get lucky. Your other option (if you're nervous about the store seeing the s-OFF) is just to call Verizon and ask them to send you a replacement. My experience has been that the folks in the Verizon store have no idea what the f they're doing, and you'll probably be just fine taking it in.
Click to expand...
Click to collapse
That was definitely a laugh. Thank you I will see if I can get it replaced! I've been kinda just ignoring the fact that I do not have a phone all this time... Thankfully I had setup the phone to forward calls to google voice. It has been a lifesaver.
Today I was flashing a new Rom (the GingerSense Leak to be specific) and when I was in Rom Manager I decided to update my recover from 2.5.0.7 to 3.0.0.5 (not sure if either of these numbers are right). When I finally rebooted into what I thought was recovery my phone sent me to the bootloader menu. Which normally isn't a big deal and it means that the recovery version didn't take. This time when I selected reboot it rebooted back into the bootloader menu. Now I can't get anywhere, no recovery and no way to reboot the phone.
Am I F$%#ed?
I did do a search and no one has quite had the same problem I am having.
Thank you for the help in advance.
Stalte said:
Today I was flashing a new Rom (the GingerSense Leak to be specific) and when I was in Rom Manager I decided to update my recover from 2.5.0.7 to 3.0.0.5 (not sure if either of these numbers are right). When I finally rebooted into what I thought was recovery my phone sent me to the bootloader menu. Which normally isn't a big deal and it means that the recovery version didn't take. This time when I selected reboot it rebooted back into the bootloader menu. Now I can't get anywhere, no recovery and no way to reboot the phone.
Am I F$%#ed?
I did do a search and no one has quite had the same problem I am having.
Thank you for the help in advance.
Click to expand...
Click to collapse
Try running an RUU.
Not sure how advanced of a user you are, but you can try and check if your phone is recognized via USB while in the bootloader and try pushing the recovery on via ADB. That way, you can just restore a good NAND instead of having to start over.
Stalte said:
Today I was flashing a new Rom (the GingerSense Leak to be specific) and when I was in Rom Manager I decided to update my recover from 2.5.0.7 to 3.0.0.5 (not sure if either of these numbers are right). When I finally rebooted into what I thought was recovery my phone sent me to the bootloader menu. Which normally isn't a big deal and it means that the recovery version didn't take. This time when I selected reboot it rebooted back into the bootloader menu. Now I can't get anywhere, no recovery and no way to reboot the phone.
Am I F$%#ed?
I did do a search and no one has quite had the same problem I am having.
Thank you for the help in advance.
Click to expand...
Click to collapse
Does your bootloader show Ship S On or Ship S off? If it's S off still, you can probably just flash a PC36IMG of a recovery, using the bootloader. That looks like what teh roxxor attatched, based on the file size of the PC36IMG he attatched. If you're not S off anymore, I'd suggest running an RUU to flash you back to stock, and then start over from that point.
k2buckley said:
Does your bootloader show Ship S On or Ship S off? If it's S off still, you can probably just flash a PC36IMG of a recovery, using the bootloader.
Click to expand...
Click to collapse
That would be much easier than what I suggested. lol I don't know why I didn't think of that.
k2buckley said:
Does your bootloader show Ship S On or Ship S off? If it's S off still, you can probably just flash a PC36IMG of a recovery, using the bootloader. That looks like what teh roxxor attatched, based on the file size of the PC36IMG he attatched. If you're not S off anymore, I'd suggest running an RUU to flash you back to stock, and then start over from that point.
Click to expand...
Click to collapse
Yep its still of I'm pushing the PC36IMG to my phone now thank you very much
Stalte said:
Yep its still of I'm using the PC36IMG to my phone now thank you very much
Click to expand...
Click to collapse
Sweet, glad you got it back up and rollin'
after like 4 hours of trying I can not get it my adb to recognize my phone. What now.....
PS: I can get it to recognize my phone in fastboot
Stalte said:
after like 4 hours of trying I can not get it my adb to recognize my phone. What now.....
PS: I can get it to recognize my phone in fastboot
Click to expand...
Click to collapse
So where are you at exactly? Did you get the recovery flashed earlier, and your phone is back up and running? And now you're just trying to get ADB to work, and you're having trouble..? OR, are you still stuck, and never got the phone back online earlier?
Do you get an error when you try to use adb, or is it just not seeing the device?
k2buckley said:
So where are you at exactly? Did you get the recovery flashed earlier, and your phone is back up and running? And now you're just trying to get ADB to work, and you're having trouble..? OR, are you still stuck, and never got the phone back online earlier?
Do you get an error when you try to use adb, or is it just not seeing the device?
Click to expand...
Click to collapse
Im still in bootloader I have done everything I can think of. Its not seeing the device.
c:\android-sdk\tools>adb devices
List of devices attached
^^^^NO DEVICES LISTED^^^^^.......SIGH.....
c:\android-sdk\tools>fastboot devices
HT12THL02230 fastboot
My 12 year old little brother solved it for me, He told me to take out my micro sd card put it in my computer and than drag and drop the PC36IMG on the sd card than booted. SUCCESS!!!!!!!!!!!!!
Thanks Everyone!!
Stalte said:
My 12 year old little brother solved it for me, He told me to take out my micro sd card put it in my computer and than drag and drop the PC36IMG on the sd card than booted. SUCCESS!!!!!!!!!!!!!
Thanks Everyone!!
Click to expand...
Click to collapse
Haha, I was confused on what you were trying to use adb for. Were you just trying to push the .zip to your sd card? The reason it wasn't working is because you were in the bootloader. ADB only recognizes if the phone is in recovery, or booted into the OS. That's why it wouldn't see adb for ya. And yes, now that you have the PC36IMG on your sd card, you should just be able to apply that using the bootloader, and then you should be able to get up and running again.
Hey guys,
I tried to root my my evo 4g with the instructions from the sticky and when I started the autoroot file as it said, it would get to found root then establishing something and the cmd would close out and my phone would stay in the bootloader mode. Instructions said to go to recovery if it didn't continue and I did go into recovery and all it gave me was a black screen with the red triangle and nothing was happening so I pulled out the battery to restart the phone. Now my phone boots up normally and it just freezes up after maybe 30 seconds of use everytime and just reboots and it repeats over and over again nonstop. It won't be recognized by my computers and it just says unidentified with the CDMA drivers not working and the phone does not recognize the SD card when its running and booted up. Please help if you guys know what I could do to make it stop restarting. Thanks in advance!
Try re-rooting via unrevoked. Click on unrevoked in my signature and follow the directions, but first, boot into the bootloader screen (after shutting off the device, simultaneously press the DOWN volume button and the power button until the device starts). Look at the top of the screen and see if it displays "S-OFF". If it does, great, you're rooted, bit if it displays "S-ON" then follow the rooting method of unrevoked or retry the method you used. If it does indeed display "S-OFF", I suggest you flash a custom recovery like amon_RA.
posting & replying via the XDA Premium app.
Well I can't do that since it won't recognize the phone through USB or recognize the SD card
Update: I just flashed my evo with the stock 3.70.651.1 rom using a card reader putting the PC36IM something file on the SD card and used bootloader to flash and It's still not recognizing the SD card and it's still freezing up 1 minute after it has booted up and restarts and repeats the loop.
I sorta have a similar problem. I have a rooted evo running CM7 .
trying to use HDMI cable with a 1080p vizio LCD TV. Nothing happens. Does CM7 support the HDMI video out.
Sent from my PC36100 using XDA Premium App
SprintTouchPro2 said:
Hey guys,
I tried to root my my evo 4g with the instructions from the sticky and when I started the autoroot file as it said, it would get to found root then establishing something and the cmd would close out and my phone would stay in the bootloader mode. Instructions said to go to recovery if it didn't continue and I did go into recovery and all it gave me was a black screen with the red triangle and nothing was happening so I pulled out the battery to restart the phone. Now my phone boots up normally and it just freezes up after maybe 30 seconds of use everytime and just reboots and it repeats over and over again nonstop. It won't be recognized by my computers and it just says unidentified with the CDMA drivers not working and the phone does not recognize the SD card when its running and booted up. Please help if you guys know what I could do to make it stop restarting. Thanks in advance!
Click to expand...
Click to collapse
can you send me the autorootlog.txt file? that should show what happened to it. And def don't try rooting it with anything else while the phone is in an inconsistent state, that is just asking to corrupt it.
Use unrevoked 3 my guide has all you need links and so on
I like unrevoked 3 easy to root and unroot . All the other programs that work for rooting can make unrooting a pain in the butt. Do what you want you want .
You don't have a recovery installed that's why you get black screen and triangles . Use amon 2.3
reaper24 said:
Use unrevoked 3 my guide has all you need links and so on
I like unrevoked 3 easy to root and unroot . All the other programs that work for rooting can make unrooting a pain in the butt. Do what you want you want .
Click to expand...
Click to collapse
how is unrooting different?
xHausx said:
how is unrooting different?
Click to expand...
Click to collapse
I'm not going to war with you on that man just saying turn s off flash a stock Ruu the latest and your good to go. Trying to find a auto or one click unrooting program to unroot can be a pain to do if your h boot is to new or old .
I'm sure your way is good I just prefer unrevoked 3 is all. Not dogging your root way. Just familiar with unrevoked 3 use it to root everyone's phone I know.
reaper24 said:
I'm not going to war with you on that man just saying turn s off flash a stock Ruu the latest and your good to go. Trying to find a auto or one click unrooting program to unroot can be a pain to do if your h boot is to new or old .
I'm sure your way is good I just prefer unrevoked 3 is all. Not dogging your root way. Just familiar with unrevoked 3 use it to root everyone's phone I know.
Click to expand...
Click to collapse
Well you're saying there's a difference in how you have to unroot when it's not true. Or at least that I know of, if there is I'm curious as to how.
Autoroot will try to downgrade the hboot to the unlocked engineering leak, if successful it's finished and all you have to do to unroot is run the RUU. If it's unable to downgrade the hboot it will bring up the stock recovery and use unrevoked forever to unlock the nand; when this is used you have to flash the s-on tool (that is left on the sdcard as URFSOn.zip) and then flash the RUU to unroot.
Unrevoked 3 breaks in through the hboot and unlocks the nand through the radio, so you will also have to use the s-on tool and flash the RUU.
You're also telling him to keep trying to root when his phone is obviously in a weird state, that's bad advice unless you want him to end up bricked like a ton of people did when the latest firmware came out.
xHausx said:
Well you're saying there's a difference in how you have to unroot when it's not true. Or at least that I know of, if there is I'm curious as to how.
Autoroot will try to downgrade the hboot to the unlocked engineering leak, if successful it's finished and all you have to do to unroot is run the RUU. If it's unable to downgrade the hboot it will bring up the stock recovery and use unrevoked forever to unlock the nand; when this is used you have to flash the s-on tool (that is left on the sdcard as URFSOn.zip) and then flash the RUU to unroot.
Unrevoked 3 breaks in through the hboot and unlocks the nand through the radio, so you will also have to use the s-on tool and flash the RUU.
You're also telling him to keep trying to root when his phone is obviously in a weird state, that's bad advice unless you want him to end up bricked like a ton of people did when the latest firmware came out.
Click to expand...
Click to collapse
no I'm not telling him to brick his phone. He doesn't have a recovery on his phone that is what he needs . Just saying if he does end up rerooting at some point he can try unrevoked 3 just a suggestion. My advice isn't bad not new to rooting or flashing. Pretty good at trouble shooting .
Well how do I get a recovery? I thought I have one since I have the option to go there? Gives me a red triangle with a phone under it. Once i mash the volume up and down and power button at the same time and hold it in for a bit a menu pops up to update from SD card or to clear storage and some other options. But anyway I reflashed the stock rom from bootloader and it's still doing the freeze after 30 seconds of use and restarts over and over again. So how do I actually get recovery and what do I do after that to make this stupid restarting of my phone to stop.
SprintTouchPro2 said:
Well how do I get a recovery? I thought I have one since I have the option to go there? Gives me a red triangle with a phone under it. Once i mash the volume up and down and power button at the same time and hold it in for a bit a menu pops up to update from SD card or to clear storage and some other options. But anyway I reflashed the stock rom from bootloader and it's still doing the freeze after 30 seconds of use and restarts over and over again. So how do I actually get recovery and what do I do after that to make this stupid restarting of my phone to stop.
Click to expand...
Click to collapse
I'll need to take a look at your autorootlog.txt file in order to find out what's up with your phone. It should be in the autoroot folder and you can post it by using the 'manage attachments' button, if it doesn't want to let you for some reason you can also email it to me.
edit: odds are you're phone is still locked but it won't hurt to try flashing the recovery, all you have to do to flash it is run the FlashZip script that came with AutoRoot and select the one that says Amon RA - hausmod. That's if it's unlocked of course, if it says s-on or that the security is still on then your phone will reject it.
There you go, there is my autorootlog
I'm not too worried about this as I took the phone to sprint and they ordered me a new phone since they didn't know what was wrong with it and I'll get it today or tomorrow but I just want to figure out what went wrong so that I know what to do if I am to root my new phone..cause this autoroot I used on this website messed up and I followed every step perfectly.
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.
Thanks to Calkulin, Dougpiston, and bwthor20 for this fix. It was too late for me, but hopefully not for you. My situation was, after flashing a rom, I was suddenly S-On without recovery. DO NOT FLASH THE RUU!!!!! Just follow this guide and you'll be good:
Thanks bwthor20 for telling me about this guide:
http://forum.xda-developers.com/showthread.php?t=695243
Now, go to the incredible version of this guide, thanks to Dougpiston:
http://pvillecomp.com/?page_id=33
These guides should get you fixed!
Cheers,
dmeadows013
That sucks man very interested in how that happened though, never seen a phone reset it self to s-on before. I think you would have to ruu to get s-off again, that is if you can ruu back to froyo. What rom are you on? Hope you figure something out.
cmlusco said:
That sucks man very interested in how that happened though, never seen a phone reset it self to s-on before. I think you would have to ruu to get s-off again, that is if you can ruu back to froyo. What rom are you on? Hope you figure something out.
Click to expand...
Click to collapse
Was attempting to run my very experimental port of the Vigor RUU. Strange because it showed the splash on my last test, but after moving /system/customize to /data/syscustomize, it did this. I'll try the Froyo RUU. I should've thought of that one. Thanks!
Why not flash an old RUU?
Could someone post the Froyo or Eclair PB31IMG? I can't seem to find it...
Official froyo 2.2 PB31IMG.zip
http://dinc.does-it.net/stock_froyo/PB31IMG.zip
cmlusco said:
Official froyo 2.2 PB31IMG.zip
http://dinc.does-it.net/stock_froyo/PB31IMG.zip
Click to expand...
Click to collapse
Thanks! Your the man!
There is another thread on here where a guy had the same thing happen to him. Tried to flash a rom then the black screen and 5 vibes. He also lost s-off. I wonder whats going on.
cmlusco said:
There is another thread on here where a guy had the same thing happen to him. Tried to flash a rom then the black screen and 5 vibes. He also lost s-off. I wonder whats going on.
Click to expand...
Click to collapse
Hmmmm... That might be it. I'll try to port it again, and see if I get the same result. If I do, that's probably the problem lol
Alright, got the PB31IMG flashed. Problem is, after flashing, it just did the 5 vibe again... Back in HBOOT
dmeadows013 said:
Alright, got the PB31IMG flashed. Problem is, after flashing, it just did the 5 vibe again... Back in HBOOT
Click to expand...
Click to collapse
Very strange not sure, if you cant get an ruu to work my guess is some sort of hardware failure.
I would try an ruu exe from your pc.
cmlusco said:
Very strange not sure, if you cant get an ruu to work my guess is some sort of hardware failure.
I would try an ruu exe from your pc.
Click to expand...
Click to collapse
Yeah. I'm probably gonna just take it into the Verizon store. There is no way they'll find out I was rooted, as I am now S-ON. I'll see what they say.
Here is the fix!
This happened to me yesterday after installing MIUI. All was working, but when I tried to switch the camera to store on the SD card, it said it wasn't available. Tried to mount/unmount with no luck. Rebooted, and I had the same thing, five vibrations, then just a flashing green LED. A battery pull and either the charger or USB plugged in a PC, and it would boot to recovery. Still couldn't read the SD Card, so no restore. Lots of Googles later I found the fix...right here on XDA. Found a LOT of threads that pretty much said that there is no recovery.
Read On...
http://forum.xda-developers.com/showthread.php?t=695243
LEAVE THE USB CABLE PLUGGED IN TO YOUR PC FOR ALL OF THIS!
After the SD fix, I could use CWM to restore a known good backup, then copied the two files over to my SD Card and used a terminal app on the phone to run the commands listed in the link. A reboot, and I was back in business. S-OFF was back too. Odd...
dmeadows013 said:
Yeah. I'm probably gonna just take it into the Verizon store. There is no way they'll find out I was rooted, as I am now S-ON. I'll see what they say.
Click to expand...
Click to collapse
Worth a try, you might get lucky.
dmeadows013 said:
Yeah. I'm probably gonna just take it into the Verizon store. There is no way they'll find out I was rooted, as I am now S-ON. I'll see what they say.
Click to expand...
Click to collapse
I wouldn't. With a USB cable plugged in to the phone and PC, you can get into hboot with a battery pull and powering on while holding volume down. This doesn't seem to work every time, so unplug, remove the battery, then try again. After getting into hboot, you can go to recovery and see CWM if you have it installed.
bwthor20 said:
I wouldn't. With a USB cable plugged in to the phone and PC, you can get into hboot with a battery pull and powering on while holding volume down. This doesn't seem to work every time, so unplug, remove the battery, then try again. After getting into hboot, you can go to recovery and see CWM if you have it installed.
Click to expand...
Click to collapse
I can get into HBOOT without being plugged in, just using the normal way. Clicked recovery, booted to the splash and then the black screen and 5 vibes. Anyway, I have installed the RUU, so it would have the stock recovery anyway.
CWM Version
dmeadows013 said:
I can get into HBOOT without being plugged in, just using the normal way. Clicked recovery, booted to the splash and then the black screen and 5 vibes. Anyway, I have installed the RUU, so it would have the stock recovery anyway.
Click to expand...
Click to collapse
Try booting with it plugged in to the PC. I could boot that way, and use it, but as soon as I unplugged the USB, it would go to a black screen and 5 vibrations.
bwthor20 said:
Try booting with it plugged in to the PC. I could boot that way, and use it, but as soon as I unplugged the USB, it would go to a black screen and 5 vibrations.
Click to expand...
Click to collapse
Well that seemed to work... I plugged it in, and it booted up to the DROID Screen. Then, I unplugged, and black screen vibes. I think I had the same thing as you, but I just had the stock recovery instead because of the RUU. How did you end up fixing the plugged in problem? I'll check out the thread you posted. Thanks man, your a lifesaver.
dmeadows013 said:
Well that seemed to work... I plugged it in, and it booted up to the DROID Screen. Then, I unplugged, and black screen vibes. I think I had the same thing as you, but I just had the stock recovery instead because of the RUU. How did you end up fixing the plugged in problem? I'll check out the thread you posted. Thanks man, your a lifesaver.
Click to expand...
Click to collapse
It is the second part of the sequence in the link I posted in the previous thread. Check to see if you can mount your SD Card. If not, you will need to do the first part so you can load the two files on it used in the second part.
bwthor20 said:
It is the second part of the sequence in the link I posted in the previous thread. Check to see if you can mount your SD Card. If not, you will need to do the first part so you can load the two files on it used in the second part.
Click to expand...
Click to collapse
Alright, got the SD fixed. Not sure how I will get the USB fix, as I do not have root. Also, for some reason, unRevoked cannot find my phone. Neither will ADB