Develop Bugs

Fastboot does not work but ADB does

Hey guys,
The power button on my phone stopped working this morning (without water damage). I'm preparing the phone to return to Samsung warranty, and in the process of reseting to stock and re-locking the OEM I noted that the phone does not respond to fastboot commands in the bootloader despite this working on the same system a week ago, no change in drivers or anything else. I installed PDAnet, still broken on Win 7 although I can reboot with adb.
I then tried this on OSX, again I can reboot with ADB, but the phone is unresponsive in fastboot.
I have three working hypotheses and I'm hoping someone can help me:
a) in some process of flashing my phone and being an uninformed n00b maybe I flashed something I shouldn't have or used some combination of partial fastboot flashes I shouldn't have. has this happened to anyone else?
b) whatever hardware damage knocked out the power button might have partially knocked out the bootloader
c) I just have really bad luck with driver set up and I just happened to mess up two different computer driver configurations but the phone is fine. to this end, I am setting up another Win 7 system fresh on a virtual drive as I'm typing, though I have little faith it will be different

update: fastboot commands didn't work on the other windows 7 virtual system, although adb reboot bootloader did
freaking a this is annoying.
i have a fully stock ROM and radio, anybody to know how to flash a new recovery image and lock the bootloader without accessing fastboot? Just have to get this ready to go back to Samsung so they can fix their own hardware mess ups.

they are 2 different drivers.

As much as I don't like using/recommending the Galaxy Nexus Toolkit (only because I feel it's better to actually learn everything you're doing), it's the easiest way I've found to get the Fastboot drivers installed.
http://forum.xda-developers.com/showthread.php?t=1392310

Thanks guys for your comments.
I've tried Android SDK drivers, PDANet, Universal Naked Driver, and now the one click toolkit mentioned above, some on three different operating systems (Win 7, Win 8, OSx) on 32 and 64 bit.
The wierdest part is that under device manager, no device shows up when the phone is in fastboot, no is there any noise or any recognition of the device being connected at all. It is completely, 100% silent. (again, ADB works when the phone is booted).
I recognize that this may not be possible, but does anyone know how to flash a recovery image without being in the bootloader mode?

If fastboot isnt working like it should, and you are sure it isnt user error, then take it for warranty.
Sent from my i9250

yeah fastboot + the power button (which was defunk in clockwork mod) are back online again, dunno for how long. agreed seems like a hardware/warranty issue.

Recoveries can be flashed with ROM Manager assuming you have SuperUser permissions, but otherwise you or the toolkit need fastboot working.
Sent from my Galaxy Nexus using xda app-developers app

[Q] pc recog in fastboot mode but not in normal boot. help

Hello ..
So yes, as the title says.
I realized that pc doesnt recognize my phone in normal boot mode.
Am using dark paranoid 2.521 toro, with franco kernel r298.
Ofc the fast charge is off, nd the cable plus usb port of the pc is fine.
Funny thing is that my pc can recognize my phone in fastboot mode. This tells me my phone's usb port aint broke either.
Yet whenever I turn my phone on, wont charge and pc wont detect it.
I tried to change the governor from interactive to ondemand, along with the IO scheduler from deadline to noob, yet nothing happened.
Can anybody please help me?

Are you trying to get adb or MTP access? What is the operating system on your PC?

.
Either one. Mtp mostlikely.
Pc or even charging off from portable battery pack aint working until I turn my phone off...
I am uskng windows 7 64 bit but also tried in 32bit pc, which ended up in not working.

"most likely?"
there are a couple of threads that discuss these usb issues. use search.

update your drivers? I've had something like this before, so I manually uninstalled my Samsung drivers and reinstalled the current ones using the GNex ToolKit.

update your drivers? I've had something like this before, so I manually uninstalled my Samsung drivers and reinstalled the current ones using the GNex ToolKit.
Click to expand...
Click to collapse
I did, I did update my drivers, but phone just go dead on the normal boot. I think something is cutting the USB coneectivity during the boot precessing..

