Trying to unlock the boot-loader to install custom recovery in order to flash a new rom
i have the Verizon version , is this possible ?
i keep getting errors from basic commands so i am not sure what i am doing wrong
C:\Android>adb reboot bootloader
C:\Android>fastboot oem unlock
...
(bootloader) fastboot oem unlock disabled!
FAILED (remote: )
finished. total time: -0.000s
C:\Android>fastboot oem unlock UNIQUE_KEY
...
(bootloader) fastboot oem unlock disabled!
FAILED (remote: )
finished. total time: 0.001s
C:\Android>fastboot oem get_unlock_data
...
FAILED (remote: unsupported command)
finished. total time: 0.000s
Hello all,
I'm hoping you guys could help me out. I have a bricked Mate 8 and am trying to fix it.
I'm hoping anyone with a Mate 8 (any and every model) could run these commands for me:
(first please boot to fastboot mode.)
fastboot getvar rescue_version
fastboot getvar rescue_phoneinfo
fastboot oem get-product-model
fastboot oem get-psid (if this has personal information please replace it with X or something.)
fastboot getvar vendorcountry
and let me know what they return.
Also, could you let me know if you run HiSuite and choose System Recovery with the device in fastboot, whether you get a 'phone not supported' screen or whether it works.
Thanks!
Hi,
Here's the results from mine:
D:\Mate-8>fastboot getvar rescue_phoneinfo
rescue_phoneinfo: NXT-C900B160
finished. total time: 0.016s
D:\Mate-8>fastboot getvar rescue_version
rescue_version: rescue0.3
finished. total time: 0.078s
gnasher666 said:
Hi,
Here's the results from mine:
D:\Mate-8>fastboot getvar rescue_phoneinfo
rescue_phoneinfo: NXT-C900B160
finished. total time: 0.016s
D:\Mate-8>fastboot getvar rescue_version
rescue_version: rescue0.3
finished. total time: 0.078s
Click to expand...
Click to collapse
Thank you for checking that!
I'm getting closer to successfully tricking HiSuite into wanting to recover my phone.
Can you please run these commands?
fastboot oem get-product-model
fastboot oem get-psid
fastboot getvar vendorcountry
I think oem get-psid might output personal information. If it does, don't post it obviously. I think the most important one is getvar vendorcountry, potentially, because mine just fails on that. When you post, please post any leading spaces, etc before the text so I have an exact replication of the command.
Thank you!
The getvar command didn't work, neither did getvar all.
D:\Mate-8>fastboot oem get-product-model
...
(bootloader) HUAWEI NXT-L29
OKAY [ -0.000s]
finished. total time: -0.000s
D:\Mate-8>fastboot getvar all
getvar:all FAILED (remote: Command not allowed)
finished. total time: 0.000s
D:\Mate-8>fastboot getvar vendorcountry
getvar:vendorcountry FAILED (remote: Command not allowed)
finished. total time: 0.021s
D:\Mate-8>fastboot oem get-psid
...
(bootloader) SN:23Q7Nxxx
(bootloader) IMEI:xxx
IMEI:xxx
OKAY [ 0.022s]
finished. total time: 0.022s
gnasher666 said:
The getvar command didn't work, neither did getvar all.
D:\Mate-8>fastboot oem get-product-model
...
(bootloader) HUAWEI NXT-L29
OKAY [ -0.000s]
finished. total time: -0.000s
D:\Mate-8>fastboot getvar all
getvar:all FAILED (remote: Command not allowed)
finished. total time: 0.000s
D:\Mate-8>fastboot getvar vendorcountry
getvar:vendorcountry FAILED (remote: Command not allowed)
finished. total time: 0.021s
D:\Mate-8>fastboot oem get-psid
...
(bootloader) SN:23Q7Nxxx
(bootloader) IMEI:xxx
IMEI:xxx
OKAY [ 0.022s]
finished. total time: 0.022s
Click to expand...
Click to collapse
Thank you very much for trying that.
It's strange. It looks like HiSuite sends all of those commands to my phone, the last one is vendorcountry which fails, then tells me my phone isn't supported (even though it lists NXT-AL10 as supported for recovery.)
Would you mind trying the System Recovery option in HiSuite and see what happens for you?
Also, if anyone with NXT-AL10 could please check if HiSuite is able to do recovery when it's in fastboot mode, this would potentially help me discover a universal unbrick method, so please let me know!
Here are the results from my AL10 with international L29C900B133 rom :
C:\adb>fastboot getvar rescue_version
rescue_version: rescue0.3
finished. total time: 0.069s
C:\adb>fastboot getvar rescue_phoneinfo
rescue_phoneinfo: NXT-C900B133
finished. total time: 0.000s
C:\adb>fastboot oem get-product-model
...
(bootloader) NEXT
OKAY [ -0.000s]
finished. total time: -0.000s
C:\adb>fastboot oem get-psid
...
(bootloader) SN:VKN5TXXXXXXXXXXX
(bootloader) IMEI:XXXXXXXXXXXXXXX
IMEI:XXXXXXXXXXXXXXX
OKAY [ 0.000s]
finished. total time: 0.016s
C:\adb>fastboot getvar vendorcountry
getvar:vendorcountry FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\adb>fastboot getvar all
getvar:all FAILED (remote: Command not allowed)
finished. total time: 0.008s
As you can see, getvar didn't work for me neither.
And it seems that HiSuite isn't able to do recovery when it's in fastboot mode, because it doesn't see my phone in this mode...
Hi.
Here are the results of my AL10 with chinese ROM AL10C00B156 :
C:\adb>fastboot getvar rescue_version
rescue_version: rescue0.3
finished. total time: 0.068s
C:\adb>fastboot getvar rescue_phoneinfo
rescue_phoneinfo: NXT-AL10C00B156
finished. total time: 0.006s
C:\adb>fastboot oem get-product-model
...
(bootloader) HUAWEI NXT-AL10
OKAY [ 0.006s]
finished. total time: 0.008s
C:\adb>fastboot oem get-psid
...
(bootloader) SN:VKN5T15C24012455
(bootloader) IMEI:869906027864873
IMEI:869906027429222
OKAY [ 0.011s]
finished. total time: 0.012s
C:\adb>fastboot getvar vendorcountry
getvar:vendorcountry FAILED (remote: Command not allowed)
finished. total time: 0.011s
I'll try HiSuite asap...
EDIT : HiSuite (4.0.4.301) recovery doesn't work for me neither : when I click on "Recover system" in the "Entered system recovery mode" screen, it says "Your device does not take care of the recoveries system"...
Thank you very much. So I guess NXT-AL10 is not supported with HiSuite, even though it says it is... Very strange!
It also looks like it's likely there's no way to recover my phone, unfortunately. I might soon give up on trying to find a way to fix it myself (even though I have fastboot...) and send phone to China to see if they can fix it under warranty.
I hope you'll find a solution !
Good luck.
Return from a NXT-L09
duraaraa said:
Hello all,
I'm hoping you guys could help me out. I have a bricked Mate 8 and am trying to fix it.
I'm hoping anyone with a Mate 8 (any and every model) could run these commands for me:
(first please boot to fastboot mode.)
Also, could you let me know if you run HiSuite and choose System Recovery with the device in fastboot, whether you get a 'phone not supported' screen or whether it works."
Click to expand...
Click to collapse
This is what I got:
:\sdk\platform-tools>fastboot getvar rescue_version
rescue_version: rescue0.3
finished. total time: 0.063s
C:\sdk\platform-tools>fastboot getvar rescue_phoneinfo
rescue_phoneinfo: NXT-L09C212B120
finished. total time: 0.016s
C:\sdk\platform-tools>fastboot oem get-product-model
...
(bootloader) HUAWEI NXT-L09
OKAY [ 0.016s]
finished. total time: 0.016s
C:\sdk\platform-tools>fastboot oem get-psid
...
(bootloader) SN:AXXXXXXXXXXXXX
(bootloader) IMEI:8XXXXXXXXXXXX
OKAY [ 0.016s]
finished. total time: 0.016s
C:\sdk\platform-tools>fastboot getvar vendorcountry
getvar:vendorcountry FAILED (remote: Command not allowed)
finished. total time: 0.016s
On the hisuite, I get a message that says my device is not supported, also wifi recovery does not work, Im guessing that happens because I have unloocked the bootloader?
I was able to get an input when running fastboot vendor country. Mine is bricked at least for the moment as well. No go with hisuite to restore.
C:\Users\Malekowsky>fastboot getvar vendorcountry
vendorcountry: dualcu/cn
finished. total time: 0.005s
fastboot oem get-psid
...
FAILED (remote: Command not allowed)
can't get imei info, wich command i can use?
I need help with unlocking bootloader of my HTC DESIRE 828. I tried the method as mentioned in the HTC DEV website but i keep encountering this error
fastboot oem get_identifier_token
FAILED (remote: unknown command)
finished. total time: 0.006sThen with little searching i found this command which i assume is used to lock bootloader ? (not sure) BTW IM NOT GETTING ANY ERROR
fastboot oem lock
(bootloader) [KillSwitch] : /dev/block/platform/mtk-msdc.0/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.051s]
finished. total time: 0.052sBUT WHEN I TRY THIS COMMAND
fastboot oem unlock
(bootloader) [ERR] Command error !!!
OKAY [ 0.004s]
finished. total time: 0.005sit shows me this error.
ADDITIONAL INFORMATION:
My phone is bricked and im trying to flash the stock rom but for that i need bootloader to be unlocked and download mode is showing "S-ON" idk what it means or does....
weapons9clear said:
I need help with unlocking bootloader of my HTC DESIRE 828. I tried the method as mentioned in the HTC DEV website but i keep encountering this error
fastboot oem get_identifier_token
FAILED (remote: unknown command)
finished. total time: 0.006sThen with little searching i found this command which i assume is used to lock bootloader ? (not sure) BTW IM NOT GETTING ANY ERROR
fastboot oem lock
(bootloader) [KillSwitch] : /dev/block/platform/mtk-msdc.0/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.051s]
finished. total time: 0.052sBUT WHEN I TRY THIS COMMAND
fastboot oem unlock
(bootloader) [ERR] Command error !!!
OKAY [ 0.004s]
finished. total time: 0.005sit shows me this error.
ADDITIONAL INFORMATION:
My phone is bricked and im trying to flash the stock rom but for that i need bootloader to be unlocked and download mode is showing "S-ON" idk what it means or does....
Click to expand...
Click to collapse
I shouldn't need to unlock bootloader in order to flash stock rom
go to developer options and check the option - enable oem unlock.then reboot and run the command.
Also how can your phone be bricked with a locked bootloader?It does not make sense .YOu cannot flash ROms on a locked bootloader and if your phone is bricked then that means your bootloader has to be unlocked!!!
Hello. I try to unlock my phone but not working adb screen.
All necessary files and drivers are installed.
When I try run command "fastboot oem unlock", received this messages:
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.005s]
finished. total time: 0.006s
I try the this solution: https://forum.xda-developers.com/android/general/sharp-aquos-s2-ss2-sat-thread-t3761071/
and i writing this command in adb, giving me this :
fastboot.exe oem cert_timecount get
...
FAILED (remote: unknown command)
finished. total time: 0.002s
Please help me unlock this phone.
Hi, did you ever resolve this?
Fingerprint lost, I backed up persist in advance, so I restore it by
fastboot flash persist [INSERT YOUR PERSIST.IMG HERE]
not worked,prompted for "Flashing is not allowed for Critical Partitions"
then I tried
adb shell
su
dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist
I checked /mnt/vendor/persist,files were successfully extracted.
However,the problem still occurred.
Appreciate for any helps.
ChuyanFang said:
Fingerprint lost, I backed up persist in advance, so I restore it by
fastboot flash persist [INSERT YOUR PERSIST.IMG HERE]
not worked,prompted for "Flashing is not allowed for Critical Partitions"
then I tried
adb shell
su
dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist
I checked /mnt/vendor/persist,files were successfully extracted.
However,the problem still occurred.
Appreciate for any helps.
Click to expand...
Click to collapse
Enter this command first: fastboot flashing unlock_critical
Sent from my OnePlus KB2007 using XDA Labs
jwarrior319 said:
Enter this command first: fastboot flashing unlock_critical
Sent from my OnePlus KB2007 using XDA Labs
Click to expand...
Click to collapse
Thanks for ur reply.
It still doesn't work.
C:\Program Files (x86)\OnePlus Mobile>fastboot flashing unlock_critical
FAILED (remote: Device already : unlocked!)
Finished. Total time: 0.005s
C:\Program Files (x86)\OnePlus Mobile>fastboot flashing unlock
FAILED (remote: Device already : unlocked!)
Finished. Total time: 0.003s
I checked the unlocked status then:
C:\Program Files (x86)\OnePlus Mobile>fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.006s]
Finished. Total time: 0.007s
*never mind*
ChuyanFang said:
Thanks for ur reply.
It still doesn't work.
C:\Program Files (x86)\OnePlus Mobile>fastboot flashing unlock_critical
FAILED (remote: Device already : unlocked!)
Finished. Total time: 0.005s
C:\Program Files (x86)\OnePlus Mobile>fastboot flashing unlock
FAILED (remote: Device already : unlocked!)
Finished. Total time: 0.003s
I checked the unlocked status then:
C:\Program Files (x86)\OnePlus Mobile>fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.006s]
Finished. Total time: 0.007s
Click to expand...
Click to collapse
Hmm, it wont allow you to unlock critical. Idk how to fix that.
You could try fastboot oem flashing unlock_critical or fastboot oem unlock_critical
Sent from my OnePlus KB2007 using XDA Labs