Can't update my oneplus 3 with TWRP (error 7) - Android Q&A, Help & Troubleshooting

I am trying to update my oneplus 3 to the latest oxygen os 5.0 which has oreo. Every time i update the phone weather it be from the settings or manually from a zip file with deleted assets I still get the error 7 (as I am using TWRP 3.1.1-2). Everywhere says to delete assets and I still get the error, I am 100% sure I have the correct update as I got the update zip directly from the directory. Any one know what to do?

Bruucio said:
I am trying to update my oneplus 3 to the latest oxygen os 5.0 which has oreo. Every time i update the phone weather it be from the settings or manually from a zip file with deleted assets I still get the error 7 (as I am using TWRP 3.1.1-2). Everywhere says to delete assets and I still get the error, I am 100% sure I have the correct update as I got the update zip directly from the directory. Any one know what to do?
Click to expand...
Click to collapse
Yeah, I had the exact same problem. Tried removing the getprop lines from updater-script etc, that returned error 3. Then I realised there was a new TWRP version (3.2.0), so installed that, and flashed the original downloaded OS. Worked perfectly! You'll need to reinstall TWRP and re-root after that, though

Related

After 12hrs trying to claw out of a hole......I ALMOST screwed up my Nexus 9 LTE

Hoping someone might see this as useful......it sure has been a 12hr nightmare! This all started because my N9 LTE was AWFUL SLOW, like going from one app to the other took 20 seconds for it to do anything, hit a text box and 20-30sec for the keyboard to pop up, all not normal, my wife has a Galaxy Tab 2 and it's 100times faster so I decided I would try and install a custom ROM........... after spending 12hrs trying to install CM13 on my Nexus 9 LTE and it giving me errors upon booting to using TWRP I did a bunch of wipes and formatting, rooted the device, tried to get it back to factory ROM etc. and then I thought I might have a bricked the tablet :'( Here's my story.
After ~8hrs of trying to install stuff from the first custom ROM I tried, then CM13 and of course reading A LOT of websites and trying to install CM13 with it not working I decided to do a clean install of CM13 and follow the steps in this thread to make it work: http://forum.xda-developers.com/nexus-9/orig-development/rom-cyanogenmod-13-nexus-9-lte-t3273566
Installation instructions
-Check if you have the latest bootloader (3.48.0.0135) and updated /vendor partition from the latest image OR just flash latest image (MMB29K) (it says here MMB29k but latest is MMV29V so I used that)
-Flash a custom recovery
-Factory Reset
-Install ROM
-Install GApps
First Step was Flashing the Latest factory Image. I went to this Website: https://developers.google.com/android/nexus/images#volantisg
Downloaded the MMB29V, used 7Zip to get to the proper folder/files.
Used this Method here to flash to factory: http://www.droidviews.com/restore-nexus-9-stock-using-factory-images/
I was able to get this to work:
fastboot flash bootloader bootloader-flounder-3.43.0.0XXX.img
fastboot reboot-bootloader
Then I tried this:
fastboot –w update image-volantis-mmb29v.zip
However I get an error saying:
Code:
target reported max download size of 518205818 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate -1985890160 bytes
error: update package missing system.img
I then tried to install these files manually and the system.img always fails.
After trying that several times trying to wipe then re-install etc. it didn't work and it was midnight and I was getting a little panicked, then I come across this thread: http://forum.xda-developers.com/nexus-9/help/marshmallow-ota-update-bricked-nexus-9-t3334871 and I thought WOW, thank god a solution and I'll get to have Android N, kinda cool.
I download the proper OTA file from here for my LTE model: https://developer.android.com/preview/download-ota.html
file: volantisg-ota-NPC56X-2-2edd174f.zip
I installed this file in the ADB/Fastboot folder then per the directions on my Tablet I went to recovery and, Wiped Cache chose “Apply Update from ADB”.
I then opened the command prompt, checked the device was connected using "ADB Devices", confirmed it’s there so then I tried: "adb sideload volantisg-ota-npc56x-2-2edd174f.zip"
It started working, got to ~35% then I get:
Code:
Total xfer:1.00x
on the command prompt window
and also
Code:
This Package is for "Flounder_LTE" devices; this is a "flounder"
E:Error in /sideload/package.zip
(Status 7)
Installation Aborted
on the tablet
So I thought that was weird since I clearly have an LTE device so I decided to download and try the regular N9 OTA image file: volantis-ota-NPC56X-2-3fa71d1a.zip
I then opened the command prompt, checked the device was connected using "ADB Devices", confirmed it’s there so then I tried: "adb sideload volantis-ota-npc56x-2-3fa71d1a.zip"
It WORKED!!! Felt like at least something was successful after 12hrs of screwing around with this.
Booted up everything was good went into the setup and all is good.....EXCEPT now I don't have LTE :'( my N9 is at 2% battery life so I will let it charge overnight and tomorrow and try and figure out how I can do this over again............if someone has thoughts or suggestion on something I did wrong in order to get CM13 in here I'm all ears.
Thanks!
Ok, in case someone reads this in the future, this morning after a little bit of sleep and the Tablet having fully charged I decided to try things again since I wasn't happy with Android N without LTE working.
Steps I took:
-Flashed Factory Img using adb/fastboot, used the MMB29R factory image as that's what I noticed was listed on the CM13 I was trying to install. This wasn't working using the Flash.All however I was able to manually flash all the files including system.img which was previously giving me errors so that was good. The unit booted up in the factory image but I didn't do anything I just booted to Fastboot so I could install CM13.
-I installed TWRP, made sure on first reboot after install to boot to recovery
-Moved the CM13 and Gapps-Pico to the N9
-Used TWRP to install the CM13 then Gapps
-Rebooted, all seemed to work, HOWEVER, I was getting the "Unfortunately Google Play Services has Stopped" and "Unfortunately Setup Wizard has Stopped" upon boot, can't go past this so I was frustrated.
-Found a link that said in ADB to type
Code:
pm grant com.google.android.setupwizard android.permission.READ_PHONE_STATE
however this didn't do anything for me
-Tried to install another Gapps, downloaded the mini version, that didn't work either
At this point, I decided maybe CM13 isn't for me....most people would have stopped a long time ago I think lol
I decided to flash the latest stock version, MMB29V and just use that, maybe I'll try again sometime.
If you sign up for the Android Beta Program (https://www.google.com/android/beta) Android N will be sent to your device as an OTA. I had no problem upgrading to N this way on my WiFi Nexus 9. When you hit the page any device that's eligible to enroll will be displayed.

oppo.verify trustzone error

Hey guys,
Running a rooted oneplus x with latest cyanogenmod (CM) nightly installed. I tried updating the latest nightly and got the following error:
updater process ended with ERROR: 7
Error installing zip file '/external_sd/cm-13.0-20161101-NIGHTLY-onyx.zip'
- I had CM recovery installed, and was getting the same error.
- I tried to update the CM recovery but I get the same error.
- I managed to install TWRP 3.0.2.0 recovery, and still no luck. Same error.
- Tried installing the latest Oxygen OS (downloaded from their site) and still same error.
- As per other forums, I've tried editing the updeater-script and still no luck. I deleted the first line, then saved and zipped. When I try to flash with that it says "can not find updater-script" even though I put the file type back to the way it was, and in the same spot.
any thoughts?
thanks!
You can try to change ONE to ONEPLUS in updater-script, do not delete the lines just change one to oneplus & then try to flash with twrp.
Same answer as in OP forum :
Before flashing, you should have done that.
http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Now, if it doesn't work, it can be quite complicated....
Try updating the TWRP or use CM recovery
http://forum.xda-developers.com/showpost.php?p=69423690&postcount=60

I cant install ANY ROM with TWRP on Honor5X. Cant restore Backup.seriously need Help

So i got my Honor 5x yesterday and thought i would install a custom rom on it since people are recommending it.
Its my first time so i followed guids. I installed adb and fastboot and managed to get TWRP 3.1.1-0- on it.
Btw, i have a Honor 5x
Model KIW-L21
I am able to get into the recovery TWRP. I made a backup and saved the folder "BACKUPS" on my PC.
I then downloaded LineageOS from their Homepage: download (DOT) lineageos (DOT) org/kiwi
I downloaded the latest version. I also downloaded Gapps from Opengapps.org. I downloaded ARM64 version 7.1
I wiped my phone completely and copied the two zip files on the phone. I went to "install", selected LineageOS zip and added Gapps. i swiped right to install and the installation stopped with ERROR 7
I tried to download older versions of LineageOS but the same thing happens. ERROR 7
I then downloaded an olderversion of CM13 with GAPPS 6.0. Again, Error 7
I downloaded XENON HD ZIP from here: mirrors (DOT) c0urier (DOT) net/android/teamhorizon/N/Official/kiwi/
Error 7
I downloaded ASOP from here: downloads (DOT) aospextended (DOT) com/kiwi/
Error 7
I looked up Error 7 and its says it is a security check that figures out, that the ROM is not compatible with the Phone. Some guy told me that this happens a lot and that i should use another rom.
I looked for a solution on youtube and found a guy who said that i can do the following:
Unzip the ROM on your pc, go into \META-INF\com\google\android and open the updater script with Notepad++. Delete the first two lines that says asserts, save, close it again and zip the whole package again.
I copied the new, modifiled rom on the phone with the GAPPS and installed it. This time ERROR 7 didnt appear. GAPPS were also installed. When i boot my device i get in the loading screen from Lineage for about 5-10 minutes. After that, it just restarts and restarts and restarts. I can't get out of the boot loop since I can't remove my battery. when I press VOL UP I come back the TWRP and can wipe the phone again.
I tried that with 3 different LineageOS ROMS and one XENON HD ROM.
I also get into a boot loop where my phone just restarts and restarts and restarts.
I tried to get my backup working so I copied the folder "BACKUPS" on my phone and went to restore in TWRP. but... i found nothing there?
I am super frustrated since my phone is basically dead and I have no idea what I can do.
BTW, every site calls my phone "KIWI" but my model number is "KIW-L21"
As mentioned in Los 14.1 thread (& should be mentioned in all threads), "ROM Firmware Required: No VoLTE firmware! (B360, B370, ...)". You must downgrade your stock rom to B350 at least, before try playing with custom roms (only for kiwi, of course).
Non VoLTE Marshmallow firmware is required. As said by @mauam get in there and have the same process repeated
Thank you for your replies.
The only thing i could find was this thread: https://forum.xda-developers.com/ho...-lineageos-14-1-pre-official-kiw-l24-t3528488
It said there:
Important note:
Stock Firmware B360 and B370 are known to cause bootloops!
(Generally: if your stock ROM supports VoLTE it is likely that it is also affected!)
All others might work, please do not ask in here how to up- or downgrade!
It doesnt mentioned what that mean and even said "dont ask in here how to downgrade"
I have no idea what all that means. I dont know what stock firmware is, what version i have or how i could downgrade it. I can access TWRP, but still have no OS on it.
edit: this is the full log:
Updateing partition details...
... done
Full SElinux support is present.
MTP Enabled
Installing zip file '/sdcard/lineage-14.1-20170816-nightly-kiwi-signed.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Comparing TZ version TZ.BF.3.0.C3-00025 to TZ.BF.3.0.C3-00022") =="1"
assert failed: kiwi.verify_trustzone("TZ.BF.3.0.C3-00025") == "1"
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/lineage-14.1-20170816-nightly-kiwi-signed.zip'
Updating parition details...
...done
Click to expand...
Click to collapse
When i edit the zip file and delete the first two line of the updater scripter with notepad++ as i mentioned above, i can install these ROMS, but they wont boot / are in an infinite Bootloop
So on which firmware you were before flashing Los
PalakMi said:
So on which firmware you were before flashing Los
Click to expand...
Click to collapse
how do i check that?
I was able to get the backup running. So I am back to EMUI 3.1 / Android 5.1.1. Here is a screenshot from my phones status: i.imgur (DOT) com/rCnuOpX.png
Activehannes said:
how do i check that?
I was able to get the backup running. So I am back to EMUI 3.1 / Android 5.1.1. Here is a screenshot from my phones status: i.imgur (DOT) com/rCnuOpX.png
Click to expand...
Click to collapse
Just go to about phone
PalakMi said:
Just go to about phone
Click to expand...
Click to collapse
I did and posted a screenshot above
is it Build number "KIW-L21C432B160"
so... B160?
update:
I just downloaded this:
NEW KIW-L21 C432B350 - D003
from this thread: https://forum.xda-developers.com/honor-5x/how-to/repository-honor-5x-file-depot-t3328288
I was going to unzip it, copy the "dload" folder on my device, go the the updater and run the "local update package".
And then my phone will be on android 6.0 with b350, right?
The next step would be to start the phone in the recovery TWRP, go to wipe --> advance wipe and select everything (system, data, cache etc). after that i copy the latest Kiwi lineage OS zip rom on my device with the GAPPS 7.1 and try to install them again via TWRP 3.1.1?
Is this right?
I just wanna ask because my phone doesnt work for 2 days now and i dont want to brick it completely. cant afford a new one
Update to marshmallow first (any update before b360, like b320)
Update to marshmallow first (any update before b360, like b320)
Click to expand...
Click to collapse
when i go to the "updater" and and search for a new update it says that there is none. My phone is still on EMUI 3.1/android 5.1.1/b160. Do i need to manually download another firmware? so a B320 patch first (with the dload folder and local upgrade package) and after that the B350 upgrade?
Try manual ota here or search here. If no luck use XDA search bar &/or Google. Good luck.
Activehannes said:
when i go to the "updater" and and search for a new update it says that there is none. My phone is still on EMUI 3.1/android 5.1.1/b160. Do i need to manually download another firmware? so a B320 patch first (with the dload folder and local upgrade package) and after that the B350 upgrade?
Click to expand...
Click to collapse
Try any marshmallow update before b360.
If it didn't work, try the above post.
so i followed this guide: https://forum.xda-developers.com/honor-5x/how-to/manual-ota-update-guide-update-app-t3445976
he describes 2 methods.
I wasnt able to find a B320 update for KIW L21, only for KIW L22 which is the Indian device I think. so I downloaded KIW L21 B330 Denmark. I unzipped the file and copied the dload folder on my device,
i went to update --> menu --> local update --> UPDATE.APP
my phone restarts into TWRP and does nothing. I know that I need the EMUI stock recovery, not TWRP, but no matter how many times I do this, it always restarts into TWRP.
i also tried the other method.
I shut down my phone, press VOLUP and VOLDOWN and Power. The phone goes into the the "honor" loading screen and restats after a few seconds. and restart again and again. If i release the power button before it restarts, it just boots into the system. If I shut it down and hold VOLUP and Power it boots into TWRP. I tried so many different compinations, but i cant get my phone into the EMUI Stock recovery. I read in the other XDA thread, that i need to unlock my phone. So i tried that. i went adb reboot bootloader --> fastboot oem relock CODE. the console did its magic but my phone is still unlocked. And now i cant repeat that command. when i go again into the bootloader and type fastboot oem relock it says:
PS C:\adb> adb devices
List of devices attached
W6HDU17610003396 device
PS C:\adb> adb reboot bootloader
PS C:\adb> fastboot oem relock 1524319619165116
...
FAILED (remote: Image verify failed,relock fail)
finished. total time: 1.810s
PS C:\adb> adb devices
List of devices attached
PS C:\adb>
Click to expand...
Click to collapse
So, i still have b160 / android 5.1 on my phone :/ can anyone figure out what went wrong?
Activehannes said:
so i followed this guide: https://forum.xda-developers.com/honor-5x/how-to/manual-ota-update-guide-update-app-t3445976
he describes 2 methods.
I wasnt able to find a B320 update for KIW L21, only for KIW L22 which is the Indian device I think. so I downloaded KIW L21 B330 Denmark. I unzipped the file and copied the dload folder on my device,
i went to update --> menu --> local update --> UPDATE.APP
my phone restarts into TWRP and does nothing. I know that I need the EMUI stock recovery, not TWRP, but no matter how many times I do this, it always restarts into TWRP.
i also tried the other method.
I shut down my phone, press VOLUP and VOLDOWN and Power. The phone goes into the the "honor" loading screen and restats after a few seconds. and restart again and again. If i release the power button before it restarts, it just boots into the system. If I shut it down and hold VOLUP and Power it boots into TWRP. I tried so many different compinations, but i cant get my phone into the EMUI Stock recovery. I read in the other XDA thread, that i need to unlock my phone. So i tried that. i went adb reboot bootloader --> fastboot oem relock CODE. the console did its magic but my phone is still unlocked. And now i cant repeat that command. when i go again into the bootloader and type fastboot oem relock it says:
So, i still have b160 / android 5.1 on my phone :/ can anyone figure out what went wrong?
Click to expand...
Click to collapse
May be i can help u with this .

[Guide] : How to use updates packages already downloaded

Hello
If you have already downloaded the updates packages, you don't need to redownload them via "System update"
Just copy them to Internal storage and follow the video
(In my case I need "update.zip" and "update_data_full_public.zip" and "update_full_VIE-L29_hw_meafnaf.zip")
https://www.youtube.com/watch?v=z4nOXgsic1o
I have all the three files, but in my case the "System Update" option on the settings just not appear. How should I procceed?
Kempf said:
I have all the three files, but in my case the "System Update" option on the settings just not appear. How should I procceed?
Click to expand...
Click to collapse
same question
what is your model VIE-???C???B???
xzanium said:
what is your model vie-???c???b???
Click to expand...
Click to collapse
vie-l29c636b370
The same as mine, lol. VIE-L29C636 running B370.
I've tried most of Firmware Finder's compatible versions B382, B384, but none of them work (through deload folder and 'forced' update).
The only one which works is the 81131 (VIE-L29C636B370).
have you tried to search in setting
also check in Setting -> Apps if they are the "System update" apps
I got b384 on system update ota
I search in setting "system update" appear but its not work, in setting->apps not appear
I'm not sure, but I think that when you have update to B370, the additional pack have not been installed.
try to download this pack update_full_hw_spcseas.zip and flash it with twrp
xzanium said:
I'm not sure, but I think that when you have update to B370, the additional pack have not been installed.
try to download this pack update_full_hw_spcseas.zip and flash it with twrp
Click to expand...
Click to collapse
i flash this in TWRP and now i cant boot to device, please help me
I downloaded rom b384 to copy to internal storage and install by twrp but not, is there any way to install rom from twrp
@vurobben, as long as I know and read about, there's no way to install it unless trough the System Update.
If your mobile is not booting, you've to download the version that allow you to update trough dload folder (in my case, the only one which do this is the 81131 - VIE-L29C636B370). Then, you've to install via TWRP the files that @xzanium said.
In my case, I'll try to do it at night. I've tried to locate the Update on the settings, and also in the apps.
And now my phone no os, i just boot in twrp recovery. Can you make a backup file in twrp and up to google drive?
sorry, my phone is VIE-L29C185
to fix your problem you must download the rollback package(C900B300) and firmware package (C636B190) from this page : http://consumer.huawei.com/kh/support/downloads/index.htm
(search for Keyword "P9 plus")
then install rollback package via 3 buttons methode (vol+ , vol- , power)
then the B190 package
I'll try to updload the files tonight.
I'm trying to do this rollback. Acually I did not know how to do it. I'll try the way @xzanium mentioned.
just extract teh zip file, then copy the dload folder to sd card
shutdown the phone
press all 3 buttons
It kind of did the trick. Now the Build Number is VIE-L19C900B300, but the EMUI is still 5.0 and Android 7.0 (Nougat). I think it'll solve @vurobben boot looping problem.
But.. the System Update option still not appear, and the clock does not work also
I'll keep trying.
Now I'm going to update for 370 (dload), then install TWRP and flash these ZIP files: 1)update_data_full_hw_spcseas, 2) update_data_full_public and 3) update_full_hw_spcseas.
[edit]
Mine is not woking anymore..
I've tried to flash the 'update_data_full_hw_spcseas', but it's in a bootloopping also. Tried to roolback again, but didn't work this time.
Now it enters in Huawei eRecovery, try to get the recovery from the server but fails..
[edit2]
I've installed the Rollback (dload), then I've downloaded the "HUAWEI P9 Plus Firmware (VIE-L29, Android6.0, EMUI4.1.1, C636B190, Thailand, Cambodia, Nonspecific)" on the same site that @xzanium mentioned and installed just after the rollback. Everithing is working now.
I've just checked and I'm on EMUI 4.1.1, Androind 6 (M) and Build VIE-L29C636B190. The goodnews is that the "System Update" is workind now. Tomorrow I'll try to update to Androin N and get everithing fine there also.
Thanks for the help.
Kempf said:
It kind of did the trick. Now the Build Number is VIE-L19C900B300, but the EMUI is still 5.0 and Android 7.0 (Nougat). I think it'll solve @vurobben boot looping problem.
But.. the System Update option still not appear, and the clock does not work also
I'll keep trying.
Now I'm going to update for 370 (dload), then install TWRP and flash these ZIP files: 1)update_data_full_hw_spcseas, 2) update_data_full_public and 3) update_full_hw_spcseas.
[edit]
Mine is not woking anymore..
I've tried to flash the 'update_data_full_hw_spcseas', but it's in a bootloopping also. Tried to roolback again, but didn't work this time.
Now it enters in Huawei eRecovery, try to get the recovery from the server but fails..
[edit2]
I've installed the Rollback (dload), then I've downloaded the "HUAWEI P9 Plus Firmware (VIE-L29, Android6.0, EMUI4.1.1, C636B190, Thailand, Cambodia, Nonspecific)" on the same site that @xzanium mentioned and installed just after the rollback. Everithing is working now.
I've just checked and I'm on EMUI 4.1.1, Androind 6 (M) and Build VIE-L29C636B190. The goodnews is that the "System Update" is workind now. Tomorrow I'll try to update to Androin N and get everithing fine there also.
Thanks for the help.
Click to expand...
Click to collapse
when rollback bootloader unlock or relock?
I could not verify yet, but I thing it does lock the bootloader again, because the bootloader option is enable under the developer settings again.

HTC U11 cant install stock rom because all files are corrupt in TWRP

Hello everyone,
so I have been playing around with my HTC U11. I unlocked the bootloader and installed the newst TWRP version. Then I flashed it to Lineage 16. However I could not install the HTC Edge Sense App and since I couldnt find any answers to that problem decided to flash back to stock rom and then update to Android 9.0 and get my Edge Sense back.
So I checked for my device CID which is HTC_034 and downloaded myself the stock rom from the getdroidtips stock firmware collection (cant post link because I am new)
I did the MD5 Checksum and everything was fine. However when I try to sideload it via adb i get a zip file corrupt error and TWRP stops it. Then I tried pushing it and installing it through the install function of TWRP. I can push it onto the device but when I want to install it I get the same error again. Things I tried so far:
1. used an older version of TWRP
2. all the 4 stockroms available for the HTC_034 on said link
3. load the .zip onto an sd card, enter it and tell TWRP to install from there - didnt work either.
4. rename the .zip to package.zip (read it somewhere)
Everytime I get the Error that the .zip is corrupt. Checksums of all the files are ok...
Has anyone an idea what else I can do? I would actually be fine with lineage 16 if I could just get my HTC Edge Sense back (
Thanks in advance for your help
Headcannon: what if the problem ia for some reason the twrp? Could i somehow flash the stock rom without going through the TWRP?
I am not talking about removing it. I am talking about somehow flashing without using it. Maybe via adb or odin?
Then the stockrom should be able to install. If something goes wrong I can still boot into recovery and use TWRP to get LOS16 back.
Ok so since I read somewhere that on the pixels root access was necessary to get HTC Edge Sense running I installed Lineage 16, added GAPPS and then used Magisk to get root access.
I still can't install HTC Edge Sense. I even downloaded the apk and pushed it onto the phone but the install always stops and tells me it can't finish
So for now I can neither have stock rom nor Edge Sense - any suggestions because I am slowly running out of ideas

Categories

Resources