Why Does Sideloading ALWAYS fail? - OnePlus 3 Questions & Answers

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

Related

[Soft Brick] No OS Installed

Hi everyone, i have medium to advanced experience with flashing tools, android drivers, adb, fastboot, recovery mode and so on.
This evening once i installed the OTA Update for my Galaxy Nexus (which was running Android 4.2) the process failed at the end (as usual -.-) and i got stuck at bootloader.
I've wiped it completely ending up with no OS installed on it, nothing on SDCARD (Internal storage in this case).
The problem is that, i have no drivers installed on my PC for this phone.
I've already downloaded the latest version of Android 4.2 to flash (.zip), but there's no way i can transfer the file to the phone without the drivers.
I already tried GNex toolkit but it's stuck on "waiting adb device" (i have no fastboot drivers installed and can't install them because i can't find a easy way to do so).
NexusRootToolkit fails on pushing the zip to the phone and flash also won't work.
Any idea of what can i do now?
I may even pay on paypal for a quick help to get my phone back on working
Get into the bootloader and use fastboot, or if you have a custom recovery installed (sounds like you don't) then you can adb push from there. ADB doesn't exist in the bootloader, only fastboot. Those are your options.
ttabbal said:
Get into the bootloader and use fastboot, or if you have a custom recovery installed (sounds like you don't) then you can adb push from there. ADB doesn't exist in the bootloader, only fastboot. Those are your options.
Click to expand...
Click to collapse
Actually i do have a custom recovery which is CMW, but i can't seem to get my internal storage mounted using i'ts options.
I will try to push the .zip using the ADB on the recovery mode.
After checking the logs i can now see :
Enable to mount /usb-otg
(Using NexusRootToolkit i just flashed TWRP as recovery mode)
Solved : adb push <romname.zip> /sdcard/<romname.zip>
After the push was completed, i flashed the new .zip using TWRP in recovery mode.
Has anyone found a solution to this? Same thing has happened to me and I'm freaking out.
NPasta said:
Has anyone found a solution to this? Same thing has happened to me and I'm freaking out.
Click to expand...
Click to collapse
You mean besides the post right above yours?
Solved : adb push <romname.zip> /sdcard/<romname.zip>
After the push was completed, i flashed the new .zip using TWRP in recovery mode.
Click to expand...
Click to collapse
Save the pain, just flash the stock ROM from fastboot already....
Mach3.2 said:
Save the pain, just flash the stock ROM from fastboot already....
Click to expand...
Click to collapse
This. I don't see what the problem is here.
marcelloLins said:
i have medium to advanced experience with flashing tools, android drivers, adb, fastboot, recovery mode and so on.
I already tried GNex toolkit but it's stuck on "waiting adb device" (i have no fastboot drivers installed and can't install them because i can't find a easy way to do so).
NexusRootToolkit fails on pushing the zip to the phone and flash also won't work.
Click to expand...
Click to collapse
If you have the experience you say you have why do you use a Toolkit? Just learning for myself.
Look for efrant posts, they are the best and most comprehensive even for medium-advanced experience.
With him you will learn everything you need to know, including getting out of trouble and out of.............toolkit.
Just in case (you never know in life) do you have android-sdk installed on your pc?
Good luck in your learning curve ( I am still and will always be in it)
help-a-noob
Having similar problem: no OS installed. Got bootloader and TWRP. adb push doesn't work: computer can't find device. how do I get to fastboot? HALP!
HALP...
That's classic..
Read this:
http://forum.xda-developers.com/showthread.php?t=1812959
Then follow this:
http://forum.xda-developers.com/showthread.php?t=1626895
gunner1937 said:
If you have the experience you say you have why do you use a Toolkit? Just learning for myself.
Look for efrant posts, they are the best and most comprehensive even for medium-advanced experience.
With him you will learn everything you need to know, including getting out of trouble and out of.............toolkit.
Just in case (you never know in life) do you have android-sdk installed on your pc?
Good luck in your learning curve ( I am still and will always be in it)
Click to expand...
Click to collapse
Yep, i do have it installed, mainly because i'm a developer myself ; )
I've solved it already, as i've said, pushing the rom using ADB.
The upgrade to 4.2.1 probably failed because i've had the phone rooted.
Thanks for all the support and links by the way
marcelloLins said:
The upgrade to 4.2.1 probably failed because i've had the phone rooted.
Click to expand...
Click to collapse
You are mistaken, root doesn't stop a system update. I can vouch for that myself, even though i know that it doesnt matter just from reading some people's posts around here.
You weren't exactly explicit on your first post, so I presume you didnt/dont have the correct baseband version for that specific OTA to apply. Very common.
Oh and if you've never been able to OTA update successfully, it's not "usual" for the rest of us. You should work towards becoming more verbose and objective when troubleshooting. That will make you more experienced.
Sent from my i9250
marcelloLins said:
Yep, i do have it installed, mainly because i'm a developer myself ; )
I've solved it already, as i've said, pushing the rom using ADB.
The upgrade to 4.2.1 probably failed because i've had the phone rooted.
Thanks for all the support and links by the way
Click to expand...
Click to collapse
Hey, I have this exact problem. My os is gone and all i have is my cwm.
I am also having trouble installing adb, my comp doesn't recognize my nexus.
Please help, thanks!
dicksonjoe said:
Hey, I have this exact problem. My os is gone and all i have is my cwm.
I am also having trouble installing adb, my comp doesn't recognize my nexus.
Please help, thanks!
Click to expand...
Click to collapse
Try installing the ADB Drivers manually in order for your PC to recognize it.
Have you tried putting it other modes such as Download Mode and check if your pc installs any driver?
You will have to ADB PUSH the OS image to your internal memory and use CW to flash the rom from the sdcard, but you will need the drivers installed or adb wont be able to see your phone
i have the same problem you had...
i read some stuff and installed adb, sdk and whatever...
im trying the " adb push" command, but i think im doing something wrong.
the rom is on c:\users\edgar\downloads
rom name is abc.zip (i renamed)
what is the correct command format i must type??
thanks guys...
edgarzin said:
i have the same problem you had...
i read some stuff and installed adb, sdk and whatever...
im trying the " adb push" command, but i think im doing something wrong.
the rom is on c:\users\edgar\downloads
rom name is abc.zip (i renamed)
what is the correct command format i must type??
thanks guys...
Click to expand...
Click to collapse
Use "adb sideload c:\users\edgar\downloads\abc.zip". "adb push" is for transferring files from PC to phone, not flashing.
AndyYan said:
Use "adb sideload c:\users\edgar\downloads\abc.zip". "adb push" is for transferring files from PC to phone, not flashing.
Click to expand...
Click to collapse
thanks, but isnt it what am i supposed to do? transfer the zip file to sdcard and then flash using twrp?
for example usb mount via twrp dont work for me
edgarzin said:
thanks, but isnt it what am i supposed to do? transfer the zip file to sdcard and then flash using twrp?
Click to expand...
Click to collapse
adb sideload does both transferring and flashing within a single command. The "sideloaded" ZIP gets saved as "sideload.zip" under the root of the storage.
Sent from Samsung Galaxy Nexus @ CM11
AndyYan said:
adb sideload does both transferring and flashing within a single command. The "sideloaded" ZIP gets saved as "sideload.zip" under the root of the storage.
Sent from Samsung Galaxy Nexus @ CM11
Click to expand...
Click to collapse
Thanks!! Now its working! in twrp, advanced mode, adb sideload, then i executed the command you told me!!! saved my phone

No ADB or connection at all with PC

Guys, i have a bit of a problem, when trying to flash Omni ROM 4.4, i installed TWPR Recovery but wiped everything, included sdcard, mistake, now, i wanted to use KDZ to flash stock firmware or through CMD push ROM file to sdcard but can't get to connect the device, if i'm in download mode or recovery, adb is not working, in Devices it lists as "Android" but with trouble to obtain drivers, and if i boot normally, can't enter the OS because i wiped, i get MTP installation and another ones, but device in ADB (adb devices) is Offline.
What can i do?
Does download mode install drivers or find your phone?
Sent from my LG-E975 using Tapatalk
atifsh said:
Does download mode install drivers or find your phone?
Sent from my LG-E975 using Tapatalk
Click to expand...
Click to collapse
The problem was about drivers, that i knew, so i found some universal adb drivers, and they got installed, device was recognized but not as online, just as host, so i couldn't use adb sideload or just use adb to push the file. Found out that adb was outdated so i downloaded another one and, everything working, sideloaded the files, and now everything is runinng up again.

ADB under TWRP

I am using Windows 8.1
I can connect my Xperia S throught ADB under USB debugging mode.
But I cannot do the same thing in TWRP.
Anything wrong?
I hope my reply helps you
microming said:
I am using Windows 8.1
I can connect my Xperia S throught ADB under USB debugging mode.
But I cannot do the same thing in TWRP.
Anything wrong?
Click to expand...
Click to collapse
It is because the TWRP version which you use doesn't seem to support ADB. Try the same using CWM
rockstar.dj364 said:
It is because the TWRP version which you use doesn't seem to support ADB. Try the same using CWM
Click to expand...
Click to collapse
or perhaps you need to install the drivers. download flashtool, install flashtool, boot to disabling driver signature in win8 (google how to do this), install flashtool's driver (i chose everything that has xperia s in it ), reboot your phone to twrp, plug your phone to pc. open device manager, then you'll see that there's exclamation mark in xperia s device, choose install/update driver, choose browser my computer, choose let me pick, choose android adb (sony adb). then simply type adb devices in cmd to test it.
that's all. perhaps there are some steps that arent necessary, but that's how i remember i done it.
good luck

Rooted phone, OTA update causes bootloop

All of the drivers are installed on this PC(Windows 10), and it recognizes it as connected in the device manager but it doesn't show up as a drive. ADB doesn't recognize the device so most methods shown here don't work. And the Microsd install doesn't work either(it gives an error shortly after you press power to go into recovery mode). So I'm not sure what else to do. Any hints or suggestions. It's a Z00A device.
Thanks!
Follow this link to add proper drivers to be recognized by sideload and then do adb sideload the whole firmware if you can enter into fastboot.
For bootloop issues,busybox,xposed and viper4fx have to be uninstalled and reinstalled. Good luck.
Grid4 said:
Follow this link to add proper drivers to be recognized by sideload and then do adb sideload the whole firmware if you can enter into fastboot.
For bootloop issues,busybox,xposed and viper4fx have to be uninstalled and reinstalled. Good luck.
Click to expand...
Click to collapse
I downloaded the drivers a month ago when I was rooting the phone in the first place, it worked and was recognized. Are you saying to download additional drivers? Just want to make sure I'm going down the right path.
MRomeo99 said:
I downloaded the drivers a month ago when I was rooting the phone in the first place, it worked and was recognized. Are you saying to download additional drivers? Just want to make sure I'm going down the right path.
Click to expand...
Click to collapse
If you have drivers installed then follow 2nd last post for the pc to recognize phone when adb sideload is started.
Read entire thread as people have gone through what you are facing now.

Not able to flash factory rom via adb sideload!!!

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.

Categories

Resources