Database Users

[Q] How to OTA, stock, root + CWM

I'm trying to install 4.2.1 just because the update message is getting annoying. I tried flashing the stock recovery and using rootkeeper to back-up root. Once I temp un-root and hit the install for the OTA, it begins to flash it, gets to 30%, then says error. I hold the power button to reset and I get a stock recovery error screen that says "No command." From here, I tried flashing stock system.img. This wouldn't write properly, so I ended up re-flashing CWM and simply rebooting and it boots back up fine.
How do I install this freaking OTA?
Edit: Can anyone find the .zip for it? Sideloading will probably work, I just can't find it.
Edit 2: Sideloading didn't work for my N4 which I have the zip for, it fails when verifying the system (related to build.prop). Not sure if the same will happen with the N10.

Help for updating

Hi i have a n7 3g on 4.2.1 rooted..i installed also ota rootkeeper
Now i nave the 422 update downloaded but i ve read the rootkeeper is not functioning on 422 so now if i install the update will my root be safe opening rootkeeper band rerooting with it?
I ve a stock ROM and kernel..just unlock bootloader and root..
sent from rootilapia

I'm also stock rom/kernel, rooted and have cwm recovery, supersu, and voodoo ota rootkeeper. I told ota rootkeeper to backup root. I copied the update file to the N7 and ran the update through cwm recovery. After the update I kept root and kept cwm recovery by answering Yes to a prompt about disabling flashing stock recovery (thus keeping cwm recovery) and Yes to a prompt about recovering root. Very easy overall.

R: Help for updating
Hi to copy the update.zip you used adb or just wired to PC and copied it in the -root of sd?
If i install the update downloaded by the nexus and then run rootkeeper would be good or better install it through recovery?
Really thanks
sent from rootilapia

I downloaded the update (6ece895ecb23.signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip) to my computer and from there to the N7 via usb cable. That way I could easily check the md5 checksum and I don't always trust d/l straight to the N7 although it should work fine. You can even install the zip from the download folder.
Do you have root via Superuser or Supersu? With Supersu and ota rootkeeper (told it to backup root) I kept both root and my cwm recovery. Without them, the update will flash the stock recovery overwriting a custom recovery like cwm or twrp and you will loose root. Even so, you can re-root after getting 4.2.2 and you can install a custom recovery.
I'm not sure if Superuser or twrp recovery gives the same results as I had, but the setup I posted above works beautifully. You do need to backup root with rootkeeper before flashing the update.

i lost root after updating even with rootkeeper. i simply flashed the supersu file i already had on my sd and all is fine

R: Help for updating
I have supersu and i ve configured rootkeeper when just installed means i checked everything
So now if i download the update for nakasig and install it through cwm and then put super su.apk in root of SD and then open rootkeeper and restore root will work?
sent from rootilapia

[Q] Lost root and TWRP after JWR66Y update.

Hi,
I lost root after updating to JWR66Y, and when I open up SuperSU, it says "There is no SU binary installed, and SuperSU cannot install it. This is a problem!"
So I turned off my phone, pressed volume down+power button to go into TWRP and re-flash SuperSU.zip, but the screen only shows broken android with exclamation mark on it.
So, my question is, what do I do? I want to flash TWRP via adb and then flash SuperSU.zip via TWRP. Is that the correct procedure? I'm afraid if something goes wrong I won't have a way to restore my nandroid backup or something.
Thanks.

you always lose root if you take an ota update or flash the factory img. when you flash stock, its just that, stock. its been that way since the beginings of android.
you want to fastboot(not adb) a custom recovery, then flash the latest su binaries via your custom recovery.

simms22 said:
you always lose root if you take an ota update or flash the factory img. when you flash stock, its just that, stock. its been that way since the beginings of android.
you want to fastboot(not adb) a custom recovery, then flash the latest su binaries via your custom recovery.
Click to expand...
Click to collapse
To add on what simms22 said,
SuperSU 1.60 flashable zip: http://download.chainfire.eu/350/SuperSU/UPDATE-SuperSU-v1.60.zip

Help with updated rooted nexus 4 with twrp

Hi, I'm running a stock 4.3 rom with twrp recovery. I initially had the Franco kernel for my phone, but when I encountered recurrent errors when trying to install the 4.4 update I reverted to stock kernel, but I still have the same issues
Whenever I try to flash the update, whether installing directly or through add sideload, I get an error saying 'system/lib/hw/power.msm8690 contains unexpected content,
Error executing updater binary'
And the install fails. Reverting to the stock kernel hasn't helped and neither had updating twrp.
I'm a n00b, so now I'm stuck, hoping someone here can help me out, cheers
Sent from my Nexus 4 using Tapatalk

Instead of using the OTA package, you should flash the full 4.4 rom instead, flashing in recovery won't wipe your data. http://forum.xda-developers.com/showthread.php?t=2527295
Flashing OTA packages using custom recoveries on a modified rom will undoubtly give you issues.

[Q] 4.4.2 undoes my root as soon as I flash SuperSU. Help?

So, against my better judgment, I installed the newest OTA update. I was running rooted 4.4 stock. I unrooted via the SuperSU options and installed the OTA to 4.4.2. Then I booted in recovery mode, loaded TWRP from a command prompt, and flashed SuperSU 1.80. Flash successful. BUT, then I rebooted the phone and it gave me the "Upgrading Android" notification again, just like it did when I first installed the OTA update. Then--no root. I'm assuming that it is undoing my root as soon as I reboot the phone. I tried re-flashing SuperSU and clearing the cache/dalvik before rebooting, but same result.
Help? Ideas? Alternatively, is there any decent firewall out there that doesn't require root, since that's all I need it for?