Evening/afternoon/morning depending on where you are.
I managed to successfully unlock the boot loader and then root my Nexus 7 using the Wugfresh Nexus toolkit and installed the latest TWRP recovery. All was going great, I decided to flash a ROM, it went well but never booted into it. I went back into recovery and stupidly deleted/wiped more than I should and long story short I have a tablet with no OS and the SD card has been wiped so I cannot flash the rom.
I have been for the past several hours trying to get the device to appear as mass storage so I could push out the rom but I am not able to that. I can see the nexus 7 appearing as a Android device in Windows Device Manager with the driver exclamation mark. I have tried to install the driver for it from the SDK folder and also downloaded the drivers from ASUS (both are the same?) but the Driver Wizard keeps saying the driver cannot be found.
I can still get into bootloader and recovery, when I do go into TWRP recovery, I go to mount option and see the USB-OTG option but I cannot check the box next to. I'm thinking I will need to get a appropriate cable and get the rom onto the device that way but will have to wait for morning when the shops are open.
I still have hope as I do have the recovery image but need the advice of the learned people of this forum to help. I am using Windows 8 in case it makes any difference, can use win 7 if anyone thinks that will make a difference? When its in bootloader the tablet then appears as a Android Phone in Device manager.
Thanks in advance to suggestions, please leave all cutting remarks at the door
Update: When I am in recovery mode on my Windows 7 machine, the tablet appears under the Android Phone section. Not sure if it helps but thought I would add that.
Can you get the device to show up in ADB? If so you can push the ROM through ADB.
mustbepbs said:
Can you get the device to show up in ADB? If so you can push the ROM through ADB.
Click to expand...
Click to collapse
Dude you were spot on, the nexus had ran out of juice so I had to painfully charge it to at least 10% before I could try it. Just to clarify, I got the device into recovery mode, in Device Manager it was appearing under Android Phone as ADB integ Port (something to that effect) and then pushed out the rom to the SDCARD using the ADB push command. Managed to install the SmoothRom and its loaded fully
My windows 8 laptop must not have a driver or something not compatible as opposed to my windows 7 PC. Although on the Win 8 laptop, when the device in Fastboot it does appear under Android Phone but when the device gets to recovery, it moves to the Unknown device. Anyway my ordeal is over and it has been nervy!
Hope this helps someone?
Related
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.
I have a Google Nexus 4, bought direct from Google, I rooted it and it was working well for a while. Then the battery started draining super fast. A friend recommended resetting, so I did and it seemed to fix it for a while. Then the battery issue came up again, so I reset again, expecting the same outcome....however, I wiped the phone completely. It turns on and displays Google, and that's it.. My computer does not recognize the phone when I plug it in, and I cannot get the USB Debugging to even be an option. Every resolution I have found for this situation needs me to enable the USB Debugging mode. Is there any other way to get all the OS files back on this phone or is it bricked?
When I plug it into the PC it tells me to look up drivers, and this is how it sees my phone: Unidentified Device USB\VID_0CF3&PID_3000&REV_0200.
It isn't recognized as a phone at all. It tells me to download Atheros Drivers.
I have searched for days trying to find the solution to this. Any help would be so very appreciated by this noob
Did you try to manually delete drivers from the device manager? Ticking the option that permanently delete the driver from PC.
And after doing this...trying Windows Update for driver installation?
PS: also try to manually flash with Fastboot all the latest Factory Image from Google....
Sent from my Nexus 4 using Tapatalk 4 Beta
thesebastian said:
Did you try to manually delete drivers from the device manager? Ticking the option that permanently delete the driver from PC.
And after doing this...trying Windows Update for driver installation?
PS: also try to manually flash with Fastboot all the latest Factory Image from Google....
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yes, I've done that, there are currently no drivers on my PC. When the phone is plugged into the PC, it tells me to find drivers because it is an unrecognized device.
MrsWhitey said:
I have a Google Nexus 4, bought direct from Google, I rooted it and it was working well for a while. Then the battery started draining super fast. A friend recommended resetting, so I did and it seemed to fix it for a while. Then the battery issue came up again, so I reset again, expecting the same outcome....however, I wiped the phone completely. It turns on and displays Google, and that's it.. My computer does not recognize the phone when I plug it in, and I cannot get the USB Debugging to even be an option. Every resolution I have found for this situation needs me to enable the USB Debugging mode. Is there any other way to get all the OS files back on this phone or is it bricked?
I have searched for days trying to find the solution to this. Any help would be so very appreciated by this noob
Click to expand...
Click to collapse
Hold volume up/down and power until it reboots into boot loader mode. Download the factory images from the Google website (search nexus stock images on Google) and plug your phone into the computer and use fastboot to flash the OS back.
Rember, as long as you can get the phone to turn on you can fix whatever other issue your having providing its software related.
To fastboot flash,
You need the android SDK, use Google to figure out how to install it but its not hard.
Run the flash-all bat found in the archive file you downloaded, or manullay flash each partition like this.
fastboot flash [partition] [.IMG name]
Sent from my Nexus 4 @1.944 GHz on Stock 4.2.2
IRX120 said:
Hold volume up/down and power until it reboots into boot loader mode. Download the factory images from the Google website (search nexus stock images on Google) and plug your phone into the computer and use fastboot to flash the OS back.
Rember, as long as you can get the phone to turn on you can fix whatever other issue your having providing its software related.
To fastboot flash,
You need the android SDK, use Google to figure out how to install it but its not hard.
Run the flash-all bat found in the archive file you downloaded, or manullay flash each partition like this.
fastboot flash [partition] [.IMG name]
Sent from my Nexus 4 @1.944 GHz on Stock 4.2.2
Click to expand...
Click to collapse
I am having trouble getting the phone to accept anything from the PC...
MrsWhitey said:
I am having trouble getting the phone to accept anything from the PC...
Click to expand...
Click to collapse
Download the toolkit and install the drivers
Sent from my Nexus 4 @1.944 GHz on Stock 4.2.2
yea download Google Nexus 4 ToolKit install drivers then you can factory restore using the toolkit to restore
i think i chose option 9 and it downloaded the need restore image
Tried it all
I have tried all those ideas and all have failed. I can never get the computer to see my device. All it says is unknown device. When I click update drivers and direct it to the sdk driver I download it still gives me no connection through fastboot or adb. I have tried selecting various general Android drivers through the update drivers screen, Found some from Google Inc. that specify Nexus 4 bootloader interface and adb interface. Nothing is working. I think I need to have a working Nexus 4 to install to correct drivers first and then I might be able to piggy back off those and use my phone to flash through fastboot or push adb. I have worked with both command lines with reasonable success before rooting samsung tablets and phones and htc's. I am familiar with the process and have read numerous ideas none of which seem to work in this case. Made it all the way to Google search page 12. Anyone know a way to force install the Nexus 4 drivers without having a working phone present? I am thinking I just need to go buy a new one and return it after I plug it in to install drivers. Don't want to have to pay the re-stock fee though. Any other ideas are very welcome.
And I have tried to use the toolkit as well and it does nothing either. I have the stock rom ready to go just need a way to get it onto the phone.
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!
Ok, here goes my story.
Just a week ago from the date this was posted, I decided to update my recovery (TWRP) through ROM Installer. Surprisingly, I didn't see TWRP at all in the "Recoveries" section of the application. Stock, ClockworkMod Touch, regular Clockworkmod (no touch), and unofficial Clockworkmod were available - from what I can remember. I decided to use Clockworkmod (no touch) to install Paranoid Android. Coming from OmniROM, I factory reset and flashed the .zip.
Flashing ended in error with Status 7. A while before I had used ClockworkMod Touch to try another ROM and had no such issue. I ignored the error and restarted my tablet hoping that it would still boot fine. It rebooted, gave me the Google logo for about 5-10 seconds and automatically rebooted into recovery.
I saw a bypass for Status 7. Removing some lines from the updater-script was the solution. Having no access to my Nexus 7 storage, this bypass is unusable
I tried flashing a new recovery using flashboot fastboot. After verifying that I had my drivers installed (Universal ADB by Koush), I opened up adb in the command line (Windows) as an administrator. I could not see my device. I tried the drivers from Asus, multiple USB 2.0 ports, and a different USB cord, but same results. I tried on a different computer. Still no detection.
Systems used: Windows 8.1, Windows 7 (x64), Windows 7 (x86)
I tried using Wug's Toolkit and used Flash Stock + Unroot, since it didn't need USB Debugging enabled. Same results...
I also tried plugging in another Android phone (LG Optimus Dynamic II) to see if Windows would recognize it. Windows recognized it, installed drivers automatically, and was recognized in ADB immediately. This practically unknown phone (XDA doesn't have a section for it yet) could be recognized, but my world famous Nexus 7 2012 can't be seen.
I have absolutely no idea of what to do now...
Are you on the bootloader screen when trying to use fastboot?
PrizmaticSmoke said:
Are you on the bootloader screen when trying to use fastboot?
Click to expand...
Click to collapse
Yes. Every time I use fastboot, I am in the bootloader.
I'm not new to this at all, so say whatever you need to ^^
The main problem is my PC not recognizing my Nexus 7 through adb. Again, I have used multiple cables with no success.
The computer I am using for this runs Windows 7 x64. I have only tried using USB 2.0 ports to connect my tablet.
Thank you!
Might try deleting the drivers and starting over. I had some issues with adb drivers for both the N7 and the kindle fire on windows 7 as well, but eventually got both working by doing this several times.
I'm assuming you ticked the option for softbricked when trying the flash stock option? If not try again and check that option.
This thread http://forum.xda-developers.com/showthread.php?t=1907796 has a section on driver installation with good info and links too.
Hope that helps. Best of luck man, getting the adb drivers working properly seems to be finicky sometimes in my experience, and i'm no stranger to PC and software troubleshooting either.
PrizmaticSmoke said:
Might try deleting the drivers and starting over. I had some issues with adb drivers for both the N7 and the kindle fire on windows 7 as well, but eventually got both working by doing this several times.
I'm assuming you ticked the option for softbricked when trying the flash stock option? If not try again and check that option.
This thread http://forum.xda-developers.com/showthread.php?t=1907796 has a section on driver installation with good info and links too.
Hope that helps. Best of luck man, getting the adb drivers working properly seems to be finicky sometimes in my experience, and i'm no stranger to PC and software troubleshooting either.
Click to expand...
Click to collapse
Thank you so much for all of this! I'll need all the luck I can get...
By the way, I checked that softbrick option ^^!
I encrypted my phone without realizing that CWM did not support encrypted devices. To fix this I was going to install TWRP since it does support it. My phone is working correctly with adb but I cannot get fastboot to find the device at all. This is making it so I cannot install TWRP on my phone now. Anyone have any ideas or suggestions? Thanks for any help.
You can install the recovery directly through the phone through Goomanager, but the fact that your computer doesn't recognize the device in fastboot is an issue I feel needs to be addressed. Goomanager solves the problem of the recovery, but I'm not sure about the fastboot issue.
Sent from my Nexus 4 using XDA Free mobile app
mikeric said:
I encrypted my phone without realizing that CWM did not support encrypted devices. To fix this I was going to install TWRP since it does support it. My phone is working correctly with adb but I cannot get fastboot to find the device at all. This is making it so I cannot install TWRP on my phone now. Anyone have any ideas or suggestions? Thanks for any help.
Click to expand...
Click to collapse
I had this issue on a different device. To solve it I went into control panel, device manager. Then look for the usb device that had an exclamation mark on it (with your device plugged into the usb port). Right click on it and update driver software. Then go to browse my computer and choose, let me pick from a list...... Pick the android composite adb interface. It'll ask you if your sure, just say yes
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
I had this issue on a different device. To solve it I went into control panel, device manager. Then look for the usb device that had an exclamation mark on it (with your device plugged into the usb port). Right click on it and update driver software. Then go to browse my computer and choose, let me pick from a list...... Pick the android composite adb interface. It'll ask you if your sure, just say yes
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thank you, thank you, thank you. This enabled MTP mode for me in about 3 seconds on my Windows 8 PC. I had tried using Wug's toolkit both automated and manual even disabling enforcement of digital signatures on driver installation and had also installed latest ADK and Google drivers to no avail (all that got me was connection in camera mode and ability to see only DCIM). I don't remember having this kind of trouble last time I decided to play with my Nexus 4. Not sure if I was using my old Windows 7 machine then or if there is a conflict with the other drivers on my machine (I have recently flashed both Motorola and Samsung devices too). I wish you had posted a couple of hours sooner lol.