ADB Sideloading won't work - device not recognized as ADB device in windows or in device manager. Custom recovery works. Won't boot to Android (system), OS corrupt. How to move an ROM ZIP onto system to flash?
Like the title says.
Things that work: Custom recovery.
Things that don't work: Android OS (system). Sideloading or anything ADB (no adb device recognized in cmd when using adb commands). Device not recognized in Device Manager, even though Google USB drivers were installed (from the android SDK) and the LG universal USB drivers were installed. Both uninstalled and reinstalled to try to verify not corrupt. Download mode won't work as the driver install fails.
any ideas?
Hi there,
Reading through this thread and asking there may help you: [HELP THREAD][Noob Friendly] LG G2 Ask any question
Related
Alright, here goes my first post. I have lingered in these forums for awhile, and have always found what I needed. This is the first time my searching on here, as well as google, has let me down.
To clarify, if I connect to my computer and have USB Mass Storage on, I can see it, move files to it and everything. My problem is, I am using my old phone (P500) to learn and practice ADB (I own a GNEX), and would like to install CWM via ADB, but I need to move files to the root of my sd.. but my phone won't show up if it's in debugging mode!
I have the drivers installed, and used a toolkit to root (worked fine, no errors). Am I missing something here or is there another issue?
Info:
Windows 7 64bit
Telus Mobility (Canada)
Model: LG-P500h
Android 2.3.3 (stock)
stock kernel
MissBizz said:
Alright, here goes my first post. I have lingered in these forums for awhile, and have always found what I needed. This is the first time my searching on here, as well as google, has let me down.
To clarify, if I connect to my computer and have USB Mass Storage on, I can see it, move files to it and everything. My problem is, I am using my old phone (P500) to learn and practice ADB (I own a GNEX), and would like to install CWM via ADB, but I need to move files to the root of my sd.. but my phone won't show up if it's in debugging mode!
I have the drivers installed, and used a toolkit to root (worked fine, no errors). Am I missing something here or is there another issue?
Info:
Windows 7 64bit
Telus Mobility (Canada)
Model: LG-P500h
Android 2.3.3 (stock)
stock kernel
Click to expand...
Click to collapse
Since the device is not getting detected with USB Debugging enabled it's safe to assume a bad driver installation. To verify tho, enable USB Debugging on the device and connect it to your PC. Go to Device Manager. Somewhere towards the top, assuming the drivers were installed will be a device "ADB Interface" with a subitem "Android Platform Sooner Single ADB Interface" or something similiar. If the "ADB Interface" item isn't there then the drivers weren't installed correctly. Uninstall them. Reboot computer. Rerun driver installation program. When it finished, reboot your PC. Power off the device. Connect it to your PC. Power on the device and let all drivers install. You should be good to go from here.
If you'd like a good known set of LGE USB drivers, download Android Flash Recovery, link is in my signature. Hope this helps.
EDIT:
Oh, and Welcome to XDA
Installing Cyanmod on N5
When following instructions from wiki
Place the CyanogenMod rom .zip file on the root of the SD card using adb:
Transfer your file(s): adb push YOURROMZIP.zip /sdcard/
Click to expand...
Click to collapse
I get error:device cannot be found.
fastboot device command lists my serial number, adb kill/resume server commands work fine.
Is the wiki missing something?
I have also attempted this step.
On some devices, the zip file can be copied to the device using standard USB Mass Storage or MTP support. Boot the device normally and transfer the file to it.
Click to expand...
Click to collapse
However after following the steps given in the Cyanmod wiki CWM version 6.04 installs the latest nightly and boots to a never ending load screen.
Any help much appreciated,
Cheers.
Are you booted into cwm recovery when using adb?
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
No the wiki states to boot back into recovery mode once the .img has been moved over to the sdcard so I am in fastboot mode when issuing the push command.
I did try this while in CWM recovery however Windows 7 looses the Android Bootloader Interface drivers and looses the device altogether. I then have the yellow exclamation mark over Android in Device manager.
Did you wipe data, cache and dalvik in cwm before flashing the zip?
chdgzgfbzc said:
No the wiki states to boot back into recovery mode once the .img has been moved over to the sdcard so I am in fastboot mode when issuing the push command.
I did try this while in CWM recovery however Windows 7 looses the Android Bootloader Interface drivers and looses the device altogether. I then have the yellow exclamation mark over Android in Device manager.
Click to expand...
Click to collapse
You can only adb push in recovery or android. Not fastboot. Plus unless you have a custom kernel with insecure adb support, you can't use android either.
Your recovery issue seems you have a windows driver issue.
I had similar issues with cwm. I had to install drivers using mskip's toolkit. I normally would never advocate using a toolkit but for me it was the only way to get cwm recognised in windows
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Yeah no doubt its a driver issue, but it is strange the USB drivers provided by google are not sufficient, unless the issue is with CWM.
I can install drivers from device manager whilst in CWM recovery, but I have so far found no source that states what drivers you need.
But yeah all cache etc wiped before install.
chdgzgfbzc said:
Yeah no doubt its a driver issue, but it is strange the USB drivers provided by google are not sufficient, unless the issue is with CWM.
I can install drivers from device manager whilst in CWM recovery, but I have so far found no source that states what drivers you need.
But yeah all cache etc wiped before install.
Click to expand...
Click to collapse
I also had a similar issue where drivers for fastboot worked fine but I couldn't get adb to work. What worked for me where the android naked usb drivers.
jd1639 said:
I also had a similar issue where drivers for fastboot worked fine but I couldn't get adb to work. What worked for me where the android naked usb drivers.
Click to expand...
Click to collapse
Cheers man, will give them a try.
jd1639 said:
I also had a similar issue where drivers for fastboot worked fine but I couldn't get adb to work. What worked for me where the android naked usb drivers.
Click to expand...
Click to collapse
for me too. universal naked driver v.0.73. i did not need to install them beforehand either. i unzipped it on desktop, when got the warning that device can not be found, went to device manager, sure enough yellow icon on nexus 5. update driver, pointed to unzipped folder on desktop, done.
akmsr said:
for me too. universal naked driver v.0.73. i did not need to install them beforehand either. i unzipped it on desktop, when got the warning that device can not be found, went to device manager, sure enough yellow icon on nexus 5. update driver, pointed to unzipped folder on desktop, done.
Click to expand...
Click to collapse
Yip the drivers worked sure enough for issuing commands in recovery.
Now after install and restart cyanogenmod is frozen on the boot screen.
Windows device manager shows Portable Device>Nexus 5 with yellow exclamation mark and "This device cannot start. (Code 10)" under properties.
OH WELL.
using
cm-11-20131229-NIGHTLY-hammerhead
Using MotoTool AIO, I put TWRP on my Moto G. Problem is, I don't have a ROM on the phone. How can I get one onto the phone (or get back to default)?!
Been years since I rooted a phone. 95% noob. And no, I didn't make a backup :/
* Fastboot can see my device, but Adb can't.
* After trying to fix it all night, the batter is at 0% and it doesn't want to take a charge.
Thank you!
You need to sideload a ROM and GAPPS. Advanced -> ADB Sideload, this should activate ADB mode, you need to have Motorola drivers installed and the phone should appear on ADB devices.
Use an otg cable with CWM.
GOT IT!! After way too long messing around.
For anyone else's reference:
The adb drivers weren't installed right. I had to go to the Device Manager > Select the phone > update driver software > "Browse my computer for driver software install from computer" > "Let me pick from a list of device drivers on my computer"
Then, I chose the ADB composite driver. Windows warned me it might not be right, but I went ahead.
From there, I followed the detailed instructions for Cyanogen MOD here, using their CWM loader and then side-loading the MOD and Gapps.
Thanks for your help!!
I was trying to install a couple of different custom roms on my phone. I have TWRP as the recovery tool. I tried a rom called ATT Buckeye and it seems to have bricked the phone. I don't have any other roms copied to the internal storage to try to flash them. I can reset to factory defaults both through holding the volume and power down and through TWRP, but I'm not able to start into a system. The only thing I can do is boot into TWRP 2.7.0.0
I saw that I can copy files using ADB, but it says "device not found" when I am connected and run adb shell. I have the drivers from LG's website installed, but there is a yellow exclamation mark on it in device manager. I found a thread where it says that I should be able to get the drivers from the Android developer SDK. I also found the individual download for Google USB drivers. In both cases, Windows isn't able to find any drivers in the USB drivers folder. I'm not sure what else I can do to revive my phone. At this point, I'd like to just get it working again any way possible.
I used this to fix my phone http://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076
Then I was able to load Cloudy G2 http://forum.xda-developers.com/showthread.php?t=2783192
Good to go
Hello xda-members,
I've been searching for 4 hours now and every time I try to use ADB along with my device I get the "unauthorized" message and can't use it.
I've been searching for answers all across the internet and tried nearly everything I could find, e.g.:
1. In windows cmd:
Code:
adb kill-server
Code:
abd start-server
2. Unplug phone
3. Reinstall drivers
4. Reboot phone / PC
5. Disable and Enable USB-Debugging-Mode
I read in several threads on other sites, that the adb key is the problem (there's no "authorization"-pop-up appearing on my phone, when connecting it via usb, furthermore I can't revoke debug permissions in developer settings), so I tried also:
1. delete .android. folder on my PC (C://User/me/.android.)
2. Copy the adb_key file to my phone (/data/misc/adb)
None of that worked. None.
I'm really desperate since I need ADB for several important reasons (to me important). I don't know when this problem occured first. When I bought the phone ADB worked fine. I don't know what to do anymore.
Technical information:
- Windows 10 PC
- Latest LG drivers, latest adb version
Phone:
- LG G4 H815 V20C (Marshmallow)
- Rooted, TWRP installed, SuperSU working without problems
So please, if anybody out there has had the same problems help me!!!
Follow_and_Feel said:
Hello xda-members,
I've been searching for 4 hours now and every time I try to use ADB along with my device I get the "unauthorized" message and can't use it.
I've been searching for answers all across the internet and tried nearly everything I could find, e.g.:
1. In windows cmd:
Code:
adb kill-server
Code:
abd start-server
2. Unplug phone
3. Reinstall drivers
4. Reboot phone / PC
5. Disable and Enable USB-Debugging-Mode
I read in several threads on other sites, that the adb key is the problem (there's no "authorization"-pop-up appearing on my phone, when connecting it via usb, furthermore I can't revoke debug permissions in developer settings), so I tried also:
1. delete .android. folder on my PC (C://User/me/.android.)
2. Copy the adb_key file to my phone (/data/misc/adb)
None of that worked. None.
I'm really desperate since I need ADB for several important reasons (to me important). I don't know when this problem occured first. When I bought the phone ADB worked fine. I don't know what to do anymore.
Technical information:
- Windows 10 PC
- Latest LG drivers, latest adb version
Phone:
- LG G4 H815 V20C (Marshmallow)
- Rooted, TWRP installed, SuperSU working without problems
So please, if anybody out there has had the same problems help me!!!
Click to expand...
Click to collapse
Greetings,
Please read the sticky threads for this forum. XDA Assist is for helping NEW members find their way, not a help desk for Senior members who should know where to ask for help.
Thread closed.