Database Info

[Q] [Urgent Help] - Almost bricked

Please help.:crying:
I did the below fastboot commands
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot reboot-bootloader
All gave me success.
But I am not able to do any of the below commands
fastboot flash bootloader bootloader-crespo-i9020xxlc2.img
fastboot flash radio radio-crespo-i9020xxki1.img
fastboot flash recovery recovery-clockwork-touch-6.0.3.1-crespo.img
fastboot -w update image-soju-jzo54k.zip
all i get is "error: cannot load 'bootloader-crespo-i9020xxkl1.img': Unknown error"
Wheareas in the mobile, i get an error:
FASTBOOT STATUS - FAILInvalid Argument

Try to use correct radio
Sent from my Nexus S using xda premium

Zenfone 3 Fastboot commands found on Nougat Bootloader

I was stuck at fastboot, so I decided to look out for extra fastboot commands, after I was done, I didn't needed it at all, but after I saw a command to reset dm verity (only possible via re-flashing stock rom before) I decided to share with the community
Be aware that I didn't tested any command
It'd be good if you say me wich works or not
Fastboot:
Code:
fastboot reboot bootloader
fastboot reboot recovery
fastboot reboot-bootloader
fastboot oem unlock
fastboot oem unlock-go
fastboot oem lock
fastboot flashing unlock
fastboot flashing lock
fastboot flashing lock_critical
fastboot flashing unlock_critical
fastboot flashing get_unlock_ability
fastboot oem device-info preflash
fastboot oem enable-charger-screen
fastboot oem disable-charger-screen
fastboot oem off-mode-charge
fastboot oem select-display-panel
fastboot oem gpt-info
fastboot oem force-hwid_
fastboot oem update-cmdline_
fastboot oem get-splash
fastboot oem show-barcode
fastboot oem unTAR_
fastboot oem dump-pmic-reg_
fastboot oem write-pmic-reg_
fastboot oem get-gpio_
fastboot oem check-fuse
fastboot oem set-fuse
fastboot oem reset-dev_info
fastboot oem adb_enable
fastboot oem shutdown
fastboot oem auth-hash
fastboot oem gen-random
fastboot oem EnterShippingMode
fastboot oem reboot-recovery
fastboot oem check-bat
fastboot oem set-batvol_
fastboot oem get-batvol
fastboot oem get-batcap
fastboot oem mbr-info
fastboot oem reset-mbr-info
fastboot oem read_emmc_blk_
fastboot oem check-DDR
fastboot oem check-ftm
fastboot oem enable-ftm
fastboot oem enable-userdebug
fastboot oem ffu_unlock
fastboot oem emmc_info
fastboot oem ffu_auto
fastboot oem reset_ffu
fastboot oem check-qcn-golden-copy
fastboot oem reset-boot_count
fastboot oem dump-log
fastboot oem system-info
fastboot oem get_build_version
fastboot oem partition-test
fastboot oem crc32-size_
fastboot oem crc32-len_
fastboot oem crc32_
fastboot oem hash_
fastboot oem crc32_debug
fastboot oem crc_test
fastboot oem reset-repartition
fastboot oem reset-dm-verity
some adb commands:
Code:
adb reboot oem-88 (shutdown)
adb reboot oem-68 (factoey_reset_text)
adb reboot oem-69 (factoey_reset)
adb reboot oem-23 (fastboot)
adb reboot oem-78 (recovery_gpt)
adb reboot oem-63 (untar)
adb reboot oem-66 (adb_enable)
adb reboot oem-52 (selinux_permissive)
adb reboot oem-08 (user_unlock)
adb reboot oem-99 (verify_data_size)
adb reboot oem-43 (shipping_mode)
adb reboot oem-11 (ota_set_dm_verity)
adb reboot oem-12 (ota_set_dm_verity_r) [BL]
thoose adb comments are from the code, I'm not the one that wrote them.

Tested:
fastboot oem dump-log
shows some bootloader level logs from recent boots
fastboot oem system-info
Code:
(bootloader) board_info: msm8953
(bootloader) mem_info:
(bootloader) mmc_info:
(bootloader) product_name: ASUS_Z017D_1
(bootloader) product_locale: en-US
(bootloader) product_carrier: US-ASUS_Z017D-WW_Phone
(bootloader) csc_build_version: WW_ZE520KL-14.2020.1703.28-20170410
(bootloader) bt_mac:
(bootloader) wifi_mac:
(bootloader) imei: XXXXXXXXXX
(bootloader) imei2: XXXXXXXXXXX
(bootloader) ssn: XXXXXXXX
(bootloader) isn:
(bootloader) color:
(bootloader) country:
(bootloader) customer:
(bootloader) revenuecountry:
(lol, really lost some **** flashing my phone)
fastboot oem get_build_version
gets the last installed stock rom version, even if you're running custom roms
fastboot oem get-batcap
returns battery capacity
fastboot oem get-batvol
returns battery voltage and capacity

adb and fastboot help needed

I'm on Linux Mint 18.3 and my G620S-L01 phone is on Android 4.4.4
I have downloaded minimal adb and fastboot tool.
First question, when issueing "adb devices" and "fastboot devices" command, shouldn't I get the same output? ( which is from what I understand the device serial number ). This is what I get:
Code:
./adb devices
List of devices attached
84dbac441b79 device
./adb reboot-bootloader
./fastboot devices
no permissions (user in plugdev group; are your udev rules wrong?); see [developer.android.com/tools/device.html] fastboot
sudo ./fastboot devices
3a226eb fastboot
Then when I issue any oem commands I tried, I always get "FAILED (remote: 'unknown command')" like for example:
Code:
sudo ./fastboot oem device-info
FAILED (remote: 'Invalid command')
fastboot: error: Command failed
I have read in some other thread, that to make oem commands working "OEM unlock" needs to be set up in Developer options. But from what I understand, this option is for >= Android 5.something. How to make those commands working on 4.4.4 version?
Edit:
I have then downloaded and installed full-blown Android studio. But the result is the same.

Question ROG5 Fastboot commands

fastboot flashing get_unlock_ability
fastbootflashing unlock
fastboot flashing lock
fastboot flashing unlock_critical
fastboot flashing lock_critical
fastboot oem enable-charger-screen
fastboot oem disable-charger-screen
fastboot oem off-mode-charge
fastboot oem select-display-panel
fastboot oem device-info
fastboot reboot-fastboot
fastboot reboot-bootloader
fastboot oem gpt-info
fastboot oem adb_enable
fastboot oem shutdown
fastboot oem get-dtid
fastboot oem get-hwid
fastboot oem get-prjid
fastboot oem get-skuid
fastboot oem get-rfid
fastboot oem get-featureid
fastboot oem get-jtagid
fastboot oem get-bcid
fastboot oem get-secdispid
fastboot oem get-cpuidhash
fastboot oem get-toolid
fastboot oem isn-info
fastboot oem ssn-info
fastboot oem system-info
fastboot oem get_build_version
fastboot oem get-batcap
fastboot oem get-batvol
fastboot oem get-bootcount
fastboot oem factory-reset
fastboot oem factory-reset2
fastboot oem reboot-recovery
fastboot oem set-permissive
fastboot oem enter-dload
fastboot oem check-s3
fastboot oem EnterShippingMode
fastboot oem check-nrfuse
fastboot oem check-fuse
fastboot oem fuse-info
fastboot oem show-barcode
fastboot oem checksetupwizard
fastboot oem asus-csc_lk
fastboot oem rsa_test_
fastboot oem crc32_
fastboot oem hash_
fastboot oem gen-random
fastboot oem auth-hash
fastboot oem auth-hash_2
fastboot oem auth-hash_3
fastboot oem get-imeiauth
fastboot oem slot_b_enable
fastboot oem get-verify_vbmeta_ret
fastboot oem update-cmdline_
fastboot oem backup-fac
fastboot oem restore-fac
fastboot oem get-pmic-reg_
fastboot oem write-pmic-reg_
fastboot oem reset-boot_count
fastboot oem reset-lock_count
fastboot oem reset-a_retry_count
fastboot oem reset-a_unbootable_count
fastboot oem reset-b_retry_count
fastboot oem reset-b_unbootable_count
fastboot oem force-hwid_
fastboot oem reset-dev_info
fastboot oem reset-auth2
fastboot oem reset-auth3
fastboot oem disable-verity
fastboot oem enable-verity
fastboot oem enable-vbmeta
fastboot oem read-vbmeta
fastboot oem read-rollback
fastboot oem reset-rollback

