I just followed the: [GUIDE] ADB, Fastboot, and Nandroid for Noobs (cant post link still new user)
and i had it working for a moment, except for when i went to recovery to try to gain root adb would not list my device. I went back and followed the step were you uninstall HTC's drivers and install the android USB driver and now ADB will not list my device at all.. anyone have a idea?
Related
I am not sure if I can post this solution in this thread as I am not a developer and merely sharing my experience, It seems several people are having issues with bootloops after installing att update or for some other reason, my post deals with helping only a certain issue. You should be able to boot into recovery by any means in order to use my solution.
The problem I had was I was trying to flash a new Rom and copied Rom and gapps into my phone( of course I was rooted and had recovery flashed) and then out of curiosity I wiped everything in advanced wipe in twrp so now I have no Rom to boot into or no file to flash and either download mode would not work, I was p******g in my shorts as I my phone was only a week old and its dead that's what I at least thought. And after spending the whole night no solution was found in xda website and neither did Google help any, now the solution. now u should compare this to ur problem and find where u stand. I installed pdanet on my pc as stock lg drivers don't seem to help pc recognize my phone in recovery mode, then I plugged my phone to pc while phone is still in recovery mode and then opened pdanet in pc and installed lg drivers through it and then adb was able to see my device(until now I was trying adb sideload and it wasn't working) so when adb was able to see my device, I used sideload in twrp and pushed Rom from pc to phone using sideload commands and my phone was back and I am the happiest man in the world. So in short
1. This method works only for people who can boot into twrp recovery but not into phone.
2. Have ur desired roms and gapps ready 3. Make sure u have a working adb in ur pc and if not install minimal adb and fastboot application only onto ur desktop for easy access, and copy ur desired Rom and gapps into that folder and rename them to 1.zip and 2.zip for easy reference and easy adb commands.
4. Download and install pdanet on your pc. Power on ur device into recovery and plug it into your pc. Start adb from the folder u installed on your desktop(hold shift and right click within the folder(minimal adb and fastboot) and click on start command here option, command opens up and it will show in which folder ur in and then type adb devices and if everything is right your phone in sideload mode should show up as adb sideload and if not (this is where the problem is) run pdanet and install lg drivers through it and then unplug exit sideload and restart sideload in ur phone and plug it back to pc and ur pdanet will notify u have connected ur lg phone. Then run adb again and type adb devices and it will show up as adb sideload and now (you should search how to use sideload as I don't remember those commands) and push Rom into (the ones u renamed for easy access and reboot and all should be all. Sorry for the lengthy post but I typed this solution into several posts individually and so decided to put it up as sticky and if anyone feels to remove part of or all the post I have no problem, just wanted to do my help to others with similar problem.
Sent from my LG-D800 using xda app-developers app
lingarajug said:
I am not sure if I can post this solution in this thread as I am not a developer and merely sharing my experience, It seems several people are having issues with bootloops after installing att update or for some other reason, my post deals with helping only a certain issue. You should be able to boot into recovery by any means in order to use my solution.
The problem I had was I was trying to flash a new Rom and copied Rom and gapps into my phone( of course I was rooted and had recovery flashed) and then out of curiosity I wiped everything in advanced wipe in twrp so now I have no Rom to boot into or no file to flash and either download mode would not work, I was p******g in my shorts as I my phone was only a week old and its dead that's what I at least thought. And after spending the whole night no solution was found in xda website and neither did Google help any, now the solution. now u should compare this to ur problem and find where u stand. I installed pdanet on my pc as stock lg drivers don't seem to help pc recognize my phone in recovery mode, then I plugged my phone to pc while phone is still in recovery mode and then opened pdanet in pc and installed lg drivers through it and then adb was able to see my device(until now I was trying adb sideload and it wasn't working) so when adb was able to see my device, I used sideload in twrp and pushed Rom from pc to phone using sideload commands and my phone was back and I am the happiest man in the world. So in short
1. This method works only for people who can boot into twrp recovery but not into phone.
2. Have ur desired roms and gapps ready 3. Make sure u have a working adb in ur pc and if not install minimal adb and fastboot application only onto ur desktop for easy access, and copy ur desired Rom and gapps into that folder and rename them to 1.zip and 2.zip for easy reference and easy adb commands.
4. Download and install pdanet on your pc. Power on ur device into recovery and plug it into your pc. Start adb from the folder u installed on your desktop(hold shift and right click within the folder(minimal adb and fastboot) and click on start command here option, command opens up and it will show in which folder ur in and then type adb devices and if everything is right your phone in sideload mode should show up as adb sideload and if not (this is where the problem is) run pdanet and install lg drivers through it and then unplug exit sideload and restart sideload in ur phone and plug it back to pc and ur pdanet will notify u have connected ur lg phone. Then run adb again and type adb devices and it will show up as adb sideload and now (you should search how to use sideload as I don't remember those commands) and push Rom into (the ones u renamed for easy access and reboot and all should be all. Sorry for the lengthy post but I typed this solution into several posts individually and so decided to put it up as sticky and if anyone feels to remove part of or all the post I have no problem, just wanted to do my help to others with similar problem.
Sent from my LG-D800 using xda app-developers app
Click to expand...
Click to collapse
I have more or less the same issue. Was with StockMod for D802 and received an official OTA and accepted and installed it. Now I'm stuck in bootloop. Unlike you, I can go into recovery (CWM not TWRP) BUT I can't seem to go into fastboot mode. When I hold the Volume Up and connect the phone through cable to my laptop, the phone boots but goes automatically into recovery mode. Did system wipe as well (which I shouldn't have) and at that point my phone has no OS to boot into so I used ADB to transfer CM 10.2 and GAPPS to my phone hoping that if I do it like I'm flashing a custom rom will help but unfortunately it didn't. I'm still stuck in bootloop and can't go into fastboot. help please...:crying:
Try a stock Rom and see if it helps.
Sent from my LG-D800 using xda app-developers app
I'll try to make this brief and to the point as I realize how many people come here seeking help.
I've rooted many android devices (my first was an htc incredible) so I'm not exactly "new" per say, but don't really fully understand what I'm doing either long story short.
Got my nexus 7 today, tested some things with the screen when I first got it (just playing videos to see how bright it is)
I Followed a video suggested (somewhere) on the forums (video here (but I can't post urls))
-Sat down, got the usb drivers from here - Can't post link
-got adb fast boot tools - can't post link
-Downloaded SuperSU
-Enabled usb debugging in settings
-Booted into recovery
-Updated Driver when prompted
-allowed usb debugging after entering adb devices command
-used adb reboot bootloader command
-used fastboot oem unlock command (worked succesfully)
-used flash recovery openrecovery-twrp-2.6.0.0-flo (personally I think it didn't flash correctly because I don't know how to explain issues I will detail below
- (unless this is where I went wrong) rebooted to get into os so I could place supersu.zip on internal storage for rooting
- sticks at glowing X
ADB won't recognize the nexus 7 in recovery or bootloader
Windows only sees the nexus 7 as either
QHSUSB_DLOAD
MTP USB Device
flo
I've tried wiping from recovery, it fails.
I DO seem to be able to get adb to recognize the tablet when it is in recovery mode now.
Adb lists
06d9e78e Recovery
I've tried reflashing Twrp, still can't wipe, Is it possible for me to just install kitkat from recovry straight from adb or fastboot? It's been a while but I was thinking if I could just reset the os it might work. I have razor-krt16s-factory-7235eb0d.tgz ready to go I just don't know how to put it on the tablet without an sd card to transfer with
I have also installed Wugs Nexus Root Kit but since I have no idea what build of 4.3 my n7 is running...it really isn't doing me any good -_-.
any help would be appreciated, I'm stumped but will be continuing to dig for answers.
Thanks
OK. I have spent the last 8 hours reading and trying my darnedest to get my phone up and running.
I wiped everything, and formatted data accidentally.
Now the phone wont mount the USB so I can put a ROM on it. I cannot get drivers to make either the skipsoft toolkit or the WugFresh tool kit to work.
I have read on ADB side loading, but cannot figure out how to get the phone to get recognized in order to connect with it. As it sets right now, I am stuck at the bootloader image, or TWRP recovery. No image on the phone, and I cant seem to get the drivers to allow my PC to see the phone. (Ive used WugFresh drivers, naked drivers)
Any help you guys can give me would be awesome.
Thank you
Mark
Hey there,
Our phones are MTP devices and because of that (I think) we can't mount them as a usb drive. But yea you can use adb sideload to get yourself up and running again.
For the drivers try this: http://forum.xda-developers.com/nexus-4/orig-development/toolkit-skipsoft-android-toolkit-nexus-t1995688
On your Phone:
1. Boot into TWRP,
2. Tap advanced,
3. Tap adb sideload,
4. Swipe to start sideload.
Once it says its waiting or something like that, it's ready to sideload from the PC.
On your PC:
Put the rom you wanna flash in the same folder as adb. So if adb is in C:\adb\ then put the file there.
In CMD type in adb sideload filename.zip (filename.zip is the name of your file you want to flash)
So an example would be:
Code:
c:\adb>adb sideload CARBON-JB-NIGHTLY-20131117-1149-mako.zip
It'll take a bit to transfer the file, but once it finishes you should be able to boot into the rom and use it normally again.
Hope it works for you, regards...
You can use Wugfresh to restore to stock and start over.
Dear people of xda,
Recenlty ive receive a FOTA update to my device which runs 4.2.2. Being stupid, i did the update although i had cwm recovery installed on my devices. Now my device keeps bootlooping into cwm without being able to do anything.
Ive read tons of threads talking about this issue but i still cant get my to boot normally.
Yingy in this thread http://forum.xda-developers.com/showthread.php?t=2563527 had the same problem but the only diffrence is my pc cant recognize my device in order to do the adb fix by thecubed.
Im plugging my G2 for the first time in this computer and that is why i think my pc is failing to install drivers. I downloaded and instellad latest driver although windows device manger shows error devices not detected and the end of the process.
In order to fix my phone i just need to make me pc recognize my phone in adb although phone was never plugged before to this pc so i think my G2 wont let it access. I tried installing universal driver such as Pdanet as offered in threat but still when i write adb devices in cmd i get device offline!
Download latest adb drviers, lates lg g2 driver, lg user support tool does not recognize plugged device as well. All me sdk manger tools are patched to latest version.
PLEASE ive tried anything possible. spend like 9 hours and still nothing. i would really appriciate your help.
Thanks.
Edit: here my problem with pdanet drivers, it asks me to allow pc usb debbuging as shown in screenshot below but icant do it since im stuck at cwm recovery!
Solved!
BOOM!! after 12 hours i FINALLY manged to solved this problem. Really simple actually lol.
If anyone come across the issue please do the following:
1. Go to clockwork recovery as always, go to install zip from sdcard, choose install zip from sideload.
2. Plug your phone to pc.
3. Run adb with lastest drivers and sdk tools.
4. At the adb folder press shift+right click and start cmd.
5. write adb devices it should show your device id like this (xxxxxxxxx sideload).
6.Download latest twrp recovery from here http://teamw.in/project/twrp2/197 and if you have open europe version G2 like me download latest version from here: http://techerrata.com/browse/twrp2/g2d802
7.put the zip file in the adb folder, do not unzip it.
8. write in cmd console adb sideload xxxx.zip (xxxx is the name of twrp file).
9. cwm will flash twrp recovery over cwm.
10. reboot in recovery in advanced options.
11. now you have twrp recovery.
12. follow this guide : http://forum.xda-developers.com/showthread.php?t=2451696&nocache=1
13. THATS IT!!!
finally after going through this mess, im never using cwm recovery again. twrp is the best
good luck everyone!
Hi
I flashed CloudG3 rom under CWM, and after install it won't boot the system - it sends me to CWM recovery instead.
Figured I would install another ROM but my device is not recognised by windows (won't show up under my computer). Can you please guide me on what I could do to sort this?
Thanks
Install the lg g2 drivers to get recognised by the os, after you download driver for adb sideload and restart, run sideload in the recovery with the usb pulgged in ur pc.
Open Android folder, and then do to platform-tools, drag a ROM there to be installed. Open a command in this folder. Write what is in the cellphone, adb sideload romfilename.zip if i'm right, then it will start installing and then you get out of the recovery stuck.
Using TWRP.
Hi
I installed lg drivers but it didn't help - looked like it was CWM that was causing an issue to get the device detected by computer.
Before you posted, I followed the instructions here http://forum.xda-developers.com/showthread.php?t=2739739 - this helped to get TWRP on top of CWM. Under TWRP, the device is detected by windows
Now should I install a rom using your guidance above or can I do it under TWRP? Or is it the same?