Database Info

[Q] Fastboot does nothing!

Hey,
i just wanted to flash the newest clockworkmod but my fastboot.exe does nothing.
Phone is in fastbootmode, please help
Windows 7 x64...but it worked the other day

Fastboot flash recovery "recovery".img where "recovery" stands for the numbers of the recovery in tools folder i believe.
Also if you run 2.3.4, recovery wil not stick after reboot unless you change something ( i believe the recovery.sh file), hope this helps!

Fmbl said:
Fastboot flash recovery "recovery".img where "recovery" stands for the numbers of the recovery in tools folder i believe.
Also if you run 2.3.4, recovery wil not stick after reboot unless you change something ( i believe the recovery.sh file), hope this helps!
Click to expand...
Click to collapse
i can flash the recovery fia ROMManager, and also can boot into it, but when i boot the phone into bootloader/fastboot mode i can't flash a new recovery, because when i hit enter after "fastboot" i get no output in cmd

If you don't get anything back on fastboot devices, then you either don't have the proper drivers installed, don't have the phone in fastboot mode, or don't have the phone connected via USB. Probably the first one.
Easiest way to get the fastboot drivers is to simply install PDA Net on your computer and follow the on screen prompts. It will automatically install the appropriate drivers for your device.
Sent from my Nexus S using XDA App

thanks, i will try when i am at home again
Sent from my Nexus S using XDA App

Check in device manager that the ADB Bootloader driver is installed.

zero383 said:
Check in device manager that the ADB Bootloader driver is installed.
Click to expand...
Click to collapse
adb works fine, i use the phone for debugging
i tried the PDAnet methode and reinstalled the driver --> no success
any other suggestions

eiabea said:
adb works fine, i use the phone for debugging
i tried the PDAnet methode and reinstalled the driver --> no success
any other suggestions
Click to expand...
Click to collapse
That method works. I suggest do it again and follow the instructions more carefully.
Sent from my Nexus S using XDA App

matt2053 said:
That method works. I suggest do it again and follow the instructions more carefully.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
did it very carefully, but no success

Did you ever figure this out? I have installed PDA net, drivers, etc, and fastboot simply will not connect to my phone. Win7x64.

ericshmerick said:
Did you ever figure this out? I have installed PDA net, drivers, etc, and fastboot simply will not connect to my phone. Win7x64.
Click to expand...
Click to collapse
Need more info.
Did you install the "ADB Bootloader Interface" driver?
Did you boot the the phone into the bootloader before trying the fastboot command? (ie. UP + PWR)

zero383 said:
Need more info.
Did you install the "ADB Bootloader Interface" driver?
Did you boot the the phone into the bootloader before trying the fastboot command? (ie. UP + PWR)
Click to expand...
Click to collapse
Yes and yes.
May want to continue here:
http://forum.xda-developers.com/showthread.php?t=1303522

Had the same issues, although drivers were installed. After including "C:\android-sdk-windows\tools"
and "C:\android-sdk-windows\platform-tools"
in the path of win7 (systemvariables)
and a restart adb and fastboot worked.

[Q] Unrooted but still have SU app after updating to 4.4.1

Hi,
I hope someone can help me out. I recently updated to 4.4.1 via Clockworkmod. The update worked fine but now I'm unrooted. I still have the SU app, it just doesn't do anything. Is there a way to remove it without rooting again? If not what's the easiest way to root the device (bootloader is unlocked and currently have stock recovery)? The first time I rooted the bootloader was locked and the process I used unlocked and rooted in the same step.
Thanks for your help!

keep the app. reflash a custom recovery, then flash the latest supersu in your custom recovery. there, youre rooted again.

simms22 said:
keep the app. reflash a custom recovery, then flash the latest supersu in your custom recovery. there, youre rooted again.
Click to expand...
Click to collapse
Thanks. Don't want to mess anything up so any info you can provide on how to flash a custom recovery while unrooted would be greatly appreciated.

danotoriusodo said:
Thanks. Don't want to mess anything up so any info you can provide on how to flash a custom recovery while unrooted would be greatly appreciated.
Click to expand...
Click to collapse
http://lmgtfy.com/?q=how+to+flash+custom+recovery+fastboot

