TWRP recovery error 7 - Zuk Z1 Q&A, Help & Troubleshooting

I flashed this official lineage os for zuk z1 , which is the first build but I am getting error 7 in TWRP while flashing and the installation is aborted. I am attaching screenshots taken of the error I encountered, please kindly check and give me any solution to this problem
I am using TWRP 3.0.2
Last ROM :-Official CM13 18-12-2016 nightly

turnoff signature verification in twrp setting

singh.9yashpal9 said:
turnoff signature verification in twrp setting
Click to expand...
Click to collapse
It won't work..i'm facing the exact same problem with the same version of the twrp recovery and i did try turning of the zip verification too.

singh.9yashpal9 said:
turnoff signature verification in twrp setting
Click to expand...
Click to collapse
Tried turning off zip signature verification, it didn't help... Then I googled the problem, I found out that we should modify code in update_script... Decompress the file, that is
1) unzip the nightly zip
2) go into META-INF>com>Google>Android
There you'll find two files , select updater-script and rename it to updater-script.txt
It will convert into txt file so you can edit it.
3) delete the assert commands till last semicolon or delete all from assert till you see ”mount(ext......” (don't delete​ Mount....)
4) save the changes. Then again rename it that is from updater-script.txt to updater-script..
5) compress the file again into zip format.
There you go, you can flash this without any errors.... I tried this , it works fine...
Anyone have any other solution? No one's facing this issue?
I read that old bootloader is also one of the problem to get this issue? How to update bootloader?

tanmeshn said:
I flashed this official lineage os for zuk z1 , which is the first build but I am getting error 7 in TWRP while flashing and the installation is aborted. I am attaching screenshots taken of the error I encountered, please kindly check and give me any solution to this problem
I am using TWRP 3.0.2
Last ROM :-Official CM13 18-12-2016 nightly
Click to expand...
Click to collapse
http://forum.xda-developers.com/zuk-...overy-t3572069
Try this Version of TWRP, What i figured is like some versions of twrp do cause some problems,..
STEPS :-
1.) Download that Image file
2.) YOU DON'T HAVE TO WIPE ANYTHING IF YOU INSTALLED ANY ROM, BECAUSE YOU ARE JUST CHANGING YOUR TWRP VERSION.
3.) IT'S JUST THE WAY YOU FLASH A ZIP FILE BUT HERE WHEN YOU GO TO THE INSTALL OPTION BOTTOM RIGHT CHANGE INTO INSTALL IMAGE.
4.) SEARCH FOR THE IMAGE AND FLASH IT. AND THEN REBOOT THEN REBOOT INTO RECOVERY AND HAVE FUN FLASHING OFFICIAL LINEAGE.
----SENT FROM LINEAGE ZUK.

tanmeshn said:
Tried turning off zip signature verification, it didn't help... Then I googled the problem, I found out that we should modify code in update_script... Decompress the file, that is
1) unzip the nightly zip
2) go into META-INF>com>Google>Android
There you'll find two files , select updater-script and rename it to updater-script.txt
It will convert into txt file so you can edit it.
3) delete the assert commands till last semicolon or delete all from assert till you see ”mount(ext......” (don't delete​ Mount....)
4) save the changes. Then again rename it that is from updater-script.txt to updater-script..
5) compress the file again into zip format.
There you go, you can flash this without any errors.... I tried this , it works fine...
Anyone have any other solution? No one's facing this issue?
I read that old bootloader is also one of the problem to get this issue? How to update bootloader?
Click to expand...
Click to collapse
Well,turning off signature verification worked for me after i clean flashed over unofficial los 14.1 and using twrp 3.1.0.0...

This worked for me,give a try
1.Wipe-> apvance wipe system dalvik data cache
2.flash unofficial recursion remix rom
3.Wipe-> apvance wipe system dalvik data cache
4.flash offical cm /los
5.flash gapps

