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:

[Q] Use computer to turn phone on?

So short story, my galaxy nexus's power button doesnt work anymore. It stopped working for no reason yesterday, yet when I plug it into the charger the charging screen comese on. I want to be able to power my phone on so that I can get all the information onto my computer so that I can easily transfer stuff to my new phone (replacement gnex coming tomorrow) Is there a way I can turn on my phone without using the power button? Any help would be much appreciated.

If you've got the SDK or just ADB available, you should be able to use the command of "adb reboot" to get the device to boot up. Could be wrong.

Can someone guide me in the direction I need so I can do this adb reboot?

chantheman525 said:
Can someone guide me in the direction I need so I can do this adb reboot?
Click to expand...
Click to collapse
Download the ADB file (usually bundled with Fastboot) from any one of these guides that requires it. Or just Google for it.
Unzip all of that, use command line to get into it's directory, hook your phone up over USB, and type:
Code:
adb reboot
Again, not sure if this will work when the phone is off. If it will work, I think you had to have USB debugging turned on. Its not working for me currently on OSX. So I don't think it will. Maybe there's a different ADB command that can help you.
Its a long shot. There are probably better options.

I'd agree with adb reboot if your computer will recognize it from this mode...
Use the guide linked in my sig to set up ADB if you need.

I'm a newbie to all this, but I don't think anyone here mentioned the necessary step of downloading and installing your phone's specific ADB drivers to your computer.
So, to recap:
Download your phone's ADB drivers on to your computer and install them.
Plug your phone in.
Go to your command prompt and type 'adb reboot'.
I think. I'm new, as you can see by my post count and thanks meter.

I tried to adb reboot. Unfortunately the galaxy nexus cant be recognized when the phone is off. Disappointing but not the end of the world. Thanks for everyones help.

If adb works in download mode you could make a jig to get you there.
Sent from my Galaxy Nexus using Tapatalk

Somehow managed to **** it up

Hi as a long time lurker around here i decided to go for an LG G4 after using an iphone for the last 10 years
So i purchased a new handset today and followed the guide and somehow cocked up
Its a h815eu and after i installed the bootloader it updated my firmware to v10c-EUR-XX
Now when i try to carry out the twrp of the guide i just get the message 'waiting for device'
Now before you say 'this is why idiots blah blah' this is the first android device i have ever owned/even looked at
I have cocked up somewhere and frankly need a bit of help
I am usually pretty savvy on most things of this nature so i am feeling a little sheepish having to resort to this thread
The handset is still functioning normally its just not having any of it on the root side of things
Suggestions?

oh forgot to add i have tried to install the twrp manager which tells me root is required for this app
when i enter the command 'apb fastboot reboot' it gives me several lines
also when i enter 'fastboot reboot' i get a message in the top left corner but i cant make it out it looks like 'fastboot uploaded' or something like that

Go into settings on your phone, general, about phone, click on software info. Next tap on build number until it says congratulations you are a developer. Next, back out of there, and look for developer options under settings/general. From here, click on that and then click on USB Debugging. If you unplug and re-plugin your phone as long as you have the proper drivers installed you should be able to do adb reboot-bootloader. From here you should be able to follow root methods elsewhere found on the forum.

drivel2787 said:
Go into settings on your phone, general, about phone, click on software info. Next tap on build number until it says congratulations you are a developer. Next, back out of there, and look for developer options under settings/general. From here, click on that and then click on USB Debugging. If you unplug and re-plugin your phone as long as you have the proper drivers installed you should be able to do adb reboot-bootloader. From here you should be able to follow root methods elsewhere found on the forum.
Click to expand...
Click to collapse
Hi yes i can do that but anything further i try to do gives me waiting for device message
Is it because i am on v10c firmware? Thats the problem with doing something new i was not sure if i cancelled the updates the root would be cancelled out once the updates were installed
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
LGH815cb3d0a5 device
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
< waiting for device >