danotoriusodo said:
Thanks. Don't want to mess anything up so any info you can provide on how to flash a custom recovery while unrooted would be greatly appreciated.
Click to expand...
Click to collapse
flashing a recovery, a rom, a kernel, and a mod doesnt require root. the only thing that requires root are apps that need root to work.

simms22 said:
flashing a recovery, a rom, a kernel, and a mod doesnt require root. the only thing that requires root are apps that need root to work.
Click to expand...
Click to collapse
Tried sideloading 4.2.2 before I rooted again and can't get my phone recognized in sideload. Now I can't even restart my phone. Tried using a different usb port and cable and nothing. I'm reading the only way to restart my phone is to wait for the battery to drain. Is there anything else I can try? Thanks.

danotoriusodo said:
Tried sideloading 4.2.2 before I rooted again and can't get my phone recognized in sideload. Now I can't even restart my phone. Tried using a different usb port and cable and nothing. I'm reading the only way to restart my phone is to wait for the battery to drain. Is there anything else I can try? Thanks.
Click to expand...
Click to collapse
What do you mean you can't restart it? Is it frozen? Try holding down the power button for about thirty seconds. It seems to be the equivalent of removing the battery.

Saturn2K said:
What do you mean you can't restart it? Is it frozen? Try holding down the power button for about thirty seconds. It seems to be the equivalent of removing the battery.
Click to expand...
Click to collapse
Got it. Thanks. Any idea why it wouldn't recognize the device? I downloaded the driver package from SDK manager and tried to update from the extras folder but it said my package was up to date. The only weird thing is the driver is showing up as Samsung Android phone in device manager. I tried uninstalling, restarted the computer, reconnected my phone and it still says Samsung.... Again, any help is greatly appreciated. Thanks.

danotoriusodo said:
Got it. Thanks. Any idea why it wouldn't recognize the device? I downloaded the driver package from SDK manager and tried to update from the extras folder but it said my package was up to date. The only weird thing is the driver is showing up as Samsung Android phone in device manager. I tried uninstalling, restarted the computer, reconnected my phone and it still says Samsung.... Again, any help is greatly appreciated. Thanks.
Click to expand...
Click to collapse
Maybe read my edit below first. What follows is the manual way for doing this. There's a program that'll do all of this for you if you don't want to mess with this.
Try installing the Google Android USB drivers.
http://developer.android.com/sdk/win-usb.html
To install the USB drivers, first boot your phone into the bootloader (hold volume down and the power button while the phone is off). Then go into your device manager in windows. You'll either see something flagged with some yellow icon or you'll need to find some entry that says something about Android or your phone. Right click on that and hit update drivers. Unzip the latest_usb_driver_windows.zip somewhere and then point the driver updater at that folder. It'll find and install drivers. Voila, fastboot should now recognize your phone.
Then follow the steps for getting into the bootloader, flashing the custom recovery, and then flashing superuser from the custom recovery.
Edit: OR, just use the Nexus Root Toolkit http://www.wugfresh.com/nrt/
It has an option for installing drivers, installing the custom recovery, etc. It's very straightforward.

Saturn2K said:
Maybe read my edit below first. What follows is the manual way for doing this. There's a program that'll do all of this for you if you don't want to mess with this.
Try installing the Google Android USB drivers.
http://developer.android.com/sdk/win-usb.html
To install the USB drivers, first boot your phone into the bootloader (hold volume down and the power button while the phone is off). Then go into your device manager in windows. You'll either see something flagged with some yellow icon or you'll need to find some entry that says something about Android or your phone. Right click on that and hit update drivers. Unzip the latest_usb_driver_windows.zip somewhere and then point the driver updater at that folder. It'll find and install drivers. Voila, fastboot should now recognize your phone.
Then follow the steps for getting into the bootloader, flashing the custom recovery, and then flashing superuser from the custom recovery.
Edit: OR, just use the Nexus Root Toolkit http://www.wugfresh.com/nrt/
It has an option for installing drivers, installing the custom recovery, etc. It's very straightforward.
Click to expand...
Click to collapse
Thanks for your help. I can definitely try the Nexus root Toolkit but I'd really like to get comfortable doing it manually.
The issue I keep running into is with the drivers. I uninstalled the drivers, installed them again while in the bootloader and it said successful (shows up as Android device > Android Bootloader Interface). Then when I enter recovery and select adb..., device manager lists it as an "Other Device > Nexus 5" with the yellow triangle. I try again there to update the drivers from the same folder that they installed in via the SDK and I get an error that the device driver software can't be found. I have usb debugging mode checked and selected always allowed for this computer. I've tried "adb devices" and nothing is recognized. Any thoughts?

