Database Users

[Q] Updating nexus 7 to 4.1.2 using OTA

Hello,
I've got a Nexus 7 that is rooted, has stock ROM and has CWM recovery (flashed using ROM manager i think). I wanted to update my nexus 7 to 4.1.2 due to the lag bug, but i'm now confused on how to do it after reading a few threads.
I have a few n00b questions:
1. Preferebly, i'd like to update OTA. Will an OTA update notification come up, even though i have CWM recovery? and if it does, will I be able to update using OTA without any problems caused by CWM?
2. How to I keep root access with OTA rootkeeper? Do I install it before I update android? and what if I have SuperSU (not pro version) installed?
3. If I can't update OTA, do I install OTA rootkeeper, install update.zip using CWM recovery and restore root?
I'd really appreciate if anyone could help me out. Thanks.

If you have superSU you can put it in survival mode and it will stick. But I have pro version, not sure if you need that. If you have custom recovery (cwm or twrp) you will need to either go back to stock recovery and OTA, or download and flash the update yourself.
Rootbrain

I received the OTA notification and tried to take it, but it failed because I had renamed the stock browser .apk and .odex files to use the GNex browser that works with flash. After renaming them both back, I copied the OTA from /cache to root and installed it in CWM recovery (choosing 'reboot into recovery' from Rom Manager). I kept CWM recovery and kept root with no problems.

Groid said:
I received the OTA notification and tried to take it, but it failed because I had renamed the stock browser .apk and .odex files to use the GNex browser that works with flash. After renaming them both back, I copied the OTA from /cache to root and installed it in CWM recovery (choosing 'reboot into recovery' from Rom Manager). I kept CWM recovery and kept root with no problems.
Click to expand...
Click to collapse
How did you keep root?
I have superSU installed and it's not the pro version (so no survival mode). Can I use OTA rootkeeper with it?

Is there a guide somewhere that spells out how we can update a rooted Nexus 7 to 4.12? I used the Wugfresh app to root. I'd ask in that topic, but don't have enough posts, yet, to have permission. I realize that there is a lot of info about this here, but some of it is, to me, something of a noob, contradictory and I'm not really sure what I need to do.
I tried doing an OTA update with SuperSU trying to protect root, but it wouldn't install, maybe because I'd used Wugfresh's kit. I’m not sure.
Any help or pointers would be appreciated.

v9s said:
How did you keep root?
I have superSU installed and it's not the pro version (so no survival mode). Can I use OTA rootkeeper with it?
Click to expand...
Click to collapse
I also have Supersu (not pro) and I did install Voodoo OTA Rootkeeper and ran it before installing the OTA. Sorry, should have mentioned that. After the OTA installed, I got an option in CWM to 'flash stock recovery' on reboot. I chose 'no' to keep my CWM recovery. Then I got a prompt to try and regain root, to which I said 'yes'. I booted into the new 4.1.2 and still had root and still had the ability to 'reboot into recovery' from Rom Manager. I feel quite lucky given the threads in which people have had lots of problems, even resorting to loading an older bootloader, modifying scripts, etc. Mine went smooth as silk and my N7 is running great.

Groid said:
I also have Supersu (not pro) and I did install Voodoo OTA Rootkeeper and ran it before installing the OTA. Sorry, should have mentioned that. After the OTA installed, I got an option in CWM to 'flash stock recovery' on reboot. I chose 'no' to keep my CWM recovery. Then I got a prompt to try and regain root, to which I said 'yes'. I booted into the new 4.1.2 and still had root and still had the ability to 'reboot into recovery' from Rom Manager. I feel quite lucky given the threads in which people have had lots of problems, even resorting to loading an older bootloader, modifying scripts, etc. Mine went smooth as silk and my N7 is running great.
Click to expand...
Click to collapse
I've had less luck. I tried to keep root, but the OTA wouldn't install. So I downloaded the .zip and installed it. That got me to 4.1.2, but I can't get root back for reasons that are unclear to me. I go through the process and get what seems like the right feedback, but it's not working for whatever reason. I'm not rooted anymore.
I may have to go back to stock and start over again.

Other posters have said to use the toolkit again to root and install a recovery. Supposedly it works just as well after the update. Is that the process you are using? Did you use stock or a custom recovery? I originally unlocked, rooted, and installed cwm recovery with Wug's rootkit, so I figure it's not the problem.

Groid said:
I also have Supersu (not pro) and I did install Voodoo OTA Rootkeeper and ran it before installing the OTA. Sorry, should have mentioned that. After the OTA installed, I got an option in CWM to 'flash stock recovery' on reboot. I chose 'no' to keep my CWM recovery. Then I got a prompt to try and regain root, to which I said 'yes'. I booted into the new 4.1.2 and still had root and still had the ability to 'reboot into recovery' from Rom Manager. I feel quite lucky given the threads in which people have had lots of problems, even resorting to loading an older bootloader, modifying scripts, etc. Mine went smooth as silk and my N7 is running great.
Click to expand...
Click to collapse
Thanks!
I did exactly what you did before reading your reply and my update process went the same way.

