Database Users

help with update from 4.2 to 4.2.1 stock rooted

Hello. I searched the forums and came up empty.
I have a stock 4.2 ROM I rooted. When the system says its updating and rebooting. It kicks me into recovery screen and does not up date.
Do I have to unroot and re lock the boot loader?
I know I'm probably just missing something stupid.
Thanks for any help.

If you were on a custom rom before then your recovery is probably messed up and not the stock recovery. Otherwise I do not know what it is that can be doing it because every time I would flash back to stock 4.2 I would get prompted to update to 4.2.1 and as well to note I have an unlocked bootloader and from what I have read before being rooted shouldnt make a difference.
Perhaps you could grab the toolkit and flash the stock recovery that is in it to your N7 and see if that helps you out.

jonnyg1097 said:
If you were on a custom rom before then your recovery is probably messed up and not the stock recovery. Otherwise I do not know what it is that can be doing it because every time I would flash back to stock 4.2 I would get prompted to update to 4.2.1 and as well to note I have an unlocked bootloader and from what I have read before being rooted shouldnt make a difference.
Perhaps you could grab the toolkit and flash the stock recovery that is in it to your N7 and see if that helps you out.
Click to expand...
Click to collapse
Crap. I was hoping I didn't have to reflash. I dont have a custom ROM never have. I just unlocked this and rooted.
I'm going to try the toolkit when I get home revert from stock to stock, see if the update takes then.
Thanks for you help.
Edit. Looks like I have twrp recovery. This is my issue I assume. Is there a zip I can just flash to update

I have removed twrp back to stock recovery. Now when system reboots to install update, it stats the update then gives me a error. No error code just error. I really dont want to wipe my device as I have it setup for my liking.
I'm using wug's toolkit

I think (...and may be wrong...), but if you modified anything in /system (deleted any of the stock apps and/or updated them) it won't update either.

RMarkwald said:
I think (...and may be wrong...), but if you modified anything in /system (deleted any of the stock apps and/or updated them) it won't update either.
Click to expand...
Click to collapse
I owe u a beer. I did add browser.apk to my system dir. I removed it and now I'm fully updated.
Thank you so much.
root keeper and I'm back in business.

[Q] 4.4.2 Stock Recovery

Hey guys!
I saw last week that I had an OTA notification to update to 4.4.3 (currently running 4.4.2 KOT49H). I downloaded it and when I rebooted to install I figured out that I had TWRP 2.7 installed and that I couldn't install OTA updates with a custom recovery
So, I'm asking, is it possible to flash stock recovery back with odin and then install the OTA? And can someone please direct me to where I could get the stock recovery for 4.4.2?
All I've found in restoring the recovery is flashing a factory image (which would completely wipe my device), but hopefully that's not the only way
Thanks!

dragancla said:
Hey guys!
I saw last week that I had an OTA notification to update to 4.4.3 (currently running 4.4.2 KOT49H). I downloaded it and when I rebooted to install I figured out that I had TWRP 2.7 installed and that I couldn't install OTA updates with a custom recovery
So, I'm asking, is it possible to flash stock recovery back with odin and then install the OTA? And can someone please direct me to where I could get the stock recovery for 4.4.2?
All I've found in restoring the recovery is flashing a factory image (which would completely wipe my device), but hopefully that's not the only way
Thanks!
Click to expand...
Click to collapse
EDIT: Nevermind, found everything I needed with Unified Android Toolkit. If anyone needs the stock recovery, here it is: http://www.mediafire.com/download/1x5zbfo426lc0x5/recovery-stock-kot49h-razor.img
Now, another thing disturbs me: when I tried to update, it just showed me an icon with a broken down Droid and the text Error! beneath it. I'm not soft-bricked or anything, just that I couldn't update. Could it be because I flashed another kernel?

Razor is the 2013 model. You might want to mention that before people here download your link and ruin their grouper or tilapia....
Why wouldn't you just download the stock images straight from Google? You didn't need to downgrade anything and you don't use Odin with a nexus....
Sent from my Nexus 5

