Hi all
I have a Smasung Galaxy note 3 (sm-n9005 htle)
I allready rooted it and installed the TWRP 3.0.2-0. That worked fine.
Now i tried to install some custom rom... it doesent work... it shows me the error 7 ...
so i googled for this error. and found a fix.. so i deleted the first lines in the updater-script... after that i tried it again. But it ditent work. It fails with the massage: could not found the binary file.
I wiped and formated the Smartphone as well.
I spend allready the whole day to install any custom rom...
Im really sad about this... maybe someone can help me.
And sorry for my bad english.
Did you confirm the phone's model # in download before flashing TWRP?
audit13 said:
Did you confirm the phone's model # in download before flashing TWRP?
Click to expand...
Click to collapse
Do you mean, that i downloaded the TWRP for my device model? Yes i did
Otherwise what do you mean?
Before flashing anything, especially if I got the phone used, I boot the phone into download just to confirm that the model # matches the label under the battery.
Only after confirming the model # in download do I start flashing files to the phone.
Does the error 7 happen with all custom ROMs?
audit13 said:
Before flashing anything, especially if I got the phone used, I boot the phone into download just to confirm that the model # matches the label under the battery.
Only after confirming the model # in download do I start flashing files to the phone.
Does the error 7 happen with all custom ROMs?
Click to expand...
Click to collapse
The Modelnumber in the downloadmode and the number under the battery are the same.
Yes i tried maybe five custom roms.
Fail is usually user fails to read instructions .
Error one .
I allready rooted it and installed the TWRP 3.0.2-0. That worked fine.
Now i tried to install some custom rom... it doesent work... it shows me the error 7 ...
Aroma installer does not work and thats why instructions tell you to use the older TWRP .
Instructions .
>>>Get a good recovery. TWRP recovery recommended, 2.8.7.0. Newer versions are not supported
>>>TWRP recovery recommended, 2.8.7.0. Newer versions are not supported
JJEgan said:
Fail is usually user fails to read instructions .
Error one .
I allready rooted it and installed the TWRP 3.0.2-0. That worked fine.
Now i tried to install some custom rom... it doesent work... it shows me the error 7 ...
Aroma installer does not work and thats why instructions tell you to use the older TWRP .
Instructions .
>>>Get a good recovery. TWRP recovery recommended, 2.8.7.0. Newer versions are not supported
>>>TWRP recovery recommended, 2.8.7.0. Newer versions are not supported
Click to expand...
Click to collapse
Thanks for it.
I tried now the TWRP 2.8.7.0. For my device there are two versions. The twrp-2.8.7.0-hlte-4.3.img.tar and twrp-2.8.7.0-hlte-4.4.img.tar.
First i tried now the twrp-2.8.7.0-hlte-4.4.img.tar but still gives me an error :
Updating partition deteils...
... done
Full SELinux support is present.
MTP Enabled
Installing '/external_sd/cm-23.1-20161016-NIGHTLY-hlte.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
Can't install this package on top of incompatible data.
Please try another package or run factory reset
E:Error executing updater binary in zip '/external_sd/cm-23.1-20161016-NIGHTY-hlte.zip'
Updating partition details...
...done
The other version of TWRP doesent work. It ends up in a reboot circle.
Try Philz Recovery .
That fails flash a clean stock rom
BUT FIRST
.Installing '/external_sd/cm-23.1-20161016-NIGHTLY-hlte.zip'
Can't install this package on top of incompatible data.
Please try another package <<<< or run factory reset >>>
---------- Post added at 11:57 AM ---------- Previous post was at 11:43 AM ----------
You would be best flashing stock rom through Odin and then if you have problems post exact details .
What rom flashed etc .
JJEgan said:
Try Philz Recovery .
That fails flash a clean stock rom
BUT FIRST
.Installing '/external_sd/cm-23.1-20161016-NIGHTLY-hlte.zip'
Can't install this package on top of incompatible data.
Please try another package <<<< or run factory reset >>>
---------- Post added at 11:57 AM ---------- Previous post was at 11:43 AM ----------
You would be best flashing stock rom through Odin and then if you have problems post exact details .
What rom flashed etc .
Click to expand...
Click to collapse
Hell Yeah!
Thanks a lot it finaly worked with Philz Recovery...
I wiped my phone several times before intsalling the rom... but with Philz Recovery it worked!
Thanks so much! Im really happy now... its not the first device with a custom rom... but the first with problems
Thanks thanks thanks
Related
I'm getting this error when trying to flash lollipop roms. I can flash Kitkat roms fine as I'm currently running xdabbeb VS982.5 1.0.0 (G3 rom), but it won't let me flash any lollipop rom. I installed twrp via the autorec program which installs 2.7.0.0 then I updated twrp within twrp with the flashable zip.
Please help
Thank you
Anyone?
Seriously no one knows? What is everyone else using that is flashing the latest 5.0.2 roms?
What am I getting this error?
Please help
Possible Fix
I've also had this problem. The only way I can seem to fix it is to also download the .md5 along with the rom itself. Just make sure its in the same folder as the rom. Everytime I have that problem with TWRP this seems to fix it. Let me know if it works for you!
Edit: Also I forgot to mention, if one isn't available to download I can help with that.
Thanks for the suggestion. I'll give it a try. If there is no. Md5 what do I do then?
All you need to do if it comes to that is download an md5 checker on your computer. Just curious, what rom are you trying to flash?
I tried resurrection remix and liquid lollipop roms. I had no issues with the initial 5.0 lollipop roms so I'm not sure what changed with 5.0.2.
So the md5 checker generates the .Md5 then you just put that on the SD card with the rom?
Resurrection remix should have an md5 on the download page right below the rom itself.
derekmt95 said:
All you need to do if it comes to that is download an md5 checker on your computer. Just curious, what rom are you trying to flash?
Click to expand...
Click to collapse
Can you point me to the program to use on my computer? Do I just load the .zip file in the program to generate the .md5sum file then put both the zip and the .md5sum file on the sdcard before flashing?
Thanks
derekmt95 said:
I've also had this problem. The only way I can seem to fix it is to also download the .md5 along with the rom itself. Just make sure its in the same folder as the rom. Everytime I have that problem with TWRP this seems to fix it. Let me know if it works for you!
Edit: Also I forgot to mention, if one isn't available to download I can help with that.
Click to expand...
Click to collapse
Nope, I downloaded the md5 file along with the zip and I'm still getting the same "error executing updater binary in zip".
Any other suggestion? How is no one else having this same issue? I'm using the latest version of TWRP 2.8.3.1 probably like most people. I don't understand.
xxNiradxx said:
Nope, I downloaded the md5 file along with the zip and I'm still getting the same "error executing updater binary in zip".
Any other suggestion? How is no one else having this same issue? I'm using the latest version of TWRP 2.8.3.1 probably like most people. I don't understand.
Click to expand...
Click to collapse
Try to reflash the TWRP.. or maybe is something wrong with the zip file
Use the TWRP compiled by blastagator
Nope, still getting same error with latest twrp.
Finally got it working. I downgraded TWRP to 2.7.0.0 and the lollipop roms are flashing fine now.
Thanks everyone for your help.
xxNiradxx said:
Finally got it working. I downgraded TWRP to 2.7.0.0 and the lollipop roms are flashing fine now.
Thanks everyone for your help.
Click to expand...
Click to collapse
How did you downgrade because I cannot seem to find a way to do it.
TheAnonymousButler said:
How did you downgrade because I cannot seem to find a way to do it.
Click to expand...
Click to collapse
just run AutoRec again and you are all set.
LG G2 cm-11 M12 : Error executing updater binary in zip (TWRP)
kashif87 said:
just run AutoRec again and you are all set.
Click to expand...
Click to collapse
Hi, I am having the same problem. Actually my LG G2 was stuck in boot loop with secure boot error. I used SRK tool to flash the partition files as well as TWRP recovery 2.8.6.1. I have wiped everything and there is no OS installed. I am stuck in TWRP recovery screen [cannot downgrade /upgrade]. I am using and OTG cable to flash the cm-11 custom ROM but it is giving me the same error. Can anyone help ?? It has been 10 days I am trying and my phone is dying please help...
Thanks in advance...
before flash 5.1.1 aosp lollipop rom u must to flash first lollipop bootstack
Hi,
I am assuming the reply was for me. Actually I am not installing lollipop. I am going for kitkat but nothing is working now. I have tried cm-10.2, cm-11 M12, cm-11 M7 but all are showing "error executing updater binary in zip". Please if someone can help me out....
Thanks is advance....
@[email protected] i think kk aosp room need jb bootleader
Hello everyone,
I am running a D802 on stock Lollipop and installed TWRP 2.8.6.0 via AutoRec. Now I booted into recovery, wiped System and Cache and got the Error message when installing CrDroid (Marshmallow 6.0.1). Now I tried installing TWRP 3.0.2.0, which succeeded and then downloaded the twrp 2.7.0.0 zip to try that as the ROM still wouldnt install. But it wont install the older TWRP. So I am asking for help to either
1) Install TWRP 2.7.0.0
or
2) Delete the getprop lines from updater-script (after I removed them I get an error 6 so i probably removed too much?)
Thank you in advance
(Guide for Error 7: http://forum.xda-developers.com/showthread.php?t=2522762)
EDIT: Someone said installing another Kernel might allow installation of the ROMs. Which Kernel could work for my phone?
EDIT 2: When flashing TWRP 2.7.0.0 it says "assert failed: run_program("/tmp/loki.sh")==0". So what exactly am I missing on my phone? Is Loki the MM Bootloader?
EDIT 3: Could it be that the build.prop was deleted when I wiped system? Would be weird if that was the cause, but I simply dont know..
Edit: Booted in Downloa Mode and flashed v30D KDZ with the 2014 LG Flashtool. Works with Stock ROM for now
I successfully rooted thus t-mobile leon a few weeks ago. I instaed the latest twrp without a problem.. I can not seem to manage a rom flash. The last error i got said invalid zip.. Or zip file corrupt.. I wiped cache and delvic and i also done a clean wipe.. I have been trying to flash cm-12.1-20150906-unofficial-ms345 . also says check md5. No md5 file found. Then reboots back to factory.. Frusterating..
Bender0112 said:
I successfully rooted thus t-mobile leon a few weeks ago. I instaed the latest twrp without a problem.. I can not seem to manage a rom flash. The last error i got said invalid zip.. Or zip file corrupt.. I wiped cache and delvic and i also done a clean wipe.. I have been trying to flash cm-12.1-20150906-unofficial-ms345 . also says check md5. No md5 file found. Then reboots back to factory.. Frusterating..
Click to expand...
Click to collapse
Check md5 of the download before flashing to make sure it matches
Sent from my LG-H901 using Tapatalk
The binary error is due to there being a couple different versions of this phone.
We've got a c50, ms345, and a h345 recovery. The metro pcs ROM is only built to flash on the metro pcs recovery since lollipop looks at the device name and not the hardware set when flashing ROMs on certain recoveries.
here is a recovery that should work.
w w w .android filehost. c o m/?fid=24052804347772357
---------- Post added at 12:20 AM ---------- Previous post was at 12:16 AM ----------
i would also recomend using xenonhd
I have tmobile version and the only twrp that works is the blue twrp from cm 12.1 thread. Itll flash cm and xenonHD and anything else. Must use mpcs version of roms though. I'm on xenonHD and it's smoking fast
Sent from my XenonHD-phone using Tapatalk
Couple days back, I factory reset my phone and when I went to upgrade it back to Lollipop it got stuck on my splash screen and never came out of it. While I do have TWRP installed, I didn't have the foresight to do a backup before upgrading and have tried flashing both cm-12.1.-20160627 and cm-13.0-20160723 both for the SM-G360H model.
Each time I attempt though it errors out with:
This package is for device: SM-G360H,SM-G360HU,core33g,core33gdd,core33gdx; this device is coreprimelte.
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/Download/*whichever zip file*'
I'm 99% sure my phone is SM-G360H because I checked before installing TWRP roughly a month back but it's been a long week and I very well have missed something important in my haste to get my phone up and running again.
Any help or links are really appreciated.
xattle said:
Couple days back, I factory reset my phone and when I went to upgrade it back to Lollipop it got stuck on my splash screen and never came out of it. While I do have TWRP installed, I didn't have the foresight to do a backup before upgrading and have tried flashing both cm-12.1.-20160627 and cm-13.0-20160723 both for the SM-G360H model.
Each time I attempt though it errors out with:
This package is for device: SM-G360H,SM-G360HU,core33g,core33gdd,core33gdx; this device is coreprimelte.
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/Download/*whichever zip file*'
I'm 99% sure my phone is SM-G360H because I checked before installing TWRP roughly a month back but it's been a long week and I very well have missed something important in my haste to get my phone up and running again.
Any help or links are really appreciated.
Click to expand...
Click to collapse
Dude u should make sure that ur device is 100% sm g360h
Because wrong rom can mess up ur phone
SM G360H dont have 4g .check if it is like that in ur mobile network. You can also compare other diff too
If u are sure its not lte
Then change ro.product.device and ro.build.product to sm g360h/core33g in ur buildprop using es fileexplorer and flash the rom
I had the same problem before here how i fixed it ..i installed stock rom usin odin then i installed cm11 first then cm13... ..i counldn't install cm12 or cm13 directly from stock rom too without getting the error 7 . just make sure to install cm 11 first ...i know it does not make sense but that how i fixed now im using cm13
---------- Post added at 04:04 PM ---------- Previous post was at 04:00 PM ----------
I forget ..just make sure that you have a clean download of the rom so the zip file is not corrupted.
try with CWM - not TWRP a was happy without "error 7"
Need help Urgent!!!!!!!!
I had rooted my phone successfully 1 year ago but while installing xposed privacy it asked unlock bootloader and changed to twrp recovery 2.8.7.0 but some problem occured i can not go after asus logo so i visited customer care and he installed kitkat 2.22.40.54 version with out locking that bootloader. After succesful usage of 1 year my settings option not opened it always show "unfortunately. com.android settings has stopped" so i tried to flash a new rom i wiped cache and data unfortunately system also.
so that im not able to flash new rom errors occurs are
1. E:unknown file system: 'osip'
E:unknown file system: 'osip'
E:unknown file system: 'osip'
E: Invalid block device on '/dev/block/zram0one......................................
2. E: Unable to locate page (system_readonly)
3. no MD5 file found even i downloaded the firmware from asus support (2.22.40.540 as well as 2.21.40.44)
4. assert failed: getprop("ro.build.asus.sku")=="ww" return code 8
5. E: Error executing updater binary in zip '/external_sd/.....................zip
(** note: i had not enabled usb debugging
when i try to flash rom using adb sideload it is not showing in the list even it is connecting as media transfer
through otg also not going i dont know it is not showing in the recovery)
thats the problem guys please help me out of this
ajay019 said:
Need help Urgent!!!!!!!!
I had rooted my phone successfully 1 year ago but while installing xposed privacy it asked unlock bootloader and changed to twrp recovery 2.8.7.0 but some problem occured i can not go after asus logo so i visited customer care and he installed kitkat 2.22.40.54 version with out locking that bootloader. After succesful usage of 1 year my settings option not opened it always show "unfortunately. com.android settings has stopped" so i tried to flash a new rom i wiped cache and data unfortunately system also.
so that im not able to flash new rom errors occurs are
1. E:unknown file system: 'osip'
E:unknown file system: 'osip'
E:unknown file system: 'osip'
E: Invalid block device on '/dev/block/zram0one......................................
2. E: Unable to locate page (system_readonly)
3. no MD5 file found even i downloaded the firmware from asus support (2.22.40.540 as well as 2.21.40.44)
4. assert failed: getprop("ro.build.asus.sku")=="ww" return code 8
5. E: Error executing updater binary in zip '/external_sd/.....................zip
(** note: i had not enabled usb debugging
when i try to flash rom using adb sideload it is not showing in the list even it is connecting as media transfer
through otg also not going i dont know it is not showing in the recovery)
thats the problem guys please help me out of this
Click to expand...
Click to collapse
Ok so as per my understanding , you have unlocked bootloader .
You also have custom recovery twrp 2.8.7 installed . Right ?
Since you wipe system , your phone is without any os right now .
So now what you do is download any stock modified rom for your device .
Download latest twrp by xanwar . Flash the twrp zip (by xanwar)from twrp 2.8.7 (already installed ).
Voila ! Now you can flash any custom rom or stock based modified roms .
I don't know this is what you asking
Boomshiva said:
Ok so as per my understanding , you have unlocked bootloader .
You also have custom recovery twrp 2.8.7 installed . Right ?
Since you wipe system , your phone is without any os right now .
So now what you do is download any stock modified rom for your device .
Download latest twrp by xanwar . Flash the twrp zip (by xanwar)from twrp 2.8.7 (already installed ).
Voila ! Now you can flash any custom rom or stock based modified roms .
I don't know this is what you asking
Click to expand...
Click to collapse
yes i unlocked bootloader and i have custom recovery twrp 2.8.7.0 installed but here the problem is i didnt enabled usb debugging mode so that i'm not able to flash and the errors are as above mentioned. modified rom you are saying means i'm using 2.22.40.54 kitkat so may i able to install lollipop or higher version.one more thing i dont know what these errors mean..
ajay019 said:
yes i unlocked bootloader and i have custom recovery twrp 2.8.7.0 installed but here the problem is i didnt enabled usb debugging mode so that i'm not able to flash and the errors are as above mentioned. modified rom you are saying means i'm using 2.22.40.54 kitkat so may i able to install lollipop or higher version.one more thing i dont know what these errors mean..
Click to expand...
Click to collapse
Ok . I understand now .
1)donwlaod latest twrp by xanwar . And flash it. So now you have latest recovery installed on your device .:fingers-crossed:
2)download gecko premium rom from Android development section here on xda . Place it on SD card .
3)reboot to recovery , wipe everything except SD card . (You will lose everything from your phone .)
4)if step 3 gives error then format data not wipe .
5)repeat step 3
6)reboot to recovery now .
Flash the rom that you downaoded (gecko premium )
7)reboot system .
8) do this first then report back .
Boomshiva said:
Ok . I understand now .
1)donwlaod latest twrp by xanwar . And flash it. So now you have latest recovery installed on your device .:fingers-crossed:
2)download gecko premium rom from Android development section here on xda . Place it on SD card .
3)reboot to recovery , wipe everything except SD card . (You will lose everything from your phone .)
4)if step 3 gives error then format data not wipe .
5)repeat step 3
6)reboot to recovery now .
Flash the rom that you downaoded (gecko premium )
7)reboot system .
8) do this first then report back .
Click to expand...
Click to collapse
one more mistake bro i didnt find xanwar twrp 3.0.2.0 so i browsed for another one which is 3.0-m-4.0 and flashed it successfully but reboot in recovery is not going then powered off the phone and started to go into recovery mode but in recovery mode touch is not working so only hanged i repeatedly switched off and on but same result. so what to do now.....? i think im having no other choices than using droidboot but adb side load is not working bz i didnt enabled usb debugging mode. in pc it is showing connected to pc until i started adb when i started it disappearing.
ajay019 said:
one more mistake bro i didnt find xanwar twrp 3.0.2.0 so i browsed for another one which is 3.0-m-4.0 and flashed it successfully but reboot in recovery is not going then powered off the phone and started to go into recovery mode but in recovery mode touch is not working so only hanged i repeatedly switched off and on but same result. so what to do now.....? i think im having no other choices than using droidboot but adb side load is not working bz i didnt enabled usb debugging mode. in pc it is showing connected to pc until i started adb when i started it disappearing.
Click to expand...
Click to collapse
I don't understand the logic behind not enabling usb debugging !
No need for all that .
If using windows then make sure the all driver shows up when you enter into fastboot mode .
Check from control panel of your PC . If not then reinstall the drivers . It must show asus composite ...........Blah Blah blah ...Android bridge interface .(well i use Linux so dont recall properly ).
Once the desired drivers are present you are good to go ahead .And flash proper twrp .And do the rest .
Bottom line :check drivers
Flash the latest twrp (24 July build) link below
https://www.androidfilehost.com/?w=files&flid=52033
Boomshiva said:
I don't understand the logic behind not enabling usb debugging !
No need for all that .
If using windows then make sure the all driver shows up when you enter into fastboot mode .
Check from control panel of your PC . If not then reinstall the drivers . It must show asus composite ...........Blah Blah blah ...Android bridge interface .(well i use Linux so dont recall properly ).
Once the desired drivers are present you are good to go ahead .And flash proper twrp .And do the rest .
Bottom line :check drivers
Flash the latest twrp (24 July build) link below
https://www.androidfilehost.com/?w=files&flid=52033
Click to expand...
Click to collapse
thank you bro successfully flashed new rom GECKO-premium-ROM-3.24.40.87-v1.0. problem solved. may i know how to install and activate xposed installer for this version and one more thing may i change the recovery any time with out disturbing os?
ajay019 said:
thank you bro successfully flashed new rom GECKO-premium-ROM-3.24.40.87-v1.0. problem solved. may i know how to install and activate xposed installer for this version and one more thing may i change the recovery any time with out disturbing os?
Click to expand...
Click to collapse
Flash xposed zip . Sdk21 v86 works flawlessly ,
Then download the apk for xposed and install it as normal apk you can change recovery anytime but be sure that you flash your devices twrp only not others .
So Ive been trying to install multiple different pie roms and each one gives me error 7 during the install with twrp.
Ive updated twrp to the newest 3.2.3, I read that could be the issue.
I was using nolimits rom but due to no future updates I wanted to try something different.
Im sure its something simple, but I cannot seem to find any resources.
I even tried deleting the assert lines in the rom zip, still same error.
Im at a complete loss.
I just put nolimits back on it so I at least have a working phone.
Any info is appreciated
cblock said:
So Ive been trying to install multiple different pie roms and each one gives me error 7 during the install with twrp.
Ive updated twrp to the newest 3.2.3, I read that could be the issue.
I was using nolimits rom but due to no future updates I wanted to try something different.
Im sure its something simple, but I cannot seem to find any resources.
I even tried deleting the assert lines in the rom zip, still same error.
Im at a complete loss.
I just put nolimits back on it so I at least have a working phone.
Any info is appreciated
Click to expand...
Click to collapse
Please post your question only once https://forum.xda-developers.com/oneplus-5/help/updating-to-beta-22-t3879346/post78437012
Please answer some questions:
Which twrp (file name)?
Which xXx rom(file name)?
Decrypted or encrypted storage?
Which rom do you want to install (exact steps)?
Sorry for the double post, Ive been super frustrated with it.
Right now im running twrp 3.2.3.0 from the twrp website, I have tried codeworkx with no change.
I was trying multiple different roms, but for the sake of troubleshooting I was trying PixelExperience Cheeseburger 9.0
Most of the installs attempted have been through twrp so Im guessing decrypted.
And I was following the steps on the roms thread.
Factory wipe, delvik and data, then attempt the install.
cblock said:
Sorry for the double post, Ive been super frustrated with it.
Right now im running twrp 3.2.3.0 from the twrp website, I have tried codeworkx with no change.
I was trying multiple different roms, but for the sake of troubleshooting I was trying PixelExperience Cheeseburger 9.0
Most of the installs attempted have been through twrp so Im guessing decrypted.
And I was following the steps on the roms thread.
Factory wipe, delvik and data, then attempt the install.
Click to expand...
Click to collapse
Decrypted or encrypted storage? Which rom do you want to install now? Please use latest codeworkx recovery.
Which xXx rom exactly you're coming from(file name)?
Ok, I am coming from xXx_NoLimits_12.0_OP5_Oxygen_5.1.3_full and Id love to install OxygenOS Open Beta 22 Full
I can certainly install the codeworkx recovery if needed.
How can I tell if I am encrypted or not? Ive always just left things as default
Btw thanks for your help
cblock said:
Ok, I am coming from xXx_NoLimits_12.0_OP5_Oxygen_5.1.3_full and Id love to install OxygenOS Open Beta 22 Full
I can certainly install the codeworkx recovery if needed.
How can I tell if I am encrypted or not? Ive always just left things as default
Btw thanks for your help
Click to expand...
Click to collapse
Just follow instructions in first post for clean installation, make sure you made backups: https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-beta-1-android-oreo-t3710003
Encryption means, you cannot access your internal storage without entering a pin when starting twrp or accessing the devices memory from outside.
So Ive followed the new install instructions from start to finish, and I cannot get past the OS flash.
Continuing to receive error 7.
Also receiving cannot mount /vendor as well
cblock said:
So Ive followed the new install instructions from start to finish, and I cannot get past the OS flash.
Continuing to receive error 7.
Also receiving cannot mount /vendor as well
Click to expand...
Click to collapse
For the error 7 make sure you downloaded the correct files, without download issues(maybe use checksum). have you removed compatibility.zip from the OB22 rom zip with either 7zip or total commander?
For vendor partition error try to mount vendor partition within twrp manually, if there's no checkbox, you need to flash what I suggested you here https://forum.xda-developers.com/oneplus-5/help/updating-to-beta-22-t3879346/post78437012
Earlier open betas created this vendor partion. You can try with OB13.
I have same problem, except I tried to fix it by flashing OB19 firmware and radio zip. Now when I boot the recovery I don't get "no vendor partition" and the bootloader unlocked error, but when I try to flash ANY rom (stable 5.1.4 /open beta 19 / PIE ), the system and vendor partitions would patcg unconditionally, but I get no OS error and the device reboots to recovery. Please help.
Ps: I have magisk and TWRP 3.2.3, and tried both clean flashing and dirty flashing. the unlocked bootloader error changed even after restoring the NAND backup. I had already removed the compatibility zip from the Pie zip. I tried blu spark and codeworx versions of twrp 3.2.3
yohouse2 said:
I have same problem, except I tried to fix it by flashing OB19 firmware and radio zip. Now when I boot the recovery I don't get "no vendor partition" and the bootloader unlocked error, but when I try to flash ANY rom (stable 5.1.4 /open beta 19 / PIE ), the system and vendor partitions would patcg unconditionally, but I get no OS error and the device reboots to recovery. Please help.
Ps: I have magisk and TWRP 3.2.3, and tried both clean flashing and dirty flashing. the unlocked bootloader error changed even after restoring the NAND backup. I had already removed the compatibility zip from the Pie zip. I tried blu spark and codeworx versions of twrp 3.2.3
Click to expand...
Click to collapse
Same as my answer above. Oneplus published every open beta as an update(even when it's a full rom) of the previous version hence when your last open beta was 10 and you want 22 you missed several in between(this was an example!).
FINALLY got it all to work.
Apparently I had issues with the firmware, had to go back and install codeworx 15.1 firmware, after that it seems to be good to go.
THANK YOU Strongst.
cblock said:
FINALLY got it all to work.
Apparently I had issues with the firmware, had to go back and install codeworx 15.1 firmware, after that it seems to be good to go.
THANK YOU Strongst.
Click to expand...
Click to collapse
How did you fix it? Can you explain what you mean by codeworx firmware? Could you provide link for file or guide?
This is the firmware from Codeworkx
https://sourceforge.net/projects/ch...firmware/firmware_5.1.7_oneplus5.zip/download.
You might have to go to an older version of twrp as well, just to get this installed.
strongst said:
Same as my answer above. Oneplus published every open beta as an update(even when it's a full rom) of the previous version hence when your last open beta was 10 and you want 22 you missed several in between(this was an example!).
Click to expand...
Click to collapse
I flashed open beta 13 & 19, and stable 5.1.4, all failed, what should I try?
---------- Post added at 07:40 PM ---------- Previous post was at 07:37 PM ----------
cblock said:
This is the firmware from Codeworkx
https://sourceforge.net/projects/ch...firmware/firmware_5.1.7_oneplus5.zip/download.
You might have to go to an older version of twrp as well, just to get this installed.
Click to expand...
Click to collapse
Which twrp version and developer? And after this can I flash Pie directly or should I install something before it? Did you dirty flash or did you use clean install? Sorry for too many questions but I tried it many times and am frustrated that it didn't work, but you fixing it gives me hope.
yohouse2 said:
I flashed open beta 13 & 19, and stable 5.1.4, all failed, what should I try?
Click to expand...
Click to collapse
What exactly means "failed"? Which error? Screenshot maybe? And from which oxygenOS you tried to update?
Also you need to flash magisk after flashing oxygenOS to make twrp sticky. Also a format of internal storage may be necessary to solve a boot problem.
The Unlocked Bootloader Warning screen is normal cause it's a warning when you unlock your bootloader, if it changed, it's due to changes made by oneplus some time ago, they changed it.
I was able to flash pie directly after updating the firmware.
twrp 3.2.3 should work
strongst said:
What exactly means "failed"? Which error? Screenshot maybe? And from which oxygenOS you tried to update?
Also you need to flash magisk after flashing oxygenOS to make twrp sticky. Also a format of internal storage may be necessary to solve a boot problem.
The Unlocked Bootloader Warning screen is normal cause it's a warning when you unlock your bootloader, if it changed, it's due to changes made by oneplus some time ago, they changed it.
Click to expand...
Click to collapse
By failed I mean that I would wipe the system partition for clean flash, install the ROM zip, which would run but say patching system and vendor partitions unconditionally, then when I want to reboot it says warning no OS. Continuing to reboot gets me automatically back to recovery.
I tried updating from xXx 5.1.2
yohouse2 said:
By failed I mean that I would wipe the system partition for clean flash, install the ROM zip, which would run but say patching system and vendor partitions unconditionally, then when I want to reboot it says warning no OS. Continuing to reboot gets me automatically back to recovery.
I tried updating from xXx 5.1.2
Click to expand...
Click to collapse
Did you try the firmware link I posted earlier?
cblock said:
Did you try the firmware link I posted earlier?
Click to expand...
Click to collapse
Will try in just a minute
---------- Post added at 09:23 PM ---------- Previous post was at 09:05 PM ----------
cblock said:
Did you try the firmware link I posted earlier?
Click to expand...
Click to collapse
still getting system patching unconditionally
Does it get stuck with an error?
Its suppose to say that