sqjzb said:
I did, I did update my drivers, but phone just go dead on the normal boot. I think something is cutting the USB coneectivity during the boot precessing..
Click to expand...
Click to collapse
Have u checked on Device Manager to c if the phone is there. It should say something like Samsung or MTP if recognized by Windows, if not it should say Android 4.0(I think) with a yellow or red symbol.
Sent from my Galaxy Nexus using xda premium

[Q] cant enable usb debugging, fastboot doesnt work

I have a Nexus 7 2013 that wont boot. USB Debugging was not enabled. At this point, I am just trying to wipe the machine with a stock image, but I am having trouble.
I have installed the sdk and drivers (so many drivers!)
Recovery mode fastboot does not recognize the device.
ADB recognizes the Nexus, but I cant seem to get it to do anything with it.
e: failed to mount anything.
I have read through so many forum threads that I'm just overwhelmed, and they all seem to require the machine being in USB debugging mode before any changes can be made.
Please help or tell me what pertinent information I have omitted.
Thank you

I think USB debugging only matters in ADB, which is when the device is actually booted into Android OS. You probably want fastboot, which is a different "application" and set of commands in a command prompt.
Code:
fastboot devices
Does that give you anything when the tablet is in fastboot mode? It should list the serial number of the device, similar to "adb devices" does. If not, it could be drivers, or another issue with the device.
Have you tried unlocking the bootloader? This will induce a factory reset of the current firmware version, which may allow you at least boot normally and take any available OTA updates.

Hello,
fastboot devices lists nothing, while adb does show the serial number.
I have used so many tutorials and a couple of toolkits that now I have no idea what is happening with my drivers.
Unlocking the bootloader to force a factory reset sounds amazing, but all the information I can find says I need to have USB debugging enabled to do so. I can not boot into the system to enable it.
Is there a way to force a reset without USB debugging?
Thank you

Usb debugging is irrelevant. Forget about it, it's only used when the system is booted.
You need to get fastboot devices to recognize the tablet.
Uninstall any and all toolkits and drivers. Redownload the sdk. Boot to the bootloader and plug it in, the drivers should install automatically. If not install the google usb drivers from the sdk manager in the sdk.
Try fastboot devices again. If it doesn't work try a different usb cord/port/computer.
You are in the bootloader when running this command right? Not the recovery? I think with the tablet off it's volume down and power. The screen that says start in big green letters at the top and has device info in the bottom left is what you want.
Edit: Did you boot to recovery and select the options to wipe data and cache? Sometimes thats all thats needed.

Also booting to recovery and performing a factory reset may be sufficient.
ADB will indeed function in recovery. I don't think you have to enable USB debugging to get this to work though.

Are you typing fastboot devices while booted in recovery? Typing fastboot devices while in recovery or booted into Android will do nothing.

hello, thank you for your advice. I now get the nexus seen by fastboot (and win 7) but have hit a wall. The last time I had my computer and the nexus together was weeks ago, when I my computer BSOD during what I thought was a simple flashing of the the stock image, but turned out to be hours of the nexus saying it was erasing personal data ... and then crash. I have replaced and added fans so my cpu wont overheat again, so please offer ideas why "fastboot flashall" or "fastboot flash image-razor-kot49h" wont work.
I appreciate all responses, and believe the answer is either very simple or a catastrophic hardware failure. I base this belief on what is left in my head after smashing it into the wall so many times over the last month when my wife asks me, "have you fixed my nexus yet, or do I need to figure out a way to buy a new one next month?"
I am stuck at unlocking the bootloader. I have highlighted "yes" on the nexus and pressed power and my command window says "erasing user data." It has said this for the last 18 hours. This is the second computer I have tried this on, using 3 different usb cables. What am I missing?

helpmynexus said:
hello, thank you for your advice. I now get the nexus seen by fastboot (and win 7) but have hit a wall. The last time I had my computer and the nexus together was weeks ago, when I my computer BSOD during what I thought was a simple flashing of the the stock image, but turned out to be hours of the nexus saying it was erasing personal data ... and then crash. I have replaced and added fans so my cpu wont overheat again, so please offer ideas why "fastboot flashall" or "fastboot flash image-razor-kot49h" wont work.
I appreciate all responses, and believe the answer is either very simple or a catastrophic hardware failure. I base this belief on what is left in my head after smashing it into the wall so many times over the last month when my wife asks me, "have you fixed my nexus yet, or do I need to figure out a way to buy a new one next month?"
I am stuck at unlocking the bootloader. I have highlighted "yes" on the nexus and pressed power and my command window says "erasing user data." It has said this for the last 18 hours. This is the second computer I have tried this on, using 3 different usb cables. What am I missing?
Click to expand...
Click to collapse
I have the same problem .. Have You reslove it?