dragancla said:
EDIT: Nevermind, found everything I needed with Unified Android Toolkit. If anyone needs the stock recovery, here it is: http://www.mediafire.com/download/1x5zbfo426lc0x5/recovery-stock-kot49h-razor.img
Now, another thing disturbs me: when I tried to update, it just showed me an icon with a broken down Droid and the text Error! beneath it. I'm not soft-bricked or anything, just that I couldn't update. Could it be because I flashed another kernel?
Click to expand...
Click to collapse
Possibly...
Any modifications you may have made to your Nexus 7 (other then rooting and a Custom Recovery installed) will almost certainly cause an OTA to fail... as an OTA first runs a checksum verification test on all system files to ensure they are the original system files.
If they've been modified by the user, they cannot be 'patched', ie. updated... so the OTA aborts with no changes made.
Anyway... you really should be posting your question(s) here...
http://forum.xda-developers.com/nexus-7-2013
...as the Razor recovery you posted clearly identifies your device as a second generation Nexus 7(2013), and as @Pirateghost points out, posting that recovery in this forum could potentially mess up other peoples devices, if they were to flash it.
Rgrds,
Ged.

[Q] Downgrade from 4.4.2 to 4.3?

Is there a way to downgrade from 4.4.2 to 4.3?

You can downgrade via downloading the Stock 4.3 files from the SuperTool site by tom and flash that via fastboot. But be careful you can brick the tablet.

hacktrix2006 said:
You can downgrade via downloading the Stock 4.3 files from the SuperTool site by tom and flash that via fastboot. But be careful you can brick the tablet.
Click to expand...
Click to collapse
Any experience? I'm interested too to downgrade to 4.3.

If you have OTA'd past 4.3 its just a simple download the images from toms server for 4.3 and fastboot flash them.
You can get the stock 4.3 images from : http://rootjunkysdl.com/?device=Tegra Note 7&folder=Roms Stock 4.3.
These files here is infact CWM/TWRP flashable zips so its just a case of unlocking the bootloader and flashing either CWM or TWRP then placing the stock 4.3 rom zip onto a SDCard and flashing it.
But before you flash the zip make totally sure you wipe the following partitions
Boot
System
Cache
UserData
This will downgrade you back to 4.3

In TWRP i can only wipe system,cache,data but not boot.

Ok wipe what you can the flashing of boot.img should wipe it before hand. Goodluck

@subzero82 How did it go with the downgrade?

hacktrix2006 said:
If you have OTA'd past 4.3 its just a simple download the images from toms server for 4.3 and fastboot flash them.
You can get the stock 4.3 images from : http://rootjunkysdl.com/?device=Tegra Note 7&folder=Roms Stock 4.3.
These files here is infact CWM/TWRP flashable zips so its just a case of unlocking the bootloader and flashing either CWM or TWRP then placing the stock 4.3 rom zip onto a SDCard and flashing it.
But before you flash the zip make totally sure you wipe the following partitions
Boot
System
Cache
UserData
This will downgrade you back to 4.3
Click to expand...
Click to collapse
Does this mean you have to unlock your bootloader?

Im getting terrible battery life, I got it new and updated to 4.4,
with playing gangstar vegas and answering email i got on only about 4 hours on 30% brightness balanced mode
is this normal?

nielo360 said:
Im getting terrible battery life, I got it new and updated to 4.4,
with playing gangstar vegas and answering email i got on only about 4 hours on 30% brightness balanced mode
is this normal?
Click to expand...
Click to collapse
I don't know if it apply to our device but it mean (on the readings) that KitKat suffer of a serious bug : The OS doesn't let some apps to go to deep sleep and the Wakelock are terrible.
That point and some others (more personnal) make me think to revert to 4.3

there is nothing on nvidia's offical site, I dont know if they are still supporting the device to fix this issue. I will try reverting to 4.3 and see how it goes, The nvidia shield has the same issue in 4.4

