Database Users

Zenfone 5 internal storage corrupted

I flashed my Zenfone 5 to CM 13.1. For the first few week of usage it was perfectly fine and had no issue after after a while the phone was acting weird so I rebooted it, while it was booting up it was stuck in the Cynogenmod logo and I figured out it was a bootloop. I tried many method to bring it back to stock but failed, i even tried the methods which i used when i was suing CM 12.1.
Issues I found:
I could flash from a tool called "Zenfone Assist" and could flash from adb but when I tried to wipe from TWRP it said failed to mount /cache /system etc and many other partitions.
I tried to lock the boot loader and change the recovery back to stock, it did say "okay" in the flashboot but nothing chnaged in the phone. The bootloader was not locked and the recovery was still TWRP. I tried many methods but it stays the same. The only thing that i could wipe was the /system.
I tried to restore using the jelly bean .raw file and still no luck, it showed 2 partitions failed ( one being OEM the other I'm not sure) and its still the same, the same unlocked bootlaoder and TWRP recover.
One member here suggested that my internal storage might be corrupted.
If it is , is there any alternative way out of it and is there any other methods I could use that might work.
Much thanks for responses.

Boot to TWRP > "Wipe" > "Advanced Wipe" > Mark "Data" > "Repair or change file system" > "Repair" > "Swipe to repair"
See if it works

leonardohenrique10 said:
Boot to TWRP > "Wipe" > "Advanced Wipe" > Mark "Data" > "Repair or change file system" > "Repair" > "Swipe to repair"
See if it works
Click to expand...
Click to collapse
didnt work, it said unable to repair /data and error repairing file system.

zaris47 said:
didnt work, it said unable to repair /data and error repairing file system.
Click to expand...
Click to collapse
Try change to other file system, and if it works, change back to ext4
Also, "Format Data" option doesn't work?

leonardohenrique10 said:
Try change to other file system, and if it works, change back to ext4
Also, "Format Data" option doesn't work?
Click to expand...
Click to collapse
Format data says unable to mount '/cache' '/system' '/data'
Changing file system is still the same, the same message and error. Although now /datd is to ext3 and now i cant change from that :3
I could also change to ext2 but now can;t revert back to ext4

zaris47 said:
Format data says unable to mount '/cache' '/system' '/data'
Changing file system is still the same, the same message and error. Although now /datd is to ext3 and now i cant change from that :3
I could also change to ext2 but now can;t revert back to ext4
Click to expand...
Click to collapse
Well, try this: http://forum.xda-developers.com/zenfone-5/help/debrick-asus-zenfoen-5-fastboot-t3377455

leonardohenrique10 said:
Well, try this: http://forum.xda-developers.com/zenfone-5/help/debrick-asus-zenfoen-5-fastboot-t3377455
Click to expand...
Click to collapse
Gave it a try and failed. Now the bootloader is still unlocked (which it shouldn't be since the guide repartitioned it) and when I go to recovery it shows a usb sing.

zaris47 said:
Gave it a try and failed. Now the bootloader is still unlocked (which it shouldn't be since the guide repartitioned it) and when I go to recovery it shows a usb sing.
Click to expand...
Click to collapse
Well, your phone is really f*cked up
You already tried xfstk method?

leonardohenrique10 said:
Well, your phone is really f*cked up
You already tried xfstk method?
Click to expand...
Click to collapse
No not that. I never heard of that. Can you tell me or give me a link to a guide of its?

zaris47 said:
No not that. I never heard of that. Can you tell me or give me a link to a guide of its?
Click to expand...
Click to collapse
Here: http://forum.xda-developers.com/android/development/hard-bricked-zenfone-unbrick-method-to-t3131911

leonardohenrique10 said:
Here: http://forum.xda-developers.com/android/development/hard-bricked-zenfone-unbrick-method-to-t3131911
Click to expand...
Click to collapse
I will try that as a last resort. What I would like to know is whenever I try to re-partition with .raw file or adb there are 2 errors always showing,
one Failed cause cant partition oem and the other, Failed cause cant format spare
Another problem is the bootloader isn't locking, any clue on why any of these 3 problems occur?

zaris47 said:
I will try that as a last resort. What I would like to know is whenever I try to re-partition with .raw file or adb there are 2 errors always showing,
one Failed cause cant partition oem and the other, Failed cause cant format spare
Another problem is the bootloader isn't locking, any clue on why any of these 3 problems occur?
Click to expand...
Click to collapse
I got this error in spare partition when I tried to flash raw firmware. This partition doesn't exist in my device, so, I changed the extension of the firmware from .raw to .zip, opened "sec_update_image.bat" with Notepad++ and deleted all lines about spare partition. After edit, I replaced this file into zip and changed extension back to raw, and it flash sucessfull. I think you can do the same for oem partition.
About bootloader, try to extract "dnx_fwr_ctp_a500cg.bin" and "ifwi_ctp_a500cg.bin" from any firmware (I recommend from Lollipop .87, I always relock with these files) and flash it manually (fastboot flash dnx dnx_fwr_ctp_a500cg.bin; fastboot flash ifwi ifwi_ctp_a500cg.bin)

leonardohenrique10 said:
I got this error in spare partition when I tried to flash raw firmware. This partition doesn't exist in my device, so, I changed the extension of the firmware from .raw to .zip, opened "sec_update_image.bat" with Notepad++ and deleted all lines about spare partition. After edit, I replaced this file into zip and changed extension back to raw, and it flash sucessfull. I think you can do the same for oem partition.
About bootloader, try to extract "dnx_fwr_ctp_a500cg.bin" and "ifwi_ctp_a500cg.bin" from any firmware (I recommend from Lollipop .87, I always relock with these files) and flash it manually (fastboot flash dnx dnx_fwr_ctp_a500cg.bin; fastboot flash ifwi ifwi_ctp_a500cg.bin)
Click to expand...
Click to collapse
:\ didnt work. As for the raw one I cant seem to do anything and I use Zenfone assist, do you know any other tool or method to flash faw file (i tried zenfone flashtool but didnt work for some reason, think its because I dont have the asus drivers for the phone , mine is windows 10 it doesnt have any drivers for that)
flashboot relocking failed, i mean it did show "Okay" but still nothing happened

zaris47 said:
:\ didnt work. As for the raw one I cant seem to do anything and I use Zenfone assist, do you know any other tool or method to flash faw file (i tried zenfone flashtool but didnt work for some reason, think its because I dont have the asus drivers for the phone , mine is windows 10 it doesnt have any drivers for that)
flashboot relocking failed, i mean it did show "Okay" but still nothing happened
Click to expand...
Click to collapse
I flashed the RAW with ASUS Flash Tool, with my phone in Fastboot (Droidboot) mode. Everything worked fine.
Sorry, but I don't know how I can help you now
Good luck with your Zenfone

leonardohenrique10 said:
I flashed the RAW with ASUS Flash Tool, with my phone in Fastboot (Droidboot) mode. Everything worked fine.
Sorry, but I don't know how I can help you now
Good luck with your Zenfone
Click to expand...
Click to collapse
May I know which os did you use? Since I dont know why but the driver for zenfone is not supported for win 10 (the one im using) so does that make a difference?

zaris47 said:
May I know which os did you use? Since I dont know why but the driver for zenfone is not supported for win 10 (the one im using) so does that make a difference?
Click to expand...
Click to collapse
I'm using Windows 10, all drivers works fine.
Download "adb and fastboot drivers", and install on Windows 10. It should work.

leonardohenrique10 said:
I'm using Windows 10, all drivers works fine.
Download "adb and fastboot drivers", and install on Windows 10. It should work.
Click to expand...
Click to collapse
I had errors with that 15 sec adb install drivers but the ones I've downloaded worked too I guess, I sued that to flash to CM13.1 in the first place

@leonardohenrique10
even the xfstk method didnt work. It keep on showing error. It has got to be a problem with the drivers or my os. Since evey time there problems occur as errors some problem occur during the flashing.

zaris47 said:
@leonardohenrique10
even the xfstk method didnt work. It keep on showing error. It has got to be a problem with the drivers or my os. Since evey time there problems occur as errors some problem occur during the flashing.
Click to expand...
Click to collapse
Try from another computer, preferably using Windows 7.

leonardohenrique10 said:
Try from another computer, preferably using Windows 7.
Click to expand...
Click to collapse
tried and it showed the same error, although this time i noticed that the two drivers with the asus device in device manager, one of them has a problem, the adb one it said (altho adb worked fine)

Zenfone 3 doesn't boot to Android

Hi guys,
I try to restore my Zenfone 3 with his original firmware downloaded from Asus website. [Version WW_V13.20.10.79]
When i restart my phone, i got the first warning to let us know the bootloader is unlocked but after i got this error.
Code:
The dm-verity is not started in enforcing mode and may not work properly
To learn more, visit: g.co/placeholder
If i try to flash with TWRP with Install Zip, i got this error:
Code:
...
This package is for "WW_Phone" devices; this is a "omni_ze552kl".
Updater process ended with Error: 7
Error installing zip file '/sdcard/Download/<nameOfTheZipFile>.zip'
Updating partition details...
...done
(sorry i can't post image)
when i try fastboot recovery, it stuck to <waiting for device>.
This is my first time with Android, and rooting and all this sh*t. I'm coming from iOS jailbreak side but iTunes couldn't help me.
If you need to know anything, let me know.
I would greatly appreciate if anyone could help me.
Thanks!
SuperDizor
*English is not my first language, sorry about that*

SuperDizor said:
Hi guys,
I try to restore my Zenfone 3 with his original firmware downloaded from Asus website. [Version WW_V13.20.10.79]
When i restart my phone, i got the first warning to let us know the bootloader is unlocked but after i got this error.
Code:
The dm-verity is not started in enforcing mode and may not work properly
To learn more, visit: g.co/placeholder
If i try to flash with TWRP with Install Zip, i got this error:
Code:
...
This package is for "WW_Phone" devices; this is a "omni_ze552kl".
Updater process ended with Error: 7
Error installing zip file '/sdcard/Download/<nameOfTheZipFile>.zip'
Updating partition details...
...done
(sorry i can't post image)
when i try fastboot recovery, it stuck to <waiting for device>.
This is my first time with Android, and rooting and all this sh*t. I'm coming from iOS jailbreak side but iTunes couldn't help me.
If you need to know anything, let me know.
I would greatly appreciate if anyone could help me.
Thanks!
SuperDizor
*English is not my first language, sorry about that*
Click to expand...
Click to collapse
I used to be difficult to use TWRP menu, then the menu advanced Wipe Wipe then select all topics except the MicroSD and then manage Otg Wipe it !! Flash Stock Recovery to be done to make Flash official rom first official rom files onto the MicroSD example, I was. UL-ASUS_Z012D-WW-13.20.10.79-user. To change its name Then insert the MicroSD MOFD_SDUPDATE Recovry Mode, then select update to zip and then choose File. "MOFD_SDUPDATE.zip" I will wait a little longer for the update firmware and set up virtually everything is not lost through the OTA.
ผมเคยเป็นแก้ไม่ยากใช้ TWRP แล้วเข้าเมนู Wipe แล้วเข้าเมนู advanced Wipe ทำการเลือกทุกหัวข้อ ยกเว้น MicroSD และ Otg แล้วจัดการ Wipe ครับ!! เสร็จแล้วให้ทำการ Flash Stock Recovery เพื่อที่จะใช้ Flash official rom ก่อนอื่นทำไฟล์ official rom ลงไปยัง MicroSD ผมยกตัวอย่างเป็น UL-ASUS_Z012D-WW-13.20.10.79-user ให้เปลี่ยนชื่อเป็น MOFD_SDUPDATE แล้วนำใส่ MicroSD แล้วเข้า Recovry Mode แล้วเลือก update to zip แล้วทำการเลือกไฟล์ "MOFD_SDUPDATE.zip" แล้วรอสักพักอาจจะนานหน่อยเพราะเป็นการ update firmware ข้อมูลและการตั้งค่าทุกอย่างจะไม่หายเสมือนอัพผ ่าน OTA

I was able to fix my phone with flashing both boot.img and recovery.img with stock image and i used WW-13.16.5.36 firmware to flash and it's worked.
Thanks for the help JadeKubPom

SuperDizor said:
I was able to fix my phone with flashing both boot.img and recovery.img with stock image and i used WW-13.16.5.36 firmware to flash and it's worked.
Thanks for the help JadeKubPom
Click to expand...
Click to collapse
I got the same issue, where did you get these files?

roosevelt84 said:
I got the same issue, where did you get these files?
Click to expand...
Click to collapse
I have the exact same error. Same here. Please someone can post download link.

SuperDizor said:
Hi guys,
I try to restore my Zenfone 3 with his original firmware downloaded from Asus website. [Version WW_V13.20.10.79]
When i restart my phone, i got the first warning to let us know the bootloader is unlocked but after i got this error.
Code:
The dm-verity is not started in enforcing mode and may not work properly
To learn more, visit: g.co/placeholder
If i try to flash with TWRP with Install Zip, i got this error:
Code:
...
This package is for "WW_Phone" devices; this is a "omni_ze552kl".
Updater process ended with Error: 7
Error installing zip file '/sdcard/Download/<nameOfTheZipFile>.zip'
Updating partition details...
...done
(sorry i can't post image)
when i try fastboot recovery, it stuck to <waiting for device>.
This is my first time with Android, and rooting and all this sh*t. I'm coming from iOS jailbreak side but iTunes couldn't help me.
If you need to know anything, let me know.
I would greatly appreciate if anyone could help me.
Thanks!
SuperDizor
*English is not my first language, sorry about that*
Click to expand...
Click to collapse
I found a solution, and now my ZF3 is working but its showing a second screen with a error when it boots.
1 - download a zip file rom from asus site
2 - open it with winrar or another of your choice
3 - go to \META-INF\com\google\android
4 - open the updater-script with a text editor
5 - search for all the words WW_Phone and replace it for omni_ze552kl
6 - save the change and close, update the file inside the compressed zip
7 - put the zip rom inside your phone and flash it through twrp, done!
*sorry about english, its not my native lang.

Hi SuperDizor,
The issues you are having are both caused by the installation of TWRP 3.0.2. that was compiled for the Zenfone 3 using omni_ze55kl as the device type instead of WW_ZE552KL or CN_ZE552KL. I assume that the person that compiled it tried to make TWRP as universal as possible (instead of making two different versions, one for each device type - the TWRP code would have been the same except for this string...). However, the updater checks for this device type string and fails (unless you modify the updater config file as described in the post above). This is also why flashing stock recovery solved your issue.
The second error message you have, the one with dm-verity not being in enforcing mode was caused by having you install TWRP and allowing it to modify the system partition. This was necessary in the past but not anymore. When you flash TWRP, the first time you start it, it ask for your permission the make the system read-write, and you should refuse, as TWRP will function anyway and you will not get the dm-verity error. The dm-verity thingy is a software module in the bootloader (aboot to be precise) that checks the integrity of the system partition. TWRP has to force it in non-enforcing mode since it modifies the system partition and your device would not boot if it left dm-verity in enforcing mode. When you don't let TWRP modify the system partition (ie staying read-only), it does not change the dm-verity mode and you don't get warning messages. Don't worry, TWRP will still enable you to root your device and do whatever it does even if it is in "read only" mode.
Hope this helps !

I just got this error seemingly out of the blue on my ZenFone 3 Laser. I didn't do anything, just walked up and it was showing this screen
Code:
The dm-verity is not started in enforcing mode and may not work properly
To learn more, visit: g.co/placeholder
Haven't rooted, unlocked bootloader, or tried to install any rom manually.

Same happened with my device too. How did you fix it? Can you please let me know the procedure for same.
---------- Post added at 03:26 AM ---------- Previous post was at 03:24 AM ----------
Niemer said:
I just got this error seemingly out of the blue on my ZenFone 3 Laser. I didn't do anything, just walked up and it was showing this screen
Code:
The dm-verity is not started in enforcing mode and may not work properly
To learn more, visit: g.co/placeholder
Haven't rooted, unlocked bootloader, or tried to install any rom manually.
Click to expand...
Click to collapse
Same happened with my device too. How did you fix it? Can you please let me know the procedure for same. Thanks

SuperDizor said:
I was able to fix my phone with flashing both boot.img and recovery.img with stock image and i used WW-13.16.5.36 firmware to flash and it's worked.
Thanks for the help JadeKubPom
Click to expand...
Click to collapse
but how to flash? its not booting in recovery mode.

Stock ROM for YB1-X90F

Where I can I download the stock ROM for this model of Yoga Book? I hosed up my machine trying to root. I can boot into recovery mode, hopefully I can flash a new ROM to recover.
Thanks,,,

This could help ...
Edit: 2017/02/21: Link has expired
You can try this one: http://s55.filefactory.com/get/f/osm8z9hwyrz/1844e07b49cb41c8/YB1-X90L_USR_S000155_1609272258_WW06_BP_ROW-flashfiles.zip
It is for YB1-X90L, however, I had success with my X90F. Download just lasts 10 hours if you don' t want to subscribe

yoga-user said:
you can try this one: (http) s55.filefactory.com/get/f/osm8z9hwyrz/1844e07b49cb41c8/YB1-X90L_USR_S000155_1609272258_WW06_BP_ROW-flashfiles.zip
It is for YB1-X90L, however, I had success with my X90F. Download just lasts 10 hours if you don' t want to subscribe
Click to expand...
Click to collapse
Be aware that you'll lose use of the touchpad/halo kb if you flash this stock. Can't find any way of resolving this problem.

No - I' ve full access to all features!
Halo keybord has all functions and can be used without any restrictions. There' s nothing in stuck Only rooting with supersu isn' t possible and the machine is now identified as YB1-X90L and has some additional functions like symbol in toolbar for missing smartcard etc.
From stock-rom I flashed boot.img, bootloader, factory.img, recovery.img and system.img and first of all there where two updates ...

yoga-user said:
Halo keybord has all functions and can be used without any restrictions. There' s nothing in stuck Only rooting with supersu isn' t possible and the machine is now identified as YB1-X90L and has some additional functions like symbol in toolbar for missing smartcard etc.
From stock-rom I flashed boot.img, bootloader, factory.img, recovery.img and system.img and first of all there where two updates ...
Click to expand...
Click to collapse
I reflashed the stock ROM (using Intel PhoneFlash Tool), then allowed the two updates. Still no sketchpad/halo function at all. Do I understand from your last paragraph that you then flashed those imgs after the two updates?

zamzenos said:
I reflashed the stock ROM (using Intel PhoneFlash Tool), then allowed the two updates. Still no sketchpad/halo function at all. Do I understand from your last paragraph that you then flashed those imgs after the two updates?
Click to expand...
Click to collapse
Hi,
I used regular adb / fastboot. As my Yoga was totally stucked I flashed all the images and then installed the updates. Now it' s build LenovoYB1-X90L_S000241_161209, Kernel-Version 3.14.55-x86_64-ga6a34be.
Last of all I locked Bootloader and restored all my Apps.
Good luck!

yoga-user said:
Hi,
I used regular adb / fastboot. As my Yoga was totally stucked I flashed all the images and then installed the updates. Now it' s build LenovoYB1-X90L_S000241_161209, Kernel-Version 3.14.55-x86_64-ga6a34be.
Last of all I locked Bootloader and restored all my Apps.
Good luck!
Click to expand...
Click to collapse
My only options to flash any of the img files is through adb sideload or placing them on the sdcard and installing via recovery. Every attempt fails with an E:footer is wrong; E:signature verification failed message. I can't find any way around the errors.

booneb50 said:
My only options to flash any of the img files is through adb sideload or placing them on the sdcard and installing via recovery. Every attempt fails with an E:footer is wrong; E:signature verification failed message. I can't find any way around the errors.
Click to expand...
Click to collapse
Have you tried the Intel PhoneFlash Tool? So far I've managed to flash the Stock twice, but with the pad/halo problem I described above.

booneb50 said:
My only options to flash any of the img files is through adb sideload or placing them on the sdcard and installing via recovery. Every attempt fails with an E:footer is wrong; E:signature verification failed message. I can't find any way around the errors.
Click to expand...
Click to collapse
Hi,
with this procedure I could restore my bricked device:
- like described at this thread: https://forum.xda-developers.com/showthread.php?t=2588979, I downloaded and installed universal adb / fastboot and fixed fastboot drivers
- then unzipped YB1-X90L_USR_S000155_1609272258_WW06_BP_ROW-flashfiles.zip and copied boot.img, bootloader, factory.img, recovery.img and system.img to my adb-folder (%UserProfile%\adb)
Caution: The next steps will wipe all your personal data! It' s a complete reset to factory settings!!!
- rebooted my device with "Volume up" and "Power" to bootloader (fastboot mode) and then connected it via usb
- opened cmd and navigated to my adb-folder
- tested fastboot mode with command "fastboot devices" with success and
- then flashed all the images (as referred to above) with fastboot commands: fastboot flash boot boot.img, fastboot flash bootloader bootloader and so on.
- after it I rebooted my device to system - be patient, don't power off, it can last very long time before first boot .
- as I had no success with supersu, at this point I decided for myself to relock bootloader - this was the second reset to factory settings
-then I re-installed all my apps manually and restored settings, contacts and calendar from my google-account
I hope, this helps

yoga-user said:
Hi,
with this procedure I could restore my bricked device:
- like described at this thread: https://forum.xda-developers.com/showthread.php?t=2588979, I downloaded and installed universal adb / fastboot and fixed fastboot drivers
- then unzipped YB1-X90L_USR_S000155_1609272258_WW06_BP_ROW-flashfiles.zip and copied boot.img, bootloader, factory.img, recovery.img and system.img to my adb-folder (%UserProfile%\adb)
Caution: The next steps will wipe all your personal data! It' s a complete reset to factory settings!!!
- rebooted my device with "Volume up" and "Power" to bootloader (fastboot mode) and then connected it via usb
- opened cmd and navigated to my adb-folder
- tested fastboot mode with command "fastboot devices" with success and
- then flashed all the images (as referred to above) with fastboot commands: fastboot flash boot boot.img, fastboot flash bootloader bootloader and so on.
- after it I rebooted my device to system - be patient, don't power off, it can last very long time before first boot .
- as I had no success with supersu, at this point I decided for myself to relock bootloader - this was the second reset to factory settings
-then I re-installed all my apps manually and restored settings, contacts and calendar from my google-account
I hope, this helps
Click to expand...
Click to collapse
Hi, I also meet the same problem and need this X90L_USR_S000155_1609272258_WW06_BP_ROW-flashfiles.zip file for recovery, but it seems the link which you shared before expired, can you help to share with me your copy or create another link? Thanks a lot!

Even_xf said:
Hi, I also meet the same problem and need this X90L_USR_S000155_1609272258_WW06_BP_ROW-flashfiles.zip file for recovery, but it seems the link which you shared before expired, can you help to share with me your copy or create another link? Thanks a lot!
Click to expand...
Click to collapse
... you have PM

can i get the link as well?

it would be very nice if someone can help with a download link for yb1-x90l complete rom or even only recovery.img

can you please share the link again?

All the firmware for both models are available at: http://www.easy-firmware.com/index.php. You have to take a subscription to be able to download the files. Files are exclusive downloads. Subscription at $15. Latest versions are the november firmware.
Verstuurd vanaf mijn Lenovo YB1-X90L met Tapatalk

vogemic said:
All the firmware for both models are available at: http://www.easy-firmware.com/index.php. You have to take a subscription to be able to download the files. Files are exclusive downloads. Subscription at $15. Latest versions are the november firmware.
Verstuurd vanaf mijn Lenovo YB1-X90L met Tapatalk
Click to expand...
Click to collapse
I find this very strange this site charges to download the firmware that cannot be found from any other reputable site that I have searched on. It may well be legit but I will steer clear anyway.

keybord
zamzenos said:
Be aware that you'll lose use of the touchpad/halo kb if you flash this stock. Can't find any way of resolving this problem.
Click to expand...
Click to collapse
you need to input country code to enable keyboard. There are several steps as below :
a) Open ‘’contacts’’ app, create a new local contact ” test”
b) Click search button at contact
c) Input ####6020# code into search bar
d) Browser the country code list, then chose country code you want to use, such as US
e) Then DUT will reboot

vimalbhimani said:
you need to input country code to enable keyboard. There are several steps as below :
a) Open ‘’contacts’’ app, create a new local contact ” test”
b) Click search button at contact
c) Input ####6020# code into search bar
d) Browser the country code list, then chose country code you want to use, such as US
e) Then DUT will reboot
Click to expand...
Click to collapse
Long time coming. Thanks for taking the trouble to detail the method. However, in order to update to lastest firmware I was obliged to input a cc. I assumed then that I had got the Halo etc working simply by updating the firmware(!). Even so, good to know why I didn't have Halo. This info is sure to be of benefit to others. Thank you.

