How do I sideload? - OnePlus 3 Questions & Answers

I have ADB installed, Android SDK.
I've tried to sideload and I get the error message "can't read".
Should I be changing the directory in terminal?
This is frustrating.
Thanks.

Anyone? Lol

koooba said:
Anyone? Lol
Click to expand...
Click to collapse
Is your phone coming up after using the command ADB devices?
What are you trying to sideload

No for whatever reason it's not.
I have the drivers installed, debugging on phone set.
Didn't list when I type advice devices.
What directory should terminal be in?
Wondering if I'm in the wrong directory perhaps?
Thanks

ADB could be anywhere and it'll work, double check the drivers and make sure the ADB drivers are installed and not just the MTP drivers.
What are you sideloading btw?

ADB can be anywhere, okay good to know. Thanks.
I'm trying to sideload Oxygen 3.2.1 since I'm having microphone issues - people can't hear me sometimes or my voice gets all messed up.
Apparently sideloading this update fixes this issue, at least for a few people it did.
When I connect the phone to the computer in regular mode, the device is listed.
When I go into RECOVERY mode with the phone, the computer doesn't find the device at all.
I'm going by the OnePlus instructions to turn it off and go into this mode.
http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_3.2.1/

unlock bootloader
install twrp
make Nandroid Backup
download FreedomOS 3.2.1
move to phone
Wipe Caches and system, no need to wipe data (in TWRP)
Install FreedomOS ( u may need to redownload SU and flash manually if not working in FreedomOS Aroma)
Done... If still issues do a clean flash, go to twrp and Advance Wipe (Caches, Data, System) DO NOT DO STORAGE!!!!
No this will not Void your warranty with OnePlus
Click here for better instructions

Thanks Brad, first I'd like to try sideload method first if at all possible.
I can't figure out why the computer won't recognize the device in RECOVERY MODE...? Tried everything, I have to be doing something wrong.
Drivers are okay when it's not in recovery mode
The weird thing is, when the phone is OFF and plugged into the computer, the computer recognizes the device when I type "adb devices".... WTH????

koooba said:
Thanks Brad, first I'd like to try sideload method first if at all possible.
I can't figure out why the computer won't recognize the device in RECOVERY MODE...? Tried everything, I have to be doing something wrong.
Drivers are okay when it's not in recovery mode
The weird thing is, when the phone is OFF and plugged into the computer, the computer recognizes the device when I type "adb devices".... WTH????
Click to expand...
Click to collapse
what drivers did u install, so when u type "adb devices" nothing at all comes up?

I installed the drivers that are on the phone when you plug it in.
When the phone is on and plugged into the computer, it recognizes it.
This is what I get -> http://imgur.com/B3a8AMg
When I turn it off and plug it in, it recognizes the device.
When I'm in recovery mode, it doesn't recognize it at all.

i am not sure how stock recovery works, but if u are in fastboot mode, does it recognize?
with it unathurized that means u did not check the box on the phone when plugged in to ur computer.... u should get this on your phone when booted into the OS
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i would try to boot into fastboot mode and push the file to ur phone and install via zip in stock recovery
and try this: http://forum.xda-developers.com/showthread.php?p=48915118#post48915118

I checked that box off, yes.
I'm about to give up, now it's not even showing a "storage" folder at all when plugged in.
Cannot even copy files into the phone, no storage showing.
OP, so many problems and it's only 4 days old.

anyone, please

Related

KFU stuck in fastboot

