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
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
i try to flash a rom and failed in the middle.
i have cwm version 6, while i select "mount USB storage" nothing happen,
while the recovery menu is open i have adb access but if i use "push" command it get stuck.
on the bootloader menu i dont have access to fastboot, i get on windows "usb device not recognized" under universal serial bus controllers in device manager.
any help here?
doesn't belong here!!!!
can the admin move it to where it belongs?
can the admin move it to where it belongs?
Fix your fastboot issue by properly installing the drivers (I suggest PDANet Android drivers, usually work fine) then flash Clockworkmod Recovery 6.0.1.0 or earlier OR TWRP latest version. The later versions of CWM Recovery have issues mounting USB.
Then mount USB, transfer a rom and flash away.
Edit: Oh and can't you restore your nandroid backup?
i think the problem is the cable driver is not installed properly ..
Keep calm, and check your driver or cable
fixed!
strangely the device gave the same error in my laptop and pc in all USB connection instead of 1.
only in my pc in specific USB connection at the back it works! i reflashed old cwm and it's all good now, thanks!
I just bought a used 64GB HTC One which came rooted. It has several backups on it and tons of folders/files which have consumed half of the storage space. I want to wipe the device so it's like new and I have a fresh build to start with.
Before I mess anything up trying to wipe the device, I want to copy everything over to my PC so I can always restore things if needed. I tried exploring the device and copying the files while the phone was on but Windows sat there forever calculating the time to copy. I'm not even sure if I can copy everything while the device is on since some files may be in use.
Because of this, I thought I read that you can connect through USB by rebooting into the bootloader (white screen which says HBOOT ... is this bootloader?). My plan is to reboot into the bootloader screen, connect USB, copy the files, boot into recovery (TWRP), wipe the entire device, and restore/flash a stock AT&T image; however, the phone never says HBOOT USB PLUG when I plug in the USB cable!!
I installed HTC Sync which recognized the device and installed the drivers (shows up in device manager without any exclamations). I then uninstalled the software. After booting into the bootloader, if I plug the USB cable in, nothing happens; however, when I hit the power button to select FASTBOOT, it changes screens, I hear the device connected sound on Windows, and the device changes from FASTBOOT to FASTBOOT USB.
In the Windows device manager I see Android USB Devices - My HTC. I tried selecting My HTC, update driver software, browse my computer, selecting the Android-USB-Drivers, and it said the best drivers were already installed. I tried to manually select the driver and use have disk to browse the drivers and I get a message saying, "The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for 32-bit systems" (I have Windows Vista 32 bit OS). If I hit the power button again and switch back to BOOTLOADER, I hear the windows device disconnected sound and I only see HBOOT.
Is there a reason why it will connect to the PC under FASTBOOT but not under BOOTLOADER? How come I cannot switch drivers ... I thought I read the HTC Sync drivers don't allow the device to connect in HBOOT which is why I'm trying to update them. Do I even need to be in bootloader to copy the device contents or can I copy it all while the device is on? Lastly, do I need to get this connection working prior to wiping the device and trying to flash/restore an image in case I need to move some files back from the PC to the device (not trying to brick the device and not be able to connect it to the PC to transfer files)?
I tried selecting My HTC, updating the drivers to the Android-USB-Driver
Forgot to include these images ... I noticed I have S-On ... do I need S-Off in order to get HBOOT USB PLUG?
Followed a video on Youtube to do S-Off and eliminate tampered with. Still not able to get HBOOT USB PLUG.
Hi all,
I was having a strange problem with my USB dropping out when using the NEWER recovery (TWRP and Philz). Which meant I couldn't push files via ADB or Sideload. Here is my solution....
Before starting
I am using Windows 7
Download Google USB driver
Make sure you have TWRP 2.7.1.1 loaded as your recovery
You may have slightly different devices show up maybe, but this is what mine showed...
Open device manager
Plug phone in and power up to bootloader
Device manager should show 'Android Device' or similar
Open recovery
**This is where my USB was dropping out**
Make sure TWRP 2.7.1.1 loads
Look at device manager and should show 'One Mini' with a yellow exclamation mark
I tried updating the drivers automatically and browsing to the Google USB folder that we downloaded above but just kept saying 'device driver loading failed'.
The only way I found worked was
Right click 'One Mini' and update driver
Browse my computer for driver software
Let me pick from a list of device drivers
If you have Android device listed click that, if not choose Portable device.
Click 'Have disk' and locate the Google USB Driver folder and should be able to load the .inf file.
Click from the list ADB USB device and click ok.
This should load your device and install properly.
You shoud now be able to use ADB and Sideload in Recovery now.
Let me know if this works or not as there are a couple of bits that I can't replicate as the driver is already there!
Is it possible? I tried a couple of methods but it always ended up with the "error: device not found". My solution was to put it in the sdcard and spare it from any kind of wipe but i'm a curious person and i'd like to hear more opinions. Long story short is it possible to run a .zip file from the bootloader/recovery without booting the Phone first to enable the USB debugging?
It's possible in recovery on Linux. I've done it in Ubuntu. I can't do it in WinXP, but maybe it's possible in newer versions of Windows.
My logic is: you can always use fastboot commands when in bootloader. But adb commands in recovery require the device to be recognized. This is a bit of a pain in the *ss because mostly Windows doesn't install the drivers correctly when you are in recovery mode. In your device tree it is recognized as a unknown device and you have to install the motorola drivers manually. Then you can use adb to push pull files i guess.
I've confirmed ADB push works in TWRP Recovery (probably others), on a PC running Windows 7.