Hi all,
I've had to root my HTC One S for school recently (yes, really), but now I can't install the update that's been released.
When I start the update my phone reboots and enters Clockwork..
I've been trying to unroot my phone, but there's a lot of (different) information out there, and I can't seem to put my finger on it.
For starters, I have no idea what RUU is and I have no idea which stock img I need, since their are more than 20 of them out there..
Can somebody please guide me through?
Thanks!
Tom
Edit: I can't seem to get a Android 1.0 USB driver working.. If I type adb devices it lists no devices.. I've tried like 5 different drivers but none are working.
Edit: My normal USB driver is working. ADB devices returns my device, but when I try to flash the recovery in normal mode, it just says 'waiting for device'.
Related
I've been trying to s-off my phone but its giving me the waiting for device status, after hours of googling i am stumped. I installed the latest SDk/drivers etc. adb devices detects my phone, i've even gone and installed pdanet just to see if it will connect and yes it does. HTC sync detects my phone, but revolutionary doesn't which i find very very odd and stressful. I am running windows 7 64 bit and yes i ran the program as admin. If there is anyone with any insight I will gladly appreciate it.
T.I.A!
MODS PLEASE LOCK THIS THREAD UP SOLUTION FOUND!!
I managed to figure it out by replacing AdbWinApi.dll with the newest one from the sdk. Now I am stuck on fastboot as adb doesn't detect it out now. reinstalled fastboot drivers, but nothing happens.
I have read all types of forums to Reboot Bootloader. Yeah, I know stuck at the beginning, not a good sign.Any way I went to Developer.android and got SDK. Followed various suggestions and have it on machine. However the windows 7 won't recognize device. I downloaded Motorola Device Manager for the drivers (I beleive this may be the issue) and it found no updates. I have debugged checked on Xoom, but jellybean icon shows up intermittently. When I type in CMD prompt to adb reboot bootloader, it doesn't recognize the device.
Other CMD commands suggested during instruction video worked verifying I had ADB installed coirrectly. I checked the device in control panel and it is unidentfied.Device properties has this error" Windows has stopped this device because it has reported problems. (Code 43)"
Please, can someone assist. I think that I need the drivers, but the motorola Device manager is the only tool I can find and I dont think it has the drivers, I could be wrong, but this is what I'm guessing.
Ok. I found online that the new USB 3.0 has issues with this process. I plugged into a 2.0 USB and I'm in business. I've gone through unlocking. Now I can't locate the Universal Xoom Root Zip. All tutorial links that I could find go to a link that no longer has the file. can someone point me in the right direction or send me a link to the file- Thanks for the help
Ok status update. I was able to find the file and have successfully Rooted. The question, now is I restarted and I have an Green Android robot on my screen with Tiamat engraved on front stomach area. I believe I was in recovery last. IS the Xoom doing anything in the background. I don't want to interrupt something if it is running. I have downloaded BiGPART and Omni 4.4 components but I seem to be stuck
Wow... Not one response. I was able to figure it out and now am the owner of 4.4
My post that died.. please read also
http://forum.xda-developers.com/showthread.php?p=48646053#post48646053
Hello guys, long story short.. a little while ago I tried upgrading my ROM to 4.4.4 and found out that i have to turn S-off and install the RUU 3.18 i think it was. Upon doing this I came to find out that my phone isn't being listed when I type adb devices. I have debugging mode on and install the latest HTC drivers and uninstalled HTC sync, but yet it wont list my device.
I did some research and found out it could be the current rom I have installed causing it not being listed and that I may have to use another ROM to get windows to see my phone. But I dont think I can flash another rom because I cant get into TWRP now. I can get in bootloader but now recovery doesnt work and i cant get into TWRP anymore,I think I also have to update Hboot too.
My question is how do I go about getting my phone listed in adb and how can install twrp again.. Its been soo long since I did this I may need some help. If i can get ADB to list my phone I should be able to do the upgrading myself.
I'm taking a break atm as this is giving me a huge headache. I know Its not hard to flash if you have ADB working. Or TWRP but I dont have either of them. Can anyone shed some light for me please..
This is whats on my bootloader page
EVITA PVT SHIP S-ON RL
HBOOT- 1.09.0000
RADIO- 0.16a.32.09.06
OpenDSP-v25.1.0.32.0405
eMMC-boot
rootbox jb evita if that matters
Thx for reading.
Any help would be greatly appreciated.
So to make sure I understand your situation:
1. You CAN boot into your rom
2. You CANNOT boot into your Recovery (I'm assuming bootloop)
3. You CANNOT see your device in adb OR fastboot (please confirm)
So here's the best case scenario. You are NOT running Windows 8.1 and you can see your device in fastboot while in the bootloader. In this case, S-OFF again and flash recovery as usual. If your ARE running Win 8.1 .... well we'll cross that bridge when we get to it.
To debug your adb problem plug your phone into your computer. Does your phone respond in any way? Do you see the device show up on your computer for file transfer? If any of these things is true, rejoice! For there is hope! This is just for assurance, but you do have developer settings turned on and adb enabled right? Have you tried other usb ports? I forget if there is authentication in 4.2.2 but if there is, did you add you trust your computer? Try revoking all trusted computers and try again. Have you tried the newest version of ADB? Have you tried a different cord? If you have tried ALL of these, open up device manager. This can be done by simply typing into the search in start on both Win7/8. Now look at the top of the list. Do you see anything like ADB Interface or Android Device? If not, do you see any unrecognized devices or any device with an exclamation mark under Other Devices or Universal Serial Bus Controller? If any of these is true, right click the device and select properties. It'll be best to post a screen shot at this point. But if you're an intrepid risk seeker, go to the driver tab and hit uninstall. Next unplug your device, wait a few moments and plug it back in. You should see a driver installation progress. I've also attached the generic Google drivers that I know for sure works should you need it. Now try adb again and hopefully your device shows up:highfive:
If all is wrong with the world, and you do not see anything when you connect your phone, try on different computer with a different cord.
i made a extremely poor decision and was trying to change the boot animation loader when i actually changed the boot cmd and now it boots to samsung then to download everytime,. i can get into the onboard recovery yet i cant access safestrap and none of the many many drivers ive tried i cant get the phone to show to connect, its listed as unknown device in my device manager and ive hand picked the ones im supposed to have to other ones. ADB doesnt see it either and i was wondering if there is cmd for adb to find myu device, if you help me guys i promise ill only practice on hand me down smart phones. Ty:cyclops: [email protected] SM-G870A
This may be a dumb question, but have you tried Odin? I have had situations similar to this with my Samsung devices and always thought i bricked. But as long i could get into download mode, i could Odin back to stock and start over.
MrAwesome75 said:
This may be a dumb question, but have you tried Odin? I have had situations similar to this with my Samsung devices and always thought i bricked. But as long i could get into download mode, i could Odin back to stock and start over.
Click to expand...
Click to collapse
ya but i havent even tried loading a file into odin cause it wont see my device
and i have installed the samsung drivers but after this happened my pc wont see the phone
has to be a way to get a connection between the pc and phone
I'm not an expert so I'm not sure. Do you have the correct drivers installed on PC?
---------- Post added at 06:34 AM ---------- Previous post was at 06:30 AM ----------
Try different Odin versions. And make sure you have the proper drivers installed on the PC.
ya ive actually read that it probably doesnt have the function running to talk with the pc cause it cant boot. im all set up to reset the phoone. just need it to appear in my odin
..does kies still work?
[email protected] said:
i made a extremely poor decision and was trying to change the boot animation loader when i actually changed the boot cmd and now it boots to samsung then to download everytime,. i can get into the onboard recovery yet i cant access safestrap and none of the many many drivers ive tried i cant get the phone to show to connect, its listed as unknown device in my device manager and ive hand picked the ones im supposed to have to other ones. ADB doesnt see it either and i was wondering if there is cmd for adb to find myu device, if you help me guys i promise ill only practice on hand me down smart phones. Ty:cyclops: [email protected] SM-G870A
Click to expand...
Click to collapse
When you boot to system
It doesn't show anything right ??
but the touch is still functioning
Sent from my GT-i9300 running cm11 using tapatalk.
when i just boot it goes to download mode and says "could not do do normal boot"
i can access recovery mode and download mode but i cant get drivers to show it, and it used to show it until i did this, can i put a file on my micro SDcard from my pc via card reader then install it in recovery mode ? like firmware or a memory wipe reset?
If you can get into recovery, I believe that would be possible. Couldn't hurt to try. As long as you can get into recovery and all the recovery functions work, I don't see why you couldn't.
fixed it!
well after two nights of reading i got my pc to discover the device by changing ports three different times to find one that seamed to like it. and also installed kies and installed the drivers from them, (figured couldnt go wrong after as many as ive used from samsung and others). so win7 pro / altered boot command and only stock options afterwards sucks big time. ty all for helping me
never let up
Hey so like i have a problem. It\s seems to be to simply impossible to get any drivers to work, i tried everything google drivers, sdk ,drivers that come on phone and drivers from some random websites. Nothing works, tried both w10 and linux ubuntu. On my older pc i had 0 issueas other than simply doing something dumb.
Im out of ideas, help? Also tried with sony z5 premium instead of my nokia 7 plus but same thing -_-
Sidenote:fastboot device from phone drivers kinda works(?) But still im not able to do anything because im stuck on waitig on devices when i want to flash
To manage an Android phone from PC you at least need
1. ADB - provided by Google
2. FastBoot - provided by Google
3. Android-USB-driver provided by OEM/Carrier matching your phone
and nothing else.
Have all of those and im stuck on waiting on devices after i reboot to bootloader. Seriously annoying maybe i will try on other pc and see what happens but its not really a solution
If your phone supports Fastboot - take note that not all phones do - then when Fastboot returns "Waiting for device" it's a driver problem: Install correct driver.
True but as i wrote official drivers don't work it's on the phone after all. Rest doesn't work too then . Heh