Database Users

One click root

So I can't root my nexus s I don't know why I have had all the great androids since day one but this baby wont budge. Will any of those one.click apps work never tried one?
Sent from my Nexus S using XDA App

dskyers said:
So I can't root my nexus s I don't know why I have had all the great androids since day one but this baby wont budge. Will any of those one.click apps work never tried one?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
There's no one click method I know of for the Nexus S.
What do you mean you can't root & it won't budge? This phone is about as easy they come (without some one click app): http://forum.xda-developers.com/showthread.php?t=931865
Install the android sdk on your computer.
Put the su.zip file on your sdcard partition of the phone.
Put the phone in fastboot mode.
Fastboot flash the recovery.
Select recovery.
Select install zip from sdcard.
Flash it.
Reboot.
You're done.

If your computer doesn't recognize the phone while it's in the bootloader, you gotta install the google Nexus S drivers or the one from PDAnet. That was where I got stuck at 1st when I tried rooting. Fastboot couldn't find my phone because I had the generic windows drivers.

Also if you have PDANet on, turn it off before putting your phone in fastboot mode.

Actually there is a one click method...brb with it
http://www.theandroidsoul.com/easy-one-click-root-for-nexus-s-full-guide/
Or search superboot nexus s
Here on xda
Either will work PC or mac.
Sent from my Nexus S using XDA App

vapor311 said:
Actually there is a one click method...brb with it
http://www.theandroidsoul.com/easy-one-click-root-for-nexus-s-full-guide/
Or search superboot nexus s
Here on xda
Either will work PC or mac.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Interesting. So the steps on the referenced one-click method you posted are:
1) put your phone in fastboot
2) do the fastboot oem unlock command manually.
3) run a batch file that contains two lines (fastboot-windows.exe flash boot boot.superboot.img & fastboot-windows.exe reboot).
I guess that's easier than putting your phone in fastboot directly and typing in a command to flash clockwork, then selecting a zip file to install from clockwork, but not much.
The drawbacks here are of course that it's superboot, and that it requires you to unlock the bootloader. I guess it's useful if you're really noob, but it only saves you typing one command.

The noob part is very true. However I prefer my bootloader unlocked anyhow.
Sent from my Nexus S using XDA App

vapor311 said:
The noob part is very true. However I prefer my bootloader unlocked anyhow.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Why do you prefer it unlocked?

I like the unlocked lock! No seriously custom roms etc.
Sent from my Nexus S using XDA App

main reason i think there is no one click root is because its so simple to do on this phone

vapor311 said:
I like the unlocked lock! No seriously custom roms etc.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
You do not need an unlocked bootloader (currently) to use custom roms, or to root, or to flash clockwork recovery, etc...

On day one that wasn't a known entity.
Sent from my Nexus S using XDA App

vapor311 said:
On day one that wasn't a known entity.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Of course, but since you contradicted my statement earlier that one disadvantage to the posted method here was that it had you unlock the bootloader by replying that you like having yours unlocked, I was trying to pin down if there was an advantage to unlocking the bootloader that had been discovered that I hadn't heard yet.
There's indication on git for our phone that the next update includes a change to the bootloader being able to use the fastboot boot command while locked. Unknown what that will actually do in terms of just fastboot flashing clockwork to apply root and custom roms.

I c wut u did there. I'm not sure how the update is going to affect things ATM. I keep it unlocked for "in case sh*t" happens. Never know what an update will bring in changes to rom management.
Sent from my Nexus S using XDA App

Perm Root not working

I followed multiple steps for installing perm root on a friends Mytouch and for some reason we could not get the s-off feature to work. I noticed too we do have SU access via adb or terminal but I still never could get s-off. After we got root we used rom manager to install clockwork and after the fact it installed 3.0.2 i believe it completely borked the recovery. I stepped it down to 3.0.0 and still had the same issue. The main reason i wanted to get s-off was to adb flash the recovery but I got a signature fail. Any ideas or suggestions to get this working correctly? Rom Manager will not let me install 2x cwm basically stating it can not install it period. I also tried the batch file root method same issue. Thanks for your help in advance.

Please look at the "True permaroot and S-OFF" thread in Development section, and execute step-by-step.
If your friend's MT4G is running Gingerbread (Android 2.3.3), you'll need to use Gingerbreak instead of Visionary+ to get root access.

Its on froyo and i followed that guide i have perm root but we can not get s off. I can use root access for any programs
Sent from my SGH-T959V using XDA App

