Hello,
So a few days ago my nexus 4 got a virus that started hijacking my text messages and made it so that the phone would not mount as mass storage to a computer. Also adb wouldn't work and i did have usb debug on. Anyway so I have TWRP installed so I just did a storage format totally wiping android and the virus from the phone. After I did that I tried pushing a nandroid backup that I have over and adb told me that the device was not found. I tried pushing the file in the bootloader, the recovery and when its trying to boot an android that's not there. Then I tried re-installing all of the usb drivers and adb. Still nothing. The I tried the adb sideload in TWRP. Still nothing. So dose anyone have any ideas about what this could be?
Thanks a bunch,
You can't use adb commands in fastboot. You should be able to do an adb push while sitting in recovery; don't use sideload unless you are sideloading something. If you can't get it to work, flash a rom and do it from within android.
Related
So I goofed really hard. was wiping my n7 and re-installing http://forum.xda-developers.com/showthread.php?t=2077396 but when I went to wipe the cache and I accidentally wiped my entire n7 fresh so there went my zip with the rom and gapps. I can still get into recovery team win recovery project v2.5.0.0) and bootloader but I cant access my storage so re-put it on and when I try and use the ADB sideload wont work. im at a loss everything I see online needs me to be in developer mode which I cant get to. Anyone have a way I can fix this?
how many of these do we need to see every day?
fix your ADB issues/drivers FIRST!
usb debugging has nothing to do with recovery, usb debugging ONLY applies to the booted OS. custom recoveries have a working adb daemon for you to attach to.
get the right drivers for ADB and either adb sideload or adb push a new rom to /data/media/0
Or connect a usb stick with usb otg and install a new rom or a nandroid backup from there. Or do a factory reset with fastboot.
Pirateghost said:
how many of these do we need to see every day?
fix your ADB issues/drivers FIRST!
usb debugging has nothing to do with recovery, usb debugging ONLY applies to the booted OS. custom recoveries have a working adb daemon for you to attach to.
get the right drivers for ADB and either adb sideload or adb push a new rom to /data/media/0
Click to expand...
Click to collapse
Or fastboot, if there are adb issues (generally became my method of choice on some Android devices because of weird adb quirks). Either way, agree with the sentiment.
well,
I have a LG G2 d805/802 with TWRP recovery. I just wipe all data, internal storage, EVERYTHING...
I read a lot about ADB sideload, but it just don't start on phone (starting adb sideload feature...), but windows can recognize my device normally.
When I sideload the ROM.zip nothing happens. I think I have to make the feature starts.
Other way is to try flash from OTG, but my TWRP 2.6.3.2 just don't recognized my otg-memory.
Any ideias for what I supposed to do?
note: I think my device is not rooted.
1. If you device is not rooted, how could you get custom recovery on your device?
2. I don't think "sideload" is an universal adb command, meaning it supported on some devices and some others don't.
3. If "sideload" doesn't work in your case, why not just push the .zip file over and flash it using custom recovery?
gabrieelheringeer said:
well,
I have a LG G2 d805/802 with TWRP recovery. I just wipe all data, internal storage, EVERYTHING...
I read a lot about ADB sideload, but it just don't start on phone (starting adb sideload feature...), but windows can recognize my device normally.
When I sideload the ROM.zip nothing happens. I think I have to make the feature starts.
Other way is to try flash from OTG, but my TWRP 2.6.3.2 just don't recognized my otg-memory.
Any ideias for what I supposed to do?
note: I think my device is not rooted.
Click to expand...
Click to collapse
I gave sideload a good effort last week for a couple hours on Verizon G2 VS980 after doing the same thing you did. Eventually, I gave up and just did an adb push command to copy the file to my phone and then installed it using twrp as votinh suggests.
SOLVED
I realized the phone will never actually start the adb sideload feature. so, when i put the "abd sideload file.zip" command i just wait. it take a few minutes to start the process.
Hi guys,
yesterday I accidentally wiped my phone and the rom's in it. So now I have to somehow get a rom on the sd card so I can flash it. Recovery works (twrp), fastboot mode works, however I can't use adb to push zips on to my sd card, I've tried on 3 different PC's 2xWindows and one mac
fastboot finds my device and adb doesn't. I've tried configuring the adb_usb.ini file with the Vendor ID of my device which I found, but adb still doesn't find it. My system is wiped so I don't have a system to go in and transfer files the normal way and my backups have been deleted so that isnt working either. I've also tried to return my phone to 100% stock with a tool I found on the OnePlus forums Thread from forum , however this didn't work fastboot crashes midway. My only option is to flash an .img file containing some system rom(which I didn't find) so I can then load files to my sd card or to get adb to work in some way so I can push the zips on to the sd card. If you can help in any way because I'm all out of ideas. It's been two hard days and this is the last thing I'm trying, otherwise I have to buy a new phone.
It's not soft bricked but I think the first method shown here could work:
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Sounds like your trying to access your phone using ADB in fastboot, this will not work. For ADB recovery, you have to enter TWRP or CWM and choose ADB sideload mode to activate phone for receiving of ROM zip using adb sideload romfile.zip. Fastboot is like EFI or BIOS boot prompt on a PC, and ADB is like a variant of GRUB bootloader with support for PXE installing the phones OS by ways of adb sideload (as reference).
Ok, I'm going to start by explaining everything I did up to this point to eliminate any troubleshooting sugggestions i may have already done.
I rooted and installed recovery the same way everyone else did. After a couple of days, I tried to install a ROM but im assuming i was encrypted because i was stuck in a loop that would only boot me into TWRP. Did my research and took the necessary steps to get around that and decrypt and boot into the new ROM.. FINALLY!!! Only one problem, this rom doesn't have Super SU installed, Alright... so i download the proper Super SU build and put it on my Micro SD card and try to boot into TWRP to flash....
This is where the problem begins. I never get the prompt to authorize my PC from my phone to allow anything, and i never did each time i reset. I'm almost certain the adb on this rom is messed up, i've wiped about 4-5 times to re-enable usb debugging from scratch in order to adb or fastboot into recovery via command prompt, however when i try adb, i get that unauthorized error an there's no option on the LG V20 to revoke under developer settings. Fastboot i just get the same "waiting for device" message. Also keep in mind that i set it to photo mode, every mode that was available and nothing. Tried different USB Cords and did this on both my laptop and my PC at work
I've tried uninstalling and reinstalling all of the drivers, re-installed the latest version of adb and fastboot to my PC, that didn't work either. Tried deleting the adbkeys file in the .android folder and still nothing.
When i try to boot in recovery manually, i just get the wipe data option and when i click yes to everything, it actually wipes my data. I'm unable to reflash TWRP because I can't access ADB or Fastboot due to the unauthorized error.
Someone, PLEASE HELP!!!!
any luck?
ahq1216 said:
Ok, I'm going to start by explaining everything I did up to this point to eliminate any troubleshooting sugggestions i may have already done.
I rooted and installed recovery the same way everyone else did. After a couple of days, I tried to install a ROM but im assuming i was encrypted because i was stuck in a loop that would only boot me into TWRP. Did my research and took the necessary steps to get around that and decrypt and boot into the new ROM.. FINALLY!!! Only one problem, this rom doesn't have Super SU installed, Alright... so i download the proper Super SU build and put it on my Micro SD card and try to boot into TWRP to flash....
This is where the problem begins. I never get the prompt to authorize my PC from my phone to allow anything, and i never did each time i reset. I'm almost certain the adb on this rom is messed up, i've wiped about 4-5 times to re-enable usb debugging from scratch in order to adb or fastboot into recovery via command prompt, however when i try adb, i get that unauthorized error an there's no option on the LG V20 to revoke under developer settings. Fastboot i just get the same "waiting for device" message. Also keep in mind that i set it to photo mode, every mode that was available and nothing. Tried different USB Cords and did this on both my laptop and my PC at work
I've tried uninstalling and reinstalling all of the drivers, re-installed the latest version of adb and fastboot to my PC, that didn't work either. Tried deleting the adbkeys file in the .android folder and still nothing.
When i try to boot in recovery manually, i just get the wipe data option and when i click yes to everything, it actually wipes my data. I'm unable to reflash TWRP because I can't access ADB or Fastboot due to the unauthorized error.
Someone, PLEASE HELP!!!!
Click to expand...
Click to collapse
different route but im in the same boat. any luck?
I fixed this shortly after. Wanted to avoid returning to stock as. The only option was you and I was on 10d. I had to go back to stock but luckily the recovery method still works.
Hello everyone,
I recently decided too install the LineageOS.
Everything went fine, but I forgot Gapps and didnt want too use my phone without them so I decided too install the ROM again but this time with the apps.
I followed the linageos guide but accidently wiped everything before I could
Code:
adb push filename.zip /sdcard/
(dunno if thats the problem)
Im using TWRP 3.1.1-1. I can get into Recovery Mode. While in fastboot modus my pc detects my phone as an OnePlus, in Recovery modus its just android.
Code:
fastboot devices
shows my serial number. OEM is unlocked.
while in recovery mode
Code:
adb push filename.zip /sdcard/
gets me
Code:
No such file or directory
Code:
adb push C:\User\...filename.zip /sdcard/
gets me
Code:
failed to copy.. remote couldnt create file
while in fastboot mode I get
Code:
no devices/emulator found
Copying by dragging the file into internal storage doesnt work neighter.
I dont know what I did different besides the wipe before the copying. Maybe the wipe deactivates USB Debugging?
Maybe someone sees where my problem is.
Thanks
r717
I guess you don't have an OTG Drive.
you could always go 100% stock again and then flash LineageOS
http://downloads.oneplus.net/oneplus-5/oneplus_5_oxygenos_4.5.13/
well first thanks for your reply. I flashed the original recovery and tried 2 sideload now. Seems to be driver problems. So I have to try every solution with Win10 and OP5 drivers I guess?
Make sure the Android drivers on your computer are up to date and also that you don't have any old drivers from a previous phone. I accidentally wiped everything on my OP5 once but when I connected it to my Windows 10 computer the OP5 was still recognized as a storage device--but I used TWRP not the stock recovery and also used the file explorer in TWRP. With the stock recovery you should still be able to side load flash the stock ROM from your computer. If you can't it's likely a driver issue.
I had once a similar issue, although not exactly this, just something with drivers.
A long process to fix was to install Linux as a virtual machine in Windows and that worked well. I could do all I needed, the phone was quickly recognized.
Virtualbox or VMware both are free/have a free version and I used Ubuntu.
Give it a try if all else fails.