Database Users

[Q] Problem...Recovery with no ROM to flash or USB recognition

Hi XDA. I have a problem and could use your help.
In order to make flashing ROM’s easier for myself I thought it would be a good idea to place them in the first folder listed on the internal sd card. In order to do this I placed a “.” befor the name of the folder. After wiping everything I learned CWM 5.8.1.8 (touch) does not see folders with dots(“.”) at the beginning. So I now am in recovery with no ROM to flash
I then proceeded to dig an even deeper hole for myself. In my attempts to install drivers for my device I have done something; now my computer fails to recognize that the device is plugged into the USB at all. Prior to my messing with it I would hear the USB input chime and Device Manager would show an “unknown device”. Now when I plug in my device nothing happens. I have tried two computers and both Win7 and Ubuntu.
I read that Linux might be able to see my device so I installed Ubuntu then the Android SDK as per this thread. It did not work for me. I still cannot see my tf101 but I can see my Nexus s with the “adb devices” command.
I bought my tf101 refurbished and can’t find the “B” version written on the device. I think I initially rooted with razorclaw...not %100 sure. I am not sure adb debugging was checked when I wiped...not sure it makes a difference at this point.
I am now looking at these NvFlash instructions but I can’t get past the 2nd step (I am a noob...obviously)
- run “./blobunpack recovery-clockwork-5.8.2.1-tf101.img” (Replace “recovery-clockwork-5.8.2.1-tf101.img” with the name of your downloaded file”)
Will this NvFlash tutorial work if the computer can’t see the device?
Any ideas?
Thanks for your time!

Try those steps from this website Reverting to Stock ROM (unroot and remove CWM recovery)
this is easier for you when u try to nvFlash your tf101. remember update driver, run as administrator on program

Thanks for the info!
I am away until tomorrow evening. I will try it then.

Hi,
I am still having problems.
Can I install drivers if the device is not listed in device manager? How?
Thanks again!

it will be reinstall or request when you unplug and plugin back your connect from tablet to PC
if your driver had been load or connected just go to Devices and Printers to check your connection, after that update your driver

Hi. Thanks for trying to help.
My problem is my computer is not seeing the device at all. No USB input chime. Nothing showing up in device manager. No nothing!
Could be the chord I guess but I don't think so. I was getting "unknown device" in device manager initially after I wiped the ROM. After attempts to install drivers I stopped getting any sign of the tf101 in device manager.

Need Help Unbricking Nexus 7

The problem is I can't unbrick and restore my nexus to stock rom.
I can't boot the device and I'm only able to boot to bootloader. However, my computer doesn't recognize the nexus. It keeps saying Window cannot recognize it whenever I plug my tablet to the computer in bootloader. I tried uninstall and reinstall driver several times, but none of them seems to work . ----> That means I can't even use adb to restore the phone simply because my tablet is not recognized in window.
Is there anyway to fix this problem? I really need your helps as soon as possible.
Thank you for reading !

Get to bootloader. Then use Wugs toolkit, open advanced options. On the very left is something like "temp boot to recovery". Once that boots it to recovery, ADB should work. It did for me. I was in some trouble last night and got out by this. If you know how to use adb/fastboot commands, you should be good. And I uninstalled my drivers and when I plugged it in the device automagically reloaded the drivers. But you have to do it a few times. Had to do it in bootloader, recovery, and another point. Anytime it asks to load drivers/etc do it.

I can't boot to recovery through Wug Tool Kit. It keeps saying Fastboot device was not found >"<
By the way, whenever I connnected my device to computer, the bootloader freezes :|

What were you doing before you go into this situation?

I was on Glazed Jelly Bean rom and wanted to go back to stock rom. I used nexus 7 toolkit to do all the work for me. However, there was something wrong like the toolkit didnt extract the stock img right or something like that, my tablet got bootloop, and what happened next was what i had been telling you guys.

