Database Info

[Q] Fastboot problem

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

[Q] Help, Xoom locked on red M screen, device not recognized

Hi, partial noob here, I've rooted a different Xoom but this one was stock US wifi only, MZ604.
Amazon appstore was restarting continually so I navigated away but left it open. Later in the day when I tried to reopen it, it crashed my Xoom. Now it is locked on red M screen. I can soft resest and get to "starting fastboot protocol support" but when connected to pc with oem usb cable, it doesn't show up under adb devices. If I adb reboot bootloader, it says device not found. I have checked my drivers, they show up under "Mot Single ADB Interface" with file version 1.1.0.0 and file version 1.7.6001.0 (two drivers). I have adb and fastboot in my SDK_tools folder, what am I missing?
Thanks for any help,
Peter

pepond said:
Hi, partial noob here, I've rooted a different Xoom but this one was stock US wifi only, MZ604.
Amazon appstore was restarting continually so I navigated away but left it open. Later in the day when I tried to reopen it, it crashed my Xoom. Now it is locked on red M screen. I can soft resest and get to "starting fastboot protocol support" but when connected to pc with oem usb cable, it doesn't show up under adb devices. If I adb reboot bootloader, it says device not found. I have checked my drivers, they show up under "Mot Single ADB Interface" with file version 1.1.0.0 and file version 1.7.6001.0 (two drivers). I have adb and fastboot in my SDK_tools folder, what am I missing?
Thanks for any help,
Peter
Click to expand...
Click to collapse
Are you rooted with custom recovery or stock? After soft reset when the "M" first appears count to three and press the volume down button, hopefully you will see "android recovery". If you do press the volume up button to enter recovery and you could do a system restore from it. I'm thinking maybe you didn't have "usb debugging" turned on in developer settings, does it show a pop up on your computer when you plug in the xoom where you can browse it's file contents? If so save any photos or important docs and do a system restore like I explained earlier.

Same woes here
solved

[Completed] Help! LG G4 bootloop, can't get into recovery or bootloader/fastboot mode

So I was following the instructions here.
http://forum.xda-developers.com/g4/development/stock-h815-20a-stock-images-kdz-t3232282
and my G4 is in a bootloop after step 7 (reboot into twrp). Gets a second or two into the animated LG logo then resets.
I want to get back into fastboot mode or recovery so I can flash again, but no button combo does anything, (p+d or p+u, held, or with the short gap as in many descriptions). If I hold all three buttons, it shows imei and a barcode, but I can't go anywhere from this screen.
It's boot loader unlocked as per LG official unlock, and still says so in tiny writing top left when first booting.
Can anyone give me some tips on how to get this thing back into fastboot mode? I have a mac with adb and fastboot working well.
Thanks,

milesritzy said:
There were three methods outlined in the post, but i think this should help you...
In order to successfully complete this method a computer will be required. A connection between your smartphone and your PC will also have to be ensured, so on your LG G4 gain developer rights and then check USB debugging – go to “menu – settings – about phone” and tap several times on built number and then access “menu – settings – developer options”. Also, on your PC flash Android SDK by following: install Android SDK on Windows or set up ADB on MAC OS X / Linux. Don’t forget to charge your handset before going any further and then apply:
Connect your LG G4 with your computer via USB cable.
On your PC access the Android SDK folder.
There, open a command prompt window: press and hold Shift keyboard key and then right click on any blank space.
In the cmd window you have to execute the following command: “adb reboot bootloader”.
Enjoy.
Conclusions
Click to expand...
Click to collapse
I'm familiar with using adb to reboot into bootloader, That's how I got this far. But it only works if you have a working OS with developer options for adb to connect to.
Unfortunately I don't have a working OS, or working anything else.

Hi,
Try posting your question here:
G4 Q&A, Help & Troubleshooting
The experts there may be able to help.
Good luck!

"adb devices" works, but "fastboot devices" doesn't

I've just got a new Z5 and am trying to install LineageOS, like I did on my dearly departed HTC m8.
I've got the android platform tools installed, and the device shows up if I use "adb devices". "adb reboot bootloader" appears to work - it shuts the device down then the LED goes blue (the documented behaviour of being in fastboot mode). However, "fastboot devices" lists nothing.
*#*#SERVICE#*#* indicates bootloader unlock is allowed, I've got dev mode enabled, I've got my unlock code ready and waiting... No fastboot mode though. Any ideas?

