I have a HTC Thunderbolt and when I try and root it using the SuperOneClick method, it starts the process and almost right away it says waiting for device... and then my computer locks up. I am a beginner and do not know much yet, but if someone has a suggestion on what to do I would sure appreciate it. I have tried restarting computer, doing a factory data reset on phone and nothing seems to make any difference.
Do you have any antivirus software on you pc? If yes, have you tried disabling it (temporarily)?
computer freeze issue
Yes. I have AVG antivirus and I have tried temporarily disabling it for 15 minutes while I try to root my phone but it did not seem to make any difference. Any other ideas?
I would recommend using this method instead to root your Thunderbolt: http://wiki.cyanogenmod.com/wiki/HTC_Thunderbolt:_Full_Update_Guide .
Related
Here is what I have I can not get Odin to find the phone to do a master clear. My phone has a charging issue in that it thinks it is charging all the time even with the charging cable unhooked from the phone and that stays whether I am running 2.1 or 2.2. All of my computers are Windows 7 and will only find the phone if it is download mode?????
I am hoping against hope it is a software issue but I am thinking it is a hardware issue. But want to try everything possible to fix it before I buy replacement parts or a new phone.
I have tried the instructions from other threads without any success.
Could someone give me a step by step process that goes from starting fresh by deleting current drivers and reinstalling everything. I may be missing something from the instructions I have followed so far.
Also if you know something else to try I am all ears.
After you one click odin to reinstal Jf6 you have to set the phone to mass storage and USB debugging again ( found in settings-aplications ). Then plug the phone back into your comp while Odin is up and running ahead of time and the phone booted and running. It should recognise it ( you'll hear that dreaded sound ), click master clear and wait for the phone to do it's thing.
Well I finally got odin to find the phone and done the master clear and it did not help.
So unless anyone has any suggestions I will assume it is a hardware issue.
bigcountry said:
Well I finally got odin to find the phone and done the master clear and it did not help.
So unless anyone has any suggestions I will assume it is a hardware issue.
Click to expand...
Click to collapse
Since you're having problems with the phone being recognized maybe it's hardware. But, my phone is recognized just fine and I have an extremely hard time getting it to master clear.
I would guess I've only gotten it to master clear twice out of probably 40 or so attempts. About 10 of those times was in download mode, but after I found out it had to be booted up it still only master cleared twice. What I do to increase the odds is manually clearing everything I can, after backing up. Factory data reset, then I go into Clockwork and clear everything I can in there by digging into the menus - cache, data, Dalvik, etc. Then I go back to stock, then just hope it'll master clear on that flash attempt.
When it takes, it goes fast, but I've let it try for 15 to 20 minutes before and had nothing happen. No progress showing, just the start announced in Odin and then the disconnection announced when I get bored of nothing happening and pull it.
So my point is, maybe try it a few more times before you write it off as hardware. I don't recall the exact conditions when I got it to work, since it takes so many tries. But I believe it's been flash to stock Eclair, rooted, USB debugging on, and sd card mounted. Maybe not mounted. I reboot the phone after every time I try.
Edit: I did another update today and master clear worked fine. Un-rooted Eclair booted normally, usb debugging enabled, and usb mounted.
Have you had the phone not turn on while it wasn't plugged in?
OK, so I got a Xoom last week and shortly after that, managed to Root it successfully using this method: http://forum.xda-developers.com/showthread.php?t=1093126
A couple of days later, I decided to try and copy some pictures, etc. over to my Xoom. I plugged it in via Micro USB port to my laptop (the same one that I used to Root the Xoom). After a minute of churning, Windows 7 32-bit tells me "MTP USB Device FAILED" with a big red X next to it. I tried both with debugging mode on and off and tried all of the available ports on my laptop. Rebooted both devices, nothing. Changed USB cords 3 times, still nothing. I also tried debug mode and ran "adb devices" with nothing appearing in ADB.
I brought the Xoom to my work PC and got the same error there. Finally, I installed the Motorola driver Installer (Moto Driver Utility) and ran the Clean and Reinstall and it still gave the same error.
I went into Device Manager while it tried to install the drivers, and under Portable Devices, it listed "MTP USB Device" properly for a minute, then when it gives the error, there is a Yellow Exclamation point on the icon. Upon further inspection, I get the error message "This device cannot start. (Code 10)"
I am really worried that I won't ever be able to do anything via USB with my Xoom again (Un-root, tansfer files from and to the Xoom, etc.) Can anyone help me out with getting this fixed? I would prefer not to have to Wipe data, but I guess if I must, I must. I wouldn't even be against going back to un-rooted stock (if possible without USB connectivity) and starting over. I get the feeling that my Root process messed with something on the USB port software on the Xoom itself. I have not loaded any custom ROMs yet, it is just stock Rooted.
Thanks in advance!
Thats weird. I rooted mine last night, and works fine. Have you tried to factory reset it?
Back up everything w/ Titanium to a SD card if you can. If not then your gonna lose all data. Try to factory reset it, and see if that works.
mithusingh32 said:
Thats weird. I rooted mine last night, and works fine. Have you tried to factory reset it?
Back up everything w/ Titanium to a SD card if you can. If not then your gonna lose all data. Try to factory reset it, and see if that works.
Click to expand...
Click to collapse
I backed up using MyBackup Pro (Titanium force closes on me for some reason), then wiped and it now works properly.
When I first went into MyBackup Pro, it didn't ask for Superuser permissions, nor did it say I had root access like it normally does on first startup after a wipe. I exited out, went back in and now Superuser asked me to give permission and it shows I have root access.
When I ran the Root process (one-click Root by amoamare), I had to run it 3-4 times before I got the "Root Successful" message, so I have a feeling that the Root process may have messed with things on the Xoom causing all the headaches.
I think my problem is just isolated to my Xoom, and I found the resolution on my own by wiping the device per a Developer's suggestion. It is ok to close this thread.
Thanks mithusingh32 for the response, I was in the middle of wiping when you sent your response
WorldOfJohnboy said:
I backed up using MyBackup Pro (Titanium force closes on me for some reason), then wiped and it now works properly.
When I first went into MyBackup Pro, it didn't ask for Superuser permissions, nor did it say I had root access like it normally does on first startup after a wipe. I exited out, went back in and now Superuser asked me to give permission and it shows I have root access.
When I ran the Root process (one-click Root by amoamare), I had to run it 3-4 times before I got the "Root Successful" message, so I have a feeling that the Root process may have messed with things on the Xoom causing all the headaches.
I think my problem is just isolated to my Xoom, and I found the resolution on my own by wiping the device per a Developer's suggestion. It is ok to close this thread.
Thanks mithusingh32 for the response, I was in the middle of wiping when you sent your response
Click to expand...
Click to collapse
In the future it probably would be good to avoid the "one click" rooting methods. Glad it has all worked out.
okantomi said:
In the future it probably would be good to avoid the "one click" rooting methods. Glad it has all worked out.
Click to expand...
Click to collapse
Honestly, it doesn't matter to me using the one-click method or the manual way, the Xoom tablet is really just not an easy device to Root. I manually Rooted my Thunderbolt phone in about 25 minutes (most of that time was rebooting), never having rooted a phone before in my life.
With the Xoom, the one-click method was quirky, but it only took me about 30 minutes all said and done to root it despite the issues.
I tried to go back to stock/locked device (start from scratch) and it took me almost 2 hours, and another hours or so to manually root it properly. This is a very picky piece of hardware.
I am trying to run the Hack kit on my Inspire 4g and am having some problems. The first time I ran it, everything seemed to be working, phone rebooted several times, etc...only when it seemed to be finished I checked to see if it was rooted and it was not. Someone suggested running it again and I did, only now the error is
Radio Downgrade Failed:
Either goldcard failed or usb connections not 100.
I have tried running it on another computer with the same error. Antivirus is off, HTC sync is uninstalled, driver that came in the hack kit is installed, usb debugging enabled, charge only mode.
I have read the effen manual and tried to search this forum before posting a thread but I couldn't come up with anything that solved my issue. If someone could point me in the right direction it would be appreciated.
Thanks
I would factory reset the phone erase everything and try again. To do it, you may need to fastboot files. I would look and see. Tell me if this works....
Please hit the thank you button if i helped!
I did the reset and it seemed to improve things but now I have a new problem. While doing the hack, it gets to the point where it asks you to volume up for the update, which I did, then it process the update and says press power to reboot. When I press power it goes to the htc screen which then starts to fade out with lines across the screen, then it just goes to a black screen. No clue what I have done wrong?
kindsir said:
I am trying to run the Hack kit on my Inspire 4g and am having some problems. The first time I ran it, everything seemed to be working, phone rebooted several times, etc...only when it seemed to be finished I checked to see if it was rooted and it was not. Someone suggested running it again and I did, only now the error is
Radio Downgrade Failed:
Either goldcard failed or usb connections not 100.
I have tried running it on another computer with the same error. Antivirus is off, HTC sync is uninstalled, driver that came in the hack kit is installed, usb debugging enabled, charge only mode.
I have read the effen manual and tried to search this forum before posting a thread but I couldn't come up with anything that solved my issue. If someone could point me in the right direction it would be appreciated.
Thanks
Click to expand...
Click to collapse
and i have same plz hep
Hey guys.
I just felt that i had to write because i have done everything in my power and searched my ass off with no success.
----
To the problem.
My computer cannot find my phone, it does detect it but the phone doesn't show me any "activate USB mode" screen. The phone just does nothing.
This all happened very suddenly, and it specially happened after installing chainfire3D.
Anyone there who knows what i should do in order to fix this problem? and my main goal is to remove the "superuser" app in the menu so that i can at least get my warranty back.
---
It seems that the phone is half rooted and half not.
When updating superuser binary it tells me that there is no "su" path and it does not update.
Z4root freezes and dies
Superoneclick doesn't detect phone
Check root tells me that i am not rooted.
i am still on stock room, i just rooted it for some apps that i wanted like chain-fire and so on.
Please guys help me if you can would be much appreciated.
This should work: http://forum.xda-developers.com/showpost.php?p=17177547&postcount=2
Try it out, it's quite simple.
you can also use this guide, it helped me when i used it
Update: Solved.
Summary of issue: two identical devices side-by-side, s-off by Firewater works fine on one and won't work on the other. This rules out a lot of possible issues and so this was not an "I don't know how to use firewater's s-off method" post.
Solution: Factory reset FOUR TIMES. On the fourth factory reset, things worked.
Lesson learned: (After you make sure you're actually doing everything right and with the right files) you might actually have to give this many tries.
Cheers.
Thanks @pjim @Dodge DeBoulet @wtoj34
Hey everybody, Recognized Contributor here, usually the one who’s glad to help everybody else, and I’m totally… at a loss. Thanks X 10 for ANY help. I’m looking forward to contributing and modding on the Verizon M8 soon!
Issue: Two identical CDMA M8 devices, both on my Verizon account. Literally the same activation, using the same usb port, usb cable, computer and human:
Device #1: temproot using WeakSauce.apk; s-off using Firewater; installed the CWM recovery for our device; made a nandroid; flashed iB4STiD’s SkyFall ROM. ALL GOOD 100%.
Device #2: temproot using WeakSauce.apk; …. Firewater’s s-off will not do its thing with device #2. It goes only this far:
Code:
Do you understand the implications of these warnings? (Yes/No)
Yes
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, hold power for 60 seconds !!
…………………………………
……………………………….
……….. (indefinitely until I disconnect; I've waited 30 minutes just to be sure)
So it STOPS BEFORE the “preparing… the first bottle is open…chugging… ” part.
But… it ran five minutes before. Device #1 is good to go. Device #2? I’ve tried the hold power for 60 seconds thing, used different usb cables, different ports (hey, maybe something broke in the 30 seconds between devices?), redownloaded everything, matched MD5 checksums anyway, hard reboot via adb, repeat, start over like ten times…
For the love of God, can anyone think of what I can be doing wrong?
So funny...........
erikalin said:
Hey everybody, Recognized Contributor here, usually the one who’s glad to help everybody else, and I’m totally… at a loss. Thanks X 10 for ANY help. I’m looking forward to contributing and modding on the Verizon M8 soon!
Issue: Two identical CDMA M8 devices, both on my Verizon account. Literally the same activation, using the same usb port, usb cable, computer and human:
Device #1: temproot using WeakSauce.apk; s-off using Firewater; installed the CWM recovery for our device; made a nandroid; flashed iB4STiD’s SkyFall ROM. ALL GOOD 100%.
Device #2: temproot using WeakSauce.apk; …. Firewater’s s-off will not do its thing with device #2. It goes only this far:
Code:
Do you understand the implications of these warnings? (Yes/No)
Yes
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, hold power for 60 seconds !!
…………………………………
……………………………….
……….. (indefinitely until I disconnect; I've waited 30 minutes just to be sure)
So it STOPS BEFORE the “preparing… the first bottle is open…chugging… ” part.
But… it ran five minutes before. Device #1 is good to go. Device #2? I’ve tried the hold power for 60 seconds thing, used different usb cables, different ports (hey, maybe something broke in the 30 seconds between devices?), redownloaded everything, matched MD5 checksums anyway, hard reboot via adb, repeat, start over like ten times…
For the love of God, can anyone think of what I can be doing wrong?
Click to expand...
Click to collapse
As an auto technician, when someone says my car wont start my first question is, is there any gas in it? The first thing I would look for is the root. I have literally had weaksauce take up to 3 minutes to get root. If in the excitement you start adb and get firewater running before you get root, it cant write to the system and would get stopped,probably around where you are getting stopped. Make sure root is working before you even plug in the cable. Do something simple like start a root app and grant it before you start. As I read through these forums forums I've seen that this device is not consistent in it's behavior. One will not be the same as the other. Could even be internal, might consider an exchange. Usb ports fail all the time.
Hi. Thanks for taking the time. Yes, I'm waiting for root. Adb wouldn't be able to access root if, well, it didn't have access to root. (Not being sarcastic, just check-listing in my head.) I also have my laptop set to make a noise when it has root access. USB port is fine. Ugh. :/ I'm not sure I can come up with any reason to exchange. Thanks for trying. Cheers.
Sent from my SPH-L710 using Tapatalk
erikalin said:
Hi. Thanks for taking the time. Yes, I'm waiting for root. Adb wouldn't be able to access root if, well, it didn't have access to root. (Not being sarcastic, just check-listing in my head.) I also have my laptop set to make a noise when it has root access. USB port is fine. Ugh. :/ I'm not sure I can come up with any reason to exchange. Thanks for trying. Cheers.
Sent from my SPH-L710 using Tapatalk
Click to expand...
Click to collapse
I'm assuming you don't have any additional security measures enabled, such as a pattern or password lock (disabling that stuff is in most of the how-to's I've seen). Have you attempted a factory reset/do-over from scratch?
Try some of these I picked up from other forums. Have you tried factory resetting the device? Have you tried re installing adb on your computer? Have you tried removing the firewater file from your phone, and re download it on the pc? Does the firewater file have a (1) next to it? Have you tried uninstalling weak sauce and super su and do adb reboot on your pc then re root? Are you using the same account on your pc as your other phone?
Sent from my HTC6525LVW using Tapatalk
Dodge DeBoulet said:
I'm assuming you don't have any additional security measures enabled, such as a pattern or password lock (disabling that stuff is in most of the how-to's I've seen). Have you attempted a factory reset/do-over from scratch?
Click to expand...
Click to collapse
Hi. Thanks for taking the time to try to help me out. Yes, no security/lock stuff. Have tried factory reset and do-over from scratch at least twice, no joy.
wtoj34 said:
Have you tried factory resetting the device? Have you tried re installing adb on your computer? Have you tried removing the firewater file from your phone, and re download it on the pc? Does the firewater file have a (1) next to it? Have you tried uninstalling weak sauce and super su and do adb reboot on your pc then re root? Are you using the same account on your pc as your other phone?
Click to expand...
Click to collapse
Appreciate you taking the time. No need to reinstall adb stuff on my computer (I use the Android SDK for a lot of things; it's fine). Accounts on PC don't matter. Just "thinking out loud" here. I think I've done every combination of your other ideas too. Thanks again for sharing the ideas though...
There's either something I can't think of trying OR there's some odd little thing wrong inside the second device, and I can't think of any legit reason to bring it back for replacement because it otherwise acts fine. Ah well. People have bigger problems, lol. Cheers.
Update: Solved. See OP.
erikalin said:
Update: Solved.
Summary of issue: two identical devices side-by-side, s-off by Firewater works fine on one and won't work on the other.
Solution: Factory reset FOUR TIMES. On the fourth factory reset, things worked.
Lesson learned: You might actually have to give this many tries.
Cheers.
Thanks @pjim @Dodge DeBoulet @wtoj34
Click to expand...
Click to collapse
Wow, never would have guessed that repeated FRs would do the trick. Was that 4 in a row after your previous attempts, or 4 total throughout the entire S-OFF ordeal?
My own experience was entirely uneventful; the only bit of panic I've experienced with this remarkable phone was well after the root/S-OFF activity, during the installation of GSAM Battery Monitor. Installation of the root companion package required a reboot, and nothing appeared to happen after the confirmation button was pressed. When I manually rebooted, I got what seemed to be a "White Screen 'o Death," with no response from the usual reboot key combo. At some point the display went dark and I was sure it was bricked. I eventually tried the 60 second power button press, though, and it booted normally. Incidentally, GSAM appeared to be successfully installed as well.
USB 2.0 vs 3.0
I also haven't had any good luck with the firewater s off...mine hangs right after I say "Yes" then my phone diaconnects from adb and I have to start the process over again.
I've tried over 30 times, but I think it's been on usb 3.0 ports. I'm going to try on 2.0 and if that doesn't work...factory reset time...