Groid said:
I also have Supersu (not pro) and I did install Voodoo OTA Rootkeeper and ran it before installing the OTA. Sorry, should have mentioned that. After the OTA installed, I got an option in CWM to 'flash stock recovery' on reboot. I chose 'no' to keep my CWM recovery. Then I got a prompt to try and regain root, to which I said 'yes'. I booted into the new 4.1.2 and still had root and still had the ability to 'reboot into recovery' from Rom Manager. I feel quite lucky given the threads in which people have had lots of problems, even resorting to loading an older bootloader, modifying scripts, etc. Mine went smooth as silk and my N7 is running great.
Click to expand...
Click to collapse
Thank you! I followed what you said and it installed perfectly.

Groid said:
Other posters have said to use the toolkit again to root and install a recovery. Supposedly it works just as well after the update. Is that the process you are using? Did you use stock or a custom recovery? I originally unlocked, rooted, and installed cwm recovery with Wug's rootkit, so I figure it's not the problem.
Click to expand...
Click to collapse
Long story short, I couldn't get root. It turns out that some people are having the identical problems that I had, others have had smooth sailing. I ended up going back to 4.1.1. At some point, when things become a little clearer, I'll try this process again.

maigre said:
Long story short, I couldn't get root. It turns out that some people are having the identical problems that I had, others have had smooth sailing. I ended up going back to 4.1.1. At some point, when things become a little clearer, I'll try this process again.
Click to expand...
Click to collapse
I cannot get root or flash a recovery. I am not used to Google device's, I manually updated to 4.1.2, so not really sure how to go back to 4.1.1. It has been a week and I have only just realised, so not real important, but I would like to get twrp back
Sent from my Nexus 7 using Tapatalk 2

Tricky103 said:
I cannot get root or flash a recovery. I am not used to Google device's, I manually updated to 4.1.2, so not really sure how to go back to 4.1.1. It has been a week and I have only just realised, so not real important, but I would like to get twrp back
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Long story short, you could try replacing the 3.41 bootloader that installed with the OTA 4.1.2 with the 3.34 bootloaded from 4.1.1.
Do this with device connected to PC, USB debugging on:
adb reboot bootloader
fastboot flash bootloader bootloader-grouper-3.34.img from the naksi-jro03d-factory-e102ba72.tgz (factory image)
fastboot flash recovery openrecovery-twrp-2.3.0.0-grouper.img (CWM recovery should work too)
fastboot reboot-bootloader
TWRP recovery should start .
flash CWM-SuperSU-v0.96.zip to regain root
update busybox binaries in SuperSU and Busybox free app.
Worked for me.

Groid said:
I received the OTA notification and tried to take it, but it failed because I had renamed the stock browser .apk and .odex files to use the GNex browser that works with flash. After renaming them both back, I copied the OTA from /cache to root and installed it in CWM recovery (choosing 'reboot into recovery' from Rom Manager). I kept CWM recovery and kept root with no problems.
Click to expand...
Click to collapse
I did this installing stock browser, what did you rename it back too. its been so long i forgot what i did. thanks

I have unlocked and rooted my N7 using the Nexus Root Toolkit but I can't remember which version and the desktop has since been formatted.
I have also patched the wallet.apk, modified build.prop (for home screen rotation before 4.1.2)
I got a notification to update the system and thus, went to install Voodoo OTA Root Keeper, protected the root and install the OTA update.
In the bootup screen, I saw the exclamation mark with the android robot but the tablet still managed to boot up.
After the tablet boots up, the settings shows it is still in 4.1.1 but when I do a system check, it mentioned that I'm on the latest.
Can someone advise on how should I go around this?
Thanks!!!

Groid said:
I also have Supersu (not pro) and I did install Voodoo OTA Rootkeeper and ran it before installing the OTA. Sorry, should have mentioned that. After the OTA installed, I got an option in CWM to 'flash stock recovery' on reboot. I chose 'no' to keep my CWM recovery. Then I got a prompt to try and regain root, to which I said 'yes'. I booted into the new 4.1.2 and still had root and still had the ability to 'reboot into recovery' from Rom Manager. I feel quite lucky given the threads in which people have had lots of problems, even resorting to loading an older bootloader, modifying scripts, etc. Mine went smooth as silk and my N7 is running great.
Click to expand...
Click to collapse
This works well, thanks

I am having the same problems as many of you. I rooted my Nexus a while ago and got a prompt for the update today. Here is the error that I am getting. Any ideas which route I should take?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Never mind I think that I just found my answer...
http://forum.xda-developers.com/showthread.php?t=1764794

4.2.2 update

Will the 4.2.2 OTA for my Nexus 7 take away root access?
Sent from my Nexus 4

Yes.
http://forum.xda-developers.com/showthread.php?t=2144330
There's a long thread on 4.2.2 already.

What about the bootloader? Will it relock it? Or is it left alone?
Sent from my Nexus 4

Also, I was just reading through that thread and it said if you have SuperSU that it won't unroot. Is that true? Or do I need to use ota rootkeeper? I know that thread may have the answers I'm looking for, but I'm too tired to read through it all. I ask all these questions because I have no computer to reroot and reunlock the bootloader with.
Sent from my Nexus 4