bikicviki said:
I have the same problem .. Have You reslove it?
Click to expand...
Click to collapse
This may help...it may not. But I was having issues getting my bootloader unlocked also when I started on mine. My remedy was to
1 plug in the nexus into the usb
2 I run Linux so it gives me choices on what to do with newly plugged in usb device. I noticed two identical choices to mount device. Choosing one just mounted the camera for some strange reason. I closed that window, then chose the other choice to mount device, the window opened and my full internals were there in the window
3 from a terminal I just wrote a prompt: fastboot oem unlock
and for some reason, it unlocked.
To sum it up I'm convinced it has something to do with how the device gets mounted. At least on mine anyway.
As for activating developer from a terminal I read it could be done but never tried it myself, if you want here's the link for the info, read the second answer down.
https://stackoverflow.com/questions/47510232/is-there-any-adb-command-to-enable-developer-options
Also check out the fastboot manual for some other things to try, you never know some may work in your situation at a terminal prompt
man fastboot
---------- Post added at 07:12 PM ---------- Previous post was at 06:57 PM ----------
Troops42 said:
This may help...it may not. But I was having issues getting my bootloader unlocked also when I started on mine. My remedy was to
1 plug in the nexus into the usb
2 I run Linux so it gives me choices on what to do with newly plugged in usb device. I noticed two identical choices to mount device. Choosing one just mounted the camera for some strange reason. I closed that window, then chose the other choice to mount device, the window opened and my full internals were there in the window
3 from a terminal I just wrote a prompt: fastboot oem unlock
and for some reason, it unlocked.
To sum it up I'm convinced it has something to do with how the device gets mounted. At least on mine anyway.
As for activating developer from a terminal I read it could be done but never tried it myself, if you want here's the link for the info, read the second answer down.
https://stackoverflow.com/questions/47510232/is-there-any-adb-command-to-enable-developer-options
Also check out the fastboot manual for some other things to try, you never know some may work in your situation at a terminal prompt
man fastboot
Click to expand...
Click to collapse
Tried to edit but anyway:
After re..re, rereading your post, and responces. Have you tried the old fashioned way
Hold down the (down volume) button at the same time the (power) key.."Together" If you get anything that pops on your screen let go of the keys, one tap at a time tap the volume up or down key ONLY, until it says (START), its in green type. if you get there you should be ok, to move along

Bricked? Thanks LineageOS

So I tried to migrate from CM to Lineage (which ive already done on my N5) and while formating my data due to encryption, my tablet is completely F'd in the A.
If I had it connected to my PC i could see it power on and would show 30 or so unknown partitions, but my screen would be blank.
I ended up deleting all of the partitions but now i cant even see the device at all.
Since i cant get anyhting on the display and since i cant even get to fastboot, i have a feeling in screwed and need to go get a new board for it now... or just a new tablet i guess, but i rly liked my & and id hate to be w/o it over something stupid like this...
Can anybody else at least confirm or possibly have another idea?
I dont even get the charging animation with it off either...

carnagex420x said:
So I tried to migrate from CM to Lineage (which ive already done on my N5) and while formating my data due to encryption, my tablet is completely F'd in the A.
If I had it connected to my PC i could see it power on and would show 30 or so unknown partitions, but my screen would be blank.
I ended up deleting all of the partitions but now i cant even see the device at all.
Since i cant get anyhting on the display and since i cant even get to fastboot, i have a feeling in screwed and need to go get a new board for it now... or just a new tablet i guess, but i rly liked my & and id hate to be w/o it over something stupid like this...
Can anybody else at least confirm or possibly have another idea?
I dont even get the charging animation with it off either...
Click to expand...
Click to collapse
Do you have ADB set up? if not, now may be a good time and through ADB try download a factory image.

