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
Related
Sorry, noob here. Please help!
My computer keeps on installing the wrong drivers everytime I plug in my Nexus 7. I don't know how to stop it.
When my tablet is in bootloader mode, Windows will try to install a bootloader interface driver that does nothing.
I have already:
- Went to Devices and Printers Installation settings and clicked on never install driver software
- Went to gpedit.msc and enabled: Prevent Installation of Devices not described by other policy settings,
So now my policy will block the auto install. But when I try to manually try to try Naked Drivers, it'll say it can't find any drivers.
When my tablet is in normal mode, the adb drivers comes back on.
I'm just trying to boot to recovery so I can install a new rom through the command prompt. Current rom is too unstable to do anything, new rom is already on the internal sdcard.
If any has any solutions, please let me know.
Thanks!
It sounds like you did things to prevent driver installation. But you need to install the correct drivers for things to work. Getting the correct drivers installed seems to be the biggest issue people have in being able to connect to a pc or use adb or fastboot. I know I installed the drivers from a root toolkit, installed rsd lite, android sdk, motohelper, etc. and still couldn't connect. Then I installed the pda.net app on the N7 and installed pda.net for android on my pc. Finally it worked and I can reliably connect to the pc, use adb and fastboot, and recognize the N7.
If all you are trying to do is get into recovery, why don't you just power off, hold the vol down and power until the screen comes on, use the up vol to change the menu to recovery, then hit the power button to enter recovery. Then you can wipe and flash. I hope I got those commands right. I'm using cwm recovery and I can get there like that. Usually, I just use Rom Manager to boot into recovery.
pdanet was what worked for me as well. none of the others did.
Sent from my Nexus 7
Thanks guys. that did the trick!
Sent from my Nexus 7 using xda app-developers app
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.
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 ^^!
howdy y'all,
so im trying to help out my buddy. he currently has no os installed as well, but can boot to bootloader and twrp recovery 2.5. no idea how he has that but I figure I could just mount some zip files and be on my way. Currently whenever we try to do anything in twrp(ie wipe/mount) it is just hung up on unable to mount /radio even when all I have checked is system. I can't use adb or fastboot as far as I'm aware of; I've tried to use the unified android toolkit from skipsoft but its no dice since I was never able to turn on debug mode to begin with? So yeah any help would be much appreciated
oh and I know its not my cable or usb ports since the tablet can still charge.
Also this is the 2012 N7
Hi,
You'll need to get adb and fastboot working, best approach is to wipe and flash factory images through fastboot but may also need to use adb for e2fsck
http://forum.xda-developers.com/showthread.php?t=2277112
See this on getting fastboot working, best of luck!
demkantor said:
Hi,
You'll need to get adb and fastboot working, best approach is to wipe and flash factory images through fastboot but may also need to use adb for e2fsck
http://forum.xda-developers.com/showthread.php?t=2277112
See this on getting fastboot working, best of luck!
Click to expand...
Click to collapse
I don't understand how I'm supposed to get fastboot working since I was never able to enable debug mode on the device in the past let alone now that it has nothing installed. And from what I can understand from the instructions I need the drivers to be installed after I plug in while under debug mode for the sdk to work.
I attempted to install the nexus 7 driver from here: http://support.asus.com/download.aspx?SLanguage=en&m=Nexus+7&os=32
However it looks like I already have the files on my computer from a previous attempt with Skipsoft's Android toolkit?
Because of this I'm unsure of how to move forward with this fastboot business.
fastboot doesn't need debugging on or an os installed, just a functional bootloader
You will probably need to manually update the drivers yo the proper ones
I see, how do I go about manually installing this driver then? I'm assuming I need to go through some sort of windows device tree? Or can I just extract a file somewhere?
You can download usbdview (just search Google for a free download) to see what driver is selected when you plug in your tab easily
Or you will need to go into device manager and select to manually update the drivers, don't allow windows to select but manually choose it
There are loads of instructional videos on YouTube for you if needed
I know this is a super late response, but I never managed to get around to trying to find out how to do a manual install. Just tried today using the Nexus Root Toolkit v.1.9.9. I still can't figure out how to manual install the driver because my issue is that windows doesn't recognize anything is plugged in, and all of these guides do state that I should have had usbdebugging checked. I can't seem to find a specific guide that correlates to setting fastboot up exclusively like you mentioned.
Also, using usbdeview like you said I could see that I have installed a google nexus adb interface, a google galaxy nexus adb interface, as well as the mtp usb driver.
Sorry for all the handholding, but this really is an issue that I've never have encountered and I can't seem to manage.
Hey again
There is a fastboot guide in the first post I linked you to
If you can't get fastboot to recognize device in bootloader mode it is possible the USB port is broken, but more likely an issue with drivers, cord or PC
So try a new USB cable, or a different PC
Try try again with drivers, uninstall and reinstall
Unfortunately this type of trouble shooting is hard to do without device in hand
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.