Database Users

Little bit confused

I've been looking at the threads but so far I don't believe there's one that tells you what to do if you've actually installed the official OTA update?
I.e. I have an rooted 2.3.4 GT-I9023 with an unlocked bootloader. With no clockwork or anything, as to be honest the last time I used it (on my old HTC DHD) it made my phone unstable (the phone would sometimes boot up of its own accord and stop at the clockwork screen).
Does anyone know how to re-root the NS after it's installed the official OTA update without clockwork?
Thanks
Edit: Downloading the OTA update won't relock the boot-loader will it?

dccxviii said:
I've been looking at the threads but so far I don't believe there's one that tells you what to do if you've actually installed the official OTA update?
I.e. I have an rooted 2.3.4 GT-I9023 with an unlocked bootloader. With no clockwork or anything, as to be honest the last time I used it (on my old HTC DHD) it made my phone unstable (the phone would sometimes boot up of its own accord and stop at the clockwork screen).
Does anyone know how to re-root the NS after it's installed the official OTA update without clockwork?
Thanks
Edit: Downloading the OTA update won't relock the boot-loader will it?
Click to expand...
Click to collapse
You cannot get root back without a custom recovery. OTA will not relock the bootloader, you'll just lose root and custom recovery.
You need to flash custom recovery using fastboot, then flash superuser to get root back. There are plenty of guides in the stickies describing the process.

Ok, so i'm updated to 2.3.6 but of course have lost root (never had CWM to begin with on this phone). Anyone know where I can DL CWM (i'm assuming it needs to be flashed via platform-tools directory in the android sdk per normal) and the latest su file?
EDIT: nvm, I found the latest CWM and successful flashed (my method was correct). However I've not been able to find the latest superuser.zip to flash yet. Also, I don't know why ppl say to use the market as I don't see how that method can work. I've already got superuser installed from before I updated but that doesn't help me get root. Only flashing the zip from recovery (as I understand it) would. Which renders the market useless in this regard.
/confused

The superuser app checks to see if you have the latest superuser binary and will download and instalk it. Or download superuser from within rom manager.
Sent from my Nexus S 4G using xda premium

Ok..the binary update fails (because i don't have root) so it's chicken and egg as far as I can tell.

You where already told. Flash custom recovery via fastboot. Boot into it and flash su.zip Same way it was done prior to update to the ota. Same as it always was and will be.

dccxviii said:
Ok, so i'm updated to 2.3.6 but of course have lost root (never had CWM to begin with on this phone). Anyone know where I can DL CWM (i'm assuming it needs to be flashed via platform-tools directory in the android sdk per normal) and the latest su file?
EDIT: nvm, I found the latest CWM and successful flashed (my method was correct). However I've not been able to find the latest superuser.zip to flash yet. Also, I don't know why ppl say to use the market as I don't see how that method can work. I've already got superuser installed from before I updated but that doesn't help me get root. Only flashing the zip from recovery (as I understand it) would. Which renders the market useless in this regard.
/confused
Click to expand...
Click to collapse
You can find superuser zip here:
http://rootzwiki.com/showthread.php?231-Superuser-2.3.6.3-17-June-2011&
3rd one down, efgh.
Flash in custom recovery.

albundy2010 said:
You where already told. Flash custom recovery via fastboot. Boot into it and flash su.zip Same way it was done prior to update to the ota. Same as it always was and will be.
Click to expand...
Click to collapse
You've misunderstood what i'm after. Thanks for trying to help tho
irishrally said:
You can find superuser zip here:
http://rootzwiki.com/showthread.php?231-Superuser-2.3.6.3-17-June-2011&
3rd one down, efgh.
Flash in custom recovery.
Click to expand...
Click to collapse
Thanks! As far as I can tell you're the first with the link I was after the entire time.
EDIT: Bah, I get a signature verification error when applying the update >.<

dccxviii said:
You've misunderstood what i'm after. Thanks for trying to help tho
Thanks! As far as I can tell you're the first with the link I was after the entire time.
EDIT: Bah, I get a signature verification error when applying the update >.<
Click to expand...
Click to collapse
Turn off signature verification in CWM and try again.

irishrally said:
Turn off signature verification in CWM and try again.
Click to expand...
Click to collapse
Turns out that CWM got overwritten by stock android recovery. Re-flashing CWM and then flashing su did the trick. I'm rooted once more!
Thanks for your help kind sir!
Curious as to how to make CWM stick for next time tho *shrug*

