Develop Bugs

assert failed: getprop("ro.build.asus.sku") == "WW" on ZE551ml

So I flashed Euphoria OS in my Zenfone 2 ZE551ML 16GB variant but now I wanna go back to stock rom. So I downloaded a full stock rom version WW-2.19.40.22. I booted into TWRP recovery, wiped data and all and then flashed the stock rom and then this assert failed get prop error appears. I can't flash the stock rom and I'm stuck with Euphoria. Any info on how I can get back to stock rom?

hello i think your devices is unlock you can use a system.img to revert back to stock if you came from custom rom
fastboot erase data
fastboot erase cache
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
then reboot if you stuck on asus logo re flash again the system.img and your done..
---
second option is flash stock recovery and boot.img and use adb sideload for flashing stock rom good luck

knoneNull said:
hello i think your devices is unlock you can use a system.img to revert back to stock if you came from custom rom
fastboot erase data
fastboot erase cache
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
then reboot if you stuck on asus logo re flash again the system.img and your done..
---
second option is flash stock recovery and boot.img and use adb sideload for flashing stock rom good luck
Click to expand...
Click to collapse
I'm unable to use the adb sideload method. My device disconnects when I activate sideload on it but it reconnects when I cancel it.

caveat13 said:
I'm unable to use the adb sideload method. My device disconnects when I activate sideload on it but it reconnects when I cancel it.
Click to expand...
Click to collapse
try to charge it first , then try again, if not work i think the best is send to service center or try to message shakalaca may be he can help you

can only go to fastboot and nothing else

i think i've ****ed up my zenfone 2.
i can only go to fastboot and i can flash boot.img , droidboot.img and recovery.img
but i can't flash system.img (it says error: cannot load 'system.img') and everytime i try to go to recovery , it just freeze on asus logo and that's it.
i can't flash asus zip file (from asus site) because the size of the file is too large and i receive error.
i was using a custom rom and decided to return to stock.
how can i fix my phone?

Your system.img is corrupted somehow, if you are using shakalaca's img just delete the current one in your folder and unzip like you did before, that worked for me after the same thing happened to me while flashing.

okay.i have some good news (for myself )
i can now get into Recovery mode.it's stock recovery with and android robot in it and saying "installing System Update"
but after a few seconds it says error and that's it.
i use "adb devices" but there's no device connected.same for "fastboot devices"
now what should i do?
p.s : i get error everytime i want to "fastboot flash system system.img" and everytime i use "fastboot -w".for flashing system it gives the "error: cannot load 'system.img'" and for -w it says "FAILED (remote: flash_cmds error! )"
edit: now i have TWRP recovery.it's the UN-Tethered one.so i don't think i can install stock rom.right?
what should i do if i want to install stock rom?
edit 2:finally.i installed a custom rom for now.everything is ok.the phone is up and running.
but now i want to return to stock rom.how?

G3 Fastboot brick, No Download mode...

I have D855 32GB, installed Lollipop D85520A on it. (official polland rom as i learned) it has rooted but no recovery. so i tried to install TWRP but my phone is stucked in Fastboot mode. Can't enter download mode , when i try fastboot screen appearing again. i can use fastboot commands and tried to remove and reflash aboot, boot ang laf.img files. there is no error all is ok but no change... When i try to list my fastboot devices it says
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
? fastboot
but in device manager page i can see recognised as Android Bootloader Interface.
Also i cannot find 32GB 20A official kdz or img files so i tried 20H istead .
So how can i fix this problem???

draqkin said:
I have D855 32GB, installed Lollipop D85520A on it. (official polland rom as i learned) it has rooted but no recovery. so i tried to install TWRP but my phone is stucked in Fastboot mode. Can't enter download mode , when i try fastboot screen appearing again. i can use fastboot commands and tried to remove and reflash aboot, boot ang laf.img files. there is no error all is ok but no change... When i try to list my fastboot devices it says
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
? fastboot
but in device manager page i can see recognised as Android Bootloader Interface.
Also i cannot find 32GB 20A official kdz or img files so i tried 20H istead .
So how can i fix this problem???
Click to expand...
Click to collapse
Now, can you use fastboot command ? Like fastboot flash recovery "withyourrecovery.img"