danotoriusodo said:
Thanks for your help. I can definitely try the Nexus root Toolkit but I'd really like to get comfortable doing it manually.
The issue I keep running into is with the drivers. I uninstalled the drivers, installed them again while in the bootloader and it said successful (shows up as Android device > Android Bootloader Interface). Then when I enter recovery and select adb..., device manager lists it as an "Other Device > Nexus 5" with the yellow triangle. I try again there to update the drivers from the same folder that they installed in via the SDK and I get an error that the device driver software can't be found. I have usb debugging mode checked and selected always allowed for this computer. I've tried "adb devices" and nothing is recognized. Any thoughts?
Click to expand...
Click to collapse
Did you flash a custom recovery while you were in the bootloader? I'm don't think adb works in the stock recovery, but I could be wrong.
As long as you have the bootloader working, that's all you really need. You just need to flash the custom recovery. Then put some superuser.zip onto your storage, boot into the recovery, and flash it.
As for the driver issue, I only did what I told you. If doing it manually didn't work, I'd try the toolkit.

Saturn2K said:
Did you flash a custom recovery while you were in the bootloader? I'm don't think adb works in the stock recovery, but I could be wrong.
As long as you have the bootloader working, that's all you really need. You just need to flash the custom recovery. Then put some superuser.zip onto your storage, boot into the recovery, and flash it.
As for the driver issue, I only did what I told you. If doing it manually didn't work, I'd try the toolkit.
Click to expand...
Click to collapse
I think the whole point of sideloading is that you can have everything stock if that's what you want. I'm going to try the toolkit because I've tried and tried and can't get the sideload to work. When the phone is turned on I can type "adb devices" and my serial number comes up. I can eneter "adb reboot bootloader" and the phone restarts. It's just when I get to recovery it tells me "device not found". Thanks again for your help and if you or anyone else has any suggestions I'm all ears.

danotoriusodo said:
I think the whole point of sideloading is that you can have everything stock if that's what you want. I'm going to try the toolkit because I've tried and tried and can't get the sideload to work. When the phone is turned on I can type "adb devices" and my serial number comes up. I can eneter "adb reboot bootloader" and the phone restarts. It's just when I get to recovery it tells me "device not found". Thanks again for your help and if you or anyone else has any suggestions I'm all ears.
Click to expand...
Click to collapse
Hmm, from your reply, I'm not sure if you're getting into recovery or not. There's the bootloader and there's recovery, they're separate things. Once you're in the bootloader, you choose to go into the recovery. Then, in the recovery, you choose to "apply update from ADB." Then you issue the adb sideload command from your computer.

Saturn2K said:
Hmm, from your reply, I'm not sure if you're getting into recovery or not. There's the bootloader and there's recovery, they're separate things. Once you're in the bootloader, you choose to go into the recovery. Then, in the recovery, you choose to "apply update from ADB." Then you issue the adb sideload command from your computer.
Click to expand...
Click to collapse
Thanks but that's what I've been doing and what's driving me crazy. ADB works when the phone is on. It recognizes my device and reboots on command. I get to the bootloader where it still recognizes my device. Once I select recovery, the phone comes up with the yellow triangle in device manager and I can't sideload after I select the option. A friend of mine who;s sideloaded before watched me do it and was just as confused. Any other suggestions?
**Update**
So for some reason the driver package installed via the SDK manager doesn't have the Nexus 5 "hardware id". I needed to add these three lines in the .inf file within the usb drivers folder:
;Google Nexus 5
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D001
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&REV_0232
One I added those and updated the driver I was able to sideload.
Thanks again for your help

LG nexus 5 hammerhead running cyanogen - unable to connect to pc using adb