dccxviii said:
Turns out that CWM got overwritten by stock android recovery. Re-flashing CWM and then flashing su did the trick. I'm rooted once more!
Thanks for your help kind sir!
Curious as to how to make CWM stick for next time tho *shrug*
Click to expand...
Click to collapse
You're welcome.
If you stick with a stock ROM then recovery will reflash every time you reboot. To prevent this you can go to system>etc, and change the file install-recovery.init to something else like install-recovery.init.bak.

[Q] Wont root after manual update?

I just pushed the new 4.2 update via adb,
I then tried re-rooting as I lost root in the project.
I used WugFreshs at first, which said successful. I tried root check and titanium backup which both said no root access.
I then tried mikes toolkit and chose root and install busybox, all that wen through great and said successful, so I retried Tibackup and rootchecker again, both were denied root access.
This time round, rootcheck said "System Running Slow" whilst checking for root access.
What should I do?
Re-boot into recovery and clear cache etc?
Factory reset?
Both?
For some reason superuser is installed not supersu if that makes a difference?
Any help appreciated.

Wilks3y said:
I just pushed the new 4.2 update via adb,
I then tried re-rooting as I lost root in the project.
I used WugFreshs at first, which said successful. I tried root check and titanium backup which both said no root access.
I then tried mikes toolkit and chose root and install busybox, all that wen through great and said successful, so I retried Tibackup and rootchecker again, both were denied root access.
This time round, rootcheck said "System Running Slow" whilst checking for root access.
What should I do?
Re-boot into recovery and clear cache etc?
Factory reset?
Both?
For some reason superuser is installed not supersu if that makes a difference?
Any help appreciated.
Click to expand...
Click to collapse
I apply the update by doing fresh install:
-always backup your data
Then I use wug's nexus root toolkit:
-flash stock + unroot 4.1.2 jzo54k
-flash zip stock + unroot 4.2 jop40c
-change the model type to "NAKASI: Android *.*.* Any build"
-apply root

gesitkumara said:
I apply the update by doing fresh install:
-always backup your data
Then I use wug's nexus root toolkit:
-flash stock + unroot 4.1.2 jzo54k
-flash zip stock + unroot 4.2 jop40c
-change the model type to "NAKASI: Android *.*.* Any build"
-apply root
Click to expand...
Click to collapse
I applied the update over the top of 4.1.2, wiped cache and then restarted.
I then used Wug's toolkit to root, which didn't work.
So I tried Mikes, which also didnt work.
Both report the Root as being succesful, but they arent.
If I change the model to all types on Wug's, would that make a difference?
Is it worth trying a manual root?

I use the Google Nexus 7 Toolkit which was great in fixing the problems after upgrade. Flashing the previous version bootloader (I think that is what it was) solved the root problem. The hints and guidance in this application are great and have always solved my problems. No offence meant to Wug here, I just find the other application suits me better.
Sent using Tapatalk 2

Waxwrong said:
I use the Google Nexus 7 Toolkit which was great in fixing the problems after upgrade. Flashing the previous version bootloader (I think that is what it was) solved the root problem. The hints and guidance in this application are great and have always solved my problems. No offence meant to Wug here, I just find the other application suits me better.
Sent using Tapatalk 2
Click to expand...
Click to collapse
As already said, both Toolkits have been attempted and both report that its rooted, but my device tells me otherwize, as do Titanium Backup.
Can someone just give me a step by step for what I should do to gain Root again?!

