Related
Hi all.
I know now that it was a mistake to wait for 2.3.3 before i rooted but i did and now i don't know how.
All the methods i can find don't work with 2.3.3.
I'm still quite green with regards to android although i did root my old LG GT540 using Z4root which was really easy.
Any help would be much appreciated.
Really? So if you unlock the bootloader (guides should be available on the development forum) and you flash ClockworkMod recovery(CWM - again there are guides for this), then you can't flash the superuser.apk? I had some trouble, but it turns out that I had to mount /system in CWM for the .apk to flash properly.
It's ridiculously easy to root the Nexus S. Before 2.3.3 you could root it without even unlocking the bootloader, now you have to unlock it first. Which is also ridiculously easy.
The only problem is that the unlocking process completely wipes all user data and the SD card. So before you root, do a complete backup. Then follow the instructions in this thread: http://forum.xda-developers.com/showthread.php?t=895545
Use the android 2.3.3 root backup that's around the forum. Easiest way to get root
Sent From Your Mom's Nexus S.
charlieb620 said:
Use the android 2.3.3 root backup that's around the forum. Easiest way to get root
Click to expand...
Click to collapse
Thanks all of you for your replies.
So how do i do this? Do i copy this file to root of storage then install through recovery?
Easiest Way To Get Root On 2.3.3
noj78 said:
Thanks all of you for your replies.
So how do i do this? Do i copy this file to root of storage then install through recovery?
Click to expand...
Click to collapse
if you have clockwork mod use this as a restore and you will have a rooted 2.3.3 its the easiest way to do it.
http://www.mediafire.com/?c1ww7zb837uycbk
just unzip and put the backup folder in your clockworkmod recovery folder boot into recovery and restore 2.3.3 takes 2 minutes and you will boot up with a rooted 2.3.3
charlieb620 said:
if you have clockwork mod use this as a restore and you will have a rooted 2.3.3 its the easiest way to do it.
Click to expand...
Click to collapse
But i need to be rooted first to install clockwork mod.
I guess i need to unlock the bootloader now to root
noj78 said:
But i need to be rooted first to install clockwork mod.
I guess i need to unlock the bootloader now to root
Click to expand...
Click to collapse
you install clockworkmod through the market your not rooted on 2.3.2????
charlieb620 said:
you install clockworkmod through the market your not rooted on 2.3.2????
Click to expand...
Click to collapse
No i updated to 2.3.3 before thinking about rooting
noj78 said:
No i updated to 2.3.3 before thinking about rooting
Click to expand...
Click to collapse
download clockworkmod from market
try to flash recovery from inside app if it works restore the backup that i posted thats in the zip
charlieb620 said:
download clockworkmod from market
try to flash recovery from inside app if it works restore the backup that i posted thats in the zip
Click to expand...
Click to collapse
No it won't work as it requires superuser permission
Guess its time to backup and unlock the bootloader!!
noj78 said:
No it won't work as it requires superuser permission
Guess its time to backup and unlock the bootloader!!
Click to expand...
Click to collapse
guess so. sorry bout that.
charlieb620 said:
guess so. sorry bout that.
Click to expand...
Click to collapse
Thank's for trying to help your very kind.
noj78 said:
Thank's for trying to help your very kind.
Click to expand...
Click to collapse
no problem. i dont mind helping when i know.
I flashed the full 2.3.3 rom, im still unlocked and I flashed cmw via original root method and it completed but when I boot into stock recovery then choose recovery I get the triangle with ! inside it
You have to get root explorer and rename install recovery.sh in the etc folder so that clockwork recovery will stick. If you don't everytime you reboot it will go back to stock
Sent from my Nexus S using XDA App
Sweet, what do you rename it to?
Bronk93 said:
Sweet, thanks dude for providing that info
Click to expand...
Click to collapse
Make sure after you rename the file flash clockworkmod again. Make sure when your in the folder before you rename mount r/o rename than remount
Sent from my Nexus S using XDA App
old-install-recovery.old
Sent from my Nexus S using XDA App
Thanks again man!
I'm sure this is discussed already but I can't seem to find it so if someone can help me or point me in the right direction.
I have a VZW GS3 that I have rooted, unlocked the boot loader and flashed CWM recovery. I then made a nandroid.
The main reason I did this was because I wanted Jelly Bean, and since Verizon is the slowest, I didn't want to wait so I installed custom ROMs.
Now that Verizon has released JB, I want to go back to my nandroid and then use the OTA firmware update service to upgrade.
Am I missing anything along the way that's essential for this to work?
Will the updated software re-root and/or relock my bootloader?
Will this automatically update the Baseband from my current VRLG7 to whatever the new one is?
One other thing, Will I still have CWM recovery after this happens? or will it revert back to stock recovery? or do I need to manually do anything to the recovery?
You're doing this to ultimately stay stock? Do you intend on flashing roms again or no? If you did a nandroid just after ONLY rooting and unlocking bootloader then restore it. Here's a step by step:
1) boot into CWM, restore your rooted, stock nandroid
2) Download EZ recovery, flash stock recovery
3) Wait for OTA
The OTA will relock your bootloader and unroot your phone. The JB OTA will also update your modem, and everything else, to VRBLK3.
One other thing, Will I still have CWM recovery after this happens? or will it revert back to stock recovery? or do I need to manually do anything to the recovery?
Click to expand...
Click to collapse
No, you will lose CWM if you do what I detail above. The OTA will fail if you still have CWM installed.
SlimSnoopOS said:
You're doing this to ultimately stay stock? Do you intend on flashing roms again or no?
Click to expand...
Click to collapse
For the time being I intend on remaining stock, but I still want to root. Maybe once CM10.1 becomes stable, I'll go back to it, as of now I've had too many bugs with 10 nightlys and stable and 10.1 nightlys.
SlimSnoopOS said:
If you did a nandroid just after ONLY rooting and unlocking bootloader then restore it
Click to expand...
Click to collapse
I don't recall, but it's possible I did it after flashing CWM recovery, would that make a difference?
Thanks for your help!
levilib said:
For the time being I intend on remaining stock, but I still want to root. Maybe once CM10.1 becomes stable, I'll go back to it, as of now I've had too many bugs with 10 nightlys and stable and 10.1 nightlys.
I don't recall, but it's possible I did it after flashing CWM recovery, would that make a difference?
Thanks for your help!
Click to expand...
Click to collapse
Nah I was just verifying to see if you modified any system settings or apps while on ICS TW. You should be in the clear as long as you reset CWM to stock recovery if all you did was root, unlock, then perform a nandroid.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
Nah I was just verifying to see if you modified any system settings or apps while on ICS TW. You should be in the clear as long as you reset CWM to stock recovery if all you did was root, unlock, then perform a nandroid.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
before I restore the nandroid in CWM, do I need to do any wiping? cache, dalvik or full wipe?
levilib said:
before I restore the nandroid in CWM, do I need to do any wiping? cache, dalvik or full wipe?
Click to expand...
Click to collapse
Absolutely.
Sent from my SCH-I535 using xda app-developers app
so which wipe(s) do I need to do?
levilib said:
before I restore the nandroid in CWM, do I need to do any wiping? cache, dalvik or full wipe?
Click to expand...
Click to collapse
No you do not, the nan will overwrite everything anyways. If you feel better then factory reset and clear caches, but it's not necessary.
Sent from my VS920 4G using xda app-developers app
thanks
I followed the instructions above and I'm back on my rooted TW.
When i try and update i get the following message:
Service Unavailable
To check for system updates, go to Settings > About device when service is available
What's wrong, how do i fix that?
searched around on google and a lot of people had the same warning error, multiple solutions were offered but none of them worked.
in the end, I ended up installing from odin completely stock unrooted, locked bootloader etc 4.0.4 (as f i want to return my phone to verizon) and once i did that it automatically updated to 4.1.1
Basically as the title states. Does anyone know a way to reduce the vibration intensity? Is this something I would need root to do? Even with a case I feel like if I'm sitting somewhere the whole room can hear the phone vibrate.
PsychDrummer said:
Basically as the title states. Does anyone know a way to reduce the vibration intensity? Is this something I would need root to do? Even with a case I feel like if I'm sitting somewhere the whole room can hear the phone vibrate.
Click to expand...
Click to collapse
You'll need to root to do it. Both Franco Kernel Updater and Trickster Mod allow you to alter the vibration intensity.
chw2006 said:
You'll need to root to do it. Both Franco Kernel Updater and Trickster Mod allow you to alter the vibration intensity.
Click to expand...
Click to collapse
So I'm not too familiar with using kernels. Are these just apps I can use with root or do I actually have to flash something?
PsychDrummer said:
So I'm not too familiar with using kernels. Are these just apps I can use with root or do I actually have to flash something?
Click to expand...
Click to collapse
No, all you need to do is root. You can change these settings on the stock kernels with the apps I mentioned.
chw2006 said:
No, all you need to do is root. You can change these settings on the stock kernels with the apps I mentioned.
Click to expand...
Click to collapse
Oh gotcha, thanks!
PsychDrummer said:
Oh gotcha, thanks!
Click to expand...
Click to collapse
You don't just need root, you need a custom recovery too. You flash the kernel in the custom recovery.
See this http://forum.xda-developers.com/showthread.php?p=47025283
jd1639 said:
You don't just need root, you need a custom recovery too. You flash the kernel in the custom recovery.
See this http://forum.xda-developers.com/showthread.php?p=47025283
Click to expand...
Click to collapse
Ok now I'm a bit confused. So the person above said that I just download the app and I can regulate the vibration using the stock kernel. Are you talking about just flashing kernels in general?
PsychDrummer said:
Ok now I'm a bit confused. So the person above said that I just download the app and I can regulate the vibration using the stock kernel. Are you talking about just flashing kernels in general?
Click to expand...
Click to collapse
What he means is you need a custom recovery to flash the SU zip (root).
Sent from my Nexus 5 using Tapatalk
0dBu said:
What he means is you need a custom recovery to flash the SU zip (root).
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
But I don't need that if I want to simply use Trickster Mod right?
You have to be rooted to use Trickster as it has to access /system level files.
Sent from my Nexus 5 using Tapatalk
PsychDrummer said:
But I don't need that if I want to simply use Trickster Mod right?
Click to expand...
Click to collapse
Hahahaha.
1. You need root to alter the vibration on your device. Apps like Trickster Mod only work if you have root.
2. In order to root your device, you'll need to flash SuperUser. In order to flash SU (or a ROM/kernel,) you'll need to install a custom recovery image on your device. I recommend TWRP.
3. Once you've flashed SU, you can install Trickster Modand grant the app root access.
Check out this thread to get you started. http://forum.xda-developers.com/showthread.php?t=2507905
Are you on PC, Mac, or Linux?
Sent from my Nexus 5 using Tapatalk
soltheman said:
Hahahaha.
1. You need root to alter the vibration on your device. Apps like Trickster Mod only work if you have root.
2. In order to root your device, you'll need to flash SuperUser. In order to flash SU (or a ROM/kernel,) you'll need to install a custom recovery image on your device. I recommend TWRP.
3. Once you've flashed SU, you can install Trickster Modand grant the app root access.
Check out this thread to get you started. http://forum.xda-developers.com/showthread.php?t=2507905
Click to expand...
Click to collapse
Right, I forgot about having to actually grant permission which I do need SU for. I have rooted/flashed before. Just a bit forgetful haha. Thanks.
soltheman said:
Hahahaha.
1. You need root to alter the vibration on your device. Apps like Trickster Mod only work if you have root.
2. In order to root your device, you'll need to flash SuperUser. In order to flash SU (or a ROM/kernel,) you'll need to install a custom recovery image on your device. I recommend TWRP.
3. Once you've flashed SU, you can install Trickster Modand grant the app root access.
Check out this thread to get you started. http://forum.xda-developers.com/showthread.php?t=2507905
Click to expand...
Click to collapse
You could just fastboot boot recovery.img where recovery.img is twrp or cwm. Then flash super su and reboot. That what you'd still have the stock recovery and root.
PsychDrummer said:
Right, I forgot about having to actually grant permission which I do need SU for. I have rooted/flashed before. Just a bit forgetful haha. Thanks.
Click to expand...
Click to collapse
Happens to the best of us, mate. :good:
Laughing 'cause we've all been there.
jd1639 said:
You could just fastboot boot recovery.img where recovery.img is twrp or cwm. Then flash super su and reboot. That what you'd still have the stock recovery and root.
Click to expand...
Click to collapse
That's true. But if you're gonna go through the trouble of flashing SU, might as well keep a custom recovery on your device in case you need to wipe.
jd1639 said:
You could just fastboot boot recovery.img where recovery.img is twrp or cwm. Then flash super su and reboot. That what you'd still have the stock recovery and root.
Click to expand...
Click to collapse
You can boot into a recovery.img without flashing it to the phone?
Sent from my Nexus 5 using Tapatalk
0dBu said:
You can boot into a recovery.img without flashing it to the phone?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yep
jd1639 said:
Yep
Click to expand...
Click to collapse
Huh... I didn't know that. Learn something new everyday.
Sent from my Nexus 5 using Tapatalk
I have a Verizon Galaxy S3 SCH-I535. I'm rooted on 4.3. Is there a way to remove the Knox bootloader and revert to an earlier firmware such as 4.1.1 or something like that, and re-root on that particular earlier firmware? Thank you!
php111 said:
I have a Verizon Galaxy S3 SCH-I535. I'm rooted on 4.3. Is there a way to remove the Knox bootloader and revert to an earlier firmware such as 4.1.1 or something like that, and re-root on that particular earlier firmware? Thank you!
Click to expand...
Click to collapse
Nope, once you're on that bootloader you're stuck with it.
Sent from my SCH-I535 using Tapatalk 2
php111 said:
I have a Verizon Galaxy S3 SCH-I535. I'm rooted on 4.3. Is there a way to remove the Knox bootloader and revert to an earlier firmware such as 4.1.1 or something like that, and re-root on that particular earlier firmware? Thank you!
Click to expand...
Click to collapse
Knox isn't the bootloader. Bootloader is just locked for OTA 4.3
Knox monitors for root etc within the OS.
Saferoot will disable knox
Sent from my SCH-I535 using xda app-developers app
5ft24 said:
Knox isn't the bootloader. Bootloader is just locked for OTA 4.3
Knox monitors for root etc within the OS.
Saferoot will disable knox
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Knox is also a firmware component along with an application component.
Using the term Knox bootloader is correct, that's what counts the warranty bit.
Sent from my SCH-I535 using Tapatalk 2
Is there a way, or is someone working on, unlocking the bootloader on 4.3 in order to flash roms?
MIKESTONY said:
Is there a way, or is someone working on, unlocking the bootloader on 4.3 in order to flash roms?
Click to expand...
Click to collapse
Maybe, we wouldn't know until it's released. Most likely it isn't being worked on.
You can flash 4.3 TouchWiz roms with safestrap.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Maybe, we wouldn't know until it's released. Most likely it isn't being worked on.
You can flash 4.3 TouchWiz roms with safestrap.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
hmmm, bummer but thanks for the info
I'll have to check out that safestrap thing
Thank you all for the info!
I suppose this way won't work to remove Knox and to revert to an earlier firmware is by wiping /system in recovery?
php111 said:
I suppose this way won't work to remove Knox and to revert to an earlier firmware is by wiping /system in recovery?
Click to expand...
Click to collapse
Doubt it. If it were that simple, someone would have discovered that by now.
About flashing ROMs with safestrap. Every time I flash a TouchWiz ROM, it flashes successfully, but it unroots me. I lose my safestrap recovery and I lose my root access. I open SuperSU that I rooted with saferoot. Here is the message I get when I open SuperSU.
There is no SU binary installed, and SuperSU cannot install it. This is a problem! If you just upgraded to Android 4.3, you need to manually re-root-consult the relevant forums for your device!
I tap OK, and SuperSU closes.
The ROM is CleanROM
php111 said:
About flashing ROMs with safestrap. Every time I flash a TouchWiz ROM, it flashes successfully, but it unroots me. I lose my safestrap recovery and I lose my root access. I open SuperSU that I rooted with saferoot. Here is the message I get when I open SuperSU.
There is no SU binary installed, and SuperSU cannot install it. This is a problem! If you just upgraded to Android 4.3, you need to manually re-root-consult the relevant forums for your device!
I tap OK, and SuperSU closes.
The ROM is CleanROM
Click to expand...
Click to collapse
There's a fix for this but I forgot, try to search for it, but it involves using terminal emulator to remove a supersu duplicate.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
There's a fix for this but I forgot, try to search for it, but it involves using terminal emulator to remove a supersu duplicate.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I just tried searching Google for it but I couldn't find that fix and i dont know what i am searching for.
php111 said:
I just tried searching Google for it but I couldn't find that fix and i dont know what i am searching for.
Click to expand...
Click to collapse
Start with post #3.
BadUsername said:
There's a fix for this but I forgot, try to search for it, but it involves using terminal emulator to remove a supersu duplicate.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
SlimSnoopOS said:
Start with post #3.
Click to expand...
Click to collapse
Earlier I tried those commands in post #5, but I would get those operation errors. So in post #5 did not work for me. I didnt try post #3.
Post #3 doesn't work for me. I don't see the #. All I get is a $ and everything I type in it types the samething on the next line down. Please see below on what I mean.
C:\Users\\Desktop\adt SDK\adt-bundle-windows-x86-20131030\sdk\platform-tool
s>adb shell
[email protected]:/ $ /system/xbin/su
/system/xbin/su
1|[email protected]:/ $ /system/xbin/su
/system/xbin/su
1|[email protected]:/ $ su
su
1|[email protected]:/ $
php111 said:
Post #3 doesn't work for me. I don't see the #. All I get is a $ and everything I type in it types the samething on the next line down. Please see below on what I mean.
C:\Users\\Desktop\adt SDK\adt-bundle-windows-x86-20131030\sdk\platform-tool
s>adb shell
[email protected]:/ $ /system/xbin/su
/system/xbin/su
1|[email protected]:/ $ /system/xbin/su
/system/xbin/su
1|[email protected]:/ $ su
su
1|[email protected]:/ $
Click to expand...
Click to collapse
Ya you aren't even getting root access.
I say either keep trying with clean wipes in rom slots, or flash 4.3 and reroot.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Ya you aren't even getting root access.
I say either keep trying with clean wipes in rom slots, or flash 4.3 and reroot.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Its I flash the ROM and I am unrooted again and I do a clean wipe and re-root and than i try to flash the ROM again and i am back to being unrooted which just does not make sense
I did not try flashing 4.3 again and my reason is after flashing 4.3 and I re-root and than try to flash a ROM again its only going to un-root me again where I have to flash 4.3 again. And I can't try custom wipes with different slots in recovery cuz when I flash the ROM I lost safestrap recovery as well and it un-rooted me.
This is what I tried again and it still unroots me.
What am I doing wrong and how could I fix this?
I flashed the latest stock via Odin like a million times and re-root it. In Safestrap recovery, I tried with stock ROM first, and I wiped the cache, and dalvik, and did a factory reset, and than installed CleanROM, and I rebooted, and go into SuperSU, and I see that message again which means I am unrooted. I am not sure about ROM slots, so I created slot 1 with the default everything including the default sizes. I tried slot 2, but my phone won't boot up with slot 2, so I have to switch to slot 1, or stock, and I open SuperSU being on slot 1, and I get the same message. I have not tried slot 3 and 4.
Whenever superSu asks for permission to run a root app my screen becomes unresponsive. Timer runs out and i am not able to apply grant permission. Help. This didnt use to happen when i was earlier rooted with towelroot. Right now also i ised towelroot
Have you tried re-flashing the supersu zip?
jameson21 said:
Have you tried re-flashing the supersu zip?
Click to expand...
Click to collapse
Yes. Didnt work.
Btw by reflash the zip file you mean reinstall it from pkay store, right?
Pardon the ignorance. Just found out that flashing a zip file and installing apps from play store are 2 different things.
Well my bootloader is locked and neither do i have a custom recovery installed. So flashing doesnt seem to be an option right now.. If i am not missing anything.
Are you running 5.0? If so how the heck did you root with towelroot? AFAIK you can not root 5.0 that way. Maybe that is a problem.
Sent from my Nexus 5 using Tapatalk
frenziedfemale said:
Are you running 5.0? If so how the heck did you root with towelroot? AFAIK you can not root 5.0 that way. Maybe that is a problem.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
No no. I am on kitkat only
Tried reinstalling it. This is what came up. I am on android 4.4.4 btw
You need to flash the supersu zip using fastboot:
teamandroid. com/2014/06/19/root-nexus-5-android-444-ktu84p-kitkat/2/ (you're going to have to fix that link because I have under 10 posts so the forum won't let me post..)
Additionally you need to have an unlocked bootloader
jameson21 said:
You need to flash the supersu zip using fastboot:
teamandroid. com/2014/06/19/root-nexus-5-android-444-ktu84p-kitkat/2/ (you're going to have to fix that link because I have under 10 posts so the forum won't let me post..)
Additionally you need to have an unlocked bootloader
Click to expand...
Click to collapse
Why is it happening now? Didnt use to happen earlier..
You say you were rooted ...why did you re-root? It looks like you are no longer rooted. Did you do an update or anything?
Sent from my Nexus 5 using Tapatalk
frenziedfemale said:
You say you were rooted ...why did you re-root? It looks like you are no longer rooted. Did you do an update or anything?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I was rooted. I unrooted because i thought it was required to update to lollipop. But i dont have any intention to update to L for now.
rahul9five said:
I was rooted. I unrooted because i thought it was required to update to lollipop. But i dont have any intention to update to L for now.
Click to expand...
Click to collapse
To get root again either flash the latest CF Auto Root in fastboot or flash the latest superSU.zip in recovery or flash a pre-rooted custom rom in a custom recovery.