I have the WiFi version of the Nexus 7 (2013). It is on KTU84P (Android 4.4.4). Bootloader is unlocked, TWRP 2.7.1.1 is installed for recovery and it is rooted.
I downloaded the OTA zip and have tried to install it in 2 different ways:
In TWRP, going to Advanced->ADB Sideload. Then from the connected PC, running "adb sideload <downloaded zip file>"
From TWRP on the device, going to Install, and selecting the downloaded zip.
In both cases, I get the same error:
Package expects build fingerprint of google/razor/flo:4.4.4/KTU84P/1227136:user/release-keys or google/razor/flo:5.0/LRX21P/1570855:user/release-keys; this device has google/razor/flo:4.3/JSS15Q/779366:user/release-keys.
Click to expand...
Click to collapse
I'm not real sure what that error means, or how to go about addressing it. Any suggestions?
Thanks
You can't flash the OTA in TWRP, at least I don't think so, but I do know that 5.0 requires the latest version of TWRP, think it's 2.8.1.0
Sent from my 2013 Nexus 7
"Until death, I will remain a Dirty Unicorn.."
Tried updating to TWRP 2.8.1.0, I couldn't even get adb to recognize the tablet when in sideload. Just gave me device not found.
But, based on your other comment, I grabbed Wug's Nexus Root Toolkit and reflashed the stock recovery. Sideload is now in progress, I think I'm good to go (I probably just jinxed it!)
Thanks a lot for the help. I had thought it would just replace the recovery - I didn't realize that actually prevented it from running.
Update TWRP in bootloader. Fasboot flash recovery recovery.img
cabadam said:
I have the WiFi version of the Nexus 7 (2013). It is on KTU84P (Android 4.4.4). Bootloader is unlocked, TWRP 2.7.1.1 is installed for recovery and it is rooted.
I downloaded the OTA zip and have tried to install it in 2 different ways:
In TWRP, going to Advanced->ADB Sideload. Then from the connected PC, running "adb sideload <downloaded zip file>"
From TWRP on the device, going to Install, and selecting the downloaded zip.
In both cases, I get the same error:
I'm not real sure what that error means, or how to go about addressing it. Any suggestions?
Thanks
Click to expand...
Click to collapse
The error message is simply saying that the file you are trying to flash is to update from 4.4.4 to 5.0. But your device is at 4.3, and so, you cannot flash this file.
You will need to first upgrade to 4.4.4 and then flash from 4.4.4 to 5.0
jj14 said:
The error message is simply saying that the file you are trying to flash is to update from 4.4.4 to 5.0. But your device is at 4.3, and so, you cannot flash this file.
You will need to first upgrade to 4.4.4 and then flash from 4.4.4 to 5.0
Click to expand...
Click to collapse
No, it was at 4.4.4. For some reason it just didn't like TWRP. When I went back to stock recovery, it sideloaded just fine. I'm up and running now on 5.0.
cabadam said:
No, it was at 4.4.4. For some reason it just didn't like TWRP. When I went back to stock recovery, it sideloaded just fine. I'm up and running now on 5.0.
Click to expand...
Click to collapse
Weird - did you modify your build.prop for any reason?
jj14 said:
Weird - did you modify your build.prop for any reason?
Click to expand...
Click to collapse
Nope. When I got the tablet, I rooted it, flashed TWRP, but didn't modify anything else. And basically the root was just so I could do full backups.
I tried twrp amd cwm and both wont work. Twrp shows jelly bean and cwm shows previous version of kitkat. Both are not showing ktu84p
Build fingerprint error when flashing 5.0 OTA via stock recovery
ImjuzCY said:
I tried twrp amd cwm and both wont work. Twrp shows jelly bean and cwm shows previous version of kitkat. Both are not showing ktu84p
Click to expand...
Click to collapse
Hello!
Really want to flash the OTA without a total wipe.
First flashed it from TWRP 2.8.1.0 and got the wrong build finger print says I have Flo:4.3/JSS15Q/779366 and it expects KTU84P/1227136
Then using WugFresh 1.9.4 flashed stock recovery so I could sideload then encountered the whole adb disappearing in recovery - eventually solved that and finally managed to adb sideload saw my screen saying it was installing the update using the stock recovery - YAY! It was short lived as the stock recovery screen told me the exact same thing that TWRP had told me.
I looked at my build.prop and it says my ro.build.fingerprint=google/razor/flo:4.4.4/KTU84P/1227136. user/release-keys
Can someone enlighten me? I've wasted so much time on this I would love some keen insight - PLEASE!!
Thanks for any and all help!
Edbogue
Same problem
Hey guys!
I have the exact same problem as OP.
tried installing the zip using the latest version of TWRP and got the same error as OP.
I reverted back to stock recovery and tried to install the OTA update and I got a similar error (image attached).
I'm stuck, could someone help?
Rooted Nexus 7 2013 running 4.4.4 with TWRP 2.8.1.0
Same here. Build.prop has the desired release keys but cwm is giving me the exact same error. Anyone have any suggestions?
open the zip file,
edit META-INF/com/google/android/updater-script
just comment the following three lines:
#getprop("ro.build.fingerprint") == "google/razor/flo:4.4.4/KTU84P/1227136:user/release-keys" ||
# getprop("ro.build.fingerprint") == "google/razor/flo:5.0/LRX21P/1570855:user/release-keys" ||
# abort("Package expects build fingerprint of google/razor/flo:4.4.4/KTU84P/1227136:user/release-keys or google/razor/flo:5.0/LRX21P/1570855:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
then the update will go through.
you will take this workaround at your own risk.
make sure the version is 4.4.4/KTU84P already.
You need to be in kk stock with all apps from Google. !
I used NRT with sideload and no problem to flash 5.0 !
ahmao said:
open the zip file,
edit META-INF/com/google/android/updater-script
just comment the following three lines:
#getprop("ro.build.fingerprint") == "google/razor/flo:4.4.4/KTU84P/1227136:user/release-keys" ||
# getprop("ro.build.fingerprint") == "google/razor/flo:5.0/LRX21P/1570855:user/release-keys" ||
# abort("Package expects build fingerprint of google/razor/flo:4.4.4/KTU84P/1227136:user/release-keys or google/razor/flo:5.0/LRX21P/1570855:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
then the update will go through.
you will take this workaround at your own risk.
make sure the version is 4.4.4/KTU84P already.
Click to expand...
Click to collapse
ahmao, when you say comment you mean this
Code:
/*comment goes here*/
as they do with CSS?
open the zip file,
edit META-INF/com/google/android/updater-script
just comment the following three lines:
#getprop("ro.build.fingerprint") == "google/razor/flo:4.4.4/KTU84P/1227136:user/release-keys" ||
# getprop("ro.build.fingerprint") == "google/razor/flo:5.0/LRX21P/1570855:user/release-keys" ||
# abort("Package expects build fingerprint of google/razor/flo:4.4.4/KTU84P/1227136:user/release-keys or google/razor/flo:5.0/LRX21P/1570855:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
then the update will go through.
you will take this workaround at your own risk.
make sure the version is 4.4.4/KTU84P already.
Click to expand...
Click to collapse
As suggested, I tried that. Commented out the lines. Now when trying to flash it just says "Installing Update" then "Installation Aborted" gives no further details. Thanks for the suggestion though.
I had same problems on n4.
I tried flashing stock recovery. Doesn't work. So, I flashed the whole stock 4.4.4 rom, and then apply the Ota. And it worked.
But I had to wipe my user data. (maybe not necessary)
Envoyé de ma Nexus 7.2 depuis tapatalk
I finally waved the white flag and used WugFresh's toolkit 1.9.8. Cool thing though. I was planning on using it to restore to stock 4.4.4. When chose the option to Flash Stock it actually downloaded and flashed the lollipop factory image instead of the latest kitkat. Did wipe data as expected with a factory image but still saved a step. Even though the bootloader was updated, it remained unlocked so I was able to immediately root. I am normally not a fan of toolkits and am more inclined to do things myself (with lots of help from forums of course) for educational purposes but I spent 2 days working on it the other way and got it done this way in under an hour.
comment means add a hash "#" in front of the script line.
if further check fails, just find the line and comment out the app_check line.
bwat1009 said:
I finally waved the white flag and used WugFresh's toolkit 1.9.8. Cool thing though. I was planning on using it to restore to stock 4.4.4. When chose the option to Flash Stock it actually downloaded and flashed the lollipop factory image instead of the latest kitkat. Did wipe data as expected with a factory image but still saved a step. Even though the bootloader was updated, it remained unlocked so I was able to immediately root. I am normally not a fan of toolkits and am more inclined to do things myself (with lots of help from forums of course) for educational purposes but I spent 2 days working on it the other way and got it done this way in under an hour.
Click to expand...
Click to collapse
Thanks man!
That worked perfectly!
I lost all my data (which is fine) plus I really needed to start from scratch at some point.
I'm trying to install TWRP custom recovery, but it seems to be crashing all the time.
Does TWRP support Android 5.0 yet?
Related
Hi All,
My Nexus 7 LTE is rooted with TWRP.
I've downloaded the OTA for 4.4.3 from one of the posts in the forums. It updates my razorg from KOT49H to KTU84L.
After using adb sideload, the update zip file is transferred successfully to my device, but it fails with the error message
Code:
"/system/bin/surfaceflinger" has unexpected contents.
error excuting updater binary in zip '/data/media/0/sideload.zip
Does anyone have any idea what could be causing the update to fail?
I've already restored to a stock kernel (from franco kernel) as well as uninstalled xposed framework.
Thanks!
Install stock recovery and take ota as normal. Then reinstall twrp and reroot.
If you fail update I have a backup I made with twrp you can use. Just need to extract it to your twrp backup folder and restore. It's 100% stock and was made after wiping data. Can't post a link to my Dropbox right now because of my post count but if you need it I an send it to you by other means.
Thanks for that. I think I might have to flash stock recovery and give it a shot, although I have a feeling even if I do that, it might not work as my tablet is no longer stock, since I've installed apps which made changes, such as FKU as well as CF-Lumen.
endlesstrail said:
Thanks for that. I think I might have to flash stock recovery and give it a shot, although I have a feeling even if I do that, it might not work as my tablet is no longer stock, since I've installed apps which made changes, such as FKU as well as CF-Lumen.
Click to expand...
Click to collapse
To get the OTA to work with either a stock or custom recovery the unexpected contents error will have to be fixed first. Somehow the surfaceflinger file was changed, that's a new one for me so I have no idea what could have changed it. I could upload a copy of mine if you want to try it but I do have the wifi version and don't know if they are the same. Otherwise you will need to fastboot flash the system image for the version you are running now for the update to work. Instead of doing that I would download the 4.4.3 factory image and extract the radio, system, and boot images and fastboot flash those. The bootloader did not change so that does not need to be flashed. Before flashing the images I would download the newest supersu zip and put it in your device storage, then flash the images, once that is done do not reboot, boot into recovery instead and flash the supersu zip then wipe cache and dalvik then reboot. Should take less than 15 minutes. ; )
You could also flash the factory image but that will install the stock recovery, lose root and completely wipe your device. If you are using windows you can open the flash-all.bat with a text editor like notepad and remove the -w from the text, that will prevent the userdata image from being flashed which wipes your device.
Thanks for your reply, wantabe.
I guessed as much, that if I couldn't figure out what changed the surfaceflinger, I might as well do a complete flash back to stock, which was what I did. Now it's just a matter of flashing back TWRP, restoring all the apps and waiting for 4.4.4 :good:
I've downloaded the ota zip and ready to flash it in twrp. But when I flash it, it shows an error saying my device have wrong build number. I'm very sure that i have kitkat ktu84p but when flashing the ota it says i have the previous jelly bean build which makes my flash unsuccessful. I've also checked build.prop and its also listed there its ktu84p. Whats the problem here and if possible show a solution please
ImjuzCY said:
I've downloaded the ota zip and ready to flash it in twrp. But when I flash it, it shows an error saying my device have wrong build number. I'm very sure that i have kitkat ktu84p but when flashing the ota it says i have the previous jelly bean build which makes my flash unsuccessful. I've also checked build.prop and its also listed there its ktu84p. Whats the problem here and if possible show a solution please
Click to expand...
Click to collapse
See it this thread helps
http://forum.xda-developers.com/nex...-qa/flashing-lollipop-ota-twrp-fails-t2939358
jj14 said:
See it this thread helps
http://forum.xda-developers.com/nex...-qa/flashing-lollipop-ota-twrp-fails-t2939358
Click to expand...
Click to collapse
Thanks for the link. Now i can conclude that the ota doesnt work with custom recoveries. Tried twrp and cwm. Twrp shows jelly bean fingerprints but cwm shows another kitkat fingerprint rather than ktu84p thats suppose to be
ImjuzCY said:
Thanks for the link. Now i can conclude that the ota doesnt work with custom recoveries. Tried twrp and cwm. Twrp shows jelly bean fingerprints but cwm shows another kitkat fingerprint rather than ktu84p thats suppose to be
Click to expand...
Click to collapse
Wonder if you are using an outdated TWRP version. Maybe the newer versions have fixed this
jj14 said:
Wonder if you are using an outdated TWRP version. Maybe the newer versions have fixed this
Click to expand...
Click to collapse
I dont think so cause ive just updated it to 2.8.1.0 which is the newest by now
I tried everything and still get wrong build fingerprint when trying to flash the 5.0
ImjuzCY said:
I dont think so cause ive just updated it to 2.8.1.0 which is the newest by now
Click to expand...
Click to collapse
Hello!
Really want to flash the OTA without a total wipe.
First flashed it from TWRP 2.8.1.0 and got the wrong build finger print says I have Flo:4.3/JSS15Q/779366 and it expects KTU84P/1227136
Then using WugFresh 1.9.4 flashed stock recovery so I could sideload then encountered the whole adb disappearing in recovery - eventually solved that and finally managed to adb sideload saw my screen saying it was installing the update using the stock recovery - YAY! It was short lived as the stock recovery screen told me the exact same thing that TWRP had told me.
I looked at my build.prop and it says my ro.build.fingerprint=google/razor/flo:4.4.4/KTU84P/1227136. user/release-keys
Can someone enlighten me? I've wasted so much time on this I would love some keen insight - PLEASE!!
Thanks for any and all help!
Edbogue
Google changed the way OTAs work in 5.0. You will usually not be able to flash a OTA if your OS is modified. Means no custom recovery or root. You will have to flash your tab back to stock kitkat.
Before it would patch individual file blocks, now it patches the whole system partition as a blob. Read more http://www.androidpolice.com/2014/1...e-means-update-will-fail-system-modified-way/
Workaround that helped me upgrade
Following the steps below seems to have done the trick for me. My issue was that Android 5.0 updates the system partition all in one go now, rather than each file separately. Following those steps will unroot your device but will allow you to install the OTA updates.
So follow these steps to refresh your current Android version (e.g 4.4.4) then use OTA or adb sideload to update to, for example, 5.0.
This will not wipe user data or the cache.
Download the Factory Image for your current version of android from google (4.4.4 most likely)
Extract each level of compressed files until you get to a .zip file (inside will be boot.img, recovery.img, and system.img)
Move these files to your ADB directory (optional step, makes the commands shorter)
make sure your device is connected with working drivers and is in bootloader mode ( adb reboot bootloader )
perform the following commands:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system
fastboot flash system system.img
Finally, (Re)start the system
After this if you want to root and reinstall a custom recovery , follow the normal steps.
I would post my source, but as I only just joined to say what helped me, I'm not allowed to post links I'll just say Google "flashing-a-stock-android-image-without-wiping-user-data" and (as of 19/11/2014) it's the top result.
Please continue here: http://forum.xda-developers.com/nexus-4/help/android-5-0-0-to-5-0-1-update-t2972371#post57515317
Finally finally!!! A fix!
Raingram said:
Download the Factory Image for your current version of android from google (4.4.4 most likely)
Extract each level of compressed files until you get to a .zip file (inside will be boot.img, recovery.img, and system.img)
Move these files to your ADB directory (optional step, makes the commands shorter)
make sure your device is connected with working drivers and is in bootloader mode ( adb reboot bootloader )
perform the following commands:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system
fastboot flash system system.img
Finally, (Re)start the system
After this if you want to root and reinstall a custom recovery , follow the normal steps.
.
Click to expand...
Click to collapse
Thank you Raingram! This worked perfectly!
I'm trying to apply the 5.0.1 LRX22C OTA update file on my Nexus 7 (2013 WiFi), which is currently running 5.0.0 Build LRX21P. I've tried installing the zip through TWRP recovery and by sideloading using the Nexus Root Toolkit from my computer...no luck either way.
Here's the issue I'm running into:
During the OTA zip install process, I get an error saying that the user build on my device is LRX21V, and the update aborts because the package expects build LRX21P. (My device settings say that I'm on LRX21P.) I upgraded to 5.0.0 in the first place by manually installing the OTA zip from build KTU84P. I'm not sure if that has anything to do with the issue, since I did not wait for the OTA to become available when it rolled out to me in the System Update feature (maybe sideloading OTAs triggers my device to load test/interim builds?).
Here's what I get in the TWRP log:
Installing '/sdcard/bc4516eb14461efdfaf309311b1f09328b654012.signed-razor-LRX22C-from-LRX21P.bc4516eb.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
script aborted: Package expects build fingerprint of google/razor/flo:5.0/LRX21P/1570855:user/release-keys or google/razor/flo:5.0.1/LRX22C/1602158:user/release-keys; this device has Android/omni_flo/flo:5.0/LRX21V/dees_troy11241447:eng/test-keys.
Package expects build fingerprint of google/razor/flo:5.0/LRX21P/1570855:user/release-keys or google/razor/flo:5.0.1/LRX22C/1602158:user/release-keys; this device has Android/omni_flo/flo:5.0/LRX21V/dees_troy11241447:eng/test-keys.
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/sdcard/bc4516eb14461efdfaf309311b1f09328b654012.signed-razor-LRX22C-from-LRX21P.bc4516eb.zip'
Error flashing zip '/sdcard/bc4516eb14461efdfaf309311b1f09328b654012.signed-razor-LRX22C-from-LRX21P.bc4516eb.zip'
Click to expand...
Click to collapse
Anyone know how I can get the update to work? I don't want to wipe my device to flash a factory image...it's not that urgent. But if there's a way I can upgrade without waiting for the OTA to rollout to me, that'd be nice.
Thanks for any help!
indiecognition said:
I'm trying to apply the 5.0.1 LRX22C OTA update file on my Nexus 7 (2013 WiFi), which is currently running 5.0.0 Build LRX21P. I've tried installing the zip through TWRP recovery and by sideloading using the Nexus Root Toolkit from my computer...no luck either way.
Here's the issue I'm running into:
During the OTA zip install process, I get an error saying that the user build on my device is LRX21V, and the update aborts because the package expects build LRX21P. (My device settings say that I'm on LRX21P.) I upgraded to 5.0.0 in the first place by manually installing the OTA zip from build KTU84P. I'm not sure if that has anything to do with the issue, since I did not wait for the OTA to become available when it rolled out to me in the System Update feature (maybe sideloading OTAs triggers my device to load test/interim builds?).
Here's what I get in the TWRP log:
Anyone know how I can get the update to work? I don't want to wipe my device to flash a factory image...it's not that urgent. But if there's a way I can upgrade without waiting for the OTA to rollout to me, that'd be nice.
Thanks for any help!
Click to expand...
Click to collapse
Same issue for me, with this strange fingerprint.
I tried to flash it by side load and TWRP 2.8.2.2 with th esame result!:crying:
I was on 5.0 rooted with TWRP and got the same error trying to take the OTA. So I downloaded the rooted rom from Scrosler found here http://forum.xda-developers.com/nexu...rx22c-t2960745 , used Wugfresh's NRT 1.9.9 to update the bootloader, and then dirty flashed (no wipes) the 5.0.1 rom with TWRP. Painless and fast with no loss of data or anything. Seriously easy, guys!
FWIW the Factory Images are a super easy way as well.
I went from 4.4.4 to 5.0 with Factory Images and the -w flag in the batch file removed (to prevent wiping data), then rooted with Chainfire Auto Root (CFAR). Whole process took about 10 minutes (less download time).
I then went from 5.0 to 5.0.1 in the same fashion. I tried to sideload the OTA but it failed verification (/recovery and /system (root, I'm guessing)) so rather than mess with flashing both then doing the OTA, I just downloaded the 5.0.1 factory Factory Image, removed the -w flag again, and took the same steps as above. Ran the batch, ran CFAR and I was done.
Edit: for clarifiaction, I did these like two weeks apart, not back to back. I also did an upgrade for a friend on his N7 and went from 4.4.4 to 5.0.1 with Factory Images exactly as above. Although I didn't remove the -w flag for him because his bootloader was locked, so it was already wiping for that. Flashed Factory Images, ran CFAR, done.
indiecognition said:
I'm trying to apply the 5.0.1 LRX22C OTA update file on my Nexus 7 (2013 WiFi), which is currently running 5.0.0 Build LRX21P. I've tried installing the zip through TWRP recovery and by sideloading using the Nexus Root Toolkit from my computer...no luck either way.
Here's the issue I'm running into:
During the OTA zip install process, I get an error saying that the user build on my device is LRX21V, and the update aborts because the package expects build LRX21P. (My device settings say that I'm on LRX21P.) I upgraded to 5.0.0 in the first place by manually installing the OTA zip from build KTU84P. I'm not sure if that has anything to do with the issue, since I did not wait for the OTA to become available when it rolled out to me in the System Update feature (maybe sideloading OTAs triggers my device to load test/interim builds?).
Here's what I get in the TWRP log:
Anyone know how I can get the update to work? I don't want to wipe my device to flash a factory image...it's not that urgent. But if there's a way I can upgrade without waiting for the OTA to rollout to me, that'd be nice.
Thanks for any help!
Click to expand...
Click to collapse
You can flash the 5.0.1 factory image without wipe (did the same and it works well till now). Just extract system and boot.img, flash them via fastboot, wipe cache and reboot, thats it.
I may have a fix
I was having the same issue on my Nexus 5...(valentine edition ) I recieved the OTA 5.0.1 update and tried to install it automatically. (Not manually) It failed, so once it did i went into Recovery Mode and I cleared my data partition cache and wiped my dalvik cache and once i rebooted i got the "Android is upgrading" screen. I'm assuming this should fix it but I havent finished upgrading to check. Try this and let me know!
Clutchisback said:
I was having the same issue on my Nexus 5...(valentine edition ) I recieved the OTA 5.0.1 update and tried to install it automatically. (Not manually) It failed, so once it did i went into Recovery Mode and I cleared my data partition cache and wiped my dalvik cache and once i rebooted i got the "Android is upgrading" screen. I'm assuming this should fix it but I havent finished upgrading to check. Try this and let me know!
Click to expand...
Click to collapse
"Android is upgrading" after clearing the dalvik cache is normal. It is just optimizing the apps for the runtime.
Well since you have recovery installed, you can try a lot of installations. just don't forget to backup.
fury683 said:
"Android is upgrading" after clearing the dalvik cache is normal. It is just optimizing the apps for the runtime.
Click to expand...
Click to collapse
Yea you were right, it ended up doing nothing... :crying:
Nexus 5 manual download solution
indiecognition said:
I'm trying to apply the 5.0.1 LRX22C OTA update file on my Nexus 7 (2013 WiFi), which is currently running 5.0.0 Build LRX21P. I've tried installing the zip through TWRP recovery and by sideloading using the Nexus Root Toolkit from my computer...no luck either way.
Here's the issue I'm running into:
During the OTA zip install process, I get an error saying that the user build on my device is LRX21V, and the update aborts because the package expects build LRX21P. (My device settings say that I'm on LRX21P.) I upgraded to 5.0.0 in the first place by manually installing the OTA zip from build KTU84P. I'm not sure if that has anything to do with the issue, since I did not wait for the OTA to become available when it rolled out to me in the System Update feature (maybe sideloading OTAs triggers my device to load test/interim builds?).
Here's what I get in the TWRP log:
Anyone know how I can get the update to work? I don't want to wipe my device to flash a factory image...it's not that urgent. But if there's a way I can upgrade without waiting for the OTA to rollout to me, that'd be nice.
Thanks for any help!
Click to expand...
Click to collapse
I finally got the install done manually...I took the liberty of writing up some tips to and solutions to all the problems i encountered, check out my thread here: http://forum.xda-developers.com/goo...al-install-t2978147/post57615642#post57615642
I think you should just be able to just tick "Force Flash" in Wug's NRT and this should fixed the mismatch issue when you flash the images. I think he said in another thread that Google hosed something in their Flash-all.bat file which is causing the issue.
For some reason I'm just not able to Google this answer or find it here on XDA.
I'm on 5.0.1 (LRX22C) and want to go to 5.0.2 (LRX22G). I have downloaded an OTA update capture and tried to adb sideload it.
It failed. After a sec I thought, "duh. I'm rooted with franco kernel installed." I then did the following:
* Used SuperSU to unroot
* Booted to bootloader
* Flashed stock recovery and kernel
* Rebooted to recovery
* Attempted adb sideload again
This still gave a failure message.
The only other post I've seen where anyone is attempting the same suggests to use Nexus Root Tookit. I'm running Xubuntu. I've loaded it through wine but all the files it downloads are failing hash checks (though the app).
Can anyone post how to go from rooted 5.0.1 to 5.0.2 (LRX22G from LRX22C) without loosing user land data? I'd really do not want to flash the recovery image.
Notes: When trying to sideload with latest CWM recovery the script says that I'm on 4.0.4 (I think) and with TWRP it says I'm on 4.3. With stock recovery it gives me an error about the recovery script (7) or something similar.
Thanks,
Mike G.
Make sure you have downloaded the proper OTA for Nexus 7(2013).
Hashcheck fails in Nexus Root Toolkit is common.After Hashfails,there will be a dialog box which contains the steps to do it manually with the Link to the files.Download it & follow the instruction.
I hope this helps
I'm having the exact same problem. I'm attaching what's appearing on TWRP.
All you need to do is flash the boot and system.img
Then flash su from twrp. It's that easy. No data loss.
I just used wugfresh's toolbox to do it. A piece of cake. I enjoyed a cup of coffee while I watched being updated.
You can also use TWRP and dirty flash the stock, rooted rom by Scrolser found here: http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22g-t3004110 . Simple and fast with no data loss.
yosmokinman said:
All you need to do is flash the boot and system.img
Then flash su from twrp. It's that easy. No data loss.
Click to expand...
Click to collapse
So I can just ”fastboot flash system system.img" from the 5.0.2 image and not loose data?
That seems like it would be the easiest. I prefer the adb/fastboot commands as NRT hides what it is doing and I like to know what's going on when I "do something" liken push a button.
Sent from my Nexus 7 using XDA Free mobile app
^Yes. It's a good idea to flash boot as well just to get in the habit of it, it didn't change this time I don't think but I could later. Only flash the bootloader if it's a new version no need otherwise.
I simply ran:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
Done, flash su through twrp to get root back.
You probably don't need to format cache but theres no reason not to and it could save you some trouble.
newkydawg said:
You can also use TWRP and dirty flash the stock, rooted rom by Scrolser found here: http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22g-t3004110 . Simple and fast with no data loss.
Click to expand...
Click to collapse
that worked perfectly for me. thx
mikejr83 said:
I prefer the adb/fastboot commands as NRT hides what it is doing and I like to know what's going on when I "do something" liken push a button.
Click to expand...
Click to collapse
NRT opens a terminal window (a real-time log) and tells you exactly what it's doing while it does its work.
All you need to do is flash the boot and system.img
Then flash su from twrp. It's that easy. No data loss.
Click to expand...
Click to collapse
I have a n7 2013 I have already rooted and installed twrp and SuperSU. I'm currently running 4.4.2 and to update to 5.02. Currently I'm getting the ota update msg for 4.4.3 which I've continued to ignore. With google not messaging me to update to 5.02 makes me think it's required to go to 4.4.3,4.4.4,5,5.02 is that correct? Or can one jump directly to 5.02? I want to keep root and twrp and my existing data I see mentioning of restoring stock recovery first. Why would one do that? What's the point of installing a custom recovery in the first place?
Long time ago I read that ota will work when rooted, but you'll lose root which then can be restored with twrp without losing data. Is that no longer true? Or is it only true of KitKat but not lollipop?
From rooted 6.0, I took the OTA and was stuck. Finally wiped everything and installed 6.0.1 fresh. flashed TWRP and supersu 2.60. But after boot, Supersu says binary needs to be updated - but fails to update.
TWRP works fine. Just can't root 6.0.1 with unlocked bootloader. Can anyone share the supersu that worked for 6.0.1? TIA
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
Root works with supersu version 2.62-3. Thanks
sam298 said:
From rooted 6.0, I took the OTA and was stuck. Finally wiped everything and installed 6.0.1 fresh. flashed TWRP and supersu 2.60. But after boot, Supersu says binary needs to be updated - but fails to update.
TWRP works fine. Just can't root 6.0.1 with unlocked bootloader. Can anyone share the supersu that worked for 6.0.1? TIA
Click to expand...
Click to collapse
That wasn't my experience. I took the 6.0.1 update and it failed. So I ran
Code:
fastboot flash system system.img
fastboot flash boot boot.img
using the system and boot images from the 6.0 update. And then I waited for the OTA again. It installed ok.
Using TWRP I installed SuperSU 2.60 for a systemless root of the boot image. Everything is fine.
i can't even get pass installing twrp. every time i flash twrp in fastboot mode it works but it wipes my entire device. booting into twrp shows "NO OS INSTALLED' and even the sd card storage is wiped. the only way to get it to boot is to flash back 6.0.1 full stock rom. any help???
Try nexus root toolkit.
tomxass said:
Try nexus root toolkit.
Click to expand...
Click to collapse
WugFresh did not work for me, after booting into TWRP and looking for the SuperSU and BusyBox they don not show up. Below is a post I have over on WugFresh Forum.
I’m having the same problem as everyone else. I’m using 6.0.1 MMB29K. It goes through the motions but when TWRP launches the /sdcard directory is empty. However, when I reboot and look at the files using an app called File Manager, I see them in /storage/emulated/0/!ReadyToFlash/Root_Files/. However, if I use a app called Root Browser I see a directory called sdcard and in there is !ReadyToFlash/Root_Files/ so they are being copied to the tablet but when you go into TWRP to install them they can’t be found. I tried to use the app Root Browser and make a directory called kiledl, this failed, probably because I do not have root access. Kind of a catch 22 here. I was just going to copy the files in sdcard to my directory and then try again. NO go!!! Anyone else have any ideas? I seems like this is some sort of permissions issue with the files but only from TWRP. I sure hope someone comes up with an answer, WugFresh and ideas?
tomxass said:
Try nexus root toolkit.
Click to expand...
Click to collapse
same result. twrp installed but can't detect my sd card or any files on the device
Download latest SuperSU 2.62-3.
Root via Nexus root toolkit.
Then copy SuperSu to nexus and flash, supersu not from NRT but downloaded latest 2.62-3, busybox and last rar.
Sorry for my English.
Found a solution, the version of TWRP that WugFresh NRT is using is not compatible with this version of the N7 seems as though these were made with a different MMC memory. Check you this link and download this modified version of TWRP. You can use the NRT Advance Utilities > fastboot flash > recovery > other and then point to this modified version of TWRP and install it. Then you can proceed with the install of SuperSU and BusyBox. They will show up in the !ReadyToFlash/Root_Files/ folder to install.
Check this link **UPDATE** Mounting Errors in Custom Recovery
**UPDATE** Mounting Errors in Custom Recover… | Nexus 7 (2013)
dlkile said:
Found a solution, the version of TWRP that WugFresh NRT is using is not compatible with this version of the N7 seems as though these were made with a different MMC memory. Check you this link and download this modified version of TWRP. You can use the NRT Advance Utilities > fastboot flash > recovery > other and then point to this modified version of TWRP and install it. Then you can proceed with the install of SuperSU and BusyBox. They will show up in the !ReadyToFlash/Root_Files/ folder to install.
Check this link **UPDATE** Mounting Errors in Custom Recovery
**UPDATE** Mounting Errors in Custom Recover… | Nexus 7 (2013)
Click to expand...
Click to collapse
noooo. That's not true. I just used NRT yesterday to upgrade to rooted 6.01.
EDIT: I think I misundersstood your post. This is only a problem if you try to install TWRP when upgrading right? If you just want to upgrade to 6.01 and keep stock recovery there is no issue.
aiiee said:
noooo. That's not true. I just used NRT yesterday to upgrade to rooted 6.01.
EDIT: I think I misundersstood your post. This is only a problem if you try to install TWRP when upgrading right? If you just want to upgrade to 6.01 and keep stock recovery there is no issue.
Click to expand...
Click to collapse
Yes it is true, it depends on what kind of eMMC chip is in it. I have a very new device and NRT would not root it. When it booted in TWRP it could not see the !ReadyToFlash/Root_Files/ folder to install the files. There was no files on SDCard at all unless you booted to Android to verify they were in fact there. I had to install the modified Recovery TWRP file first. Saying "noooo. That's not true." is a little harsh, kinda make me a liar, I think NOT. Just because the method worked for you does not mean it worked for me. Not all devices are the same. If you read other post here you will see lots of others are having the same problem.
aiiee said:
EDIT: I think I misundersstood your post. This is only a problem if you try to install TWRP when upgrading right? If you just want to upgrade to 6.01 and keep stock recovery there is no issue.
Click to expand...
Click to collapse
Correct only when using TWRP. However, I was using WugFresh NRT and it does a temporary install of TWRP then you install the SuperSU and BusyBox files. However, with the wrong version of TWRP you would not see the files in the SDCard folder, it would be empty. However, booting back to Android and using File Explorer the files where there. Using the modified version of TWRP would correct this.
interesting. i was wondering why some persons say it work and when i tried it, it wouldn't show anything in twp. can you point me to the link of the modified/correct version of twrp to use or help me by saying what to search. i don't want to sound lazy bu asking you for the link but i'm not sure as to what to google exactly to find the correct twrp to use. obviously i've been google wrong the pass few days because that hasn't come up for me in any of my past searches
Update: i found it and it works. thanks guys. now i can flash some custom roms. gonna try cm 13 tonight. thanks again
r.sorujlall said:
interesting. i was wondering why some persons say it work and when i tried it, it wouldn't show anything in twp. can you point me to the link of the modified/correct version of twrp to use or help me by saying what to search. i don't want to sound lazy bu asking you for the link but i'm not sure as to what to google exactly to find the correct twrp to use. obviously i've been google wrong the pass few days because that hasn't come up for me in any of my past searches
Update: i found it and it works. thanks guys. now i can flash some custom roms. gonna try cm 13 tonight. thanks again
Click to expand...
Click to collapse
Yes, here is the link you need to select the LTE or WiFi version depending on you device. I do not have enough post to be able post links, so try removing the "*" from the link below.
forum*.xda-developers*.com/nexus*-7-2013/nexus*-7-2013-qa/mount*-recovery*-t3064562
dlkile said:
Yes it is true, it depends on what kind of eMMC chip is in it. I have a very new device and NRT would not root it. When it booted in TWRP it could not see the !ReadyToFlash/Root_Files/ folder to install the files. There was no files on SDCard at all unless you booted to Android to verify they were in fact there. I had to install the modified Recovery TWRP file first. Saying "noooo. That's not true." is a little harsh, kinda make me a liar, I think NOT. Just because the method worked for you does not mean it worked for me. Not all devices are the same. If you read other post here you will see lots of others are having the same problem.
Click to expand...
Click to collapse
I sit corrected, sir. :good:
Just for my own edumacation, how old is your N7? I just bought two from Groupon and I wonder if they are affecteed? How can one tell ?
aiiee said:
I sit corrected, sir. :good:
Just for my own edumacation, how old is your N7? I just bought two from Groupon and I wonder if they are affecteed? How can one tell ?
Click to expand...
Click to collapse
You most have the same unit as I do. I just got mine a week ago from GroupOn as well.
i bought mine about a week ago off amazon. i had a gift card and had nothing to buy so i decided to get the N7 and give it a try