hi, which one i can use to unlock my bootloader?
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Device authorized: false
(bootloader) Device authorized2: false
(bootloader) WaterMask unlock: N
(bootloader) XBL: Post-CS3-30-ZS673KS-user
(bootloader) ABL: Post-CS3-25-WW-user
(bootloader) CID: ASUS
(bootloader) COUNTRY: WW
(bootloader) Project: ZS673KS
(bootloader) DT ID: 100
(bootloader) SB: Y
(bootloader) SBNR: Y
(bootloader) DDR Manufacturer ID: 1
(bootloader) DDR Device Type: 8
(bootloader) TotalDMCounter: 0
(bootloader) DMCounter: 0
(bootloader) SlotARetryCounter: 0
(bootloader) SlotAUnbootableCounter: 0
(bootloader) SlotBRetryCounter: 0
(bootloader) SlotBUnbootableCounter: 0
(bootloader) BOOT_COUNT: 32
(bootloader) LOCK_COUNT: 1
(bootloader) Check_APDP: 0
(bootloader) rawdump_en: false
(bootloader) Current Slot: b
(bootloader) Slot_b bootable: Bootable
(bootloader) AVB Verity: Enable
(bootloader) Verify vbmeta ret: 0
(bootloader) ABL_FTM: FALSE
(bootloader) SNAPSHOT-UPDATE-STATUS: none
OKAY [ 0.080s]
finished. total time: 0.080s

Following the answer.

fastboot oem device-info does not work for me
Code:
> fastboot oem device-info
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
And i get the same result for any fastboot oem command, even when i type random things
Almost every "generic" commands such as fastboot flashing get_unlock_ability does not work either, giving me a different message
Code:
> fastboot flashing get_unlock_ability
FAILED (remote: 'Unrecognized command flashing get_unlock_ability')
fastboot: error: Command failed
The only commands that worked so far are fastboot reboot-fastboot and fastboot reboot-bootlader
Code:
> fastboot reboot-fastboot
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
Finished. Total time: 8.642s
I have a WW device ( i think its a new one ), and i never unlocked the bootloader before, so am i missing something here ??
I really want to check those values to confirm that the device hasnt been unlocked and a few other things.

zvrsd said:
fastboot oem device-info does not work for me
Code:
> fastboot oem device-info
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
And i get the same result for any fastboot oem command, even when i type random things
Almost every "generic" commands such as fastboot flashing get_unlock_ability does not work either, giving me a different message
Code:
> fastboot flashing get_unlock_ability
FAILED (remote: 'Unrecognized command flashing get_unlock_ability')
fastboot: error: Command failed
The only commands that worked so far are fastboot reboot-fastboot and fastboot reboot-bootlader
Code:
> fastboot reboot-fastboot
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
Finished. Total time: 8.642s
I have a WW device ( i think its a new one ), and i never unlocked the bootloader before, so am i missing something here ??
I really want to check those values to confirm that the device hasnt been unlocked and a few other things.
Click to expand...
Click to collapse
Your phone is tencent edition or not?