Best bet is if somehow you could get into recovery or get adb working. Might want to uninstall drivers and install again and reboot computer. I would suggest using this thread and flash things manually back to stock. http://forum.xda-developers.com/showthread.php?t=1907796 but you would need adb working.
When you power off device and use volume and power can you get it to go into boot loader then plugged into computer try to get to recovery or adb.

Consider deleting the drivers from Windows after uninstalling them otherwise Windows may try to be "clever" and reinstall the bad driver when you plug the device in. The Nexus 7 drivers from Asus can be downloaded here and Google's USB drivers are here

Travisdroidx2 said:
Best bet is if somehow you could get into recovery or get adb working. Might want to uninstall drivers and install again and reboot computer. I would suggest using this thread and flash things manually back to stock. http://forum.xda-developers.com/showthread.php?t=1907796 but you would need adb working.
When you power off device and use volume and power can you get it to go into boot loader then plugged into computer try to get to recovery or adb.
Click to expand...
Click to collapse
What if I couldn't get adb working?

I tried everything and windows still doesn't recognize my device in fastboot

Have you tried Nexus Root Toolkit v .1.5.4?

kiddo94 said:
I tried everything and windows still doesn't recognize my device in fastboot
Click to expand...
Click to collapse
try connecting to the usb port at the back of your computer

Paranoid flashed with the bricked kernel did this to me once right after the move to 4.1.2. Even with a full wipe and all the usual safety precautions it just stuck on bootloop forever and wouldn't let me in. I chalked it up as that's what I get for being the guy that's never satisfied with stock. I was unable to get my nexus7 fixed. I sent you a suggestion on pm though.

Never mind everyone. Thank you so much for your help.
I tried install the nexus 7's driver on another computer and it recognized my device in bootloader mode, and restore everything back to stock now. Thank you so much!!!!

Mine did that to the first time I tried. After I got it to work, the permissions were all messed up and I could not get it to download anything off the web and I was getting a playstore error 90% of the time as well. I finally just wiped everything on my tablet, installed the stock rom via N7 toolkit, then reflashed smooth rom, and all is working now. It may have been a bug with the older version of N7 toolkit, as I updated it before I reran everything.

[Q] G2 soft brick!! nooooo

Okay guys, I've exhausted all my own resources and would really appreciate your help.
Long story short- I have TWRP installed with NO backup files or roms on the device. I made a TWRP backup and put it on my PC pre brick...
When I turn the G2 on and plug it into my PC i get an unknown deivce which has the hardware id: USB\VID_18D1&PID_D001&REV_0232
I attempted to use the TWRP sideload with no benefit- if i can use ADB i know how to push my image but i CANNOT get adb to see the device..
any help will be greatly appreciated!!!
-THank you
Dana

I am not familiar with adb when device is off or fastboot. So if you are desperate follow one of the guides on un-bricking the g2 (which will bring it back to stock and wipe data) but then you'll be up and running and you would just have to re-root and unlock it

djohnson308 said:
Okay guys, I've exhausted all my own resources and would really appreciate your help.
Long story short- I have TWRP installed with NO backup files or roms on the device. I made a TWRP backup and put it on my PC pre brick...
When I turn the G2 on and plug it into my PC i get an unknown deivce which has the hardware id: USB\VID_18D1&PID_D001&REV_0232
I attempted to use the TWRP sideload with no benefit- if i can use ADB i know how to push my image but i CANNOT get adb to see the device..
any help will be greatly appreciated!!!
-THank you
Dana
Click to expand...
Click to collapse
Assuming that you can boot into TWRP, then you probably just need to install the right drivers. Search around the forums.

Stock lg drivers don't seem to recognize phone in recovery mode install pdanet and then connect phone to pc while in recovery mode and open pdanet app in pc and follow instructions to install lg drivers and then pc will find ur device it worked for me when l had the same problem.
Sent from my LG-D800 using xda app-developers app

