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.
Related
Hi
I have got a hero on the cheap currently using an iPhone boot looking to move over.
The hero has a custom rom on it, I would liketo try others. Holding down the home button and powering on just leaves it with the G2 boot screen. Holding down back button and power brings me into fastboot USB. When connected to the mac I am unable to see the device / list it using adb devices. If I boot into the os and connect to the mac not mounting the sdcard I can see the device with adv devices.
I'm trying to install a recovery image, this is proving dificult with not seeing the device in fastboot.
Has anyone any thought/suggestions on to resolve? Or point me in the direction of some threads to read.
Tia
deano
use fastboot devices when in fastboot...
HI,
thanks for the reply, when in fastboot on the device I use fastboot which i have downloaded from the andriod site and put in my "tools" folder when trying to lash a recovery image it just comes back with a prompt saying "waiting for device"
thanks
just to make sure: you turn off the phone, then turn it on again while holding down BACK. this brings you to a screen with a white background and fastboot written somewhere. then you plug in the usb cable and execute "fastboot devices". if it still doesn't recognize your device then you got a problem somewhere, no idea where though. not sure if windows needs drivers or anything for fastboot to work correctly...
Yes that's correct.
Phone is recognize in everything other than when connected by fastboot.
Thanks for your input
I found this thread about my Prism
http://forum.xda-developers.com/showthread.php?t=1698905 post 5
I can press volup and power for 15 sec and get android recovery screen.
I can connect my phone to my laptop.
I can run "adb devices" and get List of devices attached: "20F3A........... recovery" so i think it sees it.
But when I run "fastboot reboot" (to test the connection) it says "waiting for device".
I think I have to give another command to adb, but don't know what.
If you can help, I'd much appreciate it!
KrisM22 said:
I found this thread about my Prism
http://forum.xda-developers.com/showthread.php?t=1698905 post 5
I can press volup and power for 15 sec and get android recovery screen.
I can connect my phone to my laptop.
I can run "adb devices" and get List of devices attached: "20F3A........... recovery" so i think it sees it.
But when I run "fastboot reboot" (to test the connection) it says "waiting for device".
I think I have to give another command to adb, but don't know what.
If you can help, I'd much appreciate it!
Click to expand...
Click to collapse
If the phone runs ADB, it's not in fastboot mode.
fastboot is a boot loader feature. ADB is a service at the operating system level. They are mutually exclusive.
Take to phone back to fastboot if it's what you want.
Code:
$ adb reboot-bootloader
kuisma said:
If the phone runs ADB, it's not in fastboot mode.
fastboot is a boot loader feature. ADB is a service at the operating system level. They are mutually exclusive.
Take to phone back to fastboot if it's what you want.
Code:
$ adb reboot-bootloader
Click to expand...
Click to collapse
Thanks! Please pardon my ignorance... I did:
Code:
adb devices
pause
adb reboot-bootloader
pause
fastboot reboot
After adb reboot-bootloader my phone changed from the recovery screen to the white tmo logo screen and hung.
fastboot reboot still says waiting for device...
EDIT Okay, I think I've figured out that, from power off, volup+power=recovery screen , and voldn+power=fastboot screen(white with tmo logo).
But I can't do anything from that fastboot screen. The computer recognizes it when I USB plug it, but it still says waiting for device.
EDIT: It appears I have a driver for adb, but no driver for fastboot, or just plugging the powered off phone in to usb.
fixed.
<deleted>
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!
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".
Hi guys,
In the past days i've been troubling my head with trying to unlock the bootloader on my lenovo tb-x103f, but cant seem to enter fastboot mode
I've been using this guide as reference, among other searches from all around, trying to work around this, but cant really seem to come to the bottom of this.
from cmd
adb recognizes my device
"adb reboot bootloader" tablet just boots into the startupscreen
"fastboot devices" somehow "confirms" that im in fastboot, even tho Im acctually not (right?)
"fastboot oem unlock-go" finishes, and says its successfull, but nothing happens (obviusly, since its not acctually in fastboot mode)
from there it just sits there, and nothing happens. have to reboot it myself, either via cmd or the button
why is it not entering fastboot mode? is there any fix for this?
This is getting really frustrating as I just wanna root the tablet and most likely install lineageOS, or some other custom ROM..
thanks in advance
If you can reboot it with a command than you are connected in fastboot mode. It sounds like you have unlocked you tablet. Enter fastboot mode through adb again and try "fastboot oem device-info"