ameyau said:
This worked for me,give a try
1.Wipe-> apvance wipe system dalvik data cache
2.flash unofficial recursion remix rom
3.Wipe-> apvance wipe system dalvik data cache
4.flash offical cm /los
5.flash gapps
Click to expand...
Click to collapse
Is this the only way?? There's no other way to do it without wiping data?

tanmeshn said:
Is this the only way?? There's no other way to do it without wiping data?
Click to expand...
Click to collapse
I installed latest TWRP recovery 3.1.0, but it didn't help, I am getting that same error 7.. never got this error before only for official lineage os I am getting this error....

tanmeshn said:
Is this the only way?? There's no other way to do it without wiping data?
Click to expand...
Click to collapse
I shall recommend u to create a back up in twrp..
After that follow above steps
And after 1st boot..restore only data part...
If that dont work u have complete backup u can restore any time

tanmeshn said:
I installed latest TWRP recovery 3.1.0, but it didn't help, I am getting that same error 7.. never got this error before only for official lineage os I am getting this error....
Click to expand...
Click to collapse
Did u installed zui?

ameyau said:
Did u installed zui?
Click to expand...
Click to collapse
Ya.. I had installed ZUI 2.5.306... It's because of it?

tanmeshn said:
Ya.. I had installed ZUI 2.5.306... It's because of it?
Click to expand...
Click to collapse
Yep there is a mismatch... Are u using mokee rom??

From stock cos12.1 I came to cm13 ... Then I flashed many roms like RR, nuclear ROM, mokee, unofficial LOS even ZUI.
Before flashing official LOS I had official cm13 nightly.. but before flashing Los I wanted to try ZUI nougat so I took backup of Cm13 ROM through TWRP then clean flashed ZUI 2.5.306 based on nougat. I didn't find this ROM interesting so I restored my previous ROM that is CM13...
Then after few days I did clean install of this official Lineage OS nightly and started getting this error 7 while installing...

ameyau said:
Yep there is a mismatch... Are u using mokee rom??
Click to expand...
Click to collapse
Just check my reply no.14

tanmeshn said:
From stock cos12.1 I came to cm13 ... Then I flashed many roms like RR, nuclear ROM, mokee, unofficial LOS even ZUI.
Before flashing official LOS I had official cm13 nightly.. but before flashing Los I wanted to try ZUI nougat so I took backup of Cm13 ROM through TWRP then clean flashed ZUI 2.5.306 based on nougat. I didn't find this ROM interesting so I restored my previous ROM that is CM13...
Then after few days I did clean install of this official Lineage OS nightly and started getting this error 7 while installing...
Click to expand...
Click to collapse
Internal data will be safe
Titanium backup can help to backup and restore... But unfortunately u have to clean install.. Unofficial rr rom (nougat)1st and then official Los.

ameyau said:
Titanium backup can help to backup and restore... But unfortunately u have to clean install.. Unofficial rom 1st and then official Los
Click to expand...
Click to collapse
I have just found some firmware for nougat, just check it out if it can help solve me my problem..https://www.androidfilehost.com/?w=f...e22a8afb52d809
Just tell me if it's firmware with latest bootloader

Check this link.. https://www.androidfilehost.com/?fid=745425885120705241

tanmeshn said:
Check this link.. https://www.androidfilehost.com/?fid=745425885120705241
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=385035244224405398 try this one..
I am not a developer so i cant suggest u on this link u posted...
I can suggest u another method.. It will work..
Backup cm13 with data in twrp..
Clean install unofficial(rr/los) rom nougat one..
Restore the back up
Now u can flash official los..
Hope this will help u

ameyau said:
https://www.androidfilehost.com/?fid=385035244224405398 try this one..
I am not a developer so i cant suggest u on this link u posted...
I can suggest u another method.. It will work..
Backup cm13 with data in twrp..
Clean install unofficial(rr/los) rom nougat one..
Restore the back up
Now u can flash official los..
Hope this will help u
Click to expand...
Click to collapse
I'll try this once.. I hope it works out.. thanks

Related

[NEED HELP]Phone stuck on "Warning:Bootloader Unlocked"...Urgent plz

Hey sombody plz help me to get through this,I installed the OTA then I unlocked bootlocker and installed the custom recovery twrp 2.8.7v2 ....then I tried to install the SuperSU....but after flashed it through twrp,I was stucked at "Warning Bootlocker Unlocked" screen for like 15 min,so then I tried to clear cache and then reboot....But that also not help,Then i tried format all the data and tried to to strt in factory mode.but still stucked at same screen.Now what should I do to get into the phone ?PLz ....its urgent
Well the thing you could do is factory resetting via TWRP or you could download a new ROM like CM 12.1 that you can find in the original android developer section and flash it with TWRP, your phone would boot up now. Keep in mind that you will lose everything.
anks095 said:
Hey sombody plz help me to get through this,I installed the OTA then I unlocked bootlocker and installed the custom recovery twrp 2.8.7v2 ....then I tried to install the SuperSU....but after flashed it through twrp,I was stucked at "Warning Bootlocker Unlocked" screen for like 15 min,so then I tried to clear cache and then reboot....But that also not help,Then i tried format all the data and tried to to strt in factory mode.but still stucked at same screen.Now what should I do to get into the phone ?PLz ....its urgent
Click to expand...
Click to collapse
The same happend to me, you must have installed the wrong SU version, just reflash stock firmware via fastboot and reinstall OTA, then if u wanna root use SuperSU v2.61, hope it helps.
Just flashed the CM12.1 through twrp ,problem is solved in a way.
anks095 said:
Just flashed the CM12.1 through twrp ,problem is solved in a way.
Click to expand...
Click to collapse
facing the same problem...... is flashing CM12.1 gonna solve it ?
praveen1618 said:
facing the same problem...... is flashing CM12.1 gonna solve it ?
Click to expand...
Click to collapse
It will but you should have unlocked bootloader.
praveen1618 said:
facing the same problem...... is flashing CM12.1 gonna solve it ?
Click to expand...
Click to collapse
unlock ur boot-loader first ,then flash cm through fastboot or if u have twrp then copy the cm zip in the sd card and then flash it through twrp.But remember to wipe the system,cache,dalvik cache and data.problem should be gone.
anks095 said:
unlock ur boot-loader first ,then flash cm through fastboot or if u have twrp then copy the cm zip in the sd card and then flash it through twrp.But remember to wipe the system,cache,dalvik cache and data.problem should be gone.
Click to expand...
Click to collapse
Sorry Noob question- when should I wipe the system,cache,dalvik cache and data ?? Before flashing cm 12.1??
And I am currently on mm rooted. And cm12.1 is based on lollypop, will there be any problem if I flash cm12.1?
bablu048 said:
Sorry Noob question- when should I wipe the system,cache,dalvik cache and data ?? Before flashing cm 12.1??
And I am currently on mm rooted. And cm12.1 is based on lollypop, will there be any problem if I flash cm12.1?
Click to expand...
Click to collapse
It will work fine.Backup your current system using twrp and then flash cm12.1.
bablu048 said:
Sorry Noob question- when should I wipe the system,cache,dalvik cache and data ?? Before flashing cm 12.1??
And I am currently on mm rooted. And cm12.1 is based on lollypop, will there be any problem if I flash cm12.1?
Click to expand...
Click to collapse
hope fully there would not be any problem....but in case of going wrong with something you should make a back up with twrp to go back to previous build,and yes ,before flashing any rom, you should wipe your cache ,dalvik cache and data......and system if u need...depends upon you
about moto x stucked while rooting
anks095 said:
Just flashed the CM12.1 through twrp ,problem is solved in a way.
Click to expand...
Click to collapse
i was trying to root moto x play i unlocked bootloader but when i tried to root my phone stuked in WARNING BOOTLOADER UNLOCKED.......... I TRIED WIPE ALL DATA FROM RECOVERY.... i tried some research someone said try to flash cm12.1 with twrp but i dont know hot to do this..... my mob is not connecting with pc plz help me guyz plz contect me at my gmail [email protected] its very urgent......plz tell me what to do step by step
sonubisht said:
i was trying to root moto x play i unlocked bootloader but when i tried to root my phone stuked in WARNING BOOTLOADER UNLOCKED.......... I TRIED WIPE ALL DATA FROM RECOVERY.... i tried some research someone said try to flash cm12.1 with twrp but i dont know hot to do this..... my mob is not connecting with pc plz help me guyz plz contect me at my gmail [email protected] its very urgent......plz tell me what to do step by step
Click to expand...
Click to collapse
first of all, which super su zip u r trying to flash ???? only this super su - "SuperSU-v2.62-3-20151211162651.zip" works on MXP...... after unlocking the boot loader u need to flash first twrp custom recovery...then entering into twrp interface,format the whole internal memory (I m sorry,u have to do that,no other way is possible)...... then put cm12 zip which u want to flash in sd card then flash the zip through twrp....... I guess this way your problem would be solved.....
If u flashed the correct mentioned supersu you should be fine.It happened 3 times also to me.I just press power continuously to power off and then it boots normally.
Please in case of SuperSU do not use 2.62-3 anymore, use 2.79SR3. Both are supposed to work, but 2.79SR3 is newer and has some bugfixes.
Note: The release 2.79 will not work, the detection fix to install systemless for all Moto devices is only integrated in 2.79SR3. 2.62-3 does no detection, it always installs systemless.
that was rom problm
mausv said:
Well the thing you could do is factory resetting via TWRP or you could download a new ROM like CM 12.1 that you can find in the original android developer section and flash it with TWRP, your phone would boot up now. Keep in mind that you will lose everything.
Click to expand...
Click to collapse
that was a rom problem
my phone is not turning on pls help after updating one ota of marshmallow security patch 1 jan
anks095 said:
Just flashed the CM12.1 through twrp ,problem is solved in a way.
Click to expand...
Click to collapse
Is cm12.1 support direct volte calling,.? Or any other custom rom which support volte calls???.

Can't get into recovery :( would appreciate some help

Hello everyone,
yes i tried the search, but i really could not find anything matching my problem
I want so gift my S4 to a friend for christmas and wanna do a full wipe + new custom rom (currently sitting on Ressurection Remix Remix 5.5.5)
When i try to enter TWRP i get stuck at the teamwin screen
I've tried the following:
- flash older TWRP again via Odin
- install newest TWRP again via TWRP Manager App
- flashing Stock Recovery (could not even get into anything, bootloop)
Any suggetions how to solve this problem?
Sorry for any grammar/vocabulary mistakes. English is not my first language
Try flashing stock rom. That also includes the stock recovery. Then reflash twrp.
GDReaper said:
Try flashing stock rom. That also includes the stock recovery. Then reflash twrp.
Click to expand...
Click to collapse
Thanks :3
do i need to root again now?
der Blonde said:
Thanks :3
do i need to root again now?
Click to expand...
Click to collapse
Unless you want to stay on the stock rom, or want to backup some apps, then no. Rooting will not be necessary if you plan on changing to a custom rom again.
rooted my s4 again,
twrp is finally working
but i cant flash the rom
Error executing updater binary in zip
anyone has an idea?
i allready downloaded the rom again but the zip is not broken
Are you using the latest version of twrp?
Yes 2.8.7.0
der Blonde said:
Yes 2.8.7.0
Click to expand...
Click to collapse
That error is caused because the recovery thinks the rom is not compatible with your phone.
Make sure your phone is compatible with the rom.
Or try these steps I found online:
1. Advance Wipe > Wipe cache, data, system, dalvik partitions.
2. Select ZIP file of your ROM and flash it.
3. You will get E:Error executing updater binary in zip (Don’t panic!)
4. Go to Reboot menu > Select Reboot to recovery.
5. After rebooting in recovery, flash the ZIP file of the ROM again WITHOUT WIPING.
Then it should work, according to the site I found it on.
The execution error indicates that the phone may not be supported by the ROM you're trying to flash..

Clean Restoration to Stock MIUI from Custom Marshmallow ROMS

Custom ROMs are awesome! But sometimes, you need to get back to stock MIUI. But you cannot directly flash the MIUI rom. Eventhough, if you have made a backup of stock miui, you ll face problems while restoring back from marshmallow based custom roms. You will get an error as " extractTarFork() process ended with ERROR 255 ".
Dirty Solution:
In TWRP, mount all partitions
Go to restore, and untick only "firmware"
Restore everything; and wipe cache, dalvik cache
Reboot system
Clean Solution:
Now from above solution eventhough you ll come back to miui, but while updating through updater app, you ll not be able to flash the OTA files. This happens only on some devices. If you are facing this, you need to follow all the above steps of dirty solution. Additionally, download fastboot rom, and flash using "Flash all", which will wipe your data and internal sd card data too.
Press Thanks if i helped you
Thank-you was searching for this..I'll try restoring now ..I'm on RR with cm13 radio flashed.and I never mind about ota but can I flash full recovery rom.zip from alka again ??
Pranbellam said:
Thank-you was searching for this..I'll try restoring now ..I'm on RR with cm13 radio flashed.and I never mind about ota but can I flash full recovery rom.zip from alka again ??
Click to expand...
Click to collapse
It will do.
Sent from my Redmi Note 3 using XDA Labs
MOVZX said:
It will do.
Sent from my Redmi Note 3 using XDA Labs
Click to expand...
Click to collapse
Bro ,can u plz tell me y is firmware failing to restore ..if u know..
This tutorial works 100%fine if any1 wants to go back to miui from cm13 based roms.but all u need to have is a twrp alka backup of miui ..
Yeah. Alka backup is required
How about we don't have miui backup to restore? Can I flash any miui fastboot ROM via miflash?
I have Unofficially unlocked boadloader with CM13 radio.
I have no problem with restore miui backup. But I am not able to flash ota updates. While flashing its opening twrp recovery and I have flashed it manually, but showing error.

need help

while installing lineage rom error occured
could not find META-INF\com\google\android\update-binary
please help me out :crying:
ravage lurker said:
while installing lineage rom error occured
could not find META-INF\com\google\android\update-binary
please help me out :crying:
Click to expand...
Click to collapse
Please give more info:
Rom version you tried to install?
TWRP version?
Rom zip downloaded again in case of file crc errors?
Flashed cm13 before your rom or zip?
Detailed steps of installation method you follow?
strongst said:
Please give more info:
Rom version you tried to install?
TWRP version?
Rom zip downloaded again in case of file crc errors?
Flashed cm13 before your rom or zip?
Detailed steps of installation method you follow?
Click to expand...
Click to collapse
i was trying to install lineage-14.1-20170530-nightly-ham-signed. evertime same error occurs and i am using twrp 3.1.1.0. no i didnt flash cm13 directly i flashed resurrection remix 7.1.2 official its working.
first i unlooked bootloader and then i tried to install lineage os but error occured so i installed resurrection remix rom and gapps
ravage lurker said:
i was trying to install lineage-14.1-20170530-nightly-ham-signed. evertime same error occurs and i am using twrp 3.1.1.0. no i didnt flash cm13 directly i flashed resurrection remix 7.1.2 official its working.
first i unlooked bootloader and then i tried to install lineage os but error occured so i installed resurrection remix rom and gapps
Click to expand...
Click to collapse
Try installing unofficial and then official LineageOS 14.1
strongst said:
Try installing unofficial and then official LineageOS 14.1
tried but still the same problem is occuring
Click to expand...
Click to collapse
ravage lurker said:
while installing lineage rom error occured
could not find META-INF\com\google\android\update-binary
please help me out :crying:
Click to expand...
Click to collapse
Hey I think you should factory reset and then try again to install lineage
Gyanesh23 said:
Hey I think you should factory reset and then try again to install lineage
Click to expand...
Click to collapse
Tried out problem is occurring in only official lineage os olny
Did you try wiping data system delvik cache and cache in twrp in advanced wipe.Maybe try that and again install lineage .
Gyanesh23 said:
Did you try wiping data system delvik cache and cache in twrp in advanced wipe.Maybe try that and again install lineage .
Click to expand...
Click to collapse
Tried every possible way
ravage lurker said:
while installing lineage rom error occured
could not find META-INF\com\google\android\update-binary
please help me out :crying:
Click to expand...
Click to collapse
Try installing other versions of it or fastboot cos and flash cm13 anf then lineage