Now, can you use fastboot command ? Like fastboot flash recovery "withyourrecovery.img"
Click to expand...
Click to collapse
Yes i can use fastboot commands also tried to write recover, laf, aboot img files. I dont have original img files of 20A but tried with 20H recovery and custom recovery img (TWRP) but no change. There was no problem or error while writing images with fastboot commands...

i have the same problem
it also says
? fastboot
still couldn't find a solution
please let me know if u find a solution

ghadeer.m96 said:
i have the same problem
it also says
? fastboot
still couldn't find a solution
please let me know if u find a solution
Click to expand...
Click to collapse
Can you erase recovery ? or not ? ( with command : fastboot erase recovery )
I can't erase recovery because i have this error ( remote failed to erase partition )

th0was said:
Can you erase recovery ? or not ? ( with command : fastboot erase recovery )
I can't erase recovery because i have this error ( remote failed to erase partition )
Click to expand...
Click to collapse
i can't do any command successfully
like when i do a flash command
it finishes sending successfully but then it gets stuck at writing ...
and it never finishes writing
---------- Post added at 07:11 PM ---------- Previous post was at 06:51 PM ----------
draqkin said:
I have D855 32GB, installed Lollipop D85520A on it. (official polland rom as i learned) it has rooted but no recovery. so i tried to install TWRP but my phone is stucked in Fastboot mode. Can't enter download mode , when i try fastboot screen appearing again. i can use fastboot commands and tried to remove and reflash aboot, boot ang laf.img files. there is no error all is ok but no change... When i try to list my fastboot devices it says
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
? fastboot
but in device manager page i can see recognised as Android Bootloader Interface.
Also i cannot find 32GB 20A official kdz or img files so i tried 20H istead .
So how can i fix this problem???
Click to expand...
Click to collapse
btw do u have an unlocked bootloader ?
mine is locked
i think this is why we're facing this problem .. cuz of locked bootloader

Can you erase recovery ? or not ? ( with command : fastboot erase recovery )
Click to expand...
Click to collapse
Yes i can erase and rewrite recovery and others with no error.
btw do u have an unlocked bootloader ?
mine is locked
i think this is why we're facing this problem .. cuz of locked bootloader
Click to expand...
Click to collapse
I don't know about my bootloader because i have bought my phone from someone else. It was rooted, used 3 days and tried to install twrp than *kaboom*. Stuck fastboot....

Flashing to stock Android NPD90G from TWRP error: "remote: unsupported command"

Flashing to stock Android NPD90G from TWRP error: "remote: unsupported command"
Fixed flashing error "remote: unsupported command" when flashing a Pixel C back to stock
I used TWRP and SuperSU to root and modify the buildprops to enable and get an early look at the windowing in Android N beta on my Pixel C release 5 ahead of time.
When Release 5 NPD90G was available I decided to flash back to stock from Developer Preview 4 NPD56N rooted with SuperSU and flashed with TWRP. I like root - I run Ubuntu and Win 7. I don't mind running a rooted device if it doesn't have all my work and financial data. When the final N release is out, the Pixel C will become my work machine. It's almost there.
I'm naturally paranoid. I change my long passwords frequently and use 2 factor authentication for everything. So if I can, I'll take a stock release. See my instructions for wiping Android devices: How to wipe an Android Phone: the paranoid editon
I could not flash the NPD90G stock bootloader because of an error "remote: unsupported command"
Here's how I fixed it.
Updated the SDK manager including SDK Tools and USB drivers.
With the Pixel C in recovery mode, {hold the power key and volume down}
In TWRP mount System and reboot to recovery
>ADB Shell.
From ADB Shell I ran
>fwtool vbnv write dev_boot_fastboot_full_cap 1 to reenable Fast boot.
Then I changed from TWRP to Fastboot mode {power button plus hold the volume up button}
>fastboot erase userdata
>fastboot erase boot
>fastboot erase cache
>fastboot erase recovery
>fastboot erase system
See Note 1. Below
>fastboot flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
>fastboot reboot-bootloader
>fastboot flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
>fastboot reboot-bootloader
Note 1.
The first time through I flashed the following line items which resulted in the resting robot Andi. I don't think I needed to do this, but if the above instructions don't work, run the following before continuing for {flash bootloader bootloader-dragon-google_smaug.7900.27.0.img}
>flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
>fastboot reboot-bootloader
>fastboot reboot-bootloader
>fastboot flash system system.img
>fastboot flash boot boot.img
>fastboot flash recovery recovery.img
>fastboot flash cache cache.img

