Related
I need to return my phone because the earphone speaker is whacked out but I have spent the last couple hours trying to unroot it and NOTHING is working...
First I tried HTC Sync on my computer, and I get the Error [171]: USB Connecetion Error
Then I tried HTC sync on my bros computer (since I have unrooted using his laptop before with no problems) and I get a different error saying something about i have the wrong version of data utility updater or whatever.
I spent the last couple hours googleing both errors and looking for fixes, but for some reason I could not get any of them to work. I am as frustrated as can be rite now, and any help would be greatly appreciated....
I'd prefer some sort of "dumbed down" step by step process rather than being sent to a another link, because chances are I have tried that method already and I couldn't get it to work...
I also can not get adb shell to work. I installed the sdk, but it still wont show up...
any help from anybody will be greatly appreciated...
try applying the current over the air update. That took root away for many if I remember correctly.
did you enable USB debuging?
I tried searching for the ota's but they're not showing up.
also I am running dc 3.2 currently, which has debugging mode auto-enabled I believe.
So you tried using a stock rom from here to get your phone unrooted?
If you download one of those stock RUU roms it will be an exe file that will automatically install the rom to your phone...is this what you are saying isn't working?
Have you tried doing a full wipe/clear before running anything?
I had the same error when I was unrooting mine. I just unplugged the Evo while it still had the boot loader screen then ran the stock RUU. Worked like a charm.
yes. I tried installing the shipped RUU using HTC Sync, but sync keeps ****ting out on me and giving me errors. My only option seems to be unrooting my phone without using htc sync. But I have tried a couple of the methods e found, but none of them had detailed enough instructions for me to make them work....
I'v literally spent the majority of my day trying to unroot this damn phone and its driving me crazy.... I don't know wth the problem is.. I unrooted a previous EVO before, now it seems hopeless /:
Comrade P said:
I had the same error when I was unrooting mine. I just unplugged the Evo while it still had the boot loader screen then ran the stock RUU. Worked like a charm.
Click to expand...
Click to collapse
what do you mean?
I GOT IT
Hang tight fellow XDAers. Tutorial coming in about 20 min. I will post link in this thread when done. Took me forever to get past those errors too....
do the over the air update that is freshly released it will remove root and nand
Bang3r said:
Hang tight fellow XDAers. Tutorial coming in about 20 min. I will post link in this thread when done. Took me forever to get past those errors too....
Click to expand...
Click to collapse
In for this
starplaya93 said:
I need to return my phone because the earphone speaker is whacked out but I have spent the last couple hours trying to unroot it and NOTHING is working...
First I tried HTC Sync on my computer, and I get the Error [171]: USB Connecetion Error
Then I tried HTC sync on my bros computer (since I have unrooted using his laptop before with no problems) and I get a different error saying something about i have the wrong version of data utility updater or whatever.
I spent the last couple hours googleing both errors and looking for fixes, but for some reason I could not get any of them to work. I am as frustrated as can be rite now, and any help would be greatly appreciated....
I'd prefer some sort of "dumbed down" step by step process rather than being sent to a another link, because chances are I have tried that method already and I couldn't get it to work...
I also can not get adb shell to work. I installed the sdk, but it still wont show up...
any help from anybody will be greatly appreciated...
Click to expand...
Click to collapse
Link to my tutorial (you will need adb though): http://ip208-100-42-21.static.xda-developers.com/showthread.php?p=7471721#post7471721
I'd find you the link but I'm at work right now but someone has a fix for that error. Basically I got that error whenever I tried to run the stock RUU and when the phone had the bootloader screen up I just took out the USB cable, stuck it back in, and then ran the RUU again.
Sent from my EVO using the XDA App
Bang3r said:
Hang tight fellow XDAers. Tutorial coming in about 20 min. I will post link in this thread when done. Took me forever to get past those errors too....
Click to expand...
Click to collapse
You have no idea how much i'm looking forward to your guide. If it works then you my friend deserve a metal.
starplaya93 said:
You have no idea how much i'm looking forward to your guide. If it works then you my friend deserve a metal.
Click to expand...
Click to collapse
It's up: http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=743192
This works if you're rooted and NAND unlocked.
http://forum.xda-developers.com/showthread.php?t=715915
cosine83 said:
This works if you're rooted and NAND unlocked.
http://forum.xda-developers.com/showthread.php?t=715915
Click to expand...
Click to collapse
Well...I guess I missed that one when I was tooling around, so I wrote my own. You're right. It clearly mentions needing the proper HBOOT, which I found was the key.. But it doesn't mention how to UN ROOT after you "Start Over." It's basically the same thing though...Cheers...
http://forum.androidcentral.com/htc-evo-4g-roms-hacks/19278-how-unroot-return-stock.html
Bang3r said:
Well...I guess I missed that one when I was tooling around, so I wrote my own. You're right. It clearly mentions needing the proper HBOOT, which I found was the key.. But it doesn't mention how to UN ROOT after you "Start Over." It's basically the same thing though...Cheers...
Click to expand...
Click to collapse
When I place the PC zip file on my sd card and then boot into Hboot, it fails to recognize the card.
I used simple root to root my phone and I am running the .79 Hboot.
I'm trying to follow your instructions but I am about ready to throw this god dam phone at the wall and use insurance to get another one
starplaya93 said:
When I place the PC zip file on my sd card and then boot into Hboot, it fails to recognize the card.
I used simple root to root my phone and I am running the .79 Hboot.
I'm trying to follow your instructions but I am about ready to throw this god dam phone at the wall and use insurance to get another one
Click to expand...
Click to collapse
You have the wrong H Boot. See here: http://ip208-100-42-21.static.xda-developers.com/showthread.php?p=7471721#post7471721
Should work on any .79 HBOOT in theory, but you have to change it to the .76 one before the RUU or the zip step you are having trouble with. Do Toast's step two which is found in the thread linked above.
Hey
So I tried to root my SGN using Chainfires' thread, my phone got unlocked but I couldn't boot it so I got stuck with a black screen with the Google logo and an unlocked lock-logo. Now I have unrooted it and reset it back to stock using droid-life.coms' "How to", but when I try to boot now I only get the balck screen with Google-logo, and no lock-logo.
Do anyone know how I can fix this? Thanks for the help!
When I try to unroot, re-lock and set to factory state I get an error, probably because my driver isn't working, the 'SAMSUNG Mobile MTP Device'..
I tried the PDANet drivers, Samsungs' drivers and yeah.. I also downloaded the "Naked drivers" wich I found on another thread on XDA.
I really need help
How far into rooting it did you get? A link to the instructions you followed, and a detailed account of what happened and what you saw will help someone else help you.
as far as drivers go, if you installed a bunch drivers from different sources, uninstall them all, reboot, install the drivers from Samsung. Also remember that when you plug your phone in and the drivers start to autoinstall, that process can take awhile and you have to be sure it completed before trying to continue. It should show a status you can open in the system tray
Galaxy Nexus Bugless Beast 4.0.3 cdma
Also, be sure to scour all the sticky posts in these galaxy nexus forums, and also all the replies in the thread you were following. Chances are someone has explained an 'all else has failed blow it away' recovery step by step. Follow it closely!
Galaxy Nexus Bugless Beast 4.0.3 cdma
eovi said:
When I try to unroot, re-lock and set to factory state I get an error, probably because my driver isn't working, the 'SAMSUNG Mobile MTP Device'..
I tried the PDANet drivers, Samsungs' drivers and yeah.. I also downloaded the "Naked drivers" wich I found on another thread on XDA.
I really need help
Click to expand...
Click to collapse
Have you tried downloading the Google USB Driver package from Android SDK? Its under Extras. If my memory serves me right, our phones actually require two drivers (one for adb and fastboot modes, and one for normal operation). Also, when you are restoring your phone are you sure its the right version? Like you're not installing an LTE ROM on a GSM device?
Sent from my Galaxy Nexus using xda premium
@cancerouspete
I got the rooting all done until the phone was going to boot, then I got stuck at the black screen with the Google-logo. Unfortunately I can't post links, but I used Chainfires' ODIN method.
I can try to uninstall the drivers and only try Samsung drivers.
@nbeebe24
Yes, I downloaded the Android SDK drivers before I started the rooting. I am not 100% sure that it is the right version. I got the GSM, do you have a nice guide or 'How To' for restoring GSM?
Thanks for the help so far!
Let's take it form the beginning. First I followed the steps in Chainfires' thread about CF-Root for SGN (Galaxy Nexus). I used the ODIN-way to flash my phone. I followed the instructions to the letter and when I tried to boot the phone I only got a black screen with a white Google-logo in the middle and an unlocked lock-logo. Nothing else happens than this. My phone is GSM-version and is bought in Norway. One of the issues is that I'm not 100% sure of what build-number my phone is.. anyone know how I can find this out?
When I tried to fix this problem myself I tried to unroot, lock and reset the phone, and then unlock/root again with another version, the same happend (with the black screen and google logo + lock-logo). It doesn't work to unroot, lock and reset, if I do this I only get a balck screen with google-logo, but no lock-logo
I really hope someone can help me with this problem! All help and tips is appreciated!
Fixed!
I've finally fixed this problem. Can tell you how I fixed it if someone else need help.
I uninstalled the PDANet drivers, Samsung drivers and uninstalled the SDK-drivers. Then I reinnstalled the SDK driver and followed this to restore the phone to stock:
http://forum.xda-developers.com/showthread.php?t=1366806
So I guess the problem was that I used the wrong version or for another build when I CF-Rooted. I have ITL41D build.
Thanks for the help and I hope this can help other with the same issue!
Love my GNex, it's a beast! Upgraded from a SGS, this was a beast when it first came out but the electronic power are growing fast! Go Samsung and Google! Love ICS
Like the title says, I can not seem to root my phone. I have read just about every guide on the forum and have reinstalled my windows LG drivers multiple times, but nothing bears fruit. Every time it says something around "fail to copy," or "permission denied," things of that sort. Maybe I haven't installed something as it's my first time trying to root. Any help on this problem would be much appreciated.
PS, I'm on ICS 4.0.4, in case that matters.
Clueless One said:
Like the title says, I can not seem to root my phone. I have read just about every guide on the forum and have reinstalled my windows LG drivers multiple times, but nothing bears fruit. Every time it says something around "fail to copy," or "permission denied," things of that sort. Maybe I haven't installed something as it's my first time trying to root. Any help on this problem would be much appreciated.
PS, I'm on ICS 4.0.4, in case that matters.
Click to expand...
Click to collapse
I'm pretty new to all this too, and I used Hereric's unbricking guide:
http://forum.xda-developers.com/showthread.php?t=2044645
I got through it successfully in one try. It should work if you use only the files included in the zip file and follow the instructions carefully.
Try it out again if you already have, and if you have any problems post 'em in this thread and I'll try to help.
Good luck!
On the TSSparkyRoot step, is the command prompt suppose to say "fail to copy....permission denied?"
Clueless One said:
On the TSSparkyRoot step, is the command prompt suppose to say "fail to copy....permission denied?"
Click to expand...
Click to collapse
No. Make sure you are logged into Windows with Administrator priveleges to avoid any potential permissions problems.
Fuzzypumper said:
No. Make sure you are logged into Windows with Administrator priveleges to avoid any potential permissions problems.
Click to expand...
Click to collapse
Got it to work, it turned out that I was just too excited when it said "Press any key to continue" and I pressed too quickly. Therefore, making the commands go into to my phone while it was rebooting... Thanks for the help.
Hi there
I've in the past, rooted some of my android phones. Just got the HTC one M8 and it updated to 5.0.
I would like to get root access (not planning on flashing a new rom). I'd like to get OTA still.
I followed step by step instructions on how to root, but when I go to SU, I get an error message:
"There is no SU binary installed, and SuperSU cannot install it. This is a problem!
If you just upgraded to Android 5.0, you need to manually re-root - consult the relevant forums for your device!"
Also, my touchscreen / keyboard seems messed up. It starts typing random stuff on it's own I think I might have damaged my phone by keep trying to do it.
I'm a noob and try to usually follow step by step instructions.
Please help - and in basic terms, please
Thanks!
Update
I reset my phone, and now it is rooted and works. Problem is that the screen is still messed up It doesn't type what I want and closes typing screen, opens other windows etc What should I do?
Does the glitchy behavior only happens when you're charging the phone?
My phone has now updated all its apps and the screen is working fine again, but I get the same message again as previously. SuperSU message: There is no SU binary installed, ......".
Seems it worked only until it updated.
Would love to get it rooted. Help would be appreciated please.
TheMabaet said:
Does the glitchy behavior only happens when you're charging the phone?
Click to expand...
Click to collapse
You're right. It was happening while charging. My phone was still linked to the laptop. So that could be it.
Hello everyone. I am stuck in a bit of a draining situation. and I really hope that some of you, may be able to help.
I have 3 kids with each their phone, all of them have been registered to Googles Family Link service. Recently the account that managed them all got suspended for being hijacked and therefor it broke their terms, and now 4 accounts are locked. Google will not help me, to release the accounts the kids have, so they can use their phones again. So I tried following a guide on bypassing the log in prompt after a factory reset on this specific device. It happily activated the tap talk function, but when I try to open Google Assistant, nothing happens. I've tried looking it the settings of Tap Talk to find any clues, but to no avail.
I have searched for different variations of the same procedure on Youtube and Google and I can't seem to get further than described..
I then decided to try unlocking the bootloader or re-flashing the stock firmware, hoping to wipe the existing system completely. The re-flashing part, well. I found the Asus Zenfone Flash tool, but I am not too sure what to do. The guide seemed a bit confusing to me, so I tried the Bootloader, since I used to flash and root all my phones back when HTC was big. I have installed Quallcomms drivers, Asus-android_USB drivers, generic Android Usb drivers and restarted the pc to make sure that was done right.
The phone however is another problem. I haven't been able to enable usb-debugging thanks to Family Link preventing access to Dev-mode, before I did the Factory reset. I can read the phone's name on the ADB update option, when I boot it to stock recovery. But any commands, makes it hang with "waiting for any device", which, from what I understand, is a driver related issue. So I have updated the drivers as each guide has descibed.
My plan was to install the latest Lineage Rom, so I have the most recent files for that.
So now I ask you. I have downloaded Rom files, Gapps, 2 types of recovery img files, but for now, I am stuck and sad and I need a Yoda in this matter. The entire situation is probably solved with a simple click or command that I am not aware of.
If you need any further info I will do my best to help. My kindest and biggest thanks to anyone that provide some help.
Kind regards
Johnny