dynamicj said:
Its on froyo and i followed that guide i have perm root but we can not get s off. I can use root access for any programs
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
If you are following the ./gfree method step by step it will root your phone.
If you are using the root.sh script and it's not working chances are you may have a bad eMMC chipset and it will not root properly.
I know HTC said they would be pushing a update to close the exploit hole that is used to root our phones but i don't think it's been pushed yet.

Im not sure but it said something about not being able to back up partition or something but either way nice HTC is becoming a motorola nice
Sent from my SGH-T959V using XDA App

dynamicj said:
Im not sure but it said something about not being able to back up partition or something but either way nice HTC is becoming a motorola nice
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
HTC isn't "becoming a Motorola". HTC, is completely different. We do have a locked bootloader. But it's easily unlock-able whereas Moto's aren't.

Its still not accepting the soff root which i am baffled at and with a broken recovery i need to know what to do now. Recovery just shows pc-cell logo
Sent from my SGH-T959V using XDA App

dynamicj said:
Its still not accepting the soff root which i am baffled at and with a broken recovery i need to know what to do now. Recovery just shows pc-cell logo
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
I don't know what to tell you. There are several threads out there regarding how to root your phone. Both in a .gfree form and a root.sh form. One of those 2 work for 99.9% of EVERYONE.

You might try finding someone who put together a .zip that can be flashed through the android recovery(white screen with boot options, etc.). Otherwise you can get the RUU and return to stock. After that follow the directions step by step and DO NOT mix methods. This should result in an S-OFF root, if you did your homework correctly.
Sent from my Shift CM7 using XDA app

I did several methods via adb .sh file and .g i have root in the os Rom manager even installed cwm but i can't get into cwm i get that image.... So still lost as nothing is working on this phone for s off
Sent from my SGH-T959V using XDA App

dynamicj said:
I did several methods via adb .sh file and .g i have root in the os Rom manager even installed cwm but i can't get into cwm i get that image.... So still lost as nothing is working on this phone for s off
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
Until you have "s-off" no recovery image will stick.

Obviously why i posted here to get insight anyways ill just redo it for the 5th time maybe it will work....
Sent from my SGH-T959V using XDA App

dynamicj said:
Obviously why i posted here to get insight anyways ill just redo it for the 5th time maybe it will work....
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
What method are you using?

I have tried them all
Sent from my SGH-T959V using XDA App

dynamicj said:
I have tried them all
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
What errors are you getting?

Just can not get it to go soff i have root in the device otherwise. Recovery also just shows a computer and cell phone icon after Rom manager install clockwork mod 3x. I am just trying to adb install a older cwm.
Sent from my SGH-T959V using XDA App

As someone already explained before, when the security is on, no matter the amount of flashing you're going to try - it won't get you anywhere, since it won't be written to the actual ROM, and will be gone on restart.
Unless you pick a guide, follow it exactly, and post here everything that doesn't look proper - I don't think the forum can help you much.
Here's one:
http://forum.xda-developers.com/showthread.php?t=858996
Follow it and post anything that doesn't look good. Including your bootloader version.

The root is sticking on reboots but still no soff that's what i have been saying and i followed the guides to a t its not my first picnic rooting or roming a phone this one just has me stumped
Sent from my SGH-T959V using XDA App

What does your bootloader show when you boot into it?
For the root to stick after boot, you had to have S-OFF, otherwise the eMMC wouldn't have been written to.
Having no info from you, as I said, it's impossible to help. If all this thread is just a complaint - by all means, but in that case there's no point in helping you. If you want help - you need to provide enough details for people to help you. Obviously, nobody can figure out anything from "I can't get s-off".

I do a adb reboot bootloader and i get us fast boot up top it says s-on but if i reboot to the os i still have root access for instance in titanium backup or Rom manager of that helps any
Sent from my SGH-T959V using XDA App

Oops! I changed LCD Density and now will not boot up.

Hey Everyone,
So I was being impatient and wanted to change the Density of my LCD on my Nexus 7. I changed it from the stock DPI to 170 using LCD Density Modder on the Market. Ever since reboot I have not been able to get past the google screen when you first turn on device. I can get into bootloader as well. My bootloader is unlocked and device is rooted if that helps.
Is there any easy way to recover the device besides a adb, or fastboot method? If not, what are the adb, fastboot commands to flash the OTA image to device from my PC?
Thanks

Download the nexus root toolkit, it can turn everything stock.
Sent from my LG-P999 using xda app-developers app