Hi Team,
Greetings.
I have been using LG Nexus 5 running cm12.1 but since the moment I updated the phone to cm13 I have started facing lots of troubles. The phone boots up and stuck on cm logo also I did something and the twrp recovery is not seen anymore instead I only have cyanogemode recovery which is driving me nuts. The present situation I am facing is I can't connect my phone to the pc for me to reinstall twrp. I really appreciate your help in this matter.
Thanks a lot for your time.
Merry Christmas!
Jinson Jose.

So the phone is not detected when connected in fastboot mode? Adb commands are often used when the phone has fully booted into the installed rom.

audit13 said:
So the phone is not detected when connected in fastboot mode? Adb commands are often used when the phone has fully booted into the installed rom.
Click to expand...
Click to collapse
Hi Yes the phone is not detected and I tried adb commands too but in vain. I guess I messed up the phone while I am on cyanogenmode recovery by trying to format the phone.

Is the phone detected when you connect the phone to the computer in fastboot mode? ADB commands will not work in fastboot mode as you need to use fastboot commands.

Maybe it might be the PC drivers? I lost connection too and managed to restore it by using the driver setup module in Wugfresh's Nexus Root Toolkit. It will walk you through removing vestiges of old drivers and help install new drivers.

audit13 said:
Is the phone detected when you connect the phone to the computer in fastboot mode? ADB commands will not work in fastboot mode as you need to use fastboot commands.
Click to expand...
Click to collapse
No the phone is not detected. All I can see is a usb sign and it says nexus 5. I can't open nexus 5 files.

The computer is a Windows xp or win7 machine?
No devices are found and you run a fastboot command?

audit13 said:
The computer is a Windows xp or win7 machine?
No devices are found and you run a fastboot command?
Click to expand...
Click to collapse
Hi Thanks for your reply. The Machine is Windows 10. I tried fastboot commands as seen in one of the google searches. When I connect the phone it is not detected. I was able to see the nexus but I think I messed things by trying to factory reset and wipe cache using cyanogenmode recovery. Now the computer shows only universal serial bus devices when I connect the phone.

OP, hello...? Am I inaudible/illegible? Have you tried setting up the ADB/Fastboot via NRT as I suggested?

I don't use Win10. I do all of my flashing on a Win7 x64 machine and everything works perfectly when I am dealing with my Nexus 4, Nexus 5, and nexus 7.

I use Win10 with no problems. It must be the driver setup. NRT will fix it for the OP if he can clear whatever is preventing him seeing my post...

Can't unlock bootloader, need help with drivers

I'm trying to unlock my bootloader to install a custom rom. "adb devices" command works fine but "fastboot devices" doesn't return anything. In windows device manager i haven't updated drivers because i dont know where to download them. Any help with drivers? I have an "android bootloader interface" option there but windows warns me that it might not be compatible and might break everything.

Download the Universal adb drivers from google

vuittion said:
Download the Universal adb drivers from google
Click to expand...
Click to collapse
I have done this, but it didn't help

enkerrohah said:
I have done this, but it didn't help
Click to expand...
Click to collapse
Download Tool all in one for flashing recovery and unlock bootloader. For One Plus 6. Check in XDA. Install necessary drivers. In developer option,usb debugging and file transfer for OTG.

sschacko said:
Download Tool all in one for flashing recovery and unlock bootloader. For One Plus 6. Check in XDA. Install necessary drivers. In developer option,usb debugging and file transfer for OTG.
Click to expand...
Click to collapse
Just downloading the adb drivers from google's own site made it work on another PC. I think my problem is that Windows has installed the wrong drivers for me. When i plug a device in for the first time, it says something like "setting up your device". I think during that point it installed wrong drivers on my own PC. On my brothers PC everything works like it's supposed to. Any idea how to get Windows to install the drivers again?

enkerrohah said:
Just downloading the adb drivers from google's own site made it work on another PC. I think my problem is that Windows has installed the wrong drivers for me. When i plug a device in for the first time, it says something like "setting up your device". I think during that point it installed wrong drivers on my own PC. On my brothers PC everything works like it's supposed to. Any idea how to get Windows to install the drivers again?
Click to expand...
Click to collapse
Problem persist when you try to install Drivers without valid signature in Windows 10.. Try to DIsable Driver Signature Enforcement..
Link to do it https://windowsreport.com/driver-signature-enforcement-windows-10/
Then try to install Drivers from this link :- https://drive.google.com/file/d/1L7EZGx5mgeQYXO19Vsp9FWu9GXhF45Qs/view
Let me know if that helps..

