Hi, Guys.
I have many doubts about this topic and there are some things that I do not understand.
I should have this system activated on my phone but I do not know if I have it activated.
This is the output of the command that should say if it is activated and says nothing.
PS C:\Program Files (x86)\Minimal ADB and Fastboot> .\fastboot devices
XXXXXXX fastboot
PS C:\Program Files (x86)\Minimal ADB and Fastboot> .\fastboot getvar anti
getvar:anti FAILED (remote: GetVar Variable Not found)
finished. total time: 0.016s
I do not understand, I do not know what you are saying. Well yes, he says he can not find the variable
The bootloader is unlocked and has the weekly EU 8.9.13 installed and use the redwolf recovery.
Thanks for all and sorry for my english.
alkaide said:
Hi, Guys.
I have many doubts about this topic and there are some things that I do not understand.
I should have this system activated on my phone but I do not know if I have it activated.
This is the output of the command that should say if it is activated and says nothing.
PS C:\Program Files (x86)\Minimal ADB and Fastboot> .\fastboot devices
XXXXXXX fastboot
PS C:\Program Files (x86)\Minimal ADB and Fastboot> .\fastboot getvar anti
getvar:anti FAILED (remote: GetVar Variable Not found)
finished. total time: 0.016s
I do not understand, I do not know what you are saying. Well yes, he says he can not find the variable
The bootloader is unlocked and has the weekly EU 8.9.13 installed and use the redwolf recovery.
Thanks for all and sorry for my english.
Click to expand...
Click to collapse
getvar:anti FAILED (remote: GetVar Variable Not found). This is not clearly answer. I didn't got arb protection. I must be known. Have or not?
no "getvar anti" = no ARB
Fabio Magalhaes said:
getvar:anti FAILED (remote: GetVar Variable Not found). This is not clearly answer. I didn't got arb protection. I must be known. Have or not?
no "getvar anti" = no ARB
Click to expand...
Click to collapse
thanks for answering, but it does not clarify much your answer, I understand that it is not activated but I do not know
alkaide said:
thanks for answering, but it does not clarify much your answer, I understand that it is not activated but I do not know
Click to expand...
Click to collapse
I´m sorry. So, "getvar anti" means that the device has no AntiRollBack protection
Fabio Magalhaes said:
I´m sorry. So, "getvar anti" means that the device has no AntiRollBack protection
Click to expand...
Click to collapse
It has no protection when you buy the phone almost automatically unlock and install an EU and these do not have that protection so free
Huawei fastboot commands
I find some fastboot commands for Huawei ( Get from my P8 Lite 2015 version )
Note: Very high possibility to brick your device if use it wrong!!!!
There they go:
fastboot
flash slock <-- this one was write like it is!!! weird!!!
flash boot
flash recovery
flash system
flash userdata
flash cache
flash cust
flash rescue_recovery
flash device_validation
getvar rescue_version
getvar rescue_phoneinfo
getvar vendorcountry
getvar rescue_ugs_port
getvar rescue_enter_recovery
getvar max-download-size
getvar error_print
getvar partition-type
oem emmc_diag
oem emmc-dump
oem get_key_version
oem battery_present_check
oem get_hwnff_ver
oem get-psid
oem get-build-number
oem get-product-model
oem hwdog certify close
oem backdoor end
oem get-bootinfo
oem check-rootinfo
oem check-image
oem relock
oem hwdog certify set
oem backdoor set
oem frp-erase
oem unlock
oem frp-unlock
oem lock-state info
oem backdoor info
oem hwdog certify begin
oem backdoor get
I hope this help some one!
Bye!
Thank you for the share!
persona78 said:
Huawei fastboot commands
I find some fastboot commands for Huawei ( Get from my P8 Lite 2015 version )
Note: Very high possibility to brick your device if use it wrong!!!!
There they go:
fastboot
flash slock <-- this one was write like it is!!! weird!!!
flash boot
flash recovery
flash system
flash userdata
flash cache
flash cust
flash rescue_recovery
flash device_validation
getvar rescue_version
getvar rescue_phoneinfo
getvar vendorcountry
getvar rescue_ugs_port
getvar rescue_enter_recovery
getvar max-download-size
getvar error_print
getvar partition-type
oem emmc_diag
oem emmc-dump
oem get_key_version
oem battery_present_check
oem get_hwnff_ver
oem get-psid
oem get-build-number
oem get-product-model
oem hwdog certify close
oem backdoor end
oem get-bootinfo
oem check-rootinfo
oem check-image
oem relock
oem hwdog certify set
oem backdoor set
oem frp-erase
oem unlock
oem frp-unlock
oem lock-state info
oem backdoor info
oem hwdog certify begin
oem backdoor get
I hope this help some one!
Bye!
Click to expand...
Click to collapse
Can you please share fastboot binaries in orders supports all commands?
Dears, with the unlock bootloader... how we can run around? Only by purchasing the unlock key? I have a P9Lite for forensic case to analize e.g...
fastboot oem get-psid does not work on a Psmart POT-LX1
but would be very helpful for get IMEI on P20, where it is not printed on backside:
>fastboot oem get-psid
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
PS C:\adb> fastboot oem unlock
FAILED (Write to device failed (Too many links))
fastboot: error: Command failed
PS C:\adb> fastboot devices
PS C:\adb> fastboot devices
PS C:\adb> fastboot devices
de3d7f09 fastboot
PS C:\adb> fastboot oem unlock
FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
PS C:\adb>
tried every fastboot command but szme error
The correct command is "fastboot flashing unlock" !
https://c.realme.com/in/post-details/1244566811094024192
zabbaluga said:
The correct command is "fastboot flashing unlock" !
https://c.realme.com/in/post-details/1244566811094024192
Click to expand...
Click to collapse
Same error with that command i tried every command noluck
Did you first apply the deep testing apk?
zabbaluga said:
Did you first apply the deep testing apk?
Click to expand...
Click to collapse
Yeah idid i solved the problem , to use fastboot command with realme devices you should use an usb 2.0 port not a 3.0 or usb ones coz my laptops had only usb 3.2 i used another one and i succeeded now im on pixel experience, thanks for your time dude
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..
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?