gap30 said:
Hi yes i can do that but anything further i try to do gives me waiting for device message
Is it because i am on v10c firmware? Thats the problem with doing something new i was not sure if i cancelled the updates the root would be cancelled out once the updates were installed
Click to expand...
Click to collapse
Go back into developer settings and click the option to delete the... I forget the wording but it deletes the computer debug connection so that way when you plug in the computer will all permission again.
Sent from my VS980 4G

jesssiii said:
Go back into developer settings and click the option to delete the... I forget the wording but it deletes the computer debug connection so that way when you plug in the computer will all permission again.
Sent from my VS980 4G
Click to expand...
Click to collapse
Thing is if you delete the the debug option or cancel it you cannot do anything on the phone via the pc
I cannot post any pics till i have 10 posts and i dont want to spam

While the phone is connected. Try and change the USB connection to PTP from MTP.

Ok i have tried kdz and still no joy
it still show the bootloader in corner on start up
and if i enter any commands the phone hangs and i have to remove the battery and get 'waiting for device'
Not good this

gap30 said:
Thing is if you delete the the debug option or cancel it you cannot do anything on the phone via the pc
I cannot post any pics till i have 10 posts and i dont want to spam
Click to expand...
Click to collapse
I'm saying to revoke the previous permissions, not turn off debug. Your phone will then present a popup to connect again when plugged into computer.
LG G2 VZW

jesssiii said:
I'm saying to revoke the previous permissions, not turn off debug. Your phone will then present a popup to connect again when plugged into computer.
LG G2 VZW
Click to expand...
Click to collapse
Yeah just tried that - the problem i have is it hangs in the bootloader if i try any commands ie fastboot reboot
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot TWRP2861.img
< waiting for device >
The first command always works which brings up several lines of text
Its anything after that and this causes the phone to hang and i have to physically remove the battery to get it going again

Strange behavior after update to Nougat.

My phone is full stock. Bootloader blocked, S-On, no root. After that bloody update i cant charge my phone normally. To charge it i must turn it off (not restart - full power down) plug charger - wait few second for battery symbol. Then turn phone on. And it will charge in normal time. I can live with that, but it irritating as my mother in law.
Second problem is much worse. None of my PC/Laptops see my M9. I trying bunch of USB cables (working perfect with other stuff) but not with M9.
I was try root my phone (kingoroot/towelroot/supersu 2.77/8/9) - no effect.
I can`t unlock bootloader, coz ADB dont see my phone.
I try ADB wifi - but it still device connectet to PC via cable in first step.
I preform more then 5 factory reset. Nothing has changed.
Sure - i can connect via AirDroid and still have acces to anything i need...
The question is:
What can i do to unlock bootloader/flash android 6.0 except waiting for official fix.
Sorry for bad eng and thanks for reading.

Enable developer options and then look for "oem unlocking" and just a bit down from there "usb debugging".
You also need look for an up to date rooting tutorial for nougat and a tutorial to return back to 6.0. You have to do a lot of reading BEFORE you start.
Beamed in by telepathy.

shivadow said:
Enable developer options and then look for "oem unlocking" and just a bit down from there "usb debugging".
You also need look for an up to date rooting tutorial for nougat and a tutorial to return back to 6.0. You have to do a lot of reading BEFORE you start.
Beamed in by telepathy.
Click to expand...
Click to collapse
Enable dev ops and turn on usb debbuging/oem unlocking was one of the first step.
Every single rootong option need cable conection - so i cant use it. And in that point we back to the begining...

Danjou667 said:
My phone is full stock. Bootloader blocked, S-On, no root. After that bloody update i cant charge my phone normally. To charge it i must turn it off (not restart - full power down) plug charger - wait few second for battery symbol. Then turn phone on. And it will charge in normal time. I can live with that, but it irritating as my mother in law.
Second problem is much worse. None of my PC/Laptops see my M9. I trying bunch of USB cables (working perfect with other stuff) but not with M9.
I was try root my phone (kingoroot/towelroot/supersu 2.77/8/9) - no effect.
I can`t unlock bootloader, coz ADB dont see my phone.
I try ADB wifi - but it still device connectet to PC via cable in first step.
I preform more then 5 factory reset. Nothing has changed.
Sure - i can connect via AirDroid and still have acces to anything i need...
The question is:
What can i do to unlock bootloader/flash android 6.0 except waiting for official fix.
Sorry for bad eng and thanks for reading.
Click to expand...
Click to collapse
If u do not hear the "connected" sound in windows when plugged in, u may have a faulty USB connection.
Try blowing some air into it or GENTLY clean it.
Good luck!

