Related
Hello!
I have a big problem in my zenfone 5 , I hope someone can help me.
Next , after the last update sent by ASUS My zenfone is simply paralyzed the logo of the manufacturer.
First tried to clear data and cache the recovery without success ... The only option I have left then was to make an update by the ADB . Okay so let's do this, using the ADB 1.0.32 ( I downloaded here on XDA ) I tried to perform the update with several different firmware , but when you get 55% have to return the message " COMMAND NOT FOUND " and the cell appears the logo of broken android
Please help me, how can I fix this. :crying:
amartinss said:
Hello!
I have a big problem in my zenfone 5 , I hope someone can help me.
Next , after the last update sent by ASUS My zenfone is simply paralyzed the logo of the manufacturer.
First tried to clear data and cache the recovery without success ... The only option I have left then was to make an update by the ADB . Okay so let's do this, using the ADB 1.0.32 ( I downloaded here on XDA ) I tried to perform the update with several different firmware , but when you get 55% have to return the message " COMMAND NOT FOUND " and the cell appears the logo of broken android
Please help me, how can I fix this. :crying:
Click to expand...
Click to collapse
Can u upload screen shot of command not found because I m really didn't get u r prblm...one tip go to stock Rom or downgrad to kitkat....
yasin0005 said:
Can u upload screen shot of command not found because I m really didn't get u r prblm...one tip go to stock Rom or downgrad to kitkat....
Click to expand...
Click to collapse
Hi yasin0005
I tried to downgrade to kitkat , but still shows the same message ... I'll post a picture of the device with the messages later ... is that I don't can do it now
See u soon
amartinss said:
Hi yasin0005
I tried to downgrade to kitkat , but still shows the same message ... I'll post a picture of the device with the messages later ... is that I don't can do it now
See u soon
Click to expand...
Click to collapse
Ok...take u r time
yasin0005 said:
Ok...take u r time
Click to expand...
Click to collapse
I can not upload files yet .. I am new to XDA have less than 10 places .. sorry but I can not post the image of the error message. But this is the message that appears on the device ...
Error picture this link amartinss.com.br/sing/IMG_20160101_123536.jpg
OR described below
"Now send the package you want to apply to the device with 'adb sideload <fillenme>'...
Finding update package...
Opening update package...
Verifying update package...
Installing update package...
assert failed: !less_than_int(28686307, getprop("ro.build.date.utc")) || greate_than_int(getprop("ro.build.date.utc"), 1392739200)
return code 8E: Error in /sideload/package.zip
(Status 8)
Installation aborted."
This happens when I try to downgrade the sideload...
To fix your issue, you need to:
1) Update your Recovery to the Latest STOCK version
2) Reinstall your ROM downloading full firmware from ASUS site
The issue is that your ROM/Recovery is not up-to-date to run the update package.
same problem! any solution? can't access fastboot for command "fastboot flash recovery file.img", just adb sideload, but gone wrong in 54%.
patrick.bitencourts said:
same problem! any solution? can't access fastboot for command "fastboot flash recovery file.img", just adb sideload, but gone wrong in 54%.
Click to expand...
Click to collapse
have you found a solution to your problem ???
I am also facing same issue while updating with adb sideload..
if you have got a solution please post it..
Have you tried to acces fastboot with the adb command: adb reboot fastboot ?
Then you could try again to flash your updated recovery.
There is a CWM modified recovery you should try.
Hello all,
I really need help for my ZE500KL. In summary, it stucks on ASUS logo and bootloop. I can't get to welcome screen.
It is not rooted, i've never touched to the original system. I got this problem after an update from OTA. The update was not interrupted for information.
I can get to the recovery menu, can do a wipe data/factory reset, but it solves nothing. Same problem.
I've tried :
- apply update from adb but this stops at 46% and failed with an error like E:failed to verify the whole-file signature
- apply update from microSD but it stops and failed without error message
I don't know if there is another way to fix.
Thanks
Bro go to the asus site and download the whole rom nd flash it thru recovery.
M also had a same problem.
So let me know nd which variant u hav?
Thanks for the reply.
When i said "I have apply update", this means that i've downloaded zip file from Asus website, and loaded it via the recovery but the process stops at 46%.
Maybe it will work for a custom recovery like CWM or TWRP but as i know, there is not a working CWM or TWRP for ZE500KL at this time. Maybe.
For me, the stock recovery don't work for loading the zip file from ASUS. It says something like : Unable to verify the whole-file signature, Process failed
Fus_XDA said:
Thanks for the reply.
When i said "I have apply update", this means that i've downloaded zip file from Asus website, and loaded it via the recovery but the process stops at 46%.
Maybe it will work for a custom recovery like CWM or TWRP but as i know, there is not a working CWM or TWRP for ZE500KL at this time. Maybe.
For me, the stock recovery don't work for loading the zip file from ASUS. It says something like : Unable to verify the whole-file signature, Process failed
Click to expand...
Click to collapse
If your device stops at logo this means that it boots into fastboot mode. I`ve had a same problem. You can take this adb driver . After installing you need to put in C:\adb file boot.img from archive which you dowloaded from official asus.com, then run cmd.
Code:
cd c:\adb
and last command will be...
Code:
fastboot boot boot.img
try it.
kvantor said:
If your device stops at logo this means that it boots into fastboot mode. I`ve had a same problem. You can take this adb driver . After installing you need to put in C:\adb file boot.img from archive which you dowloaded from official asus.com, then run cmd.
Code:
cd c:\adb
and last command will be...
Code:
fastboot boot boot.img
try it.
Click to expand...
Click to collapse
I tried. It doesn't work.
I proceed like this :
1- I've booted the device in recovery mode, connect it to PC and uninstall the device and his driver in to the device manager. I do the same in fastboot mode
2- I've installed the 15 seconds adb ver 1.43. As it is recommanded, I force install of drivers to "Android ADB interface" for recovery mode and "Android Bootloader Interface" for fastboot mode. At this time, adb detects the device via "c:\adb> adb devices"
3-I've extracted the "boot.img" from UL-ASUS Z00E-WW-12 8 5 106-user.zip from Asus Website
4-No problem to proceed with "c:\adb> fastboot boot boot.img" BUT that's all.
--> The device boots, passes the ASUS logo with the powered by android at the bottom", arrives to the second ASUS logo (the one animated), then there are messages "Android upgrading, optimising 1 of 1 app", "Starting apps", then it reboots, and bootloops .... again and again. I have to take out the battery to turn it off.
Have you tried downloading the full ROM image from the ASUS support website again? (yes, download again and try flashing your device again). Usually when it says something about signature verification failed, it is due to the incomplete download of the ROM image (corrupted), or that it has been modified.
Do report back the results.
Download Link (for your convenience): http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE500KL/UL-ASUS_Z00E-WW-12.8.5.222-user.zip
Download Link (for your convenience): http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE500KL/UL-ASUS_Z00E-WW-12.8.5.222-user.zip
Click to expand...
Click to collapse
I's been thinking to this ...
I've downloaded 3 times the ROM from asus website. The download procees has been interrupted because of internet problem but i was able to resume after. I've even downloaded previous version. I am able to extract the zip file to my computer without error like cooupted file or CRC..
I need to know if other persons have the same problem exactly with this ZE500KL because, i have recently done the same thing with my ZE551ML and i had no problem.
Have you tried flashing the previous updates (software versions) instead? Could be a "bogus" update.
Rizzed said:
Have you tried flashing the previous updates (software versions) instead? Could be a "bogus" update.
Click to expand...
Click to collapse
Yes. Same problem with .172
I was been delighted when i see this TWRP for ZE500KL http://forum.xda-developers.com/zenfone-2-laser/development/recovery-twrp-3-0-0-0-recovery-t3319704 and it works,
But my joy was so short.
It says that it was unable to install the ZIP file because the ZIP is for WW_PHONE, and my phone is an OMNI_ZE500KL !!! What is this ? Never heard about it before. What's weird with this AUS ZIP file !!!??
Can you try to ADB Sideload the ASUS ROM?
sagematt said:
Can you try to ADB Sideload the ASUS ROM?
Click to expand...
Click to collapse
Yes. I've tried every way to install.
Fusxda said:
Yes. I've tried every way to install.
Click to expand...
Click to collapse
Open a thread on ZenTalk: http://www.asus.com/zentalk/
Never heard about this OMNI SKU before.
If someone else has the same exact phone with you with a different SKU (perhaps WW?), you could try asking him to backup the recovery.img on his phone for you to flash. After that, just flash recovery via fastboot and you should be good to go.
up
Rizzed said:
If someone else has the same exact phone with you with a different SKU (perhaps WW?), you could try asking him to backup the recovery.img on his phone for you to flash. After that, just flash recovery via fastboot and you should be good to go.
Click to expand...
Click to collapse
Hello , do you find the solution i have the same problem
could you help me , thanx a lot :good:
2xboy said:
Hello , do you find the solution i have the same problem
could you help me , thanx a lot :good:
Click to expand...
Click to collapse
Stock recovery (and TWRP):
https://github.com/sabpprook/android_device_asus_ze500kl/releases
Guys I Found The Solution For This Problem :
1-Flash TWRP Recovery From The Link : https://github.com/sabpprook/android_device_asus_ze500kl/releases
2- Wipe Data and Cache And dalvik Cache and Very Important (Wipe System).
3-Flash Back The Stock recovery From The Same Link Above.
4-Flash Your .zip Stock Frimware From The Link : https://www.asus.com/support/Download/39/1/0/20/KsY29RCpsJ2bea9O/32/
5-Please if this Helped You Press Thanks! Button And Enjoy.
The Trick: Stock Recovery Cannot Wipe System But TWRP Can.
P.S: You Cannot Flash The Frimware From TWRP ... It Will Give An Error.
Enjoy
I find answer
Bro, download this file failobmennik.usite.pro/updater-script.noext and change \META-INF\com\google\android\updater-script
Hi,
I'll test it, and will give feed-back
Thanks
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.
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!
Its a 64 gb A1 variant. Everything was stock. It was on stock pie (update via OTA). I never tried unlocking bootloader as well as flashing custom rom.
3 day ago when i using it,suddenly it turn off and stuck at android one logo. I can go fastboot mode by pressing power+volume down.
I try to flash stock rom using mi flash tool,but as my bootloader is locked it show error. :crying:
Please help me out,it is my daily driver. :crying:
Use the fastboot oem unlock command and see what it does.
If the command is succesfully will trigger the factory reset of devices, but maybe you`ll get it to work.\
If the above command not working, maybe you can try to factory reset from recovery if you can boot into it.
In the end maybe a fastboot flash will do the trick.
punktnet said:
Use the fastboot oem unlock command and see what it does.
If the command is succesfully will trigger the factory reset of devices, but maybe you`ll get it to work.\
If the above command not working, maybe you can try to factory reset from recovery if you can boot into it.
In the end maybe a fastboot flash will do the trick.
Click to expand...
Click to collapse
I found this thread after i post this. Hope this will help me, though i am not try yet. I will update what happen. https://forum.xda-developers.com/showpost.php?p=78378088&postcount=43
use miunlock tool to unlock bootloader if you're not familiar with fastboot commands and as punktnet said unlocking bootloader will reset your device and erase your userdata and internal storage then maybe your device works fine if not then reboot it again in fastboot mode and flash stock firmware.
Facing similar issue. Am able to flash via test point method however still stuck when device is rebooted with this message;
Supported API: 3
E: Failed to clear BCB message: failed to FSync/dev/block/bootdevice/by-name/miscperation not permitted.
Any other solution?
WORKMEISTER said:
Facing similar issue. Am able to flash via test point method however still stuck when device is rebooted with this message;
Supported API: 3
E: Failed to clear BCB message: failed to FSync/dev/block/bootdevice/by-name/miscperation not permitted.
Any other solution?
Click to expand...
Click to collapse
This occurred to me today aswell :c I tried wiping all the data from recovery but the phone couldn't even end to wipe all. My phone went into a "erasing" screen for almost 1 hour when I decided trying to hold the power button, it rebooted but I still got into the bootloop :l my Xiaomi Mi A1 is not unlocked for bootloader so I can't flash it. I also tried with the mi unlocking but didn't go past 50% when it launched an error. Guess I'll die.