I have quit the same problem expected that i already have my bootloader unlock and usb debugging turn on...
im trying to flash twrp image, after failed yesterday to apply pixen os11. I had access to fasboot mode and to flash zip etc and my drivers was instaled but now my laptop didn't reconize my phone when plug in in fastboot and is on other devices in my devices manager. I tried to install updates manualy but nothing happened.
i dont know if it is related but i did update windows between my secon attempt to flash pixen os. Maybe the drivers were update in the same occasions ? Because a i have no others problems when my phone is boot normally and can acess to internal storage from my computer.

How to root zenfone 7 ZS670KS

hello guys
how do i root this phone please.
none of the google searched guides seem to work.
1. i've unlocked the bootloader using the asus app
2. i have adb installed on my pc
3. i've enabled usb debug mode on phone and allowing installation unknown apps
4. i've installed magisk v23 by downloading from github and just installing the apk file normally
5. i've downloaded a 2.9gb zip file from asus for androind 11 firmware onto phone and pc (but its a zip file that extracts a bin file, no image file)
my problem seems to be i don't know how to CREATE AND PATCH an image file or install twrp and install image file that way.
Could someone help, there doesn't seem to be any guides for rooting in this phones forum.

Look in the twrp thread: https://forum.xda-developers.com/t/recovery-official-twrp-for-asus-zenfone-7-series.4161719/
after twrp you can flash the magisk.zip

Seosam said:
Look in the twrp thread: https://forum.xda-developers.com/t/recovery-official-twrp-for-asus-zenfone-7-series.4161719/
after twrp you can flash the magisk.zip
Click to expand...
Click to collapse
i keep getting era waiting for device when i want to flash the phoben with twrp.
adb reboot bootloader (works and i enter the recovery menu start, bootloader, recovery, power off etc)
fastboot flash recovery_a twrp.img (when i type this cmd power shell just says waiting for device)
i have universal drivers installed and android sdk installed. not sure why it isn't recognising the phone?
When my phone is switched on normally, cmd recognises it, when i use adb devices. but as soon as i reboot into recovery mode using cmd "adb reboot bootloader" it stops recognising the phone on the list of devices using the cmd "adb devices"

so you don`t get an answer from your phone by "fastboot devices" ?
Have you tried another usb cable and or port?

Seosam said:
so you don`t get an answer from your phone by "fastboot devices" ?
Have you tried another usb cable and or port?
Click to expand...
Click to collapse
no answer from phone when in fastboot mode.
but i do get a reply in cmd when phone is switched on normally.
I'll try with another cable, but if it responds to adb when in normal mode. doesn't it mean it's not a cable issue but a software driver issue?

Seosam said:
so you don`t get an answer from your phone by "fastboot devices" ?
Have you tried another usb cable and or port?
Click to expand...
Click to collapse
seems when i do adb reboot bootloader it goes into what i thought was called fastboot. It even says fastboot.
but in that mode my phone isn't recognised by cmd when type adb devices, it doesn't come up.
it has 4 options reboot system now, botloader, enter recovery, reboot to bootloader, power off.
if i then select enter recovery. it enters a smaller text screen with lots of small blue writing. when inside that screen (recovery mode) cmd seems to recognise my device.
but it says it is unauthorized. this is in recovery mode.
i'm not sure why it says it is unauthorized. i've authorised my pc to control the phone through the fingerprint, when the message popped up.
but i can't push the twrp.img file through because of this.
since cmd doesn't seem to recognise phone in fastboot mode.
and cmd doesn't seem to have authorisation in recovery mode.
any ideas?

is it possible to root using adb sideload or install twrp using adb sideload?

articoceanic said:
seems when i do adb reboot bootloader it goes into what i thought was called fastboot. It even says fastboot.
but in that mode my phone isn't recognised by cmd when type adb devices, it doesn't come up.
it has 4 options reboot system now, botloader, enter recovery, reboot to bootloader, power off.
if i then select enter recovery. it enters a smaller text screen with lots of small blue writing. when inside that screen (recovery mode) cmd seems to recognise my device.
but it says it is unauthorized. this is in recovery mode.
i'm not sure why it says it is unauthorized. i've authorised my pc to control the phone through the fingerprint, when the message popped up.
but i can't push the twrp.img file through because of this.
since cmd doesn't seem to recognise phone in fastboot mode.
and cmd doesn't seem to have authorisation in recovery mode.
any ideas?
Click to expand...
Click to collapse
Thats the right mode.
Does the phone at normal start show that the bootloader is unlocked?
Your debugging mode is turned on in developer settings?
A sideload isn`t possible I think.

