Develop Bugs

[Q] Issue upgrading from 5.0.0 to 5.0.1 on Nexus 7 (2013 WiFi)

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.

Recovery can't find any file, can't install any zip file

After I got my nexus 5x, I unlocked bootloader and root, and finally I go back official stock 6.0.1. But the camera didn't work fine(sometimes black screen, and then phone reboot). Have to flash CM13.
Following the guide, I did those steps strictly. Yet failed.
- When I tried to install CM13.zip, the TWRP told me I had to decrypt , and need to enter the default password which I don't know/have.
- I tried another way, flash official recovery.img . Failed again: the official recovery told me "can't mount SDcard", update zip file from sd card failed.
How can I install CM13 now? Or, how can I solved the camera issue?
I feel terrible about this, could you guys help?
thank you

faytuu said:
After I got my nexus 5x, I unlocked bootloader and root, and finally I go back official stock 6.0.1. But the camera didn't work fine(sometimes black screen, and then phone reboot). Have to flash CM13.
Following the guide, I did those steps strictly. Yet failed.
- When I tried to install CM13.zip, the TWRP told me I had to decrypt , and need to enter the default password which I don't know/have.
- I tried another way, flash official recovery.img . Failed again: the official recovery told me "can't mount SDcard", update zip file from sd card failed.
How can I install CM13 now? Or, how can I solved the camera issue?
I feel terrible about this, could you guys help?
thank you
Click to expand...
Click to collapse
Update TWRP to 3.0.0-1
You can't flash anything worth flashing with stock recovery.
Make sure you are using the latest stock version "J" as it has alot of fixes for this like the camera error.

Darke5tShad0w said:
Update TWRP to 3.0.0-1
You can't flash anything worth flashing with stock recovery.
Make sure you are using the latest stock version "J" as it has a lot of fixes for this like the camera error.
Click to expand...
Click to collapse
Thanks for your reply. I will try TWRP 3.0.0.1 for bullhead
Yes, I'm using the MHC19J build. I still got the camera issue, and tired for that (this is the reason why I want flashing CM13). Do I need to format userdata while I always get the red warning at booting ?

SOLVED http://forum.xda-developers.com/nexus-5x/general/learn-using-nexus-5xwith-official-stock-t3342616

Oneplus 3 soft bricked. Attempted flashing ROM with twrp and Stock recovery!

Hello please help. So I unlocked bootloader, set up Google and finger scanning password. Flashed SuperSU and that's when everything went wrong. Got stuck on the boot logo. Any suggestions? I've read about using the Qualcomm driver method but I'm unsure if it'll work on a Mac? Any help ? I've used twrp to flash ROM no luck. Used stock recovery but adb doesn't detect my devices I guess I didn't enable USB debugging after unlocking the bootloader.

jasj0410 said:
Hello please help. So I unlocked bootloader, set up Google and finger scanning password. Flashed SuperSU and that's when everything went wrong. Got stuck on the boot logo. Any suggestions? I've read about using the Qualcomm driver method but I'm unsure if it'll work on a Mac? Any help ? I've used twrp to flash ROM no luck. Used stock recovery but adb doesn't detect my devices I guess I didn't enable USB debugging after unlocking the bootloader.
Click to expand...
Click to collapse
Flashing the stock firmware using TWRP should do it for you. Just perform a FULL WIPE (formatting all partitions) before flashing the rom and keep in mind that you need a modified TWRP version to flash Oxygen OS based roms. The official TWRP won't do it.

Can you explain what you mean by "formatting all partitions"?
I have a modified twrp recovery. When I click on wipe there is two options " advance wipe" and "format data" is the 2nd optioption the one your referring too as well? I flashed ROM.zip with the modified twrp without formatting data (I rather wait on your reply to be sure) and instead of getting stuck on the boot logo it is doing a bootloop now. Thanks for your assistance BTW.