So i cannot seem to get my computer to install pdanet. i searched for a unbrick thread and found one.. i waited an hour for it to download a 2gig file, the lg program said it was pushing to phone which took 15 seconds (no way it pushed 2gigs that fast) then it said reboot the phone then do a hard reset... i went to do that and the phone just pushed me to TWRP. ahhhh losing my mind

What's the message when installing pdanet
Sent from my LG-D800 using xda app-developers app

access denied followed by x64 issues... Im the domain admin, and the website says its good for x64...

well lets see here are you on windows 8 or 7 ?
this is what i did
I put the phone into fastboot mode then connected it to the computer, well now the customer doesn't recognize it and you should have the drivers installed then what you want to do is search for device manager, look under the Universal Serial Bus Controllers and you will see USB connect with an "!" what you need to do is right click on it then go to update drivers, from there you need to select browse my computer for the drivers not the automatic one then select "let me from a list of devices. next you want to unchecked show compatible hardware now look for Lg in the manufacture list and there should be one that says something about "adb interface" and select it.
Now try using a cmd windows and adb. what i did was i download a fastboot.zip it has adb interface in that zip file then i opened a cmd prompt in that folder by holding shift and right clicking. now once it was open i typed adb list and it recognized my phone
then i went into twrp and adb sideload and I side loaded a stock zip now you be fine and back to square one.

[Q] LG G2 802 stuck in TWRP - drives not installing

Hi,
I wiped my current rom in TWRP and something went wrong with the rom I was trying to install so I have a phone without an OS now (LG G2 802). Now I am stuck in TWRP. The backup for the phone is on my laptop but I cant seem to get my laptop to recognise the phone any more.
When I connect my phone to the laptop via USB it shows up in the device manager but with an exclamation mark. I've tried pointing to the LG folder under program files for the drives but for some reason they dont work and the device is still showing up with the yellow exclamation mark in the device manager. These drivers were working before this happened (I've connected the same phone to my laptop quite a few time before, including using ADB to root it earlier) so I don't know why this is happening.
Any help would be appreciated, I am completely lost right now.
Thanks...

You can use an otg cable with a thumb drive too.. The driver for this is under Google, see if you can find it. There was a guide somewhere but I've lost the location :/
*edit* FOUND IT
http://forum.xda-developers.com/showthread.php?t=2557248
Sent from my LG-D802 using xda app-developers app

Got around it...phew!!
As it turned out I had a few issue, for anyone else in the same boat here is what I did to get my phone back up.
First, I cant thank Koush enough for his amazing work, after installing his universal adb drivers the laptop started recognizing the phone immediately (as to why it didnt with the official drivers, I have no idea).
The drives can be found here: http://koush.com/post/universal-adb-driver
Once the phone was recognized by the laptop I knew I had some hope, I tried to adb sideload a few roms but kept getting error messages. I looked up TWRP for the latest version 2.7 and updated to that from 2.6.3.2 and the Roms started working immediately. Now I am happily running the PAC KK rom (which by the way looks fantastic).
Hope this helps anyone else who is in the same boat.
Regards,
Tariq

Bricked Oneplus 2 (SOLVED)

**UPDATE I have unbricked my phone and the whole time I thought it was a software issue on my phone but it was a cable, I guess my cable got broken when I bricked my phone and I thought it was a software issue but it was not the whole time**
I have a bricked device and I would appreciate your help and I have tried EVERYTHING!!
here is how my oneplus 2 got bricked, I was on stock oxygen os 3.0 and rooted and I had twrp recovery 3.0.
So I did a full wipe on my device and when I was flashing the resurrection remix rom in twrp it said "Error 7" so then I reboot my phone and I was in a bootloop with no os.
I went back to twrp and flash the rom again and it not work. So then I tryed to transfer a file through my computer to my device and twrp was not recognizing it and tryed adb sideload and same thing and even in cmd I
typed "adb devices" and it not recognize it and I have the drivers installed, the 15 second 1click adb and fastboot.
And then I went to fastboot mode and then I tried first aid kit and the qualcomm mega unbrick guide and all the methods and still my oneplus 2 is not being recognized by PC and I am using the official oneplus 2 usb type c cable.
I have tried 2 windows 10 PC and I turned driver signniture enforcement off for the qualcomm drivers and nothing in device manager
I tried 1 Windows 7 PC and same thing and nothing in device manager
And I tried a Linux Mint virtual machine and I typed adb devices and fastboot device in the terminal and it was not recognizing it even though I installed the packages
So do you think the problem might be the cable? because it is the official one. But my device charges through the cable to and the cable was working before my phone got bricked. Or is it a driver problem? What do you guys think and please help and I will really appreciate it and thank you.