Slender Troll said:
Also, I was just reading through that thread and it said if you have SuperSU that it won't unroot. Is that true? Or do I need to use ota rootkeeper? I know that thread may have the answers I'm looking for, but I'm too tired to read through it all. I ask all these questions because I have no computer to reroot and reunlock the bootloader with.
Sent from my Nexus 4
Click to expand...
Click to collapse
Afaik it won't relock your bootloader.
Sent from my HTC One X

I flashed back to stock.
Flashed the update
Flashed a SuperSU.zip
Rebooted
Then reinstalled twrp through goo.Im app
When I flashed update I lost root and recovery
And all is good again
Sent from my Nexus 7 using XDA Premium HD app

Slender Troll said:
Will the 4.2.2 OTA for my Nexus 7 take away root access?
Sent from my Nexus 4
Click to expand...
Click to collapse
I was on JOP40D (4.2.1) Stock, rooted, with CWM 6.0.2.3. I downloaded this OTA file http://android.clients.google.com/p....signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip from the link in the other 4.2.2 thread (http://forum.xda-developers.com/showthread.php?t=2144330)
I booted into CWM, and flashed the downloaded ZIP file as normal
When I told CWM to reboot, CWM warned me the update would flash stock Recovery and do I want to STOP this from happening and I said YES.
It then said I had lost root, and do I want to restore root, and I said YES.
It then booted into Android and continued with the upgrade.
I now have 4.2.2 stock installed (JDQ39), and still have root and custom recovery, and an unlocked bootloader.
From what I have read, if you 'sideload' the update using ADB, or do a normal OTA update, you will lose root and custom recovery. However, using the steps above will keep root and recovery for you

What if I'm using TWRP?
Sent from my Nexus 4

Slender Troll said:
What if I'm using TWRP?
Sent from my Nexus 4
Click to expand...
Click to collapse
im in the same boat,
im on 4.1.2 twrp what do i need to do to get to 4.2.2? just use that ota root keeper?

Slender Troll said:
What if I'm using TWRP?
Sent from my Nexus 4
Click to expand...
Click to collapse
TWRP is same to CMW, but for sure you should install Voodoo OTA Rootkeeper, backup SU then flash the 4.2.2 update.zip. Finally, open Voodoo and restore the backup SU --> your Root is kept. Just in case you need to verify root will work or not. Go to Play Store, install Root Checker (joeykrim) and check your root permisson.
I updated my N7 to 4.2.2 without removing root by these steps above.

Benjoy Ericsson said:
TWRP is same to CMW, but for sure you should install Voodoo OTA Rootkeeper, backup SU then flash the 4.2.2 update.zip. Finally, open Voodoo and restore the backup SU --> your Root is kept. Just in case you need to verify root will work or not. Go to Play Store, install Root Checker (joeykrim) and check your root permisson.
I updated my N7 to 4.2.2 without removing root by these steps above.
Click to expand...
Click to collapse
Can I do this without a computer?
Sent from my Nexus 4

Slender Troll said:
Can I do this without a computer?
Sent from my Nexus 4
Click to expand...
Click to collapse
Yes, if you can put your 4.2.2 OTA update.zip in your N7 Internal Storage.
Maybe by downloading the zip through wifi connect.

Benjoy Ericsson said:
Yes, if you can put your 4.2.2 OTA update.zip in your N7 Internal Storage.
Maybe by downloading the zip through wifi connect.
Click to expand...
Click to collapse
Wi-Fi connect? And where do I put it once I have it?
Sent from my Nexus 4

Slender Troll said:
What if I'm using TWRP?
Sent from my Nexus 4
Click to expand...
Click to collapse
I don't think it matters...
I used TWRP to flash the update.
Afterwards, the bootloader was still unlocked... but had been updated from 4.13 to 4.18.
And I had to reflash TWRP as the update had wiped it out, effectively resetting recovery back to Googles default recovery.
Rgrds,
Ged.

Slender Troll said:
Wi-Fi connect? And where do I put it once I have it?
Sent from my Nexus 4
Click to expand...
Click to collapse
This is OTA link for N7 Wifi Only.
Connect to wifi, download the 4.2.2 update.zip to your internal storage from this link http://android.clients.google.com/p....signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip (anywhere is ok, be sure to remember the path). Reboot your N7 to recovery mod (TWRP), choose install and browse to where you put your zip in internal storage.

Benjoy Ericsson said:
Connect to wifi, download the 4.2.2 update.zip to your internal storage from this link http://android.clients.google.com/p....signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip (anywhere is ok, be sure to remember the path). Reboot your N7 to recovery mod (TWRP), choose install and browse to where you put your zip in internal storage.
Click to expand...
Click to collapse
Just to clarify, I can leave it in the download folder?
Sent from my Nexus 4

So I'm in recovery and at the part where it gives me the option to flash. Is there anything I need to do or back up before I flash the OTA so that I don't lose root?
Sent from my Nexus 4

Success!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 7 using Tapatalk HD

Just downloaded the OTA zip, went to recovery and tried "install" (both checkmarks to check md5 and zip off) and got FAILED! The device booted normally afterwards. I copied file via USB cable in standard media mode... what am I doing wrong? On 4.2.1, stock, rooted, 16gb Wifi only N7.