jasj0410 said:
Can you explain what you mean by "formatting all partitions"?
I have a modified twrp recovery. When I click on wipe there is two options " advance wipe" and "format data" is the 2nd optioption the one your referring too as well? I flashed ROM.zip with the modified twrp without formatting data (I rather wait on your reply to be sure) and instead of getting stuck on the boot logo it is doing a bootloop now. Thanks for your assistance BTW.
Click to expand...
Click to collapse
Advanced Wipe
--> mark
"ART Cache"
"Cache"
"Data"
"Internal Storage"
"System"
--> swipe to wipe
If you don't get any errors
--> restart TWRP (Or you can't access the storage)
--> flash rom

Did that no luck. I'm trying to flash 3.2.7 anything tricky/specific I should be doing ?
I'm going to flash 3.2.6 tomorrow when I get near Wi-Fi and See what happens.
Should I be downloading "OTA zip" or" oxygenOS 3.2.6 full zip"

jasj0410 said:
Did that no luck. I'm trying to flash 3.2.7 anything tricky/specific I should be doing ?
I'm going to flash 3.2.6 tomorrow when I get near Wi-Fi and See what happens.
Should I be downloading "OTA zip" or" oxygenOS 3.2.6 full zip"
Click to expand...
Click to collapse
OTA = on the air update // for upgrading your android version e.g. OOS 3.2.6 --> 3.2.8 // NOT for solo installation!
You can either use OOS 3.2.6 or the very awesome Open Beta 7 (Don't be irritated because there is "OTA" in the filename, both are complete roms)
These are full roms officially from OnePlus.net and I'm pretty sure that they will work together with TWRP 3.0.2-22.
I suppose you simply used the wrong files. Could you tell me where you downloaded the files?

LS.xD said:
OTA = on the air update // for upgrading your android version e.g. OOS 3.2.6 --> 3.2.8 // NOT for solo installation!
You can either use OOS 3.2.6 or the very awesome Open Beta 7 (Don't be irritated because there is "OTA" in the filename, both are complete roms)
These are full roms officially from OnePlus.net and I'm pretty sure that they will work together with TWRP 3.0.2-22.
I suppose you simply used the wrong files. Could you tell me where you downloaded the files?
Click to expand...
Click to collapse
i literally downloaded those files you linked to me and still no luck. it shouldn't be a problem that I'm using android file manager to transfer the rom over to my phone right? I'm going to wipe everything and go to stock recovery and use adb push to flash stock rom. any other suggestions you got?

Anyone please? I've rooted moto g 1st and 4th grn so it's not the fact that I'm being a complete noob. I've downloaded the modified twrp flashed 3.2.6, beta 7 and cyanogenmod. No luck on anything.

jasj0410 said:
Anyone please? I've rooted moto g 1st and 4th grn so it's not the fact that I'm being a complete noob. I've downloaded the modified twrp flashed 3.2.6, beta 7 and cyanogenmod. No luck on anything.
Click to expand...
Click to collapse
Use this guide and try both methods.
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700

tnsmani said:
Use this guide and try both methods.
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Click to expand...
Click to collapse
thanks for your reply. i managed to fix it. the other guy's link for a modified twrp didn't work (the custom recovery not the link) so i downloaded another and ended up installing beta 7 which worked. for future reference the link (mega unbrick) you provided me would that work with a mac?

jasj0410 said:
thanks for your reply. i managed to fix it. the other guy's link for a modified twrp didn't work (the custom recovery not the link) so i downloaded another and ended up installing beta 7 which worked. for future reference the link (mega unbrick) you provided me would that work with a mac?
Click to expand...
Click to collapse
I doubt that though there is no specific info on this .

can't update to oxygenOS beta 25 or 26

hi, i've never had probem updating my phone to oxygenOS. however the last 2 updates won't work : twrp says "zip signature verification failed error installing zip file" and even when i download and launch the OTA it does the same.
do you have an answer that doesn't envolve factory reseting of the phone?

bigben14 said:
hi, i've never had probem updating my phone to oxygenOS. however the last 2 updates won't work : twrp says "zip signature verification failed error installing zip file" and even when i download and launch the OTA it does the same.
do you have an answer that doesn't envolve factory reseting of the phone?
Click to expand...
Click to collapse
And manually re-downloading doesn't solve the issue?

Puddi_Puddin said:
And manually re-downloading doesn't solve the issue?
Click to expand...
Click to collapse
i've tried to download the beta 25 and 26 manually and flashed it with twrp and i've tried to update with the OTA of both version and none of thoses methodes worked

bigben14 said:
i've tried to download the beta 25 and 26 manually and flashed it with twrp and i've tried to update with the OTA of both version and none of thoses methodes worked
Click to expand...
Click to collapse
Make sure you are on the right version of twrp (latest). Take a backup of system and boot, then wipe system and flash the zip and see if it works. If it doesn't just revert system and you are back to normal.

Puddi_Puddin said:
Make sure you are on the right version of twrp (latest). Take a backup of system and boot, then wipe system and flash the zip and see if it works. If it doesn't just revert system and you are back to normal.
Click to expand...
Click to collapse
hi,
i am on the latest version of twrp and i tried what you told me, still doesn't work.
any ideas of the origin of the problem? any other ideas on how to fix it?

bigben14 said:
hi,
i am on the latest version of twrp and i tried what you told me, still doesn't work.
any ideas of the origin of the problem? any other ideas on how to fix it?
Click to expand...
Click to collapse
Perhaps this version requires a clean install? I havent really been on OOS. What is new in Open Beta 25?

Puddi_Puddin said:
Perhaps this version requires a clean install? I havent really been on OOS. What is new in Open Beta 25?
Click to expand...
Click to collapse
the open beta is the oreo one. but i just checked and tried to install some other zips (a bootloader and akt) and the same problem happens

Puddi_Puddin said:
Perhaps this version requires a clean install? I havent really been on OOS. What is new in Open Beta 25?
Click to expand...
Click to collapse
i think that i found the problem, but i have no idea as how to fix it : when i install the rom, the installer tells me : Warning : No file_contexts E3004: This package is for "OnePlus 3" devices;this device is a "".

bigben14 said:
i think that i found the problem, but i have no idea as how to fix it : when i install the rom, the installer tells me : Warning : No file_contexts E3004: This package is for "OnePlus 3" devices;this device is a "".
Click to expand...
Click to collapse
Hmm, try to wipe system and flash the OOS version you are currently on. That should overwrite the system partition and perhaps fix this issue.

Twrp OREO or
https://forum.xda-developers.com/showpost.php?p=74152902&postcount=3504
or
blu spark v.50 by eng stk.
https://forum.xda-developers.com/devdb/project/?id=15934#downloads

Unofficial Lineage 15.1 Rom Update Fails

Anyone on the above rom having trouble with update?? I use the rom updater on the phone and it showed a new update for 8-12-18 I've downloaded the file twice with the same outcome, pops up an error that just says install error?? Any of the updates before that installed fine..

blake .l said:
Anyone on the above rom having trouble with update?? I use the rom updater on the phone and it showed a new update for 8-12-18 I've downloaded the file twice with the same outcome, pops up an error that just says install error?? Any of the updates before that installed fine..
Click to expand...
Click to collapse
Download and install with twrp. If that build has treble and the one you're using doesn't, you need to flash with twrp for it to change OEM to vendor which the installer cannot do in boot time. It can be dirty flashed if the keys are the same. (I.E. test key to test key. If its from the same source, it is the same)

Uzephi said:
Download and install with twrp. If that build has treble and the one you're using doesn't, you need to flash with twrp for it to change OEM to vendor which the installer cannot do in boot time. It can be dirty flashed if the keys are the same. (I.E. test key to test key. If its from the same source, it is the same)
Click to expand...
Click to collapse
I got the file downloaded but when I go into TWRP and try to install I get this error.
Error applying update: 7 (ErrorCode: :
kInstallDeviceOpenError)
Update process ended with ERROR: 1

blake .l said:
I got the file downloaded but when I go into TWRP and try to install I get this error.
Error applying update: 7 (ErrorCode: :
kInstallDeviceOpenError)
Update process ended with ERROR: 1
Click to expand...
Click to collapse
Try with https://androidfilehost.com/?fid=3700668719832238233

Uzephi said:
Try with https://androidfilehost.com/?fid=3700668719832238233
Click to expand...
Click to collapse
Worked like a charm, Thanks!!

crazy question, how do i install magisk now? I've tried it with the older twrp i was using and I've tried it with the newer version twrp you suggested and i get boot loop now. I tried with the lineage recovery and it fails?