I was trying things on my Lenovo A7-10F and ended up rebooting in fastboot mode. Pressing power doesn't do anything (even for a whole minute..); with other buttons : nothing either. Non removable battery of course, and adb won't detect the device (tried to install different drivers).. What can i do? It's heating quite a lot..
In order to replicate how it is when the battery is taken out just allow it to drain completely. That might help with the reset of it. Hope you get more help here!
Yes that's the last thing I'd like to do though since it's heating a lot and it can last for +10 hours..
did it work by just letting the battery out?
Download, extract and install this Lenovo driver to your PC
Code:
lenovo-forums.ru/index.php?app=core&module=attach§ion=attach&attach_id=39195
Download and install Minimal ADB and Fastboot (search it on xda or google).
Run it.
Connect your device to PC using USB cable.
On the command prompt type: fastboot devices
It will verify your device. If fastboot is configured properly, your device code will appear.
Then you just have to type: fastboot reboot
and your device will reboot to system
Hope it works. Good luck
Related
hello,
I'm hoping someone here can help me sort out my current problem.
I've been trying to root so I can install the latest ICS port, but having problems at the Fastboot screen.
I apologize in advance if some of the references/names I'm using are incorrect.
So, I had originally unlocked my Nexus S sometime early this year. When I restart the phone, the "unlocked" lock picture shows up under the "Google" words, and when I go into fastboot mode, the Lock State is Unlocked.
I'm running 2.3.6 right now on the Tmobile version of the phone.
When the phone is on (not in fastboot mode), I can execute ADB commands and the device is recognized. As soon as I go into fastboot it isn't.
I'm running 64bit Win 7, and I have gone through the various threads that have listed this issue, and installed PDA Net drivers and still there is no solution.
In Fastboot mode, while connected to computer under device manager, it shows up under Universal Serial Bus Controllers as an Unknown Device... I'm unable to update any drivers for it, and even when I try to manually update the drivers by going to the PDANet drivers it does not allow it.
When the phone is on in regular mode in device manager it shows up as Android Phone and within that it has a listing called Android Composite ADB Interface.
As mentioned above, when phone on in regular mode everything is detected.
I installed clockwork app from market, assuming that the phone was "rooted" based on the "unlock state" in fastboot mode, but it immediately says that phone needs to be rooted because it was unable to find SuperUser file etc etc.
I've spent the better part of a few days trying to figure this out by checking all sorts of links, but I haven't found a solution. The main issue is that the phone is not being recognized when in fastboot mode when connected by USB. And I'm unable to install the proper drivers for fastboot mode.
Hopefully this makes sense, and someone can provide some insight.
Thanks in advance!
I'm not positive about this but couldn't you adb push the su binary and apk? I don't own the Nexus but I would think since its unlocked you could just push the files. If this would work I would think it's just a temporary solution to allow superuser permission. As I understand it, fastboot is the preferred method for the Nexus.
Sent from my PG06100 using Tapatalk
Did you try a fastboot command like fastboot devices?
Don't know if this applies to you but I had a similar sounding problem when trying to root my Nexus S where everytime I booted into fastboot mode I had an error message at the bottom of the screen saying something like 'fastboot status-fail Invalid command' and so I couldn't use any fastboot functions.
To get around it I used this one-click root . For some reason I got an error message halfway through for whatever reason and it wouldn't complete the root for me but it booted me into fastboot without receiving the error message and then once I was in I went and rooted manually.
The CWM is out of date on that site though (possibly the super-user zip too) so I replaced them with the latest versions and popped it in my dropbox for you, if you wanna try it out.
http://dl.dropbox.com/u/47770734/One-Click-Nexus-S.zip
Edit: just had a little look through the bat script and the initial commands that got me into fastboot properly is (with your phone in debugging mode):
adb start-server
adb reboot bootloader
Click to expand...
Click to collapse
So you could try that first if you wanna go through manually.
Know that you can't run adb command while in fastboot mode. Boot into your CWM and then you can start an adb shell and you'll be able to push all the files you want and execute all the commands you need.
Fastboot mode is for running fastboot indeed. Try 'fastboot devices' while you're in the bootloader and see if devices pop up. If not, you really have to figure out your drivers issue. Maybe remove the device completely from your PC (including driver files) and reinstall it using the PDAnet drivers.
Greetz
Hi few days ago i've tried to install the sixth rom on my htc one s , i push the rom on the htc one s with adb push , but it failed , so i try another time and my pc didn't recognize my htc one s ,also in device manager on windows it doesn't appear and when i enter in fastboot doesn't appear fastboot USB... i've tried with 2 cable , 2 pc with different OS but no working , i have installed htc drivers , adb and fastboot driver , google usb driver but no work
My htc one s is stopped from 5 days , i hope someone help me
neverdie951 said:
Hi few days ago i've tried to install the sixth rom on my htc one s , i push the rom on the htc one s with adb push , but it failed , so i try another time and my pc didn't recognize my htc one s ,also in device manager on windows it doesn't appear and when i enter in fastboot doesn't appear fastboot USB... i've tried with 2 cable , 2 pc with different OS but no working , i have installed htc drivers , adb and fastboot driver , google usb driver but no work
My htc one s is stopped from 5 days , i hope someone help me
Click to expand...
Click to collapse
Someone help me please i don't know what do i do
neverdie951 said:
Someone help me please i don't know what do i do
Click to expand...
Click to collapse
It's either your phone is not working correctly with fastboot usb or your computer.
You can try a live CD of linux/Ubuntu - this might work.
i am screwed too! omg!~
so i killed my phone... sounds like the same thing that happened here... i am praying u find an answer ... cuz i need one too... if anyone has any info they can give me on how to make my htc one s boot... that would be great... i can install rom, well one rom... viperv3.1.3... and it says its successful.... but then i reboot and it just sits there on the boot menu thingie... not even bootlooping just stuck... i dont know too much about how to fix this phone... and idk wat i can do to fix it... you should see the amount of time ive put into tryin to fix it in the last 4 days... omg. i need my phone back ... lol... i was hoping that someone made a backup... as my drive formatted itself and clearly formatted my backup also.... so i can try to just restore it... .is this an option. i hope so .
808phone said:
It's either your phone is not working correctly with fastboot usb or your computer.
You can try a live CD of linux/Ubuntu - this might work.
Click to expand...
Click to collapse
I tried right now with ubuntu and no work...what i must do , there's no connection between my htc one s and my computer the only connection is the charging of my phone please help me
neverdie951 said:
I tried right now with ubuntu and no work...what i must do , there's no connection between my htc one s and my computer the only connection is the charging of my phone please help me
Click to expand...
Click to collapse
That is so weird. So you cannot get it to show fastboot usb?? If so, then I don't know what you can do. You need to have communication to restore with RUU. I know some people do JTAG, but considering you can buy a used One S for around $120, it may not be worth fixing. Most people I know charge around $75 for fixes so I may not be even worth it. Hopefully someone with more knowledge can jump in this thread.
808phone said:
That is so weird. So you cannot get it to show fastboot usb?? If so, then I don't know what you can do. You need to have communication to restore with RUU. I know some people do JTAG, but considering you can buy a used One S for around $120, it may not be worth fixing. Most people I know charge around $75 for fixes so I may not be even worth it. Hopefully someone with more knowledge can jump in this thread.
Click to expand...
Click to collapse
It's really strange beacuse with this metod it works a few times , but i hadn't enough time to install the rom
Before you begin with your computer:
- go into recovery
- advanced
- reboot into recovery
If it reboots straightaway, you're ready to go. But it might wait, and offer you to root your phone. Do that, otherwise it won't work!
I would also restart the computer, just for a clean start. I also wiped my phone once again (factory reset).
On your Mac:
- make sure your rom (*.zip) is inside the platform-tools folder (this is inside the android sdk, where adb is)
- your phone should be disconnected and in recovery mode
1. open Terminal
2. type: cd (press space)
3. pull the platform-tools folder onto the terminal, press enter (this is here: /android/sdk/platform-tools)
4. type: ./adb kill-server (enter)
5. type: ./adb usb (enter) -> now it should say that "error: device not found"
6. connect your phone to the computer with the usb
7. type: ./adb devices -> it should show your phone, recovery mode
8. in your phone enter sideload mode (either in advanced, or in install zip option)
9. type: ./adb devices -> check if your phone is connected in sideload mode
10. type: ./adb sideload + <full name of the rom, including .zip, without brackets>
It should work, for me everything went perfectly.
Power + Vol Down pressed together gets you access to the F1's limited recovery mode.
Power + Vol up does not get you into the bootloader.
When you connect the phone to your PC it automatically loads its USB drivers to the PC with your consent.
ADB can see the phone once the USB drivers are installed and the phone is connected via USB cable.
ADB DEVICES provides the serial number of your phone.
ADB REBOOT RECOVERY gets you into the recovery mode mentioned above.
ADB REBOOT BOOTLOADER simply reboots the phone.
FASTBOOT can't see anything.
FASTBOOT DEVICES doesn't yield serial number.
Other FASTBOOT commands sit "waiting for device".
So FASTBOOT just does nothing useful. A google search shows that this behavior is known and people think that using different drivers overcome the problem, but I tried a number of driver solutions with no success. I just think that they've closed the Oppo F1 up rather tightly.
-----
ETA: Just heard elsewhere from a semi-official source that FASTBOOT has been disabled on the F1.
I just saw this "Decision by Oppo: No Bootloader/Fastboot access for Oppo Phones starting 2016" from here > http://forum.xda-developers.com/r7-plus/help/decision-oppo-bootloader-fastboot-t3348114
If this is true, the F1f will be our last oppo. It's not a big issue for the F1f as it's my wife's phone but I will avoid locked phones on principle now. Even Huawei are making it hard to unlock bootloader so my Mate 7 could be our last Huawei.
Guys anybody tell how to flash 'magictricks' zip to unlock boot loader and to flash twrp recovery safely...
I'm week in commanding adb devices and fastboot so I need steps,help will be thankful.
Sent from my F1f using XDA-Developers mobile app
friends. I want to flash myphone (flash tool) windows 7 but do not see it. even I reinstalled windows 7, but did not see. last driver installed on the MTK what to do - I do not understand
agreed. another computer, another cable, another driver (for flash tool)
So I'm seeing a ton of posts of folks not able to get fastboot to see their devices. I've done some tinkering around and found a set of drivers that work fine for both ADB and Fastboot. (Attached)
Uninstall any ADB drivers you have on your system. Easiest way is to plug your phone in, go into device manager, right click your phone and select uninstall and check the box that says to remove the driver as well.
Then download this package, extract, simply run install.exe as admin. Don't panic, it doesn't do anything visual.
Now plug your phone in and see if adb works, you may need to authorize the computer again on the phone so make sure it's unlocked.
Reboot into bootloader and check if fastboot sees the phone by using
Code:
fastboot devices
If not then go back into device manager and right click on your phone, select update driver, let me select one from a list and you should see "Fastboot interface (Google USB ID)". Select this one.
Check fastboot without unplugging with the same command. Check and see if you can send commands to the phone by using for instance,
Code:
fastboot getvar unlocked
If the command fails, simply plug the phone into a different USB port and the same Google driver should install again and you should be able to send commands to the phone. Alternatively, you can reboot the phone by tapping the battery out and starting it all over again.
Now she chooches.
Lemme know if you're still having problems.
bless up ??
Does this work for sprint variant?
im having problems...damn it i don't get this
---------- Post added at 03:19 PM ---------- Previous post was at 02:42 PM ----------
any help please?
Verizon variant here,
I cannot seem to get this dang V20 in the right mode
(I've seen a bootloader or two in my day):highfive::laugh::silly:
I have used the adb command (several times)
Code:
adb reboot bootloader
to get it into bootloader mode, alas it is to no avail since all the command does is send the phone into "Restart" mode; nor can I get fastboot to recognize it when it is in, what I believe to be , the bootloader for said LG V20 of the
Verizon persuasion!
Suggestions?
You need fastboot, not bootloader... To get it, turn off your phone, plug your LG cable into the computer, ( but not the phone yet) hold the volume down key for 5 seconds then plug it into your cable, do not release the button till your phone boots. It should boot into fastboot... Provided you have turned on USB debugging in developer settings (turn on oem unlock while you are in there too. (this is the way on the tmo V20 at least... If that doesn't work, I would use the dirty Santa guide
Sent from my LG-H918 using Tapatalk
Not sure how I finally got it working for my Verizon variant as I tried like four or five different ways, but someone should definitely make a video.. Perhaps I will since I think visuals are a good aid to go along with written instructions..
Thanks bro works
Very easy
With my t mobile v20
My phone shows as connected in adb devices. I can also get it to reboot bootloader, but once im there.. I cant issue any commands such as fastboot oem device-id. It gives me the dreaded waitng for any device.
can't manage to make this work for H990DS, i don't get the usual authorization window to the computer, only get the window to choose which USB mode (battery charge, file transfer, so on...) I'm trying to get adb to work to activate agressive Doze on Greenify app, any help?
Thanks
Vexamus said:
So I'm seeing a ton of posts of folks not able to get fastboot to see their devices. I've done some tinkering around and found a set of drivers that work fine for both ADB and Fastboot. (Attached)
Uninstall any ADB drivers you have on your system. Easiest way is to plug your phone in, go into device manager, right click your phone and select uninstall and check the box that says to remove the driver as well.
Then download this package, extract, simply run install.exe as admin. Don't panic, it doesn't do anything visual.
Now plug your phone in and see if adb works, you may need to authorize the computer again on the phone so make sure it's unlocked.
Reboot into bootloader and check if fastboot sees the phone by using
Code:
fastboot devices
If not then go back into device manager and right click on your phone, select update driver, let me select one from a list and you should see "Fastboot interface (Google USB ID)". Select this one.
Check fastboot without unplugging with the same command. Check and see if you can send commands to the phone by using for instance,
Code:
fastboot getvar unlocked
If the command fails, simply plug the phone into a different USB port and the same Google driver should install again and you should be able to send commands to the phone. Alternatively, you can reboot the phone by tapping the battery out and starting it all over again.
Now she chooches.
Lemme know if you're still having problems.
Click to expand...
Click to collapse
Perfect and Easy!!!! :good:
thx..ur ma angel
I can't find my phone in Device Manager.
this is great and works like a charm! thanks!
Thanks!
So here's the background: I have a OnePlus 6, which I had rooted previously. I accidentally updated it without first patching the boot image, so it's not rooted now.
In an attempt to root it again, I need to use fastboot. However, whenever I use
adb reboot bootloader
it reboots the phone to fastboot mode, as expected, but then
fastboot devices
displays nothing. I find this extremely strange, because I have used fastboot commands before on both my windows machine and on my Linux machine (though I recently switched distros and have a new installation on there, so it may be missing some driver or something).
I have tried looking for any necessary drivers (I saw that sometimes usb drivers are different from fastboot drivers, but I don't know if that's the case regarding OnePlus) but after installing everything I found, it still doesn't work.
I have also tried running adb as root (on Linux) and as administrator (on Windows) but neither worked.
I tried to use Tool All In One to root it for me, but it seemed to run into the same problem. It wouldn't detect the phone in fastboot mode.
I'm absolutely baffled as to why this may be; Anyone know why this happens or what I may do to fix it?
I had the similar issue last week when adb command of fastboot devices would not identify the device. I used the fastboot ROM method to reflash the stock rom and everything worked fine afterwards including fastboot devices command identifying the device correctly. Needless to say, it would delete everything on your phone. Here is the link:
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Good luck!!
Fastboot version
Update your fastboot, maybe it's an old version.
Also check your device manager and see if the phone is listed there. Sometimes it's necessary to disable driver signature check in Windows 10. Also install the driver before you use your commands - some users reported that for some reason the driver or connection is lost after windows reboot.
A) Check fastboot drivers/reinstall them (adb and fastboot use different drivers). You might want to check if there are unknown devices in your Windows device manager, or the name of the device once fastboot mode is engaged and you plug the cable
B) Plug it in another USB port (less likely to be the problem, since ADB actually works)