Database Users

Cannot root nexus s

1. I've searched similar threads on the forum already.
2. I've used usbdeview to uninstall old drivers so as to eliminate any conflicts when installing the new ones.
3. I've tried this on both Win7 x64 as well as Vista x64 with the same results.
4. I don't care about clockwork recovery - the stock recovery is fine as as far as I can tell it makes no difference to the issue i'm having.
After checking the dozen or so guides on how to do this I first tried installing the usb drivers for the phone whilst in fastboot mode. This was impossible for me as no matter what combination I used to point the windows device driver installer to the google usb drivers, they simply would-not-install. What I did notice (though trial and error) was that those same drivers are not, in fact, used for fastboot mode, but for normal boot whilst the phone is in usb debugging mode. I.e. windows device driver installer was able to install the drivers in the folder. I then decided to go ahead anyway.
I launched the cmd (in admin mode) and navigated to the program files (x86) (so much for the 64bit sdk, GG Google lol)->android->android-sdk->platform-tools (the original tools folder is no longer the correct folder as Google moved the .dll's). I then tried to launch the various 'fastboot' commands necessary and hit another roadblock as the cmd prompt reports that 'fastboot' is not a valid command.
So there you have it, I can't install the drivers and can't execute and 'fastboot' commands. Anyone know how to root this phone using neither of those 2 components? *sigh*
Any help would be greatly appreciated.
P.S. For an added bit of irony, rooting a friends HTC HD was easier...

Fastboot is in the "tools" folder, not "platform-tools" and make sure you have copied over the .dll files into the "tools" folder or else it wont work.
The clockwork method is easy, and can be used without flashing the clockwork recovery image to the phone so you can root it and pretty much keep everything stock. The 'fastboot boot recovery.img' command boots the phone with the image, but it doesnt flash it.
The whole rooting process is really easy, it should only take a minute or two.
This guide h ttp://forum.xda-developers.com/showthread.php?t=935819 worked flawlessly for me a few times.

Thanks for the reply.
After installing the pdanet it asked me if i wanted to reinstall the usb drivers. I chose to do so because at this point, I had nothing to lose. After doing so and rebooting the phone into recovery mode, windows device manager no longer had a missing driver reported! Go figure.
I have thus been able to unlock my bootloader. However I have not been able to root my phone (to be honest i originally thought they were the same thing). The guide askes to flash the clockworkrecovery to the phone which would replace the stock recovery would it not? Is there any way to root the phone now that it's bootloader is unlocked without flashing the clockwork image?

There are usb drivers with the sdk but theyre in the 3rd party section for some reason.
The unlocked bootloader isnt necessary if you want to get root, but if you use the fastboot command i pasted above, nothing gets flashed, but the phone boots only once using the specified recovery.img. Nothing will get overwritten unless you use the 'flash' parameter as quite a few of the guides do. Make sure you have your su*.zip already copied onto your sdcard partition as this makes it easier.

mrbeardy said:
There are usb drivers with the sdk but theyre in the 3rd party section for some reason.
The unlocked bootloader isnt necessary if you want to get root, but if you use the fastboot command i pasted above, nothing gets flashed, but the phone boots only once using the specified recovery.img. Nothing will get overwritten unless you use the 'flash' parameter as quite a few of the guides do. Make sure you have your su*.zip already copied onto your sdcard partition as this makes it easier.
Click to expand...
Click to collapse
I think it doesn't matter if you do fastboot "flash" or "boot" because Nexus S was built with a safety system that replaces the custom recovery for the stock everytime you reboot. Correct me if i'm wrong

Rafael Cadina said:
I think it doesn't matter if you do fastboot "flash" or "boot" because Nexus S was built with a safety system that replaces the custom recovery for the stock everytime you reboot. Correct me if i'm wrong
Click to expand...
Click to collapse
fastboot boot only boots the recovery one time, fastboot flash flashes the recovery permanently to your phone(until you flash another). so yea, it makes a BIG difference.

I also had a difficult time rooting it because of the drivers. Once I found this thread right here http://forum.xda-developers.com/showthread.php?t=878786 the drivers worked instantly! Actually everything worked!

Hang on, so I don't need to unlock the bootloader to get perm root? (if so, how do I re-lock the bootloader?) Why do so many of the guides include this part then? What's the advantage of an unlocked botloader?
/confused.
EDIT: note that i'm running 2.3.3 if that makes any diff.

Ok, i'm I used this method (http://www.dkszone.net/root-nexus-s-android-2.3.3-gingerbread-google-samsung) to root the phone. I have confirmed this by downloading apps like adfree but when i use titanium backup is says it can't get root privileges even though the super user app is allowing it.
EDIT: I worked it out, turns out Titanium Back up needs something called 'busybox' (which wasn't the case on my previous installs on other phones). After installing it, it now works perfectly. No need for clockwork after all (not sure why i'd ever use it to be honest as I don't install custom roms but I still need root for other apps that i use).

Root Toolkit Wont Recognize N7

After about 10 tries I still cant get this damn tablet to work with the toolkit. I screwed up while updating and lost root, now I cant get the root toolkit to recognize my device after installing the drivers on any pc (tried win two with 8 and two with 7). I have no clue what to do as I was able to unlock and root it initially but now I cant redo it to get my device back and in working order. This is driving me insane!!!!!!!!! I am using the most recent toolkit, and my tablet is on 4.2.2 unlocked but no longer rooted.

Another satisfied toolkit customer. Did you pay for the privilege? If yes, I suppose you should call their support department during normal business hours.
It's a little surprising. I can see that the behavior of ADB might have changed - when the regular OS is booted. (This is a new security feature of 4.2.2 adb - you need the latest SDK version of the "adb" program)
And if you used the OTA, then the custom recovery was replaced by the 4.2.2 stock recovery, so ADB won't even show up there (stock recoveries don't run the "adbd" daemon).
But I would think that you should be able to use fastboot, even if the bootloader was also upgraded.
So, a couple of questions.
A) Can you get the tab into bootloader mode?
B) Does it show version 4.18 on that screen?
C) Does the recovery appear to have been replaced by a stock recovery?
D) Does your PC (pick one and stick with it) show an Unknown Device, or something else when you plug the tab in whilst it is in bootloader/fastboot mode?
E) From the command line, what happens when you run "fastboot devices" either from the command line or from the toolkit when the device is plugged to the PC and in bootloader/fastboot mode?

