Database Users

[Q] Fastboot on Stock 4.4.2?

I got an N7 about a month ago on sale and the first thing I did was unlock the bootloader. I decided I was going to use it as a "learning" tablet. (I'm still in learning mode, with aspirations of dipping my toes into development - that's a ways away, though.) I flashed TWRP followed by a couple of roms, and then I decided I was going to test my ability to flash a factory image. So I flashed 4.4 (this was last week before the 4.4.2 images went up). And since I was on the back on the OTA path, I figured, "I have an unlocked bootloader. What's the worst thing that could happen if I took this update?" So I did.
And now I'm confused. If I remember correctly, with 4.2.2 (what it came with out of the box), the bootloader had an option to run in "fastboot mode." In 4.4.2, my options are basically Dead Android screen or (if I power+vol up):
Reboot system now
Apply update from ADB
Wipe data/factory reset
Wipe cache partition
Fastboot stopped recognizing my tablet (adb still works, though not in recovery - I didn't think it was supposed to, so I'm surprised to see it as an option). I know there were issues in the past with the USB drivers on x64 machines, but I've tried on both 32-bit XP and 64-bit Win 7 and both machines will recognize that there is an N7 when booted normally, but say there are issues with the drivers when booted into recovery. I searched and saw people using pdanet as a workaround for installing the USB drivers, but those posts were largely from 2011/2012 timeframe - I have the latest version of Android-SDK and thus the latest (I think) USB drivers, so I'm at a loss. Did Google/Android do away with Fastboot in KitKat? Even so, ADB doesn't recognize my tablet in recovery, so even if I wanted to sideload something I can't - did Asus release newer USB drivers that I should be using?
Any help anyone can provide would be greatly appreciated.
Thanks!
miss_sticks

miss_sticks said:
I have the latest version of Android-SDK and thus the latest (I think) USB drivers, so I'm at a loss. Did Google/Android do away with Fastboot in KitKat?
Click to expand...
Click to collapse
Are you sure to have updated all the drivers for your N7 after update of your SDK?
Weird thing about N7 is that one sometimes needs to re-installi all the drivers after flashing of another firmware. I've flashed a factory image (4.3) via fastboot on two N7s within the same hour. First N7 had 4.2.2 before, After flashing 4.3 on it, I took another N7 with 4.2.0 and- I had to re-install the drivers.
I never had such a situation with Samsung devices.
Just to make sure you're doing proper ADB prompts (I see you can get this far on your own):
Code:
adb
adb devices
[I]List of devices attached
[B]<your device's serial number should now be diplayed here> [/B][/I] device
adb reboot-bootloader
fastboot devices
[I]the following output should be returned at this point
[B]<your device's serial number should now be diplayed here>[/B] [/I] fastboot
If on the place in this code where bold letters are your device serial No doesn't appear, you have a driver problem (it isn't installed properly)
Sorry for posting ADB/fastboot prompts, I don't know which orders have you done.