yoga-user said:
... you have PM
Click to expand...
Click to collapse
Can you please send me the link as well?

wait for new link download
need stock recovery backup
I will try install windows on android version
I think same Mipad2 (android version can install Windows ) install windows
http://en.miui.com/thread-248564-1-1.html

Lenovo K6 without OS

Hi, I already had my phone rooted and with TWRP installed, but I needed to restore my phone. First I did this trough the system, but I noted that a lot of old files still were there, and I went to TWRP and did a wipe, but selected /system and /cache, now I don't have a OS on my phone.
The phone doesn't turn off, everytime I try to power off, he turn on again, and stay on Lenovo logo. The only thing I can acess is Fastboot mode (via Power down + power), I cant acess TWRP trough the phone, but I found a .bat file, that when I'm in fastboot mode, it flashes twrp on my phone and I can acess it . The other problem is that I always get an error when trying to flash any rom. Things like Error:255 or ".zip file not valid". Tried 2 roms and nothing.
Can someone please help me? I would prefer a stock rom for Brazil, but now I just want any rom, dont even mind if it's not stock.

Crolys said:
Hi, I already had my phone rooted and with TWRP installed, but I needed to restore my phone. First I did this trough the system, but I noted that a lot of old files still were there, and I went to TWRP and did a wipe, but selected /system and /cache, now I don't have a OS on my phone.
The phone doesn't turn off, everytime I try to power off, he turn on again, and stay on Lenovo logo. The only thing I can acess is Fastboot mode (via Power down + power), I cant acess TWRP trough the phone, but I found a .bat file, that when I'm in fastboot mode, it flashes twrp on my phone and I can acess it . The other problem is that I always get an error when trying to flash any rom. Things like Error:255 or ".zip file not valid". Tried 2 roms and nothing.
Can someone please help me? I would prefer a stock rom for Brazil, but now I just want any rom, dont even mind if it's not stock.
Click to expand...
Click to collapse
Error 255 is caused because you are trying to install a 64bit ROM over TWRP (32bits), you need to upgrade TWRP to 64bit, just so you will be able to install a ROM. Remember that you should use Gapps in 64bit [ARM64]
TWRP: https://dl.twrp.me/karate/twrp-3.1.1-1-karate.img
Gapps: http://opengapps.org/ (ARM64)

J.D.M said:
Error 255 is caused because you are trying to install a 64bit ROM over TWRP (32bits), you need to upgrade TWRP to 64bit, just so you will be able to install a ROM. Remember that you should use Gapps in 64bit [ARM64]
Click to expand...
Click to collapse
I already had this version of twrp, but downloaded anyway and got the same error when tring to sideload a ROM "Updater process ended with ERROR: 255" . I don't know what to do anymore, I tried with 4 different ROMs, also I searched for a method to erase the lines with asserts on "update-scripts" in META-INF, but then I got a "Invalid ZIP file" error.

Crolys said:
I already had this version of twrp, but downloaded anyway and got the same error when tring to sideload a ROM "Updater process ended with ERROR: 255" . I don't know what to do anymore, I tried with 4 different ROMs, also I searched for a method to erase the lines with asserts on "update-scripts" in META-INF, but then I got a "Invalid ZIP file" error.
Click to expand...
Click to collapse
Try to go back to the 32bits version and erase everything and format the data and return to the 64bit version because here I had this problem it was because of the TWRP that I was using, it was the 32bits version, after that I upgraded to the 64bits version I did not have this problem. Remembering that in the site https://dl.twrp.me/karate/ has two versions of TWRP, the version twrp-3.1.1-0-karate.img is 32bits and the version twrp-3.1.1-1-karate. img is 64bit.

J.D.M said:
Try to go back to the 32bits version and erase everything and format the data and return to the 64bit version because here I had this problem it was because of the TWRP that I was using, it was the 32bits version, after that I upgraded to the 64bits version I did not have this problem.
Click to expand...
Click to collapse
Well, that kinda worked(?), now I have another error it says that my firmware is incompatible with the ROM version, and I need to update it (I dont know how to do this), and give me ERROR: 7 now

Crolys said:
Well, that kinda worked(?), now I have another error it says that my firmware is incompatible with the ROM version, and I need to update it (I dont know how to do this), and give me ERROR: 7 now
Click to expand...
Click to collapse
MAN, the ERROR: 7 now could be solved by deleting the lines with ASSERT in "\META-INF\com\google\android\updater-script".
So, thanks for helping me, the problem with 64/32bits worked. I'm really glad that this worked, had stuck for 3 days without OS, now i'm never messing with this stuff again haha.

Crolys said:
MAN, the ERROR: 7 now could be solved by deleting the lines with ASSERT in "\META-INF\com\google\android\updater-script".
So, thanks for helping me, the problem with 64/32bits worked. I'm really glad that this worked, had stuck for 3 days without OS, now i'm never messing with this stuff again haha.
Click to expand...
Click to collapse
I've been researching and was going to tell you to delete the above lines mentioned, I am glad you have succeeded.

got same 255 error,just now i reflashed stock rom and issue resolved

vasu009 said:
got same 255 error,just now i reflashed stock rom and issue resolved
Click to expand...
Click to collapse
how did you reflashed the stock rom, please reply cause im stuck with the twrp and unable to do it. my phone doesn't have an os now

what s the password of the trwp

J.D.M said:
I've been researching and was going to tell you to delete the above lines mentioned, I am glad you have succeeded.
Click to expand...
Click to collapse
Can install this ROM on any Lenovo K6 Power device ??

dushd95 said:
Can install this ROM on any Lenovo K6 Power device ??
Click to expand...
Click to collapse
Yeah

J.D.M said:
Yeah
Click to expand...
Click to collapse
It says device not supported why??

Dont forget to reboot again into twrp - after flashing 64bit twrp . This is a step that is very important if you will not reboot your phone into twrp after flashing 64 bit twrp then , it will keep showin you the error 255.
So check that .

wacccim said:
what s the password of the trwp
Click to expand...
Click to collapse
Go for 3.2.1.0 it is better then 3.1.1.1 in 64 bits it ain't ask password i use it to flash all roms

Tere 3.1.1-1 asking for password to encrypt data
I flashed my Lenovo k6 power with twrp 3.1.1-1 after I was not able to flash crdroid,lineage is,pixelized stock ROM to my phone. Now the twrp is asking for password to encrypt data and I am surprised because I hadn't set a password. I tried to unlock it with my phone password but I it is saying to enter correct password.
Please someone help me. I am not able to flash other things too please somebody help me.:

Erase the data
Shrestha Kumar said:
I flashed my Lenovo k6 power with twrp 3.1.1-1 after I was not able to flash crdroid,lineage is,pixelized stock ROM to my phone. Now the twrp is asking for password to encrypt data and I am surprised because I hadn't set a password. I tried to unlock it with my phone password but I it is saying to enter correct password.
Please someone help me. I am not able to flash other things too please somebody help me.:
Click to expand...
Click to collapse
Use erase the data from wipe option then you will be able to install rom and g-apps.
Every time you will need password, I don't know why but after erasing data you install all files otherwise you need to erase data again and again

Crolys said:
Hi, I already had my phone rooted and with TWRP installed, but I needed to restore my phone. First I did this trough the system, but I noted that a lot of old files still were there, and I went to TWRP and did a wipe, but selected /system and /cache, now I don't have a OS on my phone.
The phone doesn't turn off, everytime I try to power off, he turn on again, and stay on Lenovo logo. The only thing I can acess is Fastboot mode (via Power down + power), I cant acess TWRP trough the phone, but I found a .bat file, that when I'm in fastboot mode, it flashes twrp on my phone and I can acess it . The other problem is that I always get an error when trying to flash any rom. Things like Error:255 or ".zip file not valid". Tried 2 roms and nothing.
Can someone please help me? I would prefer a stock rom for Brazil, but now I just want any rom, dont even mind if it's not stock.
Click to expand...
Click to collapse
I Faced same problem. It's ok that your phone is in weird state for time now. And also possible to recover.
Hopefully you have adb-tool, custom-rom & gapp, twrp.img on your PC.
1) Boot your mobile in fastmode using Power ON with Volume down key for 5 sec (Lenovo log with left hand side sayinh fastboot mode)
2) Connect the mobile to PC using USB & Go to adb tool folder. Open command prompt in this folder & Execute the follow step by step execution
fastboot oem reboot-recovery
3)Wait for mobile to boot in to recovery mode with TWRP
Now need to flash custom-rom followed by gapps installion.
I) You can use pendrive with otg to flash custom-rom followed by gapps
OR
II)You can use phone storage/SD card to flash the custom-rom followed by gapps
OR
III)adb sideload command as fallow
a)In TWRP recovery on mobile, goto Adavanced->ADB Sideload & Swipe to start the sideload
Now on PC execute . Specify custom rom path inside ""
adb sideload "C:\adb\images\MyCustomROM.zip"
Have a patience to complete the operation.
Click back for Adavanced Menu again.
b) Select ADB Sideload & Swipe to start the sideload
Now on PC execute . Specify Gapp path inside ""
adb sideload "C:\adb\images\open_gapps-arm-7.1-pico-20180611.zip"
c)Have a patience to complete the operation.
Once complete go to TWRP Screen.
d)Now go back TWRP main menu & select wipe->format Data.
Go to Reboot->system.
How to install TWRP if no OS there
1) Boot your mobile in fastmode using Power ON with Volume down key for 5 sec (Lenovo log with left hand side sayinh fastboot mode)
2) Connect the mobile to PC using USB & Go to adb tool folder. Open command prompt in this folder & Execute the follow step by step execution
a) To check the device is connected to PC or not
fastboot oem device-info
b) To flash the recovery. Give twrp path inside the ""
fastboot flash recovery "C:\adb\images\twrp.img"
c) To boot into recovery mode
fastboot oem reboot-recovery
---------- Post added at 10:03 PM ---------- Previous post was at 09:57 PM ----------
[/COLOR]
Shrestha Kumar said:
I flashed my Lenovo k6 power with twrp 3.1.1-1 after I was not able to flash crdroid,lineage is,pixelized stock ROM to my phone. Now the twrp is asking for password to encrypt data and I am surprised because I hadn't set a password. I tried to unlock it with my phone password but I it is saying to enter correct password.
Please someone help me. I am not able to flash other things too please somebody help me.:
Click to expand...
Click to collapse
In my case, It worked with PIN.

[Recovery][8.0][Unofficial] TWRP 3.2.1-0 for EMUI 8.0 (06/05/2018)

AWARE! THIS IS NOT MY WORK! ONLY SHARE HERE FOR TEST PURPOSE!!​
Hello guys! Our p10 doesn't have received so much love from developers around here, anyway, there's some small works to make things easier for p10 users, like @OldDroid TWRP version for EMUI 5.x and some advances from @Blackball on the ROM department.
Right now, for p10 users who had updated their devices to EMUI 8.0, we didn't have any "official" twrp working to our systems, so we have to use Blackball's TWRP version for P10 plus (8.0) with some drawbacks like ADB not working over USB or decrypting /data partition.
I was looking for a solution around this and checking ROM systems across Huawei/Honor platform and i have found something interesting on Honor View 10 forums: a working TWRP which works very well with our p10 8.0 system. I have installed and tested some functions and seems to works very well, so i'm bring it to you to give some more extended testing about TWRP functionality under our system.
Disclaimer
This software comes with no warranty,XDA staff ,myself or TeamWin stuff can't be hold responsible for any damage it may cause to your device.​
Download and Installation
Download twrp recovery
Start your device in fastboot mode
Install the recovery using the following command:
Code:
fastboot flash recovery_ramdisk [name of the file].img --> ex: fastboot flash recovery_ramdisk twrp_blanc_0.1.img
Restart with this command:
Code:
fastboot reboot
Enter to the recovery and try it: Vol + (at device boot up)
IMPORTANT: /data decryption is only necessary if you have set up fingerprint and pin code. If you have it, you only have to introduce your password ONCE (at first TWRP boot up) and in other reboots only cancel this action and you're ready to go.
WHAT I HAVE TESTED:
Decrypting data partition: works
Mounting /system partition: works
Installing ZIP over /system: works
ADB over USB (including ADB sideload): works
MTP function: works
Backup&Restore: works
THINGS THAT NEED TO BE TESTED:
IMG writing
OTG function
CREDITS:
**** @zxz0O0 - This wouldn't be possible without this guy,so big big thank to him. *** i know him from my SONY devices time, a superb and talented developer ***
**** @Pretoriano80 - This guy have made all the adaptation of this TWRP for Mate 10/Honor View 10 from zxz0O0 work... All my respect for him!
**** TeamWin project ,obviously.
DOWNLOAD LINK:
PLEASE TRY IT AND REPORT BACK!
(06/05)NEW VERSION, THANKS TO @Pretoriano80 for the new build GO GIVE HIM SOME LOVE THERE
CHANGELOG:
mounting/unmounting issues shound be fixed , added a new option to exclude OEM path from wiping with Factory Reset and can be enabled/disabled in settings (thx Team OpenKirin for this), this version will work even with newer updates that bump security patch version.
wipe cache is now fixed
fixed decryption on EMUI 8.1 (now you can use the same password/pin/pattern to decrypt in TWRP), /recovery_ramdisk no longer available for backup./vendor no longer available for backup (use /vendor_image instead),/system and /data can be unmounting issue with 8.1 devices is now fixed.
ORIGINAL SOURCE:
GO THERE AND SHOW SOME LOVE TO DEVS
TROUBLESHOOTING
Some of you have been reporting that mounting /system or another partitions doesn't work. I have discover that you need to decrypt data *before* to mount any other partitions.

espaciosalter20 said:
AWARE! THIS IS NOT MY WORK! ONLY SHARE HERE FOR TEST PURPOSE!!​
Hello guys! Our p10 doesn't have received so much love from developers around here, anyway, there's some small works to make things easier for p10 users, like @OldDroid TWRP version for EMUI 5.x and some advances from @Blackball on the ROM department.
Right now, for p10 users who had updated their devices to EMUI 8.0, we didn't have any "official" twrp working to our systems, so we have to use Blackball's TWRP version for P10 plus (8.0) with some drawbacks like ADB not working over USB or decrypting /data partition.
Click to expand...
Click to collapse
after flashing it loops after twrp start screen

funiewski said:
after flashing it lopps after twrp start screen
Click to expand...
Click to collapse
Same, twrp not loading menu screen, restart.

funiewski said:
after flashing it loops after twrp start screen
Click to expand...
Click to collapse
ok, checked. /data decryption is only necessary if you have set up fingerprint and pin code. If you have it, you only have to introduce your password ONCE (at first TWRP boot up) and in other reboots only cancel this action and you're ready to go.

espaciosalter20 said:
ok, checked. /data decryption is only necessary if you have set up fingerprint and pin code. If you have it, you only have to introduce your password ONCE (at first TWRP boot up) and in other reboots only cancel this action and you're ready to go.
Click to expand...
Click to collapse
Maybe it's misunderstanding but twrp never goes further than start screen for me

funiewski said:
Maybe it's misunderstanding but twrp never goes further than start screen for me
Click to expand...
Click to collapse
weird... can you tell me about your device? which p10 version (vtr-l09 or vtr-l29) and which EMUI version? thanks!

espaciosalter20 said:
weird... can you tell me about your device? which p10 version (vtr-l09 or vtr-l29) and which EMUI version? thanks!
Click to expand...
Click to collapse
VTR-L29, Android 8.1, RR rom, Gatorade kernel

funiewski said:
VTR-L29, Android 8.1, RR rom, Gatorade kernel
Click to expand...
Click to collapse
Ok, thank you. On Original Thread this bug is also tracked. Right now, this version doesn't work on 8.1 roms... You have to wait for debugging...

Hi...successfully flashed it without any errors (not using pincode or fingerprint)...
while backing up,it says it doesnt backup imgs and files in download in /data
(isnt it the main reason why we do backups? )

virusdunil said:
Hi...successfully flashed it without any errors (not using pincode or fingerprint)...
while backing up,it says it doesnt backup imgs and files in download in /data
(isnt it the main reason why we do backups? )
Click to expand...
Click to collapse
TWRP never did internal storage backups, you can do thst with your PC, OTG, etc... you don't need a custom recovery for that.

Confirm working for me on L09C432 using stock oreo firmware. '/data' seems to be decrypted and also 'adb shell' was successful.
I had to use
Code:
adb reboot recovery
though, Vol+ on bootup always takes me to eRecovery (which I assume is a good thing).
Edit: One thing I noticed is that this recovery does not mount the same partitions as the stock firmware does. For instance when using adb shell, /system showed different contents when started using recovery. I was able to do mount the correct /system partition manually though.

tadeussenf said:
Confirm working for me on L09C432 using stock oreo firmware. '/data' seems to be decrypted and also 'adb shell' was successful.
I had to use though, Vol+ on bootup always takes me to eRecovery (which I assume is a good thing).
Edit: One thing I noticed is that this recovery does not mount the same partitions as the stock firmware does. For instance when using adb shell, /system showed different contents when started using recovery. I was able to do mount the correct /system partition manually though.
Click to expand...
Click to collapse
Vol+ takes you to erecovery if you don't press it right after you power ON. Or if it's connected to PC, i think.

why I cannot flash this kernel zip? I can flash it only from blackball TWRP for P10+?

DallasCZ said:
why I cannot flash this kernel zip? I can flash it only from blackball TWRP for P10+?
Click to expand...
Click to collapse
Could you share your what's your error message?

It was something like error 1: wrong partition name. Some other P10 users have same problem, the only solution is to use Blackball P10+ TWRP recvoery, but that recovery doesnt support decryption and USB storage.

TWRP automatically shuts down for somehow after few seconds.

espaciosalter20 said:
AWARE! THIS IS NOT MY WORK! ONLY SHARE HERE FOR TEST PURPOSE!!​
Hello guys! Our p10 doesn't have received so much love from developers around here, anyway, there's some small works to make things easier for p10 users, like @OldDroid TWRP version for EMUI 5.x and some advances from @Blackball on the ROM department.
Right now, for p10 users who had updated their devices to EMUI 8.0, we didn't have any "official" twrp working to our systems, so we have to use Blackball's TWRP version for P10 plus (8.0) with some drawbacks like ADB not working over USB or decrypting /data partition.
I was looking for a solution around this and checking ROM systems across Huawei/Honor platform and i have found something interesting on Honor View 10 forums: a working TWRP which works very well with our p10 8.0 system. I have installed and tested some functions and seems to works very well, so i'm bring it to you to give some more extended testing about TWRP functionality under our system.
Disclaimer
This software comes with no warranty,XDA staff ,myself or TeamWin stuff can't be hold responsible for any damage it may cause to your device.​
Download and Installation
Download twrp recovery
Start your device in fastboot mode
Install the recovery using the following command:
Code:
fastboot flash recovery_ramdisk [name of the file].img --> ex: fastboot flash recovery_ramdisk twrp_blanc_0.1.img
Restart with this command:
Code:
fastboot reboot
Enter to the recovery and try it: Vol + (at device boot up)
IMPORTANT: /data decryption is only necessary if you have set up fingerprint and pin code. If you have it, you only have to introduce your password ONCE (at first TWRP boot up) and in other reboots only cancel this action and you're ready to go.
WHAT I HAVE TESTED:
Decrypting data partition: works
Mounting /system partition: works
Installing ZIP over /system: works
ADB over USB (including ADB sideload): works
MTP function: works
THINGS THAT NEED TO BE TESTED:
Backup&Restore
IMG writing
OTG function
CREDITS:
**** @zxz0O0 - This wouldn't be possible without this guy,so big big thank to him. *** i know him from my SONY devices time, a superb and talented developer ***
**** @Pretoriano80 - This guy have made all the adaptation of this TWRP for Mate 10/Honor View 10 from zxz0O0 work... All my respect for him!
**** TeamWin project ,obviously.
DOWNLOAD LINK:
PLEASE TRY IT AND REPORT BACK!
ORIGINAL SOURCE:
GO THERE AND SHOW SOME LOVE TO DEVS
Click to expand...
Click to collapse
Man Whay you do not take old TWRP Kirin edition, and just 3110 and just ad emui8 to work, i have it, but I can now beacose, I have 37 models program repairs for what I am paid of.

what?

f0rb1d said:
TWRP automatically shuts down for somehow after few seconds.
Click to expand...
Click to collapse
i have the same problem

This is the error that occurs in TWRP when flashing the HYPER Kernel. The only way to flash the Kernel is using BlackBall TWRP (but his TWRP doesnt support data decryption and usb connection to PC).