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:
hi everyone, i'm trying to install CM9 on my LT15i, i've tried using the CM wiki instructions and both the following guides...
androidauthority.com/xperia-arc-lt15i-root-android-4-0-ics-80265/
and
androidforums.com/rezound-all-things-root/506466-scottys-noob-friendly-root-guide-start-finish.html
the phone is already fully unlocked and has CM 7.2.0 anzu installed. i've tried simply using the clockwork recovery mod bootloader to wipe the phone and install CM 9.0.0, but on reboot the phone gets past the boot logo then just shows a black screen, so i assumed i needed to flash an appropriate ROM for CM9; this is where my problem begins.
every forum i've read about this process says i must enable usb debugging (done) and "disable fastboot" under settings>power, i do not have a "power" option in my settings and cannot find anything related to fastboot on the phone; although i'm not sure this is the problem. when android is running normally and i attempt to list devices with adb.exe on windows, it successfully returns the phone's serial number. when i shut the phone down, hold the menu button and plug in the usb cable, fastboot mode appears to work correctly as the LED comes on blue and "android adb device" appears in the windows device manager (i've tried installing the arc usb/adb drivers from various sources, they all seem to work correctly). but when i attempt to list devices after restarting in fastboot mode, adb.exe says it cannot find any device. fastboot.exe has not communicated with the device whatsoever, but i assumed i might need to get the adb.exe usb daemon/server running correctly first for this to work.
i did this process once already when i installed CM7, it was successful the first time and everything went smoothly. from what i recall i just did exactly as described above and fastboot.exe was able to find the device no problem. but that was a number of months ago, hopefully i'm just missing some obvious step.
cheers
WookieInHeat said:
every forum i've read about this process says i must enable usb debugging (done) and "disable fastboot" under settings>power, i do not have a "power" option in my settings and cannot find anything related to fastboot on the phone;
Click to expand...
Click to collapse
There is no such thing. And USB debugging is only required if you want to root stock ROM, every other action can be done without it.
WookieInHeat said:
although i'm not sure this is the problem. when android is running normally and i attempt to list devices with adb.exe on windows, it successfully returns the phone's serial number. when i shut the phone down, hold the menu button and plug in the usb cable, fastboot mode appears to work correctly as the LED comes on blue and "android adb device" appears in the windows device manager (i've tried installing the arc usb/adb drivers from various sources, they all seem to work correctly). but when i attempt to list devices after restarting in fastboot mode, adb.exe says it cannot find any device. fastboot.exe has not communicated with the device whatsoever, but i assumed i might need to get the adb.exe usb daemon/server running correctly first for this to work.
i did this process once already when i installed CM7, it was successful the first time and everything went smoothly. from what i recall i just did exactly as described above and fastboot.exe was able to find the device no problem. but that was a number of months ago, hopefully i'm just missing some obvious step.
cheers
Click to expand...
Click to collapse
Drivers, drivers, drivers.
If your phone is in fastboot mode, make sure drivers are installed. Proper drivers.
You do not need ADB server for installing a kernel.
Just open up Command Prompt and install the kernel with command
Code:
fastboot flash boot boot.img
.
Assuming boot.img is in the same folder as fastboot.exe.
Someguyfromhell said:
Drivers, drivers, drivers.
If your phone is in fastboot mode, make sure drivers are installed. Proper drivers.
Click to expand...
Click to collapse
thanks for the reply someguyfromhell. i've tried every "android adb interface" driver under the sun for the S1 fast boot device that appears in the windows device manager when i put the phone in fastboot. when i try to send any command with fastboot.exe it just hangs at "waiting for device", i've fiddled with this stuff every which way and just cannot get fastboot.exe to see the phone. i've tried switching up the usb ports on this computer, but haven't had the opportunity to try a second computer. you've let me know i'm going in the right direction at least, if i have the same results on a second machine i'll pursue the issue further.
thanks again
wookie
WookieInHeat said:
thanks for the reply someguyfromhell. i've tried every "android adb interface" driver under the sun for the S1 fast boot device that appears in the windows device manager when i put the phone in fastboot. when i try to send any command with fastboot.exe it just hangs at "waiting for device", i've fiddled with this stuff every which way and just cannot get fastboot.exe to see the phone. i've tried switching up the usb ports on this computer, but haven't had the opportunity to try a second computer. you've let me know i'm going in the right direction at least, if i have the same results on a second machine i'll pursue the issue further.
thanks again
wookie
Click to expand...
Click to collapse
You need to unlock bootloader, if you want to install CM ROM. Arc S can only have bootloader unlocked via official method, there you can also download the correct driver which you need.
http://unlockbootloader.sonymobile.com/
Someguyfromhell said:
You need to unlock bootloader, if you want to install CM ROM. Arc S can only have bootloader unlocked via official method, there you can also download the correct driver which you need.
the bootloader is already unlocked, as i said, the phone has CM7 on it currently.
Click to expand...
Click to collapse
Hello wonderful helpful android wizards out there! I humbly seek your help.
I recently purchased an unlocked HTC M8 AT&T and had it unlocked so I could use my prepaid carrier (Simple Mobile). I have two issues I would like help with:
1) I cannot get a gps lock at all. I have made sure the device is in high accuracy mode and I have tried downloading and refreshing aGPS data via the GPS status app.
2) I am trying to upgrade to lollipop using the provided RUU file on the HTC website:
http://www.htc.com/us/support/htc-one-m8/news/
I am currently running 4.4.2. I was hoping that upgrading to the latest firmware might solve my GPS problem as a bonus, though I obviously want lollipop anyway to just generally be up to date. HTC sync manager works fine, but when I run the RUU file, it says the phone is not connected. I have tried the PB99IMH solution posted here that seemed to work for many people:
http://forum.xda-developers.com/show....php?t=1928439
The roadblock I have hit is that I cannot copy the zip file onto my Android. I keep getting the error "The device has either stopped responding or has been disconnected." I can copy other file to the phone just fine. I tried fiddling with the permissions of the file, but I honestly don't really know what I'm doing with those.
So those are my problems. I would greatly appreciate any assistance.
While in fastboot/hboot mode. Is your device recognized?
Where you have adb installed just open up a command prompt and do "fastboot devices" ... If your device's serial number shows up then it's being recognized. If not then your drivers are not installed or not recognized.
Tachi91 said:
While in fastboot/hboot mode. Is your device recognized?
Where you have adb installed just open up a command prompt and do "fastboot devices" ... If your device's serial number shows up then it's being recognized. If not then your drivers are not installed or not recognized.
Click to expand...
Click to collapse
Thank you for your response.
I never explicitly installed adb. I have sync manager on my computer, and I can see adb.exe in my processes. I tried to open up the command prompt and typed "fastboot devices" while my phone is in fastboot usb mode and nothing showed up. When I tried to run the RUU file while the phone was in fastboot, i never got beyond the "verifying information on your android phone. please wait..." part.
EDIT: I would also like to point out that sync manager doesn't recognize my phone in hboot or fastboot, thought it does recognize it normally.
semantik said:
Thank you for your response.
I never explicitly installed adb. I have sync manager on my computer, and I can see adb.exe in my processes. I tried to open up the command prompt and typed "fastboot devices" while my phone is in fastboot usb mode and nothing showed up. When I tried to run the RUU file while the phone was in fastboot, i never got beyond the "verifying information on your android phone. please wait..." part.
EDIT: I would also like to point out that sync manager doesn't recognize my phone in hboot or fastboot, thought it does recognize it normally.
Click to expand...
Click to collapse
It not being recognized while in the bootloader via the HTC Sync app is normal.
You could flash an RUU from the phone itself. Simply copy the rom.zip to your sdcard and go into the bootloader it'll see it and flash aslong as its named properly.. ie 0PB6IMG.zip or something in those lines.
To get the rom.zip while the RUU is open go into your task manager and right click the ruu process and go to file location. The only zip in there thats ~2Gbs is the rom.
Tachi91 said:
It not being recognized while in the bootloader via the HTC Sync app is normal.
You could flash an RUU from the phone itself. Simply copy the rom.zip to your sdcard and go into the bootloader it'll see it and flash aslong as its named properly.. ie 0PB6IMG.zip or something in those lines.
To get the rom.zip while the RUU is open go into your task manager and right click the ruu process and go to file location. The only zip in there thats ~2Gbs is the rom.
Click to expand...
Click to collapse
Ok, i finally got the update to work, but I am still having GPS issues. Any ideas?
I am also having GPS issues. Everything else on the device works fine, it just never finds any satellites. Any help or updates would be nice.
I'm having GPS problems as well. I'm on CM12.1. It used to work fine, but I've been playing with it trying to get LTE to work, and somewhere in there, my GPS stopped locking.
First I must say, I searched all over the internet for answer to this problem. None of the topics I read had matched my problem.
I want to unlock my bootloader so I can flash custom recovery and get root access.
When I want to access the bootloader ("adb reboot bootloader"), in my phone all goes fine (I see on my phone the Fastboot instructions, etc). The problem is in my computer that fastboot won't recognise my phone anymore. When I want to get the device-id, fastboot is stuck on "waiting for all devices". When I want to see the list of devices, ("fastboot devices"), I get nothing, wether my phone is on bootloader mode or not.
I installed all the LG drivers, including the ADB one. I am in USB debugging mode, and I disabled OEM protection.
Android version is Lollipop.
I need help on this matter, thanks in advance.
notrium dweller said:
First I must say, I searched all over the internet for answer to this problem. None of the topics I read had matched my problem.
I want to unlock my bootloader so I can flash custom recovery and get root access.
When I want to access the bootloader ("adb reboot bootloader"), in my phone all goes fine (I see on my phone the Fastboot instructions, etc). The problem is in my computer that fastboot won't recognise my phone anymore. When I want to get the device-id, fastboot is stuck on "waiting for all devices". When I want to see the list of devices, ("fastboot devices"), I get nothing, wether my phone is on bootloader mode or not.
I installed all the LG drivers, including the ADB one. I am in USB debugging mode, and I disabled OEM protection.
Android version is Lollipop.
I need help on this matter, thanks in advance.
Click to expand...
Click to collapse
not all phones can be unlocked.. search for g4 list of bootloader unlock youll see the list if yours isnt there you cant . only root 5.1 no twrp.
raptorddd said:
not all phones can be unlocked.. search for g4 list of bootloader unlock youll see the list if yours isnt there you cant . only root 5.1 no twrp.
Click to expand...
Click to collapse
I know mine can be unlocked. I actually can get to the bootloader via ADB. The problem is that fastboot won't recognise my phone afterwards. (I believe it's the european version of the H815 model, and according to one-click-root app, my phone can be safely rooted. Also my Lollipop version is 5.1.)
There are other few issues also:
Fastboot won't recognise my phone, even if the phone is not in bootloader mode.
Windows will recognise all of the LG related drivers including the ADB related driver, while the phone is powered on normally.
However, it fails to do so, in bootloader mode. I see non working driver in Windows 7 Device Manager, under "Other Devices" by the name "Android" with yellow exclamation mark. Nothing else.
Still looking for advice...
notrium dweller said:
I know mine can be unlocked. I actually can get to the bootloader via ADB. The problem is that fastboot won't recognise my phone afterwards. (I believe it's the european version of the H815 model, and according to one-click-root app, my phone can be safely rooted. Also my Lollipop version is 5.1.)
There are other few issues also:
Fastboot won't recognise my phone, even if the phone is not in bootloader mode.
Windows will recognise all of the LG related drivers including the ADB related driver, while the phone is powered on normally.
However, it fails to do so, in bootloader mode. I see non working driver in Windows 7 Device Manager, under "Other Devices" by the name "Android" with yellow exclamation mark. Nothing else.
Still looking for advice...
Click to expand...
Click to collapse
am sorry i cant help ive nver unlocked mine..
Still looking for suggestions, people...
I have the same problem, adb detects my phone but fastboot does not. Same Phone btw
Still no solution until now ? I have the same problems
My device is H815
Hi !
I have had this problem too...solved with strong battle to understand myself...
My solution : when you have installed driver ,when your phone go to fastboot mode and the pc don't want to reconize the phone : on the pc on windows go to harware manager (config panel) and you can see in theory "android" with a "?" ==> you have to install manually the driver by searching somewhere on the harware list "android adb interface " (i don't remember where it is) ==> your phone wil be reconized ! And you will have the 2 lines of ID on the adb comand interface....and follow the tutorial...
I have read hundreds of issues with driver problems when it comes to windows.
Please try Linux instead. There are live distributions like Ubuntu available. Install it on USB stick and start from there.
No driver issues anymore. Just works.
.
@steadfasterX it need some knowledge for to use Linux OS for adb thingsv (unlock bootloader ,instal TWRP,rom,apps...etc...) ? maybe you can do a small tutorial for to help ?
For windows i have found these pictures for an eventual help (see ZIP on attach file)
@Loulou-13 , now i can see my device-id - solved -
but now have another problems, my imei is not match with my device-id ...
my device is H815
yes...i know i have sent an answer too late ... but my solution is one of this problem and eventualy can be useful for other people.
for your new problem ,what happen ? .......have you enter the corect number ,without space or other ?
Loulou-13 said:
@steadfasterX it need some knowledge for to use Linux OS for adb thingsv (unlock bootloader ,instal TWRP,rom,apps...etc...) ? maybe you can do a small tutorial for to help ?
For windows i have found these pictures for an eventual help (see ZIP on attach file)
Click to expand...
Click to collapse
Well there are hundreds of guides out there just use google...
adb and fastboot working the same way under Linux so there is no need to have a specific guide for linux.
I haven't tested that guide here but it looks very good as a starting point:
http://forum.xda-developers.com/showpost.php?p=44739402&postcount=1
As said there are other maybe better guides but Google will tell you.
.
@steadfasterX thank for your link ,it's useful for people who have problem and read this thread
It's not for me .... i have my bootliader unlocked ,twrp...( and this fabulous Imperium MM rom !!!! )
So when I originally got my OP3 and rooted it, installed a recovery and installed SuperSu, I had basically no problems. Installed drivers I found on here and never had an issue. Today I found a guide on the OP forums to disable doze which I apparently need to do since certain notifications aren't working right. I plugged my phone in and tried to follow the instructions, listed here under push notification issues
https://forums.oneplus.net/threads/...3-guide-solutions-e-t-c.448097/#post-14886949
When typing in adb devices, my device shows offline. I have done numerous things to try and fix the issue which I will try to lay out here. Initially I didn't install adb or the drivers as the guide suggests, since I had already done that - but after things not working I did try that and that didn't help. Still receive the "offline" next to my serial number device. The device works fine, and I can see it and transfer files to it just fine in the MTP mode. I have also tried to "revoke" permissions like described in the youtube guide I found here https://www.youtube.com/watch?v=eSApv8NXqD4
However that didn't work either. I should note that even after revoking permissions and turning usb debugging on and off again, the phone never asks me to authorize my computer as it does in that guide. In fact I don't believe it ever asked me to authorize my computer even when I first got the device. I don't know if that is part of the issue or not. I have also used a different adb version since somewhere I found that you needed to use the newest version. The version I had was 1.32 and I found the newest here on the forums here http://forum.xda-developers.com/showthread.php?t=2317790 that it was 1.4 as the newest. That adb returns the same results.
I should also note that the guide I linked from oneplus never actually tells me to put the phone into fastboot mode to execute the command, so I tried it initially booted up, and then in fastboot thinking it was supposed to be executed there, however in fastboot mode the phone is not seen at all. adb devices returns nothing, and booted it returns offline mode. Please help me
Nobody?
Have you tried some of the suggestions on https://stackoverflow.com/questions/14993855/android-adb-device-offline-cant-issue-commands? I'm not really sure what the situation is like on Windows but first I'd ensure you've installed the latest official Android SDK just to rule out an issue with the version of ADB you're using. You could also try using ADB over WiFi.
Apart from that, you can probably get by without ADB for now. Just run the commands in a terminal emulator on the device and/or create an init script.