Okay guys, I'm trying to root my Fire 6.3 using KFU 0.9.5 (on Win7 Ultimate). I installed the drivers correctly and device manager shows "Android Composite ADB Interface". So I load up KFU and it says:
ADB Status: Online
Boot Status: Unknown
If I hit option 2 to install Perm Root, it gets to the part where it checks for twrp.img, then sets to fastboot mode. The kindle does reboot into fastboot, but then gets stuck on the "Kindle Fire" logo. Also, KFU just sits there waiting. See screenshot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If I terminate the batch, then rerun KFU, goto Bootmode Menu and set to Normal, I can get the kindle to reboot back to normal mode and all is good. I've tried searching the forum and all through Vashypooh's thread here, tried various tricks, but still have been unable to get it to work. Tried different USB ports, different cables (none are kindle oem), still nothing. Anyone else have this issue or know a way to fix it?
You could install twrp manually.
Get into fastboot mode (4002)
Shift + right click on your KFU "tools" folder containing fastboot.exe
Select the option that says something to the effect of "Run as command"
In the command window that pops up, enter:
fastboot -i 0x1949 flash recovery /path/to/twrp.img
!!VERY IMPORTANT!! Make sure you use that command with the twrp that comes with KFU. Accidentally using it on an older version could cause problems that you don't want to deal with.
When finished, reboot and change your bootmode back to normal.
soupmagnet said:
fastboot -i 0x1949 flash recovery /path/to/twrp.img
Click to expand...
Click to collapse
Tried this, it just said waiting for devices. One thing I noticed is when it's in fastboot, it doesn't even show in device manager. I read in a post about a separate driver for fastboot. Anyway, now it's stuck in fastboot...trying to get it back into normal mode.
You must be in fastboot mode and at the Kindle Fire logo/yellow triangle before issuing the command.
If that doesn't work hold the power button until your device shuts down and enter the command again. Turn it back on when it says 'waiting for device"
If that doesn't work, it is a driver failure. Uninstall/delete/reinstall your drivers and try again.
[Edit:] There are no separate drivers for fastboot
I switched to a different USB port and was able to use KFU to get it back to normal mode. I tried switching back to fastboot and this time it does show up in device manager in fastboot, but not with the yellow ! on it. It shows up as "Android ADB Interface". Running fastboot devices gives me a blank list.
I'm starting to wonder if it's the cable I'm using. It's my transfer cable for my EVO Design. Wondering if I should just get a factory cable and see if that fixes the problem.
Just because Windows says the drivers are there doesn't mean they're working properly. It is a well known issue with Windows and KFU.
Uninstall/delete/reinstall
[Edit:] You may have to do it twenty times or so, be patient with it.

[q] fastboot issue

hi there. ive search so many threads on how to enter fastboot.
there got several techniques but none are worked on my phone
im using xperia arc s
my phone is rooted and the bootloader is unlocked.
it just mebe because of there got too many threads and too many suggestions and method that makes me blurr and kinda not understand even a thing.
i really hope that someone can discuss n explain it in details on how to enter fastboot and flash custom kernel..
thank you so much
Connect the one end of the USB cable to your computer. Then while holding the menu button on your arc s (the right one) connect the other end of the USB cable on your phone. Keep the button pressed until the LED turning blue
Carl_Arc_S said:
hi there. ive search so many threads on how to enter fastboot.
there got several techniques but none are worked on my phone
im using xperia arc s
my phone is rooted and the bootloader is unlocked.
it just mebe because of there got too many threads and too many suggestions and method that makes me blurr and kinda not understand even a thing.
i really hope that someone can discuss n explain it in details on how to enter fastboot and flash custom kernel..
thank you so much
Click to expand...
Click to collapse
1) Download custom kernel in .img format. Put kernel file in fastboot folder.
2) Turn-off phone.
3) Press and hold "Menu" button, then connect phone to computer through USB cable. (LED will turn to blue color, means in fastboot mode)
4) If you using Windows 7, press and hold "Shift" button and right click mouse on fastboot folder. Select "Open command window here"
5) At command prompt window, key-in "fastboot flash boot C:\fastboot\CUSTOM KERNEL NAME.img", click "enter".
Remark1: If you put fastboot folder at D drive, then change C:\ to D:\
Remark2: example: custom kernel name is Arc_OC.img, then type C:\fastboot\Arc_OC.img
6) It will start flash custom kernel.
7) Reboot phone.
8) Done.
Personally, I've always had problems with fastboot working properly for me (possibly) due to some driver errors, which unfortunately refused to be fixed. So, I've always used flashtools instead, and frankly, it may be more simple for beginners. So, here are the steps if you wish to utilise this method instead.
1) Ensure that you've got the latest version of Flashtool.
2) Download and install the required fastboot drivers by going to your drivers folder in the Flashtools folder and running Flashtool-drivers.exe. You do not need to do this if you already have them.
3) Press and hold the menu button while connecting to the PC through USB. Ensure that the LED light turns, and stays blue for the duration of this process. This signals that the phone is in fastboot mode.
4) Return to the main screen (with the logs) and click on the lightning icon near the top left. This is the mode selector. Select fastboot mode and you'll be taken to a screen that looks like this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5) Click on 'CHECK Current Device Status' and ensure that the log states your device is in fastboot mode.
6) Click on 'Select kernel to Flash' and direct it to the folder where your .img file is stored. Check the logs to know when your flashing is successful, though it should only take a few seconds at most.
And with this, your kernel should be successfully flashed. If it doesn't, then check if you have the right drivers installed, or if you did everything right.

[Q] one x doesnt recognize usb in fastboot mode.