dalanik said:
Just downloaded the OTA zip, went to recovery and tried "install" (both checkmarks to check md5 and zip off) and got FAILED! The device booted normally afterwards. I copied file via USB cable in standard media mode... what am I doing wrong? On 4.2.1, stock, rooted, 16gb Wifi only N7.
Click to expand...
Click to collapse
Try downloading it using Wi-Fi from the link above, and then back everything up. what recovery are you using? I left the zip in the download folder, so I wouldn't lose it.
Sent from my Nexus 4

[VK810] Official Kit Kat Update Information

We're all in the process of receiving and installing this update, and there are many questions about recoveries, rooting, etc. This is a thread to gather all the info we know so people don't have to be searching through tons of posts.
(I'm in the process of installing now, so I'll answer as many of these questions as I can. I will also update the OP with info from other users. If anything I state is untrue, please post and let me know.)
Can I take the update while rooted?
Yes! If you are on 4.2 and rooted but on STOCK RECOVERY, you can take the OTA and keep root.
Can I take the update with TWRP installed?
No! You will bootloop into recovery.
Is there an alternative/manual/TWRP method of installing?
Yes, see below post.
How am I supposed to update if I installed TWRP?
See below post, "README if you are currently on JB4.2.2"
Alternative method: "download flashify from the play store, backup twrp, then flash the recovery.img from OP. No pc needed & 100% pain free." Thank you to 86shelby. Then take the OTA.
Can I root the 4.4 version?
As of 8/26, yes! Stumproot works with the Bruteforce method. http://forum.xda-developers.com/show....php?t=2850906
Can I downgrade from 4.4 to 4.2?
Yes
If anyone else has questions they'd like posted, please let me know, and I'll put them in.

NOTE: If you want root/twrp in KK4.4.2, you'll need to pre-root in JB4.2.2 before OTA update(towelroot works in JB4.2.2, but not in KK4.4.2)
Looks like Stumproot works with KK4.4.2
README if you have a non-booting device
If you tried OTA update with TWRP recovery and get stuck in a bootloop for TWRP
Do one of the options below:
A) If you still want 4.4.2 via Verizon OTA, flash stock recovery
Go into TWRP, restore stock recovery via link below
http://forum.xda-developers.com/showpost.php?p=52975059&postcount=65
B) If you want to stop the bootloop, and flash 4.4.2 via TWRP backup from below...
Go into TWRP, wipe OTA partition (which signals the device to keep going into recovery)
http://forum.xda-developers.com/showthread.php?p=51749086#post51749086
Click to expand...
Click to collapse
If I mess everything up and device doesn't boot
Restore (B) the entire device back to 4.2.2 using the kdz file(more complicated and you lose all your settings/files/apps)​
README if you are currently on JB4.2.2
If you already have TWRP, you can flash 4.4.2 via the TWRP backup below (probably can just flash over 4.2.2 without factory reset... do factory reset only if something goes wrong)
http://forum.xda-developers.com/showthread.php?p=53043541#post53043541
If you want to apply update via Verizon OTA, READ below first
If you have TWRP installed, you'll need to flash stock recovery. Either (A)
restore stock recovery only, or restore (B) the entire device back to 4.2.2 using the kdz file(more complicated and you lose all your settings/files/apps)
NOTE: some people have problems with OTA even after restoring stock recovery. You'll have to restore using the (B) method, and lose everything
[*]If you want root in 4.4.2, you'll need to apply root BEFORE OTA (via towelroot, ...?). root is allowed during OTA, will be maintained after OTALooks like stumproot works
Apply OTA, hope nothing goes wrong
Yay!
Click to expand...
Click to collapse
README if you are currently on KK4.4.2
Splitwindow/multiwindow on 4.4.2
http://forum.xda-developers.com/lg-...10-splitwindow-multiwindow-stock-4-4-t2837326
Root on 4.4.2: Use Stumproot
TWRP on 4.4.2
Root ? (Towelroot isn't working though)
Flash 4.2.2 aboot.img and TWRP.img
A) Upload aboot.img from 4.2.2 to device, then do
Code:
adb shell
su
dd if=/sdcard/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
B) Follow steps in TWRP thread to install TWRP
Click to expand...
Click to collapse
4G LTE does not work on 4.4.2?
Flash modem from 4.2.2 -> http://forum.xda-developers.com/showpost.php?p=54584896&postcount=5
Going from 4.4.2 back to 4.2.2
Install TWRP (see section above)
Get 4.2.2 TWRP backup from here and restore
or restore (B) the entire device back to 4.2.2 using the kdz file(more complicated and you lose all your settings/files/apps)
Click to expand...
Click to collapse
​

Guess I got lucky - never got around to installing the custom recovery. I MEANT to do that....

https://pvzwmdmcdn.vzw.motive.com/firmware/LG_VK810_11A_TO_22B.bin
in case you want to poke around
Verizon LG G2 users say it's okay to be rooted, just need stock recovery for OTA update... let's see what happens..
yeah, 0x136 error when it tries to update. people say 0x136/0x13E errors are because of unlocked bootloaders... i guess we need to flash completely stock via KDZ file, then take ota, then use stuff like towelroot

