Hi, i have i few questions about it-.... my xperia zl says not allowed unlock bootloader.... but im still try to do it.
i download all the files and drivers from sdk, when i open the cmd or the terminal and i type fastboot.exe getvar like sony says, i put my phone in bootloader mode with +volume and plug the usb, the blue light turn it on and stay on... but my pc or command prompt just says waiting for devices, not devide detected, is that a problem of my drivers or is for the locked bootloader?
thanks.
leo_hacker82 said:
Hi, i have i few questions about it-.... my xperia zl says not allowed unlock bootloader.... but im still try to do it.
i download all the files and drivers from sdk, when i open the cmd or the terminal and i type fastboot.exe getvar like sony says, i put my phone in bootloader mode with +volume and plug the usb, the blue light turn it on and stay on... but my pc or command prompt just says waiting for devices, not devide detected, is that a problem of my drivers or is for the locked bootloader?
thanks.
Click to expand...
Click to collapse
If your status of unlock bootloader = no mean that you can't unlock your bootloader. At the moment no method can unlock that status. Maybe you can ask your mobile carrier and request one, most likely will cost you some money.
leo_hacker82 said:
Hi, i have i few questions about it-.... my xperia zl says not allowed unlock bootloader.... but im still try to do it.
i download all the files and drivers from sdk, when i open the cmd or the terminal and i type fastboot.exe getvar like sony says, i put my phone in bootloader mode with +volume and plug the usb, the blue light turn it on and stay on... but my pc or command prompt just says waiting for devices, not devide detected, is that a problem of my drivers or is for the locked bootloader?
thanks.
Click to expand...
Click to collapse
1. i think this is not the right place to post this kind of questions...
2. if says no it means NO, you cant unlock it, u must think in buy another phone with unlocked status:YES
3. i think if you keep trying you may brick your phone...
Related
Hello friends,
How to get into fastboot to relock the bootloader, if my volume button is dead? By dead, I mean the ribbon has been ripped off of the mobo (it was soldered onto mobo).
Since I'm a brand-new noob, the only way I know of and have done is to get into fastboot mode and lock it back up like what I did when I unlocked it. Any other way to lock it, ideally within the Android OS? Since my volume buttons are completely dead, I doubt that I can get into any "mode" other than OS right now..
TIA!
adb reboot bootloader.
I've seen that command in a post from search earlier, but there was no response after that post.
Would you explain the procedure? I am afraid that I might do anything wrong on top of these disasters i've gone thru with this phone
I also saw another line during earlier search: "if they don't know how to setup an adb command, they probably shouldn't unlock their phones"... Looks like I've done what I shouldn't..?
I would say doing whatever ripped the volume button cable out was what you shouldn't have been doing If you unlocked the phone you have the software you used to unlock, right? What software/guide did you use/follow? Are you using Windows/Linux/Mac? The only way to get to the bootloader w/o the volume buttons (afaik) is to use adb via usb. If you provide more details I can try to help you.
cswithxda said:
I've seen that command in a post from search earlier, but there was no response after that post.
Would you explain the procedure?
Click to expand...
Click to collapse
Once you're in adb reboot bootloader, do fastboot oem lock. Opposite of how you unlocked it in the first place
cswithxda said:
I've seen that command in a post from search earlier, but there was no response after that post.
Would you explain the procedure? I am afraid that I might do anything wrong on top of these disasters i've gone thru with this phone
Click to expand...
Click to collapse
navigate your cmd line to the folder with adb and fastboot in it. Hook the phone up to the computer and type:
Code:
adb reboot bootloader
which will make your phone reboot into the bootloader mode. You can then proceed with what you need to do.
I also saw another line during earlier search: "if they don't know how to setup an adb command, they probably shouldn't unlock their phones"... Looks like I've done what I shouldn't..?
Click to expand...
Click to collapse
I agree with whoever said that. This is another example of people messing with things before reading and learning how they work.
Thanks for your help guys!
btw, anyone found xdadevelopers to load extremely slower in Firefox when compared to Chrome? (just offtopic)
Anyway, I unlocked the bootloader when I was switching to yakju cmd and this folder called "fastboot-and-adb" in which there is both adb.exe and fastboot.exe. I used command "fastboot unlock bootloader" or something alike.
I'll do some more search and learn. Don't want you guys to think of me as a lazy bone who unlocked their bootloader using 1-click toolkit
p.s. edit: in my other thread, someone suggested using quickboot app.
Thanks for your replies guys!
martonikaj said:
navigate your cmd line to the folder with adb and fastboot in it. Hook the phone up to the computer and type:
Code:
adb reboot bootloader
which will make your phone reboot into the bootloader mode. You can then proceed with what you need to do.
I agree with whoever said that. This is another example of people messing with things before reading and learning how they work.
Click to expand...
Click to collapse
Somehow it says device not found
I do have proper driver (Naked Driver Beta 0.5 by 1wayjonny) that my phone was able to be recognized under bootloader at the time when I could actually get into bootloader. My phone is also being recognized as media device now... I have also turning usb debug on...
Try adb remount
The ad devices
This should list the serial number
Then all commands should work
Sent from my Galaxy Nexus using xda premium
cswithxda said:
Somehow it says device not found
I do have proper driver (Naked Driver Beta 0.5 by 1wayjonny) that my phone was able to be recognized under bootloader at the time when I could actually get into bootloader. My phone is also being recognized as media device now... I have also turning usb debug on...
Click to expand...
Click to collapse
You need to turn USB debugging on, and then type "adb devices" and see if it shows up. It may not using the Naked Driver; I had to install the full Samsung USB driver package before ADB would see my Galaxy Nexus.
If it does show up, then you type "adb reboot-bootloader" and it should boot into fastboot. Then just type "fastboot oem lock" and it will wipe the storage partitions and restore the bootloader lock.
Thanks for the help at late night guys. I finally got into the bootloader, thru a mac tho Kinda ironic that I am a supporter of Windows, well, at least a firm user of Windows.
Tried adb remount, it still says device not found
synaesthetic said:
You need to turn USB debugging on, and then type "adb devices" and see if it shows up. It may not using the Naked Driver; I had to install the full Samsung USB driver package before ADB would see my Galaxy Nexus.
If it does show up, then you type "adb reboot-bootloader" and it should boot into fastboot. Then just type "fastboot oem lock" and it will wipe the storage partitions and restore the bootloader lock.
Click to expand...
Click to collapse
I believe that you quoted my "I have turned USB debug on" ;p
Gave up on trying Windows drivers. When I was flashing the Yakju, I tried Samsung full driver, and it didn't work on my machine, i.e., the phone can't be detected in bootloader mode, while the beta 0.5 driver worked. So I decided not to mess with it anymore.
It looks like when the phone is not under bootloader, windows recognize it fine as MTP devices and install proper samsung driver from the internet directly. This allows me to open it up in explorer to browse files and such, but the phone won't show up under adb devices somehow.
Looks like MTP device (when the phone is in Android OS) and the fastboot mode use two kinds of drivers. This is just my assumption, though.
Anyway, finally got into bootloader now with Mac, and it's pretty funny I have to do everything thru command as the volume rockers are dead
And most importantly, thank you guys for your help!
Just another update
It's real funny now that the bootloader is locked, I can't unlock it again cuz I don't have the volume button working, so I couldn't choose YES on the phone.
I'm not trying to unlock it again, but just to confirm if there's really no work around, in case I encounter this situation again in the future
Lucky that locking the bootloader won't erase everything, or I won't be able to flash a ROM with it locked... :cold sweating:
i can not into FASTBOOT mode
why i press the search button connect the USB
i cant see the blue led and into the charging mode, blue light for two seconds, into orange LED
not find new hardware
just SEMC Mass Storage USB Drive
oh come im f**king dead
has been installed adb package
===============================
OKAY finally, I find the problem
bootloader unlock allowed: no
SIMLOCK
How do I into FASTBOOT mode
use testpoint? s1tool? for free? help me PLZ~
Are you sure you have all the correct drivers installed?
yes, but connect the USB did not prompt new hardware
No Worries...
You have me here,
first you should have ADB installed (adb package including fastboot)
second you should have SEUS (sony Ericsson Update service) and in some cases instead of SEUS you may have SE pc suite.
Turn off your phone,after 10 seconds turn it on again and connect the USB cable while holding back key.
simply extract adb package somewhere,navigate to that folder via CMD
Type:
fastboot devices
now there should be a connected device...:good:
Feel Free To Press My THX Button
peter_dizai said:
You have me here,
first you should have ADB installed (adb package including fastboot)
second you should have SEUS (sony Ericsson Update service) and in some cases instead of SEUS you may have SE pc suite.
Turn off your phone,after 10 seconds turn it on again and connect the USB cable while holding back key.
simply extract adb package somewhere,navigate to that folder via CMD
Type:
fastboot devices
now there should be a connected device...:good:
Feel Free To Press My THX Button
Click to expand...
Click to collapse
thanks man
i try it.
peter_dizai said:
You have me here,
first you should have ADB installed (adb package including fastboot)
second you should have SEUS (sony Ericsson Update service) and in some cases instead of SEUS you may have SE pc suite.
Turn off your phone,after 10 seconds turn it on again and connect the USB cable while holding back key.
simply extract adb package somewhere,navigate to that folder via CMD
Type:
fastboot devices
now there should be a connected device...:good:
Feel Free To Press My THX Button
Click to expand...
Click to collapse
i need adb package i cant find it
There you go!
metalbug said:
i need adb package i cant find it
Click to expand...
Click to collapse
http://developer.android.com/sdk/index.html
orion4000 said:
http://developer.android.com/sdk/index.html
Click to expand...
Click to collapse
not find new hardware
just SEMC Mass Storage USB Drive
oh come im f**king dead
has been installed adb package
You can't get into fastboot mode if your bootloader is locked.
Try doing a little searching in these forums. These questions have been asked and answered many times before.
Sent from my R800x using xda premium
He speaks the truth! Also, if youre simlocked too than theres no way to unlock for free. If youre not simlocked and youre not CDMA then you can just go on sonys site to unlock your bootloader. Otherwise you need to get your bootloader unlocked, which will run you ~$24, just use the goog.
metalbug said:
not find new hardware
just SEMC Mass Storage USB Drive
oh come im f**king dead
has been installed adb package
Click to expand...
Click to collapse
You Need to Unlock your Bootloader First then try to download and install the drivers for your device.. the main driver called (S1boot fastboot) here hopefully it would help you.. http://forum.xda-developers.com/showthread.php?t=1317531
orion4000 said:
You Need to Unlock your Bootloader First then try to download and install the drivers for your device.. the main driver called (S1boot fastboot) here hopefully it would help you.. http://forum.xda-developers.com/showthread.php?t=1317531
Click to expand...
Click to collapse
no man, you dont have my idea, my device dont have blue led, and dont find new hardware "S1 boot" just only "SEMC Mass Storage USB Drive"
Oh sorry!
metalbug said:
no man, you dont have my idea, my device dont have blue led, and dont find new hardware "S1 boot" just only "SEMC Mass Storage USB Drive"
Click to expand...
Click to collapse
Sorry brother i'm trying to help! i will look for more solutions for you!
orion4000 said:
Sorry brother i'm trying to help! i will look for more solutions for you!
Click to expand...
Click to collapse
thanks man, find only way it pay for unlock
True the only way to unlock you bootloader is to pay there is no "free" way. If you need your bootloader unlocked I recommend Alejandrissmo.
BL unlocked allowed no but Iam unlock it
netizenmt said:
You can't get into fastboot mode if your bootloader is locked.
Try doing a little searching in these forums. These questions have been asked and answered many times before.
Sent from my R800x using xda premium
Click to expand...
Click to collapse
Hey man ! Ive got an xperia play R800i and Iam unlock with the S1Tool and this is worked for me and my phone said BL unlocked allowed : NO , but i cant get into fastboot mod , but the flashtool said my bootloader status : ROOT and the S1Tool the same thing . Well i guess if the bootloader status isnt rootable , but if you unlock it , the FASTBOOT NOT GONNA WORK ......
netizenmt said:
You can't get into fastboot mode if your bootloader is locked.
Try doing a little searching in these forums. These questions have been asked and answered many times before.
Sent from my R800x using xda premium
Click to expand...
Click to collapse
well today i RElock my bootloader with Xperia_relock.ftf file with flash tool. i have the same probelm with the drivers. i cant enter fastboot. And now i want to unlock it again but how to do that if when we enter to fastboot, the device connect to flash mode can i unlock it?
Geodoomer said:
well today i RElock my bootloader with Xperia_relock.ftf file with flash tool. i have the same probelm with the drivers. i cant enter fastboot. And now i want to unlock it again but how to do that if when we enter to fastboot, the device connect to flash mode can i unlock it?
Click to expand...
Click to collapse
same here..any solution anyone?
I was trying to unlock my boot loader of my Xperia S. And everthing was ok.
But when I try to connect my phone on fastboot mode (connecting the USB while volume(+) is pressed) the computer recognize the device immediately how "qhsusb_dload". When disconnect the device after that, the phone only turn on with Power and Volumen(+) keys. After that, the phone still working ok, the problem only is present when try to connect to Fastboot mode. As extra information, I can connect the phone in download mode (connecting the USB while volume(-) is pressed) and the computer recognize the device how "S1 boot download".
I'm running on Windows 8.1 pro, also I try on Windows 7 professional, both of 64-bits.
Sorry for bad english, I speak spanish.
seams you didn't install the driver,searching in the unlock thread,there might be the drivers for this problem .http://www.theandroidsoul.com/how-to-unlock-bootloader-xperia-arc-play-neo-pro/
wxl104 said:
seams you didn't install the driver,searching in the unlock thread,there might be the drivers for this problem .http://www.theandroidsoul.com/how-to-unlock-bootloader-xperia-arc-play-neo-pro/
Click to expand...
Click to collapse
I used this tool to install abd and fastboot drivers http://forum.xda-developers.com/showthread.php?t=2588979 but the problem remains.
Too I used this tutorial step per step http://forum.xda-developers.com/sho...tmctr=(not provided)&__utmv=-&__utmk=33073341
But the phone always appears how"qhsusb_dload"
d4vid.pinz0n said:
I used this tool to install abd and fastboot drivers http://forum.xda-developers.com/showthread.php?t=2588979 but the problem remains.
Too I used this tutorial step per step http://forum.xda-developers.com/sho...tmctr=(not provided)&__utmv=-&__utmk=33073341
But the phone always appears how"qhsusb_dload"
Click to expand...
Click to collapse
I don't know,did you checked if your phone can unlock or not?
wxl104 said:
I don't know,did you checked if your phone can unlock or not?
Click to expand...
Click to collapse
Yes, I checked. I followed the instructions of "unlockbootloader.sonymobile.com/instructions" to check it and "Bootloader unlock allowed" says "Yes".
d4vid.pinz0n said:
Yes, I checked. I followed the instructions of "unlockbootloader.sonymobile.com/instructions" to check it and "Bootloader unlock allowed" says "Yes".
Click to expand...
Click to collapse
I don't know why,can you download pa-4.2 beta?I can't download it ,if ok,could you download it ,and send to me?
Hey guys,
I followed this thread to unlock boot loader (http://forum.xda-developers.com/showthread.php?t=2694600), used the automated way to install adb drivers and did everything like the post says, but when I boot into bootloader and connect to my pc, when I type an adb command to get the code, it just stays at waiting for device for ages...
What I'm doing wrong? I even updated to the last api of adb, which are on the automated post (http://forum.xda-developers.com/showthread.php?t=2588979), posted by an user.
Can anyone help me please?
Thanks in advance!
You don't use ADB at the bootloader, you use fastboot. ADB is only when Android is running
Hgneto said:
Hey guys,
I followed this thread to unlock boot loader (http://forum.xda-developers.com/showthread.php?t=2694600), used the automated way to install adb drivers and did everything like the post says, but when I boot into bootloader and connect to my pc, when I type an adb command to get the code, it just stays at waiting for device for ages...
What I'm doing wrong? I even updated to the last api of adb, which are on the automated post (http://forum.xda-developers.com/showthread.php?t=2588979), posted by an user.
Can anyone help me please?
Thanks in advance!
Click to expand...
Click to collapse
This method does not require you to boot into bootloader. It does require S-off, however. Notice the instructions only tell you to boot into bootloader as the last step, simply to verify the unlock was successful.
Confused...
What? I don't know what to next then... I installed the automated way drivers, installed HTC connect program and allowed the connection via usb in developer options... What shall I do next to unlock boot loader?
For what I see on the VomerGuide it says after:
"Enter Fastboot (bootloader) Mode" ... now you are telling me that I do not need to...
When I enter in this Fastboot Mode, I connect the device to pc and then say the command to get the code, but it says waiting for device for ages and doesn't give me the code... Can you explain me what I'm doing wrong/what shall I do next?
Thanks in advance!
Hgneto said:
What? I don't know what to next then... I installed the automated way drivers, installed HTC connect program and allowed the connection via usb in developer options... What shall I do next to unlock boot loader?
For what I see on the VomerGuide it says after:
"Enter Fastboot (bootloader) Mode" ... now you are telling me that I do not need to...
When I enter in this Fastboot Mode, I connect the device to pc and then say the command to get the code, but it says waiting for device for ages and doesn't give me the code... Can you explain me what I'm doing wrong/what shall I do next?
Thanks in advance!
Click to expand...
Click to collapse
Make sure "usb debugging is enabled" on your phone, then cmd "adb devices" on PC and it should return your phonr serial number.
Will try that.
BTW, shall I enter in bootloader and then connect to PC, or do the other way around?
Thanks!
Sent from my G3
Hgneto said:
What? I don't know what to next then... I installed the automated way drivers, installed HTC connect program and allowed the connection via usb in developer options... What shall I do next to unlock boot loader?
For what I see on the VomerGuide it says after:
"Enter Fastboot (bootloader) Mode" ... now you are telling me that I do not need to...
When I enter in this Fastboot Mode, I connect the device to pc and then say the command to get the code, but it says waiting for device for ages and doesn't give me the code... Can you explain me what I'm doing wrong/what shall I do next?
Thanks in advance!
Click to expand...
Click to collapse
My apologies. I was looking under a different page from the link you provided. If you are following VomerGide, yes you do start in fastboot.
Try this first, though. Make sure USB debugging is enabled, leave phone on (not fastboot), plug it into your computer, and cmd "adb devices". If a message comes up on phone screen to allow computer connection, choose to always allow. Once you have gotten adb to recognize device, you can cmd "adb reboot bootloader" and phone should reboot into bootloader. In bootloader screen on phone, you might have to select fastboot mode. Then try to cmd "fastboot devices" and see if it brings up you device info. If so, you are good to go!
I'm trying unlock the bootloader of my Moto Z2 Force, but I just get 2 command lines
I can´t share the image, but only shows me the first 2 lines from bootloader
have you did
step by step al thy say in the guide?
its not suppse to do any problems...
try again
https://forums.lenovo.com/t5/Moto-Z-Force/Moto-Z2-Force-bootloader-unlock/m-p/3789998
hope you will make it?
I can't unlock bootloader on mine either. I am using a moto Z2 force on T-Mobile network but MetroPCS is my provider. I followed all step by steps I have all the latest Motorola drivers and Android studio components. After I type fast boot OEM get unlock data it just sits there is a blinking cursor indefinitely
JoJoEx said:
I can't unlock bootloader on mine either. I am using a moto Z2 force on T-Mobile network but MetroPCS is my provider. I followed all step by steps I have all the latest Motorola drivers and Android studio components. After I type fast boot OEM get unlock data it just sits there is a blinking cursor indefinitely
Click to expand...
Click to collapse
Grab adb and fastboot from here Extract and open folder, hold shift, right click in the folder and open command prompt. Type 'fastboot devices' to verify that your device is connected. If all set, then type 'fastboot oem get_unlock_data' to get your string and follow the steps here
cant unlockbootloader
tried it with those links and it says...failed unknown command
JoJoEx said:
tried it with those links and it says...failed unknown command
Click to expand...
Click to collapse
Make sure you're using oem cable, 2.0 usb port from the motherboard, not a hub port from the front of the pc. Also, make sure you're not putting the 'quotes' in the command.
41rw4lk said:
Make sure you're using oem cable, 2.0 usb port from the motherboard, not a hub port from the front of the pc. Also, make sure you're not putting the 'quotes' in the command.
Click to expand...
Click to collapse
im using the usbc that came with phone and using the usb 2.0 slot onth computer.. the comp is an asus tuf laptop..have phone usb set to media transfer
JoJoEx said:
im using the usbc that came with phone and using the usb 2.0 slot onth computer.. the comp is an asus tuf laptop..have phone usb set to media transfer
Click to expand...
Click to collapse
You should be in bootloader mode when you run fastboot commands
41rw4lk said:
You should be in bootloader mode when you run fastboot commands
Click to expand...
Click to collapse
i run.. .\adb devices for some reason my comp only runs it if you use .\ in front of the commands . then i use.... .\adb reboot bootloader ...the phone goes into bootloader .. then .\fastboot devices and it shows the serial, then .\fastboot oem get_unlock_codes and i was getting a cursor that stays until i close the program but with new link someone gave me for adb it says failed unknown command
1. T-mobile is unlockable
2. Turn on developer mode and Allow OEM unlock
3. On Windows PC, open adb via CMD. Connect your phone and type:
adb devies
You should allow authorisations on your phone.
4. Enter bootloader mode (maybe wait for the PC to recognize the phone). Type command:
fastboot oem get_unlock_data
5. Follow these links that others gave. Make sure Motorola and Google USB driver are installed.
Me neither , i was on lineages but something went wrong I brick my phone so I sent it to service center after that i am unable to get the Unlock Data. I seem the problm with users who repaired their phone some how .
gautam_tarun101 said:
Me neither , i was on lineages but something went wrong I brick my phone so I sent it to service center after that i am unable to get the Unlock Data. I seem the problm with users who repaired their phone some how .
Click to expand...
Click to collapse
Check usb port, cable, and adb/fastboot files. 95% of the trouble people have with flashing and/or fastboot commands can be attributed to one of those.
No that didn't work