Wilks3y said:
As already said, both Toolkits have been attempted and both report that its rooted, but my device tells me otherwize, as do Titanium Backup.
Can someone just give me a step by step for what I should do to gain Root again?!
Click to expand...
Click to collapse
Hi, are you using the fully updated version of Toolkit (updated to include the 4.2 stuff. When I did mine I was told to go ahead but if it didn't work the next step was to flash the 4.1 bootloader? as it was compatible with 4.2
The root with the 4.2 bootloader didn't give me root so I flashed the 4.1 bootloader and rooted again. This was successful for me. The Toolkit application gives you step by step instructions as you request as long as it is updated to do 4.2 and follow the advice you should have no problem.
I don't think you can do the full updates in the application unless you are a donater. If I remember correctly you cannot update the application unless you use the donater version. The update for 4.2 came out at almost the same time as 4.2 was being pushed to devices.
You sound cluey enough to know you must use USB debugging but many users don't realise this or the tapping on the build trick to get the developer options available so you can select USB debugging.
Sent using Tapatalk 2

Waxwrong said:
Hi, are you using the fully updated version of Toolkit (updated to include the 4.2 stuff. When I did mine I was told to go ahead but if it didn't work the next step was to flash the 4.1 bootloader? as it was compatible with 4.2
The root with the 4.2 bootloader didn't give me root so I flashed the 4.1 bootloader and rooted again. This was successful for me. The Toolkit application gives you step by step instructions as you request as long as it is updated to do 4.2 and follow the advice you should have no problem.
I don't think you can do the full updates in the application unless you are a donater. If I remember correctly you cannot update the application donate version. The update for 4.2 came out at almost the same time as 4.2 was being pushed to devices.
You sound cluey enough to know you must use USB debugging but many users don't realise this or the tapping on the build trick to get the developer options available so you can select USB debugging.
Sent using Tapatalk 2
Click to expand...
Click to collapse
Hey mate, thanks for your reply !
I downloaded both ToolKits yesterday, so I'm guessing they are the newly updated ones?
Yes my tablet has usb debugging enabled, and is put into the Camera Mode.
I will have another go tonight, and try a different way, including using the "All Models" choice you mentioned.
If this doens't work, whereabouts in the ToolKit(Wug's) if the option to downgrade HBOOT in order to try the Root method you attempted which was successful.
Again, thanks mate !

Wilks3y said:
Hey mate, thanks for your reply !
I downloaded both ToolKits yesterday, so I'm guessing they are the newly updated ones?
Yes my tablet has usb debugging enabled, and is put into the Camera Mode.
I will have another go tonight, and try a different way, including using the "All Models" choice you mentioned.
If this doens't work, whereabouts in the ToolKit(Wug's) if the option to downgrade HBOOT in order to try the Root method you attempted which was successful.
Again, thanks mate !
Click to expand...
Click to collapse
I don't use Rug's Toolkit but Mike's Toolkit (only because it is easier to follow and use because it tells you what to do at all stages). You can see if it is updated by checking whether it has functions for 4.2 - I always use it for flashing the latest roms as well as the unlocking, root, recovery, etc, all of which the Toolkit guides you through. It even downloads the roms for you.
My only question is why did you put it in camera mode, change it back.
Sent using Tapatalk 2

Just install the 4.2 that is already Stock rooted, de-odexed apps.
Install the ROM as already Stock rooted, de-odexed apps.
Here is the link for the download: http://www.scottsroms.com/downloads.php?do=file&id=288
Thanks to Scott's post http://forum.xda-developers.com/showthread.php?t=1991157

[Q] OTA update to 4.2.2 problems

My 7 is unlocked and rooted, using Nexus Root Toolkit. I did an OTA to get to 4.2.1 some time ago and that went well. Root and unlock persisted. I am now getting OTA options for 4.2.2 from the System menu. First time I got and error in Android's belly. I restarted and was still in 4.2.1. System then said that I was up to date. A week or so later System told me again that OTA was available and I got the same result.
Any suggestions as to how I can do the update?

rsipson said:
My 7 is unlocked and rooted, using Nexus Root Toolkit. I did an OTA to get to 4.2.1 some time ago and that went well. Root and unlock persisted. I am now getting OTA options for 4.2.2 from the System menu. First time I got and error in Android's belly. I restarted and was still in 4.2.1. System then said that I was up to date. A week or so later System told me again that OTA was available and I got the same result.
Any suggestions as to how I can do the update?
Click to expand...
Click to collapse
You have two choices
1. Flash the stock 4.2.2 image using fastboot from here https://developers.google.com/android/nexus/images
Or
2. Flash this in CWM recovery (note this link is for the wifi model) http://android.clients.google.com/p....signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip

You have to restore everything except relocking bootloader ... To be able to update ...when u finish ..just re-root
Sent from my Nexus 7 using xda premium

Same thing happened to me, I had to unroot and then root again after update.
Sent from my HTC Desire S using xda app-developers app

