Related
First up, let me tell you that doing this is not necessay to get the OTA or having a smooth JB experience. The JB OTA installs without a wipe which means the data is preserved.
UPDATE: Google has put up the full image for 4.1.1 [i9023, i9020a and i9020t] . Now you do not need to clean flash ICS and then JB. Follow the part 1 of the guide below and flash the JB image instead of ICS. Nothing more to it.
Thanks anshumandash for pointing it out
That being said, I wanted to have the real stock image on my Nexus S and then Upgrade to JellyBean. Below are the steps that I took.
Go to this GoogleAndroidImages page and download the appropriate image for your phone & download. Since mine is an international version a.k.a I9023, I chose that ROM.
The download will be a tar.gz file. Use a utility like 7Zip to uncompress it. The tar.gz will have a .tar file inside and the /tar file will have a folder. Extract the folder to your PC. For my download, the folder was named soju-imm76d
Next Steps will wipe your phone, completely
Reboot your phone into bootloader mode.
Open a command prompt, navigate to the folder in step 2.
Enter the below commands, the image file names are for my download, modify it to the file names in your folder before running (I assume that you have fastboot working)
fastboot flash bootloader bootloader-crespo-i9020xxkl1.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo-i9020xxki1.img
fastboot reboot-bootloader
fastboot -w update image-soju-imm76d.zip
After the last step, the phone reboots and takes you to the initial setup screen.
Additionally, I reflashed CWM and the the JellyBean OTA along with superuser. Below are the steps for that
Download the OTA from google server. This thread by oldblue910 is kept updated with the latest updates. Currently it has OTA's for I9023 and I9020A
Download the superuser from androidsu website. This is the RC version 3.2
Download the latest clocworkmod recovery touch-version non-touch-version
For simplicity sake, put all the files downloaded at a single folder
Reboot phone into bootloader mode.
Open a command prompt and go to the folder in step 4.
Now execute this fastboot command to flash the CWM recovery. Change the filename to the file you have downloaded.
fastboot flash recovery recovery-clockwork-6.0.0.7-crespo.img
Now using the vol down key choose to go to recovery.
There, using the options, navigate to the install zip from sdcard and first install the OTA and then the superuser zip file.
Reboot. You now have rooted JB
PS: I additionally did a fastboot oem lock and fastboot oem unlock back to back to wipe my sdcard too
Reason for this post?
Originally Posted by dEris
Because if you're not on stock 4.0.4 image, you cannot flash the OTA zip. You get a Status 7 error.
This isn't "his" way. It's the official Google way if you go to the Google site to download stock images
Click to expand...
Click to collapse
Whats the difference/benefits between ur "way" and just flashing JB zip with proper clean install?
thanks in advance ;-]
greg2826 said:
Whats the difference/benefits between ur "way" and just flashing JB zip with proper clean install?
thanks in advance ;-]
Click to expand...
Click to collapse
Because if you're not on stock 4.0.4 image, you cannot flash the OTA zip. You get a Status 7 error.
This isn't "his" way. It's the official Google way if you go to the Google site to download stock images.
I think this was the exact way I did it as well:thumbup: I must have skipped one step during the process though because my "SD" didn't get wiped.
turchs
This doesn't apply to the i9020a Nexus S
-_-
karleeezy said:
This doesn't apply to the i9020a Nexus S
-_-
Click to expand...
Click to collapse
Yes it does! I9020A OTA in the thread below!
http://forum.xda-developers.com/showthread.php?t=1736645
dEris said:
Because if you're not on stock 4.0.4 image, you cannot flash the OTA zip. You get a Status 7 error.
This isn't "his" way. It's the official Google way if you go to the Google site to download stock images.
Click to expand...
Click to collapse
ok got it
my thanks went 2 u
Couldn't you just do a factory reset after installing the OTA package?
Thank you, your tutorial was helpful. Needed to go back to stock.
FirePoncho86 said:
Yes it does! I9020A OTA in the thread below!
http://forum.xda-developers.com/showthread.php?t=1736645
Click to expand...
Click to collapse
Got it! Thanks, dude!
jithinsarath said:
First up, let me tell you that doing this is not necessay to get the OTA or having a smooth JB experience. The JB OTA installs without a wipe which means the data is preserved.
That being said, I wanted to have the real stock image on my Nexus S and then Upgrade to JellyBean. Below are the steps that I took.
Go to this GoogleAndroidImages page and download the appropriate image for your phone & download. Since mine is an international version a.k.a I9023, I chose that ROM.
The download will be a tar.gz file. Use a utility like 7Zip to uncompress it. The tar.gz will have a .tar file inside and the /tar file will have a folder. Extract the folder to your PC. For my download, the folder was named soju-imm76d
Next Steps will wipe your phone, completely
Reboot your phone into bootloader mode.
Open a command prompt, navigate to the folder in step 2.
Enter the below commands, the image file names are for my download, modify it to the file names in your folder before running (I assume that you have fastboot working)
fastboot flash bootloader bootloader-crespo-i9020xxkl1.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo-i9020xxki1.img
fastboot reboot-bootloader
fastboot -w update image-soju-imm76d.zip
After the last step, the phone reboots and takes you to the initial setup screen.
Additionally, I reflashed CWM and the the JellyBean OTA along with superuser. Below are the steps for that
Download the OTA from google server
Download the superuser from androidsu website. This is the RC version 3.2
Download the latest clocworkmod recovery touch-version non-touch-version
For simplicity sake, put all the files downloaded at a single folder
Reboot phone into bootloader mode.
Open a command prompt and go to the folder in step 4.
Now execute this fastboot command to flash the CWM recovery. Change the filename to the file you have downloaded.
fastboot flash recovery recovery-clockwork-6.0.0.7-crespo.img
Now using the vol down key choose to go to recovery.
There, using the options, navigate to the install zip from sdcard and first install the OTA and then the superuser zip file.
Reboot. You now have rooted JB
PS: I additionally did a fastboot oem lock and fastboot oem unlock back to back to wipe my sdcard too
Click to expand...
Click to collapse
Well written. I'm sure you helped hundreds of stressed out newcomers with this. :laugh:
chronophase1 said:
I must have skipped one step during the process though because my "SD" didn't get wiped.
Click to expand...
Click to collapse
yeah.. the fastbbot oem lock and fastboot oem unlock after the 4.0.4 flash wipes the SD
rhadrio said:
Couldn't you just do a factory reset after installing the OTA package?
Click to expand...
Click to collapse
The OTA is essentially an upgrade, it builds atop the existing ICS 4.0.4 rom. I had so much mods on top of my rom that I wasnted to have a clean start. Besides, there has been multiple reports of an error 7 in case of non stock or certain moded roms.
karleeezy said:
Got it! Thanks, dude!
Click to expand...
Click to collapse
Glad I could help
I am already missing the various tweaks I had on the CM9 RC2 and other mods
jithinsarath said:
yeah.. the fastbbot oem lock and fastboot oem unlock after the 4.0.4 flash wipes the SD
Click to expand...
Click to collapse
Thanks for the tutorial. Thinking of doing the update this way. I have a i9020a rooted with 4.0.4 and when I try to do OTA update I got signature verification error in CWM 5.8.0.2.
For the wipe, from what I understand, you just execute the lock command above which wipes the SD and then unlock it with the second command? Sorry total newbie on this.
That is exactly what i did when the OTA zip pacage first showed up here on xda. Good guide. Im rocking mine with simple kernel
I followed the first part of the guide to restore to stock, and then did the OTA update. It all went well except one little catch: after the OTA update for 4.1.1, I flashed the CWM 6.0.0.7, and then realize that I forgot to copy the root zip file onto SD. Had to reboot the phone and copy the file over. After that I go into bootload mode again and try to go to recovery, ends up with a red exclaim mark and phone is locked. Had to do a battery pull, restart the phone, and then reflash that CWM image, and immediately after that, go to recovery and do the root zip install. Not sure why is that. Have not tried to do the recovery again but I'm glad that I'm now on JB and rooted. Thanks OP !
I keep gettin status 7 error.
When i install the OTA through the phone itself (by letting it restart the phone and install it) i get the exclamation mark.
Im on Stock 4.0.4 and not rootet. Is there anyway to install this OTA without fully wipe it?
d960 said:
Thanks for the tutorial. Thinking of doing the update this way. I have a i9020a rooted with 4.0.4 and when I try to do OTA update I got signature verification error in CWM 5.8.0.2.
For the wipe, from what I understand, you just execute the lock command above which wipes the SD and then unlock it with the second command? Sorry total newbie on this.
Click to expand...
Click to collapse
The lock command just lock the bootloader, it is the unlock command that will wipe the SD. It will also ask you for a confirmation on your phone's screen...
d960 said:
I followed the first part of the guide to restore to stock, and then did the OTA update. It all went well except one little catch: after the OTA update for 4.1.1, I flashed the CWM 6.0.0.7, and then realize that I forgot to copy the root zip file onto SD. Had to reboot the phone and copy the file over. After that I go into bootload mode again and try to go to recovery, ends up with a red exclaim mark and phone is locked. Had to do a battery pull, restart the phone, and then reflash that CWM image, and immediately after that, go to recovery and do the root zip install. Not sure why is that. Have not tried to do the recovery again but I'm glad that I'm now on JB and rooted. Thanks OP !
Click to expand...
Click to collapse
when you rebooted the phone to copy the su.zip, the OS restored the oroginal recovery. That's why you got the red exclamation mark. To get the CWm, you can flash it again in fast boot, go into recovery and then ask the CWM to reboot.. if it is 6.0.0.7, before reboot it will ask for the recovery to be made overwrite proof (a nice new feature in v6), choose yes and you are good to go..
alireza_simkesh said:
I keep gettin status 7 error.
When i install the OTA through the phone itself (by letting it restart the phone and install it) i get the exclamation mark.
Im on Stock 4.0.4 and not rootet. Is there anyway to install this OTA without fully wipe it?
Click to expand...
Click to collapse
Status 7 error comes when you have some kind of custom rom or may be some core mod applied to your rom. I am not aware of a way to get this proceed without full wipe: You can try the below though:
1. Flash the stock 4.0.4 for your phone without data wipe (you can wipe the dalvik cache though). This will make sure you are on the "stock".
2. Try the OTA
or you can backup using titanium backup, and then follow my guide. Restore the apps after flashing 4.0.4 and the try OTA.
It will be good it you take a nandroid backup before doing either of the above.
jithinsarath said:
Status 7 error comes when you have some kind of custom rom or may be some core mod applied to your rom. I am not aware of a way to get this proceed without full wipe: You can try the below though:
1. Flash the stock 4.0.4 for your phone without data wipe (you can wipe the dalvik cache though). This will make sure you are on the "stock".
2. Try the OTA
or you can backup using titanium backup, and then follow my guide. Restore the apps after flashing 4.0.4 and the try OTA.
It will be good it you take a nandroid backup before doing either of the above.
Click to expand...
Click to collapse
Flash image or zip?
ironia. said:
Flash image or zip?
Click to expand...
Click to collapse
OK, I'm confused now
As I understand, flashing the .img WILL wipe out the apps & data.
However, I have flashed the CM9 nightlies zip multiple times without loosing the data. Here we are dealing with a stock zip, so I am not sure. You can try the zip method after taking a nandroid backup.
fastboot mode erase * and fastboot flash all image files。
in about system update.install ota file. restart error
:crying::crying::crying:
sellength said:
fastboot mode erase * and fastboot flash all image files。
in about system update.install ota file. restart error
:crying::crying::crying:
Click to expand...
Click to collapse
Wrong section, this is for development only.
As for your question, I do not understand what you are asking, what are you attempting to do with fastboot mode?
xIC-MACIx said:
Wrong section, this is for development only.
As for your question, I do not understand what you are asking, what are you attempting to do with fastboot mode?
Click to expand...
Click to collapse
the development section. only dev question ? ok
sellength said:
fastboot mode erase * and fastboot flash all image files。
in about system update.install ota file. restart error
:crying::crying::crying:
Click to expand...
Click to collapse
If you have the factory image, from Google (and nowhere else), just run the flash-all.bat file. You "may" have to unlock your bootloader prior to running it if you haven't already, and you'll need to have the device in fastboot mode prior to running the batch file too, but once those 2 simple tasks are done, the batch file takes care of the rest.
If your using a toolkit or some other method for flashing a factory image, I suggest stopping, and just doing the above.
This forum is not for any threads for questions... this needs to go to General or Q/A... just download the factory image from Google, reboot into fastboot and run the flash-all script... you don't need to be unlocked...
craigacgomez said:
This forum is not for any threads for questions... this needs to go to General or Q/A... just download the factory image from Google, reboot into fastboot and run the flash-all script... you don't need to be unlocked...
Click to expand...
Click to collapse
If im on 4.2 and my device fails to update to 4.2.1, saying me error on recovery, should I only unzip the image from google, put my n10 on fastboot mode and run the flash all script as you said? Will this erase my data? Im just root, haven't unlocked my bootloader.
Sorry for my english
lKBZl said:
If im on 4.2 and my device fails to update to 4.2.1, saying me error on recovery, should I only unzip the image from google, put my n10 on fastboot mode and run the flash all script as you said? Will this erase my data? Im just root, haven't unlocked my bootloader.
Sorry for my english
Click to expand...
Click to collapse
same question
I've unlocked & rooted & the OTA fails trying to flash the recovery (trying to flash from twrp, duh, can't overwrite).
How should I go about updating the system w/o wiping out everything I already have?
If I fastboot flash_image system will it only overwrite changes to my system partition & leave my data & apps alone?
I've got OTA Root Keeper installed, so I'm hopeful even if I lose root I can get it back easy enough (either way, no biggie; can always reroot, ain't no thang).
tia for any advice.
edit: f-bomb... no 4.2.1 img available for N10 yet...
Sent from my Nexus 10 using xda premium
dboftlp said:
same question
I've unlocked & rooted & the OTA fails trying to flash the recovery (trying to flash from twrp, duh, can't overwrite).
How should I go about updating the system w/o wiping out everything I already have?
If I fastboot flash_image system will it only overwrite changes to my system partition & leave my data & apps alone?
I've got OTA Root Keeper installed, so I'm hopeful even if I lose root I can get it back easy enough (either way, no biggie; can always reroot, ain't no thang).
tia for any advice.
edit: f-bomb... no 4.2.1 img available for N10 yet...
Sent from my Nexus 10 using xda premium
Click to expand...
Click to collapse
There is... i've seen a post in google + from a guy that links you to a google page with n10 4.2.1 img.
sikagoon7 said:
Nexus 10 hasn't gotten the (JOP40D) images yet which means the only way to get the 4.2.1 update is to get an OTA. I think the OTA link is floating around AndroidPolice and AndroidCentral somewhere but you'll have to look. Whatever images for 4.2.1 on the Nexus 10 are fake because Google hasn't even released them yet.
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
yep, & therein lies the problem. I can't seem to flash the OTA b/c I'm getting recovery errors...
when I tried flashing stock recovery I just get red exclamation
:-\
Sent from my Nexus 10 using xda premium
dboftlp said:
yep, & therein lies the problem. I can't seem to flash the OTA b/c I'm getting recovery errors...
when I tried flashing stock recovery I just get red exclamation
:-\
Sent from my Nexus 10 using xda premium
Click to expand...
Click to collapse
So what are you gonna do? I want to have the 4.2.1 and be able to update my n10 with the uncoming otas, I dunno what should I do now, im kinda stuck..
lKBZl said:
So what are you gonna do? I want to have the 4.2.1 and be able to update my n10 with the uncoming otas, I dunno what should I do now, im kinda stuck..
Click to expand...
Click to collapse
Flash stock recovery .... and get the OTA, then re-flash TWRP ....
You may have to re-root ...
Watcher64 said:
Flash stock recovery .... and get the OTA, then re-flash TWRP ....
You may have to re-root ...
Click to expand...
Click to collapse
I already have stock recovery... it's not about the recovery, I think it's because i put aosp browser instead of the default one, and when ota check system/apps, it finds something has changed. Also may be due to the root?
lKBZl said:
I already have stock recovery... it's not about the recovery, I think it's because i put aosp browser instead of the default one, and when ota check system/apps, it finds something has changed. Also may be due to the root?
Click to expand...
Click to collapse
I don't see how that would matter, I used the aosp browser as well, and all I did was put stock recovery back on ..
hmmmm
Maybe you should just flash one of the updated stock/rooted roms in the dev section.
All,
Thanks in advance for any help you can provide. I have a Nexus 4 that I rooted and installed CWM recovery on, but I never installed any new kernels, ROMs, or radios. I'm currently on 4.4.4 and I want to upgrade to Lollipop. The OTA upgrade failed. So I tried returning to stock recovery and doing both the OTA and adb sideloading the OTA zip. Both fail.
The error message is "Package expects build fingerprint of google/occam/mako:4.4.4/KTU84P/1227136:user/release-keys or google/occam/mako:5.0/LRX21T/1576899:user/release-keys; this device has google/occam/mako:4.4/KRT160/907817:user/release-keys." (But I definitely have 4.4.4 on my phone, not 4.4.0.)
The extra difficulty is that I really, really do not want to wipe my phone. I have a lot of apps with a lot of configuration and other user data. So is there anything I can do? I guess I should try unrooting somehow? Or is there some other zip I can download that, through some type of recovery, will install the OTA without doing this check and also without wiping me?
Thanks again!
moriarty00 said:
All,
Thanks in advance for any help you can provide. I have a Nexus 4 that I rooted and installed CWM recovery on, but I never installed any new kernels, ROMs, or radios. I'm currently on 4.4.4 and I want to upgrade to Lollipop. The OTA upgrade failed. So I tried returning to stock recovery and doing both the OTA and adb sideloading the OTA zip. Both fail.
The error message is "Package expects build fingerprint of google/occam/mako:4.4.4/KTU84P/1227136:user/release-keys or google/occam/mako:5.0/LRX21T/1576899:user/release-keys; this device has google/occam/mako:4.4/KRT160/907817:user/release-keys." (But I definitely have 4.4.4 on my phone, not 4.4.0.)
The extra difficulty is that I really, really do not want to wipe my phone. I have a lot of apps with a lot of configuration and other user data. So is there anything I can do? I guess I should try unrooting somehow? Or is there some other zip I can download that, through some type of recovery, will install the OTA without doing this check and also without wiping me?
Thanks again!
Click to expand...
Click to collapse
OTA wants complete stock and obviously it doesn't think so about your phone. One option could be to back up to the cloud or some place outside the phone with TiBu (or whatever backup app you trust), then flash lollipop and try restore from TiBu. Another option would be to unroot (Supersu has an option to completely unroot), then retry.
Actually, I figured out what works! This was on a stock rooted device with stock recovery, but I bet it would work with custom recovery too. Instructions modified from https://pay.reddit.com/r/nexus4/comments/1qny3f/howto_update_your_stock_w_lte_nexus_4_without/ .
1. Download the image you want from https://developers.google.com/android/nexus/images . Extract it, extract the .zip file inside it too, and collect all of the .img files into one folder.
2. adb reboot bootloader (and wait until the bootloader comes up)
3. fastboot flash bootloader bootloader-mako-makoz30f.img (or whatever file has a similar name, if you got a different image than I did)
4. fastboot reboot-bootloader (and wait until the bootloader comes back up)
5. fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.04.img (or whatever file has a similar name, if you got a different image than I did)
6. fastboot reboot-bootloader (and wait until the bootloader comes back up)
7. fastboot flash boot boot.img
8. fastboot flash recovery recovery.img
9. fastboot flash system system.img
10. fastboot format cache
11. fastboot reboot
12. Don't panic unless you've seen the startup animation for at least 15 minutes without anything else happening.
I lost root, but I imagine re-custom-recoverying and re-rooting won't be any harder than the first time around.
Hi moriarty00,
I'm going to try the same procedure, thank you for posting this.
Can you confirm that your data and app are safe after the upgrade?
moriarty00 said:
Actually, I figured out what works! This was on a stock rooted device with stock recovery, but I bet it would work with custom recovery too. Instructions modified from https://pay.reddit.com/r/nexus4/comments/1qny3f/howto_update_your_stock_w_lte_nexus_4_without/ .
1. Download the image you want from https://developers.google.com/android/nexus/images . Extract it, extract the .zip file inside it too, and collect all of the .img files into one folder.
2. adb reboot bootloader (and wait until the bootloader comes up)
3. fastboot flash bootloader bootloader-mako-makoz30f.img (or whatever file has a similar name, if you got a different image than I did)
4. fastboot reboot-bootloader (and wait until the bootloader comes back up)
5. fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.04.img (or whatever file has a similar name, if you got a different image than I did)
6. fastboot reboot-bootloader (and wait until the bootloader comes back up)
7. fastboot flash boot boot.img
8. fastboot flash recovery recovery.img
9. fastboot flash system system.img
10. fastboot format cache
11. fastboot reboot
12. Don't panic unless you've seen the startup animation for at least 15 minutes without anything else happening.
I lost root, but I imagine re-custom-recoverying and re-rooting won't be any harder than the first time around.
Click to expand...
Click to collapse
Wow, a 12-step program
I simply rolled back my changes, and applying the OTA was as simple as pressing the "restart and install" button Here are some steps:
I used the app Flashify from Play Store to flash stock 4.4.4 recovery. I downloaded the stock factory image from google's own site (this one), used 7zip to extract the archives (tgz and tar), found "recovery.img" and transfered that to my phone. Then chose that file in Flashify.
Uninstalled all apps that made system changes, like Xposed framework and mods, BetterBatteryStats etc.
Removed Root with SuperSU cleanup function
Rebooted for good measure and apply OTA from notification - wait an hour or two for it to complete
Profit (do we still say that on the internet? Getting old here...)
I don't know if certain ways to get root will break the OTA. I used towel-root, and apparently SuperSU was able to undo that completely.
DrDruge said:
Hi moriarty00,
I'm going to try the same procedure, thank you for posting this.
Can you confirm that your data and app are safe after the upgrade?
Click to expand...
Click to collapse
Yup, perfectly safe! Just make sure not to flash other images, like userdata.img.
venu123 said:
OTA wants complete stock and obviously it doesn't think so about your phone. One option could be to back up to the cloud or some place outside the phone with TiBu (or whatever backup app you trust), then flash lollipop and try restore from TiBu. Another option would be to unroot (Supersu has an option to completely unroot), then retry.
Click to expand...
Click to collapse
If I unroot with Supersu how do I get root back?
moriarty00 said:
Yup, perfectly safe! Just make sure not to flash other images, like userdata.img.
Click to expand...
Click to collapse
Thank you!
Unfortunately the steps did not work for me, maybe I had some irreversible modifications or I had followed a different rooting procedure.
Or maybe I made a mistake in the upgrading steps.
Anyway, I had to flash the whole ROM and now everything is working fine.
Hey!
Basically I have similar problem with upgrading from 4.4.4 to 5.0 using OTA. Log from TWRP says:
Package expects build fingerprint of google/occam/mako:4.4.4/KTU84P/1227136:user/release-keys or google/occam/mako:5.0/LRX21T/1576899:user/release-keys; this device has google/occam/mako:4.3/JWR66V/737497:user/release-keys.
Click to expand...
Click to collapse
Phone has been rooted using Nexus Root Toolkit. And as long as there wouldn't be a problem with flashing using adb and wiping all data, there is one setback... My nexus is somehow broken. Communication via USB does not work, at all. Neither phone nor PC sees other device. Certified LG service centre nearby said that it is problem with main board, so generally repair is unprofitable.
So question is: How do I update to 5.0 and then root, without USB connection to my PC?
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.
Is there is an easy to do this without having to wipe everything and start over fresh?
Will this work? http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
WiFivomFranMan said:
Is there is an easy to do this without having to wipe everything and start over fresh?
Will this work? http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
Click to expand...
Click to collapse
I'm on the same boat, but I think our answer will come soon. Today I found out that WugFresh will be updating the NRT Toolkit to support the Nexus Player. See this post.
Why not just download the image and flash it? Plenty of guides on how to do this
lafester said:
Why not just download the image and flash it? Plenty of guides on how to do this
Click to expand...
Click to collapse
I didn't know that there were difficulties with 5.1.1. I used Wugfresh's tool to install 5.1.1 with the "no wipe" option and I had 5.1.1 just fine - but can't figure out how to get root back!! And I need root to expand the storage!! Right now I have a fresh, clean, 5.1.1 install on my NP.
I tried Wugfresh's tool, I sure wish it told me that it didn't work with the firmware that it had already detected!!
I also tried the Chainfire root.img that I used back on 5.0 and it seems to work until I tell SuperSU to update the binaries. At that point it basically times out and asks me to reboot.
What next?! Wait for Wugfresh? Is there another way to root?
I flashed the cm recovery from dhacker and used it to flash the newest beta of supersu. After that the app didn't show up until I installed it from the store but now it works fine
I just want to upgrade it without losing all my stuff (Saved games for my NES ROM, etc...)
Why don't you locate the save data in es file explorer and copy it to the cloud. Reimage nexus player and set up es file explorer, cloud and copy the saved data back to where you stored it.
would anyone be so kind to point me to one of the guides on how to use factory image/OTA to update from 5.0 rooted to 5.1.1? I don't care about keeping my settings, and I don't care about root. just want the latest and greatest.
thanks in advance
The Nexus Player is a Nexus device, and you can always upgrade to the latest version by using the factory images found here: https://developers.google.com/android/nexus/images. The procedure to flash a factory image on any Nexus device has not changed since the Nexus One was released, so you can look at any of the guides for Nexus devices.
Essentially it boils down to this: The factory image contains a few files in an archive format. There are a few images within that you need: bootloader (I can't remember what the name of the file is but it's something like xxxxbootloaderxxx.img), system.img, boot.img, recovery.img). Extract those images from within the archive and flash them. You do this by booting into the bootloader, opening a command prompt in the same folder that you downloaded the image files) on your PC and type the following commands:
fastboot flash bootloader bootloader.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot format cache
If you also want to start fresh and wipe all your data, execute the following command: fastboot format userdata
Then execute: fastboot reboot
Done.
Notes:
1) You need to extract these files in the same directory as where you downloaded the images before proceeding.
2) if you are using Windows, you need to install the the driver (found here: http://developer.android.com/sdk/win-usb.html)
3) The procedure above assumes your bootloader is unlocked. If not, you will need to unlock it (using: fastboot oem unlock) and it will wipe all your data.
efrant said:
1) There is currently no way to get root on 5.1.1 without modifying the kernel (so that it boots SELinux in permissive mode).
Click to expand...
Click to collapse
??
I have root on my NP... I used SkipSoft's Toolkit - details are here: http://forum.xda-developers.com/nexus-6/orig-development/toolkit-skipsoft-unified-android-t2967053
etnpnys said:
??
I have root on my NP... I used SkipSoft's Toolkit - details are here: http://forum.xda-developers.com/nexus-6/orig-development/toolkit-skipsoft-unified-android-t2967053
Click to expand...
Click to collapse
You are correct. I was reading another thread talking about Android M, and then I replied to this thread, so my mistake.
I've edited my post.
efrant said:
You are correct. I was reading another thread talking about Android M, and then I replied to this thread, so my mistake.
I've edited my post.
Click to expand...
Click to collapse
Ok - whew! I know that I went through the process but I couldn't be 100% sure because I have tried so many things to get expanded storage working to no avail that I've kinda given up for the time being...
It's a nexus - use custom recovery to flash supersu and your rooted.... Done
Toneman07 said:
It's a nexus - use custom recovery to flash supersu and your rooted.... Done
Click to expand...
Click to collapse
Not necessarily... You still need a modified boot.img to get the whole thing working...
etnpnys said:
Not necessarily... You still need a modified boot.img to get the whole thing working...
Click to expand...
Click to collapse
Thats interesting considering both my nexus phone and samsung tablet are running stock kernels (boot.img) and rooted just fine using the above method.