I bought an AT&T Nexus S today, replacing my Captivate. (Hooray for working GPS! It's sad I even have to say that.)
I also primarily use a Macbook Pro. For the Galaxy S phones there was a wonderful one click root tool, which worked for Mac OS X as well, I can't seem to find a similar tool for the Nexus S.
I've looked through the forum, and in the stickies there is a root guide for the i9020A but it appears PC focused, and seems fairly involved, it as 41 steps across 4 parts. (I've not messed around much with the Android SDK before.)
There is as well a Mac root guide, but it was written in January, for 2.3.1, and the i9020T...
It links to the Superboot method, by MoDaCo, which seems a great deal easier, and supports Mac OS X... but I'm entirely unsure whether there is a build of that for the i9020A.
In short (after I've already made you read long), I've read a pretty good deal about the subject, but I still feel rather lost. What's the easiest method of rooting my Nexus S, preferably with support for Mac OS X, though that isn't a deal breaker, I can always borrow a friend's laptop if the rooting process is manageable.
And thank everyone for their time.
Just rooted mine about an hour ago and followed this guide:
http://forum.xda-developers.com/showthread.php?t=970237
I had no problems whatsoever... pretty quick and easy. At the part where it has you look for the file to rename, you can probably skip that part... I didn't see the file and I'm able to reboot into Clockwork.
Thank you r3p00c, that was exactly what I needed. Rooted within the hour, fantastic.
was your att nexus s on 2.3.4??
Please enter a valid message
I'm not new to android whatsoever.. I've just returned from an Iphone 4s cause i was missing the openess of android. Now.. i've pulled out my old Nexus S 4g, Updated it to 4.0.4 and i cant get it to connect to my computer for the life of me! tried 4 different cables, 5 different computers, every driver i could find and nothing. I've come to believe this is a software failure... All i need is root and i will be able to sleep at night. Could someone package up .zip to give root and twrp recovery that i could flash through stock recovery? I dont know else i could do to get root... but this problem is becoming quite annoying.
1. There is no way to package a zip to flash through stock recovery since it would have to be signed.
2.For someone who is "not new to android whatsoever" making 2 threads about the same topic 2 minutes apart isn't exactly acting the part.
Try this guide.
Actually you're wrong, On the Epic 4G someone did in fact manage to do so. And yeah since i'm not new to these forums i understand that stuff like this gets overlooked so i made two posts. Cry me a river.
BTW Thanks harb... but that would involve being able to connect to my PC. Which just is not possible right now.
Thats the Android Karma... it happens but a little advice.
If you can't connect to the computer then it might a hardware issue not software.
If getting root was that easy that you just had to flash a zip on stock then everyone would be doing it. And good luck getting root without unlocking your bootloader first. Not to be rude but the problem could possibly be between the computer and the chair.
robogoflow said:
Thats the Android Karma... it happens but a little advice.
If you can't connect to the computer then it might a hardware issue not software.
If getting root was that easy that you just had to flash a zip on stock then everyone would be doing it. And good luck getting root without unlocking your bootloader first. Not to be rude but the problem could possibly be between the computer and the chair.
Click to expand...
Click to collapse
It's ok, not rude. I understand what you are saying... but did you not read what i just said? somebody had accomplished this on the Epic 4G and i'm just trying to find someone who has done it with the NS4G.. I've had 4 Android devices, rooted them all and been here since the beginning. It's not a hardware problem, it connected fine before when it was on gingerbread... i downloaded the OTA ICS then flashed through stock recovery.. but if you read what i said in the first post this problem only occured AFTER updating. This is why i quit using XDA a long time ago, because people just post a bunch of useless information instead of trying to help... The problem is not me my friend, its the damned ICS update, i've read multiple posts all over the interweb w/ people who have had the same problem, yet no resolutions other than bending up the micro usb male piece on my phone which is not the problem as i said it was working fine before i updated. Have tried multiple samsung drivers, pda net, and Android SDK Drivers, multiple Cords from samsung, to htc, to blackberry and palm pre and even a nokia one now. and 5 different computers... so tell me smart guy, what would you do?
grumpySasquatch said:
It's ok, not rude. I understand what you are saying... but did you not read what i just said? somebody had accomplished this on the Epic 4G and i'm just trying to find someone who has done it with the NS4G.. I've had 4 Android devices, rooted them all and been here since the beginning. It's not a hardware problem, it connected fine before when it was on gingerbread... i downloaded the OTA ICS then flashed through stock recovery.. but if you read what i said in the first post this problem only occured AFTER updating. This is why i quit using XDA a long time ago, because people just post a bunch of useless information instead of trying to help... The problem is not me my friend, its the damned ICS update, i've read multiple posts all over the interweb w/ people who have had the same problem, yet no resolutions other than bending up the micro usb male piece on my phone which is not the problem as i said it was working fine before i updated. Have tried multiple samsung drivers, pda net, and Android SDK Drivers, multiple Cords from samsung, to htc, to blackberry and palm pre and even a nokia one now. and 5 different computers... so tell me smart guy, what would you do?
Click to expand...
Click to collapse
Bro... Chill... They're just trying to help you out. There is NO way to to root your NS without a computer (currently. We are not Epic 4G owners here). You said you didn't use your NS since GB, SO during the time in between something could have happened to the hardware. Don't rule that out just yet. Your drivers might also be bad. Is this what migrating to iOS does to people? Makes them snobby and demand fixes to problems they can't figure out on their own? Don't hate on the XDA forums. If we're not helping you "hit the thanks button anyways, you ungrateful bastard" (XDA into video ). Anywho. Chill. Keep trying.
Nexus S (GSM i9020a)
Paranoid (14.a Hybrid - 4.0.4)
Matrix Kernel (CFS - 20.0)
Intellidemmand (800/100)
Live OC (105 - 800/1000)
Deep Idle (On - Noop)
BLX - 96 (Inverted Apps)
I am chill, i am just trying to describe what I've already done so maybe someone could suggest something else. And no what i meant is i downloaded the OTA on my computer than transferred it onto my Nexus through USB mount a couple of days ago so i know its not a hardware issue. Im not demanding fixes, just trying to see if anyone has done been able to figure this out yet as i know im not the only one with this issue. And there is a big problem w/ people on the XDA forums as a whole.. i am a little frustrated and just dont like when someone is telling me is a User issue when i have tried everything conceivable and know what i am doing.. Sorry if this offended you. and IOS is a good device.. its just like.. NWO they want to control everything haha. I'd rather be part of the rebel faction. even though i love my ipad XD
There is currently no way to root 4.0.4 without an unlocked bootloader (and no custom recovery), and the only way to get an unlocked bootloader is to either have root or plug it into the PC and unlock via fastboot. As such, you are stuck with sorting out drivers - despite how annoying they are.
The video i linked to above describes in detail (and through video) exactly how to sort out NS drivers on Windows machines as well as the required fastboot commands to get a custom recovery.
Harbb said:
The video i linked to above describes in detail (and through video) exactly how to sort out NS drivers on Windows machines as well as the required fastboot commands to get a custom recovery.
Click to expand...
Click to collapse
Yes that is a good video, and does a job well done in describing on how to install drivers. My main issue is that my Computer(s) are'nt recognized my device at all... It doesn't show up as android device, or nexus s... but Unknown device. If i could figure this out i believe i could handle the rest.
grumpySasquatch said:
Yes that is a good video, and does a job well done in describing on how to install drivers. My main issue is that my Computer(s) are'nt recognized my device at all... It doesn't show up as android device, or nexus s... but Unknown device. If i could figure this out i believe i could handle the rest.
Click to expand...
Click to collapse
Pretty sure that video describes that. You need to open up device manager, double click unknown device (while device is in fastboot), hit update driver and navigate to the provided drivers on the site. Watch it a few times, you'll figure it out.
Have you tried to install PDANet? I've read numerous times about it working wonders for users who have trouble with drivers. It has all of the necessary drivers built in.
Sent from my Nexus S using xda premium
d_phekt said:
Have you tried to install PDANet? I've read numerous times about it working wonders for users who have trouble with drivers. It has all of the necessary drivers built in.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
yes i second that,PDANet Drivers usually work across all devices you should try them.
Like ppl said before, try PdaNet drivers it might help.
thanks everyone, , but like i said i tried pretty much every driver you can find online. they will not install as my device comes up as "Unknown", i've literally tried every piece of literature on the web relating to this issue... at this point i'm just going to wait for the JB update and see what happens.
grumpySasquatch said:
It's ok, not rude. I understand what you are saying... but did you not read what i just said? somebody had accomplished this on the Epic 4G and i'm just trying to find someone who has done it with the NS4G.. I've had 4 Android devices, rooted them all and been here since the beginning. It's not a hardware problem, it connected fine before when it was on gingerbread... i downloaded the OTA ICS then flashed through stock recovery.. but if you read what i said in the first post this problem only occured AFTER updating. This is why i quit using XDA a long time ago, because people just post a bunch of useless information instead of trying to help... The problem is not me my friend, its the damned ICS update, i've read multiple posts all over the interweb w/ people who have had the same problem, yet no resolutions other than bending up the micro usb male piece on my phone which is not the problem as i said it was working fine before i updated. Have tried multiple samsung drivers, pda net, and Android SDK Drivers, multiple Cords from samsung, to htc, to blackberry and palm pre and even a nokia one now. and 5 different computers... so tell me smart guy, what would you do?
Click to expand...
Click to collapse
So the ICS update makes you unable to boot to fastboot and makes your device unable to be recognized by your computer from there?
That's a new one. As far as I know, "Unknown device" is actually your device being recognized, just the driver doesn't get installed correctly.
Have you tried manually specifying which driver to install and selecting the PDA Net driver? Look at Harbb's last post.
Have you went as far as editing the drivers inf to match your hardware ID? I know I had to do that way back when the PDA net drivers weren't even available.
'til then, user error.
polobunny said:
Have you tried manually specifying which driver to install and selecting the PDA Net driver? Look at Harbb's last post.
Have you went as far as editing the drivers inf to match your hardware ID? I know I had to do that way back when the PDA net drivers weren't even available.
'til then, user error.
Click to expand...
Click to collapse
I swear you people don't listen, look i did everything in the video exact when i try to manually specify the driver it comes back saying that the folder you specified doesn't contain a compatible driver for your device... I'm not an imbecile and know how to follow instructions on a video. I know most people skip research cause they're too lazy to figure it out themselves... i posted on here as a last resort and feel like people are telling me what i already know then telling me its my fault, ridiculous. if you guys are just going to repeat what the last five people have said instead of trying to offer a new soloution then why even bother posting?
Epic 4G could do this in FROYO... It was patched by google in 2.3+. Do you want an app to secretly root you and install malware?
Sent from my Samsung Epic 4G using Tapatalk 2
grumpySasquatch said:
I swear you people don't listen, look i did everything in the video exact when i try to manually specify the driver it comes back saying that the folder you specified doesn't contain a compatible driver for your device... I'm not an imbecile and know how to follow instructions on a video. I know most people skip research cause they're too lazy to figure it out themselves... i posted on here as a last resort and feel like people are telling me what i already know then telling me its my fault, ridiculous. if you guys are just going to repeat what the last five people have said instead of trying to offer a new soloution then why even bother posting?
Click to expand...
Click to collapse
Well it is going to be basically one of two things.
1. Is user error of some sort. That is what people have been trying to help with.
2. Is hardware issue that no one can help you with of course. Or some software issue causing it to not show up for who knows what reason. Neither of which folks can help with since a computer is not seeing it. So they revert back to what they can. Point 1
When you asked a question like is there a zip that you can flash in stock recovery to give you root or custom recovery that also doesn't help your cause for people assuming user error.
The one other thing you can try is download mode and Odin.
grumpySasquatch said:
I swear you people don't listen, look i did everything in the video exact when i try to manually specify the driver it comes back saying that the folder you specified doesn't contain a compatible driver for your device... I'm not an imbecile and know how to follow instructions on a video. I know most people skip research cause they're too lazy to figure it out themselves... i posted on here as a last resort and feel like people are telling me what i already know then telling me its my fault, ridiculous. if you guys are just going to repeat what the last five people have said instead of trying to offer a new soloution then why even bother posting?
Click to expand...
Click to collapse
Cool. Trash your Nexus S, clearly broken.
Edit: That's nice of you albundy, but Mr grumpySasquatch (fitting name eh?) has tried everything, including modding the drivers inf. His Nexus S is broken beyond repair, also the first one we've ever seen that won't adb but works fine for USB mounting. *chuckle*
In the middle of backing up my apps on the nexus 7 via the NEXUS 7 TOOLKIT (http://forum.xda-developers.com/showthread.php?t=1809195)
The toolkit has been stuck on "waiting for adb mode" Apparently it was not recognized. I found instructions to fix that but I dont know how to get out of this backup mode. The nexus 7 screen has the droid laying down so I can't do anything to the nexus. And the toolkit just says "waiting for adb mode"
Please help quick because I'm afraid to do anything to it so I'm leaving it like it is until I find out what to do.
Same problem. Are there no answers for noobs?
IDK1986 said:
In the middle of backing up my apps on the nexus 7 via the NEXUS 7 TOOLKIT (http://forum.xda-developers.com/showthread.php?t=1809195)
The toolkit has been stuck on "waiting for adb mode" Apparently it was not recognized. I found instructions to fix that but I dont know how to get out of this backup mode. The nexus 7 screen has the droid laying down so I can't do anything to the nexus. And the toolkit just says "waiting for adb mode"
Please help quick because I'm afraid to do anything to it so I'm leaving it like it is until I find out what to do.
Click to expand...
Click to collapse
Holy cow. I've been on this site for hours trying to figure out if it's safe for me to unplug the USB connection from my Nexus 7 to my PC with the Toolkit 4.0 stuck at
< waiting for device >
'downloading boot.img'...
I am not allowed to post in the developer thread to ask for clarification from people who say they've solved this problem (but don't state what the solution is), and since this is the first thread I've found under "General" where I can actually post, I'm quite disappointed to find out that there are no responses to this poor schlep who posted this last December.
So, in the hopes that threads are now more likely to be seen and responded to than they used to be, I'm crossing my fingers someone can answer. Is it safe for me to disconnect my Nexus 7, or is it really taking hours to download "boot.img"?
Answer
eventide7 said:
Holy cow. I've been on this site for hours trying to figure out if it's safe for me to unplug the USB connection from my Nexus 7 to my PC with the Toolkit 4.0 stuck at
< waiting for device >
'downloading boot.img'...
I am not allowed to post in the developer thread to ask for clarification from people who say they've solved this problem (but don't state what the solution is), and since this is the first thread I've found under "General" where I can actually post, I'm quite disappointed to find out that there are no responses to this poor schlep who posted this last December.
So, in the hopes that threads are now more likely to be seen and responded to than they used to be, I'm crossing my fingers someone can answer. Is it safe for me to disconnect my Nexus 7, or is it really taking hours to download "boot.img"?
Click to expand...
Click to collapse
For anyone else who has this question, I found there was no damage done to my tablet by unplugging the USB cable and trying the procedure again. The procedure itself should initialize very quickly once a good connection is made between your PC and your tablet. I simply had to unplug my tablet and plug it back in (I used the same USB port, but I understand others have discovered they had to change to a different USB port).
eventide7 said:
For anyone else who has this question, I found there was no damage done to my tablet by unplugging the USB cable and trying the procedure again. The procedure itself should initialize very quickly once a good connection is made between your PC and your tablet. I simply had to unplug my tablet and plug it back in (I used the same USB port, but I understand others have discovered they had to change to a different USB port).
Click to expand...
Click to collapse
Changing ports worked for me.
Hi There,
I would really appreciate some help with rooting my HTC Sensation XL which runs Android version 4.0.3.
I am not too sure if I have posted this in the right section so my apologies if I haven't.
OK so I have been trying for about 6 weeks now to ROOT my HTC. The only reason that I wish to do so is so that I can delete the apps that can not be deleted from the phone IE Facebook,Twitter & similar apps. I don't use them any more and because of this I would like them off the phone.
I have spent many of hours trawling the net to find guides and step by steps on how to do this. I wouldn't say I know/understand a lot of what it asks me to do but at the same time I have a little knowledge so that I am not completely in the dark.
But after reading several step by steps,reading about all the files I need,I end up getting lost and very confused half way through so I decided that perhaps an app that does it for me would be best.
I have seen SuperOneClick recommended several times so I thought I couldn't go wrong with it.
I downloaded the file from CNET.It is version 2.3.3. I extracted it,plugged my phone in via usb (made sure it was in debugging mode) and then clicked "RUN AS ADMINISTRATOR" on the actual SOC icon. It brought up the box and I clicked "ROOT". It scrolled and it looked like it was going well until step 7 where it hangs and just states "WAITING FOR DEVICE".I gave it some time but after an hour of it not changing from this,I guessed that something was wrong. Then when I try and click on the window,it becomes unresponsive and I have to force close it.
I have searched for solutions to this,one forum even suggested that I download an older version of SOC which I did. But it pretty much did the same thing,just a different message.
As I said,all I want to do is delete these apps so if anyone can shed some light on the problem I am having and how I can actually root the phone in the most simplest terms (talk to me as if I was your Nan!) then I would be very grateful.
Thank you for your time
Crystal
You should probably move this to the HTC sensation XL thread. This is only the HTC sensation/4g/XE thread. I'm sure there are more people who can help you out if you post in that thread...
Sent from my HTC Sensation
Do NOT use any methods of rooting or anything else that you find in this forum. Like the post above says, this forum is for the Non XL Sensation. This is a different device with different processes. Using regular Sensation methods on an XL stands a real good chance of bricking your device.
Sent from your phone. You should be careful where you leave that thing.
Skipjacks said:
Do NOT use any methods of rooting or anything else that you find in this forum. Like the post above says, this forum is for the Non XL Sensation. This is a different device with different processes. Using regular Sensation methods on an XL stands a real good chance of bricking your device.
Sent from your phone. You should be careful where you leave that thing.
Click to expand...
Click to collapse
Ah thank you very much! I couldn't find the forum for the XL so I assumed that this would be the only one. Shall try to find it now.
Hello everyone. New to the forum, figured this would be the best place to ask since every guide I've ever looked up has inevitably brought me here at some point or another. Thanks to everyone that takes the time to post all of those guides/answers out there for people like me. Much appreciated.
Now, my current predicament- I told an older friend from work that I would help him get into his phone, and it's proving to be a more complicated process than I originally thought. His very young granddaughter managed to changed the PIN and he can't get in the phone. He has a Verizon Galaxy S4 SCH-i545, with a PIN lock-screen after booting. Verizon told him they would have to wipe/reset the phone to unlock it, which he's trying to avoid, so he held on to it and asked me about it. Knowing anything's possible, I accepted the mission.
After a bit of browsing, I came across a YouTube video of 2 simple ADB commands that reset the passkey file, thought I'd be done in 5 seconds. But the thing is- to do that, as well as to follow pretty much every guide I come across, USB debugging must be enabled, which I can't get to obviously. I'm pretty good with computers but the mobile-realm is somewhat new to me, so I began setup + research. So far I've installed the Java and Android SDKs, as well as the mobile drivers, started reading a bit about ADB, searched and read through numerous guides about alternate methods of enabling USB-debugging. But I keep finding guides that either aren't quite exactly what I'm looking for, or they assume a level of experience that I just don't have yet.
I'm in school full-time and work full-time, and as much as all of this interests me and I'd love to spend a week or two figuring everything out, I really don't have the time unfortunately. If someone could maybe list some clear steps from the beginning on how to enable USB debugging on a locked phone, or the easiest way to go about unlocking the phone without resetting it and deleting everything, I'd be forever grateful.