Is it possible to unroot your phone without your usb connection working anymore? I plug my phone into my computer which is running Windows XP Media Center edition Version 2002 Service Pack 3 and it says USB Device not recognized. I tried to manually update the driver in the device manager but it tells me that the specified location does not contain information about your hardware and I verified that they are the drivers for my hero. I even tried a new cable to eliminate that as a problem but I still have the same issues. To give it one last try I plugged it into my laptop Running Windows Vista and also came up with usb device not recognized. I would like to return my phone to Sprint so I can get the usb connection problem fixed but I need to unroot the phone first. PLEASE HELP! - Josh
Bassman4LF said:
Is it possible to unroot your phone without your usb connection working anymore? I plug my phone into my computer which is running Windows XP Media Center edition Version 2002 Service Pack 3 and it says USB Device not recognized. I tried to manually update the driver in the device manager but it tells me that the specified location does not contain information about your hardware and I verified that they are the drivers for my hero. I even tried a new cable to eliminate that as a problem but I still have the same issues. To give it one last try I plugged it into my laptop Running Windows Vista and also came up with usb device not recognized. I would like to return my phone to Sprint so I can get the usb connection problem fixed but I need to unroot the phone first. PLEASE HELP! - Josh
Click to expand...
Click to collapse
you can "re-flash" the stock .img files from Better Terminal. I lucked out on my last phone that went completely dead for no reason I knew of. The techs couldn't revive my rooted phone, so I got a replacement.
Since then, I do a "watered down" root - @forum.xda-developers.com/showthread.php?t=694572
Without having to wipe everything clean and start from scratch- Flashing the stock and removing root works for me through this:
I copied unrevoked and RA1.6.2 to my sdcard. Use step 7 & 8 (sh /sdcard/unrevoked and flash the RA recovery img). After reboot, I make a nand backup.
For me anyway- by doing none of the rest, it allows me to remove the apps I want to remove and allows me to reflash the stock 2.1 recovery image. I can then update to .6 if necessary to seal it up...flashing the recovery image can be done from the phone using Better Terminal as well.
The only reason I prefer it this way is, I don't want to use a custom ROM and I only want to pull some of the unecessary (for me) apps out. I'll back it up and if need be, I am 1 step closer to "unrooting" it.
I know, I know...but to each his own...I've taken a rooted phone in (no custom ROM) with a speaker issue- no hassles. I've taken a rooted phone in for dust under the screen, way back when- and had to argue the point that ROMS and rooting had nothing to do with a defect in manufacturing that caused the dust under the screen (was able to get a replacement just slightly after my 30 days was up).... So when this last one was completely dead - I thought for sure it was going to cost me.
Long Lost Thank You!
I tried that and it totally worked. I appreciate the detailed feedback. I just realized I never commented back! Now I have an EVO and I just put MIUI on it, can't wait to try it out. Thanks again!
OK folks, I know some of you are going to jump straight down my throat, but please, back off and stick to the friendly forums that this used to be where anyone would help anyone.
the story so far is that I once loved my Nexus One, I've had it since launch, I have ran Cynogen Mod 7 for a couple of years, I have had MUI roms running, I have played with various kernels, updated radio, upgraded hardware, all was going wonderfully.
the one thing I could never get was full SU!! Heck knows why!!
I then started getting random problems and downloaded the original google frf83 software and flashed the phone via update.zip using amon-ra recovery.
I thought all was well after this, as my phone received 3 OTA updates and now my phone is on...
Android 2.3.6
Baseband 32.41.00.32U_5.08.00.04
Kernel 2.6.35.7-59465-g42bad32 ([email protected] #1)
Build GRK394
I noticed that in the Status (settings) it was displaying my old sim card number, which is not the number for the sim in the phone now. his I thought was odd and that something had gone wrong.
So as most of us would do, I went to boot AmonRa recovery and it wasnt available, it had been overwritten with the default recovery; ok lets just ADB and reflash it, I hadnt used ADB for a couple of years because I did everything through AmonRa's awesome recovery!!
So off I go, install the SDK, all the appropriate packs including the USB driver, just like I did when I originally flashed the phone with the recovery image!
But an old problem came back that I hadnt even been bothered about because I always put stuff on SDcard via a card reader!!
I have had consistent problems with my nexus one for some time now in regards to the USB drivers, no matter what I do the phone will not install and I believe it could be some conflict in the device.
I am running Vista Ultimate (fully registered) and no matter what I do I cannot get the Nexus One to install. It will only display as unknown device, which is absolutely useless.
I have browsed every post and tried everything I have found, and yet nothing is working. I have used devmgmt, I have tried the roll backs, I have tried to install every driver available to get it working. I have uninstalled the device, updated drivers after fresh install attempts, I have even formatted my laptop thinking it may have had a corrupt OS and bought Vista Ultimate.
I am not a complete noob and I have been around these forums for some years, but I never thought I would have to cry out like a 4ucking Noob with such a seemingly simple problem, but it is not simple, I have done everything I can possibly find!!
I must get the USB working in order to get the recovery back, I can access my phones default recovery but it will not work when trying various roms as update.zip!!
I have tried the terminal commands on the phone to install the recovery.img but I do not have SU access and the phone point blank refuses.
I have attempted to change and remove the recovery files reffered that are causing the revert to default recovery, but shock.. I cannot delete because of insufficient permissions. I cannot ADB because the USB driver refuses to install.
So if I cannot change the files due to permissions, I cannot ADB because of USB, I cannot get to Ra's recovery because of bootfiles, I cannot use default recovery to update.zip... I am absolutely losing my mind and I'm going nuts browsing the forums for the second week running, yes I am now on day 12 of trying to fix this problem and at a complete loss...
Can someone please help??
I will even allow remote access to pc because I am that desperate to resurrect my beloved Nexus One.
I also have a Galaxy I9000 without 3 button download mode but that is an entirely different story!!
Please just someone, come to an oldskoolers rescue, and yes PAYMENT will be given to the knight in shiny armour!!
You could try on another computer which doesn't run Vista
tommert38 said:
You could try on another computer which doesn't run Vista
Click to expand...
Click to collapse
Or just use fastboot instead of adb...
His Nexus One isn't recognized by the computer, so that won't help unfortunately. Also, I've never heard of build GRK394..
tommert38 said:
His Nexus One isn't recognized by the computer, so that won't help unfortunately. Also, I've never heard of build GRK394..
Click to expand...
Click to collapse
Install the drivers for fastboot already Jeez and then read How to use android for dummies.
The Whole Story:
So yesterday I successfully upgraded my HTC One M7 to Lollipop for the first time. I was very excited because the UI is awesome. However, my cellular service didn't work. I read that this is because the firmware was out of date.
In trying to update said firmware, somehow I wiped the internal storage of my device (I know...) including my backup. But that doesn't really matter that much... because while using the HTC One Toolkit I also managed to idiotically turn S-ON! So I can't get into recovery anyway...
So I've been trying to get S-Off with firewater because if I can just get into recovery I can install an older backup I have from last year and then get a new ROM and try this circus all over again in a few weeks when my brain is hopefully not dumb. And that is where I've run into trouble with adb.
In the adb console I can see my phone's serial but it always is listed as offline. In fastboot, however, it is listed fine. I have tried so so many things, but at this point I'll try and re-try anything all over again just to get this to work.
Honestly, I'm surprised this thing isn't brIcked by now with all the f--k ups I've had in the past two days.
TL; DR: I royally messed up and accidentally turned S-On. Not sure if it is related, but now adb lists my HTC as offline while fastboot seems to recognize it fine. I can also access all my files on the phone from Windows.
One thing that (I think) is an important detail is that I cannot seem to get the RSA prompt to appear when I plug my phone into Windows with debugging mode on. I have never used this computer with this phone before, so I know it isn't saved or anything (maybe it's worth clearing the RSA keys anyway?).
What I've tried so far:
-Downloaded latest drivers from HTC (2.0.7.29 from 3/3/15)
-Installed Android Studio and updated Google USB Drivers and Platform Tools
-Rebooted Computer and Phone Multiple times
-Unplugged and re plugged USB cord
-Unchecked and rechecked USB debugging
Please...Please, I desperately need people who are better at this than I am.
Youngtusk said:
The Whole Story:
So yesterday I successfully upgraded my HTC One M7 to Lollipop for the first time. I was very excited because the UI is awesome. However, my cellular service didn't work. I read that this is because the firmware was out of date.
In trying to update said firmware, somehow I wiped the internal storage of my device (I know...) including my backup. But that doesn't really matter that much... because while using the HTC One Toolkit I also managed to idiotically turn S-ON! So I can't get into recovery anyway...
So I've been trying to get S-Off with firewater because if I can just get into recovery I can install an older backup I have from last year and then get a new ROM and try this circus all over again in a few weeks when my brain is hopefully not dumb. And that is where I've run into trouble with adb.
In the adb console I can see my phone's serial but it always is listed as offline. In fastboot, however, it is listed fine. I have tried so so many things, but at this point I'll try and re-try anything all over again just to get this to work.
Honestly, I'm surprised this thing isn't brIcked by now with all the f--k ups I've had in the past two days.
TL; DR: I royally messed up and accidentally turned S-On. Not sure if it is related, but now adb lists my HTC as offline while fastboot seems to recognize it fine. I can also access all my files on the phone from Windows.
One thing that (I think) is an important detail is that I cannot seem to get the RSA prompt to appear when I plug my phone into Windows with debugging mode on. I have never used this computer with this phone before, so I know it isn't saved or anything (maybe it's worth clearing the RSA keys anyway?).
What I've tried so far:
-Downloaded latest drivers from HTC (2.0.7.29 from 3/3/15)
-Installed Android Studio and updated Google USB Drivers and Platform Tools
-Rebooted Computer and Phone Multiple times
-Unplugged and re plugged USB cord
-Unchecked and rechecked USB debugging
Please...Please, I desperately need people who are better at this than I am.
Click to expand...
Click to collapse
maybe flashing the boot.img and stock recovery of the firmware you are into will help you!
eyeyousee said:
maybe flashing the boot.img and stock recovery of the firmware you are into will help you!
Click to expand...
Click to collapse
Thanks for the tip. Does flashing a boot.img and stock recovery require adb? Currently, that is where my main setback is.
If it doesn't require adb, can you point me into the direction of the right keywords to Google to find out how to do that?
well, as the title says. Its been like this for a few months now, so I decided reinstall the ROM. I've tried different ROMs and every time it shows up as SM-N900s (Galaxy Note 3) in windows. However, on the phone under settings, it says HTC One. On the newest insertcoin ROM it came up in windows as HTC ONE on first boot, but after that, it went back to being the SM-N900s. As well, I always make sure to do a full wipe before I install a new ROM. I checked the build.prop and it list the model ID as HTC ONE so I have no clue what could be going on here. maybe someone here has a suggestion? I'm thinking maybe this is a possible cause of my mediaserver problem that I just couldn't fix, since it happened in every rom I've tried. phone is rooted, unlocked, and S-OFF.
bbmaster123 said:
well, as the title says. Its been like this for a few months now, so I decided reinstall the ROM. I've tried different ROMs and every time it shows up as SM-N900s (Galaxy Note 3) in windows. However, on the phone under settings, it says HTC One. On the newest insertcoin ROM it came up in windows as HTC ONE on first boot, but after that, it went back to being the SM-N900s. As well, I always make sure to do a full wipe before I install a new ROM. I checked the build.prop and it list the model ID as HTC ONE so I have no clue what could be going on here. maybe someone here has a suggestion? I'm thinking maybe this is a possible cause of my mediaserver problem that I just couldn't fix, since it happened in every rom I've tried. phone is rooted, unlocked, and S-OFF.
Click to expand...
Click to collapse
Its most likely a driver issue on your computer, nothing to do with the phone imo. Uninstall these Samsung drivers and install HTC drivers.
didn't work. removed all traces of samsung drivers and software from the drive and the registry, but still comes up as SM-N900s. I Don't get it. There must be some root cause that's creating all the strange (though minor) issues on my phone.
@bbmaster123 install the latest HTC sync manager after uninstalling every older driver version.. do a full reset if that's possible. Do you end up having this problem with every custom Rom that you flash?
It's not a widely reported issue which leads me to thinking that it's more about your computer than your phone.
Still says sm-n900s after installing sync manager. While I haven't tried many custom roms, it still said smn900s in all the rims I've tried, regardless of kitkat or lollipop. I'll try using my brothers laptop tomorrow when he comes to visit and let you know how it goes
bbmaster123 said:
Still says sm-n900s after installing sync manager. While I haven't tried many custom roms, it still said smn900s in all the rims I've tried, regardless of kitkat or lollipop. I'll try using my brothers laptop tomorrow when he comes to visit and let you know how it goes
Click to expand...
Click to collapse
See question 2 here about how to force the HTC driver, this is a driver problem, the 2nd link below is another guy who recently had the same problem.
http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
http://forum.xda-developers.com/htc-one/help/hard-brick-how-fix-t3135013/page2 post 15 onwards.
Seanie280672 said:
See question 2 here about how to force the HTC driver, this is a driver problem, the 2nd link below is another guy who recently had the same problem.
http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
http://forum.xda-developers.com/htc-one/help/hard-brick-how-fix-t3135013/page2 post 15 onwards.
Click to expand...
Click to collapse
Thanks, I never would have found that!
My phone already comes up as My HTC in device manager when running normally. in any other mode it comes up as android composite usb. It does try and fail to install some driver during boot though, however it only lasts for about 3 seconds, so I have no time to install anything. as well, fastboot boot recovery.img never worked for me anyway, so instead I always just flashed my recoveries. So I can't get my computer to trigger that driver installer besides rebooting the phone, unless you know a way. But yeah, you may be right about it being my pc and not my phone (for this problem anyway).
bbmaster123 said:
Thanks, I never would have found that!
My phone already comes up as My HTC in device manager when running normally. in any other mode it comes up as android composite usb. It does try and fail to install some driver during boot though, however it only lasts for about 3 seconds, so I have no time to install anything. as well, fastboot boot recovery.img never worked for me anyway, so instead I always just flashed my recoveries. So I can't get my computer to trigger that driver installer besides rebooting the phone, unless you know a way. But yeah, you may be right about it being my pc and not my phone (for this problem anyway).
Click to expand...
Click to collapse
Ignore that HTC MTP driver thing that pops up on you computer whilst your phone is booting, we all get that.
fastboot boot recovery command no longer works unless you are on HBOOT 1.44 I think was the last time it worked, only way to do it now is to flash recovery files.
Seanie280672 said:
Ignore that HTC MTP driver thing that pops up on you computer whilst your phone is booting, we all get that.
fastboot boot recovery command no longer works unless you are on HBOOT 1.44 I think was the last time it worked, only way to do it now is to flash recovery files.
Click to expand...
Click to collapse
I don't think my phone even shipped with hboot 1.44. Or maybe it did. what the hell do I know. I guess then I'll have to wait until I can access my brother's pc later today to test it out
Well, turns out you were right all along. its my computer's fault. I guess I'll just have to mess around with the drivers. Thanks for the help! Too bad though, I was hoping that was the root cause of all the other annoying issues on my phone... oh well I guess I can live with unlocking my phone to change songs!
bbmaster123 said:
Well, turns out you were right all along. its my computer's fault. I guess I'll just have to mess around with the drivers. Thanks for the help! Too bad though, I was hoping that was the root cause of all the other annoying issues on my phone... oh well I guess I can live with unlocking my phone to change songs!
Click to expand...
Click to collapse
Get yourself into device manager and add/remove programs, and remove everything to do with your HTC, the trouble is, windows is a pain for still remembering and self installing the driver again upon reboot, so before you restart your computer, unplug your phone, restart your computer, and look up or get a driver cache cleaner for you PC, run that then restart again, now try reinstall the drivers, drivers firtst ie HTC Sync Manager and then plug your phone in.
I finally fixed it just by uninstalling HTC driver installer and plugging my phone back in. windows right away installed:
USB Composite device
HTC One
My HTC
usb mass storage device
HTC Sync manager serial interface
HTC Android Phone USB Device
I probably am going to fresh install windows anyway, been meaning to for a while, but at least I got this one solved. thanks for the help seanie!
I guess I should make new individual threads for my other phone problems, eh? I got the mediaserver battery drain issue, ACR doesn't record anymore for some reason, and the music controls on my lock screen stopped functioning.
bbmaster123 said:
I finally fixed it just by uninstalling HTC driver installer and plugging my phone back in. windows right away installed:
USB Composite device
HTC One
My HTC
usb mass storage device
HTC Sync manager serial interface
HTC Android Phone USB Device
I probably am going to fresh install windows anyway, been meaning to for a while, but at least I got this one solved. thanks for the help seanie!
I guess I should make new individual threads for my other phone problems, eh? I got the mediaserver battery drain issue, ACR doesn't record anymore for some reason, and the music controls on my lock screen stopped functioning.
Click to expand...
Click to collapse
I guess your on Lollipop, The media server issue can be sorted by going into settings - developer options - use NuPlayer (experimental), uncheck it and restart, not sure about the other issues, but it may be worth reflashing your rom and starting fresh.
As for re-installing Windows, prepare for Windows 10 or download the beta of it, when it goes RTM you can use your windows 7 or 8 key to activate it, and it totally rocks, ive been using it as my main driver now for 3 months.
I'm running kitkat (I like it better) and that option isn't under developer options. The only options I've changed under there are enabling usb debugging(but of course) and force gpu rendering. also using dalvik instead of ART, since in kitkat it was buggy, from what I've heard. I do want to also start a fresh install of the same rom, but I just haven't found the time. I did try reinstalling the rom and restoring my data with Titanium Backup, but it just ended up restoring the problem too. For now, I've just been using system tuner to kill mediaserver right after boot, and the problem goes away until next boot.
I have windows 10 build 10130 on another drive and have been testing it since the first TP, and I agree, its pretty sweet, but I'm not 100% sure yet that I'm gonna switch over to it as my main OS on my main PC. I will be definitely updating my windows 8.1 recording computer to Windows 10 as soon as it goes RTM.
bbmaster123 said:
I'm running kitkat (I like it better) and that option isn't under developer options. The only options I've changed under there are enabling usb debugging(but of course) and force gpu rendering. also using dalvik instead of ART, since in kitkat it was buggy, from what I've heard. I do want to also start a fresh install of the same rom, but I just haven't found the time.
I have windows 10 build 10130 on another drive and have been testing it since the first TP, and I agree, its pretty sweet, but I'm not 100% sure yet that I'm gonna switch over to it as my main OS on my main PC. I will be definitely updating my windows 8.1 recording computer to Windows 10 as soon as it goes RTM.
Click to expand...
Click to collapse
Not heard of the media server bug on KitKat soz.
Still don't like the Windows 10 start menu live tiles, but Start10 fixes that.
I've been using classic start, but I always have to keep switching back to the stock start to launch modern apps, which I only barely use, just stuff like calculator and settings
bbmaster123 said:
I've been using classic start, but I always have to keep switching back to the stock start to launch modern apps, which I only barely use, just stuff like calculator and settings
Click to expand...
Click to collapse
bit off topic really, but see the picts below:
cool, then I'll have to give it a try. Much more like the win7 start menu than win10's stock menu.
I know this is not really what this website is designed for but I could really do with your help as the Pros!
Okay, so I wiped my HTC One M7 because I wanted to put a different custom ROM on there, no big deal, done it a 100 times right? Well I guess I must have done it wrong this time (Maybe I ticked too many boxes?) because this time it completely formatted my phone, I mean, including the TWRP back up restore points and all the ROM zips I had in their own little folders on my internal SD card. Anyway, no big deal I just plug it into the same computer I always use (this was actually the 3rd time I had wiped and put a new ROM on today as I am just trying new ones :good: so I know the PC is fine) and it comes up with "Installing driver" but instead if it being called "HTC One M7" or whatever it usually says it just says "Android". At this point I am starting to panic a tiny bit... Anyway after about 3 min it fails and "Android" has changed to "htc MTP Device" and I cant get on to it put a ROM on there to give it a OS.
So! Troubleshoot mode activate!!!!! I start Googling, try a few different solutions, couple of Cab file installs and the like but nothing! So I un-install everything HTC related: the HTC Sync Manager and the HTC Driver Manger and even the APKs I had... Everything! An then unplug my phone and start installing them again, plug in the phone and..... NOTHING!! Exact same thing happens. I even tried using a different computer, then installed all the HTC driver stuff on it and it still didn't work. So I start to cry a little bit but then I remembered something I did for a few Salesmen that worked for the company I work for a few years ago! They wanted to get data off a USB stick and onto their Samsung tablets, I bought them a USB Female to Samsung port and it saw it as another data drive, will I have to do that with a USB Female to OEM cable? Will that even work? As it is still sorta seen as a HTC so at least it knows what it is, I refuse to think that it is done for!... Is it?
TheAnarchyRule said:
I know this is not really what this website is designed for but I could really do with your help as the Pros!
Okay, so I wiped my HTC One M7 because I wanted to put a different custom ROM on there, no big deal, done it a 100 times right? Well I guess I must have done it wrong this time (Maybe I ticked too many boxes?) because this time it completely formatted my phone, I mean, including the TWRP back up restore points and all the ROM zips I had in their own little folders on my internal SD card. Anyway, no big deal I just plug it into the same computer I always use (this was actually the 3rd time I had wiped and put a new ROM on today as I am just trying new ones :good: so I know the PC is fine) and it comes up with "Installing driver" but instead if it being called "HTC One M7" or whatever it usually says it just says "Android". At this point I am starting to panic a tiny bit... Anyway after about 3 min it fails and "Android" has changed to "htc MTP Device" and I cant get on to it put a ROM on there to give it a OS.
So! Troubleshoot mode activate!!!!! I start Googling, try a few different solutions, couple of Cab file installs and the like but nothing! So I un-install everything HTC related: the HTC Sync Manager and the HTC Driver Manger and even the APKs I had... Everything! An then unplug my phone and start installing them again, plug in the phone and..... NOTHING!! Exact same thing happens. I even tried using a different computer, then installed all the HTC driver stuff on it and it still didn't work. So I start to cry a little bit but then I remembered something I did for a few Salesmen that worked for the company I work for a few years ago! They wanted to get data off a USB stick and onto their Samsung tablets, I bought them a USB Female to Samsung port and it saw it as another data drive, will I have to do that with a USB Female to OEM cable? Will that even work? As it is still sorta seen as a HTC so at least it knows what it is, I refuse to think that it is done for!... Is it?
Click to expand...
Click to collapse
looks like a driver issue. uninstall everything and install HTC drivers manually. See FAQ #2 of nkk71's guide (linked in my signature). Once your drivers are fixed, flash latest twrp version 2.8.6.0 (assuming you have the M7 GSM). Boot in twrp 2.8.6.0 main menu, you'll be able to see your phone storage from your computer like if it was a usb stick. Drag and drop your rom.zip or your nandroid backup and flash it or restore it (as applicable).
alray said:
looks like a driver issue. uninstall everything and install HTC drivers manually. See FAQ #2 of nkk71's guide (linked in my signature). Once your drivers are fixed, flash latest twrp version 2.8.6.0 (assuming you have the M7 GSM). Boot in twrp 2.8.6.0 main menu, you'll be able to see your phone storage from your computer like if it was a usb stick. Drag and drop your rom.zip or your nandroid backup and flash it or restore it (as applicable).
Click to expand...
Click to collapse
Thanks for getting back to me, I tried that but I cant install the driver manually either, it comes up with the attached error.
TheAnarchyRule said:
Thanks for getting back to me, I tried that but I cant install the driver manually either, it comes up with the attached error.
Click to expand...
Click to collapse
Okay I have fixed it!!!! I had to plug it in at the TWRP stage and then I had to change its driver setting to a "General USB Storage Device" then it activated and renamed itself to "One" and dropped down into the USB Controllers menu. Now I can browse it and put a ROM on it!
Thanks for your help!