heat361 said:
You have two choices
1. Flash the stock 4.2.2 image using fastboot from here https://developers.google.com/android/nexus/images
Or
2. Flash this in CWM recovery (note this link is for the wifi model) http://android.clients.google.com/p....signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip
Click to expand...
Click to collapse
Thanks for your post. I tried this using Clockwork and got a very long error message. I will quote part of it.
assert failed_apply_patch_check("/system/bin/debuggerd", "a2323a0c8 and a lot more
This is followed by error in file
I saw something about busybox changing some system files.
Any ideas??

How do I unroot without whipping all data?
Sent from my Nexus 7 using xda app-developers app

Search this forum for "OTA debugged"
There are only a few threads - read them all before you take any action.
This particular problem appears to be caused by StickMount.
You don't need to delete everything, nor do you need to flash the ENTIRE stock image - only the boot.img and system.img (via fastboot) without doing a factory reset or any other wiping.
This will unroot the ROM, and (of course) prevent StickMount from working. So you should over flash a SuperSU root kit afterwards (via custom recovery).
This very same problem may recur on the next OTA - so for goodness sake's, make a nandroid backup before you re-install StickMount and give it root privileges.

bftb0 said:
Search this forum for "OTA debugged"
There are only a few threads - read them all before you take any action.
This particular problem appears to be caused by StickMount.
You don't need to delete everything, nor do you need to flash the ENTIRE stock image - only the boot.img and system.img (via fastboot) without doing a factory reset or any other wiping.
This will unroot the ROM, and (of course) prevent StickMount from working. So you should over flash a SuperSU root kit afterwards (via custom recovery).
This very same problem may recur on the next OTA - so for goodness sake's, make a nandroid backup before you re-install StickMount and give it root privileges.
Click to expand...
Click to collapse
Sorry for being a numpty... can someone put the above into a mini step by step guide for me.. I'm stuggling with the terminology.
I rooted my Nexus and have since forgotten anything techie regarding it. I have StickMount and cannot update to 4.2.2..
How do i flash boot.img and system.img via fastboot, where do i get these files from, what versions etc do i need? And over flash SuperSU root kit?
What is OTA?
Basically, I think i need a newbie guide. I am techie enough to achieve most things normally.. i just don't know the android system at all, and what i did know to be able to root it i have completely forgotten!
Any guidance would be very much appreciated. Cheers.

superSU cant update binary

stock recovery, just unlocked and rooted.
superSU said binary need to update, i choose 'normal', then it keep showing the screen as i attached.
remain the same even after reboot.
pls help
Sent from my HTC6435LVW using XDA Premium 4 mobile app

minjiet said:
stock recovery, just unlocked and rooted.
superSU said binary need to update, i choose 'normal', then it keep showing the screen as i attached.
remain the same even after reboot.
pls help
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I would recommend flashing or temporarily booting a custom recovery and then flash the latest version of SuperSu which can be found here in recovery. This should give fix the binary need's to update error your encountering. Let me know if you still have questions.

shimp208 said:
I would recommend flashing or temporarily booting a custom recovery and then flash the latest version of SuperSu which can be found here in recovery. This should give fix the binary need's to update error your encountering. Let me know if you still have questions.
Click to expand...
Click to collapse
how to boot a custom recovery? any link?

minjiet said:
stock recovery, just unlocked and rooted.
superSU said binary need to update, i choose 'normal', then it keep showing the screen as i attached.
remain the same even after reboot.
pls help
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Mine did the same. Then I chose the other option not normal and it installed it automatically through recovery. Before that it might be needed to download twrp recovery from here
http://www.teamw.in/project/twrp2/128. Use Android App Install Method.

I got my nexus 10 yesterday...
did the regular stuff:
fastboot oem unlock followed by fastboot flash recovery ... then i applied SuperSU.1.65 but its not workin > pic below.. any idea folks?
http://tinypic.com/r/2ziocra/5

awyeahh1 said:
I got my nexus 10 yesterday...
did the regular stuff:
fastboot oem unlock followed by fastboot flash recovery ... then i applied SuperSU.1.65 but its not workin > pic below.. any idea folks?
http://tinypic.com/r/2ziocra/5
Click to expand...
Click to collapse
I would recommend flashing SuperSU again in recovery and if that still doesn't work take a look at CF-Auto root which will allow you to gain root access.

shimp208 said:
I would recommend flashing SuperSU again in recovery and if that still doesn't work take a look at CF-Auto root which will allow you to gain root access.
Click to expand...
Click to collapse
thanks for the answer.. I flashed 10x times.. same story... doesn't CF-Auto root flash an old version of supersu which is not compatible with android 4.3 ?

awyeahh1 said:
thanks for the answer.. I flashed 10x times.. same story... doesn't CF-Auto root flash an old version of supersu which is not compatible with android 4.3 ?
Click to expand...
Click to collapse
People have reported that CF-Auto Root works fine with Android 4.3 on the Nexus 10. You can also always update the SuperSU app and binary after successfully rooting with CF-Auto Root.

Thx my prob was solved by appying latest recovery and latest supersu 1.65
Beamed from my Htc kickass Sensation using tapatalk 4.

Same problem here
On starting SuperSU, here’s what I get:
>The SU binary needs to be updated. Continue?
[selected: Continue]
>If you have a custom recovery like TWRP or CWM, that can be used to (try to) install the SU binary. This is recommended for HTC devices. How would you like to install the SU binary? (Normal / TWRP/CWN)
[selected: Normal]
>Installing, please wait
>Installation failed!
As far as I can tell, I can’t install TRWP/CWN because the SuperSU binary is not updated, and I can’t update the the SuperSU binary unless TRWP/CWN is installed. This looks like a vicious circle, can anyone recommend a way out of it please?
Further background:
Device: Evolveo Xtraphone 4.5 Q4, rooted by SRSroot which recognised it as an HTC device.
Also attempted: updating from SD card with UPDATE-SuperSU-v1.86.zip, by running Superuser.apk from the zip folder. This takes me back to square one: “The SU binary needs to be updated. Continue?” etc.
Any recommendations enormously appreciated, thanks!

[Q] Lost Root after OTA update. How to properly re-root without messing the system?

Hello everyone,
I noticed that this is a common problem and I realize just not that I shouldn't have just updated without informing myself.
Anyway, I checked and the root seems to be gone (checked with Root Checker, although the SU app is still there [but not working]).
I checked the fastbook and it says 'unlocked', which is good, I don't have to lose data.
How do I re-root properly?
I am using OS X at the moment and I have access to adb but, if needed, I can access a Windows computer again and use Nexus Root Toolkit again (that's what I used the first time I rooted).
I have CWM-SuperSU-v0.98.zip and recovery-clockwork-6.0.1.9-manta.img.
I checked the bootloader and it says 'no command' but it still has:
- reboot system now
- apply update from ADB
- wipe data...
- wipe cache...
Thanks in advance for any help

First thing - Nearly always you will lose root after applying an OTA - at least lately so that's not really a big deal.
Second - Get and always use the Latest version of root zip from chainfire: http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip
Or you can also just apply SuperSU from google play and you will prompted to reboot to update binaries etc. after you apply the OTA.
His blog on latest version: https://plus.google.com/+Chainfire/posts/QhrEdeJ3nqQ

I got the same problem.
I solved it by just by downgrading and upgrading back to the latest version of Cyanogenmod.
lg Darcade

I have the same problem...
I have the same problem, I have installed the 4.4.3 OTA and now SuperSU stopped working.
Any advice?

Easily got my root back using Wugfresh toolkit.

Only the paid for version of SuperSU - "Pro" will attempt to keep root after an OTA update. It worked perfectly for me on a 5, 7 and 10.

[Lemmy] said:
I have the same problem, I have installed the 4.4.3 OTA and now SuperSU stopped working.
Any advice?
Click to expand...
Click to collapse
Don`t use toolkits, just boot into TWRP in fastboot and reflash the latest superSU.zip and you`re rooted.

gee2012 said:
Don`t use toolkits, just boot into TWRP in fastboot and reflash the latest superSU.zip and you`re rooted.
Click to expand...
Click to collapse
thats what I did by now, just with CWM instead of TWRP.

[Lemmy] said:
thats what I did by now, just with CWM instead of TWRP.
Click to expand...
Click to collapse
Well done mate , toolkits suck and you have no control over them. Flashing with adb gives you full control and you learn something

gee2012 said:
Well done mate , toolkits suck and you have no control over them. Flashing with adb gives you full control and you learn something
Click to expand...
Click to collapse
...after having to go through this over and over again with every single update I'm starting to think that having root is definitely not worth the pain.

If you switch to TWRP using its built in SuperSU install makes re-rooting a breeze.
Sent from my SM-T800 using XDA Premium HD app