I have the nexus root toolkit, but don't you need the device powered on to put in usb debugging mode, etc? All I can do is hit google splash screen and get into bootloader, recovery.

There's buttons that say revert to stock, I believe those work in recovery.
Sent from my LG-P999 using xda app-developers app

redmonke255 said:
Download the nexus root toolkit, it can turn everything stock.
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
+1 just unlock and reflash
Sent from my i777 using xda app-developers app

Whenever I try to flash stock + unroot I get error message, "Windows cannot find 'C:\\data\gnexwug_DLnX.exe'. Make sure you typed the name correctly, and then try again."
Im not trying to type in anything, all I am doing is trying to restore to stock.

did you make a nandroid backup?" i am goign through the same thing right now. I am goign to restore from backup.
To change the desinty, it must be manually done in build.prod i assume. LCD Density modder might not be compatible, yet.
edit: Crap, i cant boot to recovery for some reason :/
edit2: it seems the only way to boot into recovery now is from a ROM manager application. Ijust finished restoring using the Nexus Toolkit.

I finally figured how to get SDK going and restored via nexus root toolkit. Thanks guys!
Sent from my Nexus 7 using xda app-developers app

mheller91 said:
I finally figured how to get SDK going and restored via nexus root toolkit. Thanks guys!
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Hi,
I stupidly did the same thing and am now in the same situation. :crying:
Can you tell me how you finally got it sorted?
Cheers

damienleetobin1976 said:
Hi,
I stupidly did the same thing and am now in the same situation. :crying:
Can you tell me how you finally got it sorted?
Cheers
Click to expand...
Click to collapse
Personally,
i booted into fastboot (all buttons if i remember correctly), then hit up the Tool Kit, go to advanced > temporary recovery, From there, i just restored my nandroid backup, or if you have any roms on there, just flash that.
You could do that, or once in fastboot and connected, you could just unlock, which will wipe everything.

tremblingwater said:
Personally,
i booted into fastboot (all buttons if i remember correctly), then hit up the Tool Kit, go to advanced > temporary recovery, From there, i just restored my nandroid backup, or if you have any roms on there, just flash that.
You could do that, or once in fastboot and connected, you could just unlock, which will wipe everything.
Click to expand...
Click to collapse
Hi,
I tried this and went for the Unlock route but after a restart it now just seems to be stuck at the google splash screen.
Is it usual to take this long?
Cheers

So what program is everyone using to change the DPI without getting a black screen?
Sent from my Nexus 7 using xda premium

theusername said:
So what program is everyone using to change the DPI without getting a black screen?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Just using a file explorer (specifically, solid explorer but root explorer should also work), navigating to /system/build.prop, and changing the number ro.sf.lcd_density.
changing that particular number's easy, and the last app I tried somehow managed to make a second build.prop inside the same file. So yeah.
Don't forget to backup your build.prop (preferably externally as well, in case you need to flash it) before trying this. And/or make a nandroid.

damienleetobin1976 said:
Hi,
I tried this and went for the Unlock route but after a restart it now just seems to be stuck at the google splash screen.
Is it usual to take this long?
Cheers
Click to expand...
Click to collapse
Im not sure, i dont want to advise something that is wrong, but, no, it doesn't take extraordinarily long. How long has it been?
I would boot into fastboot again and try the other route (provided you have a rom on the device or hopefully, better yet, a nandroid)

If you're using the cwm recovery from the toolkit you must be plugged in to usb to access cwm from the bootloader menu. From there you can reflash whatever you want to fix it.

jamesbra said:
If you're using the cwm recovery from the toolkit you must be plugged in to usb to access cwm from the bootloader menu. From there you can reflash whatever you want to fix it.
Click to expand...
Click to collapse
Yep, this is how it got it back and running last night.
I then used root explorer to edit build.prop and it worked like a charm.
Thanks all

HELP! I think I bricked my nexus 7. [SOLVED]

After i tryed flashing kaos droid i think ive managed to brick my nexus 7. It just boots into cwm v6.0.1.0. Ive tryed a number of times holding down the power and the volume buttons together and i CANT get into the bootloader ): . No matter what i do it just boots into the recovery even if i flash another rom it goes back to cwm. I dont know what to do please help? I cant even shut the screen off its been in cwm for over 3 hours now \:
And i was rooted and unlocked before this. Tab was working fine till i flashed kaos droid
Sent from my myTouch 4G Slide using Tapatalk 2