So this is what I get when I check for update. I'm stock unrooted I even did a FDR. Any ideas?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my XT1080 using Tapatalk

Towelroot doesn't work yet with the new update. I took the update completely stock and unrooted and I'm not able to root now.

modus81 said:
Towelroot doesn't work yet with the new update. I took the update completely stock and unrooted and I'm not able to root now.
Click to expand...
Click to collapse
have you tried other root methods?
ioroot, or this root below? (
http://forum.xda-developers.com/showthread.php?t=1886460&highlight=4+2+2

paperWastage said:
https://pvzwmdmcdn.vzw.motive.com/firmware/LG_VK810_11A_TO_22B.bin
in case you want to poke around
Verizon LG G2 users say it's okay to be rooted, just need stock recovery for OTA update... let's see what happens..
yeah, 0x136 error when it tries to update. people say 0x136/0x13E errors are because of unlocked bootloaders... i guess we need to flash completely stock via KDZ file, then take ota, then use stuff like towelroot
Click to expand...
Click to collapse
How do I install this?
Sent from my VK810 4G using Tapatalk

gfullwr70 said:
How do I install this?
Sent from my VK810 4G using Tapatalk
Click to expand...
Click to collapse
you don't. go through Settings-> System update

paperWastage said:
you don't. go through Settings-> System update
Click to expand...
Click to collapse
Ok thanks. Check my above post and pic. I get that everyone I try there check for update.
Sent from my XT1080 using Tapatalk

gfullwr70 said:
Ok thanks. Check my above post and pic. I get that everyone I try there check for update.
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
Same here

Flashing comletely stock via .kdz file
I'm getting the 0X13E error. Does anyone have the the process for this? I saw a different thread that directed to a droidreviews.com website but one of the files it said to download, my Chrome browser scanned as malicious so I stopped pursuing that route.

ssinn said:
Same here
Click to expand...
Click to collapse
gfullwr70 said:
Ok thanks. Check my above post and pic. I get that everyone I try there check for update.
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
you could try forcing the update (manually place the file and the start the apk)
see if the steps below can help you
http://forum.xda-developers.com/showthread.php?t=2699123

paperWastage said:
you could try forcing the update (manually place the file and the start the apk)
see if the steps below can help you
http://forum.xda-developers.com/showthread.php?t=2699123
Click to expand...
Click to collapse
Thanks this is what I was looking for. I'll give it till tonight to see if the ota shows up then I'll try this method.
Sent from my XT1080 using Tapatalk

paperWastage said:
you could try forcing the update (manually place the file and the start the apk)
see if the steps below can help you
http://forum.xda-developers.com/showthread.php?t=2699123
Click to expand...
Click to collapse
So is this only if you can't download the ota update or if you get an error while trying to install it after downloading it?

prana22 said:
So is this only if you can't download the ota update or if you get an error while trying to install it after downloading it?
Click to expand...
Click to collapse
first one.... my tablet wasn't able to find an OTA on 4G LTE (on t-mobile's network), but wifi works fine

Mine prompted me yesterday and I was not sure I wanted to yet (wait for other victims...). It would only let me delay it up to 24 hours, so it was going to annoy me. I let it update today and it looks fine. I did not unlock or change my recovery, but had used towelroot to gain root.
After update, it appears that root is still there.
The only glitch I have noticed is that my Mobile Hotspot (wifi name/pass) were reset to defaults.

rjkmadison said:
Mine prompted me yesterday and I was not sure I wanted to yet (wait for other victims...). It would only let me delay it up to 24 hours, so it was going to annoy me. I let it update today and it looks fine. I did not unlock or change my recovery, but had used towelroot to gain root.
After update, it appears that root is still there.
The only glitch I have noticed is that my Mobile Hotspot (wifi name/pass) were reset to defaults.
Click to expand...
Click to collapse
That's interesting, and good to know. Can anyone else verify this? I didn't think the update would go through if you were rooted. Now I might downgrade through kdz again and root before I take the OTA.

rjkmadison said:
Mine prompted me yesterday and I was not sure I wanted to yet (wait for other victims...). It would only let me delay it up to 24 hours, so it was going to annoy me. I let it update today and it looks fine. I did not unlock or change my recovery, but had used towelroot to gain root.
After update, it appears that root is still there.
The only glitch I have noticed is that my Mobile Hotspot (wifi name/pass) were reset to defaults.
Click to expand...
Click to collapse
go flash TWRP, make backup of stock and share it please?

How can I revert to stock recovery in OSX? All I see is the LG Mobile tool for windows?

[Q] SuperSU can't detect su binary after reboot

I rooted my phone with Kingroot, and ran this script to replace the Kinguser with SuperSU: http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html?m=1
After launching SuperSU it updates the binary and everything works fine until I reboot my phone. Now when I launch SuperSU it says no su binary installed. Using es file explorer I can see the su is in /system/xbin where it should be but SuperSU can't see it.
After rerooting with Kingroot and doing the same process over SuperSU will once again work fine until I reboot my phone. Anyone know what's going on and how I can get SuperSU to work properly?

