I have am using windows 7. got the latest USB drivers from motorola and the Android SDK. And get a result from D:\fastboot devices command
So it is conected OK. However when I put this command in (below) I get an error message. I copied and pasted directly from the motorola website. I am trying to unlock the phone for a friend (I normally only work on HTCs because they are the most nub friendly/forgiving) anyway moving on. What do I need to do now in order to get this done? I want to unlock the device and get the simlock off so that my friend can run this Rogers phone on Virgin. on bootloader screen the info is thus:
AP fastboot flash mode (s)
0A.74
eMMC info: Size 16G
to return to normal mode - first press power key to power down
Device is locked. Staus code: 0
Battery OK
OK to program
Transfer mode:
USB connected
And the error from the fastboot command:
D:\>fastboot oem get_unlock_data
...
FAILED (remote: unsupported command)
finished. total time: 0.007s
Am I missing a step (obviously I have to be or it wouldn't be giving me gyp) what do I need to do now? Thanks
XT910 isn't unlockable...
TrippleT said:
XT910 isn't unlockable...
Click to expand...
Click to collapse
That sucks how come? They have the device listed on the Motorola site for unlocking the device. And is there a way around it? Or do you know of any tools for calculating the simlock code so it can run on any network? Thanks and thank you for the reply
What if you put another stock rom on it?
Just flash it with RSD lite
Related
I need help with my razr. I ended up just going to safestrap and wipe my phone because i wanted a fresh start thinking that it would only do a factory reset. Well i thought wrong, my whole phone is wiped, no operating system, no anything. I rebooted it and now I am only able to access the fastboot menu. I went to flash it to stock with RSD Lite, everything was working but when it got after the system.img (12/15) it just stopped and said it failed. I thought i had the wrong .xml file so i downloaded another one but it did the same thing. This is what the screen of my phone says:
Code:
[FONT="System"]AP Fastboot Flash Mode (S)
0A.66
Device is LOCKED. Status Code: 0
Battery OK
OK to Program
Transfer Mode:
USB Connected[/FONT]
I thought maybe the "Device is LOCKED. Status Code: 0" had something to do with it but i don't know. I've tried the command "Fastboot oem get_unlock_data" and this shows up:
Code:
[FONT="System"]c:\Android\sdk\platform-tools>fastboot oem get_unlock_data
...
FAILED <remote: unsupported command>
finished. total time: 0.002s[/FONT]
If anyone could help with what .xml i need to flash a whole new system to my phone, if the phone needs to say "Device is UNLOCKED" for it to work, use a different program to flash with, or if i just have one hella expensive brick. It would be highly appreciated and you would be my new best friend if you can help.
What Fastboot file you are trying to flash?
And what rom was on the phone before the brick?
Sent from my Razr XT910
When I plug my phone in fastboot on to my pc, fastboot detects it. When I then try to run a command, it says:
FAILED (command write failed (Unknown error))
finished. total time: 0.580s
After this, the screen of my phone just stays the same, except no button input works, not even holding down the power button for 10 seconds. The only way I can get out of this, is by actually pulling out the battery. After this, my phone works normally again.
How can i make the command of my PC get to my phone?
kayaven said:
When I plug my phone in fastboot on to my pc, fastboot detects it. When I then try to run a command, it says:
FAILED (command write failed (Unknown error))
finished. total time: 0.580s
After this, the screen of my phone just stays the same, except no button input works, not even holding down the power button for 10 seconds. The only way I can get out of this, is by actually pulling out the battery. After this, my phone works normally again.
How can i make the command of my PC get to my phone?
Click to expand...
Click to collapse
Do commands (like adb install .apk) work fine when phones turned on or does it freeze still ?
Will_Xda said:
Do commands (like adb install .apk) work fine when phones turned on or does it freeze still ?
Click to expand...
Click to collapse
adb will detect my phone, but as soon as I run a command, it freezes and no writing will come trough, so no they do not work.
Oh, and for some more info on my phone:
- The bootloader hasn't been unlocked;
- Running Android 4.1.1
- Already wiped it (backup gone wrong so I lost all stuff :/)
Could it be because my USB ports are just lame? (USB 2.0)
kayaven said:
adb will detect my phone, but as soon as I run a command, it freezes and no writing will come trough, so no they do not work.
Oh, and for some more info on my phone:
- The bootloader hasn't been unlocked;
- Running Android 4.1.1
- Already wiped it (backup gone wrong so I lost all stuff :/)
Could it be because my USB ports are just lame? (USB 2.0)
Click to expand...
Click to collapse
It will only work on USB2.0 for me and not on USB3.0. what operating system are you using ?
What are you trying or wish to do?
Which command?
Will_Xda said:
It will only work on USB2.0 for me and not on USB3.0. what operating system are you using ?
Click to expand...
Click to collapse
I'm using Windows 7 Ultimate x64, fastboot and adb are both running normal for the rest.
RuudM said:
What are you trying or wish to do?
Which command?
Click to expand...
Click to collapse
Well, i am trying to unlock my bootloader, but any command that writes to the phone will freeze it.
Unlocking bootloader: If I remember well, you need to have an unlock-code from HTC. Try the steps on this page from HTC Developer. Click on the picto 'unlock bootloader'.
Tutorial for the rest can be found here
RuudM said:
Unlocking bootloader: If I remember well, you need to have an unlock-code from HTC. Try the steps on this page from HTC Developer. Click on the picto 'unlock bootloader'.
Tutorial for the rest can be found here
Click to expand...
Click to collapse
I've already done that, but the command I need to run in order to get that code freezes it.
Sorry if the next is a bit 'low-profile' but it is difficult to tell where you are stuck
Just to be sure: I assume you have selected the right phone and downloaded the right fastboot-version (Windows, Linux or OsX) on HTC.com. Unpacked size of fastboot for Windows is (at this moment, from HTC) 183.651 bytes.
Phone: you are in the bootloader-screen, and (for Windows) you have a DOS-box opened on your desktop and able to execute the fastboot command.
What happens if you type in 'fastboot devices'? Does it respond?
If so, typing 'fastboot oem get_identifier_token' should respond as well. Or is that the part where you are getting stuck?
RuudM said:
Sorry if the next is a bit 'low-profile' but it is difficult to tell where you are stuck
Just to be sure: I assume you have selected the right phone and downloaded the right fastboot-version (Windows, Linux or OsX) on HTC.com. Unpacked size of fastboot for Windows is (at this moment, from HTC) 183.651 bytes.
Phone: you are in the bootloader-screen, and (for Windows) you have a DOS-box opened on your desktop and able to execute the fastboot command.
What happens if you type in 'fastboot devices'? Does it respond?
If so, typing 'fastboot oem get_identifier_token' should respond as well. Or is that the part where you are getting stuck?
Click to expand...
Click to collapse
I've got the original Android SDK fastboot, but that won't really matter, I suppose. The rest is the same. Furthermore, when i use the 'fastboot devices', it responds, but when i use something like 'fastboot oem get_identifier_token', it says FAILED (command write failed (Unknown error)), and the phone gets stuck.
I really have no idea why this is happening, i will now test if the official HTC fastboot works... :fingers-crossed:
-----------
Omg I'm an idiot, i just had it open on hboot and not fastboot >.<
I didn't know the difference Thanks a lot anyway everyone!
My Z5 compact was updated to Nougat using the OTA service.
The bluetooth integration to my car stopped working and I read that this was a noted problem I decided to flash my phone back to Marshmallow.
I'd installed custom ROMs on previous HTC phones following info from XDA so was pretty confident.
After following the Sony guidelines and obtaining my unlock key I am unable to get it to work in fastboot mode.
I suspect that it is a USB problem at one end or another.
If I connect up the phone to the PC using the original lead I can find it using adb devices and the device is showing up as error free "Sony sa0113 ADB Interface Driver" in Windows 10 device manager.
However the phone isn't charging and I can't get it into Fastboot by holding the up vol key and plugging in the USB lead.
I can get a black screen with the blue led by running adb reboot bootloader and the phone is recognised from fastboot devices but when I try to unlock the bootloader I get an error:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -i 0x0fce oem unlock 0xB4D9AxxxxC359F2C
...
FAILED (remote: Command did not succeed)
finished. total time: 0.042s
Any help appreciated.
PhilG57 said:
My Z5 compact was updated to Nougat using the OTA service.
The bluetooth integration to my car stopped working and I read that this was a noted problem I decided to flash my phone back to Marshmallow.
I'd installed custom ROMs on previous HTC phones following info from XDA so was pretty confident.
After following the Sony guidelines and obtaining my unlock key I am unable to get it to work in fastboot mode.
I suspect that it is a USB problem at one end or another.
If I connect up the phone to the PC using the original lead I can find it using adb devices and the device is showing up as error free "Sony sa0113 ADB Interface Driver" in Windows 10 device manager.
However the phone isn't charging and I can't get it into Fastboot by holding the up vol key and plugging in the USB lead or by running adb reboot fastboot
If feels like I haven't go the fastboot USB drivers but I can't see how or where I can add them.
Any help appreciated.
Click to expand...
Click to collapse
Disable driver signature enforcement then reinstall sony drivers
tapiwasam said:
Disable driver signature enforcement then reinstall sony drivers
Click to expand...
Click to collapse
Thanks. I think I am OK there because I accepted the drivers from an unverified source during installation.
Also I can see the phone with both adb devices and fastboot devices
However when I run adb reboot bootloader the phone reboots but comes up with a blank screen with the blue led.
adb reboot bootloader just goes into bootloader mode and not fastboot mode which is needed to unlock it. Go directly into fastboot by typing adb reboot fastboot
Then when your phone led is flashing blue, run your fastboot "oem unlock" command.
Saw now that you already tried that sorry about that.
Tried running cmd with admin privileges to see if that shows any difference?
Also from sony:
Please note! It will only be possible to unlock the boot loader for certain releases. You can check if it is possible to unlock the boot loader of your device in the service menu by following the steps below:
In your device, open the dialler and enter *#*#7378423#*#* to access the service menu.
Tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked.
Click to expand...
Click to collapse
PhilG57 said:
My Z5 compact was updated to Nougat using the OTA service.
The bluetooth integration to my car stopped working and I read that this was a noted problem I decided to flash my phone back to Marshmallow.
I'd installed custom ROMs on previous HTC phones following info from XDA so was pretty confident.
After following the Sony guidelines and obtaining my unlock key I am unable to get it to work in fastboot mode.
.... snip....
Click to expand...
Click to collapse
You don't need to unlock your bootloader to simply downgrade to official MM! Just use flashtool to flash the appropriate MM ftf. There are plenty guides available on XDA and elsewhere.
I'm lost in your explanation.
You wanted to unlock your bootloader to be able to downgrade your phone? That's right? And it's fine to me, but you don't need to do that if you don't feel like. Unlocking your bootloader is nog necessary to downgrade to MM via flashtool.
So you tried to unlock your bootloader. But what you write what happened afterwards is completely unclear to me, because it contradicts itself.
-->> "Also I can see the phone with both adb devices and fastboot devices"
Fine. This means your connected with your phone and fastbook recognizes your phone. So bootloader is unlocked and software to control that works fine.
-->> "However when I run adb reboot bootloader the phone reboots but comes up with a blank screen with the blue led."
Fine, so you unlocked your bootloader, and rebooted in fastboot.
-->> Obviously. It's an unlocked bootloader, you can double unlock it or something like that. You can relock it if you want (which doesn't make any difference for what you want to do) but that's a different method.
Is there any reason that you absolutely need to a second method to enter fastboot mode? Or any fastboot mode? It could be possible with another kernel, but I don't see the point to flash another kernel. I would just leave it like it is.
PhilG57 said:
Thanks. I think I am OK there because I accepted the drivers from an unverified source during installation.
Also I can see the phone with both adb devices and fastboot devices
However when I run adb reboot bootloader the phone reboots but comes up with a blank screen with the blue led.
Click to expand...
Click to collapse
that is notmal behaviour, that is fastboot mode, indicated by that blue LED
Thanks for the clarification that I don't need to unlock the bootloader to downgrade using flashtool. What I didn't say was that I couldn't reinstall Nougat using the Sony tool software restore option or get anywhere with flashtool because the phone won't go into the blue led mode by inserting the USB and holding the up vol button. I did try running flashtool in one window and the command line tools in another with the idea of running flashtool first and then unplugging the phone and replugging it to use command line to get the blue LED state, but that doesn't work because the command line tools can't see the phone once flashtool is running and has addressed the phone.
From what i read, i assume you are on nougat and want to go back to MM, right?
So you would need flashmode instead of fastboot mode.
You get there with holding Vol down button and plugging in USB cable on turned off phone.
Flashmode also shows a green notification light instead of the blue one.
If you having Problems to get there, please check following:
make sure to have latest version of flashtool installed http://www.flashtool.net/downloads.php
install drivers from your flashtool\drivers folder
don't use an USB 3.0 port or cable(have heard of some people having trouble with)
PhilG57 said:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -i 0x0fce oem unlock 0xB4D9AxxxxC359F2C
...
FAILED (remote: Command did not succeed) <- this
finished. total time: 0.042s
Any help appreciated.
Click to expand...
Click to collapse
OP, I had the exact same problem as you. At the time I tried absolutely everything but never found the culprit. So after several months I actually succeeded today
This is the guide I followed - https://forum.xda-developers.com/z5-compact/general/guide-how-to-root-z5c-painful-using-t3549388 and it worked perfectly.
A few pointers:
- Go to the service menu (*#*#SERVICE#*#*) before you begin, before you turn OEM Unlocking ON from Dev Options .
- Take note of what it says in Configuration and Firmware.
- Now enable OEM Unlocking and take note again, it should say stuff like Model Number: Unknown and other unknown stuff.
- Reboot - IMPORTANT.
- Use the guide I gave you and you will be fine, it took me ages to find a solution but now I'm on MM and rooted
Hope I helped :fingers-crossed::fingers-crossed::fingers-crossed:
Hello
my tablet hang on huawei logo and not working anythings !!!
bootloader locked and i dont know imei serial number and biuldnumber to unlock bootloader
get device in fastboot mode and get detail to unlock bootloader and give me this message :
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
getvar:all FAILED (remote: Command not allowed)
finished. total time: 0.004s
How Can i Flash Android or factory reset or unlock bootloader
Sorry English not my first language .
Well, you need to do the following:
1- Download the firmware from here
then extract the file to get the "dload" folder.
2-Get sdcard and use card reader so your pc be able to read it as a flash stick.
3- copy "dload" folder to sdcard, then insert it into your device.
4- Get into the recovery mode,
by completely turning off your device, then press (Vlo. UP + power) buttons, wait the device vibs, release the power button and keep "vol. up" one, till you get into the recovery mode.
and from the list, chose "upgrade from sdcard" option (the last one), and your device will start re-installing the whole system again.
mann1 said:
Well, you need to do the following:
1- Download the firmware from here
then extract the file to get the "dload" folder.
2-Get sdcard and use card reader so your pc be able to read it as a flash stick.
3- copy "dload" folder to sdcard, then insert it into your device.
4- Get into the recovery mode,
by completely turning off your device, then press (Vlo. UP + power) buttons, wait the device vibs, release the power button and keep "vol. up" one, till you get into the recovery mode.
and from the list, chose "upgrade from sdcard" option (the last one), and your device will start re-installing the whole system again.
Click to expand...
Click to collapse
Hello My Friend
Thanks For Reply
Device Hang On Huawei Logo After Turn ON And Not Get in Recovery Mode !!!!
I,m Record Video Tablet Working And Attachment On This Post Please See This And Give me help to fix this please
Not Any way unlock bootloader without SN And Imei ?
Video Link : Download
mo4sa said:
Hello My Friend
Thanks For Reply
Device Hang On Huawei Logo After Turn ON And Not Get in Recovery Mode !!!!
I,m Record Video Tablet Working And Attachment On This Post Please See This And Give me help to fix this please
Not Any way unlock bootloader without SN And Imei ?
Video Link : Download
Click to expand...
Click to collapse
What did you do to get your device like that?
Generally you will find the IMEI of your device on label sticker comes with the device box, usually between the manual's pages.
Try this method to unlock the bootloader, it MIGHT work, i'm not sure, but give it a try
Get into fastboot mode (Vol. down + power) then
type this code:
Code:
fastboot oem unlock 1282022012246616
mann1 said:
What did you do to get your device like that?
Generally you will find the IMEI of your device on label sticker comes with the device box, usually between the manual's pages.
Try this method to unlock the bootloader, it MIGHT work, i'm not sure, but give it a try
Get into fastboot mode (Vol. down + power) then
type this code:
Code:
fastboot oem unlock 1282022012246616
Click to expand...
Click to collapse
Hello My Friend
Thanks for my post reply
I Try this code butt now working and give me this :
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock 1282022012246616
...
FAILED (remote: password wrong)
finished. total time: 0.010s
i don,t know what i,m to do !
If don,t unlock bootloader no any way to use my tablet ?
mo4sa said:
Hello My Friend
Thanks for my post reply
I Try this code butt now working and give me this :
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock 1282022012246616
...
FAILED (remote: password wrong)
finished. total time: 0.010s
i don,t know what i,m to do !
If don,t unlock bootloader no any way to use my tablet ?
Click to expand...
Click to collapse
Sorry, without IMEI or bootlaoder i can't deal with such situation, wait for answers from others.
Did you flash custom recovery before?
mann1 said:
Sorry, without IMEI or bootlaoder i can't deal with such situation, wait for answers from others.
Did you flash custom recovery before?
Click to expand...
Click to collapse
No i,m not Flash Custom Recovery !
No Any idea to fix this ????????????
mo4sa said:
No i,m not Flash Custom Recovery !
No Any idea to fix this ????????????
Click to expand...
Click to collapse
Did you finally get help in regards to your issue, as I have the same problem
mann1 said:
What did you do to get your device like that?
Generally you will find the IMEI of your device on label sticker comes with the device box, usually between the manual's pages.
Try this method to unlock the bootloader, it MIGHT work, i'm not sure, but give it a try
Get into fastboot mode (Vol. down + power) then
type this code:
Code:
fastboot oem unlock 1282022012246616
Click to expand...
Click to collapse
Not sure if you still have this thread in notification, but I'm having the exact same issue as the OP.
Model - S10-231u
IMEI: 863693023231929
S/N: K8D6R14B03000379
Hope you can calculate a code to unlock it, I'm ready to test or flash anything if you need me to do so.
I have the same problem and can not find a solution to it today so I hope you help
I unfortunately can not find the imei number
I have an SN number and a mac number
Either the device number S10-231w
I hope you can solve my friends
could use some help. when I input fastboot devices in terminal the phone is recognized but:
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
FAILED (remote failure)
finished. total time: 0.108s
Click to expand...
Click to collapse
I have the code, I have the phone in fastboot but the unlock fails and the phone still says locked.
edit: developer options are greyed out on oem unlocking. think I read somewhere you have to wait 3 days. can I get conformation on that? I bought an "unlocked" phone
Grimace78 said:
could use some help. when I input fastboot devices in terminal the phone is recognized but:
I have the code, I have the phone in fastboot but the unlock fails and the phone still says locked.
edit: developer options are greyed out on oem unlocking. think I read somewhere you have to wait 3 days. can I get conformation on that? I bought an "unlocked" phone
Click to expand...
Click to collapse
You must connect Motorola phones to internet if OEM unlock is greyed out.
It can take 3-14+ days after connecting to internet to be available.
Thank you for the confirmation I connected the phone yesterday to the internet