Seosam said:
Thats the right mode.
Does the phone at normal start show that the bootloader is unlocked?
Your debugging mode is turned on in developer settings?
A sideload isn`t possible I think.
Click to expand...
Click to collapse
yes, shows bootloader is unlocked when i start the phone.
usb debugging mode is turned on.
i think for some reason in fastboot mode the device driver is not recognised in windows. have googled seems it was a very old problem that happned on phones 6 years ago. nut i haven't found anything recent to solve same error.

articoceanic said:
yes, shows bootloader is unlocked when i start the phone.
usb debugging mode is turned on.
i think for some reason in fastboot mode the device driver is not recognised in windows. have googled seems it was a very old problem that happned on phones 6 years ago. nut i haven't found anything recent to solve same error.
Click to expand...
Click to collapse
So you can just try it on another pc.
Have you changed from USB 3 port to a USB 2?
My Xiaomi mix2s had sometimes this too. That's worked for me.

Seosam said:
So you can just try it on another pc.
Have you changed from USB 3 port to a USB 2?
My Xiaomi mix2s had sometimes this too. That's worked for me.
Click to expand...
Click to collapse
i think its definitely a driver issue. windows 10 seems to be overriding the drivers and installing wrong ones. and won't let me install right ones.
haven't tried in a different pc. will need to get hold of one and try.

Seosam said:
So you can just try it on another pc.
Have you changed from USB 3 port to a USB 2?
My Xiaomi mix2s had sometimes this too. That's worked for me.
Click to expand...
Click to collapse
dont'know what happened. but weirdly i used usb 2.0 as you said and the driver listed on page 2 of this link got recognised.
[RECOVERY][OFFICIAL] TWRP for ASUS ZenFone 7 Series
*** Disclaimer *** All flashing is done at your own risk! While nothing from this thread should break your device, don't come back here blaming anyone if it does! Introduction Team Win Recovery Project 3.x, or twrp3 for short, is a custom...
forum.xda-developers.com
all this time windows 10 wouldn't let me install it. kept saying the drivers i already had was the best ones. but weirdly this time it did.
thanks friend. i think i have root access now. magisk keeps asking me to install the app tho. not sure why. i have version 23.0 installed.
but when i opne magisk it shows install icons for magisk and an unknown App. both listed as version 23.0.

Seosam said:
So you can just try it on another pc.
Have you changed from USB 3 port to a USB 2?
My Xiaomi mix2s had sometimes this too. That's worked for me.
Click to expand...
Click to collapse
last question friend, thanks for all your help.
where do i download apps like ad block plus adaway minmingaurd etc.
magisk dowsn't seem to have an option for that.

articoceanic said:
last question friend, thanks for all your help.
where do i download apps like ad block plus adaway minmingaurd etc.
magisk dowsn't seem to have an option for that.
Click to expand...
Click to collapse
how solve com.asus.service keep stopping after install twrp? android 11 stock rom please answer

decade 1 said:
how solve com.asus.service keep stopping after install twrp? android 11 stock rom please answer
Click to expand...
Click to collapse
I'm not sure.
i only managed to root it by following the instructions here years ago.
maybe try updating the asus apps in play store? or ask some of the other people here who know more than me. or disable the asus apps. i don't use them.
sorry i couldn't help more

articoceanic said:
I'm not sure.
i only managed to root it by following the instructions here years ago.
maybe try updating the asus apps in play store? or ask some of the other people here who know more than me. or disable the asus apps. i don't use them.
sorry i couldn't help more
Click to expand...
Click to collapse
I try factory reset normal again I hope no recurrence