carnagex420x said:
If I had it connected to my PC i could see it power on and would show 30 or so unknown partitions, but my screen would be blank. I ended up deleting all of the partitions but now i cant even see the device at all.
Click to expand...
Click to collapse
Connect it to a PC again and check the USB mode your N7 is in.
If it is, or if you can make it work in, USB mode 9006 then follow this post. The linked N7 image is from my 32GB Hynix but you can use it to restore boot on any eMMC and adjust it later. While you do not see the partitions anymore, you may be able to access the device to restore the image.
If it is USB mode 9008 then your only recovery option is JTAG or hardware programming of the eMMC chip.
Good luck, it is still fixable :good:

the device still appears completly lifeless however i am able to get the device to show up as
Code:
Bus 002 Device 064: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
but im not sure how to go about getting fastboot yet, i get that i can dd an image to it i guess but im pretty sure i only have the 16GB not the 32, wjich i cant seem to find.
After playing with it for a couple hours and reading the entire Unbricking thread, the spot im stuck at now is the 9008-9006 mode switch. I have the QPST software and drivers working right and i get the NAK error but i follow the directions and cant get it into 9006 mode...

LineageOS update of May 24 2017 bricked my Nexus 7 2013 also.
Can't even use the Nexus Root Toolkit to recover. Always get stuck in the Google symbol.
Can enter into recovery, but it takes 15 minutes. And the directory structure showed is all empty.
Rebooting it show some errors saying that the partition table is empty.
"OEM Device Info" of NRT shows that the equipment is now locked also.
Have no idea of what to do. Can't even install the SO again.
There is a thread on "general" that seems to deal with related problems:
https://forum.xda-developers.com/nexus-7-2013/general/rd-thread-trying-to-solve-ota-brick-t3117495

ramon.hugo said:
LineageOS update of May 24 2017 bricked my Nexus 7 2013 also.
Can't even use the Nexus Root Toolkit to recover. Always get stuck in the Google symbol.
Can enter into recovery, but it takes 15 minutes. And the directory structure showed is all empty.
Rebooting it show some errors saying that the partition table is empty.
"OEM Device Info" of NRT shows that the equipment is now locked also.
Have no idea of what to do. Can't even install the SO again.
There is a thread on "general" that seems to deal with related problems:
https://forum.xda-developers.com/nexus-7-2013/general/rd-thread-trying-to-solve-ota-brick-t3117495
Click to expand...
Click to collapse
When you can boot into recovery you are good to go. Use a pendrive and an otg cable and flashthe rom from pendrive.

Already tried that ... Also impossible.

Try this way,
Connect to Computer
Use NRT then pess root, your Device will restart in TWRT then you can put the file in and reinstall.

You may be running into flash wear issues. This device is about 4 years old at this point, a similar thing started happening to the 2012 models. Don't blame the ROM, blame the NAND chip in your tablet.

I have a busted USB port so prefer to recharge via wireless. Sometimes wireless charging keeps disconnect and reconnecting if it's on so I need to shut it off.
I did that and now it just hangs at the Google screen as well.
If I hold Vol down I dont get twrp but the general bootloader. Any choice seems to just reboot it.
I think I'm screwed as well.
Prior to this my pc doesnt detect via USB at all, just charges it.

Question [Solved] POCO F3 - Unable to unlock bootloader/fastboot no device

