problem with CM13, please help - Huawei P9 Lite Questions & Answers

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

Related

[Q][KERNEL]CyanogenMod 12.1 Overclock 1.593.600hz - KCAL - Advanced color control

i downloaded the kernel on my s3 neo (gt i9300i) running cm12.1 and i got a bootloop after i restarted in my recovery (cwm) after i flashed it. can anyone help me? D:
if you want to get from a bootloop, then REFLASH your CM12.1. just boot into your recovery.
wipe system, data, cache, dalvik. THEN REFLASH your ROM CM12.1 and GAPPS (optional)
if you want to install kernel successfully, i recommended to switch from TWRP recovery.
most kernel of cm12.1 based rom suggested that you use TWRP.
I'm using TWRP and flash kernel and didnt get any bootloop...
DerPuGNa said:
...
Click to expand...
Click to collapse
thanks bro im going to try and flash twrp now and see if it does the trick. thanks
DerPuGNa said:
...
Click to expand...
Click to collapse
I changed my recovery into twrp and tried to flash the kernel on my cm12.1 but still no luck. im stuck in the boot screen :crying:
Vanwald said:
I changed my recovery into twrp and tried to flash the kernel on my cm12.1 but still no luck. im stuck in the boot screen :crying:
Click to expand...
Click to collapse
what kernel u flashing?
DerPuGNa said:
what kernel u flashing?
Click to expand...
Click to collapse
nvm hahaha. i downloaded the latest cm12.1 for my phone, flashed gapps then i flashed the kernel using twrp and i got it to work. thanks m8

[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???.

Flashed CM13, Cannot find Gapps package that works, help?

Hey everyone, I rooted my phone, unlocked the bootloader, flashed TWRP, and then flashed CyanogenMod 13 (Marshmallow). Everything worked perfectly, so I went back into my recovery to flash Gapps. I've tried Open Gapps and Slim Gapps, but both repeatedly crash setup wizard and clock among other things.
If anyone could help, I'd really appreciate it.
trent4071 said:
Hey everyone, I rooted my phone, unlocked the bootloader, flashed TWRP, and then flashed CyanogenMod 13 (Marshmallow). Everything worked perfectly, so I went back into my recovery to flash Gapps. I've tried Open Gapps and Slim Gapps, but both repeatedly crash setup wizard and clock among other things.
If anyone could help, I'd really appreciate it.
Click to expand...
Click to collapse
Same here I tried it, and it did the same for me also...
Sent from my SM-N920F using Tapatalk
These are the Gapps that worked for me
http://forum.xda-developers.com/slimroms/general/gapps-official-slim-gapps-trds-slimkat-t2792842
Thank you for the help wikked26, but it didn't work. Those Gapps still crash for me. I think it's something incorrect in the way my phone is configured, not a case of downloading the wrong Gapps.
If anyone has any other ideas, please share them! I haven't cracked the case just yet
I know I was having issues with the Slimroms version where I booted into CM and set it up before installing Gapps. Fixed it by reinstalling/wiping the cache and installing Gapps before booting anything. Don't know if that helps, but I'm running fine now.
I'm hoping this is similar to the issue I'm having. Do you get it where you can factory reset in TWRP, then flash CM13, but when you go to flash Slim Gapps? Because I figured out that after factory resetting TWRP will only successfully flash 1 zip file. I also tried to wipe the cacher, dalvik, data, and system, then flash cm13 but Gapps still wouldn't flash. Maybe its a bug with TWRP 3.0.2? I'm going to try to use a different version of TWRP and I'll update with my results
EDIT: TWRP 2.8.5 did not do anything different
Wow, thanks for all the great responses. I made sure to try and install CM13 and Gapps at the same time, before boot, after wiping everything one last time. It worked flawlessly, and I can now use Google Play Services.
I hope this thread helps anyone else who is also a little stuck. I also found that TWRP didn't have any issues flashing multiple zips at the same time, not sure whats going on with you, Orange Officer. Perhaps try removing your battery after CM13 flashes, and then boot into TWRP again and flash Gapps without booting up CM13 at all?

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

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

Categories

Resources