Database Users

[Q]Bricked Nexus 7 not recognized on windows Please Help

Hi My nexus 7 was working fine I had a custom rom (paranoidandroid ) tried to upgrade to the latest release and now stays stuck at jelly bean splash screen
ive tried
installing frivers through wugz 1.5
nexus root kit uninstalled reinstalled tried to connect in fastboot mode nothing
I used a windows 7 box and an xp box updated usb drivers on both pcs nothing its like the port on the nexcus 7 was broken or something please help!
The only way I see out is if maybe I can connect through linux but not sure how to I do have a laptop running backtrack I could use

Wrong forum for this but:
Sounds like you tried to install on top of the existing ROM without wiping.
Can you get into fastboot? if so open a command prompt from the folder you have fastboot.exe installed and type "fastboot devices". do you see your serial number? If so you're fine! Flash a custom recovery you can easily wipe/reset and wipe dalvik cache and install a new ROM.

asawoszc said:
Wrong forum for this but:
Sounds like you tried to install on top of the existing ROM without wiping.
Can you get into fastboot? if so open a command prompt from the folder you have fastboot.exe installed and type "fastboot devices". do you see your serial number? If so you're fine! Flash a custom recovery you can easily wipe/reset and wipe dalvik cache and install a new ROM.
Click to expand...
Click to collapse
I can get into fastboot and it doesnt recognize it ive tried everything different cables etc
also i was upgrading from 1.9.2 to 1.9.5 so a full wipe was not required
My main problem is i cant connect cant list devices

so if you're in fastboot mode and you type "fastboot reboot-bootloader" nothing happens?
I don't see how installing a ROM would cause these problems.

asawoszc said:
so if you're in fastboot mode and you type "fastboot reboot-bootloader" nothing happens?
I don't see how installing a ROM would cause these problems.
Click to expand...
Click to collapse
Nothing at all it doesnt recognize it at all
I dont see either I dont get it and I cant get into recovery if i try that it gets stuck at google screen
if i try to boot then I just get stuck at splash
tried different systems no dice

