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).
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.
Severe panic!!
I rooted my Desire which was running 2.2 Froyo on the O2 UK network using unrevoked and it worked fine without any issues. Custom recovery by ClockworkMod.
The next day I then decided i needed to turn S-off so found a guide and tried installing unrevoked forever from a zip on the root of the SD and i got 'installation aborted error 42'. Tried again the next day but before i got started i decided to give myself re-assurance that i wouldnt lose anything on the device so i entered recovery and chose restore.
Big mistake! My handset then rebooted and got to the O2 splash screen. It wont move from there. Pulled battery out and tried again. Same. I assume i havent bricked the device and it is just stuck in a boot loop?
Since then i have removed all my user data from the SD card and 'cleared storage'. Tried installing an miui rom and again 'installation aborted'.
Can anyone clarify why this is happening and point me in the right direction?
I am a noob and would appreciate any help on this.
TannyBhoy said:
Severe panic!!
I rooted my Desire which was running 2.2 Froyo on the O2 UK network using unrevoked and it worked fine without any issues. Custom recovery by ClockworkMod.
The next day I then decided i needed to turn S-off so found a guide and tried installing unrevoked forever from a zip on the root of the SD and i got 'installation aborted error 42'. Tried again the next day but before i got started i decided to give myself re-assurance that i wouldnt lose anything on the device so i entered recovery and chose restore.
Big mistake! My handset then rebooted and got to the O2 splash screen. It wont move from there. Pulled battery out and tried again. Same. I assume i havent bricked the device and it is just stuck in a boot loop?
Since then i have removed all my user data from the SD card and 'cleared storage'. Tried installing an miui rom and again 'installation aborted'.
Can anyone clarify why this is happening and point me in the right direction?
I am a noob and would appreciate any help on this.
Click to expand...
Click to collapse
Try to bring you phone to stock.
Download RUU .
Turn your phone on in fastboot (hold back button and press power - when your phone is off).
You have to have HTC Sync installed.
Run the exe file.
After that repeat the rooting and s-off-ing procedure.
Can the RUU be flashed in clockwork mod recovery or does it have to go through HTC Sync?
If it cannot be flashed in Clockwork Mod, I presume he has to
Connect phone via USB to PC,
boot into Fastboot as you mentioned
run HTC Sync
and then run the Ruu.exe file (does HTC Sync recognise this filetype and then do it's thing?)
And that's it? (Just that it seems too simple!)
OriginalThinking said:
Can the RUU be flashed in clockwork mod recovery or does it have to go through HTC Sync?
If it cannot be flashed in Clockwork Mod, I presume he has to
Connect phone via USB to PC,
boot into Fastboot as you mentioned
run HTC Sync
and then run the Ruu.exe file (does HTC Sync recognise this filetype and then do it's thing?)
And that's it? (Just that it seems too simple!)
Click to expand...
Click to collapse
You might need a goldcard. Try without one for now.
Right I'll let him know to give that a go. If it doesn't work I might pick your brains around the goldcard option.
Massive thanks so far for your advice!
Dude thanks for that. Im going to give that a bash and let you know how i get on!
Much appreciated!
Haven't tried this but it's worth giving it a shot. http://www.addictivetips.com/mobile...gold-card-for-htc-desire-without-hex-editing/
Or this: http://www.nazriawang.com/2010/04/how-to-create-goldcard-with-ubuntu.html
TannyBhoy said:
The next day I then decided i needed to turn S-off so found a guide and tried installing unrevoked forever from a zip on the root of the SD and i got 'installation aborted error 42'. Tried again the next day but before i got started i decided to give myself re-assurance that i wouldnt lose anything on the device so i entered recovery and chose restore.
Click to expand...
Click to collapse
Hello. I think you wanted to say you chose back-up, otherwise you couldn't have chosen the restore option since you don't have any restore points.
So if you hit back-up and your phone stuck in the boot loop it is normal. This is a problem because of the root and the fact that making a nandroid back-up will mess something in the NAND. But restoring the back-up you just made should resolve all the problems. I had the same issue and by only restoring the back-up I've just made got me working back, and still had the ROOT.
I don't think you need to run a RUU just for this.
UsManyDead said:
Hello. I think you wanted to say you chose back-up, otherwise you couldn't have chosen the restore option since you don't have any restore points.
Click to expand...
Click to collapse
I should have made clearer sorry. After i rooted successfully i entered recovery and hit backup option and it told me it had created a backup successfully. I had been using the phone as normal for another day before deciding to s-off and at that point i thought to 'test' my backup to make sure it had done it so i chose restore thinking anything i have downloaded on the phone since the back up will disappear and was expecting the restore to bring my phone back to the settings i had the previous day but the restore failed and thats when it got stuck in the boot loop.
Mine did the same thing except, instead of trying to s-off it just decided at one point that it felt like it, literally, I wasnt even using it at the time it was just charging. I did downloaded the stock ruu, it was linked earlier. Put it in fastboot, run the ruu and boom, however i did it on my goldcard, so make one if it doesnt work without it. Good luck.
paul.c said:
Try to bring you phone to stock.
Turn your phone on in fastboot (hold back button and press power - when your phone is off).
You have to have HTC Sync installed.
Run the exe file.
After that repeat the rooting and s-off-ing procedure.
Click to expand...
Click to collapse
BACK IN BUSINESS!! Dude you are the man! The RUU didnt install as it was a different boot version so from the site you suggested i used the Froyo version and its now working! Many thanks.
P.s. What's the easiest way to s-off? Also whats the correct way to create a complete back up restore point and then actually restore to that point without getting to this stage again?
paul.c said:
Try to bring you phone to stock.
Turn your phone on in fastboot (hold back button and press power - when your phone is off).
You have to have HTC Sync installed.
Run the exe file.
After that repeat the rooting and s-off-ing procedure.
Click to expand...
Click to collapse
BACK IN BUSINESS!! Dude you are the man! The RUU didnt install as it was a different boot version so from the site you suggested i used the Froyo version and its now working! Many thanks.
P.s. What's the easiest way to s-off? Also whats the correct way to create a complete back up restore point and then actually restore to that point without getting to this stage again?
TannyBhoy said:
BACK IN BUSINESS!! Dude you are the man! The RUU didnt install as it was a different boot version so from the site you suggested i used the Froyo version and its now working! Many thanks.
P.s. What's the easiest way to s-off? Also whats the correct way to create a complete back up restore point and then actually restore to that point without getting to this stage again?
Click to expand...
Click to collapse
Easiest way to s-off is alpharev:
http://alpharev.nl
***NEW ISSUE***
Since i have my phone back to it's original state and have lost root access. The idea is to root again via Unrevoked, which requires me to update the Android 1.0 driver (in device manager under other devices) to the Android Bootloader Interface. However, DM now does not say 'other devices - Android 1.0' and instead it says 'Android Devices - MY HTC'. So i decided to completely uninstall HTC Sync and all it's drivers and then rebooted PC, reinstalled SYNC and then uninstalled again but this time leaving the drivers in. Rebooted again and repeated the process but it still recognises the device as 'MY HTC' instead of 'Android 1.0'.
Could it be that this is fine, it's just the new way since i am using the updated version of HTC sync now? Or is this going to cause an issue? I am now playing it a lot safer to avoid anymore issues and quite happy to try something you may suggest...
TannyBhoy said:
***NEW ISSUE***
Since i have my phone back to it's original state and have lost root access. The idea is to root again via Unrevoked, which requires me to update the Android 1.0 driver (in device manager under other devices) to the Android Bootloader Interface. However, DM now does not say 'other devices - Android 1.0' and instead it says 'Android Devices - MY HTC'. So i decided to completely uninstall HTC Sync and all it's drivers and then rebooted PC, reinstalled SYNC and then uninstalled again but this time leaving the drivers in. Rebooted again and repeated the process but it still recognises the device as 'MY HTC' instead of 'Android 1.0'.
Could it be that this is fine, it's just the new way since i am using the updated version of HTC sync now? Or is this going to cause an issue? I am now playing it a lot safer to avoid anymore issues and quite happy to try something you may suggest...
Click to expand...
Click to collapse
Same here. But everything is working fine.
So put phone in usb debug mode and "only charge" mode, start abd, connect phone via usb to pc and type
Code:
adb devices
. If your desire's serial number is shown, everything is fine.
MatDrOiD said:
Same here. But everything is working fine.
So put phone in usb debug mode and "only charge" mode, start abd, connect phone via usb to pc and type
Code:
adb devices
. If your desire's serial number is shown, everything is fine.
Click to expand...
Click to collapse
Hey man thanks for the advice. If yours is working fine, ive no reason not to try it!
As i am a noob, can you clarify "start abd" ??
Also, type code "adb devices", where to type?
TannyBhoy said:
Hey man thanks for the advice. If yours is working fine, ive no reason not to try it!
As i am a noob, can you clarify "start abd" ??
Also, type code "adb devices", where to type?
Click to expand...
Click to collapse
To start adb issue: "adb start-server" command without the quotes
To stop it: "adb kill-server"
Here is the complete list: http://developer.android.com/guide/developing/tools/adb.html
TannyBhoy said:
***NEW ISSUE***
Since i have my phone back to it's original state and have lost root access. The idea is to root again via Unrevoked, which requires me to update the Android 1.0 driver (in device manager under other devices) to the Android Bootloader Interface. However, DM now does not say 'other devices - Android 1.0' and instead it says 'Android Devices - MY HTC'. So i decided to completely uninstall HTC Sync and all it's drivers and then rebooted PC, reinstalled SYNC and then uninstalled again but this time leaving the drivers in. Rebooted again and repeated the process but it still recognises the device as 'MY HTC' instead of 'Android 1.0'.
Could it be that this is fine, it's just the new way since i am using the updated version of HTC sync now? Or is this going to cause an issue? I am now playing it a lot safer to avoid anymore issues and quite happy to try something you may suggest...
Click to expand...
Click to collapse
Thanks for the suggestions surrounding ADB but i guess im too much of a noob for that part, it seems massively complicated, im sure it doesnt to you guys. Isnt there an easier way? Or considering my above quote, can i just assume that its all working fine and go ahead with the root or should it really need to have 'Android 1.0' in device manager?
Im pretty certain this all happened becuase the first time i rooted i had followed instructions and uninstalled HTC Sync (not the drivers) which had been on my system since i got the phone lat year. Since i had to reinstall to flash the RUU im certain its an updated version of HTC Sync thats causing this issue. But is it really an issue?
TannyBhoy said:
Hey man thanks for the advice. If yours is working fine, ive no reason not to try it!
As i am a noob, can you clarify "start abd" ??
Also, type code "adb devices", where to type?
Click to expand...
Click to collapse
Here you have a nice guide about adb:
http://androidforums.com/desire-all...fastboot-windows-updated-1st-june-2011-a.html
This should answer all your questions.
HI. Okay, so a couple weeks ago, I received a notification from HTC that said there was a new update available. Since I had S-Off and an unlocked bootloader (don't ask why, I just ****ing do.) I could not update, as it would give me errors, and cancel the update. So, earlier today I was fed-up with how slow my phone was being, and I wanted to fix it by updating. So I scoured XDA and found a thread about how to update by updating the HBoot or whatever. I followed those instructions and everything was fine, until I got to the initial part of installing the new **** through RUU. It was running fine, and then all of a sudden, the phone disconnected and ****ed the installation up. My battery was fully charged, and still has a charge as I am writing this. I digress. Whenever I would try to power my phone on, I would feel THREE (3) vibrations, and nothing would happen after. I tried booting into the stock recovery (fastboot, recovery, etc) and would still get THREE (3) vibrations. Bricked. So, I looked through a few threads on XDA, and found a few ways to fix it. Something about a Blind HBoot, or a Qualcomm Diagnostic Mode being stuck or something. Figured it was my best shot to try these. I tried them all. I put the PG76IMG.zip into my SD card, and booted up when holding Volume down, and only got THREE (3) vibrations. The tutorial said I was supposed to get FIVE (5) vibrations. So, I thought maybe it was something strange, and kept going through the tutorial. After five minutes, I'm supposed to press VOL UP, and should feel THREE (3) vibrations. Nothing happened. I waited and waited and tried again, and still, nothing. My phone is still lying here as a paperweight, and I want to get this working, so I can sell it because this phone is too much of a ****ing hassle for me. NOTHING HAS WORKED. ROMS, KERNELS, NOTHING. HAS. WORKED. I'M TIRED OF IT. I'm not a noob, I've been working with Android phones for a long time, and have never quite used an HTC device before. I had a Samsung Galaxy S Fascinate (CDMA) and it lost it's flash after I had moved to a different state. (The state I'm in does not have any towers for that carrier here.) SO. Can ANYONE give me a HIGHLY DETAILED tutorial, STEP BY STEP, to fix my phone?
HTC Wildfire S *Relocked* bootloader S-OFF CDMA METRO PCS.
I have tried everything I can find, and I have reached my wits end, man. Please, for the love of GOD, help me. I would really appreciate it.
I had 1000 rom flashes
3 Updates through RUU
Never had a brick
I hope someone can help you.
This is same as this thread http://forum.xda-developers.com/showthread.php?t=1522235
m1ndh4x8r said:
I had 1000 rom flashes
3 Updates through RUU
Never had a brick
I hope someone can help you.
This is same as this thread http://forum.xda-developers.com/showthread.php?t=1522235
Click to expand...
Click to collapse
I don't see how this helps me.
Help in the sense u have sent it to HTC for repair
Try this http://forum.xda-developers.com/showthread.php?t=1432425
Sent from my HTC_A510c using Tapatalk
kyleisah said:
HI. Okay, so a couple weeks ago, I received a notification from HTC that said there was a new update available. Since I had S-Off and an unlocked bootloader (don't ask why, I just ****ing do.) I could not update, as it would give me errors, and cancel the update. So, earlier today I was fed-up with how slow my phone was being, and I wanted to fix it by updating. So I scoured XDA and found a thread about how to update by updating the HBoot or whatever. I followed those instructions and everything was fine, until I got to the initial part of installing the new **** through RUU. It was running fine, and then all of a sudden, the phone disconnected and ****ed the installation up. My battery was fully charged, and still has a charge as I am writing this. I digress. Whenever I would try to power my phone on, I would feel THREE (3) vibrations, and nothing would happen after. I tried booting into the stock recovery (fastboot, recovery, etc) and would still get THREE (3) vibrations. Bricked. So, I looked through a few threads on XDA, and found a few ways to fix it. Something about a Blind HBoot, or a Qualcomm Diagnostic Mode being stuck or something. Figured it was my best shot to try these. I tried them all. I put the PG76IMG.zip into my SD card, and booted up when holding Volume down, and only got THREE (3) vibrations. The tutorial said I was supposed to get FIVE (5) vibrations. So, I thought maybe it was something strange, and kept going through the tutorial. After five minutes, I'm supposed to press VOL UP, and should feel THREE (3) vibrations. Nothing happened. I waited and waited and tried again, and still, nothing. My phone is still lying here as a paperweight, and I want to get this working, so I can sell it because this phone is too much of a ****ing hassle for me. NOTHING HAS WORKED. ROMS, KERNELS, NOTHING. HAS. WORKED. I'M TIRED OF IT. I'm not a noob, I've been working with Android phones for a long time, and have never quite used an HTC device before. I had a Samsung Galaxy S Fascinate (CDMA) and it lost it's flash after I had moved to a different state. (The state I'm in does not have any towers for that carrier here.) SO. Can ANYONE give me a HIGHLY DETAILED tutorial, STEP BY STEP, to fix my phone?
HTC Wildfire S *Relocked* bootloader S-OFF CDMA METRO PCS.
I have tried everything I can find, and I have reached my wits end, man. Please, for the love of GOD, help me. I would really appreciate it.
Click to expand...
Click to collapse
ok, im not saying i can get it going again but i`ll do my best to help. lets start from the beginning, what actually works atm? you say when you try boot up the phone in any way it just vibrates 3 times.
does it do anything else, does the screen light up?
does it even stay on?
when you connect it to the charger does the led still light up?
have you tried to connect it to the pc? have you tried to connect it too the pc with volume down first?
all seem very basic stuff obviously but if the pc can register it in hboot we might be able to get a ruu running on it.
Found this on a different thread...
Nevermind. Just realized you were still getting three vibrates. Sorry man. I'll keep an eye out if I see anything else that might help.
what is your hboot version? i was see 1.09.099 like in forum maybe you can start with update hboot.
you can use adb for all of this works. download a ruu and run it. after some steps you can find rom.zip in windows/temp extract it to a folder like c:\android\rom and use adb for install all *.img files. maybe it can fix that problem
hypercode said:
what is your hboot version? i was see 1.09.099 like in forum maybe you can start with update hboot.
you can use adb for all of this works. download a ruu and run it. after some steps you can find rom.zip in windows/temp extract it to a folder like c:\android\rom and use adb for install all *.img files. maybe it can fix that problem
Click to expand...
Click to collapse
seriously , adb can install img files ?!
Alright, well, I called htc and told them about my problem, and I might have to just send it in. BUT. I had my phone rooted, and had CM Recovery on it. So, since nothing is booting up at all, only the three vibrates when trying to enter either boot mode, will they be able to see that I had it rooted or anything? They said they'll charge 35$ just to ship it back in the same condition if it is. Can't really afford anything like that right now.
tl;dr I had my phone rooted, but nothing on my phone comes up, will they see my root or anything?
if you are rooted you are probably s-off or at least have unlocked bootloader. and both they will find out very easily.
Sorry for my bad it was fastboot.exe you can install .img files with fastboot.exe i was installed stock recovery with that
Sent from my HTC Wildfire S A510e using XDA App
Basically, this: http://forum.xda-developers.com/showthread.php?t=1384415
No one responded to that thread because it was in the wrong forum.
I got the "Phone -- ! -- PC" screen, and was attempting to fix it before getting this black screen of death.
Galaxy Nexus GSM
Rooted, Codename ROM, don't think there is a Kernel in there
Carrier: Virgin Mobile
Edit: I won't be able to respond for a couple hours as I'm going to work. Any and all help is much appreciated.
Original post from above thread below:
Hello guys,
I have recently bought my first android phone, the Samsung Galaxy Nexus.
On the second day I decided to root it since I needed market enabler, as my local market (UAE) has literally no apps.
I rooted using the SDK tools, fastboot and superboot. Everything worked fine for 1 day.
However, the next day, the phone just died on me, and would not boot at all. It kept getting stuck on the "Google" image at startup. At that point, I could still go into the bootloader. I tried locking/unlocking the bootloader again, since that basically wipes all the date on the phone, but it still refused to load, it would get stuck at the startup animation.
After a few more attempts, it kept spam restarting every time I tried to switch it on.
At that point, I was downloading the default OEM ROM so I could reflash that onto the phone. However, I thought I could try using the superboot bat file again, and maybe that would fix the problem. BIG MISTAKE.
As soon as I ran that file, the phone COMPLETELY died. It will not start at ALL, it will not go into Bootloader, not go into Recovery mode, and not even go into Download (odin) mode.
The ONLY possible response you can get from it, is when you plug it into the PC. My PC seems to play that "detection" sound, same sound as when you plug in a USB, but it would just play that sound over and over again, as if im plugging/unplugging a device really quickly. It seems like the phone is continously restarting itself. When I connect the phone to the PC and that disconnect/reconnect sound comes up, I went into my device manager and I could see the following:
An item under "Other Devices" called "OMAP4440" keeps appearing and dissapearing all the time, with the little "!" mark next to it indicating that there is a driver error. The drivers for this phone are fully installed on this same PC, and it use to work fine before it went dead.
Now the problem is since I cant get into any mode whatsoever, its a bit hard to diagnose the phone. I know there is a "recovery" slot at the bottom of the phone that is accessible with a small pin, but I dont for the life of me know how that works or what it does. Does anybody know how to work that or what it actually does?
Any help would be appreciated! Thanks fellas.
Click to expand...
Click to collapse
What i with my little (almost nothing experience in android) would do its going to another computer with no drivers installed, would download the toolkit and install those drivers, then plug the phone and see what happen, im sure its not bricked since the computer recognice it.. I did lot of stuff with blackberry and there was a lot of ways to recover a phone like that... From here if the toolkit recognice it in any way.. Then you could try to do some of those steps.. As far as i tried doing all kind of stuff to my phone, toolkit its for much the Best Tool and way to do anything to your phone or at least for starters like me
Sent from my Galaxy Nexus using xda premium
But the computer doesn't actually recognize it. The "detection" sound it makes is for an unresponsive device. It won't charge, won't be recognized, and no matter what combo I use, it doesn't turn it.
I played dumb, called Samsung, and now I'm going to send it in. Thanks for the help though.
sometimes my screen goes blank and I have to pull the battery and everything comes back to normal