Related
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
my own nexus 7 has been fine in connection with my Windows 7 (64-bit), with adb/fastboot working and MTP connects fine..
however, when i plugged in my friend's nexus 7 today, it always gave me no device when i tried "adb devices" command..
("adb devices" works fine in another Windows XP pc for his nexus 7..)
usb debugging is on for both devices..
as there should be no problem in my windows usb drivers installation, how come this is possible that one connects and one cannot be found?
the only difference i can tell of the 2 devices is that my own nexus 7 was connected to my windows 7 successfully when in android 4.1.1 (also works fine now after upgrading to 4.1.2), while my friend's nexus 7 was in android 4.1.2 already.
can this difference in android versions be the cause of this usb driver hell issue? *sigh*
Do you have switched on USB debugging? If not, the device will not be found.
Sent from my Nexus 7 using xda app-developers app
AndDiSa said:
Do you have switched on USB debugging? If not, the device will not be found.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
yes usb debugging is on for both nexus 7s..
after some more investigation, it seems that the recovery mode has problem.. (corrupt during OTA update?)
the bootloader mode loads fine (bootloader version 3.41), however, when tried to enter recovery mode from there, the google screen was displayed twice and then loaded into android.. apparently the recovery mode failed to load and it rebooted..
tried to load CWM with the following commands:
adb reboot bootloader
fastboot boot recovery-clockwork-touch-6.0.1.0-grouper.img
Click to expand...
Click to collapse
also displayed google screen twice and entered android system..
has anyone encountered this?
iamelton said:
after some more investigation, it seems that the recovery mode has problem.. (corrupt during OTA update?)
the bootloader mode loads fine (bootloader version 3.41), however, when tried to enter recovery mode from there, the google screen was displayed twice and then loaded into android.. apparently the recovery mode failed to load and it rebooted..
tried to load CWM with the following commands:
also displayed google screen twice and entered android system..
has anyone encountered this?
Click to expand...
Click to collapse
Yes, you have described exactly how my N7 behaves with bootloader 3.41 and clockworkmod 6.0.1.0. Try flashing clockworkmod 6.0.1.5 from this thread. This works perfectly for me. Please report back with your results!
comminus said:
Yes, you have described exactly how my N7 behaves with bootloader 3.41 and clockworkmod 6.0.1.0. Try flashing clockworkmod 6.0.1.5 from this thread. This works perfectly for me. Please report back with your results!
Click to expand...
Click to collapse
thx for the suggestion, gonna try this..
also, i found another solution here and it worked for me:
http://forum.xda-developers.com/showthread.php?t=1932063&highlight=recovery
in short, the solution is to reflash the 3.34 bootloader..
[edit]
but its really strange that my own nexus 7 (4.1.2, bootloader 3.41, CWM 6.0.1.0) has had none of this problem..
LG flash tool just stays at ready. Ive unplugged and replugged. Unplugged, powered off, plugged back in as download mode still stays at ready. So back to flash is out. Phone stuck at lg logo, but can boot to download mode, and twrp. Computer doesn't recognize twrp in adb sideload mode. I'm on windows 8, using the oem cable, and turned off the signature enforcement and restarted computer as well. So that's out. Otg is out as well I've tried exfat and fat32 on an 8gb san disk cruzer. I've used just the otg and ive used it in combination with a y--cable, both of which i've used before successfully. Also I checked the external sd folders for the otg and used the cat/proc/mounts in terminal. This post definitely sounds condescending and i'm sorry. This is one time when i would be so grateful to be proved a moron. The one solution i haven't tried yet is using the flash tool with the ota .tot file, instead of the shipping rom. What do I do?
If u can't get into recovery then revert to stock is the only option. Try holding power and vol down and press on screen where home button should be and it should take u to recovery and then u can use sideload with koush drivers and if it does not work then going back to stock is only option.
Sent from my LG-D800 using xda app-developers app
What are koush drivers? Any idea what im doing wrong with lg flash tool, because that isn't working, otherwise i would've went back to stock already.
Stock lg mobile drivers don't seem to help pc see ur phone in recovery mode so koush drivers or pdanet installed in ur pc can help solve ur problem.
Sent from my LG-D800 using xda app-developers app
Thank you so much. It was dumb to ask what the drivers were, i googled it, installed, and it worked. thank you so much.
hello,
I have recently been playing with roms and stuff on my n4. (did it on other devices, and never had any problem i couldnt fix)
but right now I kinda screwed up so bad, that I need some help.
I kinda wiped all the data on my phone from the cwm recovery.
and I'm stuck with this situation:
I can boot to bootloader + recovery
I can't boot to any rom (because there is none)
I can't connect to any pc because they won't recognize he's there (forever alone... ) (and yes i've tried all kinds of drivers)
I can't connect with adb because I can't turn on usb debugging mode.
So right now I'm stuck
I've come to the conclusion that i probably need to use fastboot fix this, but like I said before, no computer will recognize my n4. (not showing up in device manager)
also tried about 6 different usb cables - no luck
different computers ( ubuntu - mac - windows) - no luck
So is there any smart guy out there who can help me?
greetings, Julian
honorguard said:
hello,
I have recently been playing with roms and stuff on my n4. (did it on other devices, and never had any problem i couldnt fix)
but right now I kinda screwed up so bad, that I need some help.
I kinda wiped all the data on my phone from the cwm recovery.
and I'm stuck with this situation:
I can boot to bootloader + recovery
I can't boot to any rom (because there is none)
I can't connect to any pc because they won't recognize he's there (forever alone... ) (and yes i've tried all kinds of drivers)
I can't connect with adb because I can't turn on usb debugging mode.
So right now I'm stuck
I've come to the conclusion that i probably need to use fastboot fix this, but like I said before, no computer will recognize my n4. (not showing up in device manager)
also tried about 6 different usb cables - no luck
different computers ( ubuntu - mac - windows) - no luck
So is there any smart guy out there who can help me?
greetings, Julian
Click to expand...
Click to collapse
I apologise for potentially getting your hopes up, but I am in the exact same situation. I am very much interested in this thread.
Google 15 second adb drivers xda. You probably need to get adb and fastboot setup for the pc to recognize your device. In order to fix it you'll meet to use fastboot or adb commands
Sent from my Nexus 5 using XDA Free mobile app
honorguard said:
hello,
I have recently been playing with roms and stuff on my n4. (did it on other devices, and never had any problem i couldnt fix)
but right now I kinda screwed up so bad, that I need some help.
I kinda wiped all the data on my phone from the cwm recovery.
and I'm stuck with this situation:
I can boot to bootloader + recovery
I can't boot to any rom (because there is none)
I can't connect to any pc because they won't recognize he's there (forever alone... ) (and yes i've tried all kinds of drivers)
I can't connect with adb because I can't turn on usb debugging mode.
So right now I'm stuck
I've come to the conclusion that i probably need to use fastboot fix this, but like I said before, no computer will recognize my n4. (not showing up in device manager)
also tried about 6 different usb cables - no luck
different computers ( ubuntu - mac - windows) - no luck
So is there any smart guy out there who can help me?
greetings, Julian
Click to expand...
Click to collapse
You need to delete all your driver files from your pc and start over.
There is no reason for you to not be able to connect via fastboot.
Find a clean win7 machine and start over, installing the fastboot drivers before connecting your phone.
Sent from my Nexus 4 using Tapatalk
nicknc said:
You need to delete all your driver files from your pc and start over.
There is no reason for you to not be able to connect via fastboot.
Find a clean win7 machine and start over, installing the fastboot drivers before connecting your phone.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Going to try that now.
Hi both
I've tried installing the drivers but whilst the drivers claim to have installed correctly, my phone is still not recognised by my computer in Device manager. I've tried uninstalling all previous drivers before trying this.
Before we go on - should I be trying to connect my phone to the computer when turned off, in bootloader or in recovery?
Ihsahn_ said:
Hi both
I've tried installing the drivers but whilst the drivers claim to have installed correctly, my phone is still not recognised by my computer in Device manager. I've tried uninstalling all previous drivers before trying this.
Before we go on - should I be trying to connect my phone to the computer when turned off, in bootloader or in recovery?
Click to expand...
Click to collapse
The phone needs to be on, doesn't matter if it's in fastboot or recovery. You're going to need to use fastboot do I'd try it there
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
The phone needs to be on, doesn't matter if it's in fastboot or recovery. You're going to need to use fastboot do I'd try it there
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Hi
Is fastboot essentially bootloader? I've tried in the initial bootloader menu and I've tried having clicked 'start' from the bootloader.
In the bootloader it tells me fastboot is enabled, btw.
Ihsahn_ said:
Hi
Is fastboot essentially bootloader? I've tried in the initial bootloader menu and I've tried having clicked 'start' from the bootloader.
In the bootloader it tells me fastboot is enabled, btw.
Click to expand...
Click to collapse
When you're in the bootloader you can run fastboot commands. With your device plugged into the pc, from a command prompt opened on the same folder as fastboot.exe, run the command fastboot devices. Does fastboot return your device info? If so you're good to go running fastboot and flashing a factory image
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
When you're in the bootloader you can run fastboot commands. With your device plugged into the pc, from a command prompt opened on the same folder as fastboot.exe, run the command fastboot devices. Does fastboot return your device info? If so you're good to go running fastboot and flashing a factory image
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
But my problem is that fastboot Will never work if my pc wont even know my n4 is there (and also with adb/fastboot devices golving no response Either ) or am I wrong here?
jd1639 said:
When you're in the bootloader you can run fastboot commands. With your device plugged into the pc, from a command prompt opened on the same folder as fastboot.exe, run the command fastboot devices. Does fastboot return your device info? If so you're good to go running fastboot and flashing a factory image
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Not at the moment. I have had this appear in the past but this is the point I'm trying to get back to. Unfortunately I can't work out how to get it to appear here. My device is in the bootloader.
---------- Post added at 10:23 PM ---------- Previous post was at 10:13 PM ----------
Brief update - I think. My computer began installing the drivers again, but told me the device suddenly 'disconnected'. I think it's a hardware issue and that the port isn't seated properly. I'm going to replace the USB port and see if that helps.
honorguard said:
But my problem is that fastboot Will never work if my pc wont even know my n4 is there (and also with adb/fastboot devices golving no response Either ) or am I wrong here?
Click to expand...
Click to collapse
Did you do a clean install?
Have you used a different USB cable? Some cables are charging-only, with no indication otherwise. Internally damaged cables can also turn into charging only cables. Ironically, I just replaced one hooked into my daughter's phone today that would only charge intermittently.
There is no reason that wiping partitions in recovery would prevent your phone from being recognized by your PC at all.
Try a clean install of the drivers on a fresh pc with a different cable.
Sent from my Nexus 4 using Tapatalk
---------- Post added at 07:52 PM ---------- Previous post was at 07:50 PM ----------
Ihsahn_ said:
[Brief update - I think. My computer began installing the drivers again, but told me the device suddenly 'disconnected'. I think it's a hardware issue and that the port isn't seated properly. I'm going to replace the USB port and see if that helps.
Click to expand...
Click to collapse
This is typical when you connected the phone to the PC before installing the drivers. Windows will sometimes install a generic driver when you hook up the phone, preventing it from detecting the need for adb and fastboot drivers
Sent from my Nexus 4 using Tapatalk
nicknc said:
---------- Post added at 07:52 PM ---------- Previous post was at 07:50 PM ----------
[/COLOR]
This is typical when you connected the phone to the PC before installing the drivers. Windows will sometimes install a generic driver when you hook up the phone, preventing it from detecting the need for adb and fastboot drivers
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I tried uninstalling all drivers, including in USBDeview before running 15 second drivers then trying to connect my phone in fastboot/bootloader mode, with various cables and various ports. Nothing happened!
I've bought another USB cable which should be arriving soon. I've also bought a new charging/USB port to replace that inside the phone.
If it Works with that cable please give me a headsup
Verstuurd vanaf mijn ST25i met Tapatalk
Ihsahn_ said:
I tried uninstalling all drivers, including in USBDeview before running 15 second drivers then trying to connect my phone in fastboot/bootloader mode, with various cables and various ports. Nothing happened!
I've bought another USB cable which should be arriving soon. I've also bought a new charging/USB port to replace that inside the phone.
Click to expand...
Click to collapse
OK.
Sent from my Nexus 4 using Tapatalk
Well, I had similar issues when I bought this phone (coming from a HTC one s) connecting to fastboot.
What I did was:
Delete all drivers related to adb/fastboot/android (use a software to completely clean the files).
Booted my phone into fastboot mode.
Connect to PC and wait for windows to show the new hardware dialog.
Install the correct drivers (which i had downloaded and extracted) using the dialog box.
Profit.
Sent from my Nexus 4 using XDA Free mobile app
The onlY difference is that the new hardware dialog doesnt come up
Verstuurd vanaf mijn ST25i met Tapatalk
honorguard said:
The onlY difference is that the new hardware dialog doesnt come up
Verstuurd vanaf mijn ST25i met Tapatalk
Click to expand...
Click to collapse
Did you try on a different PC, installing the adb and fastboot drivers before connecting the phone for the first time?
Have you tried a different USB cable?
Sent from my Nexus 4 using Tapatalk
A brief update
I remembered I have a second Android phone knocking around. I plugged this in with one of the cables from earlier - perfect installation with all drivers, etc. This has further convinced me that the hardware of the USB port on the phone is the issue.
Thanks for all help - I'll update again if the hardware change works, or doesn't.
ok, ive installed a new windows and installed all the drivers and then i connected the phone.
Nothing.
i'm getting desperate here..
Help!! I wiped out my os on my Nexus trying to load a ROM. I can't figure out what to do. If I boot the phone it stays on a screen that says google. Everything I have found so far says to check USB debugging but I can't get to that because the phone doesn't fully boot. Also my computer is not showing my phone in windows explorer but does show a nexus device in devices and printer & device manager. As far as I can figure I have to somehow get the computer to communicate w/the phone and then load an operating system but can't seem to figure out how to do this. I can get to TWRP but find nothing there to help. What ca I do?
You need to use adb to push or side load a rom to your device while you're booted into recovery
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You need to use adb to push or side load a rom to your device while you're booted into recovery
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks. Thats what I am thinking but my device won't show in windows explorer, so I don't see away to communicate w/it. I have tried installing the device drivers but all I have now is it showing up in Device Manager as Google Nexus BootLoader Interface.Right now I am working with ADB and Fastboot and I think I have it working but I am still stuck on the drivers and the device showing up.
lol...
download WugFresh toolkit, download factory image from google, download universal ADB drivers.
enter bootloader, you should see an android with chest open, stay in bootloader and connect your phone to PC, flash ROM through Nexus 4 Tool kit.
you dont need usb debugging in bootloader
ahunter said:
Thanks. Thats what I am thinking but my device won't show in windows explorer, so I don't see away to communicate w/it. I have tried installing the device drivers but all I have now is it showing up in Device Manager as Google Nexus BootLoader Interface.Right now I am working with ADB and Fastboot and I think I have it working but I am still stuck on the drivers and the device showing up.
Click to expand...
Click to collapse
Google 15 second adb install xda. Has adb and the usb drivers. Try that. Factory image is going to wipe your device. By dirty flashing the rom you're on you'll save your data.
Sent from my Nexus 5 using XDA Free mobile app
---------- Post added at 05:09 PM ---------- Previous post was at 05:04 PM ----------
jd1639 said:
Google 15 second adb install xda. Has adb and the usb drivers. Try that. Factory image is going to wipe your device. By dirty flashing the rom you're on you'll save your data.
Edit, if those usb drivers don't work Google universal naked drivers xda
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Sent from my Nexus 5 using XDA Free mobile app
Mashed_Potatoes said:
lol...
download WugFresh toolkit, download factory image from google, download universal ADB drivers.
enter bootloader, you should see an android with chest open, stay in bootloader and connect your phone to PC, flash ROM through Nexus 4 Tool kit.
you dont need usb debugging in bootloader
Click to expand...
Click to collapse
Thanks Mashed_Potatoes. I tried Wug & Skipsoft toolkits but did not do it in bootloader mode. Hope I remember that for the next time! Still having trouble with the drivers and computer seeing the phone. In device manager should it be android device--Google Nexus ADB Interface? I just don't remember that and the phone doesn't show up in explorer, but it's listed under devices and printers. I hope I can get it. Wug toolkit gave me an error trying to install drivers. Thanks for the help
I didn't understand you, you managed to flash the ROM but not in bootloader? It won'tsay Google Nexus ADB Interface, i don't remember precisely i've done it a long time ago!
https://www.youtube.com/watch?v=a7GLJIlZzmk
try this
Mashed_Potatoes said:
I didn't understand you, you managed to flash the ROM but not in bootloader? It won'tsay Google Nexus ADB Interface, i don't remember precisely i've done it a long time ago!
https://www.youtube.com/watch?v=a7GLJIlZzmk
try this
Click to expand...
Click to collapse
I managed to re-install 4.4.4 with wug toolkit in bootloader. I got my OS back but have not been able to get the drivers sorted out (yet) so the Nexus isn't communicating w/the computer fully but I can still flash roms and install apk's w/wug also.
Try a factory reset and reinstall the drivers in PC