My Nexus 4 was running stock android (ver. 5.1.1.) and was not rooted and had never been sent for any service repairs of any kind. After I had bought an OnePlus One, I gradually stopped using my Nexus and allowed it's battery to completely drain out. Now after a gap of a few months I tried booting up my Nexus ( after adequately charging it of course) but it just would not boot up despite repeatedly holding down the power button for long durations. The surprising thing was the phone was displaying the standard charging animation while connected via USB to a power source. I tried booting into the bootloader but the phone did not respond. By "not responding", I mean even the backlight did not come on . I think the fault may lie with the power button itself but am not sure. I have some imp data on the device so I absolutely need to access it.
Any help would be highly appreciated.
Thanks in advance.
Related
Hello,
I have been having a few odd issues with my Nexus 4, random reboots, no sound from speakers unless a reboot. Anyway Last night I had it on charge and it started rebooting itself in a loop so I managed to break the cycle and I ended up on a screen with a android on its side with a big arrow pointing at the power button, so I pressed the power button and it rebooted and was sat on the Nexus 4 logo.
I left the phone doing that and when I came back a while later the phone was still on the Nexus logo (which was still animating) but the phone was roasting hot, I turned the phone off by holding the power button.
Anyway, now the Nexus will not turn on, when it is plugged into a power source I get a red LED for a couple of seconds and then it goes out. In device manager I have qhsusb_dload in device manager.
I have done many hours of searching, I tried a few things suggested on other posts using Ubuntu but nothing.
This was a stock device that had only ever been updated with official updates. I can send it back no problem but I thought I would try save everyone's time and effort and see if there was anything I could try.
Thanks
qhsusb_dload stands for Qualcomm high speed download mode. Theres nothing you can do, other than a jtag. Sorry
Hacking noob here. As in never. Sorry if this is "yet another annoying noob" issue.
I just got an N7 today and I'm having boot issues. I was able to use the device initially, I got it setup and it charged to 100% earlier. Then I did my first shutdown in order to investigate the bootloader. Since then it has been difficult to get it to power on.
The device is brand new, stock, and nothing done to it, other than user setup, and USB Debugging has been enabled. And I haven't dropped it or gotten it wet or dusty or anything fail you might be thinking of. No crazy apps, not rooting ,etc.
Reading up, it sounds like I need to power off the device, then simultaneously press Vol Up, Vol Down and Power (for some amount of time) in order to get into the bootloader /recovery menu.
This does not happen. Nothing happens.
So I tried to power the device back on. It doesn't.
I plug in the USB cable and I don't see the charging icon appear.
I notice a possible discoloration near the usb port, which could simply be the spot where the notification led is, but there is a visible "spot" that can be seen there. Wondering if this is an indicated that something is fried?
After messing around with cables and random button pressing I have gotten it to boot a couple of times, and seen the charge icon a couple of times, but I'm starting to suspect that this device is effectively DOA. Its been charged sufficiently (>60%) ever since I got it.
1. Anyone have any advice on this? I have no plans to wipe the device, I wanted to actually investigate sideloading the OTA. Answer - Ignore this.
2. Am I missing something? Is there a different/specific order of operations to start it? Answer - Bobos will fail.
3. Does it matter if USB power is connected while trying any of this? I've tried 3 different sources. And none provide a consistent state. Answer - No.
4. Can anyone else confirm this "discoloration" is visible at this spot? (halfway between the bottom center and the display area) Answer - Its just the notification led.
UPDATE: Turns out that pressing all 3 buttons causes a portal to another planet to open over Manhattan. Do not do this.
Instead simply press Power + VolDown to get to the bootloader.
I expect you have a defective device. However, you might just be doing weird things with your buttons.
To get to the bootloader, you just need to hold down the power button and volume down button. You don't need to have the microUSB cord plugged in.
For simply booting up the system: there have been times when I've had to hold the power button down for a while in order to get the device to boot up.
Sent from my Nexus 6 using Tapatalk 4
You need to hold the power button down a few seconds to turn on.
Boot loader is Power+VolDown
The discoloration is the notification led.
Thanks for the replies! I was able to finally get into the bootloader menu by following xdhall's instructions. And from there, into Recovery. Since using this method I'm not having any power on issues. It may be a "bug" in how it registers button presses, because it definitely isn't acceptable to have my experience occur (no usb charge, etc)
On to trying to update to 4.4 via the OTA recovery method. Google can't stop me now.
Thanks to sfhub for speaking to the discoloration. I really wasn't sure if I saw it before this issue started. Better to panic and ask, then assume and fail.
Oh yeah, don't press down all 3 buttons for 10 seconds from power off, it does wierd things.
I have issues getting it to power on once in a while too. Have to leave it for a while or put it on charge for a while and then the power button works.
Sent from my Nexus 7 (2013)
I was just about to ask a similar question. Many thanks to zenrage for doing the work for me.
Sent from my SPH-L710 using XDA Premium 4 mobile app
BreakShadow said:
I have issues getting it to power on once in a while too. Have to leave it for a while or put it on charge for a while and then the power button works.
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
If you get the blinking LEDs, that is because the power is drained too low.
No blinking LED,just doesn't boot always at any battery level whatsoever. No issues with the buttons, they work fine when on. Untouched and locked system.
Sent from my Nexus 7 (2013)
BreakShadow said:
I have issues getting it to power on once in a while too. Have to leave it for a while or put it on charge for a while and then the power button works.
Click to expand...
Click to collapse
I had that too...returned it.
It was totally random...and would shut down by itself at random even though I charged it recently. I think it's an issue w/ the battery level sensor because to get it to boot, I'd have to plug it in for 15min, then power it up...
My old N7 2012 never had that quirk
I'm glad you were able to solve your problem with your nexus 7! I hope you enjoy it!
Sent from my Nexus 5 using xda app-developers app
My Nexus 7(2012) 16 gb appears dead. Was on CM11 with TWRP recovery.
Here's what happened :
I was using my N7, the screen froze for a second while scrolling on the browser.
After that a dead black line appeared permanently in the middle of the screen(horizontal).
I figured it might just be the case of dead pixels.
I continued using it like that only.
After a few weeks of usage, now the device won't power up at all.
When i connect to the wall charger, i just get a back light. No display. Nothing.
I tried booting into recovery, but nothing appears on the screen.
I kept it charging for few hours, but no luck.
It only flickers when connected to charger. Disconnecting the charger causes no activity what so ever on the device.
Nothing happens if i connect it to computer via usb.
Any solutions i can try?
Press & Hold the power button for at least 10 seconds while plugged into a power source. If no signs of life after completing the above step my first thought would be a faulty board..
Its just a black blank screen.
Sent from my GT-N7100 using XDA Free mobile app
Well, I would hate to be the bearer of bad news but it appears your device had a critical failure and is now dead... Obvious answer right? HaHa
RIP Nexus :crying:
You can always try and leave it to charger for a day and see if you get some life to your nexus. I had similiar thing with my nexus, I was actually booting new ROM and then it did some flickering and got blacked out. After connecting to charger nothing happened, just random flickering. I was able to recover and get it back in bussiness when I woke up next morning (it had been charging over night). This was almost a year ago and atm I'm writing this with the same particular device. So give it a shot again, you might still get it back to work. Also you could try to boot the device to fastboot mode by pressing power+volume buttons at the same time for a while. Good luck, let me know if you were able to get it boot&work again!
You could also try popping the back off and make sure the ribbon cables for the display are seated properly. While your there check the battery cable.
Hey guys, I signed up here because I'm desperate for help!
To cut a long story short, I upgraded my N7 (wifi 2012 model) from 4.4.4 to 5.1.1 which was an awful idea as performance was through the floor. So I used the ADB tools to flash and downgrade back to a stock 4.4.4 image from the google repository.
Unfortunately, after flashing I tries to get to the recovery mode (was on the boot loader) and it said "error", wouldn't let me go any further and just kept me in the boot loader menu. I rebooted the device thinking it might have just needed a gentle shove, but it didn't reboot...it turned off after using the power off command.
Now when I "try" to turn the device on I get a black screen and nothing else. To confirm, this isn't the usual battery related "black screen" with grey static and the enabled backlight caused by long term discharge. The screen is totally black, no matter what key combination I use there is no visual response. The only time I can generally see any sign of life is when It's plugged into my laptop - windows plays the "new device detected" chime, but ADB can't see it and about 90% of the time windows states there was a device error. At this present moment the device is powered on (again, no visual sign) just a chime and an active driver showing in devmgmr for "Android ADB Interface".
ADB - Any attempt to use ADB fails and shows "no device found / connected", I've tried multiple solutions such as the nexus root kit but they all have the same issue, they just can't talk to the device. I know it's not the laptop at fault because it was detected fine multiple times prior to flashing it?
There is something alive in the device in terms of powering it off and off as holding the power+vol down button does do enough to trigger the windows chime to indicate it's powered on, but windows can't do anything with it at all. Note the device was 95% charged during the flash so it's not like it crashed mid way.
Any help would be appreciated, it'd be a shame to bin it
Thanks
Lawrence
Take the back off and disconnect the battery. Press the power button to discharge any leftover charge. Plug back in the battery, then try powering up in bootloader mode.
Sent from my LGLS991 using Tapatalk
Hi Psiphi,
I did as you suggested, took the case off and disconnected the battery cable - pressed and held the power button in different combinations to make sure it discharges any remaining power.
Sadly, no change - any attempt to power it on results in the same lack of response
Anything else to try?
Thanks
You might try forcing a flash using the Nexus Root Toolkit, but otherwise I am out of ideas short of buying new hardware.
Sent from my LGLS991 using Tapatalk
I agree use nexus toolkit, use the force flash mode... I recovered mine about 6 months ago it was dead... Nothing worked...
Sent from my LG-H811 using Tapatalk
Essential PH-1 has continued to be my daily driver for almost 5 years now.
I haven't backed up the data, not even to GDrive. Yes, quite dumb. I finally found time to start to look into backing up recently, with the ADB route.
For the past 2 or 3 years, rebooting was problematic where it'd take 5+ minutes or required pressing the Power button down for a second buzz from off state, releasing it only when the animation with small circles would start. It'd then boot up to completion.
Recently, after fully charging and booting up from off state, it started showing new symptom where it'd be stuck indefinitely the Essential logo splash screen. At that time, I was still able to go into bootloader/recovery menu.
I rebooted and let it continue stuck on the Essential logo, hoping maybe it'd just take longer. After an hour, I forced it to shut down and rebooted again and put it aside to wait for it.
Within less than 2 hours, I noticed the display went blank/black.
After that, regardless of how long I press the Power button, the phone would never wake up anymore.
Plugging in the Essential OEM power adapter also does not even show the LED turning on. Can't tell if the USB port was busted or not but would be surprised if it did as charging and data transfer had always gone through a magnetic plug that's permanently plugged-in to the USB port.
Bootloader was never unlocked and, as such, also never attempted to gain root access to Android.
It was running the official Android 10 ROM from February 2020 (?).
There was no smoke or any unusual smell.
1. Is this a known/previously reported problem? I'd like to read on what others who experienced the same may have tried to resurrect.
2. If, let us say, the problem is actually with the battery, would the phone not show any signs of life when plugged-in to power adapter?
3. What are the chances some other electronics may either have slowly deteriorated or have gotten fried inside that casing?
4. If it's never powering back on, are there instructions on how to de-solder the internal storage component to try to recover the data?
5. What other possibilities can cause an Android device to not even show any signs of life?
6. Any other ideas?
Appreciate help from the community, including any pointers even if referring to a different Android device.