Thanks for the fast reply. First of I thought the toolkit was free, since it is posted in many forums and you can download it right from the developers site. Next, I did use the OTA like a moron because I forgot that this was my unlocked and rooted nexus. Now to your questions:
A: I can get it into bootloader
B: The version is 4.18
C: The recovery only shows up with the droid dude and a red !
D: On my Win8 Desktop it shows up under Andriod Phone as 'Android ADB Interface' in device manager
E: in the comand line I get the serial of my tablet

lamboboy732 said:
Thanks for the fast reply. First of I thought the toolkit was free, since it is posted in many forums and you can download it right from the developers site. Next, I did use the OTA like a moron because I forgot that this was my unlocked and rooted nexus. Now to your questions:
A: I can get it into bootloader
B: The version is 4.18
C: The recovery only shows up with the droid dude and a red !
D: On my Win8 Desktop it shows up under Andriod Phone as 'Android ADB Interface' in device manager
E: in the comand line I get the serial of my tablet
Click to expand...
Click to collapse
This
>> E: in the comand line I get the serial of my tablet
is good.
the droid dude is the stock recovery. It actually sounds to me like the OTA succeeded for you - as you are showing both stock recovery and the 4.18 bootloader.
With the tablet in fastboot mode, just flash a custom recovery and you are good to go. You can either use "fastboot flash recovery name-of-recovery-image-file.img", or the equivalent operation in the toolkit.
Then, boot into recovery, and see if
A) the custom recovery appears correctly, and
B) if ADB now shows up either via command line or the toolkit (with the device in custom recovery).
If you got your adb & fastboot tools via installation of the Android SDK, make sure it is updated to the latest version
adb version
should report something like 1.0.31 (iirc)
good luck

[Q] stuck cyanogenmod bootloader, android lying down with red triangle in recovery

Hi,
I just unlocked and rooted my Nexus 7 with NRT, then had the CWM app on my phone, tried to install cyanogenmod from it. Got stuck on bootloader. When i enter recovery only get the android lying on back with red triangle and exclamation mark. Cannot get correct driver to connect to pc either!!!
HELP!!

