Hi, I'm going to say in advance that I'm no expert in this subject, so any help is well appreciated...
I bought this Nexus 7 in 2012/2013 and was really really satisified with the product. But as many of you know Google ruined it with a poor Android update.
After a long time without using this device, I tried to ressurect it by installing Cyanogen Mod (don't remember the version). I had followed some tutorial to root the device, install TWRP and Cyanogen.
All worked fine, the device got a little bit faster, but a lot of apps didn't work (like Netflix for example). So, again I left it aside...
This year, I saw the need to have a tablet for study purposes, but the device wasn't working really well with CMod.
Then I tried to flash the stock version with TWRP and something went wrong...
Now the device is soft bricked (I believe).
-I can access TWRP just fine. But the device doesn't show up on Windows 10 (Even after installing several different drivers)
-I can't use adb or fastboot.
I have used USBDeview, have tried using the toolkit, changing USB ports, changing cables, using different OS and nothing seems to work.
If anybody in here can help, I'll be forever grateful.
Related
After 4 hours of searching for solutions on my own, I am hoping someone might have a solution.
Rooted and installed latest TWRP no problem.
Flashed the CM 10.2 (official release), and phone rebooted and hung on a fastboot screen (last line [1170] fastboot: processing commands)
I've come to find out that I flashed the 802 version of CM 10.2 and not the 801.
Now, no drivers allow my phone to be seen by adb, nor my pc. I've tried many (800, 801, etc.) , including the LG firmware update tool mechanism for the same.
Nothing.
I can boot into TWRP, but have no backup file on my sd to flash back to normal.
I can boot into download mode, but the phone still will not be recognized.
No I am trying the R&D test tool method, but I have a feeling that this won't work either.
Any words of wisdom, other than I'm an idiot for flashing the wrong rom?
Do you have a microusb drive? Or a USB otg cable? Load a proper ROM and see if it helps
Sent from my LG-D802 using xda app-developers app
Just made an account so I could reply that I am having exactly the same issue and cannot figure out what to do. I've tried every different guide I could get my hands on and none of them seem to work.
Had same issue, i used R&D method and, it worked.
Guys, thanks for replying. I've tried the R&D method, but it sticks at 49%. Have not tried a pc with XP yet. I'm pretty sure there is a solution, but you have to wade through all the posts and decipher best you can. I can't say enough how important it is to read the entire thread before doing anything. Anyway, I'm still working on it. In the meantime I bought another G2. :
I have checked at least hundred threads now, but my problem seems unique! (First time this happened to me )
When I connect my N7 (WiFi, 32 GB) to my laptop (Win 8.1), it says "USB device not recognized - The last USB device you connected to this computer malfunctioned, and Windows does not recognize it." In Device Manager, it is like the image attached, no other recognition for the device. Upon selecting Properties, It says "Code 43" in status, also says "A request for the device descriptor failed". That happened with 2 computers; I used 2 cables (both worked previously). So it means N7's USB port is somehow malfunctioning. But it gets charged as well as ever!!
This started after I tried an OTA update of 4.4 earlier (the download had not completed, but a prior small update (1-3 MB) was installed).
Now, I have Android SDK (latest version) and installed those google USB driver and platform-tools. I have NRT 1.7.9 (which worked for me previously). But I cant get my N7 to answer to ADB requests. [highlight]Upon connecting USB, it says "Charging (USB)" but no option regarding PTP or MTP appears.[/highlight] I have developer tools installed. I followed the instructions given in NRT about ADB installation to the letter but still no progress. I have tried a factory reset too.
BTW, I dont have a custom recovery flashed. It vanished along with the precious root privilage.
Now the N7 is in Android 4.3 (JWR66Y), bootloader is unlocked, SuperSU is Installed (but do not work due to having no root access and I cant even Uninstall it for the same reasons!!!). Now the OTA update also do not work mysteriously (it downloaded the 4.4.2 update and went on to install it, but as the bar started filling, it only said "error" and stopped!!! no explanations whatsoever!!!!). I will be very happy any of the followings:
[highlight]1. root without computer (wireless ADB is also welcome),
2. working OTA, or anyhow the 4.4.2 update
3. working ADB connection with my laptop.[/highlight]
Any help will be very helpful... Thank you in advance...
If you can not communicate via USB hardware, then using fastboot is not an option (obviously). And so therefore the lock state of your bootloader is quite irrelevant, too.
Even if you were to get adb over tcp (WiFi) working, that doesn't get you much, as an adb login shell on a stock ROM is just an unprivileged user; it's not much different from using a terminal emulator app (from a privilege escalation point of view).
The only other thing left is an exploit (privilege escalation) method that runs under the stock ROM. Something similar to that Motochopper exploit from some time ago. I suppose that particular hole was plugged; whether or not a new exploit exists, I can't tell you.
You could always just send the tablet back for repair. Seems like not having a working USB port is pretty crippling to someone who wants to root, flash ROMs, copy backups off the tablet, etc.
Thank you for the replying...
Actually I lack warranty as I bought this from eBay weeks before it was officially available in India. Therefore I kept that repair thing as a last resort. I am now trying it through Linux. And being a noob there, its going too slow. However I have got the ADB working and detecting the device, so its not a port issue (I dont know why the hell windows was so adamant on that point!)... But I am yet to figure out how to flash the image... thank you for the tip over wi-fi, i was actually hoping to wait for it...
Aaron061992 said:
Thank you for the replying...
Actually I lack warranty as I bought this from eBay weeks before it was officially available in India. Therefore I kept that repair thing as a last resort. I am now trying it through Linux. And being a noob there, its going too slow. However I have got the ADB working and detecting the device, so its not a port issue (I dont know why the hell windows was so adamant on that point!)... But I am yet to figure out how to flash the image... thank you for the tip over wi-fi, i was actually hoping to wait for it...
Click to expand...
Click to collapse
Well that is very different than having a broken USB port.
You probably noticed in your search that this forum is littered with thousands of reports from users complaining about their Windows drivers. It gets pretty old, frankly. (No drivers are needed at all for Linux or Mac OS/X).
Here is a suggestion that I made in another thread just a few days ago about using fastboot under Linux - in your case, you will be on your way after installing a recovery, e.g.
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.1-grouper.img
I even attached the most recent version of the (Android SDK Linux) fastboot to that post.
Note that you don't even need a dual-boot PC or PC with a semi-permanent Linux install; you can do the whole thing with one of those "Live CD" boots and a USB stick.
good luck
Just switched over to Tmobile from Sprint and before even signing into google i went ahead and tried to root my phone. Rooting was a success. Used Flashify to flash twrp recovery. Downloaded rooted stock D80110G rom and began debloating it (like I did with the Sprint version) and then booted to recovery, wiped twice, flashed and reboot. Well, now it will just keep rebooting back to recovery and thats it!
I still have access to download mode
still have access to custom recovery
Did not do a nand backup unfortunately
cant mount in twrp because computer no longer recognizes phone!
shows up under unknown devices as LG D801
Tried the stock recovery using LG Flash tool posted in generals but ran into the "can not update because of your device policy" or something like that. Reinstalled and tried it again many times, even switching languages and countries (the last step)
Tried using the ubuntu method posted by partager.info but even ubuntu does not recognize the device. Matter of fact nothing even happens when i plug the phone in.
Tried reinstalling drivers, tried on 2 different laptops (one windows 8.1, one windows 7, and an ubuntu usb boot) and my desktop computer (windows 8.1) and am just unable to mount using twrp because none of them recognizes it!
tried using the adb sideload but twrp just stays trying to load adb sideload forever and adb terminal cant even find the connected usb device.
Tried factory reset but that just takes me to twrp.
I've redownloaded the rooted stock rom and left everything as is. I'm assuming I just need to get it onto the phone somehow so I can flash it.
I have an otg cable but not quite sure how to work it wit twrp or if that's even an option; I've just purchased it.
I feel like I've exhausted my options. Anything else I can try?
Thanks in advance.
EDIT: Should've just used Titanium to debloat instead of trying to do a fresh install! I know I know
Figured it out! not sure how to delete this thread now
zaft1 said:
Just switched over to Tmobile from Sprint and before even signing into google i went ahead and tried to root my phone. Rooting was a success. Used Flashify to flash twrp recovery. Downloaded rooted stock D80110G rom and began debloating it (like I did with the Sprint version) and then booted to recovery, wiped twice, flashed and reboot. Well, now it will just keep rebooting back to recovery and thats it!
I still have access to download mode
still have access to custom recovery
Did not do a nand backup unfortunately
cant mount in twrp because computer no longer recognizes phone!
shows up under unknown devices as LG D801
Tried the stock recovery using LG Flash tool posted in generals but ran into the "can not update because of your device policy" or something like that. Reinstalled and tried it again many times, even switching languages and countries (the last step)
Tried using the ubuntu method posted by partager.info but even ubuntu does not recognize the device. Matter of fact nothing even happens when i plug the phone in.
Tried reinstalling drivers, tried on 2 different laptops (one windows 8.1, one windows 7, and an ubuntu usb boot) and my desktop computer (windows 8.1) and am just unable to mount using twrp because none of them recognizes it!
tried using the adb sideload but twrp just stays trying to load adb sideload forever and adb terminal cant even find the connected usb device.
Tried factory reset but that just takes me to twrp.
I've redownloaded the rooted stock rom and left everything as is. I'm assuming I just need to get it onto the phone somehow so I can flash it.
I have an otg cable but not quite sure how to work it wit twrp or if that's even an option; I've just purchased it.
I feel like I've exhausted my options. Anything else I can try?
Thanks in advance.
EDIT: Should've just used Titanium to debloat instead of trying to do a fresh install! I know I know
Figured it out! not sure how to delete this thread now
Click to expand...
Click to collapse
Hi, I have the exact same problem as you. Did you end up using otg? how did you finally end up getting a rom in your device and flashing it? I sent you a pm hope fully you see it. please respond im desperate!
mnb91 said:
Hi, I have the exact same problem as you. Did you end up using otg? how did you finally end up getting a rom in your device and flashing it? I sent you a pm hope fully you see it. please respond im desperate!
Click to expand...
Click to collapse
Hey sorry, I haven't been on the site for a couple days.
I used the flashtool to go back to stock. Had to enter download mode and work from there. The big issue I was having was a driver issue. Uninstalled every driver related to android and then reinstalled after a restart and that did the trick. For some reason android phones are giving me a lot of driver issues on windows 8.1
follow these steps here but make sure you read a chunk of the thread as the steps in the main post are not complete
http://forum.xda-developers.com/showthread.php?t=2432476
Before anyone complains id like to say that i have done research into this and searched through the forums for a thread on the same matter but i have not found one.
I have recently purchased a Nexus 4 (the most well designed and premium feeling phone ive ever owned) running completely stock unrooted android 5.0.2, however upon connecting it to two different laptops i have been unable to access my files on the device or connect to the nexus root toolkit to root it.
device manager tells me that it recognises the device but the drivers are not installed. all the phone does is charge when its plugged in unless i turn on usb debugging and this only makes the noise that it makes when any device is inserted.
any help with this will be much appreciated, cheers
smiley118118 said:
Before anyone complains id like to say that i have done research into this and searched through the forums for a thread on the same matter but i have not found one.
I have recently purchased a Nexus 4 (the most well designed and premium feeling phone ive ever owned) running completely stock unrooted android 5.0.2, however upon connecting it to two different laptops i have been unable to access my files on the device or connect to the nexus root toolkit to root it.
device manager tells me that it recognises the device but the drivers are not installed. all the phone does is charge when its plugged in unless i turn on usb debugging and this only makes the noise that it makes when any device is inserted.
any help with this will be much appreciated, cheers
Click to expand...
Click to collapse
Google 15 second adb install xda. That will install drivers as well as adb and fastboot. You don't need nrt to root it. Flash the twrp image in fastboot, then flash supersu in twrp. http://techerrata.com/browse/twrp2/mako. http://download.chainfire.eu/693/SuperSU/BETA-SuperSU-v2.44.zip
Sent from my Nexus 9 using XDA Free mobile app
First, I'm not a newb, but I'm at my wits end so I'm swallowing my pride and posting this here.
I recently wiped my hard drive and reinstalled Windows 10. Prior to that Windows could see my v20, I could transfer files and ADB worked fine.
I installed command line tools to install ADB/drivers and tried both LG mobile 4.20 drivers and even tried the Intel drivers. Along the way I dusted off usbdeview to clear out the drivers and start over so likely further screwed things up.
I was able to eventually get ADB functional but no matter what I did the device wouldn't show up as a portable device under My PC.
I've finally said screw it and am currently reinstalling windows 10 from scratch for a fresh start.
So, looking for input as to the best way to proceed on fresh Windows install. Is best way to install adb/adb drivers by installing command line tools rather than full android studio? Does it matter what order I install LG drivers/ADB?
I'm running the notsostock 5.5 dirtysanta rooted on a verizon v20.
Thanks.
I haven't been able to get it to show as a portable device since flashing the NotSoStock rom. I'm on Windows 7, it was visible just fine prior to flashing and I haven't done anything to the computer in the meantime.
I've been assuming it was something goofy in the rom rather than windows drivers... It just hasn't been a big enough deal for me to monkey with, I don't often need that, and adb still works fine so I just push/pull stuff if I need to move anything...
ZachJohnson said:
I haven't been able to get it to show as a portable device since flashing the NotSoStock rom. I'm on Windows 7, it was visible just fine prior to flashing and I haven't done anything to the computer in the meantime.
I've been assuming it was something goofy in the rom rather than windows drivers... It just hasn't been a big enough deal for me to monkey with, I don't often need that, and adb still works fine so I just push/pull stuff if I need to move anything...
Click to expand...
Click to collapse
I came to the same conclusion about 4 hours ago. It was the NotSoStock rom that broke it. I wiped my v20 and installed the WETA rom and everything works perfectly. The dialer lock issue I had with that rom is gone. The hotspot issue is gone, etc. I've only been on it for a few hours, but it's definitely better than what I was on before.