Hello,
This question is mostly aimed at the experienced devs and hackers who have been hacking and developing with HTC devices for a good several years. I recall with my older HTC devices, there was an array of HTC-specific fastboot commands that could be used with "fastboot oem <command>." You could get a list of the commands with either 'fastboot oem ?' or 'fastboot oem cmdlist' (or something similar-- don't remember exactly). Also, there was a way to enter into a bootloader shell in which these commands could be used on their own without having to type 'fastboot oem.'
Does this feature no longer exist with the HTC 10? I know there are the fastboot oem commands related to bootloader unlocking, and 'fastboot oem rebootRUU' still exists for firmware flashing, but nothing else that used to work with older devices (i.e., the M7) does anything anymore. My fastboot binary is the latest generic fastboot-- I am aware there is an HTC specific fastboot that exists now, but I've used the generic google fastboot for oem firmware flashing, radio flashing, etc without any hiccups whatsoever, and I've never used anything with past devices other than the generic fastboot. And these commands I'm inquiring about, I am fairly sure were built into the device's firmware anyway and had nothing to do with what was built into the fastboot binary.
Device: HTC 10 US Unlocked, firmware is the latest Unlocked firmware (1.96--), bootloader is unlocked and S-OFF...
It was a useful feature, but if it no longer exists, oh well. Any info is appreciated, though. Thanks!
Hello,
i found theese commands in aboot.img, some are testet.
bootloader:
htc_fastboot oem reboot-download
htc_fastboot oem reboot-ftm
htc_fastboot oem rebootRUU
htc_fastboot oem listpartition
htc_fastboot oem listram
htc_fastboot oem dmesg
htc_fastboot oem last_dmesg
htc_fastboot oem get_ext_csd_emmc
htc_fastboot oem get_wp_info_emmc
htc_fastboot oem check_emmc_mid
htc_fastboot oem read_sandisk_fw
htc_fastboot oem update_emmc_partition
htc_fastboot oem read_mmc
htc_fastboot oem write_mmc
htc_fastboot oem test_emmc
htc_fastboot oem erase_phone_storage
htc_fastboot oem select-display-panel
htc_fastboot oem readconfig
htc_fastboot oem writeconfig
htc_fastboot oem easydump
htc_fastboot oem readsecureflag
htc_fastboot oem readunlock
htc_fastboot oem dumpDataCode
htc_fastboot oem dsiw
htc_fastboot oem dsir
htc_fastboot oem ddrtest
htc_fastboot oem dump_ram_full
htc_fastboot oem setbacklight
htc_fastboot oem get_tamper_flag
htc_fastboot oem get_force_sec_boot_reason
axst68 said:
Hello,
i found theese commands in aboot.img, some are testet.
bootloader:
htc_fastboot oem reboot-download
htc_fastboot oem reboot-ftm
htc_fastboot oem rebootRUU
htc_fastboot oem listpartition
htc_fastboot oem listram
htc_fastboot oem dmesg
htc_fastboot oem last_dmesg
htc_fastboot oem get_ext_csd_emmc
htc_fastboot oem get_wp_info_emmc
htc_fastboot oem check_emmc_mid
htc_fastboot oem read_sandisk_fw
htc_fastboot oem update_emmc_partition
htc_fastboot oem read_mmc
htc_fastboot oem write_mmc
htc_fastboot oem test_emmc
htc_fastboot oem erase_phone_storage
htc_fastboot oem select-display-panel
htc_fastboot oem readconfig
htc_fastboot oem writeconfig
htc_fastboot oem easydump
htc_fastboot oem readsecureflag
htc_fastboot oem readunlock
htc_fastboot oem dumpDataCode
htc_fastboot oem dsiw
htc_fastboot oem dsir
htc_fastboot oem ddrtest
htc_fastboot oem dump_ram_full
htc_fastboot oem setbacklight
htc_fastboot oem get_tamper_flag
htc_fastboot oem get_force_sec_boot_reason
Click to expand...
Click to collapse
Oh, cool! Thank you for that information. And yeah, those commands are all slightly different from the old commands that I remembered and tried to use..which would explain why they didn't work
Not entirely clear what aboot.img is...I'm guessing it's the equivalent of what used to be hboot.img.. but that I can find out easily enough.. just curious what tool you use to unpack it, though. Can it be unpacked with Android Image Kitchen?
https://www.google.com/url?sa=t&sou...-CUcQFggyMAI&usg=AOvVaw1wuu1MylB8oC8o8vtAKe0G
oem_sec_boot is 0x%X
cmd_oem_easydump
cmd_oem_dsir add=0x%x, value=0x%x
fastboot oem dsir 53
fastboot oem dsiw 51 FF
Reset the stored oem panel in device info
oem reboot-download
oem reboot-ftm
oem rebootRUU
oem listpartition
oem listram
oem dmesg
oem last_dmesg
oem get_ext_csd_emmc
oem get_wp_info_emmc
oem check_emmc_mid
oem read_sandisk_fw
oem update_emmc_partition
oem read_mmc
oem write_mmc
oem test_emmc
oem ufs_get_lun
oem ufs_set_lun
oem erase_phone_storage
oem select-display-panel
oem readconfig
oem writeconfig
oem easydump
oem readsecureflag
oem readunlock
oem dumpDataCode
oem dsiw
oem dsir
oem ddrtest
oem dump_ram_full
oem setbacklight
oem get_tamper_flag
oem get_force_sec_boot_reason
Usage: oem ddrtest 0x<addr> 0x<size> <round> [<break>]
Default test: oem ddrtest 0 0 0
Related
Hi guys
While trying to unlock my mediapad m2 bootloader, I encountered a couple of hidden fastboot commands (found in the stock rom image). Some look like standard things, others seem very interesting:
Code:
fastboot oem backdoor info
[INDENT]FB LockState: LOCKED
USER LockState: LOCKED[/INDENT]
fastboot oem backdoor get
[INDENT]FBLOCK**obfuscated**[/INDENT]
fastboot oem backdoor end
[INDENT]remote: fastboot stat not match[/INDENT]
fastboot oem get-bootinfo
[INDENT]locked[/INDENT]
fastboot oem check-rootinfo
[INDENT]old_stat: SAFE
now_stat: SAFE
change_time: 0000000000[/INDENT]
fastboot oem check-image
[INDENT]secure image verify success[/INDENT]
fastboot oem relock
[INDENT]remote: stat not match[/INDENT]
fastboot oem backdoor set
[INDENT]remote: data parse fail[/INDENT]
fastboot oem frp-erase
[INDENT]Haven't tried, but should remove the Factory Reset Protection (FRP)[/INDENT]
fastboot oem emmc_diag
[INDENT]cid info:
mid 17,oid 256,pnm 064G70,prv 0.0,psn 0x18b66278,
csd dump:
D02700320F5903FFFFFFFFEF864000AB00
ext_csd dump:
...
FMW FAIL! WRITE PROTECT![/INDENT]
fastboot oem emmc-dump
[INDENT]unknown status code[/INDENT]
fastboot oem get_key_version
[INDENT]huawei_key_v1[/INDENT]
fastboot oem battery_present_check
[INDENT]3984mv[/INDENT]
fastboot oem get_hwnff_ver
[INDENT]Ver2.3[/INDENT]
fastboot oem get-psid
[INDENT]SN:**YourIMEI**[/INDENT]
fastboot oem get-build-number
[INDENT]V100R001C00B000[/INDENT]
fastboot oem get-product-model
[INDENT]HUAWEI M2-A01W[/INDENT]
Some commands seem quite useful, while others are quite disturbing (why is there a backdoor?!).
Have fun with these commands... I'll update them if any of you have some updates.
Cheers
Loris
same question too
So a quick thread here. Asus devices won't be unlocked by the common commands which are
Code:
Fastboot oem unlock
Fastboot oem unlock confirm
From now on, asus uses there own codes.
Here it is
Code:
Fastboot oem asus-go
Fastboot oem asus-go confirm
This is not a guide. If you use the old command it will return an error UNKNOWN COMMAND.
Thanks !
thenewgengamer said:
So a quick thread here. Asus devices won't be unlocked by the common commands which are
Code:
Fastboot oem unlock
Fastboot oem unlock confirm
From now on, asus uses there own codes.
Here it is
Code:
Fastboot oem asus-go
Fastboot oem asus-go confirm
This is not a guide. If you use the old command it will return an error UNKNOWN COMMAND.
Thanks !
Click to expand...
Click to collapse
Thanks bro... but when i tried this to my zenfone 5 (t00j), fastboot still shows FAILED (remote: unknown OEM command)
i am using :
ADB version 1.0.35
Revision fc2a139a55f5-android
Same here commands fail ..see date of this post
me too unknown oem command on asus 400cg
Been trying.......
Been trying to unlock this damn bootloader for months now. This is what I got when I gave the command...……………………..
(bootloader) Fail to unlock device due to invalide signature!
OKAY [ 0.031s]
finished. total time: 0.031s
I decided to go back to stock when I learned that the device is receiving Oreo (a bit far too late IMO), but for whatever reason, Android confirms that my bootloader is unlocked, but will not agree to allow me to run
fastboot oem lock to lock the bootloader. Any idea on how to fix this?
ap4ss3rby said:
I decided to go back to stock when I learned that the device is receiving Oreo (a bit far too late IMO), but for whatever reason, Android confirms that my bootloader is unlocked, but will not agree to allow me to run
fastboot oem lock to lock the bootloader. Any idea on how to fix this?
Click to expand...
Click to collapse
Once you have download stock firmware run these commands in fastboot
Note all data on the internal storage will be erased including pictures downloads etc
fastboot oem lock begin
fastboot oem fb_mode_set
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot oem lock
Hi Everyone,
Those of you who have unlocked the OEM with a key, realize the 'bad key' error that shows up afterwards.
If you are trying to restore your phone back to factory image, the default images can be downloaded here:
Link to Factory Images
lexiyuri has a post on restoring the G7 to stock images as described here.
However, for me the bad key error didn't go away and finally ended up with additional steps in between to lock the oem. The commands below in that sequence worked for me. I don't see the 'bad key' error any more. If you're also struggling with the 'bad key' display on your g7 play, and would like to restore to stock properly, here's the code.
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot oem lock begin
fastboot oem lock begin
fastboot oem lock
fastboot oem lock
fastboot oem lock
fastboot flash boot boot.img
fastboot oem lock
fastboot flash logo logo.bin
fastboot flash dtbo dtbo.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase DDR
fastboot erase cache
fastboot erase carrier
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Hope this helps,
First of all this is a guide to lock your bootloader. You shouldn't provide a link to retail builds for this. Always use the current builds matching to your specific software channel.
Before you run any lock command you must check if your system is running. Finish the installation wizard and do a reboot. After that you should run the oem lock command. The very last step is to deactivate the OEM unlock option.
Hello,
today i got a Moto E20 for debugging my webservices. I habe to Unlock the Bootloader for that.
I enabled the Developer-Menu in Android and the oem_unlock and usb-debugging in the settings.
When i boot the device into fastboot all seems OK... i get a connection with adb and fastboot to the device.
But all "fastboot oem XXX" commands just reply
fastboot oem device_info
...
OKAY [ 0.000s ]
finished. total time: 0.000s
Click to expand...
Click to collapse
That is the default reply for
fastboot oem get_unlock_data
fastboot oem device_info
just with different timings...
Any suggestions?
Bootloader version is aruba-1bfa2a4-2021
SW-Version: motorola/aruba_reteu/aruba:11/RON31.266-20/63893
kind regards
Sven
you are in the fastbootd mode .. the correct mode would be in the bootloader mode (adb reboot bootloader) ..
unfortunately it still does not work - the relevant command does not seem to work (fastboot oem get_unlock_data) -
motorola via support says it can not be unlocked .. but i certainly dont believe that - the e40 for example can be ..
the reteu firmware might be limited ..