I see a few other posts similar to mine but there is a few differences. My Sprint nexus s 4g has been unlocked by me a few days ago. I used SDK manager and did the unlock oem command through command line. I then installed SU on my phone and don't have root still. I am not sure what I am doing wrong but I have tried many different things....Rom manager cant write where it wants to update or install things. One click acts like it worked but never changes anything. Of course my binaries are out of date with su but it cant find the binaries to update when it tries. I wouldn't doubt that the issues I am having might be because I didn't do something correctly when I unlocked bootloader.
I am running 2.3.7 droid os
kernel version 2.6.35.7
build gwk740
if that helps...Any info would be very much appreciated.
Get the su zip and put on your phones internal storage.
Reflash cwm in with fastboot on.your computer.
Boot into the recovery. Do not boot up the os or it will overwrite cwm.
In recovery flash the su zip from step 1.
That's it. You have root. Boot up phone. Launch su from app draw. Launch app that needs root and you can now grant it su permissions.
gooru11 said:
I see a few other posts similar to mine but there is a few differences. My Sprint nexus s 4g has been unlocked by me a few days ago. I used SDK manager and did the unlock oem command through command line. I then installed SU on my phone and don't have root still. I am not sure what I am doing wrong but I have tried many different things....Rom manager cant write where it wants to update or install things. One click acts like it worked but never changes anything. Of course my binaries are out of date with su but it cant find the binaries to update when it tries. I wouldn't doubt that the issues I am having might be because I didn't do something correctly when I unlocked bootloader.
I am running 2.3.7 droid os
kernel version 2.6.35.7
build gwk740
if that helps...Any info would be very much appreciated.
Click to expand...
Click to collapse
There's literally no way you can not correctly unlock the boot loader, either it's locked or it's not.
fastboot oem unlock
Don't select no
Finished
When you flash the su binary, mount /system through CWM first
I had the same problem but i just used the one click nexus root instead going thru the sdk manager and manually doing the adb commands , just look up one click nexus root in the nexus 4g development section and plug in ur phone follow directions it will do all the work for you
Thanks for the replys
For some reason my recovery mode just reboots the phone. If i could restore the phione I would have just started over.
I guess there is no new information for me?
Why can't you undo it? I would think you could download the zip with the stock images and follow the steps to unroot, you just would need to turn on your phone to the bootloader and skip the step to reboot bootloader. Then afterwards you could just go back through the rooting steps or just do the one click suggested above. To boot to bootloader you just hold volume up and the power button from an off state I believe, or volume down... Don't remember
Sent from my Nexus S 4G
What do I have to do to install a custom recovery and get root?
Where do I get the ASUS specific drivers for all of normal, recovery
and boot-loader modes, for adb, fastboot and 'disk drive'?
I can use ADB and fastboot SDK utilities from the Win7 console prompt.
the appropriate dll's and exe's are in windows path.
Are there special things to do like HTC's hboot unlock procedure?
I saw an apk file on ASUS's website for unlock, how does that work?
I found 1-click root script that is supposed to install an CWM
custom recovery and get root for you. Do I need to do anything prior
to running that to unlock the boot loader, so it will accept the fastboot
commands? Besides setting usb debug and any allowing any apk?
I don't know how to interact with the ASUS boot loader for
loading updates. For HTC I only needed a specially named zip
file on the root of the ext sd card and push buttons to start
the process. Is it similar? :fingers-crossed:
Try reading this.
http://forum.xda-developers.com/showthread.php?t=1697227
All of your questions and answers have been posted a long time ago and is readily available for your reading enjoyment. At least make an attempt to research on your own. Reading is your friend....
Sent from my SGH-I777 using Tapatalk 2
OK -- RTFM *sigh*
Can I flash cwm via fastboot w/o unlocking? I just want to root
to be able to run Titanium backup and Root Explorer tools.
Stock ROM is fine, only need cwm to get root.
The device was purchased a few days ago, (waiting for it
to arrive), so its probably .29 or .30 from factory.
I discussed the issues with ASUS and they kept reading
the text of the warning message about unlocking
instead telling me how / what to do to root.
If I understood correctly, after turning off 'fast boot'
and turning on 'USB debugging', I should be able to get the
stock boot loader into fastboot USB mode following the power on
volume button presses, then use fastboot flash recovery to
store the cwm recovery.img in the recovery partition.
I'm unsure what it is that unlock boot loader apk actually does ?
With HTC it was the hboot software version that determined
if fastboot commands were accepted. Perhaps when I actually
have the device, I'll understand better.
With that done, flash the root-signed.zip from cwm to root?
Cavsoldier already advised you to do your own research. All your questions have been answered, both for your first post and your second.
I'm not entirely sure why you seem so determined to flash CWM for root. They are completely unrelated. You only flash CWM when you unlock the bootloader. You do not have to unlock your bootloader to root the device. Just use this thread.
Also not sure why you're asking Asus how to root their product. That's a big no no. Companies don't like when you root their products. Even if the CSR knows how to root the device, they're not allowed to tell you. They'll just read from a script like they did to you.
Honestly, I'm not sure why I'm bothering to answer this. All the info you could possibly need is in the thread that was linked in the second post. All of it, for every question you've asked in both of your posts in this thread. Anything root or ROM related is in that thread. It links to several rooting methods, most of which do not require CWM, let alone an unlocked bootloader. So, basically, why haven't you clicked the link in the second post? Do it.
*sigh* sorry for being dumb
Alright -- I admit I couldn't find the search forum
button on the phone interface. After I looked via a
laptop (so I had the desktop view) it was where I
thought it was.
In any case, I found the utility script debugfs-root-v1.8
which uses all adb commands so it doesn't need to be able
to run fastboot boot loader commands. It looked like the
tricky stuff was being run on the tablet via adb shell
commands and adb control commands. If I understood
it, it leaves the tablet rooted without unlocking the boot
loader. So if I can live without nandroid backups, I can just
leave the OEM stock recovery alone.
Is there more to unrooting than removing superuser.apk
and restoring the stock su?
Would installing the current official firmware work
similar to HTC's RUU's and replace everything?
fuzzynco said:
*snipped*
Is there more to unrooting than removing superuser.apk
and restoring the stock su?
Would installing the current official firmware work
similar to HTC's RUU's and replace everything?
Click to expand...
Click to collapse
To unroot, there's an option in superuser. Installing the new firmware will not wipe data.
Sent from my Incredible 2 using Tapatalk 2 Beta-5
Thank you.....:good:
Hi, I recently decided to root my Nexus 5 using this guide on youtube: /watch?v=J1AKqrrf-5o
But after I'm all done with the rooting process, I noticed that my Nexus 5 has lost its LTE signal. Now it onlyy uses 3G. I managed to put it back on LTE by doing: *#*#4636#*#* and changed my prefered network, but by doing so, I lost my service with T-Mobile. Can't call or send messege with LTE on.
Please help me! I'm very new to Android and rooting but this first experience is not so good. Can you tell me what went wrong? Also, I rooted using the Linux guide.
Rooting alone won't mess up Wi-Fi. Don't use you tube use this http://forum.xda-developers.com/showthread.php?p=47025283
You might need this first. http://forum.xda-developers.com/showthread.php?p=47156064
jd1639 said:
Rooting alone won't mess up Wi-Fi. Don't use you tube use this http://forum.xda-developers.com/showthread.php?p=47025283
Click to expand...
Click to collapse
Many thanks, but I what can I do now? I don't want to sound like a jerk but what can the link do if I already rooted using the youtube guide (sorry again if that does sound jerkish).
danny2146 said:
Many thanks, but I what can I do now? I don't want to sound like a jerk but what can the link do if I already rooted using the youtube guide (sorry again if that does sound jerkish).
Click to expand...
Click to collapse
That's why I have you the second link
If all else fails flash the google stock images
Agreed. A root alone should not have caused an issue with your radio unless something went incorrectly. I would ( personally ) flash Google's stock nexus images and then possibly try again. Gaining root access can be done different ways, you may need to read into other alternatives...
I don't know. I use the ChainFIre CF Auto root on Ubuntu. I did unrooted the device earlier and was able to get LTE and service to work. Though after I use this samw method again, LTE stopped working properly, so I guess something is wrong with this method. Will try the "standard" method later though, if I can get a hold of a windows computer.
Let's back track a bit. What is the goal with root? Are you wanting to keep a custom recovery? What network are you using?
If you are going to just root stock and not go for a custom rom, I'd just flash a custom recovery via fastboot then boot to recovery and flash the SuperSU zip from Chainfire. At that point, you're rooted stock. If you decide to take an OTA update then you'll just need to make sure that you have the stock recovery installed. However, it's just as easy to flash the update when one of our devs packages it as a rom zip to flash via custom recovery, if not easier really.
Frankly, at this point my knowledge about android phone is still very hazy as this is acually my first ever phone, let along rooting, but I am eager to learn. So what's wrong if I didn't get a custom recovery? I just followed the instruction that they (chainfire autoroot) have for Linux and got this. Dunno if it was something in my phone nor the root. I am on T-Mobile BTW.
Yea, I'm baffled by that method affecting anything to do with service. It should be one of the least intrusive ways to root. However, weird things happen. So where are we now? Are you still rooted with the service issues? Which update / baseband are you on? You have the correct T-Mobile APNs? Have LTE(Recommended) selected under Preferred Network Mode in Settings / More... /Mobile Networks? Shouldn't really be necessary to mess with changing stuff in the Hidden Menu in this instance.
I'm on T-mobile Nexus 5 KitKat 4.4.2, with LTE in prefered mobile data. I rooted, the problem happened, unrooted this morning, the problem gone, rooted again with same method, the problem came back. I think I have the right APN since there are two with T-mobile options and I have tried both of them. As of now, I am still on root, but thinking of unroot it again...
danny2146 said:
I'm on T-mobile Nexus 5 KitKat 4.4.2, with LTE in prefered mobile data. I rooted, the problem happened, unrooted this morning, the problem gone, rooted again with same method, the problem came back. I think I have the right APN since there are two with T-mobile options and I have tried both of them. As of now, I am still on root, but thinking of unroot it again...
Click to expand...
Click to collapse
Still scratching my head over that, as the whole idea of Chainfire's auto root just literally is only supposed to install the SuperSU app and the binary and make no other changes. Obviously that isn't the case for you though. Are you unrooting via the settings in the SU app or via reflashing the stock img files?
es0tericcha0s said:
Still scratching my head over that, as the whole idea of Chainfire's auto root just literally is only supposed to install the SuperSU app and the binary and make no other changes. Obviously that isn't the case for you though. Are you unrooting via the settings in the SU app or via reflashing the stock img files?
Click to expand...
Click to collapse
I used the stock flashing method. I only unrooted it though, not lock the boot loader.
danny2146 said:
I used the stock flashing method. I only unrooted it though, not lock the boot loader.
Click to expand...
Click to collapse
Ok. So at this point, I would have the SuperSU zip (contains the SuperSU app and su binary) http://download.chainfire.eu/381/SuperSU/UPDATE-SuperSU-v1.91.zip on your phone, then fastboot a custom recovery like TWRP http://techerrata.com/browse/twrp2/hammerhead (fastboot flash recovery nameofrecovery.img), boot into recovery, and flash the zip. No need to wipe anything. Should just be able to flash and go. Then open SuperSU and make sure the binary is updated.
I'm sorry but how does one flash a custom recovery? Do I need a PC alondside or I can just do it entirely on my phone?
danny2146 said:
I'm sorry but how does one flash a custom recovery? Do I need a PC alondside or I can just do it entirely on my phone?
Click to expand...
Click to collapse
I included the command in the parenthesis in the last post.
In bootloader mode on the phone, of course, flash from PC, with the file in your fastboot folder:
fastboot flash recovery nameofrecovery.img (note - you can change the name of the file you download to whatever, as long as you leave the extension .img alone. ex: twrp.img)
If you are rooted already or still, you can flash from the phone either via the GooManager app https://play.google.com/store/apps/details?id=com.s0up.goomanager like this:
Install the app and open it. Tap menu then hit Install OpenRecoveryScript. Tap Yes. Verify that the filename displays your device's code name and hit Yes. The file will download and your device will install the recovery automatically.
or
(Rooted only) You can also use the app Flashify to flash the .img file directly from the phone. https://play.google.com/store/apps/details?id=com.cgollner.flashify
So yea, to solve your issue, I think it would be best to just start clean/stock, then go with the custom recovery flashed from PC + SuperSU zip method. If you can fastboot the other files to return to stock, this is no different and very quick. Should not take more than 5-10 seconds to flash the recovery. The whole operation, starting from scratch should take make 3-5 minutes to flash recovery, boot to it, flash the SuperSU zip then reboot, assuming you have fastboot set up properly and the 2 files you need downloaded already.
es0tericcha0s said:
I included the command in the parenthesis in the last post.
In bootloader mode on the phone, of course, flash from PC, with the file in your fastboot folder:
fastboot flash recovery nameofrecovery.img (note - you can change the name of the file you download to whatever, as long as you leave the extension .img alone. ex: twrp.img)
If you are rooted already or still, you can flash from the phone either via the GooManager app https://play.google.com/store/apps/details?id=com.s0up.goomanager like this:
Install the app and open it. Tap menu then hit Install OpenRecoveryScript. Tap Yes. Verify that the filename displays your device's code name and hit Yes. The file will download and your device will install the recovery automatically.
or
(Rooted only) You can also use the app Flashify to flash the .img file directly from the phone. https://play.google.com/store/apps/details?id=com.cgollner.flashify
So yea, to solve your issue, I think it would be best to just start clean/stock, then go with the custom recovery flashed from PC + SuperSU zip method. If you can fastboot the other files to return to stock, this is no different and very quick. Should not take more than 5-10 seconds to flash the recovery. The whole operation, starting from scratch should take make 3-5 minutes to flash recovery, boot to it, flash the SuperSU zip then reboot, assuming you have fastboot set up properly and the 2 files you need downloaded already.
Click to expand...
Click to collapse
I don't know , but this is very interesting. I now suspect that the problem is from T-Mobile's end, not mine, nor the root. I just dug into my mom,dad's phone and what did I find? 3 goddamn G! Not LTE. But when I tried to force the thing to get LTE, it disconnected from the service. However, when I moved to another location this evening, both the LTE and service came back. I think something odd is happening either in my neighborhood or T-Mobile service. Anyways, seems like nothing of major, might have to have a talk to T-Mobile about this.
But last question, with my CF root now, how can I know if I already have a custom recovery yet? And which one? You know for if I want to flash a ROM in the future. And thank you for your help!
danny2146 said:
I don't know , but this is very interesting. I now suspect that the problem is from T-Mobile's end, not mine, nor the root. I just dug into my mom,dad's phone and what did I find? 3 goddamn G! Not LTE. But when I tried to force the thing to get LTE, it disconnected from the service. However, when I moved to another location this evening, both the LTE and service came back. I think something odd is happening either in my neighborhood or T-Mobile service. Anyways, seems like nothing of major, might have to have a talk to T-Mobile about this.
But last question, with my CF root now, how can I know if I already have a custom recovery yet? And which one? You know for if I want to flash a ROM in the future. And thank you for your help!
Click to expand...
Click to collapse
Just boot into recovery and see what you have.
If you used CF-Root, then it would not have installed a custom recovery. This is something that you would have done on your own and not likely to have forgotten. If you root access is working properly, I'd suggest installing TWRP from the GooManager app as it's pretty easy and no PC required.
http://teamw.in/project/twrp2/205
Then make a nandroid back up of your phone and make sure to back up the EFS folder too and save them to a safe place. You can back that up in TWRP or from the method described here:
http://forum.xda-developers.com/showthread.php?t=2514095
Let's back up here. Why do you think you need root if you have no idea what you are doing? Are you just rooting because you can or do you have a real purpose?
Sent from my Nexus 5
Hello everybody.
First of all, I'm not sure whether this is the place to post this kind of questions. My apologies in advance. Here is my problem.
I rooted my nexus 5 nearly after a month of having bought it using the nexus root toolkit. Today I received the 4.4.3 OTA, and somewhere I read that it would fail most likely. I also read read that I should set survival mode in SuperSU (a pro option) in order to retain root access, which I couldn't. I tried to update via the OTA thinking it would fail, and it worked, only that I lost my root access.
Is there an easy way to regain root access? I don't want to wipe and re-install everything. There are only a few apps I use that need root access, however it would be nice to have them back, nevertheless.
Thanks in advance.
PS: Now I am able to record video hassle-free, no more static noise in the background :victory:
HerrJuancho said:
Hello everybody.
First of all, I'm not sure whether this is the place to post this kind of questions. My apologies in advance. Here is my problem.
I rooted my nexus 5 nearly after a month of having bought it using the nexus root toolkit. Today I received the 4.4.3 OTA, and somewhere I read that it would fail most likely. I also read read that I should set survival mode in SuperSU (a pro option) in order to retain root access, which I couldn't. I tried to update via the OTA thinking it would fail, and it worked, only that I lost my root access.
Is there an easy way to regain root access? I don't want to wipe and re-install everything. There are only a few apps I use that need root access, however it would be nice to have them back, nevertheless.
Thanks in advance.
PS: Now I am able to record video hassle-free, no more static noise in the background :victory:
Click to expand...
Click to collapse
So dump SuperSU zip on the phone (link in sig), and flash it with recovery.
Aerowinder said:
So dump SuperSU zip on the phone (link in sig), and flash it with recovery.
Click to expand...
Click to collapse
Thanks for your reply. I have already SuperSU on my phone, but when I press it it says there are some binaries missing. Busybox doesn't update the binaries since it has no root access and says the device might be improperly rooted. My recovery is TWRP, so I can actully flash root files or such.
Edit: I just tried to boot into recovery and it didn't work quite well. There is a fallen android guy with a red triangle. So I don't have recovery either it seems.
HerrJuancho said:
Thanks for your reply. I have already SuperSU on my phone, but when I press it it says there are some binaries missing. Busybox doesn't update the binaries since it has no root access and says the device might be improperly rooted. My recovery is TWRP, so I can actully flash root files or such.
Edit: I just tried to boot into recovery and it didn't work quite well. There is a fallen android guy with a red triangle. So I don't have recovery either it seems.
Click to expand...
Click to collapse
Download TWRP 2.7.1.0 from here: http://techerrata.com/browse/twrp2/hammerhead
Reboot to bootloader, fastboot flash recovery twrp.img
Flash SuperSU with TWRP.
If you do not understand these instructions, I highly suggest reading this sticky: http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
Aerowinder said:
Download TWRP 2.7.1.0 from here: http://techerrata.com/browse/twrp2/hammerhead
Reboot to bootloader, fastboot flash recovery twrp.img
Flash SuperSU with TWRP.
If you do not understand these instructions, I highly suggest reading this sticky: http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
Click to expand...
Click to collapse
Thanks for the help. I'll try that as soon as I can.
I'm trying to install a custom recovery...... I'm s - off and unlocked with sunshine. Issue is twrp manager says I'm not rooted so I can't use it. Flashify says I'm rooted but don't have su permissions, so I can't use it. I'm totally confused, they're both contradicting each other and am stuck. I have no access to a computer for 2 days so I need to install a recovery through the phone itself. Thanks.
beeper10 said:
I'm trying to install a custom recovery...... I'm s - off and unlocked with sunshine. Issue is twrp manager says I'm not rooted so I can't use it. Flashify says I'm rooted but don't have su permissions, so I can't use it. I'm totally confused, they're both contradicting each other and am stuck. I have no access to a computer for 2 days so I need to install a recovery through the phone itself. Thanks.
Click to expand...
Click to collapse
Have you downloaded SuperSu from the Play Store? If yes, make sure you've opened the actual app so it can load new binaries. Also try Root Checker Basic in the Play Store. What happens when you try to run the official TWRP app? It should be able to guide you through.
Sent via Tapatalk on VZW M8. Booyakasha!
beeper10 said:
I'm trying to install a custom recovery...... I'm s - off and unlocked with sunshine. Issue is twrp manager says I'm not rooted so I can't use it. Flashify says I'm rooted but don't have su permissions, so I can't use it. I'm totally confused, they're both contradicting each other and am stuck. I have no access to a computer for 2 days so I need to install a recovery through the phone itself. Thanks.
Click to expand...
Click to collapse
Do you have an External SD Card?
If so, download TWRP Recovery from here : https://www.androidfilehost.com/?fid=23622183712475334
This is from Captain_Throwback. You can install his TWRP using hboot method. The instructions on how to do that are here: http://themikmik.com/showthread.php?16278-RECOVERY-ALL-M8-VARIANTS-MultiROM-TWRP-Recovery-v2-8-0
I can't move the file to the root of SD card because root explorer doesn't show me having root privileges.
I recommend the fast boot method here. http://teamw.in/project/twrp2/226
beeper10 said:
I can't move the file to the root of SD card because root explorer doesn't show me having root privileges.
Click to expand...
Click to collapse
Does anyone around you have a phone with an SD slot? You could put your card in there phone and copy the file you need then put it back in your phone. Just trying to through out some ideas.
None of my friends feels the need to mess with things.