fahad999 said:
I have a bricked device and I would appreciate your help
here is how my oneplus 2 got bricked, I was on stock oxygen os 3.0 and rooted and I had twrp recovery 3.0.
So I did a full wipe on my device and when I was flashing the resurrection remix rom in twrp it said "Error 7" so then I reboot my phone and I was in a bootloop with no os.
I went back to twrp and flash the rom again and it not work. So then I tryed to transfer a file through my computer to my device and twrp was not recognizing it and tryed adb sideload and same thing and even in cmd I
typed "adb devices" and it not recognize it and I have the drivers installed, the 15 second 1click adb and fastboot.
And then I went to fastboot mode and then I tried first aid kit and the qualcomm mega unbrick guide and all the methods and still my oneplus 2 is not being recognized by PC and I am using the official oneplus 2 usb type c cable.
I have tried 2 windows 10 PC and I turned driver signniture enforcement off for the qualcomm drivers and nothing in device manager
I tried 1 Windows 7 PC and same thing and nothing in device manager
And I tried a Linux Mint virtual machine and I typed adb devices and fastboot device in the terminal and it was not recognizing it even though I installed the packages
So do you think the problem might be the cable? because it is the official one. But my device charges through the cable to and the cable was working before my phone got bricked. Or is it a driver problem? What do you guys think and please help and I will really appreciate it and thank you.
Click to expand...
Click to collapse
If your recovery mode is TWRP.. Then goto Mount -> Data
Then your computer will show your oneplus 2.
If still its not showing then update Driver Software of phone in device manager.

eldos777 said:
If your recovery mode is TWRP.. Then goto Mount -> Data
Then your computer will show your oneplus 2.
If still its not showing then update Driver Software of phone in device manager.
Click to expand...
Click to collapse
I tried both mount data on and off and still no luck, I have mtp enabled in twrp. I also checked device manager and there is nothing showing up. But twrp says that my phone is charging when my phone is connected to pc. I think the problem is probably the cable because the usb end of the cable looks sort of damaged, And I tried a Type-C OTG and put a usb on that and TWRP was not recognizing it

eldos777 said:
If your recovery mode is TWRP.. Then goto Mount -> Data
Then your computer will show your oneplus 2.
If still its not showing then update Driver Software of phone in device manager.
Click to expand...
Click to collapse
Holy crap the cable was the problem the whole time!!! I just went to the store and bought A new 3rd party USB-C cable and I plug it in to my pc and phone and immediately the pc installed drivers and now I could transfer files to TWRP from my PC!! It was a really hot sunny day today and I walked to the store which took 30 minutes and both ways 1 hour. I am so tired right now from the walk but it was worth it since my phone will be brought to life!! I am so happy right now!!!

fahad999 said:
Holy crap the cable was the problem the whole time!!! I just went to the store and bought A new 3rd party USB-C cable and I plug it in to my pc and phone and immediately the pc installed drivers and now I could transfer files to TWRP from my PC!! It was a really hot sunny day today and I walked to the store which took 30 minutes and both ways 1 hour. I am so tired right now from the walk but it was worth it since my phone will be brought to life!! I am so happy right now!!!
Click to expand...
Click to collapse
:good:

eldos777 said:
:good:
Click to expand...
Click to collapse
Thanks for your advice to for fixing the phone! I appreciate it!!