I just got my N7 2013 today. Should I update to KitKat and then root/unlock? If so, is the process the same as rooting on JB? If I do update to 4.4, should I do it with SDK & fastboot or will Chainfire's CF-Autoroot work as well? This is my first Nexus device, but not my first droid (as you can see below in my sig).
Rooting and unlocking can be done on either JB or KK, it doesn't matter. As for updating, it's mainly preference if you want to do it with a utility, manually, or with an OTA.
prsterero said:
Rooting and unlocking can be done on either JB or KK, it doesn't matter. As for updating, it's mainly preference if you want to do it with a utility, manually, or with an OTA.
Click to expand...
Click to collapse
So if I understand right, I can use the same cmd commands in fastbood/adb to unlock, install recovery and flash Chainfire's SuperSU update and binaries in 4.4?
Aizukaori said:
So if I understand right, I can use the same cmd commands in fastbood/adb to unlock, install recovery and flash Chainfire's SuperSU update and binaries in 4.4?
Click to expand...
Click to collapse
Correct. That's why nexus rules
prshosting.org
Related
Hello all,
Just did an OTA update to JRO03O after unrooting and relocking my phone. Then went to Root Toolkit 1.5.3 to root and unlock the new ROM but the only option there was JRO03H to select for my Verizon phone. Can I select this "H" version (or the last choice, which is MYSID-TORO;Android*.*) to root and unlock it? Or must I wait for my specific build to appear?
Do you use fastboot? I avoid toolkits like the plague because you learn nothing from them. Try using fastboot to flash a custom recovery(CWM or TWRP), then just flash the latest superuser zip from clockworkmod.
Edit: don't quote me though, the only time I've ever been stock is the first 30 minutes owning my Gnex. I just bypass the rooting process by flashing a custom ROM.
~~~~There is no spoon~~~~
shag_on_e said:
Do you use fastboot? I avoid toolkits like the plague because you learn nothing from them. Try using fastboot to flash a custom recovery(CWM or TWRP), then just flash the latest superuser zip from clockworkmod.
~~~~There is no spoon~~~~
Click to expand...
Click to collapse
hmm never really used anything but toolkits, could you point me to a tutorial on how to do the fastboot / superuser? I thought that you'd need to be rooted before you could install a custom recovery / superuser on your phone. I also thought that on any phone that you have to unlock the bootloader before doing anything with recovery as well. could you or someone enlighten me?
thanks!
Shukero
Here ya go, this is the tutorial I used in the beginning, still gold to this day. And you don't have to be rooted to flash a recovery from the bootloader, boot straight to recovery, then flash a custom ROM. No root needed. The bootloader does need to be unlocked first though but there's nothing to it. Just follow this guide.
http://wiki.rootzwiki.com/Samsung_Galaxy_Nexus_(toro)#IMM76K
~~~~There is no spoon~~~~
A little off topic, but is JRO03O the OTA version? I haven't taken it yet, but the most recent AOSP branch is for JRO03R, which comes after O
yes the ota is jro03o
Read forum rules before posting
This is not development
Thread moved
javroch said:
A little off topic, but is JRO03O the OTA version? I haven't taken it yet, but the most recent AOSP branch is for JRO03R, which comes after O
Click to expand...
Click to collapse
for gsm, yes, it's JRO03R
sent from my i9250
As far as I know, there is no way to keep root if you get the OTA 4.3 update, right? I want to just get the OTA and not deal with the roms. Unlocked bootloader here...
According to Voodoo OTA Rootkeeper, it doesn't work with the 4.3 update: http://forum.xda-developers.com/showthread.php?t=1241517&page=6
That's a true bummer.
Gbcue said:
As far as I know, there is no way to keep root if you get the OTA 4.3 update, right? I want to just get the OTA and not deal with the roms. Unlocked bootloader here...
According to Voodoo OTA Rootkeeper, it doesn't work with the 4.3 update: http://forum.xda-developers.com/showthread.php?t=1241517&page=6
That's a true bummer.
Click to expand...
Click to collapse
If your bootloader is unlocked then it's easy... you just flash SuperSU in recovery after the update. No ROMs to deal with. On a Nexus device with an unlocked bootloader root is never an issue.
phazerorg said:
If your bootloader is unlocked then it's easy... you just flash SuperSU in recovery after the update. No ROMs to deal with. On a Nexus device with an unlocked bootloader root is never an issue.
Click to expand...
Click to collapse
Even with stock recovery this is possible? I don't want to re-root and lose data.
Gbcue said:
Even with stock recovery this is possible? I don't want to re-root and lose data.
Click to expand...
Click to collapse
Not with stock recovery. But if you have an unlocked bootloader it's still no problem. You can boot to a custom recovery without even having to actually flash it if you want to keep stock recovery. So you just let the OTA install as normal then use fastboot to boot CWM or TWRP and flash SuperSU and you're done and rooted.
If your bootloader is unlocked, you might as well take advantage of it even if you want to remain mostly stock
Just keep in mind that SuperSU runs a daemon all the time can result in 70% cpu usage peaks. Don't blame 4.3 for it.
madd0g said:
Just keep in mind that SuperSU runs a daemon all the time can result in 70% cpu usage peaks. Don't blame 4.3 for it.
Click to expand...
Click to collapse
Do we have any idea what triggers that? Thankfully I haven't had that experience and haven't had any extra CPU usage before or after flashing 4.3 yesterday.
phazerorg said:
Do we have any idea what triggers that? Thankfully I haven't had that experience and haven't had any extra CPU usage before or after flashing 4.3 yesterday.
Click to expand...
Click to collapse
No, it seems fairly random so far. I have seen it once but can not reproduce it.
Chainfire is working on the issue though.
Questions in the Q&A, this is the general forum..
Read the rules sticky..
Beamed from my Maguro.
GldRush98 said:
No, it seems fairly random so far. I have seen it once but can not reproduce it.
Chainfire is working on the issue though.
Click to expand...
Click to collapse
SuperSU 1.43 update
add3421 said:
So is there a like guide on how to keep root when doing a system update? I have STOCK 4.2 Rooted and it is saying I should download an update. I do have TWRP installed. Is there another stock already rooted 4.3 I can download? Any help would be great so I dont have to factory reset.
Thanks!
Click to expand...
Click to collapse
Why even bother with this crap, flash the update, boot, flash custom recovery after and flash new SuperSU. You would be done before even typing this post.
I used the Nexus Root Toolkit by WugFresh to root my Galaxy Nexus on 4.3, and didn't lose any data...
All I did as usual was:-
1) Flash the update
2) Boot into TeamWin recovery (I keep the stock recovery installed)
3) Flash SuperSU 1.43
Simple, no issues.
If I have CMW Touch recovery can I install the OTA? I have received the notification but I don't know if I will be able to install it. Is there any way to revert back to Google's recovery just like installing a custom recovery? I mean not loosing data or having to so a factory reset.
Enviado desde mi Galaxy Nexus
str355 said:
All I did as usual was:-
1) Flash the update
2) Boot into TeamWin recovery (I keep the stock recovery installed)
3) Flash SuperSU 1.43
Simple, no issues.
Click to expand...
Click to collapse
How do you boot into twrp without flashing it? I know "fastboot flash recovery twrp.img" permanently overrides the built in recovery, but how would you boot into it just once?
AMKhatri said:
I used the Nexus Root Toolkit by WugFresh to root my Galaxy Nexus on 4.3, and didn't lose any data...
Click to expand...
Click to collapse
Which version of the toolkit?
krackers said:
How do you boot into twrp without flashing it? I know "fastboot flash recovery twrp.img" permanently overrides the built in recovery, but how would you boot into it just once?
Click to expand...
Click to collapse
This is the command you want "fastboot boot twrp.img"
---------- Post added at 08:45 PM ---------- Previous post was at 08:41 PM ----------
add3421 said:
ok cool, do you happen to have a link to the exact update i can download? for some reason when i click install it says restarting now.. but never does.
Click to expand...
Click to collapse
I used the link in this thread --> http://forum.xda-developers.com/showthread.php?t=2377390
SuperSU.zip from here (v1.45 now) --> http://forum.xda-developers.com/showthread.php?t=1538053
Gbcue said:
Which version of the toolkit?
Click to expand...
Click to collapse
1.6.4 after running update.
FWIW: Even though I've successfully used this kit a dozen times on four different devices, root was not working correctly (no su binary found) for me so I had to load the app via twrp which did correctly load from the toolkit after the kit installed 4.3.
Gbcue said:
Which version of the toolkit?
Click to expand...
Click to collapse
1.6.4 and it worked perfectly for me
Noticed a new build was released for OTA. Doing a little research I discovered it won't work while rooted.
Question being, what's the easiest way to update? Temporarily run custom recovery and flash it? I don't want to loss root access or any data. If needed I'll re-root again, but rather not.
Sent from my Nexus 7 using xda app-developers app
datallboy said:
Noticed a new build was released for OTA. Doing a little research I discovered it won't work while rooted.
Question being, what's the easiest way to update? Temporarily run custom recovery and flash it? I don't want to loss root access or any data. If needed I'll re-root again, but rather not.
Click to expand...
Click to collapse
There are many ways to accomplish the same end goal.
You can actually install the OTA while rooted. Just need to run the small fix in this post:
http://forum.xda-developers.com/showthread.php?p=44597339#post44597339
Rerooting on this device is super simple.
There are also other options like flashing the factory images or one of the pre-rooted odexed/deodexed repackaged mostly stock ROMs. You can find them described here:
http://forum.xda-developers.com/showthread.php?t=2415497
So just temporarily run custom recovery then flash the update? but where can I download the latest OTA update?
Sent from my Nexus 7 using xda app-developers app
datallboy said:
So just temporarily run custom recovery then flash the update? but where can I download the latest OTA update?
Click to expand...
Click to collapse
You need to run the fix I mentioned above OR unroot BEFORE installing the OTA or the OTA will fail near the end.
You can find the OTA here:
http://forum.xda-developers.com/showthread.php?t=2415497
Don't quite understand the post, so better to just hold off on an attempt.. Would using the unroot option in SuperSU, allowing the OTA update to go through, then rerooting work fine without deleting data?
I'm know more about Nook Tablet than Nexus 7, didn't care what I did to my Nook because I could fix it. I'm more cautious with this.
Sent from my Nexus 7 using xda app-developers app
Super-Su unroot never help you if you delete something in the /system directory
1)you must flash fix after root
2)do not flash permanent custom recovery and relock bootloader (if your bricked you devices you can send to Warranty Service)
3)replace backup of /system directory before update
and after update clean Dalvik Cache before flash Root again (if superuser privilegies still anavalable for you)
Understand the fix now. Noticed the update went through, but got an error when it finished. Flash ota update in temporary recovery. Correct?
Sent from my Nexus 7 using xda app-developers app
I just downloaded the OTA to the device, unrooted, installed the OTA in TWRP, and then the latest superSU zip (still in recovery). Reboot and voila.
datallboy said:
I'm know more about Nook Tablet than Nexus 7, didn't care what I did to my Nook because I could fix it. I'm more cautious with this.
Click to expand...
Click to collapse
This is a Nexus device. There's almost no way to hard-brick it. Worst case, reboot into bootloader, and fastboot push the stock images.
The fix worked, and I'm still rooted. with all data. Temporarily booted into TWRP, flashed the fix and forced OTA update. Thank you!
ripelli part
Don't fear the ota update. There were no negative effects on my rom or kernel.
-cleanROM1.3
- 3.4.0 ElementalX1.1+
sfreemanoh said:
This is a Nexus device. There's almost no way to hard-brick it. Worst case, reboot into bootloader, and fastboot push the stock images.
Click to expand...
Click to collapse
LOL if you flash STOCK and then bootloader - you will get bootloop hardbrick without FASTBOOT and ADB !!! (only APX)
(my nexus 7 1 gen in this situation)
------------------------------------------------------
why you try new customs rom, when in few weeks would be android 5.0 ?
sambistt said:
LOL if you flash STOCK and then bootloader - you will get bootloop hardbrick without FASTBOOT and ADB !!! (only APX)
(my nexus 7 1 gen in this situation)
------------------------------------------------------
why you try new customs rom, when in few weeks would be android 5.0 ?
Click to expand...
Click to collapse
I'm not sure what you're saying in reference to my earlier comment...are you saying something I said was incorrect?
I'm quite familiar with the Skipsoft Toolkits. I've used them plenty of times in the past.
Bought a Nexus 7 2013 today. First thing it wanted to do was update from 4.3 to 4.4.2. I did that. Then 4.4.3. Did that.
I now wanted to use the tooklit to unlock and flash a custom recovery so I can try out CleanRom.
There is no 4.4.3 option in the toolkit.
Question
Can I select the 4.4.2 Build and then unlock the bootloader and flash a custom recovery? This is all I need correct? I typically always used the All in one option in previous devices but since 4.4.3 isn't an option I can't.
While were at it, the other things the "All in one" flash does, such as Busybox, Rename Recovery Restore Files and Root. Do I need to do any of these? What is busybox? Why would I need to rename recovery restore files? Is unlocking bootloader and flashing custom recovery all I need to do to start flashing Roms?
Just making sure as I've always gone the "All in one" Route.
And Yes, I know I can do via ADB but Its been a long time since I've done it and would rather take the familiar route.
bigystyle84 said:
I'm quite familiar with the Skipsoft Toolkits. I've used them plenty of times in the past.
Bought a Nexus 7 2013 today. First thing it wanted to do was update from 4.3 to 4.4.2. I did that. Then 4.4.3. Did that.
I now wanted to use the tooklit to unlock and flash a custom recovery so I can try out CleanRom.
There is no 4.4.3 option in the toolkit.
Question
Can I select the 4.4.2 Build and then unlock the bootloader and flash a custom recovery? This is all I need correct? I typically always used the All in one option in previous devices but since 4.4.3 isn't an option I can't.
While were at it, the other things the "All in one" flash does, such as Busybox, Rename Recovery Restore Files and Root. Do I need to do any of these? What is busybox? Why would I need to rename recovery restore files? Is unlocking bootloader and flashing custom recovery all I need to do to start flashing Roms?
Just making sure as I've always gone the "All in one" Route.
And Yes, I know I can do via ADB but Its been a long time since I've done it and would rather take the familiar route.
Click to expand...
Click to collapse
Don't use toolkits.
I advise learning how to do this operation manually. It's very simple. Read this: http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
I know it's a long read. But seriously, you can unlock the bootloader, fastboot flash an update, flash a recovery, and have root in about 3 minutes.
I would say a normal user does not need busybox. And most apps that require it come with their own version.
Hi guys, i just bought Z1 compact and i want to make a root. Is it possible to root the phone with EasyRootTool if i have option bootloader unlock allowed set to NO?
You can use newroot or towelroot or other method
You can have a root without unlocking bootloader. Bootloader unlocking is other thing. If you have unlocked bootloader you can flash custom kernels
mosespl said:
You can use newroot or towelroot or other method
You can have a root without unlocking bootloader. Bootloader unlocking is other thing. If you have unlocked bootloader you can flash custom kernels
Click to expand...
Click to collapse
I'm trying to root with EasyRootTools, but with no succes by now. Then I manually downloaded towelroot.apk and superSU zip file. I started towellroot.apk and this apk was successfully installed. SuperSu zip file is unzipped on sd card, and when i run supersu.apk from common folder i get error message 'cannot update su binaries'. How can I update this binaries?
rkovacec said:
I'm trying to root with EasyRootTools, but with no succes by now.
[...]
How can I update this binaries?
Click to expand...
Click to collapse
You are at start point as you said. "No success by now"
You must have root, rest is for next steps.
I may be mistaken but EasyRoot is for KK 4.4.
What software do you have on your phone ?
F308 said:
You are at start point as you said. "No success by now"
You must have root, rest is for next steps.
I may be mistaken but EasyRoot is for KK 4.4.
What software do you have on your phone ?
Click to expand...
Click to collapse
I have KitKat 4.4.2 with upgrade 14.3.A.0.757. I try almost everything by now and I just can't believe that I have only z1c which can't be rooted. It must be that sometning i'm doing wrong.
I have been following few instructions with very little diffrences, but stil with no result. There is tutorial on techglen site for unlocked bootloader kitkat 4.4.2 with upgrade 14.3.A.0.757. This is one of tutorials that i followed:
Download the latest tr.apk from toweroot com, copy it to your phone and install it. Click on Make it rain. Once rooted, download update supersu zip from download chainfire eu supersu and extract superuser.apk from common folder. Install this on yoru phone. Run superuser.apk and then update binaries through it.
rkovacec said:
It must be that sometning i'm doing wrong.
Click to expand...
Click to collapse
That's usually the case.