Hey there,
sorry for the undescriptive title, but I really don't know what is going on. I received my new Poco F3 on tuesday and since then I am trying to make some progress with unlocking the bootloader. I went through the steps:
- enable developer options
- download the Flash tool from Xiaomi
- enable OEM unlock and USB debugging
- registering a new Mi account
- pairing the Mi account from the phone in Dev-Options/Mi-Unlock Status (while on data with the same SIM and phone number used in my Mi Account).
I tried it from various computers and with different cables. Somehow the phone is not detected when in Fastboot mode. Here are some things I tried (tbh - I really can't recall everthing I tried):
- installing ADB tools in Linux and Windows
- Using the XiaoMiTool V2
- installing various USB driver found in the net on WIndows
- Using an older version of the Mi Unlock Tool from their website (4.5.813.51) as there where USB drivers included.
- "unpaired" and paired my phone with the Mi Account, also detached the Mi account from the phone and reattached it.
I know that I won't get any unlock at the moment as the wait period is not over. However I expect at least that I see an error message indicating that I need to wait for X-hours longer or something. But in the various tools the phone doesn't even appear when in fastboot mode.
Using Linux and XiaoMiTool was the "most successful" method - but even here the fastboot mode was not recognized. I just got a "Service Token invalid" message - which looked like it is caused by not having a connection to the fastboot mode.
At least I now figured out that it is totally normal that devices in fastboot have "d00d" as idProduct, because this was what changed when I attached the phone in normal mode (idProduct=4ee7).
Running "adb devices" in fastboot also doesn't show anything (Windows and Linux).
I fear that I may ended up in a trap like with my first phone - the Samsung S2 i9100g - that was the "same" but different from the "normal" S2. Is there something known? Using CPU-Z I see that the CPU seems to be at least a SM8250 - so that looks promising. The Model is M2012K11AG (alioth_eea) if that helps anything.
Any hints, tips, suggestions on how to proceed are welcome I am flashing my phones since almost 10 years, so I should be able to make this work here too, right?
Thanks

"I know that I won't get any unlock at the moment as the wait period is not over. "
You managed to start the unlock timer using the tool though?
I think at first I had the same worry of it not being recognized (adb devices never worked) but as it did show in both the unlock tool and the flashtool and managed booting (fastboot boot x.img) to twrp.img recovery also after. (you load fastboot with power - & volume?)
Plugging it in when booted and/or in fastboot should result in some connected sound. I trust you checked in the system devices if the device got installed/recognized?

sathariel74 said:
Hey there,
sorry for the undescriptive title, but I really don't know what is going on. I received my new Poco F3 on tuesday and since then I am trying to make some progress with unlocking the bootloader. I went through the steps:
- enable developer options
- download the Flash tool from Xiaomi
- enable OEM unlock and USB debugging
- registering a new Mi account
- pairing the Mi account from the phone in Dev-Options/Mi-Unlock Status (while on data with the same SIM and phone number used in my Mi Account).
I tried it from various computers and with different cables. Somehow the phone is not detected when in Fastboot mode. Here are some things I tried (tbh - I really can't recall everthing I tried):
- installing ADB tools in Linux and Windows
- Using the XiaoMiTool V2
- installing various USB driver found in the net on WIndows
- Using an older version of the Mi Unlock Tool from their website (4.5.813.51) as there where USB drivers included.
- "unpaired" and paired my phone with the Mi Account, also detached the Mi account from the phone and reattached it.
I know that I won't get any unlock at the moment as the wait period is not over. However I expect at least that I see an error message indicating that I need to wait for X-hours longer or something. But in the various tools the phone doesn't even appear when in fastboot mode.
Using Linux and XiaoMiTool was the "most successful" method - but even here the fastboot mode was not recognized. I just got a "Service Token invalid" message - which looked like it is caused by not having a connection to the fastboot mode.
At least I now figured out that it is totally normal that devices in fastboot have "d00d" as idProduct, because this was what changed when I attached the phone in normal mode (idProduct=4ee7).
Running "adb devices" in fastboot also doesn't show anything (Windows and Linux).
I fear that I may ended up in a trap like with my first phone - the Samsung S2 i9100g - that was the "same" but different from the "normal" S2. Is there something known? Using CPU-Z I see that the CPU seems to be at least a SM8250 - so that looks promising. The Model is M2012K11AG (alioth_eea) if that helps anything.
Any hints, tips, suggestions on how to proceed are welcome I am flashing my phones since almost 10 years, so I should be able to make this work here too, right?
Thanks
Click to expand...
Click to collapse
I'm you're saver !!!!
Download this : https://www.mediafire.com/file/lv98wac50a2dexz/MiFlash20210226.zip/file
Extract it launch the exe then u see drivers like qualcomm,google... Then click on install when u see a pop up in chinese close all see if fastboot is recognizing you're device
ALSO LATEST ADB AND FASTBOOT VERSION : https://dl.google.com/android/repository/platform-tools-latest-windows.zip

Mother_Teresa said:
You managed to start the unlock timer using the tool though?
Click to expand...
Click to collapse
Well, I don't see any timer in the tool. However the new flash tool doesn't seem to promising (that batch one). Also in XiaomMiTool I don't see any timer. So maybe the registration is already messed up?
Mother_Teresa said:
think at first I had the same worry of it not being recognized (adb devices never worked) but as it did show in both the unlock tool and the flashtool and managed booting (fastboot boot x.img) to twrp.img recovery also after.
Click to expand...
Click to collapse
Well, this one does not work for me as it is locked...so I suppose this is a dead end at the moment. Tried this in Linux (I am more comfortable with).
Mother_Teresa said:
(you load fastboot with power - & volume?)
Click to expand...
Click to collapse
Yes, I actually do that usually (besides of the automatic Fastboot loading from XiaoMiTool).
Mother_Teresa said:
Plugging it in when booted and/or in fastboot should result in some connected sound. I trust you checked in the system devices if the device got installed/recognized?
Click to expand...
Click to collapse
Yes, it gives some connected sound in both modes (normally booted - can even mount the phone storage - and in fastboot). Not sure about the device correctly installed when in fastboot - I tried to follow some threads/videos on that but somehow it looked different for me.
X0PIRAT3 said:
I'm you're saver !!!!
Download this : https://www.mediafire.com/file/lv98wac50a2dexz/MiFlash20210226.zip/file
Extract it launch the exe then u see drivers like qualcomm,google..; Clique on install when u see a pop up in chinese close all see if fastboot is recognizing you're device
ALSO LATEST ADB AND FASTBOOT VERSION : https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Click to expand...
Click to collapse
Thanks! I may try those out (not sure if I can make this during the weekend).
EDIT: The drivers from @X0PIRAT3 really did the trick! I just installed them and tried it. Now it says 165 hours wait time (it maybe 3 hours that I last tried to rebind my account during trouble shooting!). Thanks a lot to you 2! You are really genius!

sathariel74 said:
...
Thanks! I may try those out (not sure if I can make this during the weekend).
EDIT: The drivers from @X0PIRAT3 really did the trick! I just installed them and tried it. Now it says 165 hours wait time (it maybe 3 hours that I last tried to rebind my account during trouble shooting!). Thanks a lot to you 2! You are really genius!
Click to expand...
Click to collapse
Yay, well done.
I kept default MIUI and rooted with Magisk (install this in Magisk app to fix safetynet pass).
More details here.

Well, I can endure a lot but not MIUI - its not my kind of android. I will go for LineageOS initially I think Lets see what surprises come up, luckily I still have my 5T.

sathariel74 said:
Well, I can endure a lot but not MIUI - its not my kind of android. I will go for LineageOS initially I think Lets see what surprises come up, luckily I still have my 5T.
Click to expand...
Click to collapse
Not to bash etc but what is so bad?
I installed my preferred launcher (Nova) and it works for being a familiar front-end.
Options and tweaks are mostly there these days in the settings (fe. flashlight on double-press) and if not there is root.
is it bloatware? (if so, can we fix it? )
Lineage is of course a safe bet and I probably end up trying some but I need some encouragement .
BTW: beware the Miu Flash tool not enabling 'lock device' when flashing.
edit: how to use smileys. Now it seems super happy but without it seems so serious....

Well, besides of lack of trust (which is most likely just my issue), I really dislike that "all at startscreen" quite a lot. And yes, those 20-30 apps that I was able to delete plus the 20 apps I would like to delete are another thing showing me that this ROM is not for me. Especially that memory manager stuff that enables your "high performance game experience" is a sign to better stop using MIUI. There are also some bugs (strange behaviour I saw/felt - can't even really describe) I didn't like.
I like to manage my stuff myself, even if this is more work. But I somehow know how its "glued" together. So LineageOS is what I like. Or some of the other AOSP ROMs available.