hacktrix2006 said:
If you have OTA'd past 4.3 its just a simple download the images from toms server for 4.3 and fastboot flash them.
You can get the stock 4.3 images from : http://rootjunkysdl.com/?device=Tegra Note 7&folder=Roms Stock 4.3.
These files here is infact CWM/TWRP flashable zips so its just a case of unlocking the bootloader and flashing either CWM or TWRP then placing the stock 4.3 rom zip onto a SDCard and flashing it.
But before you flash the zip make totally sure you wipe the following partitions
Boot
System
Cache
UserData
This will downgrade you back to 4.3
Click to expand...
Click to collapse
Please can you describe the exact process to downgrade to 4.3. I'm affraid to brick my device.
And do you think after downgrade, the CWM backups are compatible? I mean : I want to be able to restore 4.3 or 4.4 as I wish in order to do testings?

@chp2 if your afraid of bricking your tablet then why are you after downgrading your tablet in the first place.
Look its format
System
Cache
UserData
Then flash the 4.3 Stock zip and boom your on 4.3. CWM backups will still work regardless of what OS your so long as your using the Custom Recovery.
But as i said if your frightened of bricking your tablet you shouldn't be doing this.

hacktrix2006 said:
@chp2 if your afraid of bricking your tablet then why are you after downgrading your tablet in the first place.
Look its format
System
Cache
UserData
Then flash the 4.3 Stock zip and boom your on 4.3. CWM backups will still work regardless of what OS your so long as your using the Custom Recovery.
But as i said if your frightened of bricking your tablet you shouldn't be doing this.
Click to expand...
Click to collapse
LOL, But thanks for your help.
For me the TN7 is new and since I'm not yet familiar with it I prefer to be carefull.
And I prefer to ask before doing bad things. Perhaps in some days I'll laugh of it

LOL, i understand what you mean. But for me it was first day i got it, I rooted it and was messing with APX off the bat. Yes my first one failed because of faulty hardware so i got it replaced and yet again i Rooted it and started messing with going back and forth between 4.3 and 4.4.2.
Everything will break at one point in its life time. Tablets and phones are there to be abused mate,
If you end up in a reboot loop so long as you have your 4.4.2 backup your can just restore that and your be working again. If you brick you have APX to fix it.

Hello.Succsesfull downgraded from 4.4 to 4.3 after hour of fighting,couple of restoring backups,using supertool 1.5(i dont know does it help,nothing was happening).I was using hacktrix2006 instruction.

@ZubZero82 So you ended up flashing via fastboot then ??

I think that supertool maybe change bootloader and flash zip through twrp.
Update
Flashed 4.4 zip through TWRP,cleared System Cache UserData ,restored bacup of 4.3(error if try to install stock 4.3 without restoring),flashed stock 4.3 zip.Thanks for help.

hacktrix2006 said:
LOL, i understand what you mean. But for me it was first day i got it, I rooted it and was messing with APX off the bat. Yes my first one failed because of faulty hardware so i got it replaced and yet again i Rooted it and started messing with going back and forth between 4.3 and 4.4.2.
Everything will break at one point in its life time. Tablets and phones are there to be abused mate,
If you end up in a reboot loop so long as you have your 4.4.2 backup your can just restore that and your be working again. If you brick you have APX to fix it.
Click to expand...
Click to collapse
Finally.
I managed to downgrade to 4.3 and to block OTA popups.
I got some thrils when I had to re-install CWM but everything went ok.
Until now, no problems to report.
Thanks again hacktrix2006 :good:

no problems. I hope you just chmoded the file TegraOTA.apk in the /system/app folder (I think it was there)
If not the best way to disable OTA's is using the following command as SU
chmod 000 /system/app/TegraOTA.apk then reboot the tablet.
This will then keep the file there but make it so that it can't be read wrote to or even execute. Then if you want to OTA again you just change it back to chmod 644 /system/app/TegraOTA.apk and reboot again.

Issue updating to Android 5.0

I get this error while trying to attempt to update to the latest android 5.0 in twrp...
while installing the new zip file it says:
package expects build fingerprint of google/mantaray/manta: 4.4.4/ktu84p/1227136: user/release-keys or google/mantaray/manta:5.0/LRX21P/1570855:user/release-keys; this device has google/mantaray/manta:4.3/JWR66V/737497:user/release-keys
but my nexus 10 is already on 4.4.4

Your build.prop isn't standard, get the original one, or just use the factory image to update.

Rusty! said:
Your build.prop isn't standard, get the original one, or just use the factory image to update.
Click to expand...
Click to collapse
what i need to install to correct his to the correct build.prop of 4.4.4?
ps. my last 4.4.4 was updated directly OTA..

