I am running freedomos 1.6.1.
I am trying to flash factory rom using adb sideload.
But i get an error " error: protocol fault (no status) ".
I tried uninstalling adb-fastboot drivers & again installing them but no luck. But strangely both adb as well as fastboot commands are working fine.
Please help??
parag60288 said:
I am running freedomos 1.6.1.
I am trying to flash factory rom using adb sideload.
But i get an error " error: protocol fault (no status) ".
I tried uninstalling adb-fastboot drivers & again installing them but no luck. But strangely both adb as well as fastboot commands are working fine.
Please help??
Click to expand...
Click to collapse
Update your ADB http://forum.xda-developers.com/showthread.php?t=2588979
Rakpere said:
Update your ADB http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
As i said earlier, i tried uninstalling & again installing the drivers. & used the same tool.
How can i uninstall adb & fastboot drivers completely?
I am using ADB v1.0.31
With this tool (if you are on Windows)
USBDeview
You can view all devices ever connected to the computer.
Just remove the once for your phone.
Hope it helps.
Jrod236 said:
With this tool (if you are on Windows)
USBDeview
You can view all devices ever connected to the computer.
Just remove the once for your phone.
Hope it helps.
Click to expand...
Click to collapse
:good:Thanks man, There was something wrong with drivers.
Tried it on old machine & it worked.
Related
I have a problem with my computer, I have a GNEX and I cannot get the commands from ADB to work. Once I tried to root my phone manually and I did not work, then I tried Wug's tool and it did not work either. I tried another computer and it worked. Both PC's have win7 and the drivers installed correctly. ADB does detect the phone.
When I type a command, the cursor just blinks and nothing happens. I can keep typing characters and still nothing happens.
Sounds like you're not running the command prompt as admin.
diobando said:
I have a problem with my computer, I have a GNEX and I cannot get the commands from ADB to work. Once I tried to root my phone manually and I did not work, then I tried Wug's tool and it did not work either. I tried another computer and it worked. Both PC's have win7 and the drivers installed correctly. ADB does detect the phone.
When I type a command, the cursor just blinks and nothing happens. I can keep typing characters and still nothing happens.
Click to expand...
Click to collapse
running what? 4.0.1, 4.2.2? ....
have you updated ADB/android-sdk?
To root a Nexus "manually", you just need fastboot, a custom recovery, and a superuser or supersu flashable zip. you don't even need ADB (if the zip flashable has been copied to /sdcard/ before)
bk201doesntexist said:
running what? 4.0.1, 4.2.2? ....
have you updated ADB/android-sdk?
To root a Nexus "manually", you just need fastboot, a custom recovery, and a superuser or supersu flashable zip. you don't even need ADB (if the zip flashable has been copied to /sdcard/ before)
Click to expand...
Click to collapse
I have 4.2.2 right now, but I tried it before with 4.0.2, 4.0.4 and 4.1.1. I have updated de sdk and the commands still do not work.
diobando said:
I have 4.2.2 right now, but I tried it before with 4.0.2, 4.0.4 and 4.1.1. I have updated de sdk and the commands still do not work.
Click to expand...
Click to collapse
Premise not to use almost never win7 ... I still tried for the first time tonight sdk-platform-tools on windows and adb and fastboot commands work normally ... the phone must have the bootloader unlocked (otherwise fastboot does not work ) is launched from the promt with administrator privileges and inside the folder where resides and the phone must be in fastboot / bootloader mode to acknowledge the command but also the drivers for the Nexus should be properly installed (try uninstalling and riinstallarli maybe installing some toolkit - gnextoolkit or Nexus Root Toolkit)
bk201doesntexist said:
running what? 4.0.1, 4.2.2? ....
have you updated ADB/android-sdk?
To root a Nexus "manually", you just need fastboot, a custom recovery, and a superuser or supersu flashable zip. you don't even need ADB (if the zip flashable has been copied to /sdcard/ before)
Click to expand...
Click to collapse
Maxmaximus said:
Premise not to use almost never win7 ... I still tried for the first time tonight sdk-platform-tools on windows and adb and fastboot commands work normally ... the phone must have the bootloader unlocked (otherwise fastboot does not work ) is launched from the promt with administrator privileges and inside the folder where resides and the phone must be in fastboot / bootloader mode to acknowledge the command but also the drivers for the Nexus should be properly installed (try uninstalling and riinstallarli maybe installing some toolkit - gnextoolkit or Nexus Root Toolkit)
Click to expand...
Click to collapse
Bootloader is unlocked. The phone is not the problem, I was able to unlock, root and push updates and ROMs in another computer. I just can get the commands to work in my computer. I tried doing any of this procedures with Wug's toolkit, and that does not work either.
At the risk of sounding silly, do you have usb debugging enabled?
bodh said:
At the risk of sounding silly, do you have usb debugging enabled?
Click to expand...
Click to collapse
Yes
Sent from my Galaxy Nexus using xda premium
Try another USB cable and/or port, and be sure you are running ADB with admin privilege.
Sent from my Galaxy Nexus using xda app-developers app
diobando said:
Bootloader is unlocked. The phone is not the problem, I was able to unlock, root and push updates and ROMs in another computer. I just can get the commands to work in my computer. I tried doing any of this procedures with Wug's toolkit, and that does not work either.
Click to expand...
Click to collapse
sounds like a problem with the toolkit not being updated.
considering you just said you got it to work on your pc with command prompt.
Zepius said:
sounds like a problem with the toolkit not being updated.
considering you just said you got it to work on your pc with command prompt.
Click to expand...
Click to collapse
Sorry, I had a typo. I meant I can't in "I just can get the commands to work in my computer..."
I have been searching all over xda and google to try and solve this problem and I'm stuck. I'm trying to unlock the boot loader for my Nexus 7 (2013) that I just got yesterday and I have been following the video guide.
The problem I'm having is that when I do command "adb devices" it shows that my Nexus 7 is connected to my PC (windows 7) but it says "offline" and when I do "adb reboot bootloader" I get the error "device offline".
I have my device in developer mode and I enabled USB debugging in the settings already. In my search throughout the forums and followed the steps to make sure that my drivers were up to date. I tried doing it by manually selecting the drivers and by using the SDK Manager to install the Google USB drivers, neither of these fixed the problem.
I can't figure out what I'm doing wrong, please help!
Have you tried rebooting into the bootloader manually then if "fastboot devices" work?
If you aren't seeing a popup on your tablet when adb tries to communicate with it, then you need to upgrade your adb client to the latest version.
They added some RSA verification step to the adb connection and if you have the old client it just says device offline.
You can update "platform-tools" in the sdk manager or find a download of just the adb, fastboot client and 2 libraries. If I remember the link I'll add it.
Here's the link for just the new ADB and libraries.
http://forum.xda-developers.com/showthread.php?p=43842630#post43842630
Have u checked camera instead of mass storage? That's how I have to do it.
Sent from my Nexus 7 using Tapatalk 4
Sounds like a driver issue.
Make sure you've got the correct drivers installed. Open up Device Manager in Windows 7 and manually update the driver - http://developer.android.com/tools/extras/oem-usb.html
Read the tutorial and watch/follow the video: http://forum.xda-developers.com/showthread.php?t=2382051
Got this on a Mac today, on the first time I connected this device.
Updated to latest android-sdk, re-installed platform-tools, and it worked fine.
sfhub said:
If you aren't seeing a popup on your tablet when adb tries to communicate with it, then you need to upgrade your adb client to the latest version.
They added some RSA verification step to the adb connection and if you have the old client it just says device offline.
You can update "platform-tools" in the sdk manager or find a download of just the adb, fastboot client and 2 libraries. If I remember the link I'll add it.
Here's the link for just the new ADB and libraries.
http://forum.xda-developers.com/showthread.php?p=43842630#post43842630
Click to expand...
Click to collapse
Thanks for the response! I got the ADB part working and now I'm trying to finish with the rooting process.
edit: Only getting "database error" when trying to download the TWRP flashable zip
Forgot10- said:
Thanks for the response! I got the ADB part working and now I'm trying to finish with the rooting process.
edit: Only getting "database error" when trying to download the TWRP flashable zip
Click to expand...
Click to collapse
Are you saying you have a download problem or a flashing problem?
The twrp archive I used wasn't a flashable zip. It was just a zip file with twrp.img archived.
You need to unzip and flash the twrp.img (it has a longer name) using
fastboot flash recovery twrp.img
Hey guyz,
I wanna use multirom and I'm getting stuck on flashing kernel in modified TWRP using sideload.
When i start it i can't find my device using command on cmd "adb devices"....it says "adb server didnt ACK" and failed to start daemon.
I'm running windows 8.1 and I installed htc sync for drivers.
If some1 know how to fix this problem i would be appriciate it,
ty
Are you booted into OS, or in bootloader? adb won't work in bootloader.
Do fastboot commands work? You need to be in bootloader-fastboot mode for that.
redpoint73 said:
Are you booted into OS, or in bootloader? adb won't work in bootloader.
Do fastboot commands work? You need to be in bootloader-fastboot mode for that.
Click to expand...
Click to collapse
yeah i know, i fixed it by deleting htc sync manager, anyway ty for your support
Everytime I try to sideload the zip files from OnePlus 3 downloads it fails. always. Updated the drivers on my computer, I'm not rooter, no custom roms. What am I doing wrong?
I had the same issue. Delete ALL of your adb drivers, and (re)install the Oneplus drivers, and try adb again. Hope it works for you.
Sent from my SM-J200G using XDA Free mobile app
Same error, with android N, still not find solution.
I do say wrong drivers. Although I have the issue aswell. I have a work around, I manually push it with ADB then I flash it with TWRP.
Puddi_Puddin said:
I do say wrong drivers. Although I have the issue aswell. I have a work around, I manually push it with ADB then I flash it with TWRP.
Click to expand...
Click to collapse
First Deselect Drivee singn on pc...
Thans install driver.. If not founs your phone or filed.. and you think driver ok...
Thans first load a file on CMD. adb sideload filename... when strart loading than connect phone on pc ? and Your Befire connect pc u On slideload yes button from recovery
Hey,
I need some help.
I tried to install LineageOS 14.1 on my Oneplus 3 following this guide, but I think by wiping /data or /system the ROM, which I copied to the phone beforehand, got deleted. Now I don't have any ROM in the storage and also no system installed.
I think fastboot only works in the bootloader mode (I get my phone serial number if I enter the command fastboot devices), but it doesn't work in the recovery mode (because I don't get my serial number then).
If I use the command: C:\adb\SDK\platform-tools>adb push lineage-14.1-20180328-UNOFFICIAL-Sultan-oneplus3.zip /sdcard/ I get the error: adb: error: failed to get feature set: no devices/emulators found while in bootloader mode and also the same error if I am in recovery mode. And if I try ADB Sideload (without wiping Dalvik Cache or Cache) my phone just says Starting ADB sideload features but does nothing else.
Does anyone know what I can do to fix my phone? If it helps I backed up my phone beforehand, but the backup files also got deleted on the phone, but I still have them on my pc.
Not sure if it will help, but make sure you are using the latest ADB downloaded from:
https://developer.android.com/studio/releases/platform-tools
I have had some strange problems with old ADB versions in the past,
good luck hope it helps you.
jeffrey268 said:
Not sure if it will help, but make sure you are using the latest ADB downloaded from: ...
I have had some strange problems with old ADB versions in the past,
good luck hope it helps you.
Click to expand...
Click to collapse
Is this the most recent version?
Code:
C:\adb\SDK\platform-tools>adb version
Android Debug Bridge version 1.0.39
Version 0.0.1-4500957
Installed as C:\adb\SDK\platform-tools\adb.exe
C:\adb\SDK\platform-tools>adb devices
List of devices attached
adb server version (32) doesn't match this client (39); killing...
* daemon started successfully
C:\adb\SDK\platform-tools>adb devices
List of devices attached
C:\adb\SDK\platform-tools>fastboot devices
3d0553dc fastboot
It should be, because I installed the SDK Platform today.
Also most guides which help to get adb working say, that if the phone doesn't get recognized you should get the install the drivers via the device manager, but my phones doesn't show up there, probably because it is in bootloader/recorvery mode.
EDIT: I now discovered that my phone gets recognized as Marshall London Device in the windows device manager and if I click on it it says Google Nexus ADB Interface. Are there any Oneplus 3 drivers which I should install instead?
Flix117 said:
Is this the most recent version?
Code:
C:\adb\SDK\platform-tools>adb version
Android Debug Bridge version 1.0.39
Version 0.0.1-4500957
Installed as C:\adb\SDK\platform-tools\adb.exe
C:\adb\SDK\platform-tools>adb devices
List of devices attached
adb server version (32) doesn't match this client (39); killing...
* daemon started successfully
C:\adb\SDK\platform-tools>adb devices
List of devices attached
C:\adb\SDK\platform-tools>fastboot devices
3d0553dc fastboot
It should be, because I installed the SDK Platform today.
Also most guides which help to get adb working say, that if the phone doesn't get recognized you should get the install the drivers via the device manager, but my phones doesn't show up there, probably because it is in bootloader/recorvery mode.
EDIT: I now discovered that my phone gets recognized as Marshall London Device in the windows device manager and if I click on it it says Google Nexus ADB Interface. Are there any Oneplus 3 drivers which I should install instead?
Click to expand...
Click to collapse
I use this drivers https://androidfilehost.com/?fid=24591020540821930
xGOGI said:
I use this drivers https://androidfilehost.com/?fid=24591020540821930
Click to expand...
Click to collapse
Try this:
Download the stock recovery for your device:
http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img
Place it in c:\OP3\
Go into cmd and go to c:\OP3\
then type: fastboot flash recovery recovery_op3.img
If you get reboots after this, do the following:
Boot back into fastboot and type:
fastboot format userdata
after that type:
fastboot flash recovery recovery_op3.img
Flix117 said:
Hey,
I need some help.
I tried to install LineageOS 14.1 on my Oneplus 3 following this guide, but I think by wiping /data or /system the ROM, which I copied to the phone beforehand, got deleted. Now I don't have any ROM in the storage and also no system installed.
I think fastboot only works in the bootloader mode (I get my phone serial number if I enter the command fastboot devices), but it doesn't work in the recovery mode (because I don't get my serial number then).
If I use the command: C:\adb\SDK\platform-tools>adb push lineage-14.1-20180328-UNOFFICIAL-Sultan-oneplus3.zip /sdcard/ I get the error: adb: error: failed to get feature set: no devices/emulators found while in bootloader mode and also the same error if I am in recovery mode. And if I try ADB Sideload (without wiping Dalvik Cache or Cache) my phone just says Starting ADB sideload features but does nothing else.
Does anyone know what I can do to fix my phone? If it helps I backed up my phone beforehand, but the backup files also got deleted on the phone, but I still have them on my pc.
Click to expand...
Click to collapse
To clear some things up for you. Fastboot is only used in bootloader mode since that is what it is.
And for the adb sideload, are you initializing the sideload on your phone as well? To use sideload the phone has to be ready on the receiving end, in recovery you have to start adb sideload then launch the process on pc for it to work properly. And if you dont want the whole android SDK to just use ADB and Fastboot i recommend you install the minimal tool https://forum.xda-developers.com/showthread.php?t=2588979 :good: