Database Users

[Q] 3.2.1 rooted stock rom?

I currently have stock 3.2 rooted (US 7.006.01_COM_GEN2). I got an ota notification for 7.014.01. Is there a rooted version of the ota I can flash via cwm?
From searching around, it's also looking like another ota ( 7.014.02?) Is right behind the 7.014.01. Is that true, and if so, is that available in rooted cwm-flashable form?

Neither available yet. (I'm waiting too. They were just released, so give them some time)

I wouldn't be so quick to update something, without first knowing what it is
Old saying "if it ain't broke, don't fix it"
A little more info on the update;
http://www.androidcentral.com/syste...ia-brings-market-update-and-improved-ui-speed

Yes, the 01 and 02 will break root. But, never fear, I rooted it for you. Here's the link
http://forum.xda-developers.com/showthread.php?t=1307539&page=12

Very cool
Although I don't need it, it's nice to know some people are still doing some neat things for stock 3.2.

update without wiping?
Thanks for the info. But, unless I'm reading your instructions wrong, it sounds like I have to wipe to update to your rooted 3.2.1. Is there just a rooted update.zip that can be flashed with cwm without wiping?
Or am I missing something?

There are some roms currently in the works for 3.2.1. I'd expect them to come out fairly soon, keep an eye on the development forum. A few guys working on them right now.

mpkrcl said:
Thanks for the info. But, unless I'm reading your instructions wrong, it sounds like I have to wipe to update to your rooted 3.2.1. Is there just a rooted update.zip that can be flashed with cwm without wiping?
Or am I missing something?
Click to expand...
Click to collapse
Ok, if I hear you correctly, you are already rooted and want to use CWM to run the updates and keep root? Therefore you don't wipe out everything?
Piece of cake, just grab the update.zip and change it not to wipe your permissions. Then rebuilt it.
If you don't know how to do that, then put a backdoor into your device therefore you can get back into the device as root. Updates (normally) are not evil un-rooting tools. They don't seek and destroy root and rooting tools. Updates just reset the permissions on all files in /system removing the 'sticky' bit. The 'sticky' bit is how you get root.
What is a 'sticky' bit you ask? Well, in Linux (Unix) you can set a permission on a file so that any time it is run, it runs as the user that owns the file. This would be like setting a shortcut in Windows to say always run as 'Administrator'.
So, when you apply an update, the last thing it does is resets all the permissions back to their default. Since they recursively do this on the /system directory they remove the sticky bit on your su program.
So, all you have to do is set up a root backdoor outside the /system folder. My favorite is to set the ro.kernel.qemu = 1. This makes adb run as root. Now after your OTA resets permissions, you can just adb shell and you get #(root). Now you just reset your 'sticky' bits.
TD

Is it possible to root 4.3 locked bootloader without wiping all data

I know it was possible previously to root without unlocking the bootloader.
Is it still possible? something people are working on? or not possible and backup everything first.
Thanks in advance
Mark

mark1holland1 said:
I know it was possible previously to root without unlocking the bootloader.
Is it still possible? something people are working on? or not possible and backup everything first.
Thanks in advance
Mark
Click to expand...
Click to collapse
I didn't know that was ever possible on the Nexus 7. I bought one of the first available, and from the moment I got it I had to unlock the BL to root. Thought it was always like that. Nothing's changed as far as I can tell. On other devices, sure you can root with a locked BL, but for the N7, you've always had to unlock first, and with it being so easy, I don't think anyone's motivated enough to cook up a workaround.

absinthesummer said:
I didn't know that was ever possible on the Nexus 7. I bought one of the first available, and from the moment I got it I had to unlock the BL to root. Thought it was always like that. Nothing's changed as far as I can tell. On other devices, sure you can root with a locked BL, but for the N7, you've always had to unlock first, and with it being so easy, I don't think anyone's motivated enough to cook up a workaround.
Click to expand...
Click to collapse
Hi, absinthesummer...
Yes, there was (and still is, if you're still on JB 4.2.2) a method available of rooting without unlocking the bootloader. And it was ridiculously easy to do. Avoiding unlocking the bootloader also avoids the factory reset, and consequential wipe.
Sadly however, under Jellybean 4.3, this exploit no longer works, and it seems unlikely a similar root-without-unlocking-the-bootloader type exploit, will become available anytime soon. Which, from a security point of view, is actually (probably) a good thing.
mark1holland1 said:
I know it was possible previously to root without unlocking the bootloader.
Is it still possible? something people are working on? or not possible and backup everything first.
Thanks in advance
Mark
Click to expand...
Click to collapse
Hi, mark1holland1...
As, I've mentioned, the old 'motochopper exploit' no longer works under JB4.3, so if you want root, you're going to have to do it the old fashioned way...
------------------------------------------
Backup the stuff on your Nexus 7...
Unlock the bootloader...
Fastboot flash a Custom Recovery (CWM or TWRP)...
Using that Recovery, flash Chainfires SuperSU root updater zip...
Copy all your stuff back to the Nexus 7...
Not difficult to do... just tedious and time consuming.
------------------------------------------
...it's either the above, or wait around indefinitely for a genius developer to find another exploit, which, given the security enhancements of JB4.3 does seem hugely unlikely.
Rgrds,
Ged.

GedBlake said:
Hi, absinthesummer...
Yes, there was (and still is, if you're still on JB 4.2.2) a method available of rooting without unlocking the bootloader. And it was ridiculously easy to do. Avoiding unlocking the bootloader also avoids the factory reset, and consequential wipe.
Sadly however, under Jellybean 4.3, this exploit no longer works, and it seems unlikely a similar root-without-unlocking-the-bootloader type exploit, will become available anytime soon. Which, from a security point of view, is actually (probably) a good thing.
Hi, mark1holland1...
As, I've mentioned, the old 'motochopper exploit' no longer works under JB4.3, so if you want root, you're going to have to do it the old fashioned way...
------------------------------------------
Backup the stuff on your Nexus 7...
Unlock the bootloader...
Fastboot flash a Custom Recovery (CWM or TWRP)...
Using that Recovery, flash Chainfires SuperSU root updater zip...
Copy all your stuff back to the Nexus 7...
Not difficult to do... just tedious and time consuming.
------------------------------------------
...it's either the above, or wait around indefinitely for a genius developer to find another exploit, which, given the security enhancements of JB4.3 does seem hugely unlikely.
Rgrds,
Ged.
Click to expand...
Click to collapse
Many thanks for a recent concise and informative post!
I was mainly being lazy with regards to not wanting to wipe everything and start again! I have helium installed to back everything up, guess Ill try to get a clear day to do it all........

GedBlake said:
Hi, absinthesummer...
Yes, there was (and still is, if you're still on JB 4.2.2) a method available of rooting without unlocking the bootloader. And it was ridiculously easy to do. Avoiding unlocking the bootloader also avoids the factory reset, and consequential wipe.
Sadly however, under Jellybean 4.3, this exploit no longer works, and it seems unlikely a similar root-without-unlocking-the-bootloader type exploit, will become available anytime soon. Which, from a security point of view, is actually (probably) a good thing.
Hi, mark1holland1...
As, I've mentioned, the old 'motochopper exploit' no longer works under JB4.3, so if you want root, you're going to have to do it the old fashioned way...
------------------------------------------
Backup the stuff on your Nexus 7...
Unlock the bootloader...
Fastboot flash a Custom Recovery (CWM or TWRP)...
Using that Recovery, flash Chainfires SuperSU root updater zip...
Copy all your stuff back to the Nexus 7...
Not difficult to do... just tedious and time consuming.
------------------------------------------
...it's either the above, or wait around indefinitely for a genius developer to find another exploit, which, given the security enhancements of JB4.3 does seem hugely unlikely.
Rgrds,
Ged.
Click to expand...
Click to collapse
Hmm, wow thanks for the info. I never knew that! I just remember my first N7 every post said Step 1:Unlock your bootloader... lol had I known there was a way around it I might have tried it! But my first 16gb and my later 32gb were both unlocked and rooted within hours of buying them, so perhaps I just wasn't motivated enough to look for it.
I could see how or why that would be desirable though I guess... before I bought my S3, I had an LG L9 that the only way you could unlock the BL was to root then flash/update (LG Update tool hack) the firmware meant for the international version of the phone, which mirrored(!!!) the entire display both horizontally and vertically. Then fastboot the oem unlock and unlock the best way you could with that kind of touch screen lol, THEN re-flash standard rooted firmware for the US back over it... Seriously NOT worth it! Because even if the mirroring went away with the right firmware, the boot logo would still be mirrored and it was possible your screen would not return to normal. So forget about any warranty at that point. But, I gotta hand it to the devs on that device- now they were some motivated folks. They went to a lot of trouble to unlock that BL. You could root and install CWM without unlocking, but if you flashed CM and it was buggy or something, there was no turning back to stock. We were left with mods only unless we wanted to do alll that work.
That just reminds me how thankful I am for my S3 and N7s.

Verizon 4.4.2 OTA discussion for LOCKED bootloaders

The other thread was just too messy with too much cross information.
So, here's the quick and dirty. If you're on 4.4. and rooted you can upgrade to 4.4.2 after disabling Gravity Box and ANY mods (wifi tether, etc) and you will keep root but you will lose the ability to write to the system. This effectively makes root useless.
It's unlikely 4.4.2 will ever be rooted, but there is some sliver of hope that a solution will be found (likely involving SBF) that allows you to retain root and /system RW but it can't be taken for granted.
There's lots of other info, but this thread is just designed to separate out the discussions.

Just to add..
Inside the OTA is a manifest file which which contains check sums for files which need to exist on your phone. If the expected files are not on your phone, or the checksums of the files don't match the manifest, the OTA will fail. Hence why you need to undo some of the "hacks" and "mods"
Addtioinally to install the OTA, you need to have stock recovery on your phone. If its not on there, the OTA will either fail, or worse, put you in a boot loop! (erasing your phone's cache can help you out of the loop... mfastboot erase cache )
Once you are on 4.4.2, you can not downgrade your rom to 4.4 or older!! Trying to downgrade can/will result in bricking your device.

Can anyone comment on the "This will be permanent" warning from when rooting with SlapMyMoto/MotoWPNoMo?
I'm trying to get all my ducks in a row before I update to 4.4.2 and lose a functional root.
I'm thinking of reflashing /sys or restoring tether hack, and accepting OTA.

evandena said:
Can anyone comment on the "This will be permanent" warning from when rooting with SlapMyMoto/MotoWPNoMo?
I'm trying to get all my ducks in a row before I update to 4.4.2 and lose a functional root.
I'm thinking of reflashing /sys or restoring tether hack, and accepting OTA.
Click to expand...
Click to collapse
When MotoWPNoMo came its disabling write protection was "permanent" (it survived flashing between the roms which were out at that time) however it does NOT survive the 4.4.2 OTA.
The statement in the initial post... "keep root but you will lose the ability to write to the system. This effectively makes root useless. " is 100% accurate for those with locked bootloaders.

I got the notification this morning when I woke up that the OTA was downloaded and ready to install. It was a persistent notification, and I didn't want it there. I long pressed on it and went to app info, which was MotoOTA. I force stopped it, which did remove the notification, but it came back immediately.
I then unchecked the "show notifications" box and it was gone. I'm not really a fan of freezing apps with TiBu or anything like that, so this worked for me. I don't really care to update unless I can keep root and have write protection off.
I didn't see anything in the changelog that really implied that I'm missing much by not upgrading, for now at least. I decided to get the Moto Maker edition because I valued the customization more than then unlocked bootloader. The phone works great and does everything I need it to right now, so I have no desire to upgrade and lose root yet.
One question though, I read somewhere before that booting through recovery disables write protection, and allows you to install Xposed and other root stuff. I assume that write protect being off only lasts until the next reboot? And then you'd need to boot through recovery again, and possibly apply things through Xposed each time? Or is it just for initial setup?

fury683 said:
One question though, I read somewhere before that booting through recovery disables write protection, and allows you to install Xposed and other root stuff. I assume that write protect being off only lasts until the next reboot? And then you'd need to boot through recovery again, and possibly apply things through Xposed each time? Or is it just for initial setup?
Click to expand...
Click to collapse
You don't have to boot into recovery each time. You do need to soft reboot each time after a hard reboot though for it to stick

evandena said:
Can anyone comment on the "This will be permanent" warning from when rooting with SlapMyMoto/MotoWPNoMo?
I'm trying to get all my ducks in a row before I update to 4.4.2 and lose a functional root.
I'm thinking of reflashing /sys or restoring tether hack, and accepting OTA.
Click to expand...
Click to collapse
Well that didn't work. I'm stuck in a boot loop now. Guess I'll try flashing /sys when I get home.

fury683 said:
...One question though, I read somewhere before that booting through recovery disables write protection, and allows you to install Xposed and other root stuff. I assume that write protect being off only lasts until the next reboot? And then you'd need to boot through recovery again, and possibly apply things through Xposed each time? Or is it just for initial setup?
Click to expand...
Click to collapse
The early root processes (RockMyMoto and SlapMyMoto) replaced stock recovery with a trick that booted the phone with write protect disabled. To take the OTA, you need to put stock recovery back, thus removing this trick.
Later, MotoWPNoMo replaced the trick of booting to a tricked recovery, and allowed Write Protection to be disabled for normal boot too, and allowed stock recovery to be put back on, but this doesn't survive the OTA.
---------- Post added at 05:35 PM ---------- Previous post was at 05:34 PM ----------
evandena said:
Well that didn't work. I'm stuck in a boot loop now. Guess I'll try flashing /sys when I get home.
Click to expand...
Click to collapse
No. Put your phone in bootloader mode... then...
mfastboot erase cache

KidJoe said:
No. Put your phone in bootloader mode... then...
mfastboot erase cache
Click to expand...
Click to collapse
Can that be done from the phone with fastboot, or do I need my computer? I haven't messed with this stuff since November, so I'm a little rusty.

evandena said:
Can that be done from the phone with fastboot, or do I need my computer? I haven't messed with this stuff since November, so I'm a little rusty.
Click to expand...
Click to collapse
Have to enter that command from the PC

Wifi Tether require Write Protection?
I wasn't able to find an answer on this so I'm asking here. The only thing I really use root for on my Moto X is the wifi tether because I still have unlimited data. I am wondering if I can keep root through the OTA and keep using the Wifi Tether app after it reenables write protection. Thanks in advance.

Reserved Name said:
I wasn't able to find an answer on this so I'm asking here. The only thing I really use root for on my Moto X is the wifi tether because I still have unlimited data. I am wondering if I can keep root through the OTA and keep using the Wifi Tether app after it reenables write protection. Thanks in advance.
Click to expand...
Click to collapse
You'll probably have to keep the file on your phone to replace each time you do a hard reboot. Without R/W, your changes won't stick after a boot. Otherwise, I think you can still use the entitlement trick without an issue other than it not sticking.

Reserved Name said:
I wasn't able to find an answer on this so I'm asking here. The only thing I really use root for on my Moto X is the wifi tether because I still have unlimited data. I am wondering if I can keep root through the OTA and keep using the Wifi Tether app after it reenables write protection. Thanks in advance.
Click to expand...
Click to collapse
I'd like to know this too. At this point the only thing I really use root for is Greenify, which no longer requires root, tethering with my unlimited data (VZ), and bypassing the exchange pin requirement.

KidJoe said:
Have to enter that command from the PC
Click to expand...
Click to collapse
I'm having problems getting into recovery. Once I select Recovery from the fastboot menu, it boots straight into normal mode.
*edit* maybe I don't need adb to recognize the phone for fastboot erase cache to work. Playing with it now...
*edit 2* ok, it looks like that stopped my boot loops. Now to figure out why the update didn't work the first time...

CartlandSmith said:
you select recovery by hitting vol up button.
Click to expand...
Click to collapse
Yep, was. It was booting to safe mode when Recovery was selected.

I should clarify, I don't use the entitlement hack I just use the Wifi Tether apk. Just wondering if it requires write protection to be disabled or not. Thanks.

If I take the OTA and have root but no system RW, is it still possible to install Xposed, soft reboot, and it works normally until a hard reboot happens? Or is Xposed completely broken?

Reserved Name said:
I wasn't able to find an answer on this so I'm asking here. The only thing I really use root for on my Moto X is the wifi tether because I still have unlimited data. I am wondering if I can keep root through the OTA and keep using the Wifi Tether app after it reenables write protection. Thanks in advance.
Click to expand...
Click to collapse
You're talking "wifi tether for root" like this -> https://code.google.com/p/android-wifi-tether/
I don't think it will work due to the changes it makes when you start and stop tethering. (It appears to update files in the normally write protected area). Then again, if temp changes can be made after 4.4.2 is installed, it might work.
I think you and I are the only ones who use that app.. most everyone else is using Xposed or the hacked entitlement apk.

evandena said:
I'm having problems getting into recovery. Once I select Recovery from the fastboot menu, it boots straight into normal mode.
*edit* maybe I don't need adb to recognize the phone for fastboot erase cache to work. Playing with it now...
*edit 2* ok, it looks like that stopped my boot loops. Now to figure out why the update didn't work the first time...
Click to expand...
Click to collapse
If it's booting normally when you select recovery, it's because your recovery is missing - probably because you used SlapMyMoto.
You need to restore your recovery... you can boot into fastboot, then write the correct recovery to your phone with fastboot flash recovery recovery.img, where recovery.img is a file pulled out of the SBF package for whatever version you're running.

You guys really should just wait! Even if a new root method isn't discovered, you will be able to flash a stock 4.4.2 ROM or Eclipse's stock-based ROM via Safestrap soon enough. Certainly not worth risking losing root! Patience!
Sent from my Moto X

Easy 2 click root: How I got to 4.2.2 Camera Update/Rooted and WP permanently Off

Are the root methods too complicated/risky for you? This is a simple solution.
Start with: original droid maxx software (12.7.7 i believe) on Verizon
1. Install motoroot 1.0 (JCase's first root method from original development section), run it, and click root (that's click #1). Make sure everything's working, reboot a few times, use rootchecker to make sure you've got root. (note you won't have write protection off and there'll be a 10-15 sec delay after booting up before you have root). But hey, it's 1 click.
2. Take 1st Verizon OTA to the 4.2.2 with camera update (12.15.15 i believe). Root should survive. Check that it did with root checker.
3. Install the write protection no more from the moto x original development section on your computer. download android-sdk and make sure adb is working, make sure fastboot is working. connect your phone to your computer and run the "write protectoin no more" app on your computer (that's click #2).
That's it. Now I have write protection permanently off, and I have root. I didn't have to use cydia impactor and mess with a tricky update to 4.4 which if it doesn't work I couldn't go back to a rooted phone. I never had to fxz anything or restore anything to stock, or lose any of my data. I didn't have to pay a dime or give someone on ebay all my phone info.
Sure I'd like to have 4.4, but pretty happy with where I am and how easily I got here. And I've read a lot of people say "the root methods are too complicated" --- well this is pretty easy cause you're just using 2 packaged apps.
I've gotten a lot from this forum, and just thought I'd share. Please don't flame. I feel like this is the best compromise of features:effort for me.

It was really easy to put an unlock code into adb.
Sent from my XT1080 using Tapatalk

Piaband said:
It was really easy to put an unlock code into adb.
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
if i could unlock it when i had gotten it in august, sure. but it's too much effort to start over at this point. i have everything set up perfectly. never had to start over. also didn't want to pay for it and send my info to some stranger on the internet. anyway, moot point. good for you, but that option's not available for most people.

So does this work when your already updated to 4.4?
Sent from my XT1080 using XDA Premium 4 mobile app

No nothing roots 4.4 at this point.

vegasdgk said:
So does this work when your already updated to 4.4?
Sent from my XT1080 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No he basically just rewrote the instructions of how to root the original firmware.

akellar said:
No he basically just rewrote the instructions of how to root the original firmware.
Click to expand...
Click to collapse
I didn't rewrite it. No where are there instructions for getting root AND write protection off on the 4.2.2 camera update without 1 using command line commands AND 2 that network based program (called Cydia compactor I think). There's none of those complications here. Most people don't even realize 1 click root survives the camera update.
But you are right as to kit kat. I thought my title was clear that this is for jellybean though.

mistermojorizin said:
Are the root methods too complicated/risky for you? This is a simple solution.
Start with: original droid maxx software (12.7.7 i believe) on Verizon
1. Install motoroot 1.0 (JCase's first root method from original development section), run it, and click root (that's click #1). Make sure everything's working, reboot a few times, use rootchecker to make sure you've got root. (note you won't have write protection off and there'll be a 10-15 sec delay after booting up before you have root). But hey, it's 1 click.
2. Take 1st Verizon OTA to the 4.2.2 with camera update (12.15.15 i believe). Root should survive. Check that it did with root checker.
3. Install the write protection no more from the moto x original development section on your computer. download android-sdk and make sure adb is working, make sure fastboot is working. connect your phone to your computer and run the "write protectoin no more" app on your computer (that's click #2).
That's it. Now I have write protection permanently off, and I have root. I didn't have to use cydia impactor and mess with a tricky update to 4.4 which if it doesn't work I couldn't go back to a rooted phone. I never had to fxz anything or restore anything to stock, or lose any of my data. I didn't have to pay a dime or give someone on ebay all my phone info.
Sure I'd like to have 4.4, but pretty happy with where I am and how easily I got here. And I've read a lot of people say "the root methods are too complicated" --- well this is pretty easy cause you're just using 2 packaged apps.
I've gotten a lot from this forum, and just thought I'd share. Please don't flame. I feel like this is the best compromise of features:effort for me.
Click to expand...
Click to collapse
Hello,
I have rooted my phone when i am in 12.7.7, then i took the OTA update 12.15.15, now my device is in a boot loop, it boots normally and after a few seconds it will reboot and it goes over and over again.
any thoughts on this and should I use RSDLite to flash it to either 12.7.7 / 12.15.15???

-Zeta- said:
Hello,
I have rooted my phone when i am in 12.7.7, then i took the OTA update 12.15.15, now my device is in a boot loop, it boots normally and after a few seconds it will reboot and it goes over and over again.
any thoughts on this and should I use RSDLite to flash it to either 12.7.7 / 12.15.15???
Click to expand...
Click to collapse
which method did you use to root it? what system stuff did you change after rooting it?
a lot of people had bootloops after taking an OTA because they did the root method that had replaced their stock recovery with a write protect off mode. so in effect, they were having bootloops because they didn't have the recovery, not because they had root. it their case, there was an easy solution of just flashing a recovery. unfortunately i don't know the details of how to do that off the top of my head.'
in any case, rsd'ing to either of those software versions will likely fix all problems.
i rooted as i described with motoroot 1.0, which didn't affect my recovery and was easy to OTA without problems.
good luck

mistermojorizin said:
which method did you use to root it? what system stuff did you change after rooting it?
a lot of people had bootloops after taking an OTA because they did the root method that had replaced their stock recovery with a write protect off mode. so in effect, they were having bootloops because they didn't have the recovery, not because they had root. it their case, there was an easy solution of just flashing a recovery. unfortunately i don't know the details of how to do that off the top of my head.'
in any case, rsd'ing to either of those software versions will likely fix all problems.
i rooted as i described with motoroot 1.0, which didn't affect my recovery and was easy to OTA without problems.
good luck
Click to expand...
Click to collapse
Thanks for the quick reply,
I used the PwnMyMoto here to root, i forgot that this method will replace / remove the stock recovery.
With a minute of panic and some google search, I'd managed to use RSD lite to flash the 12.15.15 FXZ and now my phone is back in business but kinda lost root.
Right now I am looking into the RockMyMoto method here and see if it can help me to gain root.

-Zeta- said:
Thanks for the quick reply,
I used the PwnMyMoto here to root, i forgot that this method will replace / remove the stock recovery.
With a minute of panic and some google search, I'd managed to use RSD lite to flash the 12.15.15 FXZ and now my phone is back in business but kinda lost root.
Right now I am looking into the RockMyMoto method here and see if it can help me to gain root.
Click to expand...
Click to collapse
glad you got your phone back in order, might want to check out slapmymoto (which is the path to rooted kit kat and involves running rockmymoto on the way) while you're at it

mistermojorizin said:
glad you got your phone back in order, might want to check out slapmymoto (which is the path to rooted kit kat and involves running rockmymoto on the way) while you're at it
Click to expand...
Click to collapse
Not sure about the battery life on kitkat of the MAXX right now, so i will stick with 4.2.2 first and do a little research.
Anyway, thanks for the reply and I've gained root on 4.2.2 (12.15.15) using RockMyMoto:laugh:

5.1 OTA failed

I was offered the 5.1 update on my 2013 Nexus 7. In an attempt to be on the safe side, I uninstalled busybox, titanium, and fully unrooted (I always had the stock recovery, so I didn't have to worry about that). Anyway, even after all those precautions, the attempt to install failed after a couple of minutes with an android keeled over and a red warning triangle. The highly informative message "Error!" was displayed under the keeled over android. Just wondering if other folks are seeing this same problem.
About 5 minutes later while I was poking around in this forum, the tablet rebooted itself and it appears to be running 5.0.2 with no obvious problems.
Any clues about what might be going on? Any way to extract more information than "Error!"?

Claghorn said:
I was offered the 5.1 update on my 2013 Nexus 7. In an attempt to be on the safe side, I uninstalled busybox, titanium, and fully unrooted (I always had the stock recovery, so I didn't have to worry about that). Anyway, even after all those precautions, the attempt to install failed after a couple of minutes with an android keeled over and a red warning triangle. The highly informative message "Error!" was displayed under the keeled over android. Just wondering if other folks are seeing this same problem.
About 5 minutes later while I was poking around in this forum, the tablet rebooted itself and it appears to be running 5.0.2 with no obvious problems.
Any clues about what might be going on? Any way to extract more information than "Error!"?
Click to expand...
Click to collapse
To take ota you must have a clean non rooted system. Not one you attempted to remove traces of root from. If you want ota you have to flash 5.0.2 system.img extracted from the factory image. Any trace of root or a missing file or apk will cause it to fail.

madbat99 said:
To take ota you must have a clean non rooted system. Not one you attempted to remove traces of root from. If you want ota you have to flash 5.0.2 system.img extracted from the factory image. Any trace of root or a missing file or apk will cause it to fail.
Click to expand...
Click to collapse
I'm not sure what would leave a trace. I've always been able to get OTA previously via the fully uninstall everything technique.

Claghorn said:
I'm not sure what would leave a trace. I've always been able to get OTA previously via the fully uninstall everything technique.
Click to expand...
Click to collapse
Since lollipop it is very sensitive to anything different or missing in system. Just flash the 5.1 factory image with the ~w removed from the flash-all.bat file so it doesn't wipe data. Or use wugs to flash stock 5.1 image with "no wipe" enabled. Or like I said in previous you can always flash a clean system image of 5.0.2 then take ota. Either way will update you without wiping data.

Just use fastboot and manually flash system.img and boot.img, then format cache. It works every single time, without wiping data and you can easly root it again with CF Auto Root. I don't get it why people bother with OTA all the time. Always issues with them. I just did this and went from 5.0.2 to 5.1 without losing any data, and tablet now really flies. It keeps a lot more apps in RAM, for better multitasking, and I don't experiance any lag what so ever. I strongly recommend everyone to update to 5.1, because it feels like you just got a new tablet. Good job Google !

neo5468 said:
... I don't get it why people bother with OTA all the time ...
Click to expand...
Click to collapse
I'm not really bothering with it - it just showed up and started bothering me .

1.Backup everything.
2.Flash 5.1 with nexus root toolkit.
3.Restore all the data.
4.Change your build in NRT to android 5.1
5.Root it and flash TWRP/CWM if you want.
6.?????
7.Profit! duh

neo5468 said:
Just use fastboot and manually flash system.img and boot.img, then format cache. It works every single time, without wiping data and you can easly root it again with CF Auto Root.
Click to expand...
Click to collapse
... or wait for a week until someone will release a rooted 5.1 update

sensboston said:
... or wait for a week until someone will release a rooted 5.1 update
Click to expand...
Click to collapse
Why would you wait a week, we already waited too long for offical 5.1 to come out for our tablet. It is 5minutes of work, works 100% and also fasboot is the safest way to flash. Also you download the image straight from developers.google.com so there is no bs. I much rather flash that. But to each his own.

There is already a recovery flashable "stock rooted 5.1" thanks to scrosler (cleanrom Dev).
5.1 rooted ROM

neo5468 said:
Why would you wait a week
Click to expand...
Click to collapse
Agree, week is too long. A few days - better words And "one click" solution is much better in case of possible mistakes during flashing separate partitions, rooting etc...

neo5468 said:
Just use fastboot and manually flash system.img and boot.img, then format cache. It works every single time, without wiping data and you can easly root it again with CF Auto Root. I don't get it why people bother with OTA all the time. Always issues with them. I just did this and went from 5.0.2 to 5.1 without losing any data, and tablet now really flies. It keeps a lot more apps in RAM, for better multitasking, and I don't experiance any lag what so ever. I strongly recommend everyone to update to 5.1, because it feels like you just got a new tablet. Good job Google !
Click to expand...
Click to collapse
I haven't done this in forever, is it just adb reboot bootloader, then the fastboot commands for flash system.img/boot.img. I have a custom recovery, does that matter?

beall49 said:
I haven't done this in forever, is it just adb reboot bootloader, then the fastboot commands for flash system.img/boot.img. I have a custom recovery, does that matter?
Click to expand...
Click to collapse
Custom recovery is fine. There is also a new boot loader to flash as well I think. You can also run the flash all batch file in the factory image and just remove the -w from it so it doesn't wipe data. But what you posted is also correct, but flash the boot loader too. If your rusty at it just use wugs toolkit, it will run the commands for you.

Solid, removing the -w was what I was forgetting. I knew there was something else.
Thanks!

Well this popped up for me yesterday and I, in a total blonde moment, clicked OK and it promptly crashed my tablet. Which is what is expected to happen being that it was running rooted and non stock recovery.
So yes it was bricked. But is it a Nexus. It was a soft brick and easily fixed with the Nexus Root Toolkit. Which is what I would have done to update it anyway. I don't normally take OTAs. Yes I sinned before the Gods of RomFlashing and paid for it with wasted time. LOL

nlinecomputers said:
Well this popped up for me yesterday and I, in a total blonde moment, clicked OK and it promptly crashed my tablet. Which is what is expected to happen being that it was running rooted and non stock recovery.
So yes it was bricked. But is it a Nexus. It was a soft brick and easily fixed with the Nexus Root Toolkit. Which is what I would have done to update it anyway. I don't normally take OTAs. Yes I sinned before the Gods of RomFlashing and paid for it with wasted time. LOL
Click to expand...
Click to collapse
That's a little odd, usually (since lollipop) it will just fail. Bummer it actually flashed and soft bricked.

madbat99 said:
That's a little odd, usually (since lollipop) it will just fail. Bummer it actually flashed and soft bricked.
Click to expand...
Click to collapse
No big deal really. I don't keep important data on it. It's mostly used for Kindle and games. Easy to fix.