Just download the 5.0 factory image, remove -w from the flash-all script and it will update you. Less dicking around that way.

inspiron41 said:
I get this error while trying to attempt to update to the latest android 5.0 in twrp...
while installing the new zip file it says:
package expects build fingerprint of google/mantaray/manta: 4.4.4/ktu84p/1227136: user/release-keys or google/mantaray/manta:5.0/LRX21P/1570855:user/release-keys; this device has google/mantaray/manta:4.3/JWR66V/737497:user/release-keys
but my nexus 10 is already on 4.4.4
Click to expand...
Click to collapse
Exactly the same here when flashing OTA via TWRP.
The build.prop file hasn't been modified as far as I know.
Where/how to get the file please?

CBers said:
Exactly the same here when flashing OTA via TWRP.
The build.prop file hasn't been modified as far as I know.
Where/how to get the file please?
Click to expand...
Click to collapse
I found the best way around this is to install the factory nexus 10 lollipop version. It's actually quite easy or even easier than the OTA method. Just make sure you delete the -w from the .bat file to keep all your data. It worked perfectly for me.
Sent from my Nexus 5 using XDA Free mobile app

inspiron41 said:
I found the best way around this is to install the factory nexus 10 lollipop version. It's actually quite easy or even easier than the OTA method. Just make sure you delete the -w from the .bat file to keep all your data. It worked perfectly for me.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks inspiron41 - I'll give it a go at the weekend.
Which file is the -w in please?

CBers said:
Thanks inspiron41 - I'll give it a go at the weekend.
Which file is the -w in please?
Click to expand...
Click to collapse
Go to this website:
http://www.androidpolice.com/2013/1...riants-of-nexus-7-2012-and-2013-and-nexus-10/
It has detail instruction and jump down to step 3 regarding to -w
Sent from my Nexus 5 using XDA Free mobile app

I was having the same issue as the OP. So after reading this thread, I've performed the following:
Downloaded Android 5.0 factory image from: https://developers.google.com/android/nexus/images
Followed the instructions at this site, AND MADE SURE TO REMOVE '-w' AS INSTRUCTED, TO PRESERVE DATA: http://www.androidpolice.com/2013/1...riants-of-nexus-7-2012-and-2013-and-nexus-10/
It was pretty easy. I've been waiting about 30 minutes looking at the boot graphic. Hope it turns out OK. But it is easier than playing with the OTA.

After being stuck in a bootloop, I had to factory reset and now all is well.
Sent from my HTC One using Tapatalk

Darnell_Chat_TN said:
After being stuck in a bootloop, I had to factory reset and now all is well.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
...i've been having the same issue since the 5.0.0 update.
I even had to perform a total wipe to get 5.0.0 onto my N10, and even after that I still have a bad signature on my tablet. Now the problem is back installing 5.0.2 OTA, and I do not want to wipe everything again. So please where is that build.prop file, and how do I fix it? or rather, what the eff has gone wrong here, why, and who's responsible for unbreaking it?

[Lemmy] said:
...i've been having the same issue since the 5.0.0 update.
I even had to perform a total wipe to get 5.0.0 onto my N10, and even after that I still have a bad signature on my tablet. Now the problem is back installing 5.0.2 OTA, and I do not want to wipe everything again. So please where is that build.prop file, and how do I fix it? or rather, what the eff has gone wrong here, why, and who's responsible for unbreaking it?
Click to expand...
Click to collapse
Yea, I flashed the 5.0.1 factory image later. Now, I tried to flash the 5.0.2 OTA and it said it saw a 5.0.1 signature and was expecting 5.0.1, or something of that sort. It's basically the same issue all over again... No issues flashing 5.0.2 to my kids' N7s that are 100% stock.
My N10 is unlocked and rooted. There must be something in the customizations that cause this issue.