tetakpatak said:
Just to make sure you're doing proper ADB prompts (I see you can get this far on your own):
Code:
adb
adb devices
[I]List of devices attached
[B]<your device's serial number should now be diplayed here> [/B][/I] device
adb reboot-bootloader
fastboot devices
[I]the following output should be returned at this point
[B]<your device's serial number should now be diplayed here>[/B] [/I] fastboot
If on the place in this code where bold letters are your device serial No doesn't appear, you have a driver problem (it isn't installed properly)
Sorry for posting ADB/fastboot prompts, I don't know which orders have you done.
Click to expand...
Click to collapse
D'oh! Thank you so much for your help! I kept doing "adb reboot recovery" not "adb reboot-bootloader." Once I did that, everything was fine. I'm going to the corner to hang my head in newbie shame now. (But at least I'm now successfully running TWRP again.)

miss_sticks said:
D'oh! Thank you so much for your help! I kept doing "adb reboot recovery" not "adb reboot-bootloader." Once I did that, everything was fine. I'm going to the corner to hang my head in newbie shame now. (But at least I'm now successfully running TWRP again.)
Click to expand...
Click to collapse
OK, cool. Don't be ashamed, one just has to learn it
From that point on, (as you are in fastboot mode) your each prompt must begin with
Code:
fastboot (.....)
instead of "adb"

Fastboot connects with USB id 0000:0000

Hey Everybody!
I do have the following problem:
About a year ago, my Zuk Z1 lost both IMEIs. At that time I didn't know much about Android, TWRP, ADB, Qualcomm diagnostics ports etc... I learned as I went along on my journey to restore my modem connections. Unfortunately, while I tried different things I flashed one or more wrong images onto my Z1. At that time I gave up and put the phone away.
Recently, I dug it up again and while I do now know a little more about the inner workings of this phone and Android in general, I cannot get the diagnostic port 0x9008 or even the vendor ID 0x2b4c to show up under my PC.
Symptoms:
- when in Fastboot, the device registers as "unknown" usb device in windows (and as 0000:0000 in linux)
- I can set the device to register as 0x05c6 0x902d when booting into Android (NucleaROM V3.0.0 [6.0.1]), going to terminal and issuing "setprop sys.usb.config rndis,diag,adb" as root (via the terminal command "su"), but that port results in an error ("failed to enter edl mode") when trying to flash the recovery CM12.1 via QFIL (from this tutorial: androidbrick.com/lenovo-zuk-phones-qfil-roms-unbrick-guide/ )
- I can still access the phone from windows via adb (I can connect via "adb shell")
- I can still flash roms via TWRP (version 3.0.2-0)
I am about to try using the "dd" command to try to manually write the files (e.g. boot.img, emmc_appsboot.mbn, NON-HLOS.bin, etc...) from one of the recovery roms I have ("cm-12.1-20150903-EXPERIMENTAL-YOG4PAP25I-ham-signed-factory-f68f53c14c") to the partitions listed in the "partitions.xml" file therein. (I cannot use TWRP to install this rom, because it seems to be not an update (?) and there is no "META-INF/com/google/android/update-binary" file...)
My question is now: Does using "dd" to write the partitions manually work (I don't want to completely break the partitions, so I would like to have an opinion from someone who has more knowledge in this than me... )? If so, what would I need to do (e.g. under the TWRP terminal the partitons seem to be read-only, as "dd" there gives me "permission denied"; how and where do I proceed: from within Android under terminal or is there a way to do that from TWRP (terminal)? how do I remove write protection? etc.)?
If the "dd"-way does not work or if there is a better way (remember: fastboot does not work) how else can I restore the affected partitions (e.g. via "adb"? or a completely different way?)?
Do you need any other infos (command-outputs, etc.)?
Thanks for any help! I am happy about any hint you may give me!
Best regards,
ts101

"Waiting for any devices" with Moto G4

Excuse me for my bad English. I am new on this Forum. Please help me, I have a big problem!
I can’t use Fastboot command, because ewery time I got the „Waiting for devices” error message 
1) I have a Motorola Moto G4 phone (XT 1622, athene)
2) This mobile are not rooted.
3) I want to unlock my bootloader, after this I want to install TWRP, and after this I van root my mobile, for install the custom Lineage OS.
4) On my phone I activated at the Developper Otions the USB debugging, and OEM Unlocking.
5) I connected my phone to my PC, I used first time Windows 10. On this system my Moto G4 are identified: Motorola ADB interface. No problem with identification, no any yelow exclamation matrk, no unidentified device!
6) I have installed the correct ADB and Fastboot driver v.1.4.3 (link is made from this site)
7) I have installed the Motorola driver from the official Motorola site.
8) All ADB command work fine, for example adb devices, adb reboot bootloader, etc.
9) But no fastboot command work, when I tested the fastboot devices, I got the „Waiting for devices”. Of corse befor this, I rebooted my phone in fastboot mode! If I use any fastboot command, I got this error message.
10) I try to use the excellent tools (thank you for this): Universal Fastboot & ADB tool, latest version, but the situation in this case is the same, „Waiting for devices”.
11) Of corse I rebooted the PC after instalation of the drivers, the fastboot.exe is in the right paths, etc.
12) I have installed the Universal USB Driver with the Universal Fastboot & ADB tool, Install drivers button, PC rebooted after this.
13) I used Windows 10, Windows XP, and Ubuntu, and in all cases I got the „Waiting for devices”
14) Under Ubuntu I got this message, despite that on Ubuntu the ADB and Fastboot driver installations are cleare.
15) I tested all on many other PC.
16) Every time I connected my phone to the PC only on USB 2.0 port, I changed the USB port, and I changed the USB cable too.
17) I read hundred ot tutorilas on youtube, on differant Forums, but none of them helped.
18) I uninstalled or reinstalled a many timet he ADB and fastboot drivers (I tested a lot of drives from the net), and I installet a many times the official Motorola driver, and the Google universal USB driver, but nothing
Please tell me what can I do for solve this devil situation, Please help me! Thank you again!

How to install Stock OS in Moto G4 XT1624 with system partition wiped off

I have wiped all the partitions in my MotoG4 XT1624 including system partition without any backup using twrp , now the twrp recovery mode shows that i have no os installed , i have unlocked my bootloader before ,can anyone help me install stock os ,please

You might have to flash via USB cable to stock now. There are loads of user guide on this forum, including this one which worked on my xt 1622. https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138

libralibra said:
You might have to flash via USB cable to stock now. There are loads of user guide on this forum, including this one which worked on my xt 1622. https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Click to expand...
Click to collapse
I did the same thing but in the link you have mentioned ,it was mentioned that the "fastboot devices" command has to show a serial number, but nothing appears when i type that command ,i have also tried typing "adb devices" command ,but the same result ,a blank line appears

Soft bricked phone: looking for advice

Hi
I would like to ask for some advice.
I've recently soft bricked my MI2S. I can boot to recovery (TWRP 2.8.1) and fastboot. The phone isn't recognised by Windows or Ubuntu, so I can't flash anything with fastboot. Actually, fastboot, adb or MiFlash don't detect the phone. I've tried to use a USB stick with an OTG cable, but TWRP doesn't detect the USB stick. If I boot to system, it stays on the MI logo (I can wait a full night, it won't change).
My question is, do I have a problem with my USB port? I'm equipped to solder a new one, if necessary. Or is my connection problem due to another reason? I wouldn't want to go through soldering if it is for nothing. Especially, when I started to mess up with the phone, it was locked with a different MI account (it was my wife's account, but it took me a few days to connect the dots together), and I couldn't connect with MiFlash, adb or fastboot either.
The steps I did to get it soft bricked:
Flashed TWRP 2.8.1 with fastboot
Rebooted to recovery
Rebooted to MIUI (a few times)
Attempted to flash TWRP 3.5.0 (my memory fails a bit there, I think I did it via fastboot)
The last didn't work because I'm still on TWRP 2.8.1
And I can't add any more zip file to flash via recovery, nor can I use adb sideload or flash with fastboot.
Any advice or comments are more than welcome. You may just have an idea that I didn't think of.
Regards
Matt

Quick update:
I don't know if you would agree, but I can't see my issue to be a software one (the device not being recognised)
I've ordered a USB port directly from China and I'll see if I can unbrick the phone from that point.

It's great that you can still access to recovery and fastboot.
First, I advice you to back up your data.
If you cannot use adb sideload or flash with fastboot.
Try in fastboot mode
- fastboot erase cache;
- fastboot erase system;
- fastboot erase userdata.
See if that can solve your issue.