Just use recovery to restore your backup.
Sent from my Nexus 7 using xda premium

This is about the 15th post I've seen this week about someone screwing up their n7. If there already isn't one there needs to be a step by step video for the correct way to unlock, root, and flash Roms. I suggest others read heavily before doing any flashing. Its bad enough the boot loader is already screwy.

The toolkit does everything for you. All in one method and you're done.
I'm sure its his .img
Sent from my Nexus 7 using xda premium

I had this problem happen with my Xoom.
Boot into the bootloader from recovery. There should be an option to do so.
In the bootloader flash a different recovery.
Then reinstall your ROM. It should boot.
If that doesn't work I would suggest flashing the stock images in fastboot and starting over.
Sent from my Nexus 7 using xda premium

El Daddy said:
I had this problem happen with my Xoom.
Boot into the bootloader from recovery. There should be an option to do so.
In the bootloader flash a different recovery.
Then reinstall your ROM. It should boot.
If that doesn't work I would suggest flashing the stock images in fastboot and starting over.
I will try using the toolbox but i dont think i have access to fastboot from the recovery? I mean im telling you guys my screen has been on for over 4 hours because it just reboots and wont turn off.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I can not boot into the bootloader my nexus 7 boots directly into cwm. I tryed wiping caches, wiping system, formating everything, restoring a nandroid, flashing another rom..... Nothing is working
When i get home. To my computeer im going to try using the toolkit hopefully it works
Sent from my myTouch 4G Slide using Tapatalk 2

nemesis93 said:
I can not boot into the bootloader my nexus 7 boots directly into cwm. I tryed wiping caches, wiping system, formating everything, restoring a nandroid, flashing another rom..... Nothing is working
Sent from my myTouch 4G Slide using Tapatalk 2
Click to expand...
Click to collapse
I had a similar problem on my og evo. Try seeing if you can flash the recovery from a computer while booted into cwm. Then it'll reboot into new recovery, you flash rom, and you stop sharding your pants

nemesis93 said:
I can not boot into the bootloader my nexus 7 boots directly into cwm. I tryed wiping caches, wiping system, formating everything, restoring a nandroid, flashing another rom..... Nothing is working
Sent from my myTouch 4G Slide using Tapatalk 2
Click to expand...
Click to collapse
Even choosing "reboot bootloader" in recovery?
If that doesn't work, connect to you your computer and using adb type the command
Code:
adb reboot bootloader

kieso said:
This is about the 15th post I've seen this week about someone screwing up their n7. If there already isn't one there needs to be a step by step video for the correct way to unlock, root, and flash Roms. I suggest others read heavily before doing any flashing. Its bad enough the boot loader is already screwy.
Click to expand...
Click to collapse
And to you sir I have read and watched other videos/tutorials whatever you may call them. I post on here as a last resort when "i dont know what to do". I cant understand people who post but dont really have nothing helpful to say about the topic. All im asking for is some help please and thank you
Sent from my myTouch 4G Slide using Tapatalk 2

El Daddy said:
Even choosing "reboot bootloader" in recovery?
If that doesn't work, connect to you your computer and using adb type the command
Code:
adb reboot bootloader
Click to expand...
Click to collapse
I dont have a reboot bootloader option but when i go to reboot system it goes straight into cwm like i said.
Also fastboot/adb is not working. When i run a command it says "waiting for device" on my computer
Sent from my myTouch 4G Slide using Tapatalk 2

On a side note, i had tryed everything i formated the sd in cwm and now it appears on cwm as if theres "No files found" but on my computer everything i had previously is still there.
So there is a connection to the storage part of the device but not adb or fastboot
Sent from my myTouch 4G Slide using Tapatalk 2

nemesis93 said:
I dont have a reboot bootloader option but when i go to reboot system it goes straight into cwm like i said.
Also fastboot/adb is not working. When i run a command it says "waiting for device" on my computer
Sent from my myTouch 4G Slide using Tapatalk 2
Click to expand...
Click to collapse
Hmmm. You should have a working adb while booted into a custom recovery. Are your drivers installed correctly?
Also, the reason why you computer sees the files is because with mtp it caches the files.
Sent from my Nexus 7 using xda premium