Hello,
ive been trying to change rom (not the first time),
and while in fastboot mode
any trying to burn boot.img, but in order to do that I must open the usb thruogh fastboot mode,
and my phone say it cant open the USB.
is it a problem with the sense 5?
ive downloaded again the htc sync manager.
and I can load the usb from the when the phone is on.
how can I fix it?
thanks for reading!
Download and unzip the attachement.
Open a command prompt to that folder.
Connect your device
Set it in fastboot mode
Type "fastboot devices"
Tell me what you see.
Actually sounds like you are referring to "failed to open usb master mode" and if that is the case it is simply because you have the cable plugged in when you are switching between hboot and fastboot. each time you want to switch, pull out the cable then reconnect when you have changed modes
webpatrick said:
Download and unzip the attachement.
Open a command prompt to that folder.
Connect your device
Set it in fastboot mode
Type "fastboot devices"
Tell me what you see.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://imageshack.us/f/811/wm6o.jpg/
nogotaclue said:
Actually sounds like you are referring to "failed to open usb master mode" and if that is the case it is simply because you have the cable plugged in when you are switching between hboot and fastboot. each time you want to switch, pull out the cable then reconnect when you have changed modes
Click to expand...
Click to collapse
It doesnt says now there is a problem with the usb, but it still wont load it on computer.
arnon124 said:
http://imageshack.us/f/811/wm6o.jpg/
It doesnt says now there is a problem with the usb, but it still wont load it on computer.
Click to expand...
Click to collapse
Your device is recognized by fastboot, so you can flash a boot.img, the command is:
Code:
fastboot flash boot boot.img
Make sure you have copied the boot.img to the fastboot folder on your PC.
You cannot see your device in windows explorer when you are in fastboot.
Edit: You can in recovery when you mount your storage.
webpatrick said:
Your device is recognized by fastboot, so you can flash a boot.img, the command is:
Code:
fastboot flash boot boot.img
Make sure you have copied the boot.img to the fastboot folder on your PC.
You cannot see your device in windows explorer when you are in fastboot.
Edit: You can in recovery when you mount your storage.
Click to expand...
Click to collapse
finished changing the rom, thanks alot for helping!

fire 2 will not boot stuck in boot screen

my kindle fire 2 is stuck in the blue whit fire-fire screen
I can access the twrp recovery but after a incorrect wipe i have no android or so i am assuming.
i have installed the Google usb drivers through adb but the tablet will not show up i explorer
it will show as a android device but will not load anything else.
i have also booted into the twrp and attempted to mount it and it didn't work
lastly i have tried to use a fastboot cable. i get a screen on the device that says fastboot and what looks like a stoplight with the green blinking but again will not show up in explorer
dyson77 said:
my kindle fire 2 is stuck in the blue whit fire-fire screen
I can access the twrp recovery but after a incorrect wipe i have no android or so i am assuming.
i have installed the Google usb drivers through adb but the tablet will not show up i explorer
it will show as a android device but will not load anything else.
i have also booted into the twrp and attempted to mount it and it didn't work
lastly i have tried to use a fastboot cable. i get a screen on the device that says fastboot and what looks like a stoplight with the green blinking but again will not show up in explorer
Click to expand...
Click to collapse
First check you have fastboot drivers installed correctly:
Plug the cable into your device and then the computer. Reboot the Kindle. It *SHOULD* show a Fastboot screen. Once at the screen use this command on your computer:
fastboot -i 0x1949 devices
You should see something like this:
0123456789ABCDEF
Click to expand...
Click to collapse
Then enter these commands one at a time
fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
fastboot -i 0x1949 flash boot otter2-freedom-boot-10.4.6.img
fastboot -i 0x1949 flash recovery otter2-twrp-2.6.3.0-recovery.img
fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
kidicarus1602 said:
First check you have fastboot drivers installed correctly:
Then enter these commands one at a time
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B0q-ce_LYNLFQW16QWFEbDlKSUk/edit?usp=sharing
the unit wont show up in explorer at all,I have tried to run the command listed and it just says waiting for device.
I have tried rebooting into recovery reboot and still locks up
any other ideas
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
this is what device manager says
dyson77 said:
View attachment 2709099
View attachment 2709100
View attachment 2709101
this is what device manager says
Click to expand...
Click to collapse
any ideas?
Manually install the drivers.
-》Sent from my mind to your screen.
i have installed the google and adb drivers what other ones are there
dyson77 said:
i have installed the google and adb drivers what other ones are there
Click to expand...
Click to collapse
MANUALLY install the adb drivers.
-》Sent from my mind to your screen.
ok I have manually installed the drivers.
it then was showing up as a Otter-2
I then went through the same steps to add the drivers for it as a google usb driver.
but its still not showing up in my explorer and when i do a adb devices it doesn't show up
mind you that was all with the fastboot cable
when I hook it up with a standard usb and gho into the teamwin twrp it shows as a Kindle fire 2
and adb devices finds it as 0123456789abcdef
see attached pics
Ok I have been able to push a file to the fire 2 but the only file that will install is cm-10.1.3-otter2.zip
when i try to install anything else i get a error 7 and then it wont boot at all when i reboot it just goes into a loop.
would like to put cm 11 on there seems a little better
You need to update your recovery.
Sent from my Galaxy Nexus using Tapatalk
Bro you are in the wrong section. I repoted you so this thread should be in the right section soon.

