Related
Here's my 4 hour journey...
I tried rooting my Evo using AutoRoot v2.4 (http://forum.xda-developers.com/showthread.php?t=838448 I would post there but I don't have permissions, plus my problem seems more general at this point anyway). I followed all of the instructions (I'm running Android 2.2 with 3.70.651.1). At first, it was telling me that it was unable to root. After trying a couple things (such as killing all running processes), I used an RUU of 3.70.651.1 (http://www.multiupload.com/W679R1W391). I ran AutoRoot again, and this time it told me Root was successful and took me to the bootloader screen. As it did this, the AutoRoot DOS window just disappeared. I rebooted and tried a few more times, same result.
Here's where I'm not quite sure what I did. I think the next thing was I went into Recovery from bootloader, didn't really know what I was doing, and did a battery pull. Then I tried to factory reset by going bootloader -> clear storage. When I went to try and run AutoRoot again, my computer wasn't recognizing my Evo (I guess restoring the Evo caused it to lose the drivers?). When I plugged it in, it briefly searched for several "Qualcomm CDMA Technologies MSM" drivers (weird, never saw it look for those before when I plugged in my Evo?), asked me if I had a disk that came with the hardware, and when I said no it told me it couldn't find the drivers.
So basically my computer doesn't seem to recognize my Evo anymore even though it seems to be at its factory original stock settings. To top it off, it now seems to be stuck in a continuous reboot cycle every couple minutes or so (the worst that's ever happened to me before was semi-random restarts, maybe a couple times per week). I tried doing a factory reset by doing bootloader -> recovery -> menu -> factory reset but that didn't do anything. And I don't think it's charging anymore, considering that the battery is slowly getting lower and lower even though the orange light goes on when it's plugged in (though maybe it's just losing more battery than its gaining through all this restarting). At this point all I want is to get out of this continuous reboot cycle that I've spent the last couple hours trying to look for solutions for, with no luck. Much less re-customize my phone to how it was pre-restore and much less actually get through rooting it... Any help?
First re-run your RUU.
http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install ; download the modified hboot drivers
http://unrevoked.com/recovery/ ; download unrevoked
Make sure to have installed, then uninstall htc sync on your computer, and that usb debugging is enabled on your phone. Then run unrevoked and you should be good to go.
"First re-run your RUU."
But my PC isn't recognizing my Evo, I guess because something is wrong with the drivers? I tried running the RUU and it said Error [170]: USB Connection Error.
Caperi said:
"First re-run your RUU."
But my PC isn't recognizing my Evo, I guess because something is wrong with the drivers? I tried running the RUU and it said Error [170]: USB Connection Error.
Click to expand...
Click to collapse
http://dl.dropbox.com/u/19699565/3.70 RUU Zip.zip
A 3.70 ruu in PC36IMG form. Re-name to PC36IMG, then place on your sdcard, then boot into the bootloader, and apply the update and reboot.
teh roxxorz said:
[link]
A 3.70 ruu in PC36IMG form. Re-name to PC36IMG, then place on your sdcard, then boot into the bootloader, and apply the update and reboot.
Click to expand...
Click to collapse
How should I access my sdcard, since my PC isn't recognizing my phone?
I could probably do it via another phone, but I won't have access to that until tomorrow; is that the only way?
Edit: Oh boy. Just tried typing your link in on my phone, and apparently the phone doesn't recognize its sdcard... Might be why my PC isn't seeing my phone?
Well, you can take the battery out, remove the sdcard, the mount it to your computer via micro usb adapater.
teh roxxorz said:
Well, you can take the battery out, remove the sdcard, the mount it to your computer via micro usb adapater.
Click to expand...
Click to collapse
Don't have one of those, but even if I did (or got the files on there via another phone), wouldn't the fact that it won't recognize the sdcard be a problem when trying to get it to apply the update?
The battery is starting to get really low (about 10%), I think it's not recognizing the charger
Caperi said:
Don't have one of those, but even if I did (or got the files on there via another phone), wouldn't the fact that it won't recognize the sdcard be a problem when trying to get it to apply the update?
The battery is starting to get really low (about 10%), I think it's not recognizing the charger
Click to expand...
Click to collapse
Then what you could do is copy the files on the sdcard to the pc, then re-format it from there, then place the files on it, and stick it on the charger asap.
This link to recover sd card and usb:
http://forum.xda-developers.com/showthread.php?t=695243
Then let charge, use external wall charger if needed. If you have to buy one, its like 5 or 10 bucks and its better then having to buy a whole new phone.
Then, download the PC36IMG.zip (RUU in zip form), place on root of sd card, boot into bootloader, let it scan, when it asks if you want to run the update, say yes. Bada bing bada boom, your up and running. Then go download Unrevoked, its easier if your not completely sure what your doing, plus it has a nice and pretty UI that you cant possibly screw up and 5 minutes later your completely rooted, simple as that.
RileyGrant said:
This link to recover sd card and usb:
http://forum.xda-developers.com/showthread.php?t=695243
Then let charge, use external wall charger if needed. If you have to buy one, its like 5 or 10 bucks and its better then having to buy a whole new phone.
Then, download the PC36IMG.zip (RUU in zip form), place on root of sd card, boot into bootloader, let it scan, when it asks if you want to run the update, say yes. Bada bing bada boom, your up and running. Then go download Unrevoked, its easier if your not completely sure what your doing, plus it has a nice and pretty UI that you cant possibly screw up and 5 minutes later your completely rooted, simple as that.
Click to expand...
Click to collapse
Pardon me if I'm misunderstanding, but what I'm seeing from your post is that to fix the sd card issue I need to fix the usb issue, to fix the usb issue i need to get root, and to get root i need to fix the sd card issue? Haha, yeah I lost you somewhere along the way...
@teh roxxorz - You're saying that the sd card issue should be fixed if I reformat the SD card on my PC? If so, that's what I'm going to try tomorrow when I have that other phone I can use.
That should fix your issue.
So I reformatted the sdcard on my PC, got the PC36IMG.zip on there, ran it via bootloader, and it worked. But, I'm still stuck in the continuous reboot cycle, can't connect my phone to the PC, and in the brief moments it stays on, it won't recognize the sdcard...
On the bright side, it successfully charged overnight, so that's not going to be a problem.
I'm hesitant to try rooting (if that's even possible at this point) to fix the problem while it's in this state in case I have to take it back to Sprint, unless there's a reason that should fix the problem? It seems pretty hopeless right now...
If you're phone is still acting crazy & it won't stay on, I wouldn't try unrevoked. Just get rid of any evidence of rooting from your SD card, and take it back to Sprint - assuming you're s-on. If you have insurance, they'll give you a new one for free. Otherwise, I'm not sure what it will cost or if it will, or if you'll have to go through HTC.
plainjane said:
If you're phone is still acting crazy & it won't stay on, I wouldn't try unrevoked. Just get rid of any evidence of rooting from your SD card, and take it back to Sprint - assuming you're s-on. If you have insurance, they'll give you a new one for free. Otherwise, I'm not sure what it will cost or if it will, or if you'll have to go through HTC.
Click to expand...
Click to collapse
+1.
If its acting wacky before root, rooting it wont fix it. I would take it back to Sprint, for sure.
Sent from my PC36100 using XDA App
It sounds like you put your phone in diagnostic mode, when turning it on Volume Down takes it to the bootloader while Volume Up does Diag Mode. Check to see whether or not your phone shows S-OFF in the bootloader, if so you'll want to run the FlashZip script and select the Sprint Lovers file.
However, if your computer is still having trouble recognizing your phone let it sit for two minutes without the battery. If that still does not fix it use Volume Up and power one more time to try and take it out of that. I would also recommend against running Unrevoked if your phone is in Diag mode, it is very easy to permanently mess something up with it in that state.
edit: If you need to charge it more just turn the phone off and it should charge fine.
Problem I'm seeing is that u used auto root. I've seen nothing but thread after thread of problems with it. I've always used unrevoked3 and I've rooted many different phones including...2 heros, 2 evos, an Eris, a Droid, a Droid 2, and a Droid incredible. Never once did it fail or give me any issues. Simply follow the instructions and even watch the video on their site. If I where u I'd just ruu ur phone and start all over.
xHausx said:
It sounds like you put your phone in diagnostic mode, when turning it on Volume Down takes it to the bootloader while Volume Up does Diag Mode. Check to see whether or not your phone shows S-OFF in the bootloader, if so you'll want to run the FlashZip script and select the Sprint Lovers file.
However, if your computer is still having trouble recognizing your phone let it sit for two minutes without the battery. If that still does not fix it use Volume Up and power one more time to try and take it out of that. I would also recommend against running Unrevoked if your phone is in Diag mode, it is very easy to permanently mess something up with it in that state.
edit: If you need to charge it more just turn the phone off and it should charge fine.
Click to expand...
Click to collapse
My phone has always been S-ON throughout this.
I did try leaving it off and without battery for extended periods of time - no dice.
How could I tell if it's in diagnostic mode and what does diagnotistic mode do?
plainjane said:
If you're phone is still acting crazy & it won't stay on, I wouldn't try unrevoked. Just get rid of any evidence of rooting from your SD card, and take it back to Sprint - assuming you're s-on. If you have insurance, they'll give you a new one for free. Otherwise, I'm not sure what it will cost or if it will, or if you'll have to go through HTC.
Click to expand...
Click to collapse
k2buckley said:
+1.
If its acting wacky before root, rooting it wont fix it. I would take it back to Sprint, for sure.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
So I took it to Sprint, they spent a couple hours on it, placed an order for a new one, and gave me this one back saying it was dead and unfixable (I think all they did was a hard reset). When they gave it to me, it was on, and remained on without restarting for like 30 mins (I thought they had fixed it without realizing it). Just now, I turned it off and on again, and the reboot cycle started again... Any reason why it may have been working that one time? I'll probably just wait for the replacement, but just curious as to why it may have worked.
@Papa_Smurf - Yeah I tried to RUU it but that didn't fix any of the problems
I think it may have just been playing possum. Is it still doing it?
Yeah now it's in the reboot cycle again. Maybe if I was to let it run through the cycle long enough it might eventually stop until I manually powered down and on again (I'm guessing that's what had happened when I got it back from Sprint).
Hi, i have a problem with my phone i could not find any solution online.
Two days ago the phone was in my pocket in sleep mode. I took it out and it was closed, no button was responding, i took the battery out, put it back again and started it. It asked for the pin code, i entered then it said "unlocking sim card" then the phone restarted.
From that moment it constantly restarts, regardless of me entering pin code or not, it restarts. I use stock firmware and i didn't do any overclocking or any modifications to the phone.
I tried the boot screen (the one which is entered by pushing yolume down+power button) I did factory reset from that screen, it didn't help. I put the phone in recovery mode and a screen appears and nothing happens, i think it is like a dfu mode in iphone, i don't know how to use it. In the boot screen a green text screen appears for a second says "PC101img.zip is missing" or something like that.
Do i have to load the rom again to this phone? If so how can i do that?
Any help will be appreciated.
Hey,
i've never heard of this issue on any phone.
So you coulds just try to do a few things.
First you could try to flash a new radio ROM.
just see the android developement section and the radio thread.
the radio doesnt change the actual rom on your device so yiou wouldnt loos your data.
it might help it might not, as we dont know what the reason for the issue ist.
when does it reboot? when you enter the sim code?
try a different sim card, just to see if it still happens and/or try to remove the sim passcode.
this might help and might help to see where the issue is...
nick
Thanks for the answer. I didn't try different sim card but i tried to start the phone without the sim card and the sd card. It didn't change anything, it still restarts after few seconds.
the-nj said:
Hey,
i've never heard of this issue on any phone.
So you coulds just try to do a few things.
First you could try to flash a new radio ROM.
just see the android developement section and the radio thread.
the radio doesnt change the actual rom on your device so yiou wouldnt loos your data.
it might help it might not, as we dont know what the reason for the issue ist.
when does it reboot? when you enter the sim code?
try a different sim card, just to see if it still happens and/or try to remove the sim passcode.
this might help and might help to see where the issue is...
nick
Click to expand...
Click to collapse
I don't see how a new radio would affect the phones sim card...
Sent from my T-Mobile G2 using XDA Premium App
The problem seems to be with the sim card. I changed the sim card of the phone and it didn't restart from that moment. I used vodafone sim card with the phone for a week and after a week sim card started restarting the phone.
Is there a known cause of vodafone sim cards doing this?
Re: Constantly reboot...
the same issue does happen on mine! Stock firmware, never rooted, however, I've tried using different SIM cards and removed SD card, the same situation still exists. Reboot and reboot... please help!
Spastic909 said:
I don't see how a new radio would affect the phones sim card...
Click to expand...
Click to collapse
Yeah, and randomly suggesting to flash new radios for a problem this person never heard of before is not great advice. Bricking the phone is possible when radio flashing, and should be approached with caution, and only done when there is a radio-specific issue.
hi there,
was going to flash back to from 2.3.4 to the 181 Generic World image to root the phone again. i ran into the 1% battery bug thing. ok, so i removed the battery, put it back in, started the phone and now i can't use the phone no more.
it boots up, claims that it can't find the SIM card, hangs, then shut it self down.
if i remove the SIM card and SD card the phone boots up and shut it self down after a sec.
i can actually don't do anything, it simply shuts down.
i was flashing some other firmwares but always with the same outcome. i also tried to wipe all the user data while flashing, no sucess either.
this is the most bad situation i can imagine, so help would be much much appreciated
tahnks in advance
damo
ok, i just booted with the usb cable plugged in an it works.
seems like i got the 0% battery problem, thus the phone shuts it self down immediately (makes sense).
****, now i have to solve this bloody ****.
thanks anyway
damogran said:
****, now i have to solve this bloody ****.
thanks anyway
Click to expand...
Click to collapse
For 0% battery, is not yet any good solution unfortianly.
Sent from my MT15i using Tapatalk
there's the domocmo kernel which gives you 1% battery so it ain't all too bad actually
try the 0% battery workaround by bazoocase...it works fine...if not try when booting try to activate the plane mode...it requires fast hands and timing...plane mode minimizes battery use....
I think you have to use the flashtool and flash the new firmware. Goodluck
damogran said:
hi there,
was going to flash back to from 2.3.4 to the 181 Generic World image to root the phone again. i ran into the 1% battery bug thing. ok, so i removed the battery, put it back in, started the phone and now i can't use the phone no more.
it boots up, claims that it can't find the SIM card, hangs, then shut it self down.
if i remove the SIM card and SD card the phone boots up and shut it self down after a sec.
i can actually don't do anything, it simply shuts down.
i was flashing some other firmwares but always with the same outcome. i also tried to wipe all the user data while flashing, no sucess either.
this is the most bad situation i can imagine, so help would be much much appreciated
tahnks in advance
damo
Click to expand...
Click to collapse
Oh brother...it's like I am watching a mirror :'(
Sent from my LT15i using XDA
Hello all,
This is just the continuation of my last post - http://forum.xda-developers.com/galaxy-s4-tmobile/help/s4-acting-buggy-using-roms-t3306395
I was recommended to use Odin to flash the original 4.4.4 firmware, so I did just that and my phone worked for a few hours. But then, it would freeze again and force reboot. Then it would get stuck in bootloop and I would have to take the battery out to reset it. When this finally loaded, I wouldn't get any service and told me to insert an SIM card even though there was one already inserted. A few moments later it would crash again.
After this, I flashed the 4.4.2 firmware through Odin, and the same things kept happening. I'd only be able to use my phone normally for about an hour or so and then the cycle of crashing and bootlooping would start again.
I noticed that whenever I did a factory reset and wiped all data, the phone would work normally for a short period of time. But as usual, a bit later it will freeze.
Is this just a hardware problem with my phone and practically unsolvable, or is there a fix to this?
Any help will be appreciated, thank you.
Did you restore any data or apps after flashing the fresh firmware?
lumin30 said:
Did you restore any data or apps after flashing the fresh firmware?
Click to expand...
Click to collapse
Nope, I just went to the store to get a couple of my most used apps like WhatsApp, Twitter, and Soundcloud. I didn't restore anything else
Did you take out the micro SD card as well? Do you get messages when the device crashes?
Sent from my SM-G920T using Tapatalk
serio22 said:
Did you take out the micro SD card as well? Do you get messages when the device crashes?
Sent from my SM-G920T using Tapatalk
Click to expand...
Click to collapse
Yup, I tried rebooting without my SD card as well, same problem occurs. And usually what happens is it'll boot up, but becomes unresponsive as soon as I touch it. It will then reboot by itself and go into a bootloop. In the rare occasion I am able to bypass my lock screen after booting, I get a com.process is not responding and my background is all black. This too will eventually freeze and enter a bootloop.
fmaster12 said:
Hello all,
This is just the continuation of my last post - http://forum.xda-developers.com/galaxy-s4-tmobile/help/s4-acting-buggy-using-roms-t3306395
I was recommended to use Odin to flash the original 4.4.4 firmware, so I did just that and my phone worked for a few hours. But then, it would freeze again and force reboot. Then it would get stuck in bootloop and I would have to take the battery out to reset it. When this finally loaded, I wouldn't get any service and told me to insert an SIM card even though there was one already inserted. A few moments later it would crash again.
After this, I flashed the 4.4.2 firmware through Odin, and the same things kept happening. I'd only be able to use my phone normally for about an hour or so and then the cycle of crashing and bootlooping would start again.
I noticed that whenever I did a factory reset and wiped all data, the phone would work normally for a short period of time. But as usual, a bit later it will freeze.
Is this just a hardware problem with my phone and practically unsolvable, or is there a fix to this?
Any help will be appreciated, thank you.
Click to expand...
Click to collapse
i am also have some problem.
I noticed that when I restart, or power off and on my HTC 10, sometimes it will bootloop 2 to 3 times at the white HTC logo. Eventually, the green boot animation will load, Android will start and the phone will behave normally.
Except for this anomaly, my phone has been rock stable in everyday use. It's a Taiwan set with the latest 1.30 firmware.
Anyone else having this issue?
Nobody?
Same issue. It started with the most recent OTA update. After installing, it was stuck in a boot loop until I hard powered it off. Then it boot correctly, but asked to send a bug report.
Now when i restart my phone, it typically always asks to send a bug report.
mine does the bootloop with xposed installed on bell's 1.21 firmware.
Just chiming in - US unlocked on ATT, have seen this issue on the stock 1.53 ROM as well as Bad Boyz. It is indeed transient in nature.
Installed 1.80 Taiwan firmware and it's still there...
Just booted up from power off, and it rebooted 4 times by itself before the green HTC circle logo finally appeared! Coming from an LG G4 with the infamous boot loop of death, this is scary stuff!
There is another thread on this a few threads below this one. As I mentioned there, I had this issue on a fully stock U.S. Verizon 10. I formatted my SD card, which I had transferred over from my m8, and have not seen the issue since then.
Parakaleo said:
There is another thread on this a few threads below this one. As I mentioned there, I had this issue on a fully stock U.S. Verizon 10. I formatted my SD card, which I had transferred over from my m8, and have not seen the issue since then.
Click to expand...
Click to collapse
Did you format the microSD card using the 10, or using a PC?
chong81 said:
Did you format the microSD card using the 10, or using a PC?
Click to expand...
Click to collapse
PC. It cleared the card, I put my music back on it and nothing else. And that seems to have solved it.
Had this issue too
After some tests i found, that my microsd-card was the fault! had a samsung 128gb evo+ card.
with a different card this issue doesnt occur.
put back my samsung card and the issue occured again.
after low-level formatting the card the problem is solved
Parakaleo said:
PC. It cleared the card, I put my music back on it and nothing else. And that seems to have solved it.
Click to expand...
Click to collapse
Well, I take this back. After formatting my SD card, I had 4-5 days with no problems, then this morning when I powered on the phone, it did the bootloop/send error report thing again
It does seem to be related to the microSD card - I removed my microSD for a few days, rebooted plenty of times and encounter a single boot loop.
Mine is a Lexar 128GB UHS-I 633x microSD.
Folks, please share the microSD card you're using, and whether you have encountered the transient bootloop.