Anyone?
I tried flashing the SuperSU.zip, but when I launch the app it fails to update the binary. I've also tried installing ChainsDD Superuser but it also fails to update the binary. I've even tried manually copying, setting permissions, and symlinking the files found in the SuperSU.zip, but it still fails to update.
I don't like using Kingroot because apps like Titanium Backup and Lucky Patcher don't work with it's su binary. Has anyone encountered this before? Why won't SuperSU update? And when it does update why can't it survive past a reboot? This is stressful ha. Any help is very much appreciated.
By the way I'm using a Cricket Galaxy S4 (SGH-I337Z). It's a weird model that few people seem to know about (I337ZTUUBOA1). The only root method that works on it is Kingroot otherwise I would have just rooted it some other way.

I had an idea wile reading your post could u try flashing TWRP for ur phone then rooting with the built in installer might be worth a try but u might need to Un root or flash back to what ever firmware ur using to remove root so that TWRP sees that ur not rooted

xstokerx said:
I had an idea wile reading your post could u try flashing TWRP for ur phone then rooting with the built in installer might be worth a try but u might need to Un root or flash back to what ever firmware ur using to remove root so that TWRP sees that ur not rooted
Click to expand...
Click to collapse
I've got twrp flashed. How do I use the built in root installer??

When u boot into system from TWRP it will ask you if u want to root the system but it only asks if TWRP can't detect root.

xstokerx said:
When u boot into system from TWRP it will ask you if u want to root the system but it only asks if TWRP can't detect root.
Click to expand...
Click to collapse
I unrooted and rerooted with twrp. It installed su binary, but when I install SuperSU and launch it it still gives the no binary installed error

Nihilian said:
I unrooted and rerooted with twrp. It installed su binary, but when I install SuperSU and launch it it still gives the no binary installed error
Click to expand...
Click to collapse
Try rooting with kingroot, then uninstall king user by going into king user and unrooting. Once that is done, download the newest version of SuperSU.zip (update-supersuv2.46.zip I think is newest) then copy to phone storage, reboot to twrp and then flash the SuperSU zip. Reboot and profit!
Hope this helps!
Sent from my A0001 using XDA Free mobile app

Nihilian said:
I unrooted and rerooted with twrp. It installed su binary, but when I install SuperSU and launch it it still gives the no binary installed error
Click to expand...
Click to collapse
Sorry to hear was worth a shot I can't think of any thing else right now :crying:

Klown80 said:
Try rooting with kingroot, then uninstall king user by going into king user and unrooting. Once that is done, download the newest version of SuperSU.zip (update-supersuv2.46.zip I think is newest) then copy to phone storage, reboot to twrp and then flash the SuperSU zip. Reboot and profit!
Hope this helps!
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Still no luck I think it's an issue with the SuperSU app. Something during a reboot causes it to break for some reason. I really hope it can be fixed :/

Well only thing I can think of is odin to stock and start over or find a nice custom rom that works with your phone that comes pre rooted if there are any.......

xstokerx said:
Well only thing I can think of is odin to stock and start over or find a nice custom rom that works with your phone that comes pre rooted if there are any.......
Click to expand...
Click to collapse
Finally found a working custom rom and everything is working. Thanks

Nihilian said:
Finally found a working custom rom and everything is working. Thanks
Click to expand...
Click to collapse
Awsome to hear u found something that works for u and ur welcome ?

I don't wanna open new topic coz I have similar problem.....
I have huawei g630, rooted and unlocked bootloader, but no cwm.... and supersu gives me this messages.....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and when I click on that phone restarts and nothing happens..... when I cancel that this is msg.....
what could be the problem?

jabre said:
I don't wanna open new topic coz I have similar problem.....
I have huawei g630, rooted and unlocked bootloader, but no cwm.... and supersu gives me this messages.....
and when I click on that phone restarts and nothing happens..... when I cancel that this is msg.....
what could be the problem?
Click to expand...
Click to collapse
I'm sorry but I probly can't help I know nothing about your phone this is the att/Canadian s4 forum how did u get your phone rooted? U can try unrooting and rooting with a different method or retry with same method

Everything stock, suddenly stuck on Boot loop after reboot.

Short version: Nexus 4 is stuck on bootloop but it's as good as new with the stock ROM and everything.
Long version: My nexus 4 has stock kernel, stock ROM of Lollipop that was updated when google rolled it out few months back. I did have my bootloader unlocked via Nexus Root Toolkit few months back while i still had KitKat, but apart from that, i have NEVER ROOTED, NEVER INSTALLED A CUSTOM RECOVERY, NEVER CHANGED KERNEL, NEVER INSTALLED ANY OTHER CUSTOM ROMs. The only tampering i did was unlock the bootloader and never bothered anything else. But suddenly, my phone got stock on bootloop last night. I powered it off normally, full charged the phone, and when i turned it on, it got stuck ever since. It did happen once when the phone updated to lollipop for the first time, but a simple restart solved it that time. I have tried wiping cache, factory resetting and wiping cache again, but no luck so far.
All posts related to stuck bootloop in XDA are because of tampering the phone, installing a custom ROM, going back to stock etc. I didn't find a relevant post if this happens while still in stock with never tampered phone. If there is a post like that, please kindly redirect me there. I am left without a clue here with very less experience outside stock stuff.
PLEASE HELP !

