Related
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?
[Q] Need help in solving "Unfortunately, settings have stopped working" error
Problem: My unrooted SGH-I747 model AT&T GS3 recently gave me this error whenever trying to access the settings. The error shows up even after a full factory reset and I can no longer access my phone. Stuck a little after the language selection in the beginning stages of the setup.
Attempted fixes: Obviously, the initial factory reset. Then clearing the cache + factory reset.
After those failed to work, I tried to flash to a AT&T stock rom from this forum (http://forum.xda-developers.com/showthread.php?p=33570269#post33570269) using Odin. I tried to use the first row of downloads but the first row but it did not have a MD5 file, so I used the second row of downloads instead but this rom failed to install. My guess is that it may be too old of a version.
I would appreciate any help.
[SOLVED]
The problem may have arose from a critical error in the phone's software that had affected the OS system of the phone. I resolved the issue by flashing a new custom OS (cyanogenmod) to my phone. These are the steps that I took:
1. Installing Odin (http://forum.xda-developers.com/showthread.php?t=1722686)
2. Rooting my cellphone with CFAutoRoot using Odin (http://forum.xda-developers.com/showthread.php?t=1725839)
3. Installing a custom recovery TWRP -- highly recommended very user friendly (http://forum.xda-developers.com/showthread.php?t=1793224)
4. Installing a new custom rom through TWRP-- used Cyanogen (http://forum.xda-developers.com/showthread.php?t=1778270)
5. Installing gapps (http://opengapps.org/?api=5.1&variant=nano)
6. Identifying the correct bootloader by downloading and installing Samsung Phone Info by vndnguyen through the Play Store.
7. Installing the correct bootloader and modem (http://forum.xda-developers.com/galaxy-s3-att/general/rooted-ucufnj1-stock-rom-t2985006)
Please refer to respective installation guides for more instructions regarding installation of any new software.
I hope this helps anyone who may have run into the same problem.
Before attempting to flash anything, confirm the bootloader on your phone. An easy way to determine if the bootloader is 4.3 or newer, boot into download mode. If you see anything about warranty bit, your phone has at least a 4.3 bootloader and no attempts should be made to flash anything from sammobile.com.
If you have a 4.3 or newer bootloader, I recommend flashing a custom recovery such as TWRP, and then flashing a stock ROM from recovery.
First off, thank you for the reply audit!
Now I have officially rooted my phone using CF-Autoroot and have installed TWRP. I have also confirmed that the bootloader is at least 4.3 because it does show the warranty bit.
Which of the stock roms are compatible with this bootloader?
Do you want to stay on a stock ROM? If not, you could flash a custom ROM such as cm12.1 using TWRP. Once you have flashed a custom ROM, you can look under settings to determine the baseband on the phone which is another clue as to which bootloader is on your phone.
audit13 said:
Do you want to stay on a stock ROM? If not, you could flash a custom ROM such as cm12.1 using TWRP. Once you have flashed a custom ROM, you can look under settings to determine the baseband on the phone which is another clue as to which bootloader is on your phone.
Click to expand...
Click to collapse
Just to be clear, cm12.1 is the cyanogenMod nightly?
Yup. If you flash it, your baseband may be unknown which tells me you are probably not running a 4.4.2 bootloader and modem.
audit13 said:
Yup. If you flash it, your baseband may be unknown which tells me you are probably not running a 4.4.2 bootloader and modem.
Click to expand...
Click to collapse
I'll try it out and see if I can get past the language screen this time.
Got the latest Cyanogenmod Zip file onto my phone. Tried flashing it through TWRP with the install option but it failed.
Log reads that no MDS file was found, detected filesystem ext4 for /dev/block/platform msm_sdcc.1/byname system. Can't install this package on top of incompatible data.
CM12.1 won't have an md5 file. You're trying to install cm12.1 for the d2att or d2lte? You're running the latest TWRP which I believe is 2.8.7.0? or 2.8.7.1?
5K posts.
"all i can really do , is stay out of my own way and let the will of heaven be done"
I'm pretty sure that CM de-unified the variants for CM 12.
From: https://wiki.cyanogenmod.org/w/D2lte_Info
Note: Unified device
Between the release of CM 11 M3 and CM11 M12, all Qualcomm-based variants of this device were merged into a single build: d2lte. The device information pages for the individual variants should be used to reference any device-specific unlock instructions, download recoveries, to build CM 10.2, or to install CM 12.1: d2att, d2cri, d2mtr, d2spr, d2tmo, d2usc, d2vzw.
Click to expand...
Click to collapse
I think this was just to make searching a bit harder/ more complicated.
audit13 said:
CM12.1 won't have an md5 file. You're trying to install cm12.1 for the d2att or d2lte? You're running the latest TWRP which I believe is 2.8.7.0? or 2.8.7.1?
Click to expand...
Click to collapse
For d2att and running 2.8.7.0 for TWRP.
You should be good then.
The file should be left unzipped/unrared when using it right? I'm using it as such but it keeps returning the same error message saying that it won't install it.
Yes, leave it zipped. What is the TWRP error message?
The error log:
detected filesystem ext4 for /dev/block/platform msm_sdcc.1/byname system.
Can't install this package on top of incompatible data.
Please try another package or run a factory reset
E: Error executing updater binary in zip '/sdcard/Download/cm-12.12015913-NIGHTLY-dtatt.zip
Error flashing zip '/sdcard/Download/cm-12.120150913-NIGHTLY-D2att.zip
Weird, did you do a full wipe before trying to install?
Can't believe it was that simple. I thought I had already made the wipe when I did it with the original recovery but making a second wipe through TWRP actually helped make it happen. I finally got through and have full access to my phone.
Unfortunately, the cell service doesn't seem to work but I'm guessing that I need to do more for the set up?
Edit: Not recognizing the sim card for some reason
Sounds like you need to update the bootloader and modem to the older KK version which I think is ne4.
Sorry for the late reply I've been busy the past week. I'm guessing the modem won't work without the proper bootloader? I've tried flashing the latest and original modem from the Modem list (http://forum.xda-developers.com/showthread.php?t=1831898). While they installed successfully I still don't get a signal.
I was worried which bootloader to take because it may lead to bricking. Which one are you referring to and are they in the Bootloader updates topic here? (http://forum.xda-developers.com/showthread.php?t=2321310)
Hi guys,
As soon as I got the OP3 in July, I somehow managed to successfully perform all the steps to get it rooted. I was running OnePlus3Oxygen_16_OTA_013_all_1608061823_765c081a5c8e4dad.zip
OnePlus has been showing me a "new version available" since September, but I very patiently and calmly didn't install it OTA because I didn't want to lose the root.
Finally had a bit of time today, decided I'd finally upgrade. Looked around for the "most recent stable version" and picked this one: OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2af7.zip
Followed the steps for flashing using TWRP (twrp-3.0.2-1.28-oneplus3) here:
https://forum.xda-developers.com/oneplus-3/how-to/oxygenos-4-0-android-nougut-official-t3529684
It worked. Yay. Then (god dammit **** ****) I still saw this "new version available" and couldn't swipe it away... I accidentally clicked it and it downloaded the OTA. Fine.
Now I'm stuck in a TWRP boot loop. I tried re-installing the OTA_035.zip from TWRP -- I tried restoring my Nandroid Backup (only had enough room to save "Boot / Recovery / System" partitions, NOT data) -- and I tried ADB Sideloading 16_OTA_013.zip.
I'm stuck rebooting in TWRP 3.0.2-1.
Is there anything I can try before going ballistic and wiping my data?
Thanks.
Marc
Have you tried the newest blu-spark twrp? https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Puddi_Puddin said:
Have you tried the newest blu-spark twrp? https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Click to expand...
Click to collapse
Hey Puddi_Puddin, thanks for replying.
I never heard of blu-spark, but gave it a shot. Even though the guide seems to apply only to OP3T: https://forums.oneplus.net/threads/...-or-custom-recovery-without-data-loss.479265/
Anyways I flashed blu-spark with ADB. Booted into blu-spark. Wiped Dalvik/Cache, re-installed OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2af7.zip, wiped Dalvik/Cache, rebooted -- keeps booting into blu-spark TWRP.
Get the "device unlocked" error screen, then the dm-verity error screen, then the OnePlus logo for about 2 seconds, and then back to blu-spark. Repeat ad nauseum.
What state is my device even in? I wouldn't call it bricked... I assume it's still rooted, bootloader works, I can flash different TWRP versions, ...
Any other ideas ... ?
Zingapuro said:
Hey Puddi_Puddin, thanks for replying.
I never heard of blu-spark, but gave it a shot. Even though the guide seems to apply only to OP3T: https://forums.oneplus.net/threads/...-or-custom-recovery-without-data-loss.479265/
Anyways I flashed blu-spark with ADB. Booted into blu-spark. Wiped Dalvik/Cache, re-installed OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2af7.zip, wiped Dalvik/Cache, rebooted -- keeps booting into blu-spark TWRP.
Get the "device unlocked" error screen, then the dm-verity error screen, then the OnePlus logo for about 2 seconds, and then back to blu-spark. Repeat ad nauseum.
What state is my device even in? I wouldn't call it bricked... I assume it's still rooted, bootloader works, I can flash different TWRP versions, ...
Any other ideas ... ?
Click to expand...
Click to collapse
After you've flashed the full zip, flash also the latest stable version of SuperSu (2.79) and latest TWRP from @eng.stk (the v11, it solves the dm-verity error). Then reboot to recovery, it should appear TWRP and the error should't appear.
Zingapuro said:
Hey Puddi_Puddin, thanks for replying.
I never heard of blu-spark, but gave it a shot. Even though the guide seems to apply only to OP3T: https://forums.oneplus.net/threads/...-or-custom-recovery-without-data-loss.479265/
Anyways I flashed blu-spark with ADB. Booted into blu-spark. Wiped Dalvik/Cache, re-installed OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2af7.zip, wiped Dalvik/Cache, rebooted -- keeps booting into blu-spark TWRP.
Get the "device unlocked" error screen, then the dm-verity error screen, then the OnePlus logo for about 2 seconds, and then back to blu-spark. Repeat ad nauseum.
What state is my device even in? I wouldn't call it bricked... I assume it's still rooted, bootloader works, I can flash different TWRP versions, ...
Any other ideas ... ?
Click to expand...
Click to collapse
There are quite a few versions of TWRP from eng.stk (bluspark). Which one did you install? Try version 11 which is supposedly for N or 3.0.2-19 or 23.
Thanks for your help everyone.
I downloaded SuperSU-v2.79 here http://downloadmirror.co/Utz/UPDATE-SuperSU-v2.79-20161211114519.zip
I flashed both ZIPs OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2 and UPDATE-SuperSU-v2.79-20161211114519.zip
I confirm I'm using twrp-3.0.2-0_blu_spark_v11-op3.img (from the link provided by Puddi_Puddin)
Still see dm-verity error ... still keeps booting into blu_spark TWRP. :crying:
Zingapuro said:
Thanks for your help everyone.
I downloaded SuperSU-v2.79 here http://downloadmirror.co/Utz/UPDATE-SuperSU-v2.79-20161211114519.zip
I flashed both ZIPs OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2 and UPDATE-SuperSU-v2.79-20161211114519.zip
I confirm I'm using twrp-3.0.2-0_blu_spark_v11-op3.img (from the link provided by Puddi_Puddin)
Still see dm-verity error ... still keeps booting into blu_spark TWRP. :crying:
Click to expand...
Click to collapse
Try the other two given by me.
Zingapuro said:
Thanks for your help everyone.
I downloaded SuperSU-v2.79 here http://downloadmirror.co/Utz/UPDATE-SuperSU-v2.79-20161211114519.zip
I flashed both ZIPs OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2 and UPDATE-SuperSU-v2.79-20161211114519.zip
I confirm I'm using twrp-3.0.2-0_blu_spark_v11-op3.img (from the link provided by Puddi_Puddin)
Still see dm-verity error ... still keeps booting into blu_spark TWRP. :crying:
Click to expand...
Click to collapse
From where have you dowloaded the OTA? XDA or OnePlus forum?
I saw a thread regarding the OnePlus 3T update some post above, if you've downloaded from there you've made a mistake if you own a OnePlus 3.
tnsmani said:
Try the other two given by me.
Click to expand...
Click to collapse
You mean 3.0.2-19 or 23. Not blu_spark, right? Ok I tried twrp-3.0.2-23-oneplus3.img from here (https://www.androidfilehost.com/?fid=529152257862684308)
I tried flashing my old images I used last year (I just wanted the phone to boot into *something*) Oxygen_16_OTA_013 & SuperSU-v2.74. Managed to boot. Updated 4 Apps (??) But as soon as the login screen came up, it would reboot ... and keep looping. So I couldn't use the phone, but at least I managed to boot into something other than TWRP.
Next I tried to reinstall OOS4, 16_OTA_035 with SuperSU-v2.79 SR2. Still get the verity error, but at least I managed to boot! But - the phone is *super* buggy/unusable... SIM cards aren't working - I can't access my options screen - and "Developer options are not available for this user".
Now from my "About" screen I have OOS 4.0, Android 7.0, Kernel version 3.18.31-perf+ [email protected] <-- (that's from my TWRP version. right?)
Did the OTA I install from OnePlus directly screw everything up? For that brief moment before I installed it, I tasted a seemingly properly working OOS 4, so I know it's possible...
A few lessons I've learned are -- I can use any recovery (TWRP) to use MTP and flash files and stuff... but in order for the phone to work properly, I have to a) flash the SuperSU (not just the ROM) and b) make sure I have the "correct/proper" TWRP (kernel?) matched with each ROM. Is that kind of right? That's where I'm stuck I guess.
let92 said:
From where have you dowloaded the OTA? XDA or OnePlus forum?
I saw a thread regarding the OnePlus 3T update some post above, if you've downloaded from there you've made a mistake if you own a OnePlus 3.
Click to expand...
Click to collapse
I downloaded from here
https://forum.xda-developers.com/oneplus-3/how-to/oxygenos-4-0-android-nougut-official-t3529684
I'm sure I'm making a ton of mistakes -- that's why I'm here
(I read here https://forum.xda-developers.com/on...mple-trick-t3530685/post70415499#post70415499 that .28 shouldn't be used)
This post mentions a procedure to get rid of verity https://forum.xda-developers.com/oneplus-3/how-to/fix-device-mapper-verity-simple-trick-t3530685
I'm currently backing up my data, and I'll attempt to follow these instructions to switch to f2fs (hopefully get rid of the verity error) and install OxygenOS 4.0.1 (http://otafsc.h2os.com/patch/amazon...n_16_OTA_037_all_1701041839_aa64b084a40a4.zip)
I'm also a bit confused about the best version of SuperSU-v2.79 to use, because blu_spark was writing somewhere (can't find where) that SR1 and SR2 were the cause of battery issues ... So yeah, I've got other things to try, but should the ROM from OOS4.0.1 work with any of them?
THANKS.
Zingapuro said:
You mean 3.0.2-19 or 23. Not blu_spark, right? Ok I tried twrp-3.0.2-23-oneplus3.img from here (https://www.androidfilehost.com/?fid=529152257862684308)
I tried flashing my old images I used last year (I just wanted the phone to boot into *something*) Oxygen_16_OTA_013 & SuperSU-v2.74. Managed to boot. Updated 4 Apps (??) But as soon as the login screen came up, it would reboot ... and keep looping. So I couldn't use the phone, but at least I managed to boot into something other than TWRP.
Next I tried to reinstall OOS4, 16_OTA_035 with SuperSU-v2.79 SR2. Still get the verity error, but at least I managed to boot! But - the phone is *super* buggy/unusable... SIM cards aren't working - I can't access my options screen - and "Developer options are not available for this user".
Now from my "About" screen I have OOS 4.0, Android 7.0, Kernel version 3.18.31-perf+ [email protected] <-- (that's from my TWRP version. right?)
Did the OTA I install from OnePlus directly screw everything up? For that brief moment before I installed it, I tasted a seemingly properly working OOS 4, so I know it's possible...
A few lessons I've learned are -- I can use any recovery (TWRP) to use MTP and flash files and stuff... but in order for the phone to work properly, I have to a) flash the SuperSU (not just the ROM) and b) make sure I have the "correct/proper" TWRP (kernel?) matched with each ROM. Is that kind of right? That's where I'm stuck I guess.
I downloaded from here
https://forum.xda-developers.com/oneplus-3/how-to/oxygenos-4-0-android-nougut-official-t3529684
I'm sure I'm making a ton of mistakes -- that's why I'm here
(I read here https://forum.xda-developers.com/on...mple-trick-t3530685/post70415499#post70415499 that .28 shouldn't be used)
This post mentions a procedure to get rid of verity https://forum.xda-developers.com/oneplus-3/how-to/fix-device-mapper-verity-simple-trick-t3530685
I'm currently backing up my data, and I'll attempt to follow these instructions to switch to f2fs (hopefully get rid of the verity error) and install OxygenOS 4.0.1 (http://otafsc.h2os.com/patch/amazon...n_16_OTA_037_all_1701041839_aa64b084a40a4.zip)
I'm also a bit confused about the best version of SuperSU-v2.79 to use, because blu_spark was writing somewhere (can't find where) that SR1 and SR2 were the cause of battery issues ... So yeah, I've got other things to try, but should the ROM from OOS4.0.1 work with any of them?
THANKS.
Click to expand...
Click to collapse
Unfortunately I haven't tried to update the phone yet, so I don't know what else you can do. But you can also follow the guide posted by @Viper The Ripper here:
https://forum.xda-developers.com/showpost.php?p=70499899&postcount=5
I think that it's simpler and I'll follow that one this weekend when trying to updating my phone
Zingapuro said:
Hi guys,
As soon as I got the OP3 in July, I somehow managed to successfully perform all the steps to get it rooted. I was running OnePlus3Oxygen_16_OTA_013_all_1608061823_765c081a5c8e4dad.zip
OnePlus has been showing me a "new version available" since September, but I very patiently and calmly didn't install it OTA because I didn't want to lose the root.
Finally had a bit of time today, decided I'd finally upgrade. Looked around for the "most recent stable version" and picked this one: OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2af7.zip
Followed the steps for flashing using TWRP (twrp-3.0.2-1.28-oneplus3) here:
https://forum.xda-developers.com/oneplus-3/how-to/oxygenos-4-0-android-nougut-official-t3529684
It worked. Yay. Then (god dammit **** ****) I still saw this "new version available" and couldn't swipe it away... I accidentally clicked it and it downloaded the OTA. Fine.
Now I'm stuck in a TWRP boot loop. I tried re-installing the OTA_035.zip from TWRP -- I tried restoring my Nandroid Backup (only had enough room to save "Boot / Recovery / System" partitions, NOT data) -- and I tried ADB Sideloading 16_OTA_013.zip.
I'm stuck rebooting in TWRP 3.0.2-1.
Is there anything I can try before going ballistic and wiping my data?
Thanks.
Marc
Click to expand...
Click to collapse
In my opinion, the only thing you can try is to make a data backup from recovery to any external storage (like a pendrive) by Otg, but it takes some risks. In case this partition has been damaged, you can get issues when you install the rom.
The safest you can do is clean installation in spite of you lose data so, full wipes and a new full rom.
Enviado desde mi ONEPLUS A3003 mediante Tapatalk
You have to install stock recovery, and then reboot into recovery, you will have a instalation error, reboot and loop solved Then, you can flash your twrp and su without loosing data
I discovered following this threath desesperate and going to do a clean install, dowload the files and try to do it steap by steap: https://forum.xda-developers.com/oneplus-3/how-to/fix-device-mapper-verity-simple-trick-t3530685
Good luck :good:
P.D.: I have formated system partition, so I lost the android configuration
satisastur said:
You have to install stock recovery, and then reboot into recovery, you will have a instalation error, reboot and loop solved Then, you can flash your twrp and su without loosing data
I discovered following this threath desesperate and going to do a clean install, dowload the files and try to do it steap by steap: https://forum.xda-developers.com/oneplus-3/how-to/fix-device-mapper-verity-simple-trick-t3530685
P.D.: I have formated system partition, so I lost the android configuration
Click to expand...
Click to collapse
Hey Satisastur,
Thanks for taking the time to comment. Yes, actually that's exactly the guide I wanted to follow. But I'm stuck before even starting -- if I make Nandroid Backup now (in ext4) I can't load it back once filesystem changes to f2fs -- isn't that right?
(I also asked the question in that thread: https://forum.xda-developers.com/on...rity-simple-trick-t3530685/page8#post70525818 )
And uh... sorry... what exactly do you mean "android configuration"... like ringtones and stuff?
Zingapuro said:
Hey Satisastur,
Thanks for taking the time to comment. Yes, actually that's exactly the guide I wanted to follow. But I'm stuck before even starting -- if I make Nandroid Backup now (in ext4) I can't load it back once filesystem changes to f2fs -- isn't that right?
(I also asked the question in that thread: https://forum.xda-developers.com/on...rity-simple-trick-t3530685/page8#post70525818 )
And uh... sorry... what exactly do you mean "android configuration"... like ringtones and stuff?
Click to expand...
Click to collapse
Yes, I was on f2fs before this happens, so I only have to install all without formating data. You should do a manual backup to do that, once on recovery, you be able to enter phone data partition from windows. Copy all folders you want to save before formating to f2fs in recovery. Other setup and configuration like ringtones and stuff, all cache and configuration of apps, wallpaper, led, colors and themes... you will lost it. I don't know how to backup that, but its the worst part of formating data... google backup doesn't save all the config
You will start with the android phone start menu, like new, with new dactilar and patron security, etc...
@Zingapuro
Try TWRP 3.0.2_19 and Supersu 2.79 stable. For some people this works and according to eng. stk, only Supersu 2.79 stable is compatible with N.
tnsmani said:
Try TWRP 3.0.2_19 and Supersu 2.79 stable. For some people this works and according to eng. stk, only Supersu 2.79 stable is compatible with N.
Click to expand...
Click to collapse
Tried flashing twrp-3.0.2-19-oneplus3.img and from TWRP installing:
OnePlus3Oxygen_16_OTA_037_all_1701041839_aa64b084a40a4.zip
UPDATE-SuperSU-v2.79-20161211114519.zip
Same issues as described above: boots into 4.0.1, but buggy, SIM cards don't work, no Dev options, etc...
satisastur said:
Copy all folders you want to save before formating to f2fs in recovery.
Click to expand...
Click to collapse
Yeah, I have a feeling this is my only choice. This is the next thing I'll try.
Zingapuro said:
Tried flashing twrp-3.0.2-19-oneplus3.img and from TWRP installing:
OnePlus3Oxygen_16_OTA_037_all_1701041839_aa64b084a40a4.zip
UPDATE-SuperSU-v2.79-20161211114519.zip
Same issues as described above: boots into 4.0.1, but buggy, SIM cards don't work, no Dev options, etc...
Yeah, I have a feeling this is my only choice. This is the next thing I'll try.
Click to expand...
Click to collapse
Try this guide: https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757
It will fix most of your issues.
For going back to full stock use this guide: https://forums.oneplus.net/threads/guide-how-to-unroot-your-oneplus-3-and-go-back-completely-to-stock.456232/
I hope everything will go back to normal.
Hi everyone,
Just want to update that my phone is back up and running. Thanks for your all your help.
More details here:
https://forum.xda-developers.com/on...rity-simple-trick-t3530685/page9#post70588707
Is there any way to update this thread to [SOLVED] ?
Zingapuro said:
Hi everyone,
Just want to update that my phone is back up and running. Thanks for your all your help.
More details here:
https://forum.xda-developers.com/on...rity-simple-trick-t3530685/page9#post70588707
Is there any way to update this thread to [SOLVED] ?
Click to expand...
Click to collapse
Great!
I think you can edit the thread title
Boot into your recovery [Vol+ and Power]
Connect your phone to your PC
Execute the following fastboot command on your PC (More informations on fastboot)
Code:
fastboot continue
Your phone will start right away. :good:
hello!
hopefully somenone can help me:
i try to install lineage os 14.1 (lineage-14.1-20170208-nightly-oneplus3-signed), downloaded from official lineage os site on my op3, but i always get error:7.
exactly it says:
Wiping data without wiping /data/media...
Done.
Formatting Cache using make_ext4fs...
Updating partition details...
...done
Installing zip file ' /sdcard/Download/lineage-14.1-20170208-nightly-oneplus3-signed.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Comparing TZ version TZ.BF.4.0.1-76917 to TZ.BF.4.0.1-00186
assert failed: oppo.verify_trustzone("TZ.BF.4.0.1-76917")=="1"
Updater process ended with ERROR: 7
Error installing zip file ' /sdcard/Download/lineage-14.1-20170208-nightly-oneplus3-signed.zip
Updating partition details...
...done
I use the newest twrp (twrp-3.0.3-0-oneplus3) downloaded from official twrp site. i checked the md5 sums of the zip file and it is correct. bootlader is unlocked. I had cm 13 rooted with supersu installed on the op3, when i first tried to install lineage 14.1, but got this error:7. then i changed to oxygen stock rom (not rooted) and tried again, still error:7.
before trying to install, i made a factory reset, then i tried advanced wipe with dalvik,system,data and cache wiped. both wiping methods without success.
i dont have much experience and dont know what to do now? please help.
You need to edit the updater-script in the .zip in META-INF/com/google/android and delete the very first parts of the script beginnings with "assert".
That should do it
I install the lineage 08/02/2017 successfully, First I flash Oxygen Os 4.0.2 then I wipe
-System
-Cache-
-Data
-Dalvic Cache
Then Flash Lastest Lineage built with twrp 3.0.4-1
hello,
ok, i installed oxygen OS 4.0.2. i did not changed to stock recovery, so still have twrp.
when i boot the phone i get a dm-verity warning. can i just ignore it?
i have no root at the moment. bootloader is unlocked.
what should i do next? use the nightly or experimental lineage? update twrp to 3.0.4-1?
better install firmware plus modem 4.0.2(or 4.0.3) not full oxygen zip
hi,
with twrp 3.0.4-1 the installation of lineage was successful.
i followed the way akuma48465 said above.
just one last question:
is it normal that i get the dm-verity-warning during boot? can i just ignore it? is there a way to get rid of the warning? after the warning, booting is proceeding normally by the way.
flotsch1 said:
hello!
hopefully somenone can help me:
i try to install lineage os 14.1 (lineage-14.1-20170208-nightly-oneplus3-signed), downloaded from official lineage os site on my op3, but i always get error:7.
exactly it says:
Wiping data without wiping /data/media...
Done.
Formatting Cache using make_ext4fs...
Updating partition details...
...done
Installing zip file ' /sdcard/Download/lineage-14.1-20170208-nightly-oneplus3-signed.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Comparing TZ version TZ.BF.4.0.1-76917 to TZ.BF.4.0.1-00186
assert failed: oppo.verify_trustzone("TZ.BF.4.0.1-76917")=="1"
Updater process ended with ERROR: 7
Error installing zip file ' /sdcard/Download/lineage-14.1-20170208-nightly-oneplus3-signed.zip
Updating partition details...
...done
I use the newest twrp (twrp-3.0.3-0-oneplus3) downloaded from official twrp site. i checked the md5 sums of the zip file and it is correct. bootlader is unlocked. I had cm 13 rooted with supersu installed on the op3, when i first tried to install lineage 14.1, but got this error:7. then i changed to oxygen stock rom (not rooted) and tried again, still error:7.
before trying to install, i made a factory reset, then i tried advanced wipe with dalvik,system,data and cache wiped. both wiping methods without success.
i dont have much experience and dont know what to do now? please help.
Click to expand...
Click to collapse
Just use latest TWRP recovery, 3.0.4-1. It will work as well.
Use 4.0.3 firmware . This solved it for me.
flotsch1 said:
hello!
hopefully somenone can help me:
i try to install lineage os 14.1 (lineage-14.1-20170208-nightly-oneplus3-signed), downloaded from official lineage os site on my op3, but i always get error:7.
exactly it says:
Wiping data without wiping /data/media...
Done.
Formatting Cache using make_ext4fs...
Updating partition details...
...done
Installing zip file ' /sdcard/Download/lineage-14.1-20170208-nightly-oneplus3-signed.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Comparing TZ version TZ.BF.4.0.1-76917 to TZ.BF.4.0.1-00186
assert failed: oppo.verify_trustzone("TZ.BF.4.0.1-76917")=="1"
Updater process ended with ERROR: 7
Error installing zip file ' /sdcard/Download/lineage-14.1-20170208-nightly-oneplus3-signed.zip
Updating partition details...
...done
I use the newest twrp (twrp-3.0.3-0-oneplus3) downloaded from official twrp site. i checked the md5 sums of the zip file and it is correct. bootlader is unlocked. I had cm 13 rooted with supersu installed on the op3, when i first tried to install lineage 14.1, but got this error:7. then i changed to oxygen stock rom (not rooted) and tried again, still error:7.
before trying to install, i made a factory reset, then i tried advanced wipe with dalvik,system,data and cache wiped. both wiping methods without success.
i dont have much experience and dont know what to do now? please help.
Click to expand...
Click to collapse
same here.
twrp 3.0.4-1/oos 4.0.3/wiped(cache/system/dalvic cache/data) but still not work.
Clean Install the experimental version first then install newest nightly. That's what worked for me.
flotsch1 said:
just one last question:
is it normal that i get the dm-verity-warning during boot? can i just ignore it? is there a way to get rid of the warning? after the warning, booting is proceeding normally by the way.
Click to expand...
Click to collapse
That's normal. If you're still on firmware 4.0.2, just go fastboot and enter the commands:
Code:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
Reboot.
Firmware 4.0.3 doesn't have support for the commands anymore. So flash 4.0.2, run the command to save 5 precious seconds when the phone boots, then flash 4.0.3 firmware again if you want.
Jlew7715 said:
Clean Install the experimental version first then install newest nightly. That's what worked for me.
Click to expand...
Click to collapse
Already did that. got the same resault of error7.
thanks for replay~
This is because for any new versions of custom rom u need oos 4.0.3 modem so flash 4.0.3 modem zip and then flash the rom... This worked for a friend of mine
Puddi_Puddin said:
Use 4.0.3 firmware . This solved it for me.
Click to expand...
Click to collapse
where can I find a flashable 4.0.3 firmware/modem zip? I could probably dissect the zip file I guess.
---------- Post added at 02:53 PM ---------- Previous post was at 02:15 PM ----------
ExtentedByte said:
You need to edit the updater-script in the .zip in META-INF/com/google/android and delete the very first parts of the script beginnings with "assert".
That should do it
Click to expand...
Click to collapse
Easiest way to deal with it.
cheetah_chen said:
Already did that. got the same resault of error7.
thanks for replay~
Click to expand...
Click to collapse
Coming from Oxygen 3.2.7 I had to upgrade to 4.0.3, install TWRP 3.0.4-1, Wipe data/cache and then install Lineage OS (latest nightly 0302)
Error 7 TZ issues
Hi Guys,
I am running TWRP twrp-3.0.4-1-oneplus3 and when I try to install any ROM I get the error 7. Last night I tried lineage-14.1-20170302-nightly-oneplus3-signed which eventually failed (attached error 7 image) then I tried RR-N-v5.8.2-20170218-oneplus3t-Official which too failed citing TrustZone error.
I modified LineageOS text removed "assert"as mentioned earlier but it still fails.
I tried "adb sideload image.zip /sdcard/" and its show serving but on phone the progress bar increases faster then what percentage showing on windows and it fails too.
I can't even wipe data and cache most of the times due to partition error, Is it something wrong with TWRP?
I suspect TWRP might be the issue but need experts advise please.
junostik said:
Hi Guys,
I am running TWRP twrp-3.0.4-1-oneplus3 and when I try to install any ROM I get the error 7. Last night I tried lineage-14.1-20170302-nightly-oneplus3-signed which eventually failed (attached error 7 image) then I tried RR-N-v5.8.2-20170218-oneplus3t-Official which too failed citing TrustZone error.
I modified LineageOS text removed "assert"as mentioned earlier but it still fails.
I tried "adb sideload image.zip /sdcard/" and its show serving but on phone the progress bar increases faster then what percentage showing on windows and it fails too.
I can't even wipe data and cache most of the times due to partition error, Is it something wrong with TWRP?
I suspect TWRP might be the issue but need experts advise please.
Click to expand...
Click to collapse
Did you upgrade to the firmware that is required? Otherwise try a different twrp..
Puddi_Puddin said:
Did you upgrade to the firmware that is required? Otherwise try a different twrp..
Click to expand...
Click to collapse
Can you please let me know which firmware I should upgrade to?
junostik said:
Can you please let me know which firmware I should upgrade to?
Click to expand...
Click to collapse
Currently I do not have time. Have you used the search option in the thread yet?
junostik said:
Can you please let me know which firmware I should upgrade to?
Click to expand...
Click to collapse
You definitely need to install 4.0.3 and after you can install Lineage.
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?