Hey, so my nexus died while it was connected to a PC. I was sending a movie to nexus but the transfer was frozen so I decided to pull out the cable/don't judge me/. After that I realised that its off and doesn't react at all.
If I connect it to PC it tries to install apx driver without success.
It doesn't boot/adb won't find device.
Any chance to wake it up? Guess I should use warranty.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Have you tried holding the power button for 20-30 seconds?
Sent from my Nexus 7(2012) that has zero issues.
Of course that was first thing I did also with hard reset.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
margaretiak said:
Hey, so my nexus died while it was connected to a PC. I was sending a movie to nexus but the transfer was frozen so I decided to pull out the cable/don't judge me/. After that I realised that its off and doesn't react at all.
If I connect it to PC it tries to install apx driver without success.
It doesn't boot/adb won't find device.
Any chance to wake it up? Guess I should use warranty.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi, margaretiak...
Some questions....
What do you see when you plug the Nexus 7 into the charger?
Do you see the WHITE-ON-BLACK battery charging animation?
Do you see anything on the screen at all? Any hint of illumination?
Sorry for all the the questions.... just trying to better understand your situation.
Have you tried these various button combinations?
http://forum.xda-developers.com/showthread.php?t=2133986
-----------
If you're PC is trying to install APX drivers, that, unfortunately, is not a good sign, as it's suggestive of a dead bootloader. APX drivers are typically used for nvFlashing, amongst other things, bootloaders. Unfortunately, nvFlash in APX mode, for the Nexus 7, is a mystery that thus far, nobody yet has been able to crack.
If you do have a dead bootloader, there's really not much that can be done, other than an RMA under warranty.
Very unusual, though, for a file transfer to cause this kind of problem...
Rgrds,
Ged.
Yep,it's totally dead. Display is off. Well I havnt lost anything important guess/got tib in PC/ so I'll get new one nexus. Hope they can't find out that it's rooted/modified.
And few days ago I had also problem with nexus. Guess also while I was transfering files..but via USB otg. I lost connection to HDD and then nexus has turned off. When I tried to turn it on, nexus was blinking/flashing. After some time I managed to boot into recovery so I deleted caches and it worked.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
The HDD removal crash is a bug in the kernel. But it shouldn't kill your device completely like that.
Shouldn't but it did. Running slim ROM 4.2 without any kernel based modification.
Well I'm not desperate since it has the screen lifting from the begin. I just hope I'll get new one or repaired..at least I can add screen lifting to issues.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Just to know..they replaced motherboard but in service they made few scratches on my n7 so I returned it with this and also screen lifting (that i forgot to add before)
Related
So... I cannot turn on my Asus tf101 unless I plug it in to a power source, once the screen lights up I can unplug it immediately and it functions normally when turned on. I bought this device refurbished from best buy a few months back, I dealt with the issue but now am looking to sell it. Any ideas on how to fix this? I have never rooted the device, however I have tried factory resets and cold boots.
mled203 said:
So... I cannot turn on my Asus tf101 unless I plug it in to a power source, once the screen lights up I can unplug it immediately and it functions normally when turned on. I bought this device refurbished from best buy a few months back, I dealt with the issue but now am looking to sell it. Any ideas on how to fix this? I have never rooted the device, however I have tried factory resets and cold boots.
Click to expand...
Click to collapse
Are you holding the pwr button long enough. If so,it sounds like the switch is bad.
I hold the power button for 12 seconds and try it with different variation holding volume keys. It functions fine when the device is powered on.
Sent from my Galaxy Nexus using xda app-developers app
It could be a bad battery or your charger is only giving enough to power the device on. I would try a new charger first.
Sent from my Transformer TF101 using xda premium
But once powered on, it functions flawlessly. The only issue is turning it on.
Sent from my Galaxy Nexus using xda app-developers app
I'v got the same problem. So +1. Any ideas?
I have the same problem, i am actually talking with the Asus Support Centre
I emailed them. All I can do.
Sent from my Galaxy Nexus using xda app-developers app
mled203 said:
I emailed them. All I can do.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Do you have the keyboard docking station for it?
Are you on custom ROM or OEM?
What "app killers" are you running?
Some custom ROM's have had similar issues a long while back. maybe yours is getting that issue IF your running custom.
Keyboard dock, if you have it, does it do the same thing for powering on, where it needs to be plugged in to start the screen?
I only ask about the app killers because I had experienced a similar issue about a year ago due to an app killer I had installed. Removed it, and the phone worked fine. Put it back on and it reverted back to having to be plugged in to start the screen.
Have you tried a clean wipe of everything on the tablet? And I do mean CLEAN, no dirty flashes here (keep your pants on bud).
Lastly have you given the charge port a good ole blow out lately? Long bursts aren't really going to do any damage, but I would stick to short quick bursts of compressed gas, again NO VACUUM CLEANERS. They create static and the charge port is quite susceptible to static discharge.
I know your pretty intelligent, but let me put it out there again. DON'T be a fool and use alcohol on your tool.
This post made me laugh. I do not have the keyboard docking station. I have never installed any task killers as I do not believe in them. The tablet has been running the stock ROM the whole time and has never been tampered with.
Sent from my Galaxy Nexus using xda app-developers app
And yes I have done a factory reset twice with no success.
Sent from my Galaxy Nexus using xda app-developers app
mled203 said:
And yes I have done a factory reset twice with no success.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
But you never said if you gave the ole girl a good ole cleaning in the slot.
I would venture to say that you need to send it in to Asus or take it back to Best Buy (if your able to). It sounds like there may be a voltage issue with the digitizer or the inverter.
And NEVER EVER EVER Invert your digits while cleaning out the slot.
You also didn't say if you went deep up in the ole girl and gave her a good rootin.
I'm working with Asus right now and of course there's something wrong with my serial number. Nerve been rooted. Blew it out and that did nothing.
Sent from my Galaxy Nexus using xda app-developers app
mled203 said:
I'm working with Asus right now and of course there's something wrong with my serial number. Nerve been rooted. Blew it out and that did nothing.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Please keep us posted as I am curious to know how ASUS customer service is to deal with.
Well, I am trying to send my TF to Asus to fix the problem and they are a bit annoying. I have just dealt with HTC before and that was wonderful, but here they have send me 4 emails asking me to wipe, to update and to do everything that I have already done, and after that they have sent me to another web to fill another questionary. With HTC I just had to told them the IMEI and in 4 days I had my phone back
I had similar issue with mine. It was one of the reason I took back to best buy and used the buy back.
I then picked up the Nexus 7.
Sent from my Nexus 7 using Tapatalk 2
I had a similar issue, do you use your device often ?
I figured out after a couple of months that each time it showed this behaviour the battery was in fact empty and it was in fact the root of the problem.
My transformer take much longer time to boot when plugged even with a full battery, and when it's empty it doesn't boot at all.
I must plug it, wait for it to be enough charged to boot unplugged, and do so. Then plug it back when started.
Considering that the transformer on stock cannot shut off when plugged to its keyboard (or even to USB ? Or is it just mine ? When I shut it off plugged to the keyboard then close it, it boot on again) When the tablet is left for several days unused the battery will be empty.
Sent from my Transformer using xda app-developers app
Yes I do. But even if the device is fully charged it will still not power on unless plugged in and I don't have the dock.
Sent from my Galaxy Nexus using xda app-developers app
Ok, sounds to be a totally different issue then, sorry
Sent from my Transformer using xda app-developers app
mled203 said:
Yes I do. But even if the device is fully charged it will still not power on unless plugged in and I don't have the dock.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Do the power and volume buttons work normally once fully booted? I have had similar issues, one was improperly seated power button, the other was a loose ribbon cable way down in the guts of this beast. Also, was this happening the whole time you've had it , or after a firmware update?
Right now I'm dealing with one that the screen won't stay on once I get into ics unless I'm plugged in. I went in and noticed that if the auto brightness wasn't set, it works. So I tweaked the settings in display time off when unplugged and uninstalled some screensaver app, and now it's working fine. It was probably the first thing, even though was already set to one minute. Anyway, just letting people know sometimes it isn't hardware. But the op probably is since he's done factory reset.
So I've been having some SERIOUS issues with my battery and have requested an RMA. Last night after a ton of issues (and at one where I soft-bricked pretty badly) I managed to unroot + load stock 4.2.2. It was late at night, so I decided I would re-lock the bootloader later.
Fastforward to today, I enable usb-debugging mode, plug in the phone and Windows 7 gives me an error. It says there's an issue. I go to device manager and it shows up with the yellow logo. I figure it's a driver issue so I uninstall drivers, and re-install naked drivers .72. Restart, plug it in and the same issue.
I go to a different computer and try it, same pop (this is Windows XP) saying device not recognized.
I also noticed my device no longer charges from the computer, when I plug it in it charges for a second, then stops.
How do I lock the bootloader if I cannot connect my Nexus 4 to the computer?? I tried going to bootloader and connecting the device, but nothing happens at all there. SOMEONE HELP!
EDIT: Here's the error message in Windows under the device manager: "windows has stopped this device because it has reported problems. (code 43)". Getting panicked now.
Search for BootUnlocker in the play store. Never tried it myself but by the reviews it seems to work. Good luck.
Edit: just saw that you have to be rooted. Sorry.
Sent from my Nexus 4 using xda premium
defnow said:
Search for BootUnlocker in the play store. Never tried it myself but by the reviews it seems to work. Good luck.
Edit: just saw that you have to be rooted. Sorry.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Yep saw that one too.
I'm pretty much stuck. There's literally nothing I can do except hope it somehow magically works later on...
Would Google accept the phone as under warranty if the bootloader is unlocked? The battery is SHOT, like it drains 1% every min while under use + like forever to charge. My hope is that the thing never boots when they get it so they can't actually see that it's unlocked.
Try using a different usb cord and I'm not sure if Google will accept it.
Sent from my Nexus 4 using xda premium
defnow said:
Try using a different usb cord and I'm not sure if Google will accept it.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Have already tried using 2 different cords. I'm going to try out another computer tomorrow that's brand new and see if it works there. Will also try charging fully but I don't see how that would affect it.
Still leaning towards them not being able to turn it on as a pass. That's the best possible case scenario for me.
I had same issue but try to update drivers of or PC
And install an app on or n4 called sdscan it will fix this issue
Sent from my Nexus 4 using xda app-developers app
illumanati22 said:
I had same issue but try to update drivers of or PC
And install an app on or n4 called sdscan it will fix this issue
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Tried it, doesn't work. Also, the issue isn't with the SD card since it mounts just fine on the phone itself. Issue comes up only when connected to a PC.
It doesn't even charge from the PC USB port.
Hi, I have a Nexus 4 and Nexus 7 (2013 edition) on Stock Android 4.4 Kit Kat and I've had a problem for a while now. The problem is that my phone and tablet reboot themselves and then works normally for 10 seconds to a minute when it boots up and it crashes and reboots itself, and it keeps doing that, over and over. It's a loop. It starts when my phone reboots on itself and on my Nexus 7 it will disconnect from my home Wifi and if you reboot the tablet, it does the same thing. This is my 5th time with this problem and I can't find out why it happens. This has happened to me since I've had Android 4.3. I have always fixed this by leaving both devices off a day or two and then It would work like normal. Then the problem would disappear for a few weeks and then the problem would repeat itself. This has happened to me on Paranoid Android on 4.3 but never on stock until now. I thought it was a problem on Paranoid Android but now I see it's a problem of my devices. I'm actually on Android 4.4 when I got this problem again. I actually left both devices off for 2 days and it still has the same problem. I don't think it's because of any apps because it actually crashed on me right after I did a factory reset to my phone on the setup screen. Can someone please help me?
Capture a logcat or kmsg
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Capture a logcat or kmsg
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
In the adb it says my device is offline. I have usb debugging on and allowed it the RSA key fingerprint. What should I do?
Do you have drivers installed (windows) or rules (Linux)? Has it ever worked before?
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Do you have drivers installed (windows) or rules (Linux)? Has it ever worked before?
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have the drivers installed. I actually always used the WugFresh Nexus Root Toolkit but it always worked
Try another computer or USB cable, also try to uninstall and reinstall drivers. Also best to stay away from toolkits
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Try another computer or USB cable, also try to uninstall and reinstall drivers. Also best to stay away from toolkits
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It actually just died on me. Both devices where having problems with Wifi and then my Nexus 4 reboots itself so I turned off both devices. What should I do!? I'm desperate right now! :crying:
Seems like a really strange issue, especially on two devices so it would be extra weird to call it a hardware defect so you can most likely rule this out.
Without logcats or last_kmsgs I would just be guessing but for now boot to bootloader on both devices and write down everything on these screens
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Seems like a really strange issue, especially on two devices so it would be extra weird to call it a hardware defect so you can most likely rule this out.
Without logcats or last_kmsgs I would just be guessing but for now boot to bootloader on both devices and write down everything on these screens
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I finally could get the logcat out of the Nexus 4 and 7 (2013)!
demkantor said:
Seems like a really strange issue, especially on two devices so it would be extra weird to call it a hardware defect so you can most likely rule this out.
Without logcats or last_kmsgs I would just be guessing but for now boot to bootloader on both devices and write down everything on these screens
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Can a bug report help? Now what happens is that when I try to connect my phone to my WIFI it will actually reboot and then it works normal.
There is lots to dig through in those logcats but the main errors are with your facebook app, these shouldnt cause a reboot
on wifi to the best of my knowledge but consider uninstalling that buggy poorly made app anyway
can you get me an output when it powers off, it sounds like you can replicate easy so do this:
cat /proc/last_kmsg
right after it auto reboots, the kernel log will be more helpful
and if you want to do another logcat
adb shell dmesg ; adb logcat -b system -b radio -b events -b main
will make things much easier to read
Ill dig some more when i get home, but for now try to at least get this kernel log immediately after reboot
demkantor said:
There is lots to dig through in those logcats but the main errors are with your facebook app, these shouldnt cause a reboot
on wifi to the best of my knowledge but consider uninstalling that buggy poorly made app anyway
can you get me an output when it powers off, it sounds like you can replicate easy so do this:
cat /proc/last_kmsg
right after it auto reboots, the kernel log will be more helpful
and if you want to do another logcat
adb shell dmesg ; adb logcat -b system -b radio -b events -b main
will make things much easier to read
Ill dig some more when i get home, but for now try to at least get this kernel log immediately after reboot
Click to expand...
Click to collapse
Well after that happened, I actually installed the factory image of KRT16S on both my devices and now they both of them work, except for this one time where I had to reboot my phone so it could connect with my home WIFI. The problem is that I know that this problem will happen in the future and I want to stop it. Could flashing it with JTAG solve this problem?
Without the logs I can't say that it will happen again or what the cause is, but I will say it shouldn't happen. I have a n4 and n7 as well and neither do this, nor any other android I've ever owned unless I'm running an unstable build or have malicious apps.
JTAG will be more than overkill, anything you could do with JTAG can be done through bootloader as of now. If you want I'll walk you through a complete wipe and restore of all firmware software
Sent from my Nexus 4 using Tapatalk 2
demkantor said:
Without the logs I can't say that it will happen again or what the cause is, but I will say it shouldn't happen. I have a n4 and n7 as well and neither do this, nor any other android I've ever owned unless I'm running an unstable build or have malicious apps.
JTAG will be more than overkill, anything you could do with JTAG can be done through bootloader as of now. If you want I'll walk you through a complete wipe and restore of all firmware software
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
As I said, my phone and tablet are working normal right now and I really don't want to mess with them but it would be of great help if I could contact you in the future when this problem repeats itself so I could get those logs and install everything correctly.
And when you say firmware software, you mean the factory image?
Not inherently, by firmware I mean mostly the bootloader and radio and by software the os, be it custom or otherwise
Yes if you run into issues down the road feel free to find me
Sent from my Nexus 4 using Tapatalk 2
demkantor said:
Not inherently, by firmware I mean mostly the bootloader and radio and by software the os, be it custom or otherwise
Yes if you run into issues down the road feel free to find me
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
And how would you wipe and restore of all firmware software?
wipe/format through fastboot and flash in fastboot
Just picked up a p600 and has been working fine on the CM 2.0 ROM. Today however i try to turn on and no matter which buttons nothing is happening. Only once I got it into the recovery and choose to boot system but again black screen. Have I a did and am I better off switching for snapdragon version?
Sent from my Nexus 5 using XDA Premium 4 mobile app
When you can enter download mode (von down+power) try to flash stock rom with odin.
Wont even turn on at all black screen
Sent from my Nexus 5 using XDA Premium 4 mobile app
Only once did it randomly go into trwp recovery but its seen like a fault not software issue. Hope I can get a replacement
Sent from my Nexus 5 using XDA Premium 4 mobile app
Its dead nothing happening with any button combos. Battery was 90%. Losing faith with Samsung had to get a replacement for a note 3 previously and have now switched to a nexus 5. May get a refund on this and wait on the nexus 10 2014 model
Sent from my Nexus 5 using XDA Premium 4 mobile app
My condolences mate maybe there is a way to reset it with ADB commands or something? Wait till you get another answer, I don't know too much about these things myself.
I tried unplugging battery for 15mins opened it very carefully. But no luck. I'm just really annoyed as I lost data and its rooted so swap is only option
Sent from my Nexus 5 using XDA Premium 4 mobile app
What I didn't understand is why you not re-flash a ROM via recovery or flash a stock ROM via Odin to see if this solve your problem. That will be one of my first steps.
PS. Other options are connect the device in the black-screen-mode and check via adb if you can see anything. Maybe an access to log cat is her possible and to get an output to see what goes wrong.
I've been having the same problem.. I just bought mine on Monday. It has either shutdown it self or just doesn't want to turn on, but I have to press the power button and +- volume buttons to turn it back on.. Now, I'm just waiting for it to do it again so I can return it...
Sent from my GT-N5110 using XDA Premium 4 mobile app
No response from PC at all via Odin and adb tried that its a fault
Sent from my Nexus 5 using XDA Premium 4 mobile app
There is something called usb jig that can fix these kind of issues. .google it
Sent from my SM-P600 using Tapatalk
It's all good got a new replacement was definitely dead but I agree possibly fixable just was covered under warranty
Sent from my SM-P600 using Tapatalk
Does any body knows why my phone wont push drivers to my computer? It just does it ones in a blue moon. Im on Icerom deodex, i think, because it was unlock which broke the usb drivers command.. i try different roms, port, and usb cable i event reset my computer and install lg divers but it will still not work. The computer doesn't even make a connection sound, and my phone say its charging.
Sent from my LG-LS980 using XDA Premium 4 mobile app
Tapp the charge icon in notification tray and select mtp or do it in settings
Sent from my LG-D802 using XDA Premium 4 mobile app
Did that it wont work... not even in download mode... or sideload.... i got lg and adb drivers is not my computer its my phone not pushing drivers...
Sent from my LG-LS980 using XDA Premium 4 mobile app
mine's been doing this for a month, :/
my buddy's also has this problem. He's on Malladus and I'm on GreenDevil's unofficial CM 11.
We're both on VS980
I've been using Airdroid to transfer ROMS to my phone. https://play.google.com/store/apps/details?id=com.sand.airdroid
I have several different drivers, on my Win 7 laptop and Win 8 desktop and nothing has worked. I've tried different cables too. it's also not recognized in ADB at all ever.
I would LOOVE an answer to this. I have no idea what is happening. It's baffling.
OK so I think not sure(something got burn cause I left my phone charging in recovery mode and I felt to sleep and when I woke up in was burning hot?) So I'm wondering if that was the problem ? I'm freaking out cause I'm paying for insurance and I don't wanna brick my phone and not fix it. At least lg tool was able to reset the root counter so I can return it for a new one but now I can't! Now what ?
Sent from my LG-LS980 using XDA Premium 4 mobile app