Put your device in fastboot mode. Do not connect it yet.
Run wugz 1.5.2 (that's the latest I think) and press the "Full Driver Installation guide".
Check the instructions to remove your current drivers. Remove them.
connect your device
Reinstall the drivers manually (not via the toolkit). Use the naked drivers from here.
Download the factory image from here and flash it via the toolkit.
root it, flash cwm do whatever you want to do :silly:
profit

Wont respond or recognize it

snipestech said:
Wont respond or recognize it
Click to expand...
Click to collapse
You need to install the drivers. Do you know how to get into your device manager in windows and install drivers for devices connected? You need to dl th wugz that regunus told you about above. After installing you can tell your computer to search in that folder to install drivers. When you open your device manager do you see anything yellow with a question mark. Once you have the drivers installed correctly then follow this http://forum.xda-developers.com/showthread.php?t=1781250 and you will be golden. Been through this a couple times already

Also when you try to manually install drivers for the devices that are not recognized in the device manager make sure to guide the driver install wizzard in the folder Universal_Naked_Driver_0.7 (or wherever you unzipped your drivers) and NOT in a specific directory like "amd64" or "i386".
If all drivers are succesfully installed, your computer will see the device in fastboot mode and your problems are gone ^_^

snipestech said:
Wont respond or recognize it
Click to expand...
Click to collapse
You can install the toolkit from here http://forum.xda-developers.com/showthread.php?t=1809195 then use it to install the drivers, then install temp cwm, then reboot into recovery, do a full wipe and try to install 1.95 again. You can use the toolkit to install a rom as well if you download it to your computer. Hope it helps.You always have to wipe cache and dalvic cache when flashing any rom. No wipe means you don't need to do a data/factory reset.

Vocalshock said:
You need to install the drivers. Do you know how to get into your device manager in windows and install drivers for devices connected? You need to dl th wugz that regunus told you about above. After installing you can tell your computer to search in that folder to install drivers. When you open your device manager do you see anything yellow with a question mark. Once you have the drivers installed correctly then follow this http://forum.xda-developers.com/showthread.php?t=1781250 and you will be golden. Been through this a couple times already
Click to expand...
Click to collapse
Its not connecting at all Ive done this before ive had many Android phones when i connect nothing happens. I tried different cables computers etc nothing no connection at all
Would like to try to connect on linux if not Its going on ebay as is

snipestech said:
Its not connecting at all Ive done this before ive had many Android phones when i connect nothing happens. I tried different cables computers etc nothing no connection at all
Would like to try to connect on linux if not Its going on ebay as is
Click to expand...
Click to collapse
dude, forget the ebay! Your device is ok!
Check the Device Manager in the control panel to make sure all the drivers have been installed correctly. After that we'll see

I did dalvic and that's it also I already tried that tool kit regunus is connect via teamviewer see if he can help
Sent from my Galaxy Nexus using xda premium

snipestech said:
I did dalvic and that's it also I already tried that tool kit regunus is connect via teamviewer see if he can help
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I think he should be able to help. If not let me have a go at it..I have Team Viewer.

He would need dubugging mode on wouldnt he
Sent from my SGH-I777 using Tapatalk 2

Regunus tried no avail.
I reformatted my laptop dual boot windows 7 32 bit.
Tried all previous suggestions its not recognized, me and Regunus came to the conclusion that the port can't be bad Cuz it charges yet it does not recognize it.
I just finished installing adb fastboot on ubuntu if I go to terminal and list devices nothing if I connect my Galaxy sIII it shows up so again not being recognized while other devices do.
Current state :
Fastboot start goes to paranoid android jelly bean splash
And hangs
Fastboot recovery stays stuck at Google screen
I have reciept and all to bad I can't return may just post on ebay

Same Issue
I'm having the same problem, was this ever resolved?
Edit: I was having the same problem. Downloaded 'Nexus 7 Toolkit' and ran the 'install driver' option again (option 1). Device was recognized again.

No such thing as no way out. Keep find a way to connect and you're all set. Have you tried force reboot to fastboot and then enter recovery? I have similar problem once with my nexus s and i finally find a way after 10 hours of constant googling

I've tried nexus 7 toolkit
I reboot into fastboot mode and select recovery and it goes to Google and hangs I've tried on different post nothing at all
Sent from my SPH-L710 using Tapatalk 2

When it was recognized what state was it in?
fastboot mode?
Sent from my SPH-L710 using Tapatalk 2

HELP! ADB -USB Not Recognized

Hi folks,
I really hope someone can help me here. My TF300T is currently rooted and unlocked with the lates CM 10 (4.2.2) build. I am having some issues with reboots since upgrading to 4.2.2 and I would like to change the ROM. I am also trying to flash the upgraded TWRP recovery but unfortunately I am unable to do this. When I boot the TF300 into the menu where you have to select the USB icon normally this would load the ADB driver but my PC comes up as 'USB device not recognized'. I've tried this from two different PCs' with the same outcome. I won't be able to flash recovery or ROM unless I get this sorted. I should note that when I connect the TF300 while it is booted the PC recognizes it no problem. It also works in USB debugging mode so I'm very confused as to why it won't work from the boot menu. I've tried manually installing the drivers, installing Asus PC Sync and also re-installing SDK tools; all to no avail. Any ideas on how to fix this would be greatly appreciated. Thank you!

vipergrm said:
Hi folks,
I really hope someone can help me here. My TF300T is currently rooted and unlocked with the lates CM 10 (4.2.2) build. I am having some issues with reboots since upgrading to 4.2.2 and I would like to change the ROM. I am also trying to flash the upgraded TWRP recovery but unfortunately I am unable to do this. When I boot the TF300 into the menu where you have to select the USB icon normally this would load the ADB driver but my PC comes up as 'USB device not recognized'. I've tried this from two different PCs' with the same outcome. I won't be able to flash recovery or ROM unless I get this sorted. I should note that when I connect the TF300 while it is booted the PC recognizes it no problem. It also works in USB debugging mode so I'm very confused as to why it won't work from the boot menu. I've tried manually installing the drivers, installing Asus PC Sync and also re-installing SDK tools; all to no avail. Any ideas on how to fix this would be greatly appreciated. Thank you!
Click to expand...
Click to collapse
When you get the USB device not recognized, go into device manager locate the device on the list right click and then click on update driver. When it asks you selecte that you want to find the driver files on the computer, then select the option to look at the list of drivers. Once in the list there should be a driver for ADB try installing it and see if it works. That's how I got my adb to work while on recovery.

jgaf said:
When you get the USB device not recognized, go into device manager locate the device on the list right click and then click on update driver. When it asks you selecte that you want to find the driver files on the computer, then select the option to look at the list of drivers. Once in the list there should be a driver for ADB try installing it and see if it works. That's how I got my adb to work while on recovery.
Click to expand...
Click to collapse
Thanks but that still didn't work for me. What exact driver did you use? Thanks!

Don't remember the name exactly, but from what I can see right now on device manager these are the details on the driver:
ASUS Android ADB Interface
Driver Provider: ASUSTek Computer INC.
Driver Date: 7/17/2012
Driver Version: 4.0.0.5
Digital Signer: Microsoft Windows Hardware Compatibility Publisher
Also, have you tried removing all previous ASUS drivers and trying to install them again?

jgaf said:
Don't remember the name exactly, but from what I can see right now on device manager these are the details on the driver:
ASUS Android ADB Interface
Driver Provider: ASUSTek Computer INC.
Driver Date: 7/17/2012
Driver Version: 4.0.0.5
Digital Signer: Microsoft Windows Hardware Compatibility Publisher
Also, have you tried removing all previous ASUS drivers and trying to install them again?
Click to expand...
Click to collapse
Thanks again. I will give this another go later and see what happens...

Any luck?

jgaf said:
Any luck?
Click to expand...
Click to collapse
I haven't had the opportunity to try it again just yet. I plan to do this tomorrow night on my nightshift in work. I'll let you know then. Thanks for asking

Tried tonight again and still no luck. I know the driver installed on this machine definitely works because its the same one that worked last week when I tried it. Oddly, the ADB driver picks up ok when I'm in the OS with debugging on but I don't think i would be able to flash whilst logged on to the OS. This is concerning because the CM10 ROM 4.2.2 which I have installed a the moment is firing up random reboots. I know it's still in experimental stage and I'm not complaining but it would be nice to change my ROM when needed. Below is a couple of screenshots of the problem I am having.

I had a similar problem my adb worked flawlessly when the OS was running, but it wouldn't get recognized when in recovery (fastboot worked too). So, what I wrote earlier solve my problem. Sucks it didn't work for you. Anyways do you have a recovery installed? If you do why can't you use that one? Also, I'm pretty sure you can install recovery when the OS is running, even from android terminal emulator in the pad.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2

Thanks again. I did do a backup thankfully and currently it is restoring. I will try to see after restoring the backup if it works. Another method I have found to repair the bootloader is the NVFLASH method, although this does scare me a little! I would be very interested in trying those drivers you have as mine are older but so far I have been unable to find anything newer, despite extensive searching. :crying:
Thanks for your help thus far! :good:

Looks like I'm finally getting somewhere. I decided that I would try connecting directly to the TF300 instead of through the keyboard dock and oddly this worked. The driver is now loading correctly and I am able to flash again! Now to choose a JB ROM... :good:

[Q] Bricked Updating to CM11

Hey guys any help or suggestions will be greatly appreciated on this matter. I will try to be as detailed as possible but I'm trying to fix this phone for a friend and he isn't very phone savvy. From what I understand, he was previously on CM10 and tried updating to CM11 using the cmupdater. For some reason it failed and he was stuck in TWRP. When he tried to reboot it kept kicking him back to recovery. He took his phone to a phone repair shop who then wiped his device. At this point he gave me the phone to try to fix.
First of all I have working fastboot and adb drivers for my Nexus 5 so I don't think this is a driver issue but I'm no expert on the Nexus 4 so I could be wrong. I'm also running Windows 8.1 if this is any relevance.
I can still access the devices bootloader (ver MAKOZ20i)
I can still access TWRP (ver 2.6.0.0)
When plugging the device into my USB 2.0 ports, nothing shows up in my device manager in bootloader, TWRP, or TWRP ADB sideload.
When plugging the device into my USB 3.0 ports, I see 'Unknown USB Device (Device Descriptor Request Failed)' and the Device Instance Path is 'USB\VID_0000&PID_0002\7&20F39B9B&0&2' in bootloader, TWRP, or TWRP ADB sideload.
I've never heard of a device not being seen at all in by USB 2.0 ports but showing using USB 3.0 ports so I attempted to give extra juice to the phone using a powered USB OTG cable. Still nothing shows up.
I've tried running 'fastboot device' and 'adb devices' with no luck.
I think I've covered all the bases... can anyone think of anything that could help me re-install a new rom or factory reset or his he out of luck?

I think it may be a Win8 problem. You have access to another machine with Win7 or WinXP?

Install "universal driver.exe" in win7, than connect phone while power off, I think it'll install driver...than push any custom ROM to phone via adb or just flash any official IMG..

Well I can tell you WHY it didn't work. That version of TWRP is not able to install 4.4 (CM11). if you manage to successfully push via adb and get it started again, make sure to flash the newest version of TWRP before trying that again.

Thanks for the reply guys. I kind of guessed that the version of TWRP was not compatible as I installed CM11 on my old Nook Tablet and had to update my recovery before installing it. Unfortunately the guys who wiped the phone prevented me from installing an old version of CM10 that my friend probably had from the cmupdater.
As for Windows 8 being the issue.. I attempted to try to use my laptop which runs Windows 7 but was unable to get anything to happen. Since the laptop only had USB 2.0 ports, plugging in the device to any of the ports did the exact same thing as what it did on my desktop (Windows doesn't even recognize anything is connected). I still get the charge animation on the phone but yea... nothing in device manager. I'm thinking of running Linux from a live installation to see if anything different happens, unfortunately its been ages since I've touched Linux so this is kind of a last ditch effort here.
Any other thoughts?

mrlazyone said:
Thanks for the reply guys. I kind of guessed that the version of TWRP was not compatible as I installed CM11 on my old Nook Tablet and had to update my recovery before installing it. Unfortunately the guys who wiped the phone prevented me from installing an old version of CM10 that my friend probably had from the cmupdater.
As for Windows 8 being the issue.. I attempted to try to use my laptop which runs Windows 7 but was unable to get anything to happen. Since the laptop only had USB 2.0 ports, plugging in the device to any of the ports did the exact same thing as what it did on my desktop (Windows doesn't even recognize anything is connected). I still get the charge animation on the phone but yea... nothing in device manager. I'm thinking of running Linux from a live installation to see if anything different happens, unfortunately its been ages since I've touched Linux so this is kind of a last ditch effort here.
Any other thoughts?
Click to expand...
Click to collapse
One more, when you plug into usb 3.0 you can see unknown device Right ??
If yes, download driver files from here Here.
It's a zip contains .inf files, Now click on unknown device and select update drivers then give the path to these drivers manually.
Hope this will help you out.

I'm pretty convinced at this point that the phone can't be fixed by me. Running it through Ubuntu I can't see the device at all (USB 2 & 3) when running the lsusb command but it sees my nexus 5 just fine. I even tried modifying drivers to match vendor id product id and class id as reported by windows. Thanks for the suggestions. Does anyone know of a reputable service to get this phone repaired? How much does a JTAG repair usually cost?
Sent from my Nexus 5 using XDA Premium 4 mobile app

mrlazyone said:
I'm pretty convinced at this point that the phone can't be fixed by me. Running it through Ubuntu I can't see the device at all (USB 2 & 3) when running the lsusb command but it sees my nexus 5 just fine. I even tried modifying drivers to match vendor id product id and class id as reported by windows. Thanks for the suggestions. Does anyone know of a reputable service to get this phone repaired? How much does a JTAG repair usually cost?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The following method may still help
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060

DrFredPhD said:
The following method may still help
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
Click to expand...
Click to collapse
Awesome! Didn't realize this was an option. It didn't work using the USB 3.0 ports but the USB 2.0 actually worked for this method. Thank you!

Huge mistake

Hey guys ,let's get straight. I'm totally dumb.
After flashing Lollipop factory img which reseted my internal storage (made a backup on PC), today I decided to try AOSP. Downloaded with my phone, flashed it. But the file was corrupted (bad download or something). Results : I only had that rom on my internal storage, my phone won't boot. I thought I could use NRT, although it as always worked fine, now it keeps telling me "adb device not found", "no fastboot devices". So, actually I can't do anything and I can't see what can I do.. already tried reinstalling drivers, but windows isn't even showing my nexus 4 on device manager
Looks like I need help, and sleep too..

Pedrau said:
Hey guys ,let's get straight. I'm totally dumb.
After flashing Lollipop factory img which reseted my internal storage (made a backup on PC), today I decided to try AOSP. Downloaded with my phone, flashed it. But the file was corrupted (bad download or something). Results : I only had that rom on my internal storage, my phone won't boot. I thought I could use NRT, although it as always worked fine, now it keeps telling me "adb device not found", "no fastboot devices". So, actually I can't do anything and I can't see what can I do.. already tried reinstalling drivers, but windows isn't even showing my nexus 4 on device manager
Looks like I need help, and sleep too..
Click to expand...
Click to collapse
Hmm can you get at least to the bootloader menu. If you can, there's still hope. At this time, you're better off using the manual commands rather than the NRT (the NRT use a set of pre-configured scripts and doesn't always end up where you would like to) Have you tried to also plug your device inside another USB port?

zaclimon said:
Hmm can you get at least to the bootloader menu. If you can, there's still hope. At this time, you're better off using the manual commands rather than the NRT (the NRT use a set of pre-configured scripts and doesn't always end up where you would like to) Have you tried to also plug your device inside another USB port?
Click to expand...
Click to collapse
Yes I can acces to bootloader and TRWP. Tried another USB port, another USB cable, using manual commands it says " <waiting for device>" and nothing happen..

What drivers are you using. I use the Google usb driver available here
http://developer.android.com/sdk/win-usb.html
How to install these drivers here
http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver
You also need the android platform tools installed on your pc for adb and fast boot commands to work. I use this installer
http://forum.xda-developers.com/showthread.php?t=2317790
Make sure you have completed these steps on your PC before you connect it to your nexus.

venu123 said:
What drivers are you using. I use the Google usb driver available here
http://developer.android.com/sdk/win-usb.html
How to install these drivers here
http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver
You also need the android platform tools installed on your pc for adb and fast boot commands to work. I use this installer
http://forum.xda-developers.com/showthread.php?t=2317790
Make sure you have completed these steps on your PC before you connect it to your nexus.
Click to expand...
Click to collapse
Thanks buddy , but my drivers were fine before all this. And now i can't reinstall it that way since my nexus isn't even showing up on device manager, I used another method from NRT. Gonna test on w7..
EDIT: Problem solved using windows 7. There seems to have problem with drivers on windows 8.1

Yes, in windows 8 you need to disable driver signature enforcement. In windows 7 no problem.

venu123 said:
Yes, in windows 8 you need to disable driver signature enforcement. In windows 7 no problem.
Click to expand...
Click to collapse
I didn't have to on Windows 8.1.

Nexus 4 bricked, no OS, no recovery.

Hello
I tried a Nougat rom for the Nexus 4 which was available as a full update package (including system bootloader rom etc) and installed it with the update command from adb instead of from custom rom.
now my phone is bricked and I cant seem to get it fixed.
It either gets stuck in a bootloop, or i can force switch it to bootloader mode. From there I can go to recovery but the stock recovery is useless.
Problem is when i connect this to my windows 10 pc, it shows no sign of being detected. I installed drivers over and over including the universal ADB and fastboot drivers available here on XDA. it doesnt show up under adb devices command and even the Nexus 4 rootkit doesnt detect it as a phone.
I wanna make this phone working again. I'm guessing the way is to go back to stock image and then re-root and re-flash custom recovery and ROM. but even for this, it should be detected by the PC and adb command and rootkit right? Is there something I'm overlooking here?
This is the ROM I tried
https://forum.xda-developers.com/nexus-4/development/fake-nexus-rom-nexus-4-t3230268
The way to install it is also mentioned there and that is exactly what I did.

Did you try this adb installer: https://forum.xda-developers.com/showthread.php?t=2588979
In that thread, I read the people are able to use adb on Windows 10. If that doesn't work, find a Windows 7 PC or boot to ubuntu using bootable pendrive and flash the factory images using fastboot.
Nitin

nitin.chobhe said:
Did you try this adb installer: https://forum.xda-developers.com/showthread.php?t=2588979
In that thread, I read the people are able to use adb on Windows 10. If that doesn't work, find a Windows 7 PC or boot to ubuntu using bootable pendrive and flash the factory images using fastboot.
Nitin
Click to expand...
Click to collapse
So are you saying this is definitely a problem of Windows 10? I hadnt even considered that...

BluTheCool said:
So are you saying this is definitely a problem of Windows 10? I hadnt even considered that...
Click to expand...
Click to collapse
I read many users complaining about that. You can try that installer; as I mentioned - users have reported that they were able to use adb on Windows 10 after installing adb using that installer. If that doesn't work try the second suggestion (Ubuntu/ Linux)
Nitin

nitin.chobhe said:
I read many users complaining about that. You can try that installer; as I mentioned - users have reported that they were able to use abd on Windows 10 after installing adb using that installer. If that doesn't work try the second suggestion (Ubuntu/ Linux)
Nitin
Click to expand...
Click to collapse
i tried the installer but it made no difference. i tried it my win 7 partition as well but it didnt show up in the device manager.. i think usb debugging must have been disabled with my new rom flash. but even then i dont get why it wont show up as anything in devman...
any command i try ends with waiting for device and since i cant find the device in devman I cant even update the driver manually. I guess I could give linux a shot

Hey I finally figured out the problem. Its unbelievable. The usb port of the device was slightly bent in such a way that every cable I tried never really connected with the phone. I twisted it up a little and now its being detected as fastboot. The drivers you provided work like a charm now. Thanks for all the help !

BluTheCool said:
Hey I finally figured out the problem. Its unbelievable. The usb port of the device was slightly bent in such a way that every cable I tried never really connected with the phone. I twisted it up a little and now its being detected as fastboot. The drivers you provided work like a charm now. Thanks for all the help !
Click to expand...
Click to collapse
Glad that it helped, hope you get it revived soon :fingers-crossed:
Nitin

BluTheCool said:
Hey I finally figured out the problem. It's unbelievable. The USB port of the device was slightly bent in such a way that every cable I tried never really connected with the phone. I twisted it up a little and now it's being detected as fast boot. The drivers you provided work like a charm now. Thanks for all the help!
Click to expand...
Click to collapse
It seems I have the same prob, as my N4 too doesn't get detected. But my ph can charge with USB when I connect to PC.
How you twisted USB port? I mean it has very less room to insert any tool.

sandy7874 said:
It seems I have the same prob, as my N4 too doesn't get detected. But my ph can charge with USB when I connect to PC.
How you twisted USB port? I mean it has very less room to insert any tool.
Click to expand...
Click to collapse
Tell me one thing - can you boot to fastboot mode?
Nitin

nitin.chobhe said:
Tell me one thing - can you boot to fastboot mode?
Nitin
Click to expand...
Click to collapse
Yes I m able to boot to Fastboot mode.

sandy7874 said:
Yes I m able to boot to Fastboot mode.
Click to expand...
Click to collapse
Ping me on hangouts. My email ID is in my signature.
Nitin