cart00nist said:
Short version: Nexus 4 is stuck on bootloop but it's as good as new with the stock ROM and everything.
Long version: My nexus 4 has stock kernel, stock ROM of Lollipop that was updated when google rolled it out few months back. I did have my bootloader unlocked via Nexus Root Toolkit few months back while i still had KitKat, but apart from that, i have NEVER ROOTED, NEVER INSTALLED A CUSTOM RECOVERY, NEVER CHANGED KERNEL, NEVER INSTALLED ANY OTHER CUSTOM ROMs. The only tampering i did was unlock the bootloader and never bothered anything else. But suddenly, my phone got stock on bootloop last night. I powered it off normally, full charged the phone, and when i turned it on, it got stuck ever since. It did happen once when the phone updated to lollipop for the first time, but a simple restart solved it that time. I have tried wiping cache, factory resetting and wiping cache again, but no luck so far.
All posts related to stuck bootloop in XDA are because of tampering the phone, installing a custom ROM, going back to stock etc. I didn't find a relevant post if this happens while still in stock with never tampered phone. If there is a post like that, please kindly redirect me there. I am left without a clue here with very less experience outside stock stuff.
PLEASE HELP !
Click to expand...
Click to collapse
Did it just spontaneously reboot and go into a bootloop? Will it boot into the Bootloader? If so, you might try reflashing the image files directly and see if that fixes it. You can do that using Wug's NRT and selecting the Soft-Brick option under Stock + Unroot.
Hopefully that works. If not, it could be a hardware failure, but exhaust software side fixes first.

ariesgodofwar said:
Did it just spontaneously reboot and go into a bootloop? Will it boot into the Bootloader? If so, you might try reflashing the image files directly and see if that fixes it. You can do that using Wug's NRT and selecting the Soft-Brick option under Stock + Unroot.
Hopefully that works. If not, it could be a hardware failure, but exhaust software side fixes first.
Click to expand...
Click to collapse
No, i turned it off myself. Then charged the battery to 100% and then turned it back on. It got in the bootloop ever since. After u suggested, i downloaded the stock ROM and tried flashing it using Wug's NRT selecting the soft-brick option. Everything went smoothly but I am still stuck with the bootloop. If it's a hardware problem, i'm as good as screwed. There is no LG Service Center in Nepal!

cart00nist said:
No, i turned it off myself. Then charged the battery to 100% and then turned it back on. It got in the bootloop ever since. After u suggested, i downloaded the stock ROM and tried flashing it using Wug's NRT selecting the soft-brick option. Everything went smoothly but I am still stuck with the bootloop. If it's a hardware problem, i'm as good as screwed. There is no LG Service Center in Nepal!
Click to expand...
Click to collapse
How long did you wait after booting it after flashing the stock ROM? It can sometimes take a while to boot the first time.

theminikiller said:
How long did you wait after booting it after flashing the stock ROM? It can sometimes take a while to boot the first time.
Click to expand...
Click to collapse
About 10 minutes.
In another note, I don't have custom recovery or root access. But i found that i can install a custom ROm i.e. cyanogenmod using Nexus Root Toolkit. Will i run to any known problem if i do that?

cart00nist said:
About 10 minutes.
Click to expand...
Click to collapse
I would suggest you try again and wait maybe a little over half an hour to see if it boots then.

theminikiller said:
I would suggest you try again and wait maybe a little over half an hour to see if it boots then.
Click to expand...
Click to collapse
Ok, will try again.
In another note, I don't have custom recovery or root access. But i found that i can install a custom ROm i.e. cyanogenmod using Nexus Root Toolkit. Will i run to any known problem if i do that?

cart00nist said:
Ok, will try again.
In another note, I don't have custom recovery or root access. But i found that i can install a custom ROm i.e. cyanogenmod using Nexus Root Toolkit. Will i run to any known problem if i do that?
Click to expand...
Click to collapse
You shouldn't, just make sure it's for the same android version.

theminikiller said:
You shouldn't, just make sure it's for the same android version.
Click to expand...
Click to collapse
I flashed it again and It's been exactly half an hour but it's still stuck with the same four colorful dots rotating screen. Could it be because of the ROM build? I saw that there is a previous build of the same lollipop 5.1.1 in google's link.. Should i try flashing that instead?

cart00nist said:
I flashed it again and It's been exactly half an hour but it's still stuck with the same four colorful dots rotating screen. Could it be because of the ROM build? I saw that there is a previous build of the same lollipop 5.1.1 in google's link.. Should i try flashing that instead?
Click to expand...
Click to collapse
You could, you could also try flashing a custom recovery and then installing a custom ROM to see if that helps.

theminikiller said:
You could, you could also try flashing a custom recovery and then installing a custom ROM to see if that helps.
Click to expand...
Click to collapse
How do i flash a custom recovery from fastboot mode? Since i cannot go to the homescreen and turn on USB debugging, i cannot root the device. The NRT only has root+custom recovery together in a single button. Since i only need the custom revovery and that also i need to install it by staying in the fastboot mode, how do i do it? This is the only phone i have and i cannot afford another phone anytime soon. Thankyou so so much for helping me