El Daddy said:
Even choosing "reboot bootloader" in recovery?
If that doesn't work, connect to you your computer and using adb type the command
Code:
adb reboot bootloader
Click to expand...
Click to collapse
So far i got adb to work finally! Happy im making some progress.
Now im able to boot into the bootloader so i can run fastboot commands. I currently have NO rom whatsoever installed so im waiting to flash the stock rom using the toolkit. Thank you for your help
Also when i booted into twrp it said i had 3% battery left lol so im just hoping it will work now.
Sent from my myTouch 4G Slide using Tapatalk 2

OP will stop making threads like this if people stop recommending toolkits......................
And definition of brick is beyond repair - unable to boot up, e.g. Black screen when power button is pressed, not even the Google screen.
Will the next nexus have a longer screen?

Mach3.2 said:
OP will stop making threads like this if people stop recommending toolkits......................
And definition of brick is beyond repair - unable to boot up, e.g. Black screen when power button is pressed, not even the Google screen.
Will the next nexus have a longer screen?
Click to expand...
Click to collapse
Well it was beyond repair for the moment being if i did NOT have access to adb, fastboot, nor the Bootloader i said that three times already.
But whatever i finally got adb to work and was able to fastboot flash a stock image. Thank you so much el daddy for your help i really appreciate it.
Sent from my myTouch 4G Slide using Tapatalk 2

nemesis93 said:
Well it was beyond repair for the moment being if i did NOT have access to adb, fastboot, nor the Bootloader i said that three times already.
But whatever i finally got adb to work and was able to fastboot flash a stock image. Thank you so much el daddy for your help i really appreciate it.
Sent from my myTouch 4G Slide using Tapatalk 2
Click to expand...
Click to collapse
No problem. I'm glad you got it to work.
And thank you for flashing with fastboot and not a toolkit
Sent from my Nexus 7 using xda premium

El Daddy said:
No problem. I'm glad you got it to work.
And thank you for flashing with fastboot and not a toolkit
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Yeah i tryed at first because i was lazy and it didnt work so i did it through fastboot.
Thanks again
Sent from my myTouch 4G Slide using Tapatalk 2

Glad you got it working

nemesis93 said:
And to you sir I have read and watched other videos/tutorials whatever you may call them. I post on here as a last resort when "i dont know what to do". I cant understand people who post but dont really have nothing helpful to say about the topic. All im asking for is some help please and thank you
Sent from my myTouch 4G Slide using Tapatalk 2
Click to expand...
Click to collapse
Sorry I wasn't trying to bust your stones. I haven't rooted yet because of all of the posts like yours. I've just seen more problems with flashing on this device then any other that I have with my past Droid devices. What we really need is apx (spelling?) Drivers and n7 files for a sure fire recovery from any disaster

Hopefully I don't have to start another thread.
I too think I bricked my Nexus 7.
I was having trouble and I accidentally cleared a file from the System UI app (its a system required app) which caused me to loose the 3 buttons on the bitten of the screen.
So I went to CWM to do a restore which said it failed.
After that it would not boot.
Its just stuck with the Google logo on the screen.
I held down the power up & down volume buttons and I get a screen that gives me that START button on the top right of the screen with the text in small size on the bottom left.
I can use the up and down volume to make the start button change to recovery mode or bootloader but activating them just goes to Google logo.
Can I recover or is it totally lost?
I also don't remember if I left the Nexus 7 in Debug mode which is usually required to perform custom Roms
Thanks
Rob
Sent from my SPH-D710 using Tapatalk 2

Phone reboots into TWRP

well I have been having problems on how to do unlock my phone using a Mac, but I was finally able to unlock it and flash TWRP recovery by using mattlgroff's utility 1.20 now the I have installed TWRP recovery, every time I connect my phone to the Mac it asks me superuser permission for AdB shell I grant permission and it says "Adb shell has been granted permission" and it reboots into TWRP recovery. I even denied superuser permission but it still does the same thing. I have USB debugging on.
is this normal? because I need to transfer some files to my phone so I can Flash a Rom through TWRP. I would really appreciate your help. thanks.
here's a picture attached showing what it says as soon as I connect the phone to computer.
after that it just reboots into TWRP.

Are you on stock rom?
Sent from my Galaxy Nexus using xda premium

denisjr said:
Are you on stock rom?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yeah I'm on stock Rom 4.1.2

Try using air DROID & maybe using a different rom will do it
Sent from my Galaxy Nexus using xda premium

denisjr said:
Try using air DROID & maybe using a different rom will do it
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I fixed it! I had to reset my Mac's SMC, apparently it kept flashing TWRP every time I connected my phone to the computer.
thanks for being helpful anyways !