root nexus s build GRI40 v. 2.3.3 - Nexus S Q&A, Help & Troubleshooting

hi... with the upgrade to 2.3.3 i lost root!!! any ideas? thanks

Flash recovery via fastboot, mount system,flash su.zip,unmount system. Work for me on 2.3.3.

jtoxx said:
Flash recovery via fastboot, mount system,flash su.zip,unmount system. Work for me on 2.3.3.
Click to expand...
Click to collapse
hi, how to run fastboot on the new bootloader?

There are many, many guides in the development section on how to root. You can find a list of those guides at the beginning of this post:
http://forum.xda-developers.com/showpost.php?p=11380101&postcount=1

Related

[Q] Nexus S I9020A: Has Anyone Successfully Rooted Device?

I am at my wits end.
I have tried for the better part of a day to root my i9020A (Android 2.3.4, KD1, GRj22).
Has anyone successfully gained root?
If so, could you point me in the right direction.
PS. I will appreciate help from someone who has actually done this (I9020A).
Thanks.
Is your bootloader unlocked, if so then you have to flash clockwork recovery, by using fastboot mode through sdk android software, through your computure. You can get the recovery file and root file in general forum. In the general forum, there is a guide there as well and you can also go to youtube as well.
It's fairly simple - this applies to all of the versions of the Nexus S:
Boot into bootloader - fastboot oem unlock (this wipes)
Flash custom recovers
Mount /system
flash SU binary through recovery
On reboot the recovery will be overwritten with stock. To prevent this rename / delete /etc/install-recovery.sh
pterry30 said:
Is your bootloader unlocked, if so then you have to flash clockwork recovery, by using fastboot mode through sdk android software, through your computure. You can get the recovery file and root file in general forum. In the general forum, there is a guide there as well and you can also go to youtube as well.
Click to expand...
Click to collapse
My bootloader is locked.
I cannot get my device to recognize the USB drivers.
I tried both Android SDK & Samsung USB Mobile drivers
I had to use the junefabrics driver. Shabby has a one click that does most of it and provides the adb driver
Sent from my Nexus S 4G using XDA App
pterry30 said:
Is your bootloader unlocked, if so then you have to flash clockwork recovery, by using fastboot mode through sdk android software, through your computure. You can get the recovery file and root file in general forum. In the general forum, there is a guide there as well and you can also go to youtube as well.
Click to expand...
Click to collapse
aritafari said:
My bootloader is locked.
I cannot get my device to recognize the USB drivers.
I tried both Android SDK & Samsung USB Mobile drivers
Click to expand...
Click to collapse
Phew! Finally
I was able to unlock my bootloader (used pdanet).
If at first you don't succeed, try and try again.
pterry30 said:
Is your bootloader unlocked, if so then you have to flash clockwork recovery, by using fastboot mode through sdk android software, through your computure. You can get the recovery file and root file in general forum. In the general forum, there is a guide there as well and you can also go to youtube as well.
Click to expand...
Click to collapse
agree with pterry30
aritafari said:
Phew! Finally
I was able to unlock my bootloader (used pdanet).
If at first you don't succeed, try and try again.
Click to expand...
Click to collapse
Can you explain please...

[Q] ROM Installation

I found a rom for the NS, based on build GRI40, rooted, deodexed etc, downloaded the zip file and now I have a problem. I'm running stock rom at the moment and from what I've read so far, I should be able to put the zip file on the usb drive, boot into recovery and simply select the new rom.
Is this accurate? Would my phone be rooted after this, even though the bootloader wasn't unlocked prior to this operation? Thanks and sorry for being a noob
flodb113 said:
I found a rom for the NS, based on build GRI40, rooted, deodexed etc, downloaded the zip file and now I have a problem. I'm running stock rom at the moment and from what I've read so far, I should be able to put the zip file on the usb drive, boot into recovery and simply select the new rom.
Is this accurate? Would my phone be rooted after this, even though the bootloader wasn't unlocked prior to this operation? Thanks and sorry for being a noob
Click to expand...
Click to collapse
You'll have to unlock its bootloader and root your phone prior to flashing a custom ROM
How to Root Android 2.3.3 Gingerbread on Nexus S? [Complete Step-by-Step Guide]
http://jaxov.com/2011/02/how-to-root-android-2-3-3-gingerbread-on-nexus-s/
Click to expand...
Click to collapse
Or you can also root your phone using 1-click method:
http://forum.xda-developers.com/showthread.php?t=1138755
Click to expand...
Click to collapse
Pick and choose a method you like!
Oh I thought there was a way to get pass the root procedure. Thank you for clearing things up for me.
You don't need root to flash custom roms. Just an unlocked bootloader (and a custom recovery if you flash unsigned roms).
Sent from my Nexus S using XDA App

How to root Xoom with Android 4.1.1?

I have looked all over the forums and I can not find it. All the forums show how to root a Xoom with Honeycomb or Ice Cream Sandwich TO Jellybean, but what if i already have JellyBean? I just want to get superuser access onto the stock Jellybean ROM and Kernel.
This Link:
http://forum.xda-developers.com/showthread.php?t=1796335
Has been the most useful so far, but even it only roots Ice Cream Sandwich.
How do I root Android 4.1.1 on my Motorola Xoom with 4.1.1.
This should work! Flash it in recovery
What do I need?
matt4321 said:
This should work! Flash it in recovery
Click to expand...
Click to collapse
Do I need to have clockwork mod installed or anything, i have done NOTHING root to my xoom. I rooted my HTC EVO 4G. But i havent flashed a recovery, installed a ROM, No SU, NOTHING. So what exactly should i do with your zip?
Use instructions and tools in http://forum.xda-developers.com/showthread.php?t=1468298 to get Clockwork installed, and then use the modded zip that matt4321 posted (I think that should work... )
Yeah use the AIO tool to unlock your bootloader, then you want to install CWM recovery, then boot into recovery and flash the zip I uploaded
I used this exact process (ended up just GEDify'ing it after sending it back to stock), but before I did that everything worked fine.
Thank you!
I'm too junior to get a Thanks button, so thank you to matt4321 for the JB universal XOOM root, to airesch for leading me too XxLordxX's link and of course to XxLordxX for the tools and instructions to get my XOOM rooted! Worked perfect on my XOOM WIFI JRO03H with no problems. You guys are the best!:good:
stuck on Starting Fastboot Protocol Support - Xoom Android 4.1
I'm trying to follow the directions to install ClockworkMod Recovery
http://forum.xda-developers.com/showthread.php?t=1074979
I'm using Recovery Image (solarnz-R4c-100611-1150) FLASHED THROUGH FASTBOOT
MD5: 20575d4b62bf697f77abca9093877ea3
and following the procedure for "Method 2 Without CWM"
I got as far as entering the code: adb reboot bootloader
The Xoom rebooted and the Motorola logo appears with the message "Starting Fastboot Protocol Support"
It's just stuck there.
The volume up/down buttons don't do anything at this point.
Any ideas?
thanks!
themonman said:
I'm trying to follow the directions to install ClockworkMod Recovery
http://forum.xda-developers.com/showthread.php?t=1074979
I'm using Recovery Image (solarnz-R4c-100611-1150) FLASHED THROUGH FASTBOOT
MD5: 20575d4b62bf697f77abca9093877ea3
and following the procedure for "Method 2 Without CWM"
I got as far as entering the code: adb reboot bootloader
The Xoom rebooted and the Motorola logo appears with the message "Starting Fastboot Protocol Support"
It's just stuck there.
The volume up/down buttons don't do anything at this point.
Any ideas?
thanks!
Click to expand...
Click to collapse
Here, detailed procedure with snapshots.
http://forum.xda-developers.com/showthread.php?p=29733454
N00b tutorial: Flashing EOS3 to MZ604 Xoom (Wifi)
Hi,
thanks for the url.
One problem.
And the most important, download EOS-RECOVERY-V6, the "recovery software" that will allow you to work without the need of the PC:
Recovery Image: http://goo.im/devs/teameos/recoveries/wingray/eos-recovery-r6.img
This link goes to a file not found page.
Any update on where I can get that file?
thanks!
wesamothman said:
Here, detailed procedure with snapshots.
http://forum.xda-developers.com/showthread.php?p=29733454
Click to expand...
Click to collapse
themonman said:
Hi,
thanks for the url.
One problem.
And the most important, download EOS-RECOVERY-V6, the "recovery software" that will allow you to work without the need of the PC:
Recovery Image: http://goo.im/devs/teameos/recoveries/wingray/eos-recovery-r6.img
This link goes to a file not found page.
Any update on where I can get that file?
thanks!
Click to expand...
Click to collapse
You have to use another recovery. Eos-r6 was abandoned and another recovery came in as the perfect one. TWRP recovery
http://forum.xda-developers.com/showthread.php?p=28988754
matt4321 said:
This should work! Flash it in recovery
Click to expand...
Click to collapse
Matt,
Is this file appropriate for the WiFi only Xoom?
I installed TWRPv2.8.0.0-Wingray-Non-BigPart on my Xoom. That process went flawlessly.
I used TWRP to install "vanilla" Xoom-Universal-Root.zip. This also appeared to go flawlessly.
However, various root checker apps tell me I do NOT have root.
Please, any suggestions? I ultimately want to get to BigPart but I'm stuck at this point.
thanks,
Dave
vronp said:
Matt,
Is this file appropriate for the WiFi only Xoom?
I installed TWRPv2.8.0.0-Wingray-Non-BigPart on my Xoom. That process went flawlessly.
I used TWRP to install "vanilla" Xoom-Universal-Root.zip. This also appeared to go flawlessly.
However, various root checker apps tell me I do NOT have root.
Please, any suggestions? I ultimately want to get to BigPart but I'm stuck at this point.
thanks,
Dave
Click to expand...
Click to collapse
Yeah, that zip should be good to root any Xoom on 4.1. I wouldn't bother sorting root if you want to go to bigpart as it wipes everything anyway.
Jump straight to bigpart, read read and read again this thread: https://forum.xda-developers.com/showthread.php?t=2506997
Once that is all sorted and booted, I think you should be good to just flash whatever root tool you want (SuperSU, phh superuser etc)
My memory is rusty on all this though, I haven't messed with my xoom in a long time and you quoted a post over 4 years old lol

[Q] Root and Custom recovery not sticking...

curious if there is something i'm missing here... i've unlocked my bootloader successfully but whenever i fastboot flash a recovery or flash root files in recovery nothing seems to stick... not sure whats going on... i've heard of having to flash recovery everytime on devices with a locked bootloader but i didn't think that would apply here... any help is much appreciated... (this is also my first samsung/nexus device so i'm more familiar with methods used on the EVO line)
thispaininmyhead said:
curious if there is something i'm missing here... i've unlocked my bootloader successfully but whenever i fastboot flash a recovery or flash root files in recovery nothing seems to stick... not sure whats going on... i've heard of having to flash recovery everytime on devices with a locked bootloader but i didn't think that would apply here... any help is much appreciated... (this is also my first samsung/nexus device so i'm more familiar with methods used on the EVO line)
Click to expand...
Click to collapse
Make sure you're using a perm root method. and make sure you have the correct updated SU application. My root wouldn't come through because I didn't have the latest SU.
Hopefully I helped.
thispaininmyhead said:
curious if there is something i'm missing here... i've unlocked my bootloader successfully but whenever i fastboot flash a recovery or flash root files in recovery nothing seems to stick... not sure whats going on... i've heard of having to flash recovery everytime on devices with a locked bootloader but i didn't think that would apply here... any help is much appreciated... (this is also my first samsung/nexus device so i'm more familiar with methods used on the EVO line)
Click to expand...
Click to collapse
Hi,
What root method did u use?
What recovery are u using?
What ROM are u flashing?
The more info, the better
Vs Nexus S4G using tapatalk2
Unlocked the boot loader with fast boot commands then flashed superuser.zip with clockwork 3.x.x and twrp 2.2.0 haven't tried flashing any Roms since nothing seems to stick...
Sent from my Nexus S 4G using Tapatalk 2
And Vidal I used the toolkit you linked me to in my last q&a post...
Sent from my Nexus S 4G using Tapatalk 2
vidaljs said:
Hi,
What root method did u use?
What recovery are u using?
What ROM are u flashing?
The more info, the better
Also after looking into the scripts and files in the method with the toolkit it seems none of the files get pushed to the device to begin flashing
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
By default, any recovery you flash on the system will be gone by the next reboot. This is a security measure the android os does I think.
1. You can flash a ROM. Anyone. I prefer aokp or cna. That way the recovery sticks (the recovery sticks on all the ROMs besides stock)
OR
P.S. You will need the latest cwm recovery
2. So all you need to do is to flash the recovery of your choice. I would recommend CWM for this short guide. Then once flashed go to the recovery make a backup. Then if it reboots flash the same recovery again. Boot into it and restore that backup. When you restore it and go reboot system now it should come up with a menu saying recovery flash fix (or something around those lines). Hit/navigate to yes and you should get a sticky recovery from there. BTW I have not tried this method.
You cannot blame me for bricking, damaging or done anything to your phone
Hope this helps.
Regards,
UselessSniper001
P.S. I don't know how root isn't sticking. I mean if you have flashed the su is the recovery already well then you are all set to go. Unless you haven't actually flashed the su in the recovery. Then flash the recovery from your PC boot into the recovery and flash the su files in the recovery. Reboot and enjoy. Then follow this guide above. Or follow this link:
http://forum.xda-developers.com/showthread.php?t=875875&page=2
I finally figured out the SU and CWM I was flashing was ancient so I found the newest and they stuck with help of the fix ya mentioned inside CWM... Thanks
Sent from my Nexus S 4G using Tapatalk 2

Downgrade or smth with firmware 5.18 (at&t one x, one xl)

Hey.
Need you help or advice..
I made a mistake when flashed my ATT One X with the latest firmware(
And now i can't do anything, I mean root or custom recovery.
I have S-OFF and super CID but I don't how to fix this.. to downgrade or to roll back to oldest firmware.
Even to have root will be perfect.
How can I manage this?
Thanks in advance!
vimev said:
Hey.
Need you help or advice..
I made a mistake when flashed my ATT One X with the latest firmware(
And now i can't do anything, I mean root or custom recovery.
I have S-OFF and super CID but I don't how to fix this.. to downgrade or to roll back to oldest firmware.
Even to have root will be perfect.
How can I manage this?
Thanks in advance!
Click to expand...
Click to collapse
According to your bootloader details you are at a good starting point. Here is what I recommend you do from here:
1. Download a custom recovery like TWRP:
http://forum.xda-developers.com/showthread.php?t=2558503
2. flash this in bootloader mode. If you don't know how here is the help thread you need to read through:
http://forum.xda-developers.com/showthread.php?t=2593382
3. Once you have a custom recovery installed, you can flash SuperSu or other root app (google is your friend.)
4. Stick with the rooted rom you have or flash another of your choosing.
Madcat8686 said:
According to your bootloader details you are at a good starting point. Here is what I recommend you do from here:
1. Download a custom recovery like TWRP:
http://forum.xda-developers.com/showthread.php?t=2558503
2. flash this in bootloader mode. If you don't know how here is the help thread you need to read through:
http://forum.xda-developers.com/showthread.php?t=2593382
3. Once you have a custom recovery installed, you can flash SuperSu or other root app (google is your friend.)
4. Stick with the rooted rom you have or flash another of your choosing.
Click to expand...
Click to collapse
Men.. thats great! Thanks a lot!
I was thinking its impossible to make root...
vimev said:
Men.. thats great! Thanks a lot!
I was thinking its impossible to make root...
Click to expand...
Click to collapse
Not impossible for you because your bootloader is unlocked and you are S-Off. You are always able to root and flash.
Hey, I have the same bootloader setup but i am unable to flash a recovery
Grinno said:
Hey, I have the same bootloader setup but i am unable to flash a recovery
Click to expand...
Click to collapse
What happens when you try to flash a recovery?
What recovery are you trying to flash?
Post your own bootloader (Don't show the IMEI)
Madcat8686 said:
Not impossible for you because your bootloader is unlocked and you are S-Off. You are always able to root and flash.
Click to expand...
Click to collapse
exad said:
What happens when you try to flash a recovery?
What recovery are you trying to flash?
Post your own bootloader (Don't show the IMEI)
Click to expand...
Click to collapse
I use EZT toolkit....It runs the commands then said fail (too many links
Grinno said:
I use EZT toolkit....It runs the commands then said fail (too many links
Click to expand...
Click to collapse
Why are you using a toolkit to flash recovery???
Just download from http://goo.im/devs/OpenRecovery/evita
or download the unofficial TWRP from the original android dev section if you plan on flashing an AOSP or CM based Rom and then fastboot flash recovery recovery_filename.img
Easy peasy. Too many links is an error that should have nothing to do with flashing recovery...
exad said:
Why are you using a toolkit to flash recovery???
Just download from http://goo.im/devs/OpenRecovery/evita
or download the unofficial TWRP from the original android dev section if you plan on flashing an AOSP or CM based Rom and then fastboot flash recovery recovery_filename.img
Easy peasy. Too many links is an error that should have nothing to do with flashing recovery...
Click to expand...
Click to collapse
Donno, Maybe fastboot/drivers or messed up. I keep getting cannot load 'recovery.img' unknown error
Grinno said:
Donno, Maybe fastboot/drivers or messed up. I keep getting cannot load 'recovery.img' unknown error
Click to expand...
Click to collapse
You need to type the filename of the recovery file you download. Either the recovery filename you are typing is wrong or the file is not in the folder you are trying to flash from.
exad said:
You need to type the filename of the recovery file you download. Either the recovery filename you are typing is wrong or the file is not in the folder you are trying to flash from.
Click to expand...
Click to collapse
Thanks, Got it to flash..... you were correct i was typing the filename wrong.

Categories

Resources