So normally I can read my way through forums and get my device unlocked. I just can't get it done with the Nexus Q. I'm having problems with getting the drivers. I can't even turn on usb debugging. I called Google for help and they did even know what it was till they looked it up. Can I commission someone to help me? Does anyone have any help? All I want is to use it as a wireless amp, but it seems like only a dream.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Gagamonstar said:
So normally I can read my way through forums and get my device unlocked. I just can't get it done with the Nexus Q. I'm having problems with getting the drivers. I can't even turn on usb debugging. I called Google for help and they did even know what it was till they looked it up. Can I commission someone to help me? Does anyone have any help? All I want is to use it as a wireless amp, but it seems like only a dream.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
a wireless amp?
try this
I can't post links cause I'm too new...
Google 'nexus q debug mode' and there should be a stackoverflow result that says 'android - Anyone know how to turn on USB debugging "ON ...'. Go there and follow the instructions on unlocking your device. Then install Cyanogenmod.
I still haven't figured out how to do this, but my understanding is that you have to either boot or flash a boot image which is insecure (meaning that debugging is turned on) and then use the adb commands. This can be done from fastboot when the Q is booted into bootloader.
To put it into bootloader you plug in the Q, then immediately cover the "eye" LED on the front of the Q and slightly push the Q down. It doesn't seem that it works if you are covering it when the eye when the cable is plugged in. It has to go from light to no light. The ring then starts blinging red, and then you remove you hand. The ring turns solid and the Q is in bootloader mode. If you keep the hand on while it's blinking it runs recovery factory reset.
Be sure to post if you find an insecure boot disk that works.
Related
Yesterday I tried to open an flv video file, downloaded from my Google Drive. When it got to 100% downloaded, and about to open, my screen went black. No response at all. I could see that the screen was at least backlit, but I couldn't power the phone down, or anything. So I took the battery out and put it back in. Phone boots up, then goes immediately into the same black screen. Took the battery AND SIM card out this time, waited a few minutes, put these back in, held the power key.. nothing. No response. Can't even boot into recovery mode. Even charging the phone does not yield any response, such as the LED turning on. However, when I plug the phone into my PC, my PC starts looking for a new driver for QHSUSB_DLOAD, which it can't get drivers for.
Any suggestions? Besides buying a new phone?
Are you able to boot into hboot?
Sent from my myTouch 4G using XDA Premium HD app
bricked MyTouch 4G
Almost the same thing with my MyTouch 4G. Phone won't boot anymore. When I press the power button the backlight just lights up but the screen is black. The LED flashes amber when i plug it to the charger or to a USB port but the pc can't detect it.
Sad.
no guarantees, but...
found this QHSUSB_driver(64 bit win, couldn't find 32 bit, sorry). save it, unzip it, plug your phone in, go to device manager(volume down and power if nothing shows) click your device(could say something like 'Other device
qhsusb_dload' with a question mark)right click and either uninstall driver and re-install, or update driver using the new one you downloaded, this should force your computer to recognize your device. I haven't tried this(because I haven't had this issue myself) so I can't guarantee anything. Just didn't see a lot of responses, so I figured maybe a bad idea could be better than none...? Really hope this helps you out!
QHSUSB_DLOAD driver won't give him anything unless he has a special SW and skills to reprogram the HBOOT. Currently his HBOOT is failed/erased, and the phone won't boot. There is a project in Sensation forums going on, trying to achieve just that (reloading corrupted HBOOT through SW over QHSUSB_DLOAD), but I don't know the status.
Jack_R1 said:
QHSUSB_DLOAD driver won't give him anything unless he has a special SW and skills to reprogram the HBOOT. Currently his HBOOT is failed/erased, and the phone won't boot. There is a project in Sensation forums going on, trying to achieve just that (reloading corrupted HBOOT through SW over QHSUSB_DLOAD), but I don't know the status.
Click to expand...
Click to collapse
I see, said the blind man. Unfortunately, that is quite a bit above my pay grade. It would seem, however, that the unbricking of the sensation is now complete. It's not n00b friendly(i.e. you won't see me anywhere near it) but here's a link http://forum.xda-developers.com/showpost.php?p=23580776&postcount=279 to look into it and maybe someone smarter than myself(like Jack_R1) can tell you if it will work for your phone.
@Jack_R1 Thanks for not just saying I'm an idiot, and instead explaining it. Not everybody here is quite as decent about this stuff as you were.
You suggested the correct driver for his situation, and after my post you've pointed him to the right thread in Sensation forum - this is more than I did. So by no means you should think of your help less than what it was.
OP, you can try Sensation guide. Don't proceed if you won't be able to identify the HBOOT version.
Ok so I have been reading around and most of what I found about my specific problem (boot loop with never putting any custom restore or root or ANYTHING on it) was pretty much was useless. I am not a complete beginner I have put custom mods on many of my devices, defy, atrix, dell streak, ect, and I have used ADB among other things (not that I am a pro at it mind you!)
I realize theres a thread up for this here
http://forum.xda-developers.com/showthread.php?t=1356257
but I want to know if this will work or is for people WHO HAVE NEVER DONE ANY MODIFICATIONS TO THEIR KINDLE FIRE
If it is then I will give it a shot.
What happened is (to my knowledge) my daughter was playing with it, and the next morning, it was boot looping, and quickly. So when I turn it on, it shows kindle fire then goes black, then repeats or once in a while will make it to the slide to unlock but 2-3 seconds after goes black and continues the bootloop
ANY HELP GREATLY APPRECIATED!
I recommend giving Amazon a call and get the device replaced.... If you still have a warranty?
AustinFire said:
I recommend giving Amazon a call and get the device replaced.... If you still have a warranty?
Click to expand...
Click to collapse
Why would I even try to fix it if I had a warrant? .... thanks anyways...
so ive downloaded the drivers and its basically not working, and the method for deleting the drivers (the one some idiot posted at least) will only work IF THE DEVICE STAY CONNECTED... Which it obviously isnt... and the 3-4 seconds of it saying KINDLE FIRE isnt long enough for me to find it in the device manager... by the time that updates its already rebooting...
so please anybody.... i dont understand why it would be so difficult.... I JUST NEED A RECOVERY I DONT NEED ANY OF MY STUFF
I have tried running ADB shell it says device not found....
If it is a hardware problem, then flashing is pointless. It did this on its own. Processor or board issue. Given the variety of things I see posted, hardware is an issue at least 1/3 of the time, my guess.
Sent from my Amazon Kindle Fire using xda app-developers app
Ixthusdan said:
If it is a hardware problem, then flashing is pointless. It did this on its own. Processor or board issue. Given the variety of things I see posted, hardware is an issue at least 1/3 of the time, my guess.
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
I would agree with you but i had installed some apps prior that seemed to make it glitchy and slow, and my daughter probably just triggered something (she is 3 and just constantly opens and taps things, i caught her in settings before) ... im pretty positive its software, especially since I read a few people with the same exact symptoms of mine... (it shows logo then reboots repeatedly, but sometimes makes it to the slide screen for like 4 seconds then it goes back to boot loop) Im sure I could fix it but I need help with getting my ADB in order or im screwed xD
I have also read several places that my problem could be fixed with a factory cable...
Have you tried a hard reset (hold the power button down for 30 seconds then power back on)? That should clear any stuck apps. It also sounds similar to a low power boot loop. If you haven't tried charging it you might want to put it on the charger overnight and see what that does. Other than that I don't know why a stock KF would bootloop.
Sent from my Amazon Kindle Fire using xda premium
Dead Battery
This is covered in a sticky post
http://forum.xda-developers.com/showthread.php?t=1623244
JimCo06 said:
Have you tried a hard reset (hold the power button down for 30 seconds then power back on)? That should clear any stuck apps. It also sounds similar to a low power boot loop. If you haven't tried charging it you might want to put it on the charger overnight and see what that does. Other than that I don't know why a stock KF would bootloop.
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
I have tried all of that, many times in fact. I also think its odd that it got stuck in a bootloop but from what ive read stock KF do that sometimes and its usually as simple as changing the way it boots which is why I think the factory cable is what I really need...
kinfauns said:
This is covered in a sticky post
http://forum.xda-developers.com/showthread.php?t=1623244
Click to expand...
Click to collapse
like i said... thats why i think i need a factory cable (fastboot)... but the problem here is i dont have a factory cable... lmao!
so basically im stuck at the fact that the drivers arent working, thus the KF is not being recognized, making fastboot impossible, or am i wrong? somebody please clarify...
Untraumatized said:
like i said... thats why i think i need a factory cable (fastboot)... but the problem here is i dont have a factory cable... lmao!
so basically im stuck at the fact that the drivers arent working, thus the KF is not being recognized, making fastboot impossible, or am i wrong? somebody please clarify...
Click to expand...
Click to collapse
You don't know whether or not your fastboot drivers are working because you must first put the device into fastboot mode to see if Windows will load the appropriate drivers.
Your problem is that on a stock device unable to boot into the system, 2 out of the 4 possible ways of putting the KF into fastboot mode are unavailable to you. The remaining options are to use a factory cable or to crack the case open to get access to the motherboard.
http://forum.xda-developers.com/showthread.php?t=1668159
There's another thread on the forums here about someone who disconnected the battery and hardwired it to a charger, but that seems like a really bad idea to me. A factory cable is your best/safest first step to getting out of your situation.
Hello everyone, I'm in need of a bit of assistance and was hoping you all might be able to help. So last night when I woke up to use the restroom i used my phone to guide me using the screen as a light since we are removing all Christmas decorations and I did not want to step on any of them. On my way back from the restroom the screen light turned off and will not turn back on. I have been trying to reset it all morning long using the power\volume key method and this time it will not work. The phone will not recognize any sort of input from me but when i connect it to my computer, the computer recognizes it and tries to install some random drivers.
Shortly after this I got a flashing red led light. Also the phone attempted to boot up but then will revert to the red light. I was able to get into the bootloader and from there went to the recovery. I wiped all data and cache and tried reinstalling the PAC rom and the franco kernel and gapps thinking this would fix my problem. It did not and now I am out of ideas. I am not sure what to do and have looked around and figured it is not the battery issue since I was able to get into the bootloader and the recovery.
Currently the only thing I can get it to do is if i hold both volume buttons and the power button while connected to my PC there will be a solid red light. I am still trying to get into the bootloader again but so far no success. Thanks in advance for any help or suggestions anyone may have.
See if this can help? I don't know. Tough situation buddy.
http://forum.xda-developers.com/showthread.php?t=2250454
Sent from my Nexus 4 using xda app-developers app
My sister has an old note 4 that she wants her pics and stuff off. The screen is completely broken and doesn't turn on. The phone will boot up, it's running stock with no root and the us option was set on charge only.
Is there a way to still access the internal data without the screen, with use charging only set??
DoSe420 said:
My sister has an old note 4 that she wants her pics and stuff off. The screen is completely broken and doesn't turn on. The phone will boot up, it's running stock with no root and the us option was set on charge only.
Is there a way to still access the internal data without the screen, with use charging only set??
Click to expand...
Click to collapse
Developer options unlocked on this phone?
If yes try this app called Vysor. It needs USB debugging though which is under dev options.
Install it on your Computer & it will install the app on your phone.
vishnu vijay said:
Developer options unlocked on this phone?
If yes try this app called Vysor. It needs USB debugging though which is under dev options.
Install it on your Computer & it will install the app on your phone.
Click to expand...
Click to collapse
I don't think so. As far as I know, nothing was ever tweaked to need Dev enabled.
adb commands to verify what can you do - if no usb debugging, then no.
Hey guys!
Dropped my phone. Screen is completely black. Charges fine. Fully charged now, notification light went from red to green.
Plug into PC, I hear the Windows USB mount sound, I see option to disconnect. In Device Manager, under Android Devices, Nexus 6p Adb Interface. In abd, no devices listed.
Device was rooted and 100% had debugging enabled, but since the screen went dark, a bunch of buttons were pressed and I have no idea what has happened as a result. If I had to guess.. if is in download, or recovery mode. I can't tell.
Any ideas on how I can regain access without spending money (haha, I know)? I read somewhere that the Nexus 6p doesn't have HMDI out. Is that true? So that wouldn't be an option? I just need to know if fixing the screen will fix the phone. It doesn't appear anything else is damaged, but how do I know for sure?
Thanks!