Latest oreo roms and some problems...

When I install the latest oreo rom and recommended recovery, there are always problems
for example: error 7, Can't mount vendor, unable to mount storage...
When I install Pixel Experience and RR oreo rom, this error is happening and I can not install a different rom or another zips, using different recovery not the solution. I tried some suggestions here but the result has not changed
I installed a stock rom with QPST and problems improved
Exactly what we should do, Can you explain in detail
thanks to those who contributed :good:
Which recovery you using
poyraz4558 said:
When I install the latest oreo rom and recommended recovery, there are always problems
for example: error 7, Can't mount vendor, unable to mount storage...
When I install Pixel Experience and RR oreo rom, this error is happening and I can not install a different rom or another zips, using different recovery not the solution. I tried some suggestions here but the result has not changed
I installed a stock rom with QPST and problems improved
Exactly what we should do, Can you explain in detail
thanks to those who contributed :good:
Click to expand...
Click to collapse
Please provide specifics of ROM and TWRP Version. Did you load mods? Did you use custom kernel?
I installed this recovery for bootleggers 8.1 rom,
https://androidfilehost.com/?fid=673956719939820462 (twrp 3.2.1.0 It works well),
then I've installed Orangefox recovery for try and I used for long time without any problem,
later I flashed this recovery for Pixel Experience rom
https://androidfilehost.com/?fid=1322778262904027766 (twrp 3.2.3.0),
installed without a problem but a long time stuck in google logo, I rebooted three times a long press power button and the phone opened normally
No problem when using the phone but all times error on recovery.. such as 'vendor, invalid argument, mount error.
Always these errors during the rom installation and wiping..
Now is stock rom installed, I think there are some changes in the new rom because such problems did not happen before,
thank you for your answers and developers
poyraz4558 said:
I installed this recovery for bootleggers 8.1 rom,
https://androidfilehost.com/?fid=673956719939820462 (twrp 3.2.1.0 It works well),
then I've installed Orangefox recovery for try and I used for long time without any problem,
later I flashed this recovery for Pixel Experience rom
https://androidfilehost.com/?fid=1322778262904027766 (twrp 3.2.3.0),
installed without a problem but a long time stuck in google logo, I rebooted three times a long press power button and the phone opened normally
No problem when using the phone but all times error on recovery.. such as 'vendor, invalid argument, mount error.
Always these errors during the rom installation and wiping..
Now is stock rom installed, I think there are some changes in the new rom because such problems did not happen before,
thank you for your answers and developers
Click to expand...
Click to collapse
Okay... I'd recommend one thing.
Install the custom ROM. Then follow flashing procedure and do read the new FAQ posted by the devs. And after that... Try to reflash the recovery.img by pressing install image option. After this... If the problem persists, try to follow the procedure again and check if your recovery image isn't corrupt. Plus don't use the recovery from TWRP.ME
I have a recovery that can solve this problem but you can't restore ROMs you backed up
Phantom Slayer04 said:
Okay... I'd recommend one thing.
Install the custom ROM. Then follow flashing procedure and do read the new FAQ posted by the devs. And after that... Try to reflash the recovery.img by pressing install image option. After this... If the problem persists, try to follow the procedure again and check if your recovery image isn't corrupt. Plus don't use the recovery from TWRP.ME
Click to expand...
Click to collapse
thanks, I understand
I did actually try a second time, just flashed pixel experience rom and twrp 3.2.3.0 recovery on the stock rom - recovery.. same errors are happening and this problems improve only when I install stock rom with QPTS.. I will do clean installation in a short time again, just wonder why there is so much vendor error on recovery...
poyraz4558 said:
thanks, I understand
I did actually try a second time, just flashed pixel experience rom and twrp 3.2.3.0 recovery on the stock rom - recovery.. same errors are happening and this problems improve only when I install stock rom with QPTS.. I will do clean installation in a short time again, just wonder why there is so much vendor error on recovery...
Click to expand...
Click to collapse
Did you wipe the partitions? Did you format data partition?
Phantom Slayer04 said:
Did you wipe the partitions? Did you format data partition?
Click to expand...
Click to collapse
yes I did, including vendor..Today I searched the topics in the forum; return to old rom is not recommended after installing the new rom, I see similar troubles in rom forums..
poyraz4558 said:
yes I did, including vendor..Today I searched the topics in the forum; return to old rom is not recommended after installing the new rom, I see similar troubles in rom forums..
Click to expand...
Click to collapse
If you want to install latest update roms then read this FAQ:https://forum.xda-developers.com/showpost.php?p=77872447&postcount=2325:confused:
if you want to revert to old roms then you have to flash stock nougat rom using qfil and install twrp 3.2.1.0 and install old roms
don't do it wrongly otherwise you will get updater error 7 or can't mount vendor, etc,
Sudhar123 said:
If you want to install latest update roms then read this FAQ:https://forum.xda-developers.com/showpost.php?p=77872447&postcount=2325:confused:
if you want to revert to old roms then you have to flash stock nougat rom using qfil and install twrp 3.2.1.0 and install old roms
don't do it wrongly otherwise you will get updater error 7 or can't mount vendor, etc,
Click to expand...
Click to collapse
Thank you, I learned later that.. That's why i'm using an old rom because sometimes I can't any process on recovery, There are too many errors..
poyraz4558 said:
When I install the latest oreo rom and recommended recovery, there are always problems
for example: error 7, Can't mount vendor, unable to mount storage...
When I install Pixel Experience and RR oreo rom, this error is happening and I can not install a different rom or another zips, using different recovery not the solution. I tried some suggestions here but the result has not changed
I installed a stock rom with QPST and problems improved
Exactly what we should do, Can you explain in detail
thanks to those who contributed :good:
Click to expand...
Click to collapse
You should be on latest nougat that is with november security patch. All rom after 14/10/2018 should flash with latest twrp that is 3.2.3.0. all roms before that should be flashed with twrp 3.2.1.0.
sk.vyshak said:
You should be on latest nougat that is with november security patch. All rom after 14/10/2018 should flash with latest twrp that is 3.2.3.0. all roms before that should be flashed with twrp 3.2.1.0.
Click to expand...
Click to collapse
Ok..Which sections will be deleted on twrp 3.2.3.0 during wipe, is vendor partition included ?
poyraz4558 said:
Ok..Which sections will be deleted on twrp 3.2.0.3 during wipe, is vendor partition included ?
Click to expand...
Click to collapse
The thing is with new twrp there is decryption support which was lacked in old. Vendor partition is present in both i think. All the new roms are encrypted by default

Categories

Resources