Fastbooting android whose recovery is not opening.

While trying to root my redmi 1s, i accidentally pressed a wrong button due to which it seemed like if recovery is no longer functioning.
The mobile is getting struck at mi logo and is not proceeding forward.
Pressing volume down+power button successfully opens fastboot screen. Earlier when I was connecting it to mi suite on pc, i was able to flash. But due to incomplete charged battery, flashing procedure stopped. After the recent windows update, mi pc suite is recognizing the android but is not able to flash it. It pops out a dialogue box saying "cant flash the device". Any idea what can i do now?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
akshat2119 said:
While trying to root my redmi 1s, i accidentally pressed a wrong button due to which it seemed like if recovery is no longer functioning.
The mobile is getting struck at mi logo and is not proceeding forward.
Pressing volume down+power button successfully opens fastboot screen. Earlier when I was connecting it to mi suite on pc, i was able to flash. But due to incomplete charged battery, flashing procedure stopped. After the recent windows update, mi pc suite is recognizing the android but is not able to flash it. It pops out a dialogue box saying "cant flash the device". Any idea what can i do now?
Click to expand...
Click to collapse
If your phone boots into fastboot, then try installing twrp recovery and then flash the rom you wish.
vicky romero said:
If your phone boots into fastboot, then try installing twrp recovery and then flash the rom you wish.
Click to expand...
Click to collapse
but how to flash twrp via fastboot. i.e. which software would recognize fastbooting android?
akshat2119 said:
but how to flash twrp via fastboot. i.e. which software would recognize fastbooting android?
Click to expand...
Click to collapse
Flashing twrp is done by fastboot using adb tools. First install the USB drivers of your phone. You can simply google them. Then go to this link https://drive.google.com/open?id=0B_43Fi9T_yqvUy1jOWk0cnJyZEk
and download the four files in the adb folder. Now download the latest twrp image i.e, twrp 3.0.0-0 from this link
https://dl.twrp.me/armani/
keep the adb tools i.e, the four files you had downloaded and the twrp image in the same folder. Rename the twrp 3.0.0-0 to recovery.img. Now hold shift key and press right click on your mouse. From there select open command window here. Now open fastboot and connect your phone through Usb and type this code
Code:
fastboot devices
This is to check wheather your device is connected or not. If it's connected then it will show some code. After that type this code
Code:
fastboot flash recovery recovery.img
That's it twrp will be flashed right away. Then you can flash MIUI or any other custom rom.
Thank you
vicky romero said:
Flashing twrp is done by fastboot using adb tools. First install the USB drivers of your phone. You can simply google them. Then go to this link https://drive.google.com/open?id=0B_43Fi9T_yqvUy1jOWk0cnJyZEk
and download the four files in the adb folder. Now download the latest twrp image i.e, twrp 3.0.0-0 from this link
https://dl.twrp.me/armani/
keep the adb tools i.e, the four files you had downloaded and the twrp image in the same folder. Rename the twrp 3.0.0-0 to recovery.img. Now hold shift key and press right click on your mouse. From there select open command window here. Now open fastboot and connect your phone through Usb and type this code
Code:
fastboot devices
This is to check wheather your device is connected or not. If it's connected then it will show some code. After that type this code
Code:
fastboot flash recovery recovery.img
That's it twrp will be flashed right away. Then you can flash MIUI or any other custom rom.
Click to expand...
Click to collapse
A big thank you. I owe you for helping out. By the way after installing recovery I tried downloading rom(both armani which was earlier working and miui official). The script gets sideloaded successfully but again the operating system is not loading. ie mobile is still struck in bootloader
akshat2119 said:
A big thank you. I owe you for helping out. By the way after installing recovery I tried downloading rom(both armani which was earlier working and miui official). The script gets sideloaded successfully but again the operating system is not loading. ie mobile is still struck in bootloader
Click to expand...
Click to collapse
Flash this firmware before installing the rom. It'll fix the bootloops.
https://www.androidfilehost.com/?fid=24052804347850305
Thanks @fefifofum for this flashable zip.

Categories

Resources