HunterTik said:
Your phone is tencent edition or not?
Click to expand...
Click to collapse
No, its the ROG edition

zvrsd said:
No, its the ROG edition
Click to expand...
Click to collapse
Then use official unlock mathod hope it works for you.

zvrsd said:
fastboot oem device-info does not work for me
Code:
> fastboot oem device-info
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
And i get the same result for any fastboot oem command, even when i type random things
Almost every "generic" commands such as fastboot flashing get_unlock_ability does not work either, giving me a different message
Code:
> fastboot flashing get_unlock_ability
FAILED (remote: 'Unrecognized command flashing get_unlock_ability')
fastboot: error: Command failed
The only commands that worked so far are fastboot reboot-fastboot and fastboot reboot-bootlader
Code:
> fastboot reboot-fastboot
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
Finished. Total time: 8.642s
I have a WW device ( i think its a new one ), and i never unlocked the bootloader before, so am i missing something here ??
I really want to check those values to confirm that the device hasnt been unlocked and a few other things.
Click to expand...
Click to collapse
Did this work for you? I have the exact same problem even after using the official bootloader unlock..

zvrsd said:
fastboot oem device-info does not work for me
Code:
> fastboot oem device-info
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
And i get the same result for any fastboot oem command, even when i type random things
Click to expand...
Click to collapse
You're in userspace fastboot. Reboot to the bootloader
The one you get to by using volume up and power is bootloader
From bootloader `fastboot reboot fastboot` -> userspace fastboot
From userspace fastboot, select reboot bootloader -> bootloader
`adb reboot fastboot` -> userspace fastboot
`adb reboot bootloader` -> bootloader
The bootloader also needs to be unlocked for most commands to work.

Andrologic said:
Did this work for you? I have the exact same problem even after using the official bootloader unlock..
Click to expand...
Click to collapse
You might want to check this https://forum.xda-developers.com/t/rog5-fastboot-commands.4255537/post-85135791
After following his instructions, i was able to make the commands work.
Big thanks to him !!

zvrsd said:
You might want to check this https://forum.xda-developers.com/t/rog5-fastboot-commands.4255537/post-85135791
After following his instructions, i was able to make the commands work.
Big thanks to him !!
Click to expand...
Click to collapse
Thanks. Found it - going to try..

General Parsed LK.img

i decided to parse the lk img from the android 9 stock rom so heres the output
Code:
[?] Image size (from header): 847276 bytes
[?] Image name (from header): lk
[?] LK version: N/A
[?] Command Line: N/A
[?] Platform: MT6761
[?] Product: hardware.sku
[?] Needs unlock code: False
[?] Uses verified boot: True
[?] Factory reset protection (FRP): True
[?] FOTA support: False
[?] Available OEM commands: ['fastboot oem p2u', 'fastboot oem off-mode-charge', 'fastboot oem key', 'fastboot oem lks', 'fastboot oem scp_status', 'fastboot oem scp_log_thru_ap_uart', 'fastboot oem usb2jtag', 'fastboot oem ultraflash', 'fastboot oem ultraflash_en', 'fastboot oem secureBoot', 'fastboot oem battery', 'fastboot oem getversions', 'fastboot oem alive', 'fastboot oem getprojectcode', 'fastboot oem getUID', 'fastboot oem auth_timecount', 'fastboot oem auth_start', 'fastboot oem permission', 'fastboot oem getpermissions', 'fastboot oem getsecurityversion', 'fastboot oem md5', 'fastboot oem repair', 'fastboot oem simunlock', 'fastboot oem simlock', 'fastboot oem simlock_status', 'fastboot oem getdllname', 'fastboot oem unlock']
[?] LK ATAGs: ['atag,videolfb-fb_base_h', 'atag,videolfb-fb_base_l', 'atag,videolfb-vramSize', 'atag,boot', 'atag,imix_r', 'atag,fg_swocv_v', 'atag,fg_swocv_i', 'atag,shutdown_time', 'atag,boot_voltage', 'atag,two_sec_reboot', 'atag,mem', 'atag,vcore_dvfs', 'atag,dfo', 'atag,meta', 'atag,devinfo', 'atag,videolfb', 'atag,mdinfo', 'atag,ptp', 'atag,masp']
now one thing im confused about: fastboot oem key
i had researched this and it helped unlock the bootloader of the Nokia 3
they did it by
fastboot oem key <MD5 Hash Of Your Device Serial>
fastboot flashing unlock
i would try and test this but it dont have the phone on me rn

