Related
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???.
Hello,
I flashed CM 13 NIGHTLY from 15.07.2016 and wanted to flash capps for CM13. I always seem to get an error in TWRP saying:
Updater process ended with ERROR=7
Error flashing zip '/sdcard/capps-13.0-20160707-signed.zip'
I tried flashing other TWRP versions but it didn't help.
Can anyone help me, please?
The TWRP log is here: http://pastebin.com/LDacBqkb
Thank you.
EDIT: Just for your information, I even tried full wipe and everything... still not working at all... Please help me.
Try mounting /system as read-write in twrp before flashing capps.
svantes said:
Try mounting /system as read-write in twrp before flashing capps.
Click to expand...
Click to collapse
First shot!
Thank you, it works now!
Marked as solved.
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
A GUIDE TO FLASH LATEST TREBLE ROMS, OLDER TREBLE ROMS OR NON-TREBLE ROMS ROMS
UPDATE: A guide to rename our /factory partition as /vendor so that you can flash OLDER Android Oreo treble builds! We do not need this guide on Android Pie custom ROMs or for Stock ZUI WE ONLY NEED THIS FOR ANDROID OREO TREBLE BUILDS REQUIRING /factory renamed as /vendor
for Lenovo Zuk Z2 PRO
Latest Treble : /factory renamed i.e switched to /vendor
Older Treble:/factory mounted as /vendor
Non-Treble: Nothing to do with Vendor, Factory stuff lol
INTRO
As you all know that we now have TREBLE, and Zuk-devs are working hard to improve it further so that when the time comes we can move to GSI builds of future Android versions.
Recently, Zuk-devs have renamed the /factory partition into /vendor partition previously we were mounting /factory as /vendor but now it has been converted(renamed) to /vendor partition with this you'll be able to use a Proper Magisk zip, and you don't need a modded/edited Magisk, etc and lotta other kinds of stuff that we will discuss and come to know in the future.
rootdir: fstab: Use the right label for our vendor partition.
TUTORIAL:
What you want to do:
** Flash OLD TREBLE ROMS /factory is renamed to /vendor - NOTE NOT NEEDED FOR NEWER ROMS! **
Instructions:
* Flash "Factory2Vendor_plus.zip",
*Flash belowTWRP,
*Reboot To TWRP,
*Flash ROM,
+ GApps / + Magisk etc
* Reboot.
*Enjoy :fingers-crossed:
Downloads:
Factory2Vendor_pro: https://androidfilehost.com/?fid=746010030569969371
TWRP for /factory renamed as /vendor roms https://github.com/cosmedd/android_...eases/download/20180413/20180413_recovery.img
** REVERTING BACK to NORMAL aka renaming /vendor back to/factory **
Instructions:
*Flash "Vendor 2Factory_plus.zip",
*Flash OFFICIALTWRP,
*Reboot TWRP,
*Flash ROM,
+ GApps / + Magisk etc
*Reboot.
*Enjoy :fingers-crossed:
Downloads:
Vendor2Factory_pro: https://androidfilehost.com/?fid=673956719939835215
https://twrp.me/zuk/zukz2row.html
** REVERTING BACK to NORMAL aka renaming /vendor back to/factory **
Instructions:
*Flash ROM,
+ GApps / + Magisk etc
*Reboot.
*Enjoy :fingers-crossed:
Notes:
This 'New TWRP' will work for both Latest Treble and Non-Treble RoMs
For ZUI also no need to flash any patch, New TWRP shall work (Needs to be tested)
You can flash Non Treble RoMs and Nougat Builds or other builds with the new TWRP and no patches need to be flashed
Once you flash "factory2vendor" or "vendor2factory" you do not need to flash again unless mentioned in the build
or if you want to revert back to Old Treble RoMs where /factory was mounted as /vendor
CREDITS
Zuk-devs - Davidevinavil, DD3Boh and Cosmedd (https://github.com/zuk-devs)
@Fedor917 for giving the idea
And all others who have contributed in any manner! :highfive:
Reserved
You'll be able to use above method for Latest AEX coming soon by Davidevinavil and all the ROMs compiled using the latest sources as per by Zuk-devs
Links added, enjoy
thx
Can we make this procedure opposite? i.e. flash first twrp and than that zip? I normally flash twrp with official twrp app
1 or 2 should I do if I want to flash from the latest zui to AEX5.4 ,thx
thanks
Thanks zuk developer
I just tryed to flash Vendor 2Factory_pro..zip but I get following error "failed to mount '/vendor' (invalid argument)". I was in previous version 5.4 (1104). After restart, it does not load the rom but the bootloader. problem is the devices is not recognized under "adb devices" when in bootloader. Any ideas will be very welcome
darquesp said:
I just tryed to flash Vendor 2Factory_pro..zip but I get following error "failed to mount '/vendor' (invalid argument)". I was in previous version 5.4 (1104). After restart, it does not load the rom but the bootloader. problem is the devices is not recognized under "adb devices" when in bootloader. Any ideas will be very welcome
Click to expand...
Click to collapse
In bootloader (fastboot) you must use
fastboot -i 0x2b4c
ADB works in twrp or with system . Just follow this guide .
mar.ur said:
In bootloader (fastboot) you must use
fastboot -i 0x2b4c
ADB works in twrp or with system . Just follow this guide .
Click to expand...
Click to collapse
I installed the vendor, but the twrp is only black.
Any solution?
JustBr said:
I installed the vendor, but the twrp is only black.
Any solution?
Click to expand...
Click to collapse
Did you install latest twrp after flashing f2v
mar.ur said:
In bootloader (fastboot) you must use
fastboot -i 0x2b4c
ADB works in twrp or with system . Just follow this guide .
Click to expand...
Click to collapse
Thanks. I flashed last rom and after that updated twrp with twrp app and now I get no error about partitions.
I thought that to flash a twrp image with adb, I should do into fastboot mode. Can I also do it into recovery or system just with command : fastboot -i 0x2b4c flash recovery twrp.img?
Which guide do you mean? I checked on this thread and could not find a guide about adb.
Many thanks!
You can install twrp.img in any twrp .Just go to install/ install image and choose new twrp.img , then mark recovery and flash it .
mar.ur said:
Did you install latest twrp after flashing f2v
Click to expand...
Click to collapse
my twrp and 3.1, downloaded a recovered image(new twrp ), select image, recover and flash .. and the screen continues black, do not start twrp ... !!!!
JustBr said:
my twrp and 3.1, downloaded a recovered image(new twrp ), select image, recover and flash .. and the screen continues black, do not start twrp ... !!!!
Click to expand...
Click to collapse
I test a lot of systems . Last I was on mokee 7.1.2 with redwolf twrp with vendor partition ( not the latest ) . I install f2v.zip then twrp https://github.com/cosmedd/android_...eases/download/20180413/20180413_recovery.img . After that restart to recovery . Finally install to the latest Aex . No problems at all . First of all start with 2018.03.11 twrp , then install f2v.zip , 2018.04.13 twrp , restart to recovery and install aex or rr . That's all
Hy bro,
Can you send me the twrp version 2018.03.11 link?
failed to mount 'vendor'
After following the previous steps. TRWP start to show "failed to mount 'vendor' (invalid argument)'" message. I'm able to install the AEX 5.4, but the google apps do not crashes.
Any help?
Solved: wrong TWRP.
Nice boot animation
JustBr said:
Hy bro,
Can you send me the twrp version 2018.03.11 link?
Click to expand...
Click to collapse
https://github.com/cosmedd/android_...eases/download/20180311/20180311_recovery.img
mar.ur said:
https://github.com/cosmedd/android_...eases/download/20180311/20180311_recovery.img
Click to expand...
Click to collapse
Last help, I do everything by the pc, in fasboot mode ? or last twrp by his flash (twrp).
I had rooted my yu yureka and flashed twrp . I had installed lineage os 14 and had it working very smoothly. A few days back I updated lineage os on it and also flashed it's volte modem files after updating twrp . Now it worked fine for some days and then one day it starts rebooting every now and then . And yesterday it developed something new.
It starts with yu logo and then goes dark for a second and then again displays yu logo and then again dark and ....... Loop goes on. But if you start charging it , it stays stuck on the yu logo . Also when I try to flash some other version of lineage os , it exits installation with error code 7
Is it hard bricked ?
Please give some solution for this asap
v1nashak said:
I had rooted my yu yureka and flashed twrp . I had installed lineage os 14 and had it working very smoothly. A few days back I updated lineage os on it and also flashed it's volte modem files after updating twrp . Now it worked fine for some days and then one day it starts rebooting every now and then . And yesterday it developed something new.
It starts with yu logo and then goes dark for a second and then again displays yu logo and then again dark and ....... Loop goes on. But if you start charging it , it stays stuck on the yu logo . Also when I try to flash some other version of lineage os , it exits installation with error code 7
Is it hard bricked ?
Please give some solution for this asap
Click to expand...
Click to collapse
Flash twrp 3.2.3
Flash du Oreo
https://androidfilehost.com/?fid=11410963190603842520
Rajendran Rasa said:
Flash twrp 3.2.3
Flash du Oreo
Click to expand...
Click to collapse
Did as you said and got .....
Updater process ended with signal :7
Error installing zip file '/external_sd/du_tomato....'
Updating partition details
Failed to mount '/system' (Invalid Argument)
v1nashak said:
Did as you said and got .....
Updater process ended with signal :7
Error installing zip file '/external_sd/du_tomato....'
Updating partition details
Failed to mount '/system' (Invalid Argument)
Click to expand...
Click to collapse
Wipe system, data, cache,
Then flash ROM
Rajendran Rasa said:
Wipe system, data, cache,
Then flash ROM
Click to expand...
Click to collapse
Did that too
Got same result
"
E1001 : Failed to update system image
Updater process ended with error : 7
Error installing zip file '.....'
Failed to mount '/system' (invalid argument)
"
Edit : Also if that's of any help , I am unable to use features of the twrp like installing zips and wiping without plugging in my phone because it shuts down while the process is going on
Somebody please help !
Dude the problem is of battery inserted. Change it and it would help .
A few days back I also had this problem. After changing the battery problem was solved.
To flash a clean room first wipe all partitions and then flash the image.
Updater process ended with signal :7
Error installing zip file '/external_sd/du_tomato....'
Updating partition details
Failed to mount '/system' (Invalid Argument)
This means your partition size is 1.4 gb only soc change it to 2.5 gb and then flash the image
saalimsam said:
Dude the problem is of battery inserted. Change it and it would help .
A few days back I also had this problem. After changing the battery problem was solved.
To flash a clean room first wipe all partitions and then flash the image.
Updater process ended with signal :7
Error installing zip file '/external_sd/du_tomato....'
Updating partition details
Failed to mount '/system' (Invalid Argument)
This means your partition size is 1.4 gb only soc change it to 2.5 gb and then flash the image
Click to expand...
Click to collapse
Battery problem solved !
Now could you please give me a step by step guide of next task
v1nashak said:
Battery problem solved !
Now could you please give me a step by step guide of next task
Click to expand...
Click to collapse
Flash stock ROM in fastboot
Rajendran Rasa said:
Flash stock ROM in fastboot
Click to expand...
Click to collapse
Please provide link for the stock ROM