Develop Bugs

[Q] Enter Fastboot mode with scrapped volume button, to relock the bootloader

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:

Unlock bootloader: no xperia zl

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...

[Q] Qhsusb mode when try Fastboot mode Xperia S

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?

I tried to unlock my bootloader and my phone is stuck on bootloop

I have tried to re-flash the original ftf file, but I think that I had forgot my "USB debugging" option disabled before unlocking my bootloader... I do not really know wtf is really going on... Any help?

DrunkProgrammer said:
I have tried to re-flash the original ftf file, but I think that I had forgot my "USB debugging" option disabled before unlocking my bootloader... I do not really know wtf is really going on... Any help?
Click to expand...
Click to collapse
I don't think usb debugging is necessary if you select flash mode. Just check that drivers are installed in pc properly or not.

hhjadeja007 said:
I don't think usb debugging is necessary if you select flash mode. Just check that drivers are installed in pc properly or not.
Click to expand...
Click to collapse
They are installed properly! I have fixed again my phone from bootloop when I was trying to install CWM with the same ftf that I am trying right now but it does not work this time

It surely is a problem with pc. Try using your friend's pc.
One another thing, can you enter fastboot mode?
Type fastboot devices in cmd while connecting your phone with vol- button.

pc isnt detecting mobil in fastboot

My pc is not detecting Mobil in fastboot mode. I want to unlock bootloader and root it, is there any way to fix it? I'm using win 10

bisht ankur said:
My pc is not detecting Mobil in fastboot mode. I want to unlock bootloader and root it, is there any way to fix it? I'm using win 10
Click to expand...
Click to collapse
You need to download the correct drivers for Z2 Plus, search on google

visheshjain25 said:
You need to download the correct drivers for Z2 Plus, search on google
Click to expand...
Click to collapse
I tried universal adb drivers and Lenovo z2 adb drive but they didn't work.

bisht ankur said:
I tried universal adb drivers and Lenovo z2 adb drive but they didn't work.
Click to expand...
Click to collapse
Your drivers are not correct, that's why the pc is not detecting the phone, try downloading MI Flash Tool, it has all the necessary drivers for Z2 Plus, google it

visheshjain25 said:
Your drivers are not correct, that's why the pc is not detecting the phone, try downloading MI Flash Tool, it has all the necessary drivers for Z2 Plus, google it
Click to expand...
Click to collapse
Thanks for replying, I tried mi flash but it also didn't work.

this worked for me
bisht ankur said:
My pc is not detecting Mobil in fastboot mode. I want to unlock bootloader and root it, is there any way to fix it? I'm using win 10
Click to expand...
Click to collapse
Connect your smartphone to PC
Make sure the USB debugging is enabled and revoke all debugging history(the option below the enable debugging)
Now install the drivers that appear on the screen as ZUK z2 drivers or something like that.
Install it .
It should take some time.
Then try the following command line"adb devices"
Now a prompt should appear
Click always allow and then on allow.
Now you should be able to connect your phone to the PC.
I just unlocked my bootloader on a win 10 machine
Like this if this works for you.

emotionless161098 said:
Connect your smartphone to PC
Make sure the USB debugging is enabled and revoke all debugging history(the option below the enable debugging)
Now install the drivers that appear on the screen as ZUK z2 drivers or something like that.
Install it .
It should take some time.
Then try the following command line"adb devices"
Now a prompt should appear
Click always allow and then on allow.
Now you should be able to connect your phone to the PC.
I just unlocked my bootloader on a win 10 machine
Like this if this works for you.
Click to expand...
Click to collapse
wow, thanks mate it worked.:good::good:

bisht ankur said:
wow, thanks mate it worked.:good::good:
Click to expand...
Click to collapse
Glad I helped

bisht ankur said:
My pc is not detecting Mobil in fastboot mode. I want to unlock bootloader and root it, is there any way to fix it? I'm using win 10
Click to expand...
Click to collapse
Same here but I used adb wireless app and it worked

IAM also facing this problem 1)first of all you must install zuk drivers only next adb fastboot drivers install your PC and let's go

bisht ankur said:
My pc is not detecting Mobil in fastboot mode. I want to unlock bootloader and root it, is there any way to fix it? I'm using win 10
Click to expand...
Click to collapse
same issuue