Fain11 said:
If u do not hear the "connected" sound in windows when plugged in, u may have a faulty USB connection.
Try blowing some air into it or GENTLY clean it.
Good luck!
Click to expand...
Click to collapse
I try all (4) cables/all 10 usb port on all of my computers. I don`t see dirt in port phone/pc.
i just turn on speakers. Yea i hear "plong". But my PC dont see my phone. And adb dont see it either.

Danjou667 said:
I try all (4) cables/all 10 usb port on all of my computers. I don`t see dirt in port phone/pc.
i just turn on speakers. Yea i hear "plong". But my PC dont see my phone. And adb dont see it either.
Click to expand...
Click to collapse
Try re-installing HTC drivers.
See here the latest:
https://androidmtk.com/download-htc-usb-drivers

lastest drivers already in use. But i made small step forward. ADB see my phone. But i stuck @waiting for device... (child crying bbs)

Definitely sounds like a driver problem. Maybe try running a live Linux disc and run adb from that?

philicibine said:
Definitely sounds like a driver problem. Maybe try running a live Linux disc and run adb from that?
Click to expand...
Click to collapse
Perkeleen vittupää! bloody driver. I download drivers from http://droididea.com/download-android-usb-drivers-for-pc-samsung-lg-motorola-sony-oppo-and-others/ adb see my phone on every one goddamn port on all of my comps.
Linux u say... ok maybe it will help but what distro of linux?

Ubuntu is good if your new to it.

philicibine said:
Ubuntu is good if your new to it.
Click to expand...
Click to collapse
Ubuntu hate my GTX 970... Atm linux mint is my second os. And... suprise... linux don`t see my htc either. i install MTP, ADB and android tools - nothing change. Except one thing. adb devices command return 0 devices... I need to learn a lot of new things.

You have enabled USB debugging right? In developer options on the phone?

sure thing. Unlock bootloader in programing options enabled too. Ha! mint see my htc when i type lsusb. So another small step forward. Now i only must figure out why adb dont see my phone.

Can you get into fastboot? If fastboot devices sees your phone you can flash a ROM with that.

fastboot devices - no perrmision im lurking for solution for this atm

sudo fastboot devices

philicibine said:
sudo fastboot devices
Click to expand...
Click to collapse
yeah that one help a little. Now i see "HT535YJ0****"
http://askubuntu.com/questions/705537/no-permissions-fastboot-fastboot-and-adb-not-working - this is solution it think. But i don`t know yet how to use it. I can get my idVendor from lsusb Bus 003 Device 004: ID 0bb4:0ff0 HTC (High Tech Computer Corp.) Now i have few minutes to read about udev. After that i know im newbie and first things first - basics.
At this moment i stuck here
$ sudo sh -c "echo '# Megafon SP-A20i' >> /etc/udev/rules.d/51-android.rules"
$ sudo sh -c "echo 'SUBSYSTEM=="usb", ATTR{idVendor}=="8087", MODE="0666", GROUP="plugdev"' >> /etc/udev/rules.d/51-android.rules"
$ sudo service udev restart
udev stop/waiting
udev start/running, process 1821
$

Don't worry about udev if your phone is already detected.
You need to find the firmware for your phone and a stock ROM.zip that matches it.
First use
Code:
sudo fastboot flash firmware.zip
And then
Code:
sudo fastboot flash ROM.zip
Hopefully you will be sorted then.
---------- Post added at 10:05 PM ---------- Previous post was at 09:59 PM ----------
Just read back to what your trying to do in your first post.
You can do this to unlock your bootloader
Code:
sudo fastboot oem unlock
Then you can flash twrp, and then any ROM you need.

philicibine said:
Then you can flash twrp, and then any ROM you need.
Click to expand...
Click to collapse
Nope. It can`t be so easy. "< waiting for device >". When i try do it on windows i see the same txt.
Command "get oem token identifier" give the same result. And as u know i need this token to unlock bootloader via htc developer center.

But you said when you did sudo fastboot devices this happened?
Danjou667 said:
Now i see "HT535YJ0****"
Click to expand...
Click to collapse
That's what happens when your device is ready to flash and detected.
Surely if you precede every command to unlock with sudo you should be fine? No more waiting for device.

USB debugging

Hello everyone, I really need help bad!! I just got my honor 7x and was trying to unlock my bootloader. I have followed directions for how to do this. The problem is that although I can see phone and files on laptop. For some reason the phone doesn't show as connected. I have tried adb commands as well as multi tool. Every way I try it doesn't work. I have unlocked bootloaders on other phone before. No matter what driver I have downloaded I still have yellow caution. Sighn in device manager ager. I have searched and searched for solution with no resolve. If it matters it is the model that a
Ends with the number 24. Thanks in advance

Hmmm..
edshawn911 said:
Hello everyone, I really need help bad!! I just got my honor 7x and was trying to unlock my bootloader. I have followed directions for how to do this. The problem is that although I can see phone and files on laptop. For some reason the phone doesn't show as connected. I have tried adb commands as well as multi tool. Every way I try it doesn't work. I have unlocked bootloaders on other phone before. No matter what driver I have downloaded I still have yellow caution. Sighn in device manager ager. I have searched and searched for solution with no resolve. If it matters it is the model that a
Ends with the number 24. Thanks in advance
Click to expand...
Click to collapse
Hello..
Original Cable ?
What Version Of Windows ?
Drivers Installed ?
ADB Debugging Switched On ?
When You Type "ADB / FASTBOOT DEVICES" Seeing A Series Of Letters & Numbers ?

RaiderWill said:
Hello..
Original Cable ?
What Version Of Windows ?
Drivers Installed ?
ADB Debugging Switched On ?
When You Type "ADB / FASTBOOT DEVICES" Seeing A Series Of Letters & Numbers ?
Click to expand...
Click to collapse
original as well as tried other cable.
windows 8
installed whatever drivers i could find. nothing said 7x .
i have allow adb debugging in charge only mode checked. i
when i type fastboot command as well as adb devices it doesn't find anything.

edshawn911 said:
original as well as tried other cable.
windows 8
installed whatever drivers i could find. nothing said 7x .
i have allow adb debugging in charge only mode checked. i
when i type fastboot command as well as adb devices it doesn't find anything.
Click to expand...
Click to collapse
Ok... Since I have no intention to root until Huawei pushes the Oreo and Facial Recognition updates, I have kept USB Debugging "OFF" and set Select USB Configuration to: Media Transfer Protocol (MTP)
Then, I attempted to do what you are trying to do... and it worked perfectly..
So.. Do This:
Step 1 Click on your windows icon and in the search bar type "CMD"
Step 2 Set USB Configuration to MTP.
Step 3 Again I had Debugging off.. you can try it with it on if you like.. either way turn off your device.
Step 4 Hold down the Vol-Down button while plugging your device into your USB cable connected to your computer.
Step 5 This will turn on your device and put you in Fastboot Mode.
Step 6 Now go to your ADB Command Line and type "fastboot devices"
You'll see it.....