Xoom Mz609 - Xoom Q&A, Help & Troubleshooting

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

Related

[Q] Problem Unlocking Bootloader HTC ONE X

Code:
C:\adb>fastboot getvar cid
cid: CWS__001
finished. total time: 0.002s
C:\adb>fastboot oem writecid 11111111
... INFO elite_init_sd, SD card already power on
INFOsdhw_7xxx_open: id=0
INFO[SD_HW_ERR] SD: No device attached
INFO902910 902E20
FAILED (status read failed (No such file or directory))
finished. total time: 1.262s
C:\adb>
This is what i get.
otherwise when i try to unlock with HTCdev I get error 106 cant unlock bootloader
agbm97 said:
Code:
C:\adb>fastboot getvar cid
cid: CWS__001
finished. total time: 0.002s
C:\adb>fastboot oem writecid 11111111
... INFO elite_init_sd, SD card already power on
INFOsdhw_7xxx_open: id=0
INFO[SD_HW_ERR] SD: No device attached
INFO902910 902E20
FAILED (status read failed (No such file or directory))
finished. total time: 1.262s
C:\adb>
This is what i get.
otherwise when i try to unlock with HTCdev I get error 106 cant unlock bootloader
Click to expand...
Click to collapse
Try these http://www.youtube.com/watch?v=picF8-dcr3w&feature=player_detailpage mayby it help you help

[SOLVED] Can't unlock bootloader to install recovery and new ROMs

I recently acquire a Moto G GPE, I read several post and also try with this https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b and none works. See output:
Code:
D:\>cd d:\Software\Android\ADT\sdk\platform-tools\
d:\Software\Android\ADT\sdk\platform-tools>fastboot.exe oem unlock_data
...
(bootloader) 'unlock_data' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.011s
d:\Software\Android\ADT\sdk\platform-tools>fastboot.exe oem get_unlock_data
...
(bootloader) This command is not needed to unlock. Run fastboot oem
(bootloader) unlock directly.
OKAY [ 0.012s]
finished. total time: 0.012s
D:\>cd d:\Software\Android\ADT\sdk\platform-tools\
d:\Software\Android\ADT\sdk\platform-tools>fastboot.exe oem unlock_data
...
(bootloader) 'unlock_data' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.011s
d:\Software\Android\ADT\sdk\platform-tools>fastboot.exe oem get_unlock_data
...
(bootloader) This command is not needed to unlock. Run fastboot oem
(bootloader) unlock directly.
OKAY [ 0.012s]
finished. total time: 0.012s
Any help?
reynierpm said:
I recently acquire a Moto G GPE, I read several post and also try with this https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b and none works. See output:
Code:
D:\>cd d:\Software\Android\ADT\sdk\platform-tools\
d:\Software\Android\ADT\sdk\platform-tools>fastboot.exe oem unlock_data
...
(bootloader) 'unlock_data' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.011s
d:\Software\Android\ADT\sdk\platform-tools>fastboot.exe oem get_unlock_data
...
(bootloader) This command is not needed to unlock. Run fastboot oem
(bootloader) unlock directly.
OKAY [ 0.012s]
finished. total time: 0.012s
D:\>cd d:\Software\Android\ADT\sdk\platform-tools\
d:\Software\Android\ADT\sdk\platform-tools>fastboot.exe oem unlock_data
...
(bootloader) 'unlock_data' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.011s
d:\Software\Android\ADT\sdk\platform-tools>fastboot.exe oem get_unlock_data
...
(bootloader) This command is not needed to unlock. Run fastboot oem
(bootloader) unlock directly.
OKAY [ 0.012s]
finished. total time: 0.012s
Any help?
Click to expand...
Click to collapse
When you are in fastboot mode, what does the seventh line says?
"Device is ******. Status Code: *"
Also, have you tried this code?
Code:
fastboot oem unlock
Z-WolF said:
When you are in fastboot mode, what does the seventh line says?
"Device is ******. Status Code: *"
Also, have you tried this code?
Code:
fastboot oem unlock
Click to expand...
Click to collapse
Thanks it was LOCKED but after run the command you suggest me and follow the instructions now I have my device UNLOCKED. Now I'm trying to install this recovery but I can't because I don't know how to install from ZIP, any guide or help?

Could someone please run fastboot command for me?

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?

Rooting and unlocking bootloader with newest miui version

Hello,
i cant figure out how is it possible to unlock the bootloader & root after having the newest update.
I cant flash anything using fastboot - it says my device is locked
the version - MIUI-V7.2.3.0.LXKCNDA
any solution? :crying:
first you must unlock bootloader.
dani9998 said:
Hello,
i cant figure out how is it possible to unlock the bootloader & root after having the newest update.
I cant flash anything using fastboot - it says my device is locked
the version - MIUI-V7.2.3.0.LXKCNDA
any solution? :crying:
Click to expand...
Click to collapse
You got the answer, first unlock the bootloader, then flash whatever you want https://youtu.be/ZkBLrn0Dzt4
Enviado desde mi Mi-4c mediante Tapatalk
i get following error:
C:\fastboot>fastboot devices
8c718fed fastboot
C:\fastboot>fastboot oem edl
...
OKAY [ 0.001s]
finished. total time: 0.004s
C:\fastboot>fastboot oem unlock bootloader
...
FAILED (remote: Token verification failed, reboot the device)
finished. total time: 0.011s
C:\fastboot>fastboot oem unlock bootloader
...
FAILED (remote: Token verification failed, reboot the device)
finished. total time: 0.014s
C:\fastboot>fastboot oem unlock bootloader
...
FAILED (remote: Token verification failed, reboot the device)
finished. total time: 0.017s
Click to expand...
Click to collapse

Yuphoria bootloader unlock error

i am getting this
Code:
C:\adb>adb reboot bootloader
C:\adb>fastboot -i 0x2A96 oem devices
...
FAILED (remote: unknown command)
finished. total time: 0.004s
C:\adb>fastboot -i 0x2A96 oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.005s
C:\adb>fastboot devices
73face0a fastboot
C:\adb>
any help to fix this or reset everything !
i did this as before it was not detecting at fastboot due to driver issues : https://forum.xda-developers.com/yu-yuphoria/help/flash-twrp-yu-yuphoria-yu5010a-t3628611
but later i fixed driver issue, hope that is not causing any problem
Try . fastboot OEM unlock

Categories

Resources