cart00nist said:
How do i flash a custom recovery from fastboot mode? Since i cannot go to the homescreen and turn on USB debugging, i cannot root the device. The NRT only has root+custom recovery together in a single button. Since i only need the custom revovery and that also i need to install it by staying in the fastboot mode, how do i do it? This is the only phone i have and i cannot afford another phone anytime soon. Thankyou so so much for helping me
Click to expand...
Click to collapse
Try following this guide: http://forum.xda-developers.com/showthread.php?t=2018179
Your bootloader is already unlocked so you can ignore that part of the guide. Follow the instructions to install adb and fastboot. Then instead of using adb commands to boot into the bootloader do it by first powering off your phone, then power it on while holding the volume down button.
When you are there follow the instructions to flash a recovery image, but instead of using CWM as is suggested there use TWRP instead from this link: http://forum.xda-developers.com/showthread.php?t=2002326 there will be a link in the post to their webpage where you can download the image file. The reason I recommend TWRP over CWM is that CWM is discontinued and haven't been updated in a while.
Then use the same command as in the guide to flash the recovery image, just use the TWRP image file instead. You can ignore the root part since custom Rom's come pre-rooted. Then to flash a custom ROM follow the guide to boot into recovery. Once there you should be able to copy files from your computer and to your phone.
To then install a custom ROM find a ROM you want to try, some stable ones right now are XenonHD and Chroma. Download the zip file from their thread, download a GApps package. There is usually a link to one in the ROM threads. Then copy those two files to your phone.
Then in recovery choose to do a factory reset. Then choose to install first the ROM zip and then the GApps zip, and then wipe cache. You should then try to boot it up normally.
Let's hope that works, but ask if something is unclear. ☺

theminikiller said:
Try following this guide: http://forum.xda-developers.com/showthread.php?t=2018179
Your bootloader is already unlocked so you can ignore that part of the guide. Follow the instructions to install adb and fastboot. Then instead of using adb commands to boot into the bootloader do it by first powering off your phone, then power it on while holding the volume down button.
When you are there follow the instructions to flash a recovery image, but instead of using CWM as is suggested there use TWRP instead from this link: http://forum.xda-developers.com/showthread.php?t=2002326 there will be a link in the post to their webpage where you can download the image file. The reason I recommend TWRP over CWM is that CWM is discontinued and haven't been updated in a while.
Then use the same command as in the guide to flash the recovery image, just use the TWRP image file instead. You can ignore the root part since custom Rom's come pre-rooted. Then to flash a custom ROM follow the guide to boot into recovery. Once there you should be able to copy files from your computer and to your phone.
To then install a custom ROM find a ROM you want to try, some stable ones right now are XenonHD and Chroma. Download the zip file from their thread, download a GApps package. There is usually a link to one in the ROM threads. Then copy those two files to your phone.
Then in recovery choose to do a factory reset. Then choose to install first the ROM zip and then the GApps zip, and then wipe cache. You should then try to boot it up normally.
Let's hope that works, but ask if something is unclear.
Click to expand...
Click to collapse
Installed TWRP, and then installed XenonHD. Everything went ultra smooth. Again got stuck in the same boot screen. Tried factory reset, doesn't work! I'm screwed!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

cart00nist said:
Installed TWRP, and then installed XenonHD. Everything went ultra smooth. Again got stuck in the same boot screen. Tried factory reset, doesn't work! I'm screwed!
Click to expand...
Click to collapse
I'm afraid that the only suggestion I have left is to try flashing a factory image manually instead of using the toolkit. This is a guide on how to do it: http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/

theminikiller said:
I'm afraid that the only suggestion I have left is to try flashing a factory image manually instead of using the toolkit. This is a guide on how to do it: http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
Click to expand...
Click to collapse
Haha. I was out for a while and my stupid brother flashed a Droid ROM of about 900MB. I don't know what he was thinking. I cannot even scold him because he his my cousin. lol
Now the phone doesn't even turn on. It probably is on because when i connect it to the PC, the new hardware is detected and the driver is also probably installed, because the windows doesn't say the driver installation was failed. But i cannot see anything on the screen. I am about to throw my phone in the trashcan. lol I feel so stupid. Do you have any last suggestion for me?

cart00nist said:
Haha. I was out for a while and my stupid brother flashed a Droid ROM of about 900MB. I don't know what he was thinking. I cannot even scold him because he his my cousin. lol
Now the phone doesn't even turn on. It probably is on because when i connect it to the PC, the new hardware is detected and the driver is also probably installed, because the windows doesn't say the driver installation was failed. But i cannot see anything on the screen. I am about to throw my phone in the trashcan. lol I feel so stupid. Do you have any last suggestion for me?
Click to expand...
Click to collapse
Do you get any feedback if you use the command "fastboot devices"?

theminikiller said:
Do you get any feedback if you use the command "fastboot devices"?
Click to expand...
Click to collapse
Oh rite i forgot to tell you. i did fastboot devices and so far it doesn't show up the serial number of my phone.

cart00nist said:
Oh rite i forgot to tell you. i did fastboot devices and so far it doesn't show up the serial number of my phone.
Click to expand...
Click to collapse
In that case I unfortunately don't have any more ideas, sorry. I wish you luck with your phone tho, maybe some other member here at xda has any other ideas.