My nexus 7 is rooted. Is that why it can't accept the 4.1.2 update? What should I do? It keeps reminding me to install the update every 15 minutes. When I try to, it just crashes.
Sent from my Nexus 7 using xda app-developers app
You want to eat from two tables ... ? It's your choice, original or rooted ...
Sent from my Nexus 7 using xda app-developers app
I'm trying to update it while keeping root. I downloaded ota root keeper. But I keep getting the "dead Android with red exclamation mark" screen every time I try to install the OTA update. I even tried its option to temporarily un-root before performing the update, but no luck. Anyone have any ideas?
Edit - Also I tried installing it manually. Used GooManager to install TWRP and tried installing 4.1.2 through it. Still fails every time. I'm disgusted.
Sent from my Nexus 7 using xda app-developers app
I had my Nexus 7 rooted w/ the "Google Nexus 7 Toolkit" and I was able to update to 4.1.2 w/o any problems.
Sent from my Nexus 7 using xda app-developers app
Having the same issue as well..Can't root.
Sent from my GT-I9100 using xda premium
---------- Post added at 02:41 PM ---------- Previous post was at 02:25 PM ----------
Well after trying again I finally successed doing so.
Sent from my GT-I9100 using xda premium
Backup--unroot--relock--update--unlock--reroot--recover? I'm brand new to this stuff (don't even have a N7 yet), but seems like this would work.
The stock update will only install with stock recovery being root has no effect. If you have changed system apps. Like to the 4.2 apps floating around could stop the update as well. Google does not care another root or unlocked. I would say do factory reset then update then root. Or download one of the stock cwm/twelve roms and be done with it.
Sent from my Nexus 7 using Tapatalk 2
Well it happened again. The 4.2.2 update is out and I can't update to it. Every time I try, I get the dead android error icon.
It sure gets old saying this, but...
The error message is recorded in the recovery log at
/cache/recovery/recovery.log
You will find that the problem has nothing to do with root per se - generally the root user (or apps that were granted root privilege) have altered or deleted something in /system needed for the OTA to correctly complete.
In general, OTAs are not meant for customized ROMs - it is unreasonable for anyone to have an expectation that they will work correctly on a customized ROM.
But I didn't install a customized rom. I just rooted/unlocked it.
You can always download the update from Google's servers and flash it through fastboot. No hassle.
Bryon15 said:
But I didn't install a customized rom. I just rooted/unlocked it.
Click to expand...
Click to collapse
the proof is in the pudding...
...and the pudding is at /cache/recovery/recovery.log
bftb0 said:
generally the root user (or apps that were granted root privilege) have altered or deleted something in /system needed for the OTA to correctly complete.
Click to expand...
Click to collapse
Note that the recovery.log file gets overwritten every time you boot the recovery, so the thing you are trying to retrieve (let's say with the booted OS) will be from the immediately prior use of the recovery. So, attempt the OTA (let it fail), then boot into the OS and capture that file (using something which is root-privileged).
Related
I just manually updated jelly bean to 4.1.2 using CWM and I don't have root anymore. I'm going to try rerooting when I get home but, I was wondering, will I be able do it without losing all my data?
I have exactly the same issue, I'ved tried either using NRT or manually, not success and no error as well
Your bootloader should still be unlocked, so its a simple matter of installing the JB SuperSU zip. You can download this from my drop box.
http://db.tt/jlsmjBz3
your data should remain intact.
Sent from my Nexus 7 using XDA Premium HD app
Wow, I can't even boot into CWM anymore even though I was able to this morning. I have the USB connected to get around the bug, and I've ever tried using ADB. I'll let you know how it goes after fixing this problem first.
[edit]
I couldn't boot into CWM despite my efforts. I ended up using Wug's Nexus Root Toolkit, which thankfully supports 4.1.2 already, and re-rooted and it worked like a charm. Here's the link to the tool kit for anyone who needs it: http://forum.xda-developers.com/showthread.php?t=1766475
Flash new JB bootloader. This will fix the old bootloader bug of not being able to boot into recovery without the aid of a PC.
http://db.tt/cgk5NmQn
Sent from my Nexus 7 using XDA Premium HD app
To save you the hassle next time you update, give ota rootkeeper a try. It's free on the market.
Sent from my Nexus 7 using xda app-developers app
Root again
I rooted again with Nexus Root Toolkit version v1.5.3. I only pressed "Root" button (10 minutes).
Can I Re root without pc?
How do you flash without access to recovery? Adb?
I never thought I would be the person ignoring a system update but after 3 unsuccessful attempts at installing the latest iteration of Android its not looking good. There is an error message showing up after about 30 secs or so I just have to reboot in system recovery mode. Is there a solution in place to fix this problem without sending the device back. It seems to me there is some bug in the software, however since this happened my nexx has been flawless without one single glitch. Any ideas ...
Sent from my Nexus 10 using xda app-developers app
rdsreference said:
I never thought I would be the person ignoring a system update but after 3 unsuccessful attempts at installing the latest iteration of Android its not looking good. There is an error message showing up after about 30 secs or so I just have to reboot in system recovery mode. Is there a solution in place to fix this problem without sending the device back. It seems to me there is some bug in the software, however since this happened my nexx has been flawless without one single glitch. Any ideas ...
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
You could probably get it to install by installing it via image (downloaded from Google) and adb (run from the Android SDK), as opposed to using the over-the-air update from Google.
The method of doing it that way that I am familiar with will erase everything. But I think you can still do it that way and not erase everything... if you are interested and want to attempt either just say so.
Are you temp unrooting it?
Sent from my SCH-I510 using xda app-developers app
Most likely there is something on your tablet that is not stock so the update is failing. Could be that your bootloader is unlocked, maybe you are rooted, maybe you have a custom recovery, or remnants of a custom kernel on the device. Do you have to do the update? Why not simply install a new version of a custom ROM that is running Android 4.2.2?
Maybe I am missing something, as I see a lot of people doing an official update and then going on to custom things again. I just think it is way too much of a hassle and doesnt gain anything. I have never once done an official update once I was running a custom ROM, I simply install the new ROM version that runs the latest Android. Simple as that and never had a problem.
i received the ota today...when i tried to update. it fail...then it show me the android screen with messege 'no command'...what should i do now?
Sent from my HTC6435LVW using XDA Premium 4 mobile app
minjiet said:
i received the ota today...when i tried to update. it fail...then it show me the android screen with messege 'no command'...what should i do now?
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you are rooted and have StickMount installed or had it installed you might need to replace the \system\bin\debuggerd file before doing the upgrade again.
See also http://forum.xda-developers.com/showthread.php?t=2419468
Search for how to sideload the security update using adb
jalize said:
If you are rooted and have StickMount installed or had it installed you might need to replace the \system\bin\debuggerd file before doing the upgrade again.
See also http://forum.xda-developers.com/showthread.php?t=2419468
Search for how to sideload the security update using adb
Click to expand...
Click to collapse
Ya, i'm rooted, now the n10 cant boot at all....what can i do?
anyone can show me step by step guide?
Or flash the Factory image with a bit editing. This should do: http://forum.xda-developers.com/showthread.php?t=2377307
Sent from my Galaxy Nexus using XDA Premium HD app
I got that as well on my N10. Stock, stock recovery rooted. Booting into recovery didn't help. The next morning it was the same thing, but after a while it shut itself off and when I was ready to flash a stock img, had the USB cable plugged into the laptop, I look at the N10 and it's booting just fine, then starts applying the update.
Not helpful I know, but just wanted to let you know it fixed itself, I did nothing. Good luck.
Same problem on stock rooted. Impossible to boot and to switch off the device. I've wait the nexus shut down by himself and after the update have been automaticaly installed on the boot. I'm always rooted. Strange.
Use http://www.afterdawn.com/software/s...l_devices/nexus_root_toolkit.cfm#all_versions app is the best to fix and very easy
Sent from my Nexus 10 using XDA Premium 4 mobile app
---------- Post added at 06:01 PM ---------- Previous post was at 05:58 PM ----------
A fixed all my problems, i am on stock with the same problem on jelly bean 4.3, now rooted and again with a custom recovery.
Sent from my Nexus 10 using XDA Premium 4 mobile app
thanks for the help...my n10 back to normal automatically after i plug in charger...weird
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Okay, something pretty similar happened to me twice now. I'll share what I saw and did.
Unboxed brand new n10 and immediately went through the process to unlock and root it. I did *not* install a custom recovery.
After a couple of hours playing, it prompted me to install an update. I *think* it was actually on 4.2 before and this was the update to 4.3.
Applied the update and it rebooted and went to the "No Command" screen. As others stated, it felt very stuck.
I eventually gave up and figured it was soft-bricked so I use the Nexus Root Toolkit to download and install a factory fresh 4.3 (v). Lost all my customizations.
Fast forward to this morning. It prompted me for a new update to 4.3. I made a full backup using Nexus Root Toolkit and tried it, but again, it just got stuck on the "No Command" screen.
This time, I tried pressing all three buttons (power, vol down, vol up) quickly, but it did not bring up the stock recovery screen until I actually pressed them in order, (power, vol down [next to power], vol up [farthest from power]). At that point it brought up the recovery menu and I selected the option to wipe cache.
It took a while, but after wiping, I rebooted and it went straight into Android without a problem and it *looked* like it finished the upgrade. Oddly, it still reports it is 4.3 (v) rather than 4.3 , so i don't know if I ended up aborting the upgrade or if it was just trying to re-install (v) for some reason.
DEinspanjer said:
Okay, something pretty similar happened to me twice now. I'll share what I saw and did.
Unboxed brand new n10 and immediately went through the process to unlock and root it. I did *not* install a custom recovery.
After a couple of hours playing, it prompted me to install an update. I *think* it was actually on 4.2 before and this was the update to 4.3.
Applied the update and it rebooted and went to the "No Command" screen. As others stated, it felt very stuck.
I eventually gave up and figured it was soft-bricked so I use the Nexus Root Toolkit to download and install a factory fresh 4.3 (v). Lost all my customizations.
Fast forward to this morning. It prompted me for a new update to 4.3. I made a full backup using Nexus Root Toolkit and tried it, but again, it just got stuck on the "No Command" screen.
This time, I tried pressing all three buttons (power, vol down, vol up) quickly, but it did not bring up the stock recovery screen until I actually pressed them in order, (power, vol down [next to power], vol up [farthest from power]). At that point it brought up the recovery menu and I selected the option to wipe cache.
It took a while, but after wiping, I rebooted and it went straight into Android without a problem and it *looked* like it finished the upgrade. Oddly, it still reports it is 4.3 (v) rather than 4.3 , so i don't know if I ended up aborting the upgrade or if it was just trying to re-install (v) for some reason.
Click to expand...
Click to collapse
When you cleared cache you lost the update package I believe, so it didn't update, when I received my OTA I had TWRP installed and it went through nicely. Maybe you should try it and then installing Stock Recovery again.
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my GT-I9505
I have a Nexus 10. I just took and installed the OTA that arriced 08/27/2013. I am not rooted or unlocked. It is only a wifi (not a carrier specific).
I have been sick since i took the first Ota several weeks ago. I was constantly having to reboot because it would drop the connection. Firefox was useless. And above all, I was unable to get Grassland Live wallpaper and Wind Turbine 3D to work.
It all works now!
Sent from my Nexus 10 using xda app-developers app
I just read in another thread that the issue as described is caused by apply the OTA when rooted. Just unroot then apply the OTA update and reboot. Assuming you are using SuperSU., it has an unroot option in the settings panel.
Good luck.
Hey, I've done a full wipe as well as return to stock, then proceed to install jwr66y from scratch, after installing i proceeded installing twrp and superuser, everything seems to run fine with root and all. The only thing which has been bothering me is that some apps are displaying force close error immediatly after starting them. Examples are Adaway, Adfree and Yelp.
Anyone knows what's going on there?
Same thing with me, some apps just crash immediately. I'm glad I made a backup before I installed. I installed the ota through a zip to preserve root/custom recovery and also just installing it normally. Same thing happens with crashes.
Sent from my Nexus 4 using Tapatalk 4
CCDillon said:
Same thing with me, some apps just crash immediately. I'm glad I made a backup before I installed. I installed the ota through a zip to preserve root/custom recovery and also just installing it normally. Same thing happens with crashes.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Yeah i also installed though a Zip which was supposed to be vanilla with added busybox and root.
I had my nexus 7 running so i was backing up from there which fixed the problem. However i am really wondering why apps which were downloaded straight from google play messed around.
I hope they won't mess around later.
I was completely stock and the same thing happened to me. I had to erase recovery, data and boot loader through fastboot and then reinstall everything new from the factory image on Google's site.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Oh wow. I had to do that with the initial 4.3 release. Don't think I'll do it for such a minor update unless I have a lot of free time. Though, the software update notification is in the way most of the time.. In surprised this isn't affecting more devices.
Sent from my Nexus 4 using Tapatalk 4
So when I try to install the new 4.4 update it is stuck on the rebooting now screen, It has been there for 20 minutes. I am unlocked and rooted if that makes a difference. Also I tried to flash thunderkat and that also failed in twrp. I have no clue why. Just seeing if anyone might have an answer for my problem.
bootloop
kench33 said:
So when I try to install the new 4.4 update it is stuck on the rebooting now screen, It has been there for 20 minutes. I am unlocked and rooted if that makes a difference. Also I tried to flash thunderkat and that also failed in twrp. I have no clue why. Just seeing if anyone might have an answer for my problem.
Click to expand...
Click to collapse
I had exactly the same, you must exit out of bootloop, factory reset then continue. WUGS NRT for N10 tells you to do it and how and when. I've only had this issue on N10, not my N7 or N4.
Example video http://www.youtube.com/watch?v=T1Se7Hr9Cww
My nexus won't even reboot. It stays at that installing update screen, was that how yours was?
Sent from my Nexus 10 using Tapatalk
kench33 said:
My nexus won't even reboot. It stays at that installing update screen, was that how yours was?
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
Huh? Are you updating? Don't. Do fresh stock install. Then unroot with no custom recovery. Then install custom recovery.
Sent from my Nexus 10 using Tapatalk
In the mean time, you can return to normal by reflashing the cm nightly/stable ROM you were running when you tried to update to 4.4. I had the same issue, but managed to reflash the stable cm 10.2 zip and my nexus began to function again.
Sent from my Nexus 10 using XDA Premium HD app
---------- Post added at 02:39 PM ---------- Previous post was at 02:37 PM ----------
But also I would like to know how to go about reflashing stock and undoing root without permanently losing my game data. From what I understand, a nandroid backup would take care of all of that for me?
Sent from my Nexus 10 using XDA Premium HD app
Flash the latest Factory image via fastboot. There is a way tot modify the flash-all.bat so it wont wipe any data.
Sent from my Galaxy Nexus using XDA Premium HD app
nigelhealy said:
Huh? Are you updating? Don't. Do fresh stock install. Then unroot with no custom recovery. Then install custom recovery.
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
That will erase everything on it though, right?
kench33 said:
That will erase everything on it though, right?
Click to expand...
Click to collapse
Yes.
So? I backup myself and restore myself, using LAN file-server for small files and a USB drive for large files.
There is more time wasted in trying to keep data and settings than the time it takes to re-enter.