Database Users

problem with CM13, please help

So I flashed CM13 and GApps through TWRP, but I get asked the famous "password".. how can I solve this?

SALVO9 said:
So I flashed CM13 and GApps through TWRP, but I get asked the famous "password".. how can I solve this?
Click to expand...
Click to collapse
Format data in twrp.

try default_password

TWRP recovery error 7

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

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

Gapps installed and phone boots into recovery

Hello, since Lineage OS came officially to Redmi Note 7 a couple of days ago, I've decided to install it. I was previously on Pixel Experience so this was the first time I was installing the gapps as well.
The installation of Lineage OS went fine but everytime I try reboot into the system after the installation of gapps, the phone is always booting again into recovery.
How can I solve this?
Thanks for the attention ?
Edit: everytime I try to setup my account the ui/ android configuration crashes and I can´t setup my account. I am currently using the arm64 stock version for android 10 and Lineage OS 17.1

Which gapps? U mount system, vendor and data before? Or better mount all before. Flash your rom, boot the system, boot in the recovery and flash the gapps package.

joke19 said:
Which gapps? U mount system, vendor and data before? Or better mount all before. Flash your rom, boot the system, boot in the recovery and flash the gapps package.
Click to expand...
Click to collapse
It worked thanks! I was flashing the rom, flashing the stock gapps and then boot into the system.

joke19 said:
Which gapps? U mount system, vendor and data before? Or better mount all before. Flash your rom, boot the system, boot in the recovery and flash the gapps package.
Click to expand...
Click to collapse
Now I can boot up the system but when I try to steup my google account the whole thing crashes. It says "Setup Wizard has stopped working" . I am trying to install the arm64 stock version for android 10 and Lineage OS 17.1. Do you know what can I do to solve this problem?

nokuteshimo said:
Now I can boot up the system but when I try to steup my google account the whole thing crashes. It says "Setup Wizard has stopped working" . I am trying to install the arm64 stock version for android 10 and Lineage OS 17.1. Do you know what can I do to solve this problem?
Click to expand...
Click to collapse
Opengapps stock? Test another gapps builder like bitgapps or nikgapps.

joke19 said:
Opengapps stock? Test another gapps builder like bitgapps or nikgapps.
Click to expand...
Click to collapse
It worked with bitgapps. Thank you for the help!

Booting only into recovery

Hey hello community,
Actually i have been installing a custom rom in my redmi note 7s (code named as: lavender). First i have tried Corvus OS v15.0 based on Android 11. Then I want to try Evolution X Rom just because some says it was better. But i have faced some lag problems in Evolution X so I want to switch back to Corvus.
The problem comes when after flashing the same Rom (what i have previously flashed) through TWRP it is not booting up but instead goes to Recovery again. The Evolution X is working fine when flashing again but not Corvus. I have re-downloaded the zip file for Corvus but the same problem is occurring. I have TWRP version 3.4.0 but i have trued newer verson but the same problem is there. I have also tried flashing older versions of corvus but its giving me Error-1 during flashing process.
I can't figure out the solution by my own so I want help from you guys. Ask me about any other thing you want to know about this situation.
Thank you in advance for helping me.

One possible solution is to clean wipe and then format data before flashing the Corvus ROM within recovery mode.

deolux2 said:
One possible solution is to clean wipe and then format data before flashing the Corvus ROM within recovery mode.
Click to expand...
Click to collapse
Thanks for your reply but i have tried clean wipe format multiple times before flashing including internal storage

chirag_pandit said:
Thanks for your reply but i have tried clean wipe format multiple times before flashing including internal storage
Click to expand...
Click to collapse
Please try the latest stable version of OrangeFox Recovery instead of the official TWRP.
Kind regards.

deolux2 said:
Please try the latest stable version of OrangeFox Recovery instead of the official TWRP.
Kind regards.
Click to expand...
Click to collapse
Ok let me try thanks

I have tried with orange for but still the same problem.

Is the Corvus OS file corrupted?
If the file is okay, please ask for help in the following Telegram group:
Redmi Note 7/7S | OFFICIAL
Channel: @RedmiNote7Updates Off-Topic: @RedmiNote7OT Photograpy: @RedmiNote7Photography Customization: @XiaomemeCustomization Combot: https://combot.org/c/-1001290323095 Abide by all the rules, type /rules to check all rules.
t.me
Kind regards

Check this out this is what's happening.
Please help me out in this situation.