Hello,
After over an hour of searching for something similar, I figured I'd just ask...
I'm trying to set-up a phablet as a dedicated car informant. I've got most everything set-up to satisfaction. I ran the fastboot command "fastboot oem off-mode-charge 0" to have the phone boot on charge. This worked fine for the Medion (lenovo) life X6001 with 5.1.
Then I set-up the tasker to automate certain actions. All seemed fine; low battery parameters as a safety net, offline maps on boot, turns off when disconnected from power source, ect.
But... now that I've got the tasker doing what I want; the phone no longer turns on by itself when connected to power source. Seemingly reverted back to it's charging screen, I enter fastboot, run the command again, seemingly accepted; no dice. Ok, so it worked before I had set-up the tasker, so I assume the tasker has changed something. I start disabling the new flows individually to find the culprit and sure enough, a few shut-down and boot-ups later, apparently the auto-off on power disconnect throws the fastboot command out the window. Disabled the phone starts up when connected to power source.
Here's the kicker: after dicking with the phone to no avail, I discover that not only does the phone boot when it's off and finds a power source but it also boots when it's turned off and is disconnected from it's power source... How weird is that? Logically, a tasker shut-down on power disconnect would interfere with a command that also tells the phone to boot when disconnected.
Before this point I hadn't entered any other fastboot commands, so I couldn't have inadvertently given an unknown command. Fastboot oem off-mode-charge 0 seemingly makes this device boot on connect and disconnect.
All great and well, there are more than one way to skin a cat...yet I tried to reverse the command with fastboot oem off-mode-charge 1 but the command isn't recognized. So I tried fastboot oem off-mode-charge disable; this was a recognized command but doesn't toggle the command to off. I've tried all the different variations I can find with regards to oem off-mode-charge but nothing will restore the original function.
I've also tried to dump the bootloader to find the hidden commands, but the walkthrough
on this forum doesn't work with this device. I get into super user function just fine but # cd /dev/....... isn't a recognized directory....
I know this is kind of a long post. I hope someone will bare with me who can shed some light. Thanks in advance.
Bump.
No one willing to share an idea?
Am I asking my questions incorrectly?
Bummer...
There's a forum named Connected Car on XDA, try asking over there
Thanks for your reply. I can ask in the car forum, I assumed being that the specific question doesn't have anything to do with the actual installation that it belonged here...
I've read all the posting rules and guidelines and I'm still not a star on choosing the correct forum.
Are you looking for fastboot commands?
Mwmcc said:
Hello,
After over an hour of searching for something similar, I figured I'd just ask...
I'm trying to set-up a phablet as a dedicated car informant. I've got most everything set-up to satisfaction. I ran the fastboot command "fastboot oem off-mode-charge 0" to have the phone boot on charge. This worked fine for the Medion (lenovo) life X6001 with 5.1.
Then I set-up the tasker to automate certain actions. All seemed fine; low battery parameters as a safety net, offline maps on boot, turns off when disconnected from power source, ect.
But... now that I've got the tasker doing what I want; the phone no longer turns on by itself when connected to power source. Seemingly reverted back to it's charging screen, I enter fastboot, run the command again, seemingly accepted; no dice. Ok, so it worked before I had set-up the tasker, so I assume the tasker has changed something. I start disabling the new flows individually to find the culprit and sure enough, a few shut-down and boot-ups later, apparently the auto-off on power disconnect throws the fastboot command out the window. Disabled the phone starts up when connected to power source.
Here's the kicker: after dicking with the phone to no avail, I discover that not only does the phone boot when it's off and finds a power source but it also boots when it's turned off and is disconnected from it's power source... How weird is that? Logically, a tasker shut-down on power disconnect would interfere with a command that also tells the phone to boot when disconnected.
Before this point I hadn't entered any other fastboot commands, so I couldn't have inadvertently given an unknown command. Fastboot oem off-mode-charge 0 seemingly makes this device boot on connect and disconnect.
All great and well, there are more than one way to skin a cat...yet I tried to reverse the command with fastboot oem off-mode-charge 1 but the command isn't recognized. So I tried fastboot oem off-mode-charge disable; this was a recognized command but doesn't toggle the command to off. I've tried all the different variations I can find with regards to oem off-mode-charge but nothing will restore the original function.
I've also tried to dump the bootloader to find the hidden commands, but the walkthrough
on this forum doesn't work with this device. I get into super user function just fine but # cd /dev/....... isn't a recognized directory....
I know this is kind of a long post. I hope someone will bare with me who can shed some light. Thanks in advance.
Click to expand...
Click to collapse
In order to obtain fastboot commands. I assume you must have installed the ADB and fastboot program on your computer (ADB setup version 1.3.exe etc) once you install this program there would be a folder under your C:\ drive named ADB.
Open the folder after installing the driver
Press window button + R to bring the Run dialogue box
Type cmd and press enter if Win XP or "if you use Windows 7 OS right click a blank space while holding shift"
Open command prompt here.
if XP then, command prompt appears; use "cd" command in the command window to start the command from the open folder.
i.e. if command indicates C:\ Documents and Settings\ User etc change the command to open by typing "cd.." twice and then type "cd adb" all without quotes until your command starts in the folder where your adb and fastboot. exe files are present.
Now type " fastboot" without quotes in the folder C:\adb, the command would look similar "C:\adb\fastboot" without quotes to receive all fastboot commands and switches associated with this command; similarly adb commands and its switches when typing "C:\adb\adb" without quotes in the same folder.
Hope this information will resolve your issue,
Regards,
alza689
I appreciate your effort. Yes, I'm looking for device specific hidden fastboot commands. Unfortunately, this method only shows the basics and doesn't display the command needed to toggle fastboot oem off-mode-charge. The walk-through for dumping the bootloader provided on these forums didn't work for my device.
Thanks again.
Perhaps googling might help
Mwmcc said:
I appreciate your effort. Yes, I'm looking for device specific hidden fastboot commands. Unfortunately, this method only shows the basics and doesn't display the command needed to toggle fastboot oem off-mode-charge. The walk-through for dumping the bootloader provided on these forums didn't work for my device.
Thanks again.
Click to expand...
Click to collapse
Try various methods of google search, it might help! try fastboot commands and enter your specific device in the search, as I ran out of options to help you.
Regards,
689alza
Trust me, before I take the time to register on a forum and ask a question I've searched 'til near anxiety attack through google...
Thanks anyway.
Try this link, hope it helps you.
Mwmcc said:
Trust me, before I take the time to register on a forum and ask a question I've searched 'til near anxiety attack through google...
Thanks anyway.
Click to expand...
Click to collapse
http://www.xda-developers.com/how-to-discover-hidden-fastboot-commands/
Mwmcc said:
Am I asking my questions incorrectly?
Bummer...
Click to expand...
Click to collapse
Possibly you have already solved your issue from 2 years ago.
I suspect that you are using an OTG USB adapter.
Have you tried disconnecting it before shutting down the phone/tablet?
That was the only way I could prevent my tablet from rebooting by itself after installing the "fastboot oem off-mode-charge 0".
Related
I need to find a way to root my lg-h901 asap. The ways i found doesnt seem to work. When i do the adb command to unlock my bootloader it says waiting on devices and never continues on and i need root so i can use a call recording app due to legal issues. Any suggestions or ideas will be greatly appreciated
dillonorden said:
I need to find a way to root my lg-h901 asap. The ways i found doesnt seem to work. When i do the adb command to unlock my bootloader it says waiting on devices and never continues on and i need root so i can use a call recording app due to legal issues. Any suggestions or ideas will be greatly appreciated
Click to expand...
Click to collapse
There are call recording apps on playstore. Along with the rooting is so simple I did it the same day I got my v10 T-Mobile variant
dillonorden said:
I need to find a way to root my lg-h901 asap. The ways i found doesnt seem to work. When i do the adb command to unlock my bootloader it says waiting on devices and never continues on and i need root so i can use a call recording app due to legal issues. Any suggestions or ideas will be greatly appreciated
Click to expand...
Click to collapse
First things first, you don't need root to record your phone calls. Like Wadamean said, there are call recording apps in the play store. I personally use "Call Recorder ACR", but you can use whatever you prefer. Most call recorders won't require root access.
As for rooting, if you type the adb command and it says that it's waiting for your device, the most likely cause is that you do not have the proper drivers installed on your computer. An easy way to check this would be to type the command "adb devices" and make sure that your V10 appears under "List of devices attached". If you don't see your h901 device listed, your computer doesn't know that the V10 is connected, and it'll be difficult for your computer to issue commands to a device it can't see
Follow each step in this guide. That doesn't mean click this link, skip to the downloads, and then proceed to root like you've always done. It means click this link, READ THE POST, then once you have finished reading it, read it again to make sure you didn't miss anything. It will guide you through setting up adb with a universal driver. It will also guide you through doing things like enabling USB Debugging, which is required for issuing adb commands.
http://forum.xda-developers.com/tmobile-lg-v10/general/guide-how-to-root-lg-v10-easy-t3274699
If you are still having issues after reading this guide and FOLLOWING THE INSTRUCTIONS, post there to let them know where you're getting stuck at and someone will help you out.
Appreciate the advice i thought call recording was a root only feature so i do apologize for that inconvience guys
As far as rooting my computer does reconize the device ive ran the adb command to check and it did list it and i still got stuck. Ive installed the universal drivers so that may be where i messed up. Thank you for the link im going to try again tonight bc i want root
dillonorden said:
Appreciate the advice i thought call recording was a root only feature so i do apologize for that inconvience guys
As far as rooting my computer does reconize the device ive ran the adb command to check and it did list it and i still got stuck. Ive installed the universal drivers so that may be where i messed up. Thank you for the link im going to try again tonight bc i want root
Click to expand...
Click to collapse
No worries, that's why we're here :good:
If you can see your V10 listed on the ADB devices list, then something else is up. Make sure that USB Debugging and OEM Unlock are checked in Developer Options... What command are you getting stuck at?
Both options are checked in developers options. Ill type the oem unlock command and it reads waiting on device
dillonorden said:
Both options are checked in developers options. Ill type the oem unlock command and it reads waiting on device
Click to expand...
Click to collapse
Ahh, sounds like you aren't in fastboot mode. Make sure that your USB connection type is set to PTP rather than MTP or charge only. Before you issue ANY other adb commands, run "adb devices" and make sure that you see your v10. It should read something like this:
List of devices attached
LGH901blahblah device
Click to expand...
Click to collapse
See it on the list? Good. You should be able to run "adb reboot bootloader". At this stage, your phone should reboot to a mostly dark screen. Once in the bootloader, you should be able to run "fastboot oem unlock". Be forewarned that it can take a few minutes. If you see "waiting on device," you're either not in the right mode (your phone won't acknowledge fastboot commands if it's not in Bootloader mode) or the drivers on your computer are screwy and need to be reinstalled. If you can issue adb commands but not fastboot ones, you probably need additional drivers - more info here: http://android.stackexchange.com/questions/46142/fastboot-doesnt-see-device
This should get you started in the right direction, feel free to PM or post in the guide if you're still having trouble. :good:
ok so i followed the guide, reinstalled the LG drivers. and re setup the ADB system wide. I put my phone in usb ptp and ran command ADB devices. It listed my device, so i ran the ADB reboot bootloader and it rebooted. the screen i get is the LG boot screen but in the top left corner it shows fastboot mode and list the commands to unlock the bootloader. I run command fastboot oem unlock and I get the same waiting on device and waited an hour and got nothing. I even tried unplugging it restarting command prompt held the vol down button when i plugged my device back in to make it boot into FASTBOOT mode. i run the command fastboot oem unlock and still get nothing.
What am I doing wrong? I follow the guide to the very T and still get nothing. Could I possibly get someone to make a file with everything done and flash it using Odin? Im not new to this and dont understand why this V10 H901 is giving me so much trouble. Ive rooted a Motorola OG droid, Droid 2, Bionic, Samsung Note 2, 3 and Grand Prime and never had this much trouble. I really enjoy having root privileges but this is getting ridiculous but I also refuse to give up. If anyone can help me I would much appreciate it. Also Thanks to the ones who have tried helping me so far, this is why I enjoy XDA so much
ok i believe my device isnt being reconized while in fastboot mode. I tried going into fastboot mode by plugging my device in a PC while it was off and holding the Vol Down button and when I go into command prompt and run command fastboot devices nothing shows up. I really need to root this device so any help is appreciated
ok confirmed at 0130 hrs I am loosing connection in fastboot mode... What is the issue?
dillonorden said:
ok i believe my device isnt being reconized while in fastboot mode. I tried going into fastboot mode by plugging my device in a PC while it was off and holding the Vol Down button and when I go into command prompt and run command fastboot devices nothing shows up. I really need to root this device so any help is appreciated
ok confirmed at 0130 hrs I am loosing connection in fastboot mode... What is the issue?
Click to expand...
Click to collapse
Are you the administrator of the pc? What OS are you using?
I am administrator and im using windows 7 so i dont see where im having an issue at
Hello,
A friend of my asked me to install a new version on his iOcean X8 Mini.
After a few minutes into the process, I discovered that I couldn't modify anything at all.
Problems start occuring when I enter Fastboot via ADB (I power up the phone, connect it to PC, give it permission to use Android USB Debugging, then via 'adb rebeoot fastboot' I enter the Fastboot menu). Every command I enter here returns 3 dots just doing nothing. My command prompt is unusable after entering a command (for example 'fastboot oem unlock').
I've tried to push a ROM via ADB but this isn't working as well since it returns something like 'no permission' when trying to install, but I figured this was due to the locked bootloader.
Searched all over the internet for solutions, but so far nothing has really worked. What I somehow did mange to do is root the device (don't know if it was by default, I assume not), via RootGenius.
Anybody got any experience with this, and perhaps know some steps I can undertake to indeed unlock the bootloader of this phone?
Thanks in advance!
I have the Huawei Ascend Y300-0151 and am trying to unlock the bootloader, in which I cannot get through their website because it's really buggy and won't accept my information.
So these are the steps I've taken:
- Download SDK Manager and install platform-tools and Google USB Driver
- Boot my phone up and connect to the PC
- I can run the command 'adb devices' and my device shows with a unique ID.
- Boot my phone into recovery/download mode (purple screen).
- Connect my phone, the PC detects it.
- However, when I run the command 'fastboot devices', nothing shows up.
Yes, I have installed a driver for my device and it's now showing as Android Bootloader Interface.
I've run out of ideas and have been googling for answers for a very long time, but to no avail.
Any help would be greatly appreciated, thanks!
illquo said:
I have the Huawei Ascend Y300-0151 and am trying to unlock the bootloader, in which I cannot get through their website because it's really buggy and won't accept my information.
So these are the steps I've taken:
- Download SDK Manager and install platform-tools and Google USB Driver
- Boot my phone up and connect to the PC
- I can run the command 'adb devices' and my device shows with a unique ID.
- Boot my phone into recovery/download mode (purple screen).
- Connect my phone, the PC detects it.
- However, when I run the command 'fastboot devices', nothing shows up.
Yes, I have installed a driver for my device and it's now showing as Android Bootloader Interface.
I've run out of ideas and have been googling for answers for a very long time, but to no avail.
Any help would be greatly appreciated, thanks!
Click to expand...
Click to collapse
Given that your attempting to unlock the bootloader of your Huawei device, you should probably send an email to Huawei support requesting for your bootloader unlock code (thats what I did and they replied asking for my device information, and I gave it to them to which I then got my unlock code). For ADB to work you need to boot into fastboot mode, not recovery, then simply use the bootloader unlock code with the following command in cmd: fastboot oem unlock <insert your code here>
And then your done. Be cautious when unlocking your bootloader as you should make sure you have your developer options enabled and the "allow bootloader to be unlocked" option enabled as well.
LaserOP said:
Given that your attempting to unlock the bootloader of your Huawei device, you should probably send an email to Huawei support requesting for your bootloader unlock code (thats what I did and they replied asking for my device information, and I gave it to them to which I then got my unlock code). For ADB to work you need to boot into fastboot mode, not recovery, then simply use the bootloader unlock code with the following command in cmd: fastboot oem unlock <insert your code here>
And then your done. Be cautious when unlocking your bootloader as you should make sure you have your developer options enabled and the "allow bootloader to be unlocked" option enabled as well.
Click to expand...
Click to collapse
I have e-mailed them 2 weeks ago and they are not replying. You're meant to do it through their website, but as I've said, I supply the correct information and it either re-directs to a page that is not there or says I am not entering my information correctly when I've done it over and over again.
The purple screen is fastboot mode isn't it? Because that's the screen I'm entering the commands in, but it's not showing up. I cannot enter in a code for fastboot oem unlock because my device will not be recognized by fastboot in the first place.
So before I am to unlock my bootloader, I'm trying to get my device recognized by fastboot.
illquo said:
I have e-mailed them 2 weeks ago and they are not replying. You're meant to do it through their website, but as I've said, I supply the correct information and it either re-directs to a page that is not there or says I am not entering my information correctly when I've done it over and over again.
The purple screen is fastboot mode isn't it? Because that's the screen I'm entering the commands in, but it's not showing up. I cannot enter in a code for fastboot oem unlock because my device will not be recognized by fastboot in the first place.
So before I am to unlock my bootloader, I'm trying to get my device recognized by fastboot.
Click to expand...
Click to collapse
You can send them an email to get the unlock code, trust me, thats what I did. Maybe try contacting them via their support section of their site if you didn't do so last time.
By the "purple screen" do you mean the screen with options such as "HBOOT", "Fastboot", "Reboot" etc.? The "fastboot devices" command should work if it is recognised by the command "adb devices"
LaserOP said:
You can send them an email to get the unlock code, trust me, thats what I did. Maybe try contacting them via their support section of their site if you didn't do so last time.
By the "purple screen" do you mean the screen with options such as "HBOOT", "Fastboot", "Reboot" etc.? The "fastboot devices" command should work if it is recognised by the command "adb devices"
Click to expand...
Click to collapse
I'll give it a go again, thanks.
By purple screen, I mean holding down the power button and both volume control buttons and the screen boots into a purple screen. Just a purple screen, that's it. I can boot into two other modes by holding down the power button and the volume up button and another by holding the power button and volume down button. I don't have a boot mode that displays any options as you've listed above.
EDIT: I'm in fastboot mode now! It was the mode where you hold down the power button and volume down button. Hahaha. I'll let you know how I get on with unlocking the bootloader. Thanks for your help
No problem, if you found my replies helpful please press the thanks button! It is much appreciated!
Hi guys,
This Is my first post so I hope I do it correctly. As the title says I am having problems with fastboot on my Acer Iconia One 10 B3-A40. I have enabled developer settings on my device and turned on the setting to unlock OEM. The problem is when I try to run the tablet in fastboot mode to unlock the OEM through ADB commands. When connected to my computer and running the command "adb devices" it shows my device Id and that it is connected. I then run the command "adb reboot-bootloader" to which the tablet switches off and makes the chime that it was disconnected from the computer and makes another chime and connects back onto the computer, the screen on my tablet remains blank with no indication it is in fastboot mode. When I run the command "fastboot devices" my device id shows up again that it is connected. When I originally tried to flash a patched boot image of my stock firmware it went through the process and failed mid way through saying it couldn be done cos the device was locked. After that I googled a bit to see what to do so that’s when I realised OEM unlock was to be switched on in developer settings and also using ADB commands. After returning to fast boot mode I ran the command "fastboot oem unlock" the 3 dots come up on command prompt to show the process is going but nothing happens on my device. Nothing will happen if I press the power button or the volume down button but if I press the volume up bottom, on command prompt it shows OKAY and then the amount of seconds it took to complete, the time changes based on how quick or long i take to press the volume up button but the device remains locked. I have being trying to find a solution for days and have searched everything i could find before making this post. It would be greatly appreciated if someone could help.
I am on an older macbook pro running High Sierra. the phone I'm using is a Blu G5 running android 9. I have the developer options unlocked and oem unlocked and usb debugging checked. When i open my terminal i type cd and drag and drop the platform tools folder into the terminal window changing the directory to the folder containing the adb and fastboot files. I can use adb commands such as adb devices and get the serial number and it says devices. So far so good. Then i reboot the phone into the bootloader manually or using command adb reboot bootloader and the phone goes into fastboot mode. I know because it says it on top of the screen in white letters. Then i run into the problem fastboot commands don't work. If I type in fastboot devices nothing but a new command line shows up. When i type in any other command like fastboot device or fastboot oem unlock it says "waiting for any devices." I wait and wait but nothing happens. I have looked on the internet for a solution but all i find is that the driver may not deinstalled properly. I have tried manually installing fastboot driver and used sdk manager to install the fastboot driver and I have tried it using the terminal in android studio but no matter what when i try useing fastboot commands i get the "waiting for any device" message. Does any have a solution or could anyone recommend and forum for android development on MacOSX?
@DimDreams
Seems the Fastboot driver is invalid.
jwoegerbauer said:
@DimDreams
Seems the Fastboot driver is invalid.
Click to expand...
Click to collapse
I have literally tried like 10 different sdk tool downloads just platform tool download basically every thing i can find. By chance would you or anyone out there have a working driver for MacOSX 10.13.6? or link a guide that can help me figure this out. I have made a little progress with a forum on xda about fastboot on macs but i still just keep getting the waiting for any device message.
@DimDreams
May also be that the Fastboot Android mode is not available on the phone in question.
I've had similar issues before and noticed that fastboot mode works better via USB 2.0 than USB 3.0. Maybe check which port you're using and switch. ADB seems to work well either way, however. Hope that helped.
I just had this problem as well and I found this, what worked for me is first boot your phone into bootloader mode with
Code:
adb reboot bootloader
. While in the bootloader fastboot worked for me. Hope this helps someone!