I am trying to adb sideload custom rom but adb devices is not recognizing my nexus 6p. Does anyone know of a solution? I have deleted my internal storage, I have no os, am I screwed? My computer recognizes that my phone is connected, adb recognizes my phone is attached when not in recovery. The only time my phone is not attached is when in twrp recovery, when in recovery my phone shows up in device manager with an exclamation point and the message that the drivers are not installed but adb is installed.
Thank you.
blopez805 said:
I am trying to adb sideload custom rom but adb devices is not recognizing my nexus 6p. Does anyone know of a solution? I have deleted my internal storage, I have no os, am I screwed? My computer recognizes that my phone is connected, adb recognizes my phone is attached when not in recovery. The only time my phone is not attached is when in twrp recovery, when in recovery my phone shows up in device manager with an exclamation point and the message that the drivers are not installed but adb is installed.
Thank you.
Click to expand...
Click to collapse
I'm assuming you're bootloader is unlocked. If so, just flash factory images.
Sent from my Nexus 6P using Tapatalk
Related
Today, I wanted to reinstall the ROM on my Google nexus 4, and my phone was previously rooted months ago (with Google_Nexus_4_ToolKit_v2.0.0) and was installed with AOKP custom ROM. So I booted into the recovery mode, and accidentally I formatted the system, the cache, the data, etc. I thought when I connect the phone (in recovery mode) to my PC, the PC should recognize my phone and display it as a USB drive in my computer.
However, I was so wrong. With the right driver, the phone is recognized by my PC (as shown in device manager), but it won't show up as a USB drive. So I cannot put in any ROM/gapps file into the phone, I tried to use adb push to load the ROM/gapps into the phone, but I keep getting the "Read-only file system" error. I found the /storage/sdcard0/ can receive the pushed files, but in recovery mode, I cannot select these files for install.
I am now stuck in the recovery mode and cannot do anything. I need you guys help. How can I install a ROM now? thanks a million!!!!
Adb can only be used when your device is booted on android. If not then go to the boot loader and use fastboot.
Sent from my Nexus 4 using Tapatalk 2
rcholic said:
Today, I wanted to reinstall the ROM on my Google nexus 4, and my phone was previously rooted months ago (with Google_Nexus_4_ToolKit_v2.0.0) and was installed with AOKP custom ROM. So I booted into the recovery mode, and accidentally I formatted the system, the cache, the data, etc. I thought when I connect the phone (in recovery mode) to my PC, the PC should recognize my phone and display it as a USB drive in my computer.
However, I was so wrong. With the right driver, the phone is recognized by my PC (as shown in device manager), but it won't show up as a USB drive. So I cannot put in any ROM/gapps file into the phone, I tried to use adb push to load the ROM/gapps into the phone, but I keep getting the "Read-only file system" error. I found the /storage/sdcard0/ can receive the pushed files, but in recovery mode, I cannot select these files for install.
I am now stuck in the recovery mode and cannot do anything. I need you guys help. How can I install a ROM now? thanks a million!!!!
Click to expand...
Click to collapse
Of course you are able to use ADB in recovery mode. Have you tried
Code:
adb push nameoftherom.zip /sdcard/
or if you are using a recovery where you are able to use adb sideload
Code:
adb sideload nameoftherom.zip
Then it should work. Or try mounting the usb in mounts/storage -> mount usb storage
scream4cheese said:
Adb can only be used when your device is booted on android. If not then go to the boot loader and use fastboot.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Of course, it should work if the drivers are installed properly
Like others said use adb push to put a file on the device and then you can flash it with recovery.
If you don't have adb you can get it either by downloading android SDK or just downloading adb did
Sent from my Nexus 4 using xda app-developers app
Try flashing back to stock, then just root and put your ROM back on, I've had to do it once before
Sent from my Nexus 4
I flashed the wrong kernal and I'm stuck on a bootloop. I can't access my internal storage via TWRP or cant use ADB either. ADB isn't recognizing the device. Is there anyway I can come out of this without losing my data on the phone? I can see the g2 listed as Other Devices in my PC's Device Manager while plugged in. I suppose that has something to do with it. Is there some driver I need to use ADB in recovery?
sacredsoul said:
I flashed the wrong kernal and I'm stuck on a bootloop. I can't access my internal storage via TWRP or cant use ADB either. ADB isn't recognizing the device. Is there anyway I can come out of this without losing my data on the phone? I can see the g2 listed as Other Devices in my PC's Device Manager while plugged in. I suppose that has something to do with it. Is there some driver I need to use ADB in recovery?
Click to expand...
Click to collapse
not sure if you found out already but
all you have t do is go to mount and mount what uou need
sacredsoul said:
I flashed the wrong kernal and I'm stuck on a bootloop. I can't access my internal storage via TWRP or cant use ADB either. ADB isn't recognizing the device. Is there anyway I can come out of this without losing my data on the phone? I can see the g2 listed as Other Devices in my PC's Device Manager while plugged in. I suppose that has something to do with it. Is there some driver I need to use ADB in recovery?
Click to expand...
Click to collapse
http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
device manager, right click phone, update drivers, browse computer, let me pick from a list, unclick show compatible hardware, and find LGE or LG and pick the adb driver
Yes, I solved it. Got the drivers fixed.
Fun fact : If your G2 is just getting stuck at boot, turn it off for an over and try again. I stupidly flashed a zip containing a recovery using Flashify and not the boot.img and I got stuck in Fastboot mode or it'd just stuck at the boot animation. I had given up and decided to go back to stock, wiping all my photos. But thankfully the stock flash got stuck because I am using a custom kernal. I turned it off, watched some tv and tried again. Booted right back into the rom. Flashed a proper recovery using adb, got into TWRP, reflashed my rom and didn't lose any data. @autoprime got me through the process via IRC so big kudos to him!
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.
Hello,
i delete the System and Data on my LeEco Le Pro3.
TWRP is installed.
Can i flash a rom with an usb flash drive in TWRP or fastboot?
greeting gizez
Boot into TWRP and use MTP to transfer ROM file from your PC to Phone. Then flash the ROM.
I have this problem, but I can't see the phone when connected to a PC. adb sideload doesn't work (adb devices doesn't find anything). Do I need to install driver for the phone? I originally used fastboot to unlock the bootloader and flashed TWRP, then installed LineageOS and gapps just fine. I then proceeded to wipe system in TWRP (I was trying to get back to new phone setup so I can transfer stuff from old phone, which I skipped the first time).
Any idea how to get around this? I tried plugging in pen drive through an micro USB OTG and a usb-c to micro usb adapter, but it's not recognized in TWRP, either. Would very much appreciate any help!
You can get your data. First try to connect phone while is in TWRP. Your phone can be detected as file manager. Try this.
If not, check my theme;
https://forum.xda-developers.com/le-pro3/help/brick-t3609704
marik1 said:
[...]
Go Advanced -> ADB Sideload, type "adb sideload aicp_zl1_n-12.1-NIGHTLY-20170516.zip" (zip of OS should be downloaded and put into "Minimal ADB and Fastboot" installation folder with name as same as the text of command). It should let you turn on system.
[...]
Click to expand...
Click to collapse
Also "adb push" command can be helpful. Sometimes phone is not current on adb devices list, but you can also try. As i remember, target should be /sdcard/0
marik1 said:
You can get your data. First try to connect phone while is in TWRP. Your phone can be detected as file manager. Try this.
If not, check my theme;
https://forum.xda-developers.com/le-pro3/help/brick-t3609704
Also "adb push" command can be helpful. Sometimes phone is not current on adb devices list, but you can also try. As i remember, target should be /sdcard/0
Click to expand...
Click to collapse
Thanks, but unfortunately no luck. Both adb sideload and adb push said error - device '(null)' not found. It seems like the PC is not recognizing the phone. I checked device manager on the PC, it showed LEX727. I right-click and had it install the driver. It says driver successfully installed. Then device manager showed MTP device with a !. I again tried having driver installed, but this time it doesn't find any driver.
I'm at my wit's end... Any more suggestion?
TWRP and/or Minimal ADB isn't trouble here? Tried you both on main menu of TWRP and in ADB Sideload mode? You can also try do it trough bootloader, for this check my link and read all.
marik1 said:
TWRP and/or Minimal ADB isn't trouble here? Tried you both on main menu of TWRP and in ADB Sideload mode? You can also try do it trough bootloader, for this check my link and read all.
Click to expand...
Click to collapse
Actually, the problem is solved, by using another PC. This one showed LEX727 in windows explorer as soon as i plug in the phonr (in twrp). I was able to drag and drop the zip files to the phone and go on my merry way. Now back in business!
I was trying to flash the latest images on my 6P, but it's not recognized in Bootloader/Fastboot mode. It boots to the logo, then reboots into TWRP. It's recognized by adb in recovery, but if I try and boot into boot-loader, it no longer is recognized.
I have tried in Windows 10, and Linux. Previously it was recognized. I am thinking that when I flashed the latest image, I didn't enable USB debugging. But it's odd that it can be recognized in TWRP and not bootloader.
I tried wiping data, but that didn't work.
(Yes I have the latest usb drivers for both windows and linux.)
dratsablive said:
I was trying to flash the latest images on my 6P, but it's not recognized in Bootloader/Fastboot mode. It boots to the logo, then reboots into TWRP. It's recognized by adb in recovery, but if I try and boot into boot-loader, it no longer is recognized.
I have tried in Windows 10, and Linux. Previously it was recognized. I am thinking that when I flashed the latest image, I didn't enable USB debugging. But it's odd that it can be recognized in TWRP and not bootloader.
I tried wiping data, but that didn't work.
(Yes I have the latest usb drivers for both windows and linux.)
Click to expand...
Click to collapse
What exact command are you typing while booted in the bootloader?
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
What exact command are you typing while booted in the bootloader?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
first i try adb devices, which returns nothing while in bootloader:
adb devices
List of devices attached
But when in TWRP I get:
List of devices attached
5VT7N15A28001306 recovery
So I can't seem to flash when in bootloader. I tried installing an OTA from TWRP but I get
error 7
Which makes no sense since it's an Angler Zip file for the Nexus 6P.
D'OH! I should have been using FASTBOOT in bootloader and I was using ADB, D'OH!
dratsablive said:
I was trying to flash the latest images on my 6P, but it's not recognized in Bootloader/Fastboot mode. It boots to the logo, then reboots into TWRP. It's recognized by adb in recovery, but if I try and boot into boot-loader, it no longer is recognized.
I have tried in Windows 10, and Linux. Previously it was recognized. I am thinking that when I flashed the latest image, I didn't enable USB debugging. But it's odd that it can be recognized in TWRP and not bootloader.
I tried wiping data, but that didn't work.
(Yes I have the latest usb drivers for both windows and linux.)
Click to expand...
Click to collapse
Have you opened developer options and made sure that USB debugging is definitely enabled. Maybe try the Nexus root toolkit to see if that helps. Also, you could try plugging your device in while in bootloader and check device manager. There may be something unrecognised or with a yellow triangle with a name like bootloader interface. If you see that then you could try installing the driver for it.
DEVILOPS 007 said:
Have you opened developer options and made sure that USB debugging is definitely enabled. Maybe try the Nexus root toolkit to see if that helps. Also, you could try plugging your device in while in bootloader and check device manager. There may be something unrecognised or with a yellow triangle with a name like bootloader interface. If you see that then you could try installing the driver for it.
Click to expand...
Click to collapse
Please see comment above yours.