Hang on a sec.
It's just occurred to me that something else might be wrong. Booting into "fastboot" is the same as entering recovery mode, right? Well, when I try doing it, all I get on my phone is the blue LED. Just a black screen. That seems obviously wrong, because it should be displaying Sony's built-in recovery mode stuff, right?
While we're at it, I've just tried again on my work computer, holding volume up and inserting a USB cable. The computer recognised and installed "S1Boot Fastboot", and I can see it in Device Manager under "Other devices". However, the status is "The drivers for this device are not installed. (Code 28) There are no compatible drivers for this device."
This was the same on my home machine. I tried installing Sony's drivers, and the Android drivers, but each time I pointed Windows at the directory I'd unzipped to it would just say that it couldn't find any drivers there.
e: #$%&!
I'm trying with Sony's "Emma" tool. It says to hold vol-down and connect the phone, which gives a green light (not a blue one), but says "this phone is locked". But I've unlocked it! Sony's instructions at the address listed in the error message say to enable debugging then select "OEM unlocking" from the dev options, which I have done! What gives?

Got it!
I Can't post the URL due to low number of posts, but I found what I needed from the question on the android Stack Exchange called "Windows 10 Fastboot Driver". I grabbed a tool called Zadig, which was able to install a driver for Fastboot, so I could flash recovery.
Right. Now to get set up! Woo!

Thank you!
Hyperlynx said:
Got it!
I Can't post the URL due to low number of posts, but I found what I needed from the question on the android Stack Exchange called "Windows 10 Fastboot Driver". I grabbed a tool called Zadig, which was able to install a driver for Fastboot, so I could flash recovery.
Right. Now to get set up! Woo!
Click to expand...
Click to collapse
Thank you! I had the same problem. The device showed up as "Android" and I couldn't install the drivers.
You can find instructions and the download link here: https://android.stackexchange.com/questions/129174/windows-10-fastboot-driver

"Waiting for device" after flashing kernal and rebooting device

Hi all,
sorry if there is plenty of these threads already floating around but wasnt able to find a relevant one to my problem. I'm hoping someone here might be able to help.
This is the primary XZ rooting guide i have been following, with other supplimentary guides 1 & 2
These have been my steps:
- Managed to successfully update fastboot driver with "android_winusb.inf-file" from 'Google USB Driver' within android studio.
- Unlocked bootloader
- Installed AndroPlus Kernel sucessfully "fastboot flash boot boot.img"
Now went to reboot device as stated by instructions (mistake) and now the device is not recognized in cmd "waiting for device". I've replugged the usb in multiple ports and the device shows up as "android" in devices and printers. I go to update the android "SOMC Flash Device" to the platform tools directory but makes no difference in cmd. Still "waiting for device". In Device Manager there is no sign of the device either.
When the phone is turned on it shows your device has been "unlocked and cant be trusted will reboot in 5 seconds" then proceeds to xperia logo and freezes. With no recoveries theres not much options.
Is there a way to continue from here or even return to a previous state? It seems like i hit a brick wall. Please help

MugenG said:
Hi all,
sorry if there is plenty of these threads already floating around but wasnt able to find a relevant one to my problem. I'm hoping someone here might be able to help.
This is the primary XZ rooting guide i have been following, with other supplimentary guides 1 & 2
These have been my steps:
- Managed to successfully update fastboot driver with "android_winusb.inf-file" from 'Google USB Driver' within android studio.
- Unlocked bootloader
- Installed AndroPlus Kernel sucessfully "fastboot flash boot boot.img"
Now went to reboot device as stated by instructions (mistake) and now the device is not recognized in cmd "waiting for device". I've replugged the usb in multiple ports and the device shows up as "android" in devices and printers. I go to update the android "SOMC Flash Device" to the platform tools directory but makes no difference in cmd. Still "waiting for device". In Device Manager there is no sign of the device either.
When the phone is turned on it shows your device has been "unlocked and cant be trusted will reboot in 5 seconds" then proceeds to xperia logo and freezes. With no recoveries theres not much options.
Is there a way to continue from here or even return to a previous state? It seems like i hit a brick wall. Please help
Click to expand...
Click to collapse
Installed adb SystemWide?
adb drivers are Installed corrcetly? , better to reinstall them.