So many things out of whack here.
The android lying on it's back is the stock recovery; this conflicts with your assertion that you rooted your device with NRT.
You claim you don't have a working driver on your PC; this also contradicts your assertion about using NRT to root.
No clue what your phone has to do with your tablet.
The only WAG I can make from this is that:
- your "phone" == your "tablet"
- the "CWM app" is actually ROM manager, and you used it to somehow (how, without root?) boot into the recovery, which is still stock. (So of course it won't install a custom ROM)
good luck

originally had the drivers
bftb0 said:
So many things out of whack here.
The android lying on it's back is the stock recovery; this conflicts with your assertion that you rooted your device with NRT.
You claim you don't have a working driver on your PC; this also contradicts your assertion about using NRT to root.
No clue what your phone has to do with your tablet.
The only WAG I can make from this is that:
- your "phone" == your "tablet"
- the "CWM app" is actually ROM manager, and you used it to somehow (how, without root?) boot into the recovery, which is still stock. (So of course it won't install a custom ROM)
good luck
Click to expand...
Click to collapse
I originally had the drivers on pc and used NRT but then deleted them as did not want a conflict when i then did it with my galaxy nexus. Is there an easier way to ge those drivers again so can try to get out of this mess

davjet said:
I originally had the drivers on pc and used NRT but then deleted them as did not want a conflict when i then did it with my galaxy nexus. Is there an easier way to ge those drivers again so can try to get out of this mess
Click to expand...
Click to collapse
If your tablet does not boot into the regular OS, then the only two recourses left are:
(a) custom recovery
(b) fastboot
Since it appears from your prior post that you do not have a custom recovery installed, option (a) above is not available to you. That leaves only a fastboot method. So, get the drivers re-installed. I would suggest you use a RECENT toolkit to install the drivers, and then ignore the fact that you have the toolkit and learn how to use fastboot manually. (Use the toolkit only to install drivers, nothing else). You will learn something by doing that. Installing a custom recovery with a N7 having an unlocked bootloader is literally a single command:
Code:
fastboot flash recovery name_of_recovery_image_file.img
To my knowledge, there are no Generic Class USB drivers for ADB or fastboot, meaning that they will always be selected by a match to the specific USB hardware VID/PID (Vendor ID/ Product ID) values - meaning that they will not typically interfere with each other from device to device. You can probably have hundreds of them safely installed on a Windoze PC. Dog help you if you have Windows 8 though (although at least one of the toolkits apparently is savvy enough to deal with Win 8 - that might be the only reason to use one.)
good luck

ok!
thanks,
I did get drivers installed again with NRT but then I used nexus 7 toolkit to flash the CWM recovery-

Please help with flashing recovery

I recently updated rm2pro with android 10 system update and I'm trying to flash recovery but it keeps leaving me on "waiting for device" in command window, however it does detect adb device. I don't know if it's missing drivers or what, I tried plenty. I want to switch to custom rom but can't flash recovery and can't find a guide anywhere, hope to see a solution soon.

Lost dash charge and USB connectivity

Recently lost the ability to dash charge and use my USB-C jump drive on my OP6T. I've flashed a couple of different ROMS, I updated to OnePlus6TOxygen_34.J.55_OTA_055_all_2107132253_b2cbbb97b4eee.zip, re-flashed another rom, I even swapped out the port with a new replacement I ordered. I'm out of ideas, the port is new so it doesnt need cleaning, USB debugging has been toggled and USB config set to file transfer. Computer doesnt recognize it using the original cable either. I'm leaning towards a software issue but i'm afraid to do too much flashing as I dont have my USB-C to fall back on as backup and would essentially brick the thing if I cant read from the jump drive. Any idead?

Are you able to run fastboot commands from the bootloader or adb commands in recovery?
Or even mount storage in recovery?

SMcC2 said:
Are you able to run fastboot commands from the bootloader or adb commands in recovery?
Or even mount storage in recovery?
Click to expand...
Click to collapse
I'm able to get to get to fastboot, and now I just screwed myself out of TWRP and root by flashing a rom without TWRP. The PC will charge the phone, but wont see it. ADB sees no devices and Shapeshift's recovery doesnt have many options. Basically now i need to flash a recovery image by device only. and that still doesn't solve the connection and slow charge issue

Are you rooted with Magisk?
You should be able to install the twrp.zip from Magisk if so. If not the TWRP app in may work to get it back.
It sounds like you may need to try the MSM tool soon.

root checker says i'm not properly rooted anymore, i've only got the magisk.apk courtesy of google's restore. Looks like the official twrp app will download but not let you flash the img unless rooted. I'm hoping this is a software bug with the oxygen image since i replaced the cable and port and no fix, otherwise i'm gonna have to buy a new device.

and I dont think MSMtool will do anything if the phones not recognized. the all-in-one tool was useless since it didnt see the phone in fastboot

I am able to wirelessly ADB. but as far as i know, there's no way to flash recovery. As soon as i boot to fastboot I obviously lose wifi. any other ideas? i'm not familiar with wireless adb