Darnell_Chat_TN said:
Yea, I flashed the 5.0.1 factory image later. Now, I tried to flash the 5.0.2 OTA and it said it saw a 5.0.1 signature and was expecting 5.0.1, or something of that sort. It's basically the same issue all over again... No issues flashing 5.0.2 to my kids' N7s that are 100% stock.
My N10 is unlocked and rooted. There must be something in the customizations that cause this issue.
Click to expand...
Click to collapse
and again, trying to flash the 5.1 OTA and it says there is a 4.4.2 signature so it wont install... but I have re-flashed the stock image several times by now. I just do not get it.

[Lemmy] said:
and again, trying to flash the 5.1 OTA and it says there is a 4.4.2 signature so it wont install... but I have re-flashed the stock image several times by now. I just do not get it.
Click to expand...
Click to collapse
Why not just update using the 5.1 factory image? I run unlocked stock/rooted on my N10, and that's the method I always use to update. Would also do it this way on my N5 and now N6. Just fastboot flash all the images from the factory image manually (READ: EXCEPT USERDATA). You can also skip flashing the recovery if you run a custom recovery. However, for the sake of completion, I include flashing the stock recovery. Then I let it boot up normally. Then I'll boot back into the bootloader and flash TWRP and flash SuperSU. Updating this way is easier for me since I don't have to worry about the OTA failing due to customizations I may have made to the system (especially now with the new way Android updates after 5.0).

I've already had to upgrade my tablet by flashing stock for the last three upgrades, and every single time I ended up havnig to wipe the tablet clean and install and configure everything from scratch. I'm still hoping that at some point I wouldn't have to do that anymore...
---------- Post added at 08:57 AM ---------- Previous post was at 08:49 AM ----------
could this all be because my tablet is rooted and has CWM recovery installed?

[Lemmy] said:
I've already had to upgrade my tablet by flashing stock for the last three upgrades, and every single time I ended up havnig to wipe the tablet clean and install and configure everything from scratch. I'm still hoping that at some point I wouldn't have to do that anymore...
---------- Post added at 08:57 AM ---------- Previous post was at 08:49 AM ----------
could this all be because my tablet is rooted and has CWM recovery installed?
Click to expand...
Click to collapse
That's weird. I can't remember the last time I had issues using the stock images, and most people seem to be okay doing it. How are you flashing it? I follow Method 2 from this OP: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008. I just skip the command that flashes userdata, and it always works. I always flash the new cache image because when I would just erase it, it would be forever stuck in the bootanimation.
Before 5.0, being rooted didn't affect upgrading via OTA. Now, however, any little modification to the system (including being rooted) will cause the OTA to fail everytime. Also using a custom recovery like CWM will cause it to fail. So if you really want to go the OTA route, the least you would have to do is completely unroot (inside the SuperSU app itself) and flash the stock recovery. If you've uninstalled any system apps, you have to reinstall them or it will also fail.

charesa39 said:
That's weird. I can't remember the last time I had issues using the stock images, and most people seem to be okay doing it. How are you flashing it? I follow Method 2 from this OP: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008. I just skip the command that flashes userdata, and it always works. I always flash the new cache image because when I would just erase it, it would be forever stuck in the bootanimation.
Before 5.0, being rooted didn't affect upgrading via OTA. Now, however, any little modification to the system (including being rooted) will cause the OTA to fail everytime. Also using a custom recovery like CWM will cause it to fail. So if you really want to go the OTA route, the least you would have to do is completely unroot (inside the SuperSU app itself) and flash the stock recovery. If you've uninstalled any system apps, you have to reinstall them or it will also fail.
Click to expand...
Click to collapse
My N10 is with stock ROM 5.0.1 and stock recovery but rooted with unlocked bootloader (and custom launcher). I have two questions:
1) I can unroot it through SuperSU. Do I have to switch back to the stock launcher before trying the OTA installation of 5.1?
2) I remember last time I could gain root by simply installing SuperSU. After flashing the 5.1 factory image, can I still get root this same way, or do I have to install, for example, TWRP and then flash SuperSU?
Thanks!