areallydumbperson said:
i decided to parse the lk img from the android 9 stock rom so heres the output
Code:
[?] Image size (from header): 847276 bytes
[?] Image name (from header): lk
[?] LK version: N/A
[?] Command Line: N/A
[?] Platform: MT6761
[?] Product: hardware.sku
[?] Needs unlock code: False
[?] Uses verified boot: True
[?] Factory reset protection (FRP): True
[?] FOTA support: False
[?] Available OEM commands: ['fastboot oem p2u', 'fastboot oem off-mode-charge', 'fastboot oem key', 'fastboot oem lks', 'fastboot oem scp_status', 'fastboot oem scp_log_thru_ap_uart', 'fastboot oem usb2jtag', 'fastboot oem ultraflash', 'fastboot oem ultraflash_en', 'fastboot oem secureBoot', 'fastboot oem battery', 'fastboot oem getversions', 'fastboot oem alive', 'fastboot oem getprojectcode', 'fastboot oem getUID', 'fastboot oem auth_timecount', 'fastboot oem auth_start', 'fastboot oem permission', 'fastboot oem getpermissions', 'fastboot oem getsecurityversion', 'fastboot oem md5', 'fastboot oem repair', 'fastboot oem simunlock', 'fastboot oem simlock', 'fastboot oem simlock_status', 'fastboot oem getdllname', 'fastboot oem unlock']
[?] LK ATAGs: ['atag,videolfb-fb_base_h', 'atag,videolfb-fb_base_l', 'atag,videolfb-vramSize', 'atag,boot', 'atag,imix_r', 'atag,fg_swocv_v', 'atag,fg_swocv_i', 'atag,shutdown_time', 'atag,boot_voltage', 'atag,two_sec_reboot', 'atag,mem', 'atag,vcore_dvfs', 'atag,dfo', 'atag,meta', 'atag,devinfo', 'atag,videolfb', 'atag,mdinfo', 'atag,ptp', 'atag,masp']
now one thing im confused about: fastboot oem key
i had researched this and it helped unlock the bootloader of the Nokia 3
they did it by
fastboot oem key <MD5 Hash Of Your Device Serial>
fastboot flashing unlock
i would try and test this but it dont have the phone on me rn
Click to expand...
Click to collapse
What did you use to parse the image?

honestly i forgot, if i find the tool ill give u the link

Thank you... I'm trying to parse the lk img from Motorola XT2213-3(MT6833) but I don't have enough patience to do it using a hex viewer lol

damnthefall said:
Thank you... I'm trying to parse the lk img from Motorola XT2213-3(MT6833) but I don't have enough patience to do it using a hex viewer lol
Click to expand...
Click to collapse
this took alot of hunting but i finally found it https://github.com/leeminh888/lk_parser

Why do I bootloop after flashing Corvus OS, and my twrp shows random file name

Qintil5 said:
Why do I bootloop after flashing Corvus OS, and my twrp shows random file name
Click to expand...
Click to collapse
wrong place to discuss this, also the random file names are due to user encryption im trying to fix this but my nokia 2.2 died and i have no one to test

areallydumbperson said:
areallydumbperson said:
wrong place to discuss this, also the random file names are due to user encryption im trying to fix this but my nokia 2.2 died and i have no one to test
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Can corvus OS be booted without turning off encryption?