Related
I just started using the Nexus 7 (WiFi) and I am on 4.2.1 and I am rooted. I rooted with the Wug's Toolkit. Anyway I want to update to 4.2.2 and I don't want to use any custom rom's, I just want to have an original update that I can flash without having to unroot. I have flashed my nexus with Clockwork Mod Recovery. Any places were I can get this rom and how I can install it?
Help Please!!
hettige677 said:
I just started using the Nexus 7 (WiFi) and I am on 4.2.1 and I am rooted. I rooted with the Wug's Toolkit. Anyway I want to update to 4.2.2 and I don't want to use any custom rom's, I just want to have an original update that I can flash without having to unroot. I have flashed my nexus with Clockwork Mod Recovery. Any places were I can get this rom and how I can install it?
Help Please!!
Click to expand...
Click to collapse
Hello there!
What about a little search? is a search bar in every part of the forum!!!
Anyway there you go:
http://forum.xda-developers.com/showthread.php?t=1745781
Just don't get used to it :good:
Read the forum rules!
So I downloaded the zip but it won't install properly it says error code 7??
Sent from my Nexus 7 using xda app-developers app
n/m
hettige677 said:
So I downloaded the zip but it won't install properly it says error code 7??
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
That's because you are using a custom recovery. You can either flash a stock recovery or edit some files in the zip so you can flash it in the custom recovery.
Leonhan said:
That's because you are using a custom recovery.
Click to expand...
Click to collapse
Possibly, but probably not. In most of the reports that have been coming in - when the users actually report the full error message rather than saying something ambiguous like "I got a Status 7 error" - the problems revolve around altered/removed files in /system, or having a custom kernel (boot or LNX partition) installed. That suggests that the recovery version is not causing assert() failures.
The other thing to rememder is that the program that is interpreting the edify updater-script is the "updater-binary" program which is shipped inside the OTA - so it is virtually identical independent of the choice of recovery (other than perhaps kernel behavior differences).
Leonhan said:
You can either flash a stock recovery or edit some files in the zip so you can flash it in the custom recovery.
Click to expand...
Click to collapse
Even though what you are saying here does only require being able to operate a plain-text editor and a zip tool, it's way above the heads of most folks who think that OTAs should work on non-stock ROMs. And I'm not sure how these folks would be better off with partially-patched ROMs. In any event, if this course is taken indeed a custom recovery would need to be used for this, as modifying the zip contents will break the OTA package signing, so the stock recovery couldn't be used.
The OP should just
- make a full nandroid backup of what they have now
- download the factory 4.2.2 images from Google
- extract the system.img file and boot.img images
( hint for windoze users: 7-zip understands .tgz files)
fastboot flash boot boot.img
fastboot flash system system.img
- reflash a basic SuperSU or Superuser root kit
Sort of crude, but it's a decent hack for the lazy or poorly informed. It won't "erase my data", but presumably it will break whatever it was that altered the stock system and/or boot partitions - the very things that are causing the OTA to fail on them with their rooted & modified ROMs.
If they don't like the result, they can simply restore their nandroid backup.
i just got OTA update notification for 4.4.3 on my rooted ,stock,custom recovery Nexus 4 running on 4.4.2.
i use SuperSU,Xposed etc.
i have few questions hoping that someone will help me,
1. what happens if i update OTA normally , i lost data?root ? or there is possibility of softbrick while updating.
2. what is the best way of updating rooted phone with stock.
thanks in advance!!:good:
mrYogii said:
i just got OTA update notification for 4.4.3 on my rooted ,stock,custom recovery Nexus 4 running on 4.4.2.
i use SuperSU,Xposed etc.
i have few questions hoping that someone will help me,
1. what happens if i update OTA normally , i lost data?root ? or there is possibility of softbrick while updating.
2. what is the best way of updating rooted phone with stock.
thanks in advance!!:good:
Click to expand...
Click to collapse
Download and Install the OTA, you will loose your ROOT AND RECOVERY but not the data. That is the easiest way.
plz elaborate the process, i am new to it.
and one more question : what if i do OTA normally(over wifi).
with custom recovery and xposed OTA will fail and maybe soft brick.
please read here: http://forum.xda-developers.com/nexus-4/general/info-nexus-4-ota-help-desk-t2145848
carlosmg2 said:
with custom recovery and xposed OTA will fail and maybe soft brick.
please read here: http://forum.xda-developers.com/nexus-4/general/info-nexus-4-ota-help-desk-t2145848
Click to expand...
Click to collapse
thats what i am fearing , plz guide me for updating my rooted stock .
anyone in the same situation? OTA hit on device but not sure to update due to rooted and custom recovery, with Xposed and other modifications, plz help
mrYogii said:
anyone in the same situation? OTA hit on device but not sure to update due to rooted and custom recovery, with Xposed and other modifications, plz help
Click to expand...
Click to collapse
You have two (best I think) solutions:
1) Get back to stock and download OTA... before you do that, download Titanium Backup, backup your apks with it's cache so you won't have to set them up or start games from beggining... to backup messages etc you can use My Backup Pro, for calendar and contacts synchronize your Google account
2) Try to "get back to stock" as near as you can and try OTA... if it fails, it's not difficult to recover from softbrick
parkourz said:
You have two (best I think) solutions:
1) Get back to stock and download OTA... before you do that, download Titanium Backup, backup your apks with it's cache so you won't have to set them up or start games from beggining... to backup messages etc you can use My Backup Pro, for calendar and contacts synchronize your Google account
2) Try to "get back to stock" as near as you can and try OTA... if it fails, it's not difficult to recover from softbrick
Click to expand...
Click to collapse
i think 1 option i will try, what will be the process of
parkourz said:
Get back to stock
Click to expand...
Click to collapse
, if i am running stock but with custom recovery and xposed like modifications .
mrYogii said:
thats what i am fearing , plz guide me for updating my rooted stock .
Click to expand...
Click to collapse
in the link I posted OTA HELP DESK is all well explained.
I was in your same situation (stock + franco kernel+ TRWP recovery + Xposed) and i have just installed the OTA. This is what I did:
1- Uninstall Xposed (from inside the installer)
2- Uninstall Cerberus app (because in some cases it modifies system)
2- Flash stock kernel
3- Flash OTA in recovery
* It failed because Franco kernel modifies /system/lib/hw/power.msm8960.so --> so renamed power.msm8960.so.bak to power.msm8960.so
4- Flash OTA in recovery
5- Flash TRWP recovery
6- rooted
carlosmg2 said:
in the link I posted OTA HELP DESK is all well explained.
I was in your same situation (stock + franco kernel+ TRWP recovery + Xposed) and i have just installed the OTA. This is what I did:
1- Uninstall Xposed (from inside the installer)
2- Uninstall Cerberus app (because in some cases it modifies system)
2- Flash stock kernel
3- Flash OTA in recovery
* It failed because Franco kernel modifies /system/lib/hw/power.msm8960.so --> so renamed power.msm8960.so.bak to power.msm8960.so
4- Flash OTA in recovery
5- Flash TRWP recovery
6- rooted
Click to expand...
Click to collapse
i have stock kernel , i used xposed for ui tweaks and boot animation etc apart from that all other things are stock only, if i uninstall xposed m i good to go for OTA from wifi? or i have to flash it in recovery?if so then plz point me to 4.4.3 update download link.
thanks!
mrYogii said:
i have stock kernel , i used xposed for ui tweaks and boot animation etc apart from that all other things are stock only, if i uninstall xposed m i good to go for OTA from wifi? or i have to flash it in recovery?if so then plz point me to 4.4.3 update download link.
thanks!
Click to expand...
Click to collapse
read THIS http://forum.xda-developers.com/nexus-4/general/info-nexus-4-ota-help-desk-t2145848
I'm not sure, but your situation may need 'Scenario #2' (+ uninstalling Xposed)
can anyone else conform me on this:
i have stock kernel , i used xposed for ui tweaks and boot animation etc apart from that all other things are stock only.
suggested(http://forum.xda-developers.com/nexus-4/general/info-nexus-4-ota-help-desk-t2145848) :
Section B: Flashing in a custom recovery
1) Download the OTA.zip and copy to your phone.
2) Boot into recovery.
3) Flash the OTA just like you would a ROM.
4) Reboot.
i am not sure that xpose modifications come in this condition or not
mrYogii said:
can anyone else conform me on this:
i have stock kernel , i used xposed for ui tweaks and boot animation etc apart from that all other things are stock only.
suggested(http://forum.xda-developers.com/nexus-4/general/info-nexus-4-ota-help-desk-t2145848) :
Section B: Flashing in a custom recovery
1) Download the OTA.zip and copy to your phone.
2) Boot into recovery.
3) Flash the OTA just like you would a ROM.
4) Reboot.
i am not sure that xpose modifications come in this condition or not
Click to expand...
Click to collapse
yeah, you need to uninstall Xposed too (from within the app, not like uninstalling normal apps). Then you can reinstall and have all modules and config untouched.
carlosmg2 said:
yeah, you need to uninstall Xposed too (from within the app, not like uninstalling normal apps). Then you can reinstall and have all modules and config untouched.
Click to expand...
Click to collapse
i tried as you told, while installing OTA from zip i got following error:
/syaystem/priv-app/SystemUI.apk has unexpected contents.
installation aborted.
plz help
stock 4.4.2 nexus 4 SystemUI.apk
anyone has stock 4.4.2 nexus 4 SystemUI.apk? i have to revert back to install 4.4.3 update through recovery.
mrYogii said:
can anyone else conform me on this:
i have stock kernel , i used xposed for ui tweaks and boot animation etc apart from that all other things are stock only.
suggested(http://forum.xda-developers.com/nexus-4/general/info-nexus-4-ota-help-desk-t2145848) :
Section B: Flashing in a custom recovery
1) Download the OTA.zip and copy to your phone.
2) Boot into recovery.
3) Flash the OTA just like you would a ROM.
4) Reboot.
i am not sure that xpose modifications come in this condition or not
Click to expand...
Click to collapse
mrYogii said:
i tried as you told, while installing OTA from zip i got following error:
/syaystem/priv-app/SystemUI.apk has unexpected contents.
installation aborted.
plz help
Click to expand...
Click to collapse
Try this it'll work for you
http://forum.xda-developers.com/showthread.php?p=53176897
Sent from my Nexus 5 using XDA Free mobile app
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
This is essentially the Nexus 7 2013 WiFi's factory stock image in flashable zip format, so you can flash the device back to factory stock using CWM or TWRP, without having to rely on fastboot. It is useful for people who broke their USB port, but still have custom recovery. Or messing with roms on the go and wanting to return to stock without having access to a computer.
Included are separate zip files that will flash specific partitions of the device. To have a complete stock form of the device and preventing any issues, make sure you flash all zip files. More advance users can choose to only flash specific partitions to suit their needs.
>>> DOWNLOAD: razor_lrx21p_stock_flashable_zips <<<
Flash instruction (Important):
0. (optional) Create a full nandroid backup before flashing is recommended.
1. To have a working and stable OS, make sure you flash all the zip files, unless you know what you're doing.
2. To prevent serious incompatibilities, do a factory reset if you are coming from KitKat or from a custom rom. I would only skip doing a factory reset if the device is already running stock Lollipop.
Note: If you do not want to erase your custom recovery, do not flash the "recovery.zip", this will return your custom recovery back to stock.
I have tested flashing these multiple times with my Nexus 7 WiFi 32gb with no issues. Before proceeding with flashing, each zip files will check to make sure if the device is a Nexus 7 2013 WiFi (flo), so it won't allow you to accidentally flash on a wrong device.
If you have any issues after flashing these, even after factory resetting, follow this guide to use fastboot instead to return the device to stock.
MD5 Checksum:
File: razor_lrx21p_boot.zip
MD5: 9c12f5f7a83facf80cf596a6de1187ab
File: razor_lrx21p_bootloader_4.04.zip
MD5: 818864adb28b3559fd9d7107115de57c
File: razor_lrx21p_ddr.zip
MD5: d4ee8ae2ec00a37dc9af589cee87f9e0
File: razor_lrx21p_recovery.zip
MD5: 86d2f2d8b784ee108153b0606220040f
File: razor_lrx21p_system.zip
MD5: a0d5c8ce8fbaadc2c304f1f78e9bd6cc
Thanks a lot.
I am currently using Cleanrom. I have download the stock rooted Lolipop, and wish to flash that. It was said in that thread, that I need the latest bootloader. So from the zip file above, should I only flash the bootloader and then flash L? Or would it not make a difference if I flashed all the zips (besides the recovery)?
No, I do not want to get rid of my custom recovery. I am using the latest version of TWRP
Flashed with TWRP, works well. Thanks a lot!
eksasol said:
This is essentially the Nexus 7 2013 WiFi's factory stock image in flashable zip format, so you can flash the device back to factory stock using CWM or TWRP, without having to rely on fastboot. It is useful for people who broke their USB port, but still have custom recovery. Or messing with roms on the go and wanting to return to stock without having access to a computer.
Included are separate zip files that will flash specific partitions of the device. To have a complete stock form of the device and preventing any issues, make sure you flash all zip files. More advance users can choose to only flash specific partitions to suit their needs.
>>> DOWNLOAD: razor_lrx21p_stock_flashable_zips <<<
Flash instruction (Important):
0. (optional) Create a full nandroid backup before flashing is recommended.
1. To have a working and stable OS, make sure you flash all the zip files, unless you know what you're doing.
2. To prevent serious incompatibilities, do a factory reset if you are coming from KitKat or from a custom rom. I would only skip doing a factory reset if the device is already running stock Lollipop.
Note: If you do not want to erase your custom recovery, do not flash the "recovery.zip", this will return your custom recovery back to stock.
I have tested flashing these multiple times with my Nexus 7 WiFi 32gb with no issues. Before proceeding with flashing, each zip files will check to make sure if the device is a Nexus 7 2013 WiFi (flo), so it won't allow you to accidentally flash on a wrong device.
If you have any issues after flashing these, even after factory resetting, follow this guide to use fastboot instead to return the device to stock.
MD5 Checksum:
File: razor_lrx21p_boot.zip
MD5: 9c12f5f7a83facf80cf596a6de1187ab
File: razor_lrx21p_bootloader_4.04.zip
MD5: 818864adb28b3559fd9d7107115de57c
File: razor_lrx21p_ddr.zip
MD5: d4ee8ae2ec00a37dc9af589cee87f9e0
File: razor_lrx21p_recovery.zip
MD5: 86d2f2d8b784ee108153b0606220040f
File: razor_lrx21p_system.zip
MD5: a0d5c8ce8fbaadc2c304f1f78e9bd6cc
Click to expand...
Click to collapse
Flawless as usual, thanks Eksasol
Great, will do this tomorrow! Thanks
Envoyé de ma Nexus 7.2 depuis tapatalk
particular order?
Thank you very much eksasol!
Is there a particular order in which these files should be flashed?
Cheers,
Sandor
schermvlieger said:
Thank you very much eksasol!
Is there a particular order in which these files should be flashed?
Cheers,
Sandor
Click to expand...
Click to collapse
No they should all work. The phone will boot correctly as long as you have all the proper kernel (boot), system (OS) and bootloader installed.
timrock said:
Thanks a lot.
I am currently using Cleanrom. I have download the stock rooted Lolipop, and wish to flash that. It was said in that thread, that I need the latest bootloader. So from the zip file above, should I only flash the bootloader and then flash L? Or would it not make a difference if I flashed all the zips (besides the recovery)?
No, I do not want to get rid of my custom recovery. I am using the latest version of TWRP
Click to expand...
Click to collapse
You should flash both the bootloader and DDR zip. Then flash the the rom, it should work. Also if you are coming from KitKat, you will need to factory reset or you will get lots of errors.
Marvellous!
eksasol said:
You should flash both the bootloader and DDR zip. Then flash the the rom, it should work. Also if you are coming from KitKat, you will need to factory reset or you will get lots of errors.
Click to expand...
Click to collapse
Would a factory reset delete the files I have on my device? If so, the ROM is in a folder on my device.
Sent from my Nexus 7 using Tapatalk
Which one of these zips controls user data? I want to try and dirty flash, as I dont want to lose any data if I dont have to. Any suggestions?
I have not done a factory reset yet; and add away tells me the device is not rooted.
Did the update remove root, or is this one of those issues related to not doing a factory reset?
All else seems to be working at the moment.
eksasol said:
You should flash both the bootloader and DDR zip. Then flash the the rom, it should work. Also if you are coming from KitKat, you will need to factory reset or you will get lots of errors.
Click to expand...
Click to collapse
So the bootloader and DDR zips can be flashed through TWRP to update the bootloader only, and then a separate rooted ROM (ie scrosler's) can be flashed through TWRP with the help of the updated bootloader?
I did try to flash the bootloader only, but it failed. The need for the DDR would explain why.
Cheers.
Thanks this is what ive been looking for.
Bought my nexus 7 2013 3weeks ago it came with 4.4.2 and i towelrooted it n flashed twrp now on a custom rom but wish i didnt coz i wanted the updates 5.0 but i dont have a pc so this is what i needed.
So if i flash all zips does that mean il be stock 5.0 and ready for future updates?
Aslo my bootloader is already 4.04 so should i stil flash the one above?
Is it possable to flash jus system+boot zips as a second rom (multirom)?
I am not going to install 5.0 yet because some of the apps I use are not yet compatible. If I just flashed the boot loader but stayed with my current ROM , cleanrom, would that be a problem?
Sent from my Nexus 7 using Tapatalk
Thanks man this was really helpful for me <3 Can't seem to get root access though. Any idea why?
James_Feltham said:
Thanks man this was really helpful for me <3 Can't seem to get root access though. Any idea why?
Click to expand...
Click to collapse
Hi James,
You'll need to re-root your device after you flashed these images.
CF-Autoroot will help you here; click.
You'll need to reinstall your custom bootloader as well if the stock bootloader does not meet your requirements.
timrock said:
Would a factory reset delete the files I have on my device? If so, the ROM is in a folder on my device.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
It depends, for normal Android devices, if you factory reset using stock recovery it will wipe everything in the device. For TWRP and CWM, if you factory reset it will leave your internal storage alone.
MWFD said:
Which one of these zips controls user data? I want to try and dirty flash, as I dont want to lose any data if I dont have to. Any suggestions?
Click to expand...
Click to collapse
None of them control userdata, I excluded that partition image. If you want to dirty flash, just don't do a factory reset or wipe your /data folder.
toonarmy4life said:
Thanks this is what ive been looking for.
Bought my nexus 7 2013 3weeks ago it came with 4.4.2 and i towelrooted it n flashed twrp now on a custom rom but wish i didnt coz i wanted the updates 5.0 but i dont have a pc so this is what i needed.
So if i flash all zips does that mean il be stock 5.0 and ready for future updates?
Aslo my bootloader is already 4.04 so should i stil flash the one above?
Is it possable to flash jus system+boot zips as a second rom (multirom)?
Click to expand...
Click to collapse
Do not flash these zip as a secondary rom for multirom, this is meant to flash for the entire device only. This is factory images, not roms. You could download some type of stock based roms and use it with multirom instead. If you have the latest bootloader you don't need to flash it again, but it won't hurt if you do. Yes, flashing all the zips and factory resetting will return the device to stock.
timrock said:
I am not going to install 5.0 yet because some of the apps I use are not yet compatible. If I just flashed the boot loader but stayed with my current ROM , cleanrom, would that be a problem?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
That should not be any problem.
James_Feltham said:
Thanks man this was really helpful for me <3 Can't seem to get root access though. Any idea why?
Click to expand...
Click to collapse
Because this is Android 5, it have extra security to prevent rooting like in the past. I believe to get root you need try Chainfire's CF-AutoRoot method, or use a custom kernel and flash SuperSu.
schermvlieger said:
I have not done a factory reset yet; and add away tells me the device is not rooted.
Did the update remove root, or is this one of those issues related to not doing a factory reset?
All else seems to be working at the moment.
Click to expand...
Click to collapse
This isn't an update. It is a factory image that return the device to stock form. You will lose root and every changes to the system partition in the process.
Can this file be flashed on any device??
#divy said:
Can this file be flashed on any device??
Click to expand...
Click to collapse
No only on Nexus 7 2013 WiFi 32gb
http://shield.nvidia.com/tablet-release-notes/2.2/
now to figure out how to get this to update on my rooted LTE Tablet.....
I'm rooted and just got the update. But haven't completed the update yet as I'm too lazy to reroot.
I tried using the nvidia updater, which failed since it rebooted and CWM had no idea what to do. I made a CWM backup so I am going to see how well it flashes in CWM manually.
I managed to find the OTA download location and have superSU at the ready in my downloads folder in case I have to reflash. the OTA saved as:
/data/data/com.nvidia.ota/files/ROM/shield_tablet_software_upgrade_2.2_-_lte__5.0.1.zip
Someone please report the steps on how to do this for Rooted 2.1.
CWM install zip failed. build fingerprint mismatched, its probably CWM. Will try sideloading stock recovery then installing the zip afterward, I think I remember seeing somewhere here that's how people upgraded rooted devices from 2.0 to 2.1
Omg things seem to be more snappy! The dreaded lag may be gone! I'm not rooted so I did the ota install
I'm really interested in your findings, i need to find a tutorial on how to flash back stock recovery then i can do the update and hopefully reroot.
Iorkca said:
I'm really interested in your findings, i need to find a tutorial on how to flash back stock recovery then i can do the update and hopefully reroot.
Click to expand...
Click to collapse
currently working on it right now, need about a few to upload all files and then get everything setup....
From a post on Geforce forum
fjrichman
*
*
*
*
For rooted users you'll want to use theses.
US LTE Full:*http://ota.nvidia.com/ota/rom/productionBL-droid-signed-wx_na_do-full_ota-29979_512.4856.zip
US Wifi Full:*http://ota.nvidia.com/ota/rom/productionBL-droid-signed-wx_na_wf-full_ota-29979_512.4856.zip
I successfully updated rooted wifi using link
Awsome sounds good. Quick question to get stock recovery back all id have to do is extract the recovery.img file from the ota 2.1 file i downloaded off nvidia's site and load it like i did the CWM recovery from the root thread right?
Or (if you've got root) wait until the full 2.2 .zip is available, then download it and flash it through your custom recovery, followed by the latest SuperSU. (just like the last Lollipop update).
Interestingly, the OTA update tool has an option for "Check full update" (under the top right menu), but it doesn't seem to return anything...yet...
Sent from my SHIELD Tablet using XDA Free mobile app
Pretty much you are going
Flash Stock recovery by any preferred method
Flash Update
adb Reflash CWM recovery
Thru recovery flash SuperSU
**Profit**
Working on getting all the files in one package as of right now. Damn internet hogs in my house.
Cant we use Flashify to flash stock recovery and then updating the OTA and then reflash our recoverys and supersu.zip?
NaminatoR1254jaime.sier said:
Cant we use Flashify to flash stock recovery and then updating the OTA and then reflash our recoverys and supersu.zip?
Click to expand...
Click to collapse
Yeah, if you have the stock recovery file....
mcord11758 said:
From a post on Geforce forum
fjrichman
*
*
*
*
For rooted users you'll want to use theses.
US LTE Full:*http://ota.nvidia.com/ota/rom/productionBL-droid-signed-wx_na_do-full_ota-29979_512.4856.zip
US Wifi Full:*http://ota.nvidia.com/ota/rom/productionBL-droid-signed-wx_na_wf-full_ota-29979_512.4856.zip
I successfully updated rooted wifi using link
Click to expand...
Click to collapse
Did you clean install, or did you dirty flash?
Just curious if this can be applied as an update our not.
Sent from my SHIELD Tablet using XDA Free mobile app
masterchiefb117 said:
Yeah, if you have the stock recovery file....
Click to expand...
Click to collapse
I dont
But Im downloading the 2.1 update stock images. Funny how I deleted the 2 gb zip yesterday and now I need it.
masterchiefb117 said:
Pretty much you are going
Flash Stock recovery by any preferred method
Flash Update
adb Reflash CWM recovery
Thru recovery flash SuperSU
**Profit**
Working on getting all the files in one package as of right now. Damn internet hogs in my house.
Click to expand...
Click to collapse
You won't be able to successfully flash the UPDATE .zip file (~94MB) on a rooted (read: modified) Lollipop version.
Recovery version is irrelevant.
You need the FULL 2.2 rom (already found above , ~731MB), flash it in your current custom recovery and re-root by flashing SuperSU again.
Sent from my SHIELD Tablet using XDA Free mobile app
ok, here's what I dug up. If you are rooted and want it NOW, get to it, otherwise wait for someone to clean up the process:
get the OTA from here: https://forums.geforce.com/default/...hread-released-2-17-15-/post/4464815/#4464815
get your latest SuperSU flashable zip: http://download.chainfire.eu/396/SuperSU/
get your recovery ready for reflashing, the OTA will install the stock recovery again. I went with: http://forum.xda-developers.com/showpost.php?p=58864006&postcount=90
boot into recovery and install zip from sideload. then choose either: adb sideload productionBL-droid-signed-wx_na_do-full_ota-29979_512.4856.zip or adb sideload productionBL-droid-signed-wx_na_wf-full_ota-29979_512.4856.zip
reboot and let the upgrade happen, you've lost root and recovery, but you still are unlocked so you just have to reflash them. get into fastboot with power and volume down, then flash recovery: fastboot flash recovery openrecovery-twrp-2.8.5.0-shieldtablet.img
load up recovery and flash the superSU zip and you're back in business.
ShrekOpher said:
Did you clean install, or did you dirty flash?
Just curious if this can be applied as an update our not.
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
Wiped cache and davlik then just in case flashed supersu after rom
An Droid said:
You won't be able to successfully flash the UPDATE .zip file (~94MB) on a rooted (read: modified) Lollipop version.
Recovery version is irrelevant.
You need the FULL 2.2 rom (already found above , ~731MB), flash it in your current custom recovery and re-root by flashing SuperSU again.
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
That means a rooted lollipop user with custom recovery, can download the full ota, and dirty flash it, right?