mj56gt said:
My N10 is with stock ROM 5.0.1 and stock recovery but rooted with unlocked bootloader (and custom launcher). I have two questions:
1) I can unroot it through SuperSU. Do I have to switch back to the stock launcher before trying the OTA installation of 5.1?
2) I remember last time I could gain root by simply installing SuperSU. After flashing the 5.1 factory image, can I still get root this same way, or do I have to install, for example, TWRP and then flash SuperSU?
Thanks!
Click to expand...
Click to collapse
1) No, you can keep whichever launcher you are using whether it be Trebuchet, Google Now Launcher, Nova, etc. since it's more of just an app and not a system mod.
2) As far as I know (or thought), you've always had to flash SuperSU using a custom recovery unless your ROM already came pre-rooted. In which case, all you would have to do is install SuperSU from the Play Store. But to answer your question, after flashing the factory image, you would have to flash a custom recovery like TWRP and then flash SuperSU using said custom recovery. However, that's not complicated at all. After flashing the factory image, it just takes like another 5 minutes to flash TWRP, boot into it, flash SuperSU, boot into the OS, verify root status, then power off, boot back into the bootloader and flash the stock recovery (if you don't want to keep the custom recovery). While you're at it, after flashing SuperSU, why not flash the Translucent Nav/Status Bar Mod found here: http://forum.xda-developers.com/showthread.php?t=2771708 provided by @hanspampel. He's done a great service for us. It's the easiest and best mod for the stock N10 right now that restores the translucent decor that Google decided to disable on our device. I flashed it on my N10 after upgrading to 5.1 and it works flawlessly. But that's just a suggestion.

charesa39 said:
1) No, you can keep whichever launcher you are using whether it be Trebuchet, Google Now Launcher, Nova, etc. since it's more of just an app and not a system mod.
2) As far as I know (or thought), you've always had to flash SuperSU using a custom recovery unless your ROM already came pre-rooted. In which case, all you would have to do is install SuperSU from the Play Store. But to answer your question, after flashing the factory image, you would have to flash a custom recovery like TWRP and then flash SuperSU using said custom recovery. However, that's not complicated at all. After flashing the factory image, it just takes like another 5 minutes to flash TWRP, boot into it, flash SuperSU, boot into the OS, verify root status, then power off, boot back into the bootloader and flash the stock recovery (if you don't want to keep the custom recovery). While you're at it, after flashing SuperSU, why not flash the Translucent Nav/Status Bar Mod found here: http://forum.xda-developers.com/showthread.php?t=2771708 provided by @hanspampel. He's done a great service for us. It's the easiest and best mod for the stock N10 right now that restores the translucent decor that Google decided to disable on our device. I flashed it on my N10 after upgrading to 5.1 and it works flawlessly. But that's just a suggestion.
Click to expand...
Click to collapse
Thanks a lot for the suggestions! Have a wonderful weekend...

Never mind

Installing 5.0.2 on rooted tablet

So I recieved the notification that the 5.0.2 update was ready to install on my tablet. My tablet is ROOTED but that is all, still stock, I only root to use ad away. I get an error trying to install it OTA. How can I install the update, without having to wipe all my data? Sorry, I am very new to this stuff

viper2ko said:
So I recieved the notification that the 5.0.2 update was ready to install on my tablet. My tablet is ROOTED but that is all, still stock, I only root to use ad away. I get an error trying to install it OTA. How can I install the update, without having to wipe all my data? Sorry, I am very new to this stuff
Click to expand...
Click to collapse
No go on root. Your system partition has to be pristine. (Technically you can add files, but the ones that came with it have to be unchanged) Just undo any changes you have made and unroot and the OTA should work.

So if I get this right, OTA breaks also when recovery is stock, but supersu installed, modified hosts and gps.conf file

jshamlet said:
No go on root. Your system partition has to be pristine. (Technically you can add files, but the ones that came with it have to be unchanged) Just undo any changes you have made and unroot and the OTA should work.
Click to expand...
Click to collapse
Only changed I have made are installing ad away

viper2ko said:
Only changed I have made are installing ad away
Click to expand...
Click to collapse
The HOSTS file came with the stock image. It counts, unfortunately. (I'm also an Adaway user)

Modify /system, you don't OTA. Period.
Just download the Nexus image and flash just system.img, not the batch file.

Can I flash the system.img in TWRP or do I need to flash the stock recovery?
And will this upgrade me from 5.0.1 to 5.0.2 without losing anything except for root?
Thanks!

^You flash the system image with fastboot. Run: fastboot flash system system.img
You'll keep data just have to reflash the su zip in twrp.

yosmokinman said:
^You flash the system image with fastboot. Run: fastboot flash system system.img
You'll keep data just have to reflash the su zip in twrp.
Click to expand...
Click to collapse
Thanks for the info. Just had this problem myself and was trying to figure out what to do. This must be a 5.x problem? I've never had this problem on 4.x as long as I had the stock recovery installed. Just had to re-root after. Guess I'm off to download the factory images since it won't even show an update available after erroring out. It definitely still shows 5.01 as being the version I'm on.

flyinion said:
Thanks for the info. Just had this problem myself and was trying to figure out what to do. This must be a 5.x problem? I've never had this problem on 4.x as long as I had the stock recovery installed. Just had to re-root after. Guess I'm off to download the factory images since it won't even show an update available after erroring out. It definitely still shows 5.01 as being the version I'm on.
Click to expand...
Click to collapse
Just download Scrosler's Factory Stock Rooted Rom 5.0.2 in the Android Development section and install via TWRP over the top of 5.0.1. No need for a fresh install.

magnumlove said:
Just download Scrosler's Factory Stock Rooted Rom 5.0.2 in the Android Development section and install via TWRP over the top of 5.0.1. No need for a fresh install.
Click to expand...
Click to collapse
Oh I wasn't going to do a fresh install (i.e. wiping everything), just flash that system.img or modify the batch file to remove the "-w" flag and just run that. I'm wary of running 3rd party ROMs now after I couldn't play movies through Play Movies that were downloaded to the device instead of streamed. Something to do with copy protection I guess

It isn't a "3rd party ROM," just a flashable version of 5.0.2. If you flash using TWRP, just don't have it wipe anything. I flashed his 5.0.1 flashable ROM over 4.4.4 (after updating my bootloader) and didn't lose anything.

Telyx said:
It isn't a "3rd party ROM," just a flashable version of 5.0.2. If you flash using TWRP, just don't have it wipe anything. I flashed his 5.0.1 flashable ROM over 4.4.4 (after updating my bootloader) and didn't lose anything.
Click to expand...
Click to collapse
Assuming this was in reply to me? I'm not worried about losing anything. I've done the whole back it up and wipe between ROMs a ton on my OG Droid and Galaxy Nexus. In this case it's a worry that Play Movies for instance will detect that it is not a stock ROM/image and will disallow playing downloaded versions of movies in the app. I.e. you can download vs. stream for offline playback. I nearly found out the hard way (night before leaving on a vacation) that I couldn't play downloaded versions (it will download but not play them) when I for instance installed AOKP to my Nexus 7. As best I could tell from a bunch of Googling, it's something to do with copy protection.

It was, but I didn't know your experience level. I guess what I wanted to say is that scrosler's stock rooted ROM is exactly that; once it's on the tablet it isn't any different from rooting the OTA or factory image. It's just flashable via recovery instead of having to use fastboot or flash-all.bat.

Telyx said:
It was, but I didn't know your experience level. I guess what I wanted to say is that scrosler's stock rooted ROM is exactly that; once it's on the tablet it isn't any different from rooting the OTA or factory image. It's just flashable via recovery instead of having to use fastboot or flash-all.bat.
Click to expand...
Click to collapse
Ah ok. Well, I ended up using fastboot to flash the system.img last night and looks like I'm good to go. I tried unrooting (SuperSU remove root function) and changing betterbatterystats to a non-system app first but the OTA still failed. Yeah I learned how to use the basic adb/fastboot stuff when I got my Galaxy Nexus and again with the N7. I figured that way if I totally broke something I'd know how to fix it, and all the fancy tools weren't around when the GNex first came out (at least I don't think they were).

I dirty flashed scrosler's 5.0.1 ROM when I got the 5.0.1 OTA notification, but when the 5.0.2 factory image was posted I fastboot flashed the system.img from that and rerooted. Naturally, less than half a day or so later, scrosler posted his 5.0.2.

So for someone that's not really too experience with fastboot, could someone post a step by step?
Where would I get the system.img?

Check the sticky threads for guides. Read and reread then get started on setting up the Android SDK. Once complete, type in the commands letter for letter.