Twrp can't flash
The problem is that I can't boot into the twrp because when i try to flash it the answer is failed unsupported remote command

Tugio said:
The problem is that I can't boot into the twrp because when i try to flash it the answer is failed unsupported remote command
Click to expand...
Click to collapse
When in fastboot mode, use:
Code:
fastboot boot twrp-local-file-on-computer.img

DanBUK said:
When in fastboot mode, use:
Click to expand...
Click to collapse
It's nice of you to help a fellow XDA user. But I suspect he's already solved his problem of three months ago.....

Hi guys
I have the same problem:
- the bootloader is unlocked (Coreboot menu says so)
- fastboot says "secure: yes" but "unlocked: yes" too
- "fastboot flashing get_unlock_ability" returns "1"
- "fastboot flashing unlock" says that the bootloader is already unlocked
But I have no recovery and if I try to fastboot boot recovery.img it fails with signature verification error
Can I do something to unbrick the device?
Regards

lllopa said:
Hi guys
I have the same problem:
- the bootloader is unlocked (Coreboot menu says so)
- fastboot says "secure: yes" but "unlocked: yes" too
- "fastboot flashing get_unlock_ability" returns "1"
- "fastboot flashing unlock" says that the bootloader is already unlocked
But I have no recovery and if I try to fastboot boot recovery.img it fails with signature verification error
Can I do something to unbrick the device?
Regards
Click to expand...
Click to collapse
My solution is very simple:
fastboot flashing lock
fastboot flashing unlock
fastboot reboot
And now let it boot.... and wait.
After the (failed) reboot check again: Now you can write all partitions... worked with my Pixel C

Make sure you have the latest version of fastboot and adb. I get these errors almost every month if I don't update.
https://developer.android.com/studio/releases/platform-tools.html

@stevep2007, thank you so much! I've been dealing with this "remote: unsupported command" nonsense for days now after trying to revert back to an older Oreo version of Lineage. This did the trick!

How can I solve the problem when my Pixel C is not unlocked? My Pixel made an update and after installing the Update I got the green little man. Now I have no Chance to activate USB debugging etc. Its also not possible to install twrp.img
How can I go to ADB shell with locked bootloader? Or isn't it possible?
Fastboot devices shows me my tablet. ADB devices also show my tablet with "sideload".
But every try to flash my Pixel fails. I alway get the message .... remote: unknown command.......fastboot error: command failed
flash-all.bat showes that all "*.img are missing" error: command failed... unknown command etc.......
So any idea to get my Pixel working again? ADB shell would make it I think. But how with locked bootloader.

_Arne_ said:
My solution is very simple:
fastboot flashing lock
fastboot flashing unlock
fastboot reboot
And now let it boot.... and wait.
After the (failed) reboot check again: Now you can write all partitions... worked with my Pixel C
Click to expand...
Click to collapse
This did it for me!! Thanks much. I also updated platform-tools at the same time, who knows which did it

