Related
I'm not sure if I'm posting this in the right section, this is my first question. So I decided to finally root my nexus one, mostly to take advantage of the newly integrated wi-fi calling feature in the new cyanmod. i was able to unlock it through fastboot, it now shows the lock when the phone boots up, but it doesnt appear to be unlocked. apps requiring root like rom manager, setcpu, etc. don't seem to be detecting that the phone is rooted. when i first open rom manager i get the message "you must root your phone for rom manager to function. superuser wasnot found at "/system/bim/su" or "/system/xbin/su". use google search on your computerto find instructions on how to root your phone." then when i select to flash a rom it says "an error occurred while attemping to run privileged commands". i tried uninstalling and reinstalling rom manager, rebooting, etc.. no luck. i've been searching threads for hours. please help!
You haven't rooted your phone.
Unlocking the bootloader just allows you to install unofficial images. You can now install a rooted image, to save yourself the trouble of having to root one.
First thing you probably want to do is install a custom recovery, which can then be used to make backups and install custom ROMs, etc.
Go find a custom recovery (look in the wiki), and install via fastboot. Stay away from Clockwork 3.xx...
Sent from my Nexus One using XDA App
mm installing a recovery will not root the phone either...
You need to root the phone (superoneclick works well)
http://forum.xda-developers.com/showthread.php?t=803682
If the bootloader is unlocked, you don't need to root the current ROM, unless you plan on keeping it, which the OP obviously doesn't (because why else would anyone download ROM Manager?)...
With an unlocked bootloader you can just flash any system image you want. You probably still want a custom recovery though, so you might as well flash recovery first, and then use that to flash ROMs...
Sent from my Nexus One using XDA App
danger-rat said:
Stay away from Clockwork 3.xx...
Click to expand...
Click to collapse
thought it was okkay if you are directly flashing 3.something and not upgrading it from a previous release?
Amon RA is the best though...
Sent from my Nexus One
I don't run any roms just root. I received the OTA update lastnite and without thinking, I allowed it to update. I usually use SuperOneClick but that doesn't seem to work with this update. I have searched high and low and can't find any information on rooting this. Any help is appreciated.
SOLVED. I reverted to SuperOneClick 1.7 and used rageagainstthemachine and it worked after a reboot. zergRush in 2.2 doesn't seem to work against this update.
SuperOneClick 2.2.2 Will Work With FRK76 if...
I took the rageagainstthecage exploit file from SuperOneClick 1.7 and placed it in the "Exploits" sub-directory of SuperOneClick 2.2.2 and it worked as well after a reboot. Note: You'll get a warning message about it's incompatibility with Android 2.3 + (not an issue as FRK76 is 2.2.3)
Don't know what the above means
Does 2.3.1 work without modification?
While I still have my 2 year old droid, I don't have my windows computer any more. Is there any way to do this with a Mac?
Noob needing help
sir_lunatic said:
I don't run any roms just root. I received the OTA update lastnite and without thinking, I allowed it to update. I usually use SuperOneClick but that doesn't seem to work with this update. I have searched high and low and can't find any information on rooting this. Any help is appreciated.
Click to expand...
Click to collapse
Good day, I've scoured the xda dev & android forums, and haven't been able to come up with a resolution to this: I let the OTA [FRK76 - 2.2.3] update slip through, and now i'm having issues rooting.
Besides the fact i'm running linux, i refuse to use any of the one click methods.. Would rather root manually so i know what's happening.
I'm running Ubuntu & doing this all through ADB / terminal, following the instructions listed in android forums [Rooting the Droid without rsd lite up to and including FRG83D], i get to step 13 and i still see the $ & not #.
As there anyone out there who can assist?
Thanks much in advance!
sir_lunatic said:
SOLVED. I reverted to SuperOneClick 1.7 and used rageagainstthemachine and it worked after a reboot. zergRush in 2.2 doesn't seem to work against this update.
Click to expand...
Click to collapse
how does one get an older version of SuperOneClick 1.7?
envoy510 said:
Does 2.3.1 work without modification?
Click to expand...
Click to collapse
As per i know it does not.
Pete has a stock rooted FRK76 Rom on his website, fyi
My D1 seems remarkably resistant to rooting. I downloaded SOC 2.3.3, added rageagainstthecage to the exploits folder, and it still won't even really get to the "Waiting for Device" command. It kills/boots the ADB daemon then hangs. If I kill one of the ADB processes manually, I can get it to skip the automatic version check and get to "Waiting for Device" but then nothing happens there, either.
Any help (or hell, an alternate rooting method- I'd do it the long way too) would be great.
flukehawkins said:
My D1 seems remarkably resistant to rooting. I downloaded SOC 2.3.3, added rageagainstthecage to the exploits folder, and it still won't even really get to the "Waiting for Device" command. It kills/boots the ADB daemon then hangs. If I kill one of the ADB processes manually, I can get it to skip the automatic version check and get to "Waiting for Device" but then nothing happens there, either.
Any help (or hell, an alternate rooting method- I'd do it the long way too) would be great.
Click to expand...
Click to collapse
The rageagainstthecage exploit works for the FRK76 build, but I couldn't get SuperOneClick to run without crashing, so I just did it manually.
Download SuperOneClick 1.7
Extract, and use the rageagainstthecage, busybox, su, Superuser.apk with this guide: http://forum.xda-developers.com/showpost.php?p=8315805&postcount=2
The only difference is the block device /system is mounted from (the guide says mtdblock3, and I think on the droid it is mtdblock4). Just type `mount` on the command line and look for the line that has /system and check the mount path.
I used superoneclick 1.7 to root a stock frk76.
On a note to new users...if you are on windows 7, I could not get it to work. I had an old xp machine that I downloaded soc1.7 to, when I first tried to run it, my PC posted an error about .net 2.0 framework. I Google, found, and downloaded the net 2 0 framework and it worked instantly.
It did not give me recovery. I used rsdlite and only rsd recovery after I rooted it to install cwm. Once you install cwm go directly to it and flash your new rom.
For me, after I rooted and had a stock rom, my recovery would not survive a reboot. But after moving cm7 and gapps to my SD card, re-rsd recovery. Booted directly to recovery. Flashed. Once booted I went to rom manager and had it reflash cwm recovery again and it never had another issue.
My steps may sound confusing but this is what I did.
I do not have sdk setup completely on my laptop and found this to be extremely easy. It works 100% and supplied no errors. I hope this helps someone else.
Is there a RUU i can run to unroot my phone?
YoungCorruptionV2.0 said:
Is there a RUU i can run to unroot my phone?
Click to expand...
Click to collapse
No ruu on here but you can simply flash an unrooted stock rom and accept updates thru Verizon.
stkiswr said:
No ruu on here but you can simply flash an unrooted stock rom and accept updates thru Verizon.
Click to expand...
Click to collapse
Ah okay thanks for the tip. I'll look in the development section for one
YoungCorruptionV2.0 said:
Ah okay thanks for the tip. I'll look in the development section for one
Click to expand...
Click to collapse
You may be able to find it on rom manager but def can find it on peter Alfonso site
i have previously unlocked bootloader and rooted my device using the Hasoons all in one tool kit and then had been using ard 12.1.
I then fancied trying the latest GE 4.3 release (stock) which i downloaded and flashed and all seemed fine however when i went to check root was still there i have the icon but get a message saying that there is no su binary installed. I have tried to use the toolkit again to go back the root procedure in the hope i can re-install what ever is missing however for some reason now the tool kit comes up with an error message in the box saying waiting for device or device not recognized.
I have tried to sort the problem but now feel i am just going round and around in circles and really dont have the knowledge to put it right as im quite new to the flashing and modding side and dont fully understand all the terminology, im sure its probably something really simple to fix for those who know how so would really appreciate some advice.
My overall aim would be to be running the stock rom (or might even try the new arhd 4.3 ge) with root so that i can then use the volume + to wake mod as i find this really usefull as my power button is quite depressed and hard to use.
hpsauce37 said:
i have previously unlocked bootloader and rooted my device using the Hasoons all in one tool kit and then had been using ard 12.1.
I then fancied trying the latest GE 4.3 release (stock) which i downloaded and flashed and all seemed fine however when i went to check root was still there i have the icon but get a message saying that there is no su binary installed. I have tried to use the toolkit again to go back the root procedure in the hope i can re-install what ever is missing however for some reason now the tool kit comes up with an error message in the box saying waiting for device or device not recognized.
I have tried to sort the problem but now feel i am just going round and around in circles and really dont have the knowledge to put it right as im quite new to the flashing and modding side and dont fully understand all the terminology, im sure its probably something really simple to fix for those who know how so would really appreciate some advice.
My overall aim would be to be running the stock rom (or might even try the new arhd 4.3 ge) with root so that i can then use the volume + to wake mod as i find this really usefull as my power button is quite depressed and hard to use.
Click to expand...
Click to collapse
hello you are in need of the new 4.3 superuser.zip
http://download.clockworkmod.com/test/superuser-4.3-beta3.zip
if you are using CWM, when it asks to fix su upon reboot, select NO
Wow thank you!!!!!
You have no clue, or maybe you do, how lost I got trying to root my HTC One. This is all new to me, but this forum has helped massively. I found that the supersu zip I had was the older version when I already had 4.3 uploaded before rooting. This community rocks!
why do my gapps processes keep crashing?
NM forgot to full wipe
So I have the same issue - my only question is that I am running 4.4 now. Does this super user file still work or is there a 4.4 version?
Just use "SuperSu" if you face any root acces issues
Sent from my loved HTC One S using (most time buggy) Tapatalk
HHEELLPPP
Hi there, Im new to the rooting world, I have a htc one m7 from sprint trying to sim unlock it, as far as I know I unlocked the bootloader, tampered it, and rooted, but no access to super user so I can sim unlock it. I downloaded and installed this App that you mention, but still keeps saying no binary updated, and with this 4.3 version says there was an error installing superuser. Please help, I dont know what to do.
I was having this same issue on my Note 2 (4.3). I seem to have found a way to restore root that may help you as well.
I think this issue may be caused by the SU app & binary updates. Uninstalling the updates has restored root for me.
Go to:
Settings > More > Application Manager > All > SuperSU > Uninstall updates
(menu options may be slightly different on other devices)
This will roll back SuperSU and hopefully restore your root access.
Let me know if this helps.
Any updates on this? I'm trying to get root on an HTC One M7 that I just purchased and I'm running into the same error.
Thanks!
I tried to unlock my bootloader, following various guides, and kept getting stuck on the "Download Mode !!!" part. I just want to install the latest stable version of Cyanogenmod on my phone since the stock ROM is being a real pain for me (very slow and unresponsive).
I have:
Android 4.1.2
Build Number: JZ054K
Software Version: AME-XXX
I read online that you need the Euro firmware to unlock the bootloader, can I flash the euro firmware and will it mess with my service? I'm confused as to how the firmware affects things since I've read conflicting information. I didn't flash my firmware a few hours before trying to unlock, so maybe that's the problem?
Seriously?
There aren't enough threads and guides for you to read already? Everything you need is already out there on this forum so why start another thread just because you are too lazy to search and read for yourself?
I have read around and have tried a number of guides a number of times. They haven't worked for me and I'm just wondering what i'm doing wrong. Even though all the information is out there, I don't have the experience to understand it apparently. I've spent hours trying to figure things out but i keep reading conflicting info and half-explained steps and now I'm just confused and would like a clear point in the right direction.
So, do i need to reflash the latest firmware, wait a few hours, then try again on a full charge? Or do i need a euro firmware? Which guide should i follow?
I've downloaded a few applications and driver packages and whatnot but if those could possibly conflict with each other and cause problems i could work with a fresh OS. I'm running OS X but i have linux VMs and friends with clean windows installs (mine is all sorts of messed up)
eatfoodnow said:
I tried to unlock my bootloader, following various guides, and kept getting stuck on the "Download Mode !!!" part. I just want to install the latest stable version of Cyanogenmod on my phone since the stock ROM is being a real pain for me (very slow and unresponsive).
I have:
Android 4.1.2
Build Number: JZ054K
Software Version: AME-XXX
I read online that you need the Euro firmware to unlock the bootloader, can I flash the euro firmware and will it mess with my service? I'm confused as to how the firmware affects things since I've read conflicting information. I didn't flash my firmware a few hours before trying to unlock, so maybe that's the problem?
Click to expand...
Click to collapse
It isn't a question of firmware, the phone needs to have an unlockable bootloader to be able to be, well, unlocked. Here is a list http://forum.xda-developers.com/showthread.php?t=2181581 of P880 bootloader versions. Follow the guide to check which BL your phone has.
Thats obsolete, all versions can be unlocked afaik, either with official method or by fuse editing. No need to keep sim card in,you just need proper drivers
Oh, OK, I didn't know that. But, even better, OP should not have any trouble, provided he follows the BL unlock guide here http://forum.xda-developers.com/showthread.php?t=2224020
Maybe his BL is already unlocked OR is relocked (meaning can't be unlocked anymore).
Its more likely that his drivers are messed up imo.
The fuse editing method should work for everyone, i recommend you give it a try
So the fuse method would be the "BL-unlock.bat" method on that bootloader unlock forum post? I've tried it before, but I'll try it again. The directions only say to run it, is there anything else I need? Now, since it's a .bat file I absolutely have to run it on Windows, right? Because if so I'll use a friend's computer instead of my windows installation.
What are the necessary installations before I run the file? How should I configure settings on my phone? (like what type of usb connection should it be)
There are a lot of things that people expect readers to know but I'm really not very knowledgeable about standard practices for phone stuff so I really need every step. Thanks for helping!
Since its.bat file, you can open it in text editor to see which commands it executes. I'd still recommend to do it on windows machine, other OSs may work but aren't tested.
You need abd & fastboot drivers, plus drivers for our device. It's been a while since I've done it, but afaik you can get proper device drivers via lg support tool.
Flying_Bear said:
Since its.bat file, you can open it in text editor to see which commands it executes. I'd still recommend to do it on windows machine, other OSs may work but aren't tested.
You need abd & fastboot drivers, plus drivers for our device. It's been a while since I've done it, but afaik you can get proper device drivers via lg support tool.
Click to expand...
Click to collapse
Also, correct me if i'm wrong I only had stock for 2hours, but also stock needs usb debugging to be enabled or adb won't work?
Yep, afaik usb debugging needs to be enabled
When you are fast enough, it is possible in charging mode wihle the carger animation is shown. But you have install adb driver very fast...
So I'm pretty sure I got the bootloader unlocked, I ran the .bat file and it went through everything until the part where it checks to see if my bootloader is unlocked, it just froze forever, so I closed it.
How should I go about checking?
Also, what would be my next step now for installing CM10.1.3? I tried to follow the guide on the cyanogenmod wiki (install_CM_for_p880) (I can't post links yet)
...but ran into problems with pushing it into root with adb. It said I didn't have permissions, so I googled some stuff, but just got myself confused.
Thanks for all the help btw!
eatfoodnow said:
So I'm pretty sure I got the bootloader unlocked, I ran the .bat file and it went through everything until the part where it checks to see if my bootloader is unlocked, it just froze forever, so I closed it.
How should I go about checking?
Also, what would be my next step now for installing CM10.1.3? I tried to follow the guide on the cyanogenmod wiki (install_CM_for_p880) (I can't post links yet)
...but ran into problems with pushing it into root with adb. It said I didn't have permissions, so I googled some stuff, but just got myself confused.
Thanks for all the help btw!
Click to expand...
Click to collapse
you can check your bl status by entering sw mode (phone off, hold vol+ and insert charger) or reeboting into bl (adb reboot oem-unlock)
to install cm steps are:
-install recovery (you can choose either cwm or twrp, it's more about looks than functions)
-download rom zip onto sd card
-install said zip from said recovery, there's no adb involved
Now my personal opinion, I really don't see the point in flashing 10.1, i would go staright for cm11 if i were you
Ok well I think I got things together more or less, eventually I tried to install CM10.1 with the ROM manager app. I forgot to select the options to wipe my data partitions and now I'm stuck in an endless boot loop every time I turn the phone on. I tried to boot from my backup using CWM which I made with the app prior to trying to install, and it gave me an error about an MD5 checksum failing, no matter what I tried. Should I do the factory reset/wipe option with CWM now? What's my best option.
Also why would you recommend CM11 over CM10.1? I don't want to have to deal with a nightly, all this phone stuff is a supreme headache to me.
eatfoodnow said:
Ok well I think I got things together more or less, eventually I tried to install CM10.1 with the ROM manager app. I forgot to select the options to wipe my data partitions and now I'm stuck in an endless boot loop every time I turn the phone on. I tried to boot from my backup using CWM which I made with the app prior to trying to install, and it gave me an error about an MD5 checksum failing, no matter what I tried. Should I do the factory reset/wipe option with CWM now? What's my best option.
Also why would you recommend CM11 over CM10.1? I don't want to have to deal with a nightly, all this phone stuff is a supreme headache to me.
Click to expand...
Click to collapse
Factory reset then get nandroid manager app and see if you can restore your stuff with that
CM11 is bugless atm and performance (imo) is way superior
So after a factory reset/data wipe, my phone just booted into CM10.1 and now that's working. And it looks like all of my stuff on the phone is still there (though of course apps aren't installed and whatnot, that wouldn't make sense). Thanks for all the help!
I tried to find a feature list or something to see what exactly is better about CM11, and found out that "stable" doesn't exactly mean stable for CM, and that it looks like a good idea to update, so I think I will try to update to that. Do you know anywhere that has an actual feature list to show me what CM11 does that CM10.1 doesn't?
I rooted my phone a week ago, I kept with the stock Rom for a few days, then installed a Renovate sense 6 Rom which seemed to work well. I had SuperSU installed, plus a few other apps, but then all of a sudden I got an error message when trying to open SuperSU saying the binary was missing, so I downloaded a root checker which said I wasn't fully rooted! After looking on the forums to find a solution I relocked my boot loader and unrooted the phone. Trying to find a stock RUU for my phone ( unlocked Europe version ) was a bloody nightmare. Also getting it to install on my phone was a pain, but probably more to do with my computer having a slow moment.
Is it really worth all the hassle when I can all go wrong in a couple of days ?
Don't think I'll be re routing again any time soon
Sent from my HTC One
Well it's like anything. If you don't know why you need something you probably don't need it
Sent from my HTC One using XDA Premium 4 mobile app
bloodyniceben said:
I rooted my phone a week ago, I kept with the stock Rom for a few days, then installed a Renovate sense 6 Rom which seemed to work well. I had SuperSU installed, plus a few other apps, but then all of a sudden I got an error message when trying to open SuperSU saying the binary was missing, so I downloaded a root checker which said I wasn't fully rooted! After looking on the forums to find a solution I relocked my boot loader and unrooted the phone. Trying to find a stock RUU for my phone ( unlocked Europe version ) was a bloody nightmare. Also getting it to install on my phone was a pain, but probably more to do with my computer having a slow moment.
Is it really worth all the hassle when I can all go wrong in a couple of days ?
Don't think I'll be re routing again any time soon
Sent from my HTC One
Click to expand...
Click to collapse
the phone never come unrooted .. you never had root installed properly
when it's flashed correctly from recovery it will not just go away
http://download.chainfire.eu/396/SuperSU
Flash that from recovery and you'll be rooted
I had SuperSU installed, everything was fine, anything I did with the phone worked. After a week it said the SU binaries were missing, and you couldn't get into SuperSU to do anything, but previously you could. If the phone was never rooted correctly like you say, i would have had this problem from the start.
Also after rooting I used a root checker which said I was rooted, but after this Su binary issue started, it said I wasn't rooted.
Still, I'm back to unrooted now, and the only reason I did it was to get Sense 6, which has since come out as an update, so I'm no worse off
Ben
Sent from my HTC One using XDA Free mobile app
bloodyniceben said:
I had SuperSU installed, everything was fine, anything I did with the phone worked. After a week it said the SU binaries were missing, and you couldn't get into SuperSU to do anything, but previously you could. If the phone was never rooted correctly like you say, i would have had this problem from the start.
Also after rooting I used a root checker which said I was rooted, but after this Su binary issue started, it said I wasn't rooted.
Still, I'm back to unrooted now, and the only reason I did it was to get Sense 6, which has since come out as an update, so I'm no worse off
Ben
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
This is a rom issue not a root issue. Could have also been an issue with the kernel. To be honest if you dont really use the root functions then there maybe no need for you to have it. To be honest most people dont really need root. They just wanna seem cool with some things they can show off on their device instead of using it for anything important or handy. I would advice to judge for yourself. Take the extra options/security risk and weigh it against remaining stock which has less options/secure.
I agree with the previous post, if you don't know what it is, you probably don't need it. As far as SuperSu disappearing, it sounds like either you didn't install it correctly or something changed. The ideal way to install SuperSu is to install via the recovery. And even so, if you reinstall your OS, you will need to reinstall SuperSu. Software does not simply disappear, something had to be done to hasten it's departure. An easy fix to your issue would have been to download the SuperSu zip package from http://download.chainfire.eu/supersu, and install it via your recovery. What I personally don't like about locking a bootloader is that now it says TAMPERED at the top of the screen.
Your issues seem to be with the restoring to stock process which HTC do make a bit convoluted, triggered by the root error not rooting itself.
Now to answer your question: My main reason for rooting is I want to take fine grained backups. Second is lots of clever people have come up with mods and improvements I like to install over the stock Sense ROM.
If you don't need anything that needs root, no need to root. Simple as that.
bloodyniceben said:
I rooted my phone a week ago, I kept with the stock Rom for a few days, then installed a Renovate sense 6 Rom which seemed to work well. I had SuperSU installed, plus a few other apps, but then all of a sudden I got an error message when trying to open SuperSU saying the binary was missing, so I downloaded a root checker which said I wasn't fully rooted! After looking on the forums to find a solution I relocked my boot loader and unrooted the phone. Trying to find a stock RUU for my phone ( unlocked Europe version ) was a bloody nightmare. Also getting it to install on my phone was a pain, but probably more to do with my computer having a slow moment.
Is it really worth all the hassle when I can all go wrong in a couple of days ?
Don't think I'll be re routing again any time soon
Sent from my HTC One
Click to expand...
Click to collapse
if you want RUU search @ htc1guru.com with firmware/software version
flash same firmware again + flash custom recovery + flash SuperSu it will resolve your problem