Related
Hello all,
My phone randomly turned off today and started hanging on the boot animation screen.
I can still access CWM and fastboot.
I've tried wiping and reinstalling a ROM, but the phone just reboots itself during the install . It also does the same thing during a nandroid restore.
Since I wasn't sure what else to do, I tried to use the GNEX Toolkit to flash to stock. I keep getting write errors when trying to flash. I think the problem is I can't install the ADB drivers on my computer. I've done some research, but it seems that you have to be in Android, with USB Debugging on to install them. I can get the fastboot USB drivers working, but can't do do the restore without the ADB drivers as well.
Also tried Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0
PDAnet needs me to be in Debugging mode.
Tried updating Android 1.0 Driver manually in Device Manager.
Any help would be appreciated. Will thank any helpful posts. Thank you!
This is also my issue and a link to my thread http://forum.xda-developers.com/showthread.php?p=25386193#post25386193
---------- Post added at 05:08 PM ---------- Previous post was at 05:06 PM ----------
TwinkyOfHope said:
Hello all,
My phone randomly turned off today and started hanging on the boot animation screen.
I can still access CWM and fastboot.
I've tried wiping and reinstalling a ROM, but the phone just reboots itself during the install . It also does the same thing during a nandroid restore.
Since I wasn't sure what else to do, I tried to use the GNEX Toolkit to flash to stock. I keep getting write errors when trying to flash. I think the problem is I can't install the ADB drivers on my computer. I've done some research, but it seems that you have to be in Android, with USB Debugging on to install them. I can get the fastboot USB drivers working, but can't do do the restore without the ADB drivers as well.
Also tried Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0
PDAnet needs me to be in Debugging mode.
Tried updating Android 1.0 Driver manually in Device Manager.
Any help would be appreciated. Will thank any helpful posts. Thank you!
Click to expand...
Click to collapse
I have also tried the same stuff the issue is i cant get into debugging mode because the screen doesnt turn on. i have 2 batterys so the battery isnt the issue. (besides the fact that the phone drains the battery but doesnt charge)
Bump
Sent from my SGH-I897 using xda premium
Have you tried Odin?
Sent from my Galaxy Nexus using xda premium
lucas.scott said:
Have you tried Odin?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I got my phone detected by ODIN this morning after numerous driver installs.
However, I've been a little worried to flash a stock ROM through it since the Gnex toolkit had write errors. The guy in this thread seems to have possibly bricked his phone http://forum.xda-developers.com/showthread.php?t=1621430&page=2
I had used "Galaxy Nexus Toolkit V7.7.0 to :
Unlock my BootLoader,
Root my phone
Rename Files Recovery
Flash Recovery (CWM Touch)
Install BusyBox on Phone
And now, i have install the rom JellyBean 4.1.1 with the Recovery Mode :
(I take the Rom here : http://forum.xda-developers.com/showthread.php?t=1737849)
After HAVING done all of this, i try to boot my phone, but he remained stuck on the loading screen (animation) ... even after 1 hours of waiting....
I had go back in recovery mode and I "Wipe" all the DATA, now there is no more operating system on my phone and i'm not able to install a new ROM and i can't even go thru my phone data via USB cauz my computer not recognize my Samsung Galaxy Nexus anymore...
Someone can help me I think I'm in big trouble right now...
This is the problem with toolkits. Things can go wrong and you don't know where it went wrong. See my signature for my thoughts.
As far as getting your phone working again. Follow efrants guide http://forum.xda-developers.com/showthread.php?t=1626895 it has all the info you need to get up and running.
Sent from my Nexus 7 using xda premium
First of all, next time, do not use the toolkit or one-click-root methods. They have more chance of bricking your device than using fastboot commands.
Also, can I ask you which recovery you have right now? Is it clockworkmod or stock?
Ok thanks i try this right now... Hope it will work, i'm freaking out at the moment...
Ok, i'm in big big trouble.
The driver does't find my Device at all. I can't enter in my phone via USB from my PC, so i can't do anything....
They have no more OS on my device, i guess this is why Windows7 dont recognize my phone with any drivers i had try the one from SAMSUNG that have working well for me before i **** up my phone, and now the Universal Naked Driver (http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1) , don't work
**** **** **** (sorry)
Epsilons said:
Ok, i'm in big big trouble.
The driver does't find my Device at all. I can't enter in my phone via USB from my PC, so i can't do anything....
They have no more OS on my device, i guess this is why Windows7 dont recognize my phone with any drivers i had try the one from SAMSUNG that have working well for me before i **** up my phone, and now the Universal Naked Driver (http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1) , don't work
**** **** **** (sorry)
Click to expand...
Click to collapse
Make sure you uninstall any unrelated drivers first. Then proceed with the driver installation.
Sent from my Nexus 7 using xda premium
I have already done this...
I had uninstall the SAMSUNG driver correctly.
And then install the Universal Naked Driver.
Nothing work for me, it's like my phone had no more OS installed, and windows doesnt recognize it.
Epsilons said:
I have already done this...
I had uninstall the SAMSUNG driver correctly.
And then install the Universal Naked Driver.
Nothing work for me, it's like my phone had no more OS installed, and windows doesnt recognize it.
Click to expand...
Click to collapse
Boot into the bootloader. Then install the driver.
Your phone should show up as Android 1.0 in your device manage on your PC. Update that.
Sent from my Nexus 7 using xda premium
I've been seeing issues with the toolkits and rooted my phone hours ago using adb, worked flawlessly except the drivers lol.
But after I got that resolved it worked, no jb issues and no other issues. Recovery stuck as well.
Sent from my Galaxy Nexus using Tapatalk 2
El Daddy said:
Boot into the bootloader. Then install the driver.
Your phone should show up as Android 1.0 in your device manage on your PC. Update that.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Witch driver ? The SAMSUNG or the Universal Naked Driver
Epsilons said:
Witch driver ? The SAMSUNG or the Universal Naked Driver
Click to expand...
Click to collapse
They both should work fine (I got Samsung one installed and works flawlessly), but Naked Driver is better I believe
In my Device Manager on Windows 7 i got :
SAMSUNG Android Phone :
---> Samsung Galaxy Nexus BootLoader Interface
but when i go in "My Computer" , nothing is here, i cant go into my phone to flash a ROM... it's crap !!!!!!!!
And now i'm Unable to install SAMSUNG driver because it's says i need to put my phone into "USB Debbuging Mode" , when i had actually no OS installed on it so i cant do nothing.... what the .....................................!!!!!!!!!!!!!!!!!!!!!!!!!!!!
I'm running with the Universal Naked Driver, but cant even open my phone to copy file on... i think i had broke my phone ! :X
Epsilons said:
In my Device Manager on Windows 7 i got :
SAMSUNG Android Phone :
---> Samsung Galaxy Nexus BootLoader Interface
but when i go in "My Computer" , nothing is here, i cant go into my phone to flash a ROM... it's crap !!!!!!!!
And now i'm Unable to install SAMSUNG driver because it's says i need to put my phone into "USB Debbuging Mode" , when i had actually no OS installed on it so i cant do nothing.... what the .....................................!!!!!!!!!!!!!!!!!!!!!!!!!!!!
I'm running with the Universal Naked Driver, but cant even open my phone to copy file on... i think i had broke my phone ! :X
Click to expand...
Click to collapse
OK so it looks like you have the driver installed.
What is telling you to enable USB debugging mode?
Read the link I posted and flash the stock image via fastboot.
Sent from my Nexus 7 using xda premium
I cant flash anything...
I cant open my phone via My Computer
I cant copy a ROM to my phone
I cant do anything
...
I'm not able to copy files to my Phone, my computer not recognize it at all since my phone had no OS on it....
Epsilons said:
I cant flash anything...
I cant open my phone via My Computer
I cant copy a ROM to my phone
I cant do anything
...
I'm not able to copy files to my Phone, my computer not recognize it at all since my phone had no OS on it....
Click to expand...
Click to collapse
Yes, I realize you can't do these things. I gave you the info to fix your problem in the second post.
You need to boot into the bootloader and flash the stock images with fastboot. I don't know how much clearer I can be.
Be patient with rooting, frustration will lead to mistakes.
Sent from my Galaxy Nexus using Tapatalk 2
Epsilons said:
I cant flash anything...
I cant open my phone via My Computer
I cant copy a ROM to my phone
I cant do anything
...
I'm not able to copy files to my Phone, my computer not recognize it at all since my phone had no OS on it....
Click to expand...
Click to collapse
Ordinarily, I don't recommend tool kits either, but in this case you quite frankly seem like the kind of fella that needs one. SO HERE IT IS. This is a different toolkit than you used before. Be sure to select the correct device first off(because this works with ALL Nexus devices not just one), then do the part entitled "Initial Setup". Do the FULL DRIVER INSTALLATION. It may be that you don't need to, but it will not hurt so do it anyway. After that, click on the "won't boot up" checkbox under "Flash Stock + Unroot" button, then click the button. At all times, read and follow directions. I used this toolkit once, now I do things manually. But you seem incapable. Not intended to be insulting, just a statement of your technical aptitude. Not everyone can do this stuff. So if you have tried EVERYTHING above and been unable to complete any of it correctly, then try this. It isn't one-click and requires some amount of effort on your part. My 11 year old nephew did it though. Good luck.
Epsilons said:
I cant flash anything...
I cant open my phone via My Computer
I cant copy a ROM to my phone
I cant do anything
...
I'm not able to copy files to my Phone, my computer not recognize it at all since my phone had no OS on it....
Click to expand...
Click to collapse
As El Daddy said, you are not reading the instructions. Your fastboot driver IS installed properly if you see "Samsung Galaxy Nexus BootLoader Interface". Follow the instructions step-by-step. You do NOT need to see anything in "My Computer". It seems like you are panicking, and not reading...
---------- Post added at 08:12 PM ---------- Previous post was at 08:09 PM ----------
kyokeun1234 said:
First of all, next time, do not use the toolkit or one-click-root methods. They have more chance of bricking your device than using fastboot commands.
Click to expand...
Click to collapse
And let's not scare the guy: you CANNOT "brick" your device using a toolkit. There is a big difference between not being able to boot because of a bad flash (not a brick), and a device that cannot boot at all (i.e., a brick).
It seems like people are using the term brick to mean a lot of things other than what it was meant to mean: "bricked" means that you cannot boot your device without JTAG, or sending it in for repair, i.e., it's as useful as a brick.
Ok thank you everyone, sorry about my patience tonight...
Now ma Samsung Galaxy Nexus is on Jelly Bean 4.1.1 with SuperUser and all the stuff and i'm happy
So thanks everyone.
I got it
Hello
Here's my proplem:
I flashed cyanogenmod nightly build (12.03.2013) and everyting was fine until i updated my HOX by the cmupdater to the next nightly build (13.03.2013). This build is screwed as i can understand ( http://forum.xda-developers.com/showthread.php?t=1786696 ). Ok, then i flashed old working rom (12.03.2013).
USB connection not working since i flash it, however all other works great. In cwm recovery usb storage is not working too. And even in fastboot mode usb is not working.
sorry for my english... hepl me!
Hi,
Did you install HTC Sync Manager to get the HOX drivers ?
Also, if USB doesn't work in CWM... I suggest you to change your ROM, kernel etc....
(On which ROM, kernel etc. are you ? Did you install any addons ?)
o0oMegA said:
Hi,
Did you install HTC Sync Manager to get the HOX drivers ?
Also, if USB doesn't work in CWM... I suggest you to change your ROM, kernel etc....
(On which ROM, kernel etc. are you ? Did you install any addons ?)
Click to expand...
Click to collapse
Yes, htc sync manager and all drivers are reinstalled about five times - no result. I`ve tried three cords, all three are original.
I was on stock ROM, then i flashed cm10.1. And now I'm on stable nightly cm10.1 build. I just can't flash anything, fastboot isn't working...
In cwm I tried to restore old stock backup, but the phone just stops on bootscreen, because i can't flash boot.img i think...
I'm in panic!
I even don't know what else i can try to do to fix it...
'adb devices' returns nothing; same with 'fastboot devices'. I even can't reinstall fastboot mode drivers, cause there's no reaction from windows when i plug the cable in.
Is it kind of "usb brick" or what?
And... is there another method to flash kernel? without fastboot i mean.
what a moron i am...
Full formating of internal memory via CWM was totally bad idea... Now my HOX is totally bricked.
Please help, mates...
What you can't power it on?
Uninstal all drivers and htc syncmanager from the pc. Go into device manager and delete any entry that has something to do with android phones or myHTC (of its there) reboot the pc
Put the phone in the bootloader and connect it to the pc .....
TToivanen said:
What you can't power it on?
Click to expand...
Click to collapse
I can power it on, but there's nothing but the recovery on it.
Mr Hofs said:
Uninstal all drivers and htc syncmanager from the pc. Go into device manager and delete any entry that has something to do with android phones or myHTC (of its there) reboot the pc
Put the phone in the bootloader and connect it to the pc .....
Click to expand...
Click to collapse
Did it all, nothing happened. In fastboot mode when i plug the cable in "fastboot" becomes "fastboot usb", but windows is't reacting...
Fastboot usb is a start.....what if you perform
Fastboot devices from the command prompt
Mr Hofs said:
Fastboot usb is a start.....what if you perform
Fastboot devices from the command prompt
Click to expand...
Click to collapse
Oh, i've tried it so many times... But "fastboot devices" returns nothing, as i said, any other command writes "waiting for device"
Hmmm im running out of ideas here
So you get nothing in the device manager....not a unknown device or APX ?
Mr Hofs said:
Hmmm im running out of ideas here
So you get nothing in the device manager....not a unknown device or APX ?
Click to expand...
Click to collapse
No, nothing...
Mr Hofs said:
Hmmm im running out of ideas here
So you get nothing in the device manager....not a unknown device or APX ?
Click to expand...
Click to collapse
I've found my old HTC Desire, reloaded it into bootloader, then connected to PC and killed all drivers. With Desire it all work great, but HOX is still bricked...
Hmmm then i guess you have some serious usb brick
---------- Post added at 09:34 PM ---------- Previous post was at 09:32 PM ----------
Do you know your hboot version and cid....the only possible thing i can think of is a ruu ? If it can read the phone
Mr Hofs said:
Hmmm then i guess you have some serious usb brick
---------- Post added at 09:34 PM ---------- Previous post was at 09:32 PM ----------
Do you know your hboot version and cid....the only possible thing i can think of is a ruu ? If it can read the phone
Click to expand...
Click to collapse
It's no good. It can be fixed in HTC Service center?
hboot 1.36.0000
cid 038 (india as i remember)
It belongs to 3.14.720.** but i can't find one....only lower ones, so thats a no go.
I guess its a repair centre issue
Mr Hofs said:
It belongs to 3.14.720.** but i can't find one....only lower ones, so thats a no go.
I guess its a repair centre issue
Click to expand...
Click to collapse
I think RUU can't help...
To say that it's sad - is to say nothing...
Anyway, thanks a lot for trying to help, mate! :good:
Well i wish you all the best and i really hope you get it sorted ! This goes beyond my knowledge
Ok, my HOX has been bricked too once.
To unbrick it, I downloaded the ROM of my Internet provider (SFR) and installed it on my phone... (I had no waiting for device issue but to put the rom inside my SD card I used the CWM recovery)
Then I installed a custom ROM.
Also, you may try to :
1. Google your " Waiting for device " issue in fastboot usb mode
2. Get a new fastboot kit. I use the "zedomax"'s fastboot kit (it's a Youtuber) You may find the kit in videos descriptions.
I suppose you didn't make any backup of your HOX thanks to the CWM... :l
(I didn't make any backup of my HOX when it's bricked but now it's working fine...)
Good luck !
o0oMegA said:
Ok, my HOX has been bricked too once.
To unbrick it, I downloaded the ROM of my Internet provider (SFR) and installed it on my phone... (I had no waiting for device issue but to put the rom inside my SD card I used the CWM recovery)
Then I installed a custom ROM.
Also, you may try to :
1. Google your " Waiting for device " issue in fastboot usb mode
2. Get a new fastboot kit. I use the "zedomax"'s fastboot kit (it's a Youtuber) You may find the kit in videos descriptions.
I suppose you didn't make any backup of your HOX thanks to the CWM... :l
(I didn't make any backup of my HOX when it's bricked but now it's working fine...)
Good luck !
Click to expand...
Click to collapse
I have few backups: of stock ROM and of cmROM, but it's no connection when i mount mass storage in CWM...
Hey guys i've been looking through alot of google and can't seem to come up with anything so i turn to you awesome people.
My friend got a Galaxy Nexus GSM and he bought it with a boot loop problem. The phone is rooted and bootloader unlocked. I know because i can go to CWM recovery and also theres the unlock sign on it. However I can't get my computer to recognize it what so ever not even mount the storage. I figure i need to get the drivers to install but i need it to be recognized in device manager to do it through a rootkit. I tried to install the ADB drivers but also got no luck. I then tried to get to ODIN for it to work but ODIN won't recognize it either. Is there any way to install the drivers so i can put on a ROM on this. I think the person he bought it from formatted everything and messed it up. Is there anyway i can install the drivers without getting it to recognize first? I tried it in windows 7 and in windows 8. ANY HELP IS GREATLY APPRECIATED!!!
dnpmoney45 said:
Hey guys i've been looking through alot of google and can't seem to come up with anything so i turn to you awesome people.
My friend got a Galaxy Nexus GSM and he bought it with a boot loop problem. The phone is rooted and bootloader unlocked. I know because i can go to CWM recovery and also theres the unlock sign on it. However I can't get my computer to recognize it what so ever not even mount the storage. I figure i need to get the drivers to install but i need it to be recognized in device manager to do it through a rootkit. I tried to install the ADB drivers but also got no luck. I then tried to get to ODIN for it to work but ODIN won't recognize it either. Is there any way to install the drivers so i can put on a ROM on this. I think the person he bought it from formatted everything and messed it up. Is there anyway i can install the drivers without getting it to recognize first? I tried it in windows 7 and in windows 8. ANY HELP IS GREATLY APPRECIATED!!!
Click to expand...
Click to collapse
read the stickies
http://forum.xda-developers.com/showthread.php?t=1626895
Pay attention to Section A. Forget Odin, no need to be using that.
First off thanks so much for the reply and help it is very aprreciated!
Secondly i did come across this sticky however like i stated the phone is in a boot loop which means i cant get past the google logo in order to set it in developer mode and set usb-debugging neither can my computer recognize the phone when i plug it in, using the original cable i've tried every port there is on my desktop and laptop and nothing comes up in device manager. The phone is completely wiped and no OS is on it. Is there any way i can get a ROM on the phone?! This is one idea i have but i don't know if it'll work, I was thinking of buying a another working nexus install the drivers with that one and then i can get the bootloop one to get recognized? and return the new one. Will that work?
dnpmoney45 said:
First off thanks so much for the reply and help it is very aprreciated!
Secondly i did come across this sticky however like i stated the phone is in a boot loop which means i cant get past the google logo in order to set it in developer mode and set usb-debugging neither can my computer recognize the phone when i plug it in, using the original cable i've tried every port there is on my desktop and laptop and nothing comes up in device manager. The phone is completely wiped and no OS is on it. Is there any way i can get a ROM on the phone?! This is one idea i have but i don't know if it'll work, I was thinking of buying a another working nexus install the drivers with that one and then i can get the bootloop one to get recognized? and return the new one. Will that work?
Click to expand...
Click to collapse
You need to get adb to work with your device, which you can do in a custom recovery. You don't need to have USB debugging enabled, you would if you were booting into the OS, but not the recovery.
You can get drivers setup while in recovery or fastboot just as easy as if you were booted into the OS, so no you don't need another device.
cupfulloflol said:
You need to get adb to work with your device, which you can do in a custom recovery. You don't need to have USB debugging enabled, you would if you were booting into the OS, but not the recovery.
You can get drivers setup while in recovery or fastboot just as easy as if you were booted into the OS, so no you don't need another device.
Click to expand...
Click to collapse
thanks thats great news cause i dont have that kind of cash but how do i get ADB to work with the phone every installation guide i've looked at requires that i have the phone recognized om device manager. Is there anyway to install adb without having the device to recognize?
dnpmoney45 said:
thanks thats great news cause i dont have that kind of cash but how do i get ADB to work with the phone every installation guide i've looked at requires that i have the phone recognized om device manager. Is there anyway to install adb without having the device to recognize?
Click to expand...
Click to collapse
again, read the thread i gave you. if you're still asking this question, read it again.
Isn't that for the nexus 4? And I did pay attention to section A but it told me how to install the drivers which is the same way as every other tutorial I've looked at. My device doesn't show up on my computer and I can't install their way. As for the fastboot driver installation idk what their talking about. I followed the instructions though and got no results. I didn't do the whole thing cause for part C I need the original rom for galaxy nexus and also I don't know if the platform tools zip is for my device so I haven't gone through with it just yet. I'm sorry it's not my phone so I don't want to mess it up even further. I've read about the part with it being in recovery mode with the volume up + power option but I'm at work and haven't tried that yet but I doubt that will work since the phone is clean. Can u please be a little more specific there's 99 pages that I have to go through for that sticky. If u can't it's ok I'll just have to go through it next week. Once again thanks for pointing me in the right direction and giving me some hope.
Sent from my Nexus 4 using xda premium
WTF, how in the hell did that thread get here, sorry man
This is the right one
http://forum.xda-developers.com/showthread.php?t=1626895
a maguro wrote this.
Oh ok thanks this makes a lot more sense. Sorry for not telling u that earlier lol.
seriously thanks ill try it tonight.
Sent from my Nexus 4 using xda premium
ok so i tried the link but im always stuck with part A. When i go into fastboot and then try the command "fastboot devices" it hangs on waiting for the device. I can't see the device anywhere on my computer to install the fastboot drivers as instructed by 1wayjonny in this post http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1
Am i missing something here? i did everything in the other steps such as downloading all the files into the same directory and everything. Im using windows 7 and i updated all my drivers for usb and even tried different usb cables including the original and usb2.0 and 3,0 ports but still no dice. I also tried it on windows 8 and got the nada.
dnpmoney45 said:
I can't see the device anywhere on my computer to install the fastboot drivers as instructed by 1wayjonny in this post http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1
Click to expand...
Click to collapse
You reboot the device into bootloader/fastboot mode, then you connect the USB, and there's no sign at all that a USB device has been installed?
Remove all drivers, reboot, and start over. Get a tool for Windows that allows you to really dig on all of the installed drivers and remove all Nexus devices drivers permanently. Rant: Umm, Windows sucks bad. Thanks Linus!
bk201doesntexist said:
You reboot the device into bootloader/fastboot mode, then you connect the USB, and there's no sign at all that a USB device has been installed?
Remove all drivers, reboot, and start over. Get a tool for Windows that allows you to really dig on all of the installed drivers and remove all Nexus devices drivers permanently. Rant: Umm, Windows sucks bad. Thanks Linus!
Click to expand...
Click to collapse
I've done it both ways just to ensure it wasn't something that simple. I uninstalled all drivers i can possibly find theres non no where i used CC to look for more and device deview and even unistalled the java se and eclipse and android SDK and all the packages and installed them again and still nothing. My nexus 4 however recognizes both in adb and fastboot ......
Anything at all? Anyone?
Sent from my Nexus 4 using xda premium
dnpmoney45 said:
Anything at all? Anyone?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Well, maybe you could try omapflash. If you can't get several PCs to see the device, then something's wrong with the USB port?
Not even on Linux?
a manta wrote this.
bk201doesntexist said:
Well, maybe you could try omapflash. If you can't get several PCs to see the device, then something's wrong with the USB port?
Not even on Linux?
a manta wrote this.
Click to expand...
Click to collapse
I did a little looking up about omapflash and from what i can see so far there needs to be drivers installed first. I may be wrong but i have to do some more research on it and i dont have a linux pc my laptop is down thanks to a power pin connector pin being pulled out. and i dont know if the device port is good or bad i can get a charge but that doesnt mean its fine. What if i get another device and install drivers via that and then try to get it to recognize? would that work?
dnpmoney45 said:
What if i get another device and install drivers via that and then try to get it to recognize? would that work?
Click to expand...
Click to collapse
To really make sure that the issue isn't on the host side but rather the USB port on the device? Yeah, that would rule it out.
Also, I just remembered: you're not using the USB ports of your PC case are you? Make sure you're using the motherboards' own USB ports.
a maguro wrote this.
bk201doesntexist said:
To really make sure that the issue isn't on the host side but rather the USB port on the device? Yeah, that would rule it out.
Also, I just remembered: you're not using the USB ports of your PC case are you? Make sure you're using the motherboards' own USB ports.
a maguro wrote this.
Click to expand...
Click to collapse
Thats all it would do?! What about making me able to install the drivers and get the phone to be recognized? No wont work im dreaming?
And no im not using case ports at all i use them for charging and thats all i know at least that those arent reliable.
Windows 8 64-bit...drivers install...stuck
even I am stuck on the same roadblock. have my GNex stuck on the google logo. can access recovery mode though (TWRP 2.5.0.0). Now i just upgraded my PC to Windows 8 64-bit and cant seem to be able to install drivers.
the problem is that almost all the methods require:
1. GNex to be connected with USB Debugging ON
2. install ADB Drivers
3. get into Fastboot or Recovery
4. install Bootloader Drivers
since i cant get past the Google logo on my GNex...i cant perform Steps 1 & 2.
and if i directly try to install the bootloader drivers the OS returns an error (yellow exclamation next to the installed driver)
Added pictures to help explain better.
Thnx in advance.
rej_ares said:
even I am stuck on the same roadblock. have my GNex stuck on the google logo. can access recovery mode though (TWRP 2.5.0.0). Now i just upgraded my PC to Windows 8 64-bit and cant seem to be able to install drivers.
the problem is that almost all the methods require:
1. GNex to be connected with USB Debugging ON
2. install ADB Drivers
3. get into Fastboot or Recovery
4. install Bootloader Drivers
since i cant get past the Google logo on my GNex...i cant perform Steps 1 & 2.
and if i directly try to install the bootloader drivers the OS returns an error (yellow exclamation next to the installed driver)
Added pictures to help explain better.
Thnx in advance.
Click to expand...
Click to collapse
SOLVED (Dont know how but it worked):
1. Factory reset (TWRP)
2. Installed an old ROM which was already on the GNex
3. Restart...it gets stuck at the Google logo...remove battery
4. TWRP - Factory reset
5. reboot...
Hello,
I really dont know what to do anymore.
No matter which ROM I flash, I always get stuck in a bootloop. I always wait 20-25 for a boot, but it doesnt pass the bootanimation.
Here is what happened:
My PC didnt recognize my phone anymore even though I didnt change any driver settings or something like that. Same with other PCs, not even showing up in device manager at all. So I thought I messed up some settings in my phone, thats why I wiped data, system, cache, internal store, then pushed a new ROM to my phone via USB OTG, but it doesnt boot at all. Phone still doesnt get recognized by any pc, not even in TWRP or bootloader.
Here are the things I tried so far:
- Ressurrection Remix (latest 3 versions) with OpenGapps
- Lineage OS with DynamicGapps
- both of them without any gapps
- OMNI Rom with DynamicGapps
I also did a factory reset before every flash. After 20 minutes of bootloop I also tried a 2nd boot for 20 minutes...nothing.
Since I cant access my phone from PC I cant flash stock ROM (or is it possible to flash it via TWRP?). I guess I just wiped something that I shouldnt have wiped. Does anyone have an idea what else I could try?
I had something similar happen to my 5x a while back. After fiddling with drivers/device manager etc, I found this on net which actually worked for me:
Solution 5 – Uninstall Android drivers if PC not recognizing phone
Sometimes you might not have the latest drivers, or your drivers might not be properly installed, so in order to fix issues with Android devices and Windows 10, it’s advised that you uninstall your Android drivers. To do so, follow these steps:
Connect your Android device to your computer and open Device Manager.
In Device Manager locate your Android device. Usually it’s located in Other Devices or in Portable devices section, but the location might be different on your computer.
Right click the device and choose Uninstall.
uninstall-driver
After the drivers have been uninstalled, disconnect your Android device.
Reconnect it again, and wait for Windows 10 to install its drivers again.
Check if your Android device is now recognized.
---------- Post added at 06:09 PM ---------- Previous post was at 06:06 PM ----------
Above post fixed my driver/PC not recognizing phone issue. As far as your bootloop issue, I'm assuming your bootloader is still unlocked, right? If so, and if above fix works where PC recognizes phone, try flashing google factory images via fastboot commands.
jrotert said:
I had something similar happen to my 5x a while back. After fiddling with drivers/device manager etc, I found this on net which actually worked for me:
Solution 5 – Uninstall Android drivers if PC not recognizing phone
Sometimes you might not have the latest drivers, or your drivers might not be properly installed, so in order to fix issues with Android devices and Windows 10, it’s advised that you uninstall your Android drivers. To do so, follow these steps:
Connect your Android device to your computer and open Device Manager.
In Device Manager locate your Android device. Usually it’s located in Other Devices or in Portable devices section, but the location might be different on your computer.
Right click the device and choose Uninstall.
uninstall-driver
After the drivers have been uninstalled, disconnect your Android device.
Reconnect it again, and wait for Windows 10 to install its drivers again.
Check if your Android device is now recognized.
---------- Post added at 06:09 PM ---------- Previous post was at 06:06 PM ----------
Above post fixed my driver/PC not recognizing phone issue. As far as your bootloop issue, I'm assuming your bootloader is still unlocked, right? If so, and if above fix works where PC recognizes phone, try flashing google factory images via fastboot commands.
Click to expand...
Click to collapse
Since it doesnt show up in device manager, I cant uninstall the driver there.
I also tried it on a new PC that did never get in touch with an android phone - nothing. Not even a sound when I plug it in. The phone is just charging, thats it.
Have you tried using a different cable?
Keksdroid said:
Hello,
I really dont know what to do anymore.
No matter which ROM I flash, I always get stuck in a bootloop. I always wait 20-25 for a boot, but it doesnt pass the bootanimation.
Here is what happened:
My PC didnt recognize my phone anymore even though I didnt change any driver settings or something like that. Same with other PCs, not even showing up in device manager at all. So I thought I messed up some settings in my phone, thats why I wiped data, system, cache, internal store, then pushed a new ROM to my phone via USB OTG, but it doesnt boot at all. Phone still doesnt get recognized by any pc, not even in TWRP or bootloader.
Here are the things I tried so far:
- Ressurrection Remix (latest 3 versions) with OpenGapps
- Lineage OS with DynamicGapps
- both of them without any gapps
- OMNI Rom with DynamicGapps
I also did a factory reset before every flash. After 20 minutes of bootloop I also tried a 2nd boot for 20 minutes...nothing.
Since I cant access my phone from PC I cant flash stock ROM (or is it possible to flash it via TWRP?). I guess I just wiped something that I shouldnt have wiped. Does anyone have an idea what else I could try?
Click to expand...
Click to collapse
try Wug's Nexus Root Toolkit he is able to flash phone in bootloop
panicbear said:
Have you tried using a different cable?
Click to expand...
Click to collapse
I dont have any other cable, but maybe I should get a new one just to test. The cable I have is just 3 months old and was high quality....
pincher65 said:
try Wug's Nexus Root Toolkit he is able to flash phone in bootloop
Click to expand...
Click to collapse
Yeah I always used that tool in the past. But since my PC doesnt recognize the phone at all, not even in fastboot mode, that doesnt help me. I really need a solution that works just with TWRP...
Edit: Just an idea from my side. Would it work if someone, who just cleaned flashed, makes an nandroid backup, which I just restore with TWRP?
what radio at you installed? 7.1.1 02.2017 for TWRP
pincher65 said:
what radio at you installed? 7.1.1 02.2017 for TWRP
Click to expand...
Click to collapse
Radio is m8994f-2.6.36.2.20 - flashed it in December.
For TWRP?? Can I flash the stock zim through TWRP?
Keksdroid said:
For TWRP?? Can I flash the stock zim through TWRP?
Click to expand...
Click to collapse
yes. also PixelROM has full img
pincher65 said:
yes. also PixelROM has full img
Click to expand...
Click to collapse
Okay I will try that. I guess I will loose TWRP when I flash it?!
Keksdroid said:
Okay I will try that. I guess I will loose TWRP when I flash it?!
Click to expand...
Click to collapse
No.
pincher65 said:
No.
Click to expand...
Click to collapse
So I tried the stock rom and pixel rom, both when I try to flash them I get the Error message "Zip file is corrupt". There is no md5sum to check if its really corrupt...
Keksdroid said:
So I tried the stock rom and pixel rom, both when I try to flash them I get the Error message "Zip file is corrupt". There is no md5sum to check if its really corrupt...
Click to expand...
Click to collapse
disable check md5sum in setting TWRP.
pincher65 said:
disable check md5sum in setting TWRP.
Click to expand...
Click to collapse
Either way I'm blind, or I dont have that setting...
Keksdroid said:
Either way I'm blind, or I dont have that setting...
Click to expand...
Click to collapse
sorry, I have inattentively read the previous post. redownload zip if doesn't help, then your recovery is damaged and it is necessary to look for a way to connect him to PC
Problem solved. Got a new USB cable today, it worked now. Flashed stock image, it finally booted.
But wow, the old cable is already broken after 3 months...well it still charges very fast, but thats it.