Hey guys need some help. Has anyone been able to root Sprint Nexus S 2.3.7 yet???
Got a new phone & it came preloaded with 2.3.7. I really want to root it but I haven't found anything about it. Many thanks if anyone can help me.
Sent from my Nexus S 4G using XDA Premium App
I'm pretty sure the one click still works if your feeling lazy.
Sent from my Nexus S 4G using Tapatalk
Are u speaking about the app or on pc?
Sent from my Nexus S 4G using XDA Premium App
treezy26 said:
Hey guys need some help. Has anyone been able to root Sprint Nexus S 2.3.7 yet???
Got a new phone & it came preloaded with 2.3.7. I really want to root it but I haven't found anything about it. Many thanks if anyone can help me.
Sent from my Nexus S 4G using XDA Premium App
Click to expand...
Click to collapse
Please understand how *all* Nexus devices work. You are free to unlock the boot loader at ANY time and flash whatever you want. All the "One Click Root" scripts do is automate the following process:
1.) Unlock the boot loader (fastboot oem unlock)
2.) Flash custom recovery (fastboot flash recovery recovery.img)
3.) Boot into recovery and flash the su zip package (installs the su binary into /system/xbin and chmod's it appropriately)
No update will *ever* break this process. With an unlocked boot loader you can flash whatever the hell you want (boot, userdata, system, recovery) and there's nothing at the OS level preventing that.
These "one click root" scripts just prevent anyone from learning what is actually happening (when it's actually quite simple) and lead to 20 threads like this each time an OTA drops.
krohnjw said:
Please understand how *all* Nexus devices work. You are free to unlock the boot loader at ANY time and flash whatever you want. All the "One Click Root" scripts do is automate the following process:
1.) Unlock the boot loader (fastboot oem unlock)
2.) Flash custom recovery (fastboot flash recovery recovery.img)
3.) Boot into recovery and flash the su zip package (installs the su binary into /system/xbin and chmod's it appropriately)
No update will *ever* break this process. With an unlocked boot loader you can flash whatever the hell you want (boot, userdata, system, recovery) and there's nothing at the OS level preventing that.
These "one click root" scripts just prevent anyone from learning what is actually happening (when it's actually quite simple) and lead to 20 threads like this each time an OTA drops.
Click to expand...
Click to collapse
Sadly 2.3.3 DID break root without unlocking the bootloader for those people who didn't want to have to deal with having their SD Card wiped.
Ive used one click root before just never for the nexus. I am new to this phone & just want to get everything right.
So i can use one click root on 2.3.7 with no problems?
I am very familiar with root on my previous phone (evo).
Like i said i just want to get all the angles down pat before i attempt this. Thank you for your time.
Sent from my Nexus S 4G using XDA Premium App
kenvan19 said:
Sadly 2.3.3 DID break root without unlocking the bootloader for those people who didn't want to have to deal with having their SD Card wiped.
Click to expand...
Click to collapse
That was never an intended function of fastboot for the device (to be able to boot a recovery) - it was a loophole that was closed. Unlocking the boot loader (and subsequently being able to flash whatever you want) is not going to be prevented.
treezy26 said:
Ive used one click root before just never for the nexus. I am new to this phone & just want to get everything right.
So i can use one click root on 2.3.7 with no problems?
I am very familiar with root on my previous phone (evo).
Like i said i just want to get all the angles down pat before i attempt this. Thank you for your time.
Sent from my Nexus S 4G using XDA Premium App
Click to expand...
Click to collapse
Yes, it should - at least look here (from the sticky in the NS4G development forum) so you know what it's going to do: http://forum.xda-developers.com/showthread.php?t=1078213
There aren't too many angles other than unlock your boot loader using fastboot (one command), flash a custom recovery (download it and flash it using one command) and then flash the su binary package. All downloads are in that thread.
krohnjw said:
That was never an intended function of fastboot for the device (to be able to boot a recovery) - it was a loophole that was closed. Unlocking the boot loader (and subsequently being able to flash whatever you want) is not going to be prevented.
Click to expand...
Click to collapse
Yes, it was a loophole but it was a nice loophole but you are correct. Nexus devices are the embodiment of Google's ideals for Android. There have been a number of google blog posts which state that Nexus devices are meant to be easy to unlock and install custom 3rd party software.
Related
So I traded my galaxy s 4g on craigslist about a month ago for a nexus s (t-mobile) which besides the 4g antenna is 100% better in every way possible. I absolutely love the phone. It came previously rooted which I was ok with. It is on 2.3.3. Not sure what method was used to gain root. Now that the backstory is done here is my dilemma:
I constantly get the update message. I guess I wouldn't mind so much if I could just get rid of the message but the problem isn't just that. I also want to be on the latest greatest version of android. So I've read a bunch of walkthroughs and various ways to update to the latest firmware on a custom rom like cm7 and keep the root, or un root and go to stock 2.3.3 and manually update to stock 2.3.4.
I need an opinion on which would be my easiest way (new to android previous iPhone jail breaker) to get to 2.3.4?
You cannot lose root on a nexus s. No matter the update you can always reroot as its a developer phone with an unlocked bootloader.
Sent from my PC36100 using XDA Premium App
Do the update
Download su.zip and the right cwm recovery image for your phone
Mount USB storage
Copy su.zip on sdcard and recovery image goes into /tools folder inside your adb/sdk folder on pc
Boot into fastboot, vol up+power
In a cmd prompt do 'fastboot devices' should return a number (this step is just to check if fastboot/adb is working properly)
'fastboot flash recovery recoveryimagename.img'
Choose recovery option on phone
Install su.zip from sdcard
Done
Sent from my Nexus S using XDA App
I forgot to mention that it will not take the update. I tried a bunch of times and it doesn't work, just gets locked up during the process.
Sent from my Nexus S using XDA App
stompincc said:
I forgot to mention that it will not take the update. I tried a bunch of times and it doesn't work, just gets locked up during the process.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
i'm pretty sure that's just cause you're on a custom rom. flash a stock rom and the update should work fine
Any problems with using one click root, after update?
Sent from my Nexus S 4G using xda premium
mentosone said:
Any problems with using one click root, after update?
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
It's the same as every other release.
- Flash custom recovery
- Use Custom recovery to flash SU binary
If your one click root script is automating that then it will continue to work without any issues. If it's not it's a fairly simple process...
mentosone said:
Any problems with using one click root, after update?
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
I went from a completely stock 2.3.5 to a rooted 2.3.7 using one click root v2. Now I'm running petes deodexed 2.3.7 ROM with no issues.
Thanks. I just got nexus s, was using g2x.soon as I get a chance I will root and flash recovery.
Sent from my Nexus S 4G using xda premium
O OK. But you did not update then root. U u updated to a rooted 2.3.7,right?
Sent from my Nexus S 4G using xda premium
mentosone said:
O OK. But you did not update then root. U u updated to a rooted 2.3.7,right?
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
It's irrelevant.
- Unlock the boot loader (fastboot oem unlock).
- You can now flash anything you want via fastboot (recovery, boot, userdata, etc). Flash a custom recovery (fastboot flash recovery recovery.img)
- Use said custom recovery to flash the su binary and chmod it appropriately
- Done
All the "One click root" scripts do is automate this process.
Unlike other Android devices the Nexus devices allow you to simply unlock the boot loader. You aren't relying on exploiting existing code on the device to gain elevated privileges in order to flash a new recovery/boot loader or place the su binary. Unlock the boot loader and do whatever the heck you want with it via fastboot - no update is going to break that.
Learn to USE your phone and do the manual root process. That way when you have an issue you will be familiar with the process of fixing your phone. Honestly it is the easiest phone to root.
Sent from my Nexus S 4G using xda premium
krohnjw said:
It's irrelevant.
- Unlock the boot loader (fastboot oem unlock).
- You can now flash anything you want via fastboot (recovery, boot, userdata, etc). Flash a custom recovery (fastboot flash recovery recovery.img)
- Use said custom recovery to flash the su binary and chmod it appropriately
- Done
All the "One click root" scripts do is automate this process.
Unlike other Android devices the Nexus devices allow you to simply unlock the boot loader. You aren't relying on exploiting existing code on the device to gain elevated privileges in order to flash a new recovery/boot loader or place the su binary. Unlock the boot loader and do whatever the heck you want with it via fastboot - no update is going to break that.
Click to expand...
Click to collapse
Thats all I needed to know thank you very much!
Sent from my Nexus S 4G using xda premium
hi everybody today i tried to update my HOX with this stock room "stock rooted 2.33.162.2 - odex/deodex and unsecure boot.img with init.d"
my android version is 4.0.4
HTC sense versio 4.0
Software Number 1.88.707.2
HTC SDK API level 4.11
HTC Extension Version 403_1_GA_4
then after i flashed the room the HTC wont boot (just shows me the white HTC screen) and i still have access to the recovery mode (CWM) i downloaded another room to tried to flash the phone (my nandroid bk shows me an MD5 error when i tried to restore) then i dont have any idea about how can i move the new zip file to the cellphone, i am very frustrated because i cant do it anything yet
please somebody help me
Thanks in advance for your help
If you get it working, the first order of business is to ditch CWM and switch to TWRP as it was not properly ported to our device. Are you sure you have a XL? The dual core version? Make sure you have the right ROM for the right device. I can't help you to transfer as you are using CWM and I'm not familiar with mounting. Word on the street is that there is a good chance it'll wipe your entire SDcard
Sent from my One X using xda premium
InflatedTitan said:
If you get it working, the first order of business is to ditch CWM and switch to TWRP as it was not properly ported to our device. Are you sure you have a XL? The dual core version? Make sure you have the right ROM for the right device. I can't help you to transfer as you are using CWM and I'm not familiar with mounting. Word on the street is that there is a good chance it'll wipe your entire SDcard
Sent from my One X using xda premium
Click to expand...
Click to collapse
thanks for your quickly response, well i have an AT&T HTC one X and yes its the dual core version, the phone comes with the CWM, unlocked and rooted, how can i install the TWRP ? because if i connect the phone to the computer doesnt shows me anything (i cane heard the tone when windows detect something new but its all) i tried to use odin but odin doesnt shows me anything and i tried with fastboot and adb but doesnt fount the device connected
from recovery do a factory reset and try again to boot it.... if u have a nandroid backup there is a setting to turn off md5 checking so it will restore......... as long as your using TWRP recovery (which you should be if not) you can mount usb storage and transer whatever you need......
18th.abn said:
from recovery do a factory reset and try again to boot it.... if u have a nandroid backup there is a setting to turn off md5 checking so it will restore......... as long as your using TWRP recovery (which you should be if not) you can mount usb storage and transer whatever you need......
Click to expand...
Click to collapse
i did it but still the same problem i am very frustrated because i cant do anything and i dont have any idea about how can transfer the zip file from my computer to the cellphone
fjej78 said:
i did it but still the same problem i am very frustrated because i cant do anything and i dont have any idea about how can transfer the zip file from my computer to the cellphone
Click to expand...
Click to collapse
you need to download twrp recovery, should be in the stickies, and flash it from hboot.
stick the recovery image in your adb/fastboot folder and rename it to twrp.img, boot phone into bootloader
from cmd prompt, fastboot flash recovery twrp.img
then on device select bootloader, then recovery.....once in twrp recovery you can mount usb and transfer..
no matter what just focus on getting twrp recovery flashed...your fixes will all come after that
18th.abn said:
you need to download twrp recovery, should be in the stickies, and flash it from hboot.
stick the recovery image in your adb/fastboot folder and rename it to twrp.img, boot phone into bootloader
from cmd prompt, fastboot flash recovery twrp.img
then on device select bootloader, then recovery.....once in twrp recovery you can mount usb and transfer..
no matter what just focus on getting twrp recovery flashed...your fixes will all come after that
Click to expand...
Click to collapse
yeah, i can do it i use the one click tool, and i installed another room, but i lost the root how can i root again? and how can i avoid the disclaimer when the phone boot?
BTW thanks you so much for your help
fjej78 said:
yeah, i can do it i use the one click tool, and i installed another room, but i lost the root how can i root again? and how can i avoid the disclaimer when the phone boot?
BTW thanks you so much for your help
Click to expand...
Click to collapse
any custom rom that you flash will be rooted already. As far as the red text goes, that is there to stay until the device gets s-off or you go back to completely stock/use a stock recovery.
18th.abn said:
any custom rom that you flash will be rooted already. As far as the red text goes, that is there to stay until the device gets s-off or you go back to completely stock/use a stock recovery.
Click to expand...
Click to collapse
sorry for the stupid question but what is s-off?
Security-off....see the phones which HTC does allow bootloader unlocking don't really get unlocked. Their unlocking really just partially unlocks and to have a HTC phone with a truly "unlocked" boitloader you have to have s off. Which gives the user full rights over the entire phone....so htcdev unlocked bootloaders aren't really even unlocked, they're simply less restricted.......
Sent from my SCH-R720 using xda app-developers app
18th.abn said:
Security-off....see the phones which HTC does allow bootloader unlocking don't really get unlocked. Their unlocking really just partially unlocks and to have a HTC phone with a truly "unlocked" boitloader you have to have s off. Which gives the user full rights over the entire phone....so htcdev unlocked bootloaders aren't really even unlocked, they're simply less restricted.......
Sent from my SCH-R720 using xda app-developers app
Click to expand...
Click to collapse
And exists a way or method to unlock completely the phone? (something that does not turn my phone on a luxury brick)?
Well a few guys and myself have all bricked our fair share of devices trying.......in the general forum you can follow the development on it in the [DEV]S Off thread...
http://forum.xda-developers.com/showthread.php?t=1639972
Sent from my SCH-R720 using xda app-developers app
18th.abn said:
Well a few guys and myself have all bricked our fair share of devices trying.......in the general forum you can follow the development on it in the [DEV]S Off thread...
http://forum.xda-developers.com/showthread.php?t=1639972
Sent from my SCH-R720 using xda app-developers app
Click to expand...
Click to collapse
thanks for all your help, i will close this post
thank you so much
Hi, this belongs in Q&A. Please keep all question/help related threads in that section only. Thank You.
Thread Moved.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"If you choose not to decide, you still have made a choice"
Sent from my Galaxy Note (i717), using XDA Premium.
Ok everyone. Horrible question I know but here goes. I want to be right so please excuse a question I am sure has been asked many many times.
Situational info:
HTC one s s4 boot loader 1.06
No regular PC access.
Extensive knowledge and experience rooting and flashing G1 and G2X
Goal: unlock boot loader and open root access to enable flashing of roms via recovery while remaining PC independent
Steps I plan to execute:
1) unlock bootloader on htcdev site
2)grant root access following instructions(or all in one tool - your input here is appreciated)
3)instal CWM
4)download rom and kernel of choice
5) boot into boot loader, enter recovery, wipe, flash, boot
If I have any of this wrong please advise.
Again I apologize for the redundancy of this thread. Mods please delete after my process is verified to keep board clean. I only have one crack at this (PC access extremely limited) and I want to get it right.
Sent from my HTC VLE_U using xda app-developers app
Looks correct. First install HTC drivers & HTC Sync software (in order to unlock bootloader, I believe HTCdev site will instruct this).
I recommend (as well as many others, I believe) TWRP over CWM. ESPECIALLY if you do not have computer access. The 1S does not have S-OFF, which makes it very hard for us to flash kernels & radios. Well, not hard, but you need a PC if using CWM. Using TWRP, you can usually flash these things from your device. So definitely use TWRP for your situation.
You can't root without a PC. It's impossible. You are required to get a token that you can only get from a command prompt on the computer. Sorry, but you're out of luck. But when/if you get a PC the steps you wrote were mostly right
1) Correct
2) FLASH RECOVERY (use TWRP, CWM is not good on this device)
3) Then root by flashing a SuperSU zip in RECOVERY (that's why #2 and #2 are switched)
4) Yep
5) Always always always BACKUP YOUR ROM. Then wipe system, data, cache, and dalvik cache. then flash the ROM. If you have extra time you should fastboot your kernel if your hboot is below 1.13 (meaning 1.13 is NOT able to flash the kernel.)
Hope I helped. If I did press thanks
OP did mention that he will have limited PC access to perform the unlock process, so he will be able to do it initially.
Here's the link for TWRP: http://forum.xda-developers.com/showthread.php?t=1677670 (make sure to use this one, the other link in the forums is for the S3 processor)
Ok so I can flash recovery as soon as I unlock boot loader and use twrp check.
The supersu, that's just a zip to flash in recovery to grant root access?
What is fasbooting kernel?
Thanks guys, appreciate the help. Will be performing this within the next two hours. Just trying to be ready so it goes off smooth. Once I get this done I need to do my friend's G2(condition for PC time lol)
Sent from my HTC VLE_U using xda app-developers app
TWRP is a recovery. You will use that instead of CWM, not in addition to.
If you're going to flash a custom rom then you don't have to worry about rooting first. The rom will be rooted already.
Fastbooting kernel is a method of using a pc + command prompt to flash the kernel on your phone. Because HTC hasn't completely "unlocked" the 1S, we need workarounds like that to do certain things. However. TWRP will allow you to flash most things, including most kernels. If you use TWRP and yout hboot is low (which yours is) you shouldn't have too many issues.
Brief note here, I won't have adb access on this pc....will I be able to flash twrp without adb? I see there is an app in the market for it but seems to require root first. Thanks again for the input
Also, downloaded roms and kernels will need to reside on my SD card. This will become an issue if pre install format/wipe kills my SD card. Please advise. Roms and kernels will need to always be installed from SD card via recovery
Sent from my HTC VLE_U using xda app-developers app
briandresstoyota said:
Brief note here, I won't have adb access on this pc....will I be able to flash twrp without adb? I see there is an app in the market for it but seems to require root first. Thanks again for the input
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
You need adb access. That's how you flash recovery, using command prompt on the PC.
Not sure about this app, what's the name of it? To my knowledge you need adb to flash recovery on this phone.
If this isn't possible, you will still be able to root, just not have a custom recovery or flash roms. I don't believe you need to unlock the bootloader to root...not 100% sure but I believe you can root without it, which should be pretty simple.
On twrp website there is an option to install recovery via an app called goomanager. In the app store goo manager states root required. Should I revise my steps to this:
1)unlock bl
2) root using supersu img
3)goomanager install twrp
4)use twrp to flash roms and kernels
I would really love to avoid flashing radios btw. I just feel like it might be safer to let it be. Radios always made me nervous on previous devices
Sent from my HTC VLE_U using xda app-developers app
You could download goo manager from the play store then install open recovery script from menu..then flash the SuperSU zip. You wouldn't require ADB then.
invasion2 said:
You could download goo manager from the play store then install open recovery script from menu..then flash the SuperSU zip. You wouldn't require ADB then.
Click to expand...
Click to collapse
This is correct. I forgot about goomanager.
As for the radios, there isn't really too much risk on the 1S. I remember it was always a scary issue on the HD2 because of EU vs. US radios, which could cause a brick. On the 1S you can flash EU radios with no prob. Actually, some people report better performance in the US with EU radio. So yeah, don't be worried about it, it's pretty safe on this device - with normal precautions and proper flashing of course.
HOWEVER:
Make sure to only use S4 radios/roms on S4 processor. There is an S3 version of the 1S as well, and you cannot switch any roms/kernels/radios between the two.
Hey hey!!! Made it work. Flashed aokp. Running sooooo amazing. Anyone know how to make home screen and app store rotate?
Sent from my HTC One S using xda app-developers app
Can't make home screen. But turn on auto-rotate in settings and it should rotate the store.
So I am a happy rooted owner. No sound in music apps or YouTube.
Sent from my HTC One S using xda app-developers app
Soo started with aokp then cm10. No sound on either except in power amp. So weird
Sent from my HTC One S using xda app-developers app
Try flashing official CM10
http://get.cm/?device=ville
If you prefer a stock look try TrickDroid or Viper
Sent from my HTC One S using xda app-developers app
Actually flashed most recent cm10 nightly after my go with AOKP. Still no dice. I've posted the issue on both ROM dev forums so hopefully it will get resolved. I feel like it is operator error but I have flashed each ROM twice with a full wipe before each install. I understand the process for flashing so I hope its something small I missed.
Sent from my HTC One S using xda app-developers app
briandresstoyota said:
Actually flashed most recent cm10 nightly after my go with AOKP. Still no dice. I've posted the issue on both ROM dev forums so hopefully it will get resolved. I feel like it is operator error but I have flashed each ROM twice with a full wipe before each install. I understand the process for flashing so I hope its something small I missed.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Do you have no sound from the speaker or do you have headphones or something plugged in?
Has anyone successfully rooted Kitkat yet? I've looked around and haven't come across any threads about it yet.
SynUnlimited said:
Has anyone successfully rooted Kitkat yet? I've looked around and haven't come across any threads about it yet.
Click to expand...
Click to collapse
Considering only like 3 people have it, I'd say no.
Bl00dRunzC0ld said:
Considering only like 3 people have it, I'd say no.
Click to expand...
Click to collapse
Guess I'm one of the lucky few then.
SynUnlimited said:
Guess I'm one of the lucky few then.
Click to expand...
Click to collapse
And we all hate you
I find this funny.
First of all you come here seeking for help from the community, but in the same time you are absolutely not involved in the same community from which you're seeking help - while others actually try to do something for all of us.
I find this thread offensatory as a user that is trying to help and contribute to the community
Sent from my XT1032 using xda app-developers app
darkeingel said:
I find this funny.
First of all you come here seeking for help from the community, but in the same time you are absolutely not involved in the same community from which you're seeking help - almost 6 years in here and you are still leeching only - while others actually try to do something for all of us.
I find this thread offensatory as a user that is trying to help and contribute to the community
Sent from my XT1032 using xda app-developers app
Click to expand...
Click to collapse
Who are you talking to?
OP, obviously
Sent from my XT1032 using xda app-developers app
darkeingel said:
OP, obviously
Sent from my XT1032 using xda app-developers app
Click to expand...
Click to collapse
Well considering you said something about leeching for 6 years, and OP's join date is Jan 2013, it threw me off.
So, when the OP got Kitkat, he can dump the system (without root), provide it to us and we tell him, if he can root - win/win.
But hell, yeah, I know... "Community"
You can
gain root flashing SuperSU - http://forum.xda-developers.com/showthread.php?t=1538053
To root can't you just unlock bootloader.
Download superSU to /storage
http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip
Then download CWM and boot recovery (don't even need to flash it) using the following (apologies if syntax not 100%, I'm not at my laptop to check)
fastboot boot recovery cwmrecovery.img
Then just flash superSU via CWM.
You don't really need any special rooting 'tool'. Its just basic stuff.
scott_doyland said:
To root can't you just unlock bootloader.
Download superSU to /storage
http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip
Then download CWM and boot recovery (don't even need to flash it) using the following (apologies if syntax not 100%, I'm not at my laptop to check)
fastboot boot recovery cwmrecovery.img
Then just flash superSU via CWM.
You don't really need any special rooting 'tool'. Its just basic stuff.
Click to expand...
Click to collapse
I know that for booting simply recovery it s not need unlock bootloader. Only for boot recovery obviously, not flashing it permanently.
scott_doyland said:
To root can't you just unlock bootloader.
Download superSU to /storage
http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip
Then download CWM and boot recovery (don't even need to flash it) using the following (apologies if syntax not 100%, I'm not at my laptop to check)
fastboot boot recovery cwmrecovery.img
Then just flash superSU via CWM.
You don't really need any special rooting 'tool'. Its just basic stuff.
Click to expand...
Click to collapse
Tried both flashing CWM and just straight booting it and it just restarts the phone and doesn't boot into recovery. Also tried TWRP same results.
SynUnlimited said:
Tried both flashing CWM and just straight booting it and it just restarts the phone and doesn't boot into recovery. Also tried TWRP same results.
Click to expand...
Click to collapse
dont work any method, uploadig kitkat ota for global gsm model xt1032 : Cruzando los dedos-: