Related
Hi everyone,
I've run out of ideas on this one and other threads couldn't really help me/were closed already.
I tried CM, stock android by Ivan and M1cha as well as some others, but about a month ago, I was curios for MIUI 6 based on Lollipop for my Mi2s and changed from M1cha's CM12 5.0.1.
Now that I've seen that Ivan published his 5.1.1 I wanted to try it out. He also provides us with a modified custom recovery that I wanted to flash.
First, I renamed the file to update.zip and tried to flash it in Mi-Recovery 2.0.1, which didn't work due to the failing signature verification.
Also, choosing update package in the Updater app in MIUI didn't work out, it immediately tells me something went wrong.
Then I thought, why not use fastboot? That worked before.
Not this time. I tried the simple way, meaning just fastboot flash recovery recovery.img: Then, bc it didn't work, I first erased the recovery partition and then flashed the recovery.img, which was still unsuccessful.
Whenever I try to enter recovery mode, my phone just gets stuck showing the MI logo and not doing anything.
I can reenter fastboot mode or simply reboot to the system as usual, except for when no system is installed.
When I gave up on the custom recovery thing, I simply tried to flash the ROM via update.zip methods, as well as via fastboot. None of them worked, either because the signature verification fails (stock recovery) or because the zip file does not contain the android-info.txt and the other txt file.
As mentioned above, upon entering fastboot -w and then flashing the recovery.img, I can suddenly enter recovery mode. This sucks!
TL;DR: No usual method of flashing either custom rom or recovery works (to my knowledge)
Can anyone help me? I know its stupid but I start feeling kind of boxed in on MIUI.
Thanks in advance
fastboot oem unlock
fastboot flash recovery recovery.img
unfortunately, that didn't work either...
leonfromotown said:
unfortunately, that didn't work either...
Click to expand...
Click to collapse
Do fastboot devices and tell us the output
SkiFire13 said:
Do fastboot devices and tell us the output
Click to expand...
Click to collapse
5b799fb fastboot
looks just the way it did before
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.
Please. Any ideas. Are the anothers methodes to install firmware for my yd201? I have tried yotaflasher, fastboot, twmp who are really installed the filles, .imgs but my phone restart in botloop with logo android. I have unloked mt phone and i ca't return it, i have losed d:crying:e warenty
The only method surefire method is still using yotaflasher and check the output while flashing to see if everything goes right. If you get a chunk error on the system partition flash this partition by hand using fastboot. If this (and all the other methods you mention) don't work there may be something wrong with your phone.
Have you already tried flashing back to the HK version to see if that works?
Today i have installed all the firmware Ru and it was ok. No errors but. After restart bootloader with logo by android. My phone is a yd201 international version buyed under www.coolicool.com The original soft it was HK? I have not tried yet. Only EU and RU.
Hi, I had soft brick two times, because i tryied to unlock bootloader a flash twrp 3.0.2. ibtw now succesfully. Yotaflasher helps to make my phone alive with latest UE version. Hope it helps
Synthi said:
Hi, I had soft brick two times, because i tryied to unlock bootloader a flash twrp 3.0.2. ibtw now succesfully. Yotaflasher helps to make my phone alive with latest UE version. Hope it helps
Click to expand...
Click to collapse
I have already unooked bootloader that it was ok. I have installed with fastboost twrp 2.8.5 and also 3.0.2 but after reboot it rest in bootloop logo android. The command fastboot works but adb don t see my phone. I wonderred if that because it is not actived usb debuggind..
This thread will be for the Canadian version of ZE552KL, and will be updated with specific info relevant to Z012DC model found in Canada (Canada Computers, Staples, other retailers). It has WW SKU number.
It took me a while and some searching to figure all steps out. I also modified Asus N and M firmware to remove version checks. Without this step - i was stuck with error 7 in TWRP. The only difference between Z012D and Z012DC seems to be in Fastboot and ADB drivers, TWRP recovery, system images seem to work well so far.
Steps:
1. Download Fastboot and ADB Drivers. For me usb driver on ZE552KL Asus download page didn't work. Select "Only install driver", you do not need to update your drivers via DRP.
Fastboot driver (for Vendor VID_18D1&PID_D00D): http://drivers.drp.su/Telephone/Hua...03.00/Huawei-FORCED-Allx64-2.00.03.00-drp.exe
ADB Driver (for VID_18D1&PID_D002): http://drivers.drp.su/Telephone/Leshcat/WinAll/Leshcat-WinAll-drp.exe
2. Save the following files on your External SD Card:
Modified M image UL-ASUS_Z012D-WW-13.20.10.152-user.zip
Modified N image UL-ASUS_Z012D-WW-14.2015.1701.8-user.zip
SuperSU - latest version from here
no-verity-opt-encrypt-5-1.zip. Give thanks to @kaffeine1 , without him - we would all be stuck with black screens
3. Save ADB and Fastboot files on your computer, and extract; give thanks to @snowwolf725
4. Download newer recovery (TWRP 3.1.0) from here
5. Unlock bootloader via unofficial unlock method; give thanks to @snowwolf725
6. Get into fastboot by turning off the phone, and pressing volume up + power. Install recovery that you downloaded in step #4:
Code:
fastboot flash recovery twrp-3.1.0-0-Z012D.img
7. Follow the steps this guide by @kaffeine1 . Skip the steps of downloading Nougat and Marshmallow firmware from Asus site, as you have already downloaded and saved both firmwares in Step #2 . Also skip the last step - do not reboot into Nougat, but go back to fastboot mode.
8. Root Nougat - follow steps under #2 here:
https://forum.xda-developers.com/zenfone-3/how-to/twrp-recovery-3-0-2-root-zenfone-3-t3569926
How to update to the latest version of OS:
1. Go to Asus Site, download latest WW image UL-ASUS_Z012D-WW-14.2020.1703.28-user.zip
2. Extract UL-ASUS_Z012D-WW-14.2020.1703.28-user.zip\META-INF\com\google\android\updater_script , edit, remove first two lines, and put back into the zip file (e.g. using 7zip)
3. Extract from above zip file boot.img , and flash it via: fastboot flash boot boot.img
4. Flash recovery: fastboot flash recovery twrp-3.1.0-0-Z012D.img
5. Reboot into recovery, and flash:
- Firmware that you modified in #2
- no-verity-opt-encrypt-5.1.zip
- Latest SuperSU
- Rooted.zip (from step #8 above)
6. Reboot mobile, and enjoy new version!
Phone info as purchased:
Model Number: ASUS_Z012DC
Android version: 6.0.1
Baseband version: M3.10.42-Libra_080001
Build number: MMB29P.WW_Phone-13.20.10.152-20161222
Manufacture date (on the box): January 2017
Latest version - UL-ASUS_Z012D-WW-14.2020.1703.28-user.zip
Model Number: ASUS_Z012DC
Android version: 7.0
Baseband version: M3.10.47-Libra_080001
Build number: NRD90M.WW_Phone-14.2020.1703.28-20170410
Special thanks to:
- @jcadduono for TWRP recovery
- @snowwolf725 for guide unlock bootloader
- @kaffeine1 for guide how to upgrade to N from M
Reserved for future use
can i follow this step for ZE520KL ?
I got my self a canadian vertion ZE552KL, but i can´t seem to fully unlock the boot loader, it goes onto fastboot, but it does not allow me to flash anything it gives a permision denied .
when i tried to flash fw from sdcard gives a error: the the sku is "WW_" and mine is ""
have you came across this problem.
how can it be solved?
thanks
lastremnant said:
can i follow this step for ZE520KL ?
Click to expand...
Click to collapse
no, I do not think so. these are different phones.
DilipRB said:
I got my self a canadian vertion ZE552KL, but i can´t seem to fully unlock the boot loader, it goes onto fastboot, but it does not allow me to flash anything it gives a permision denied .
when i tried to flash fw from sdcard gives a error: the the sku is "WW_" and mine is ""
have you came across this problem.
how can it be solved?
thanks
Click to expand...
Click to collapse
try first flashing 6.0.1 firmware from asus site and then modified 7.0 firmware. if the error is when flashing 6.0 fw - try modified 6.0. and do paste specific rrror.
anterus said:
no, I do not think so. these are different phones.
Click to expand...
Click to collapse
nevermind sir, it worked for me
Strange things do happen!!!
anterus said:
try first flashing 6.0.1 firmware from asus site and then modified 7.0 firmware. if the error is when flashing 6.0 fw - try modified 6.0. and do paste specific rrror.
Click to expand...
Click to collapse
i was trying this because i wanted to upgrade fw to 7 and trying to unlock bootloader to flash twrp for backups...
I tried original Asus UL-ASUS_Z012D-WW-13.20.10.131-user and gave strange error after check... this fw is for "WW_Phone" and this phone is ""
but after reestart i got OTA updates... now my ZE552KL-Z012DC is in 7.0....
i can live with that, only problem for me is adb backups, i prefer twrp.
thanks
P.D. what pusles me is why getprop("ro.product.name") returns empty sting????
DilipRB said:
i was trying this because i wanted to upgrade fw to 7 and trying to unlock bootloader to flash twrp for backups...
I tried original Asus UL-ASUS_Z012D-WW-13.20.10.131-user and gave strange error after check... this fw is for "WW_Phone" and this phone is ""
but after reestart i got OTA updates... now my ZE552KL-Z012DC is in 7.0....
i can live with that, only problem for me is adb backups, i prefer twrp.
thanks
P.D. what pusles me is why getprop("ro.product.name") returns empty sting????
Click to expand...
Click to collapse
backup those zips, open with winrar or another app. open meta-inf/android/google/updater-script with notepad++ try deleting from ifelse until ) );
save and let winrar save new update
lastremnant said:
backup those zips, open with winrar or another app. open meta-inf/android/google/updater-script with notepad++ try deleting from ifelse until ) );
save and let winrar save new update
Click to expand...
Click to collapse
Tryed that, and got footer error...
seems that to modifying the script file and then recompresing will change the compretion check algorithem. giving a footer error.
i should try pakaging the apk again...
there was a program to do so but i cant recall which...
thks
DilipRB said:
Tryed that, and got footer error...
seems that to modifying the script file and then recompresing will change the compretion check algorithem. giving a footer error.
i should try pakaging the apk again...
there was a program to do so but i cant recall which...
thks
Click to expand...
Click to collapse
i found it ...
apktool from :
https://forum.xda-developers.com/showthread.php?t=1989533
Sorry this was for apks... but i guess same principle aplies... when i can i shall try and post the outcome
DilipRB said:
i was trying this because i wanted to upgrade fw to 7 and trying to unlock bootloader to flash twrp for backups...
I tried original Asus UL-ASUS_Z012D-WW-13.20.10.131-user and gave strange error after check... this fw is for "WW_Phone" and this phone is ""
but after reestart i got OTA updates... now my ZE552KL-Z012DC is in 7.0....
i can live with that, only problem for me is adb backups, i prefer twrp.
thanks
P.D. what pusles me is why getprop("ro.product.name") returns empty sting????
Click to expand...
Click to collapse
I noticed that in some cases TWRP doesn't "stick", and gets overridden by default bootloader. Specific check is essentially useless - just to prevent flash of improper image. Just remove the check in the new FW, or use modified FW that has the check removed. I think in your case you can just re-flash TWRP since your bootloader is unlocked?
I tryed several TWRP 3.02 and 3.10 if a boot imge ... if entered bootloader with volum key + power it says all ok but booting never happens... if i enter bootloader trough adb it stucks until i disconnect and reconnect usb cable. when trying to flash. fast boot returns error not have permision and side load error secttion 7 on UL modified or else footer w
error after passing check. i shall try modiffying UL 13.20.10 and see what happens
DilipRB said:
I tryed several TWRP 3.02 and 3.10 if a boot imge ... if entered bootloader with volum key + power it says all ok but booting never happens... if i enter bootloader trough adb it stucks until i disconnect and reconnect usb cable. when trying to flash. fast boot returns error not have permision and side load error secttion 7 on UL modified or else footer w
error after passing check. i shall try modiffying UL 13.20.10 and see what happens
Click to expand...
Click to collapse
flash modified images through twrp - with links in OP
Well my wife liked the phone so much, that she "kindly requested" me to gift it to her... now she is the proud owner of a canadian vertion of ZE552KL and i got myself a ZS570KL
thanks a lot for all your help.
P.D. : i think she was not happy with the time i was spending with the device.
I know this is going to sound super dumb, but the unofficial bootloader unlock still triggers the bootup message and voids the warranty, right?
This might be even dumber... But my guess is that the official app to unlock boot loader, does more than unlock,
My guess is that it also register with asus mobile, the fact that for your device has been unlocked...
DilipRB said:
This might be even dumber... But my guess is that the official app to unlock boot loader, does more than unlock,
My guess is that it also register with asus mobile, the fact that for your device has been unlocked...
Click to expand...
Click to collapse
That's what some manufacturers do, like Motorola and HTC. But from back when I unlocked the BL on my Zenfone 2 Laser, I remember that all it did (as far as I could tell) was unlock the bootloader and set a flag in the bootloader that made it say it was unlocked that couldn't be reversed. No need for fancy registration systems when you can just boot up the phone and take a look.
What was modified in your N-image firmware file? There is now a newer version that I'd like to install. Can you provide an updated modified file for version WW-14.2020.1703.28 or give the steps needed to modify it myself?
Jarrick said:
What was modified in your N-image firmware file? There is now a newer version that I'd like to install. Can you provide an updated modified file for version WW-14.2020.1703.28 or give the steps needed to modify it myself?
Click to expand...
Click to collapse
Updated OP with instructions regarding how to upgrade to the latest version of N - just tested steps myself. Should be applicable to all future versions of N posted on Asus site. Enjoy!
today , I unlocked the bootloader of my Real Me 2 Pro and everything was fine and after I tried to boot it back to system after flashing magisk and the decryption.zip , I got this message saying " The current boot / recovery image have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it"
I can just flash the official firmware or any ohter ROM but the PC can't seem to detect the fastboot mode and neither am I able to boot into fastboot / recovery.
can someone please help.!
vishnusai.karumuri said:
today , I unlocked the bootloader of my Real Me 2 Pro and everything was fine and after I tried to boot it back to system after flashing magisk and the decryption.zip , I got this message saying " The current boot / recovery image have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it"
I can just flash the official firmware or any ohter ROM but the PC can't seem to detect the fastboot mode and neither am I able to boot into fastboot / recovery.
can someone please help.!
Click to expand...
Click to collapse
Hi, how about your phone? is your problem have solved?
i have same problem like you. and i want to know about to solve it
thank you
hi, my problem a bit different with recovery.
i have stock recovery with unlocked bootloader. im with coloros 5.2 and can not install coloros 6 update. stock recovery cant find update file in phone storage, wifi doesnt work and starting update from os, returns update failed after one reboot. and suggestion?
vishnusai.karumuri said:
today , I unlocked the bootloader of my Real Me 2 Pro and everything was fine and after I tried to boot it back to system after flashing magisk and the decryption.zip , I got this message saying " The current boot / recovery image have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it"
I can just flash the official firmware or any ohter ROM but the PC can't seem to detect the fastboot mode and neither am I able to boot into fastboot / recovery.
can someone please help.!
Click to expand...
Click to collapse
I face the same issue. Flashed twrp. Then flashed boot+magisk+patched img file. Now the phone halts at the fastboot mode and is not booting up. It also unable to be power off. plz help. The model is Realme2 RMX 1805
Dont worry you do have a unlocked device so u need a pc to do that download system.img, vendor.img for your device and just open cmd then type this fastboot flash system system.img then fastboot flash vendor vendor.img and reboot it second method if you dont have an pc not sure that it will work you need a second device with otg support download bugjaeger app from playstore and use the same commands which i mention in pc method