_Arne_ said:
My solution is very simple:
fastboot flashing lock
fastboot flashing unlock
fastboot reboot
And now let it boot.... and wait.
After the (failed) reboot check again: Now you can write all partitions... worked with my Pixel C
Click to expand...
Click to collapse
In the scenario described by @llopa this solution does not work.
In that scenario there are no solutions

bernardomarx said:
In the scenario described by @llopa this solution does not work.
In that scenario there are no solutions
Click to expand...
Click to collapse
Sorry replied incorrectly

No bootloader , no recovery!

So,recently i switched from cm14.1 back to cm13 and when i did that, i forgot to downgrade the bootloader,so after i flashed the rom I went to the bootloader and made the downgrade,Successfully booted into cm13,but when i tried going to recovery to flash xposed,i found out there's bootloop ( stuck on asus logo ) ! Everytime i try to boot into bootloader or recovery! nothing works!

Saumitraa said:
So,recently i switched from cm14.1 back to cm13 and when i did that, i forgot to downgrade the bootloader,so after i flashed the rom I went to the bootloader and made the downgrade,Successfully booted into cm13,but when i tried going to recovery to flash xposed,i found out there's bootloop ( stuck on asus logo ) ! Everytime i try to boot into bootloader or recovery! nothing works!
Click to expand...
Click to collapse
if no boot loader you have to use unbrick threads.
If you had a flashed back a stock recovery and boot.img if on rooted mm bl with giovix modder tool , you could've downgraded via sd card and stock recovery ..in my link below
There were 2 different cm 13s , one with mm bl and one based on 5.
.

Unbricked
So i unbricked the phone! Everything was success! xfstk worked then i got the 4 color screen and after that the bootloader!
Extracted the .raw file and then flashed using commands, but when the phone tries to reboot, it gets stuck on the ASUS logo! waited half an hour for that! Service center people say that its a motherboard problem! Any advice ?

Saumitraa said:
So i unbricked the phone! Everything was success! xfstk worked then i got the 4 color screen and after that the bootloader!
Extracted the .raw file and then flashed using commands, but when the phone tries to reboot, it gets stuck on the ASUS logo! waited half an hour for that! Service center people say that its a motherboard problem! Any advice ?
Click to expand...
Click to collapse
did you get any error in any command. if you got bootloader it must work
flash xfstk again and and run these commands after extracting raw.. tell me if any of the command fails or give error
1. fastboot devices ( see if it is recognized: else plug out usb and plugin again)
2. fastboot oem erase_osip_header
3. fastboot oem start_partitioning
4. fastboot flash /tmp/partition.tbl partition.tbl
5. fastboot oem partition /tmp/partition.tbl
6. fastboot erase system
7. fastboot erase cache
8. fastboot erase data
9. fastboot erase APD
10. fastboot erase ADF
11. fastboot oem wipe splashscreen
12. fastboot oem stop_partitioning
13. fastboot flash splashscreen splash_sign.bin
14. fastboot flash token MFG_BOM_Full.bin
15. fastboot flash ifwi ifwi-prod.bin
16. fastboot flash boot boot_sign.bin
17. fastboot flash recovery recovery_sign.bin
18. fastboot flash fastboot droidboot_sign.bin
19. fastboot flash APD APD.img
20. fastboot flash system system.img
21. fastboot reboot

No errors
I flashed everything again, no errors whatsoever! The phone just wont boot! Stuck on Asus logo for an hour , then switched off the phone

Saumitraa said:
I flashed everything again, no errors whatsoever! The phone just wont boot! Stuck on Asus logo for an hour , then switched off the phone
Click to expand...
Click to collapse
Which build number raw file you use ?

Saumitraa said:
I flashed everything again, no errors whatsoever! The phone just wont boot! Stuck on Asus logo for an hour , then switched off the phone
Click to expand...
Click to collapse
send me log of cmd when you run commands

timbernot said:
Which build number raw file you use ?
Click to expand...
Click to collapse
This one : WW_ZE551ML_2.20.40.194_20160713