My nexus is hard bricked after a usual reboot. There is no reaction on power button or power button + vol. down. I have the latest update (Oreo 8.1). The bootloader hasn't been unlocked. The only one reaction is a Qualcomm HS-USB QDLoader 9008 (COM3) when I plug in the phone to my windows PC.
So is there any option to reanimate the phone?
Possibly the battery is completely done. My friend at work was telling me how his 6p's shut off completely and a new battery brought back to life. However unless your gonna change the battery yourself is it worth the risk of investing $100 your call.
Nexus 6P bootloader locked
I would like to share my experience on how I saved my Nexus 6P which was bootlooping with bootloader locked and inaccessible recovery mode.
The problem started when I had updated my phone with latest OTA update 8.1.0 (Oreo). While I was browsing fb after the update, suddenly the phone froze and restarted. And ever since that moment it begun to bootloop. I tried to access recovery from Fastboot so that I can clear the cache which would most of the time resolve the bootloop issue however this time around I was unable to go to the recovery mode too. I wouldn't been able to flash from fastboot since bootloader was locked. There is no way to get around this unless I would be able to load the OS and go into Developer option to turn on "Enable OEM unlock" in the settings.
Since I would not be able to flash the stock ROM or get into recovery mode, I contacted Google support for help. They directed me to Huawei Support. Huawei told that since my phone is out of 1 year warranty they would not be able to service this phone and would cost me nearly $400 for getting me a replacement. Spending $400 for 20 months old phone was absurd.
I started to explore online what are the options available given the tight situation that I was into. I came across few forums discussing about using a heat gun above the finger print sensor to throttle the CPU which may stop the phone from bootlooping. I used a hair dryer to heat the phone while the phone is continuously bootlooping. I would heat for about 7 - 10 mins to an extent where I would not be able to hold the phone anymore. After nearly 7 to 8 failed attempts spread over 2 weeks, the magic worked.
The last attempt was slightly different. Here is what I did -
1. Battery was fully drained
2. I started to charge the phone while I kept it outside my window for about 20 mins. Temp outside was around 15 degrees Fahrenheit. (Did this step since I read somewhere that keeping the phone in refrigerator and restarting would resolve bootloop issue) However it continued to bootloop.
3. While the phone continued to bootloop, I allowed the phone to charge overnight.
4. Next day I saw that the phone did not restart like how it used to. It was stuck at GOOGLE and would not restart.
5. I disconnected from the charger. Went to fastboot and switched off the phone.
6. I started to heat the phone using hair dryer with the phone switched off for about 10 mins. I held it was a cloth since it gets hot pretty fast.
7. Paused for a sec, turned on the phone (it was bootlooping) and continued to heat the phone for another 5 mins. (by then I gave up)
8. Stopped heating. I left the phone and went out to work on something else. After half an hour, when i returned I saw that the phone was completely switched off and was not bootlooping. I got excited since I know that the phone was fully charged overnight and there is no way that the phone would have died due to battery drain.
9. I immediately turned on by holding on to the VOL down button. I selected recovery from fastboot. To my surprise for the first time in 2 weeks I was able to go into recovery mode. I cleared cache and restarted the phone in Normal mode.
10. Phone booted properly and loaded the OS.
11. First thing I did was to go into developer options and turn on "ENABLE OEM UNLOCK" option. (By now I knew how important it was to have this enabled. THIS COULD SAVE YOUR $549 PHONE!!)
12. Took a backup of all the files and unlocked the bootloader.
I downgraded the OS to 7.1.2 (Aug release) which I felt was a stable one for Nexus 6P. I also did a h/w check and all the tests passed CPU / Memory is fine. I am still not sure what could have caused the bootloop but the fact that it happened after the Oreo OTA would make me to stay away from upgrading the Android version beyond 7.1.2.
Thanks,
Prasad
Exodusche said:
Possibly the battery is completely done. My friend at work was telling me how his 6p's shut off completely and a new battery brought back to life. However unless your gonna change the battery yourself is it worth the risk of investing $100 your call.
Click to expand...
Click to collapse
Actually I've already replaced the battery by myself and of course it wasn't original. But after this the phone has been working for 6 months correctly. Moreover, it seems that the battery isn't completely dead.
I could try change the battery once again but how it could cause hard brick?
@Speed1908 thanks for your replay, but it is not my case.
Related
Ok so I was running paranoid android 3.99 and I've been getting the OTA notices that I need to update. I did that just today, and it downloaded the update and apparently installed it. Then I was stuck in recovery (reboot just kept sending it back to recovery). So I did some googling, decided I should not have tried to OTA and decided I should try to go back to stock and properly flash the rom.
This was my first attempt going back to stock. I downloaded what I thought was the correct nakasi file for my 2012 Nexus 7 (Wifi only, grouper I believe). I got adb and fastboot installed and started sending the prompts. It appears 'fastboot flash bootloader bootloader-grouper-4.23.img" worked properly, but when I tried "fastboot -w update image-nakasi-jwr66v.zip" I got an error and the tablet just kept rebooting into recovery; it would not load past the "Google" screen.
So I put the tablet down (with 98% charge), took my kid to baseball practice and came back an hour later to work on it. The tablet had turned off. Now it appears dead. It does not show a charge symbol when plugged in, and will not power on with "power" or "power and down button." As a result, adb/fastboot does not recognize it.
I thought I had soft bricked it, but now I'm scared I might have hard bricked it. It looks like maybe I installed the wrong nakasi file (the one I installed ended in "v," but the one I just saw from Google ends in "y").
I will try letting it charge overnight and seeing if it will boot in the morning. In the meantime, any ideas, or should I just consider this brick a sign that I should upgrade to the new Nexus (and be more careful)?
Where did you get the stock image? All the official one can be downloaded from here: https://developers.google.com/android/nexus/images#nakasi
If you can boot into bootloader, you can flash the proper image with fastboot, of not, then your device is hardbricked.
If you are worried about a flat battery then you can check it with a voltmeter the voltage should be between 3.6 and 3.7 if the tablet won't charge the battery you could manually charge it THIS IS DANGEROUS the n7 regulates the voltage and current to the battery but if you uses 500mA charger and tape the wires onto the battery and only give it about 30 mins you should be ok . Check the temp of the battery as you do this if it starts to get hot unplug wait for it to cool and go again.
Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
Thanks for responding. I charged it overnight, to no avail. I don't think it was hard-bricked, but probably is now that it shutdown and won't recharge or boot.
I unfortunately did not get the file from this site or google, as I should have. I got it from another site I have used before, which was linked to a youtube video on how to return to stock. I thought I followed it exactly, but maybe not.
there is one final thing I'm thinking. when I plug it in to my computer, I am getting the "ding-dong" sound like it's connected. Still, adb/fastboot don't appear to be picking it up. Anything i can do to get it recognized?
It doesn't sound good try plugging it in and holding in the power button for one minute use your watch it can take anything over 30 second's that works on a fully functioning n7 with a completely flat battery to get it to charge not sure if it will work on yours. A bricked device should have the same characteristics as a brick if your computer detects something well a brick can't do that otherwise back to my suggestion of manual charging
Sent from my C5303 using xda app-developers app
You may be in what is called APX mode. Sounds like you might have overwritten the bootloader with the wrong image, which usually means bad news, especially if you can't get into fast-boot mode to write over the image.
Unless it's still under warranty, you can't do much. I had this same problem when I attempted to upgrade to Kit Kat. Not sure what happened, but my tablet was hosed and it only shows up as an APX device. Luckily, it was still under warranty and I was able to RMA it with Asus and they replaced the motherboard free of charge. My purchase date happened to be 11 months prior, so I had about a month left on my warranty. Got lucky.
Try what is suggested in this post: http://forum.xda-developers.com/showpost.php?p=30002160&postcount=10
It might help, it might not. Some have reported trying for a few hours eventually helped get it out of APX mode, but I tried it with mine for days, and nothing helped.
--- This may belong in the Xposed forum, I am uncertain. ---
Hello. Please forgive my ignorance regarding the technical aspects of methods discussed on these forums.
I have a Samsung Galaxy S4 GT-I9505 supplied by Vodafone Australia. This was received today as a replacement for a screen issue I had with my previous S4. On the previous S4, I had rooted using a Saferoot method as read about on this forum. Later I had installed Xposed to use Keepchat and everything was fine. Today I have rooted this replacement phone successfully using the same method, and then moved to install Xposed. The Xposed application required an update, the very first option in the app was red and suggested an update or a reboot, and the reboot did nothing, so I pressed update. The phone turned off but didn't restart. I tried the usual button presses and battery pulls and finally a simple power up using the standard power button started the phone up. It got as far as the lock screen I believe, before shutting down again. It is now unresponsive. It wont turn on, enter the boot menu (multi button holding method) or charge. I believe the battery is quite low at this point, and unable to charge, causing me some consternation. It has now been over 30 minutes with no response.
If anyone could provide a resolution to this issue, I would be extremely thankful.
Regards,
CaleS
Try and ask in this forum my friend good luck
http://forum.xda-developers.com/showthread.php?t=2265477
Hello again.
I have an update on my situation.
I left the phone on charge and it eventually turned on by itself. I played around with it for a while and it seemed OK. Eventually it turned off again. I had to pull the battery to get it to turn back on. After starting up again, getting to the lockscreen, it turned off again. This process repeated many times, until I got frustrated.
The next day I thought I'd try a factory reset via volume up + power, and the device managed to stay on long enough for this to complete. After the phone reset, I used it for a while and again it turned off. The same cycle continued.
Perhaps the phone is naturally faulty, despite my rooting attempt, as it was a refurbished model. I am quite happy to return it for another replacement under warranty, however I may not be able to do it as the device is rooted. I would gladly remove the root using stock firmware and Odin, however the phone resets after a few seconds of entering download mode.
Any advice?
Thanks.
Sounds to me you have a faulty power button. It's somehow stuck that's why it even reboots in download mode. It's a common problem for the S4. Try to wedge it or replace it.
if it is refurbished model it might as well be dead battery.
battery sensor detects "low battery" state and shutdown phone saying battery 0% - to protect battery against fully depleted state (damaging to max capacity or even impossible to charge at some point)
if you power it on again it will boot and say it has like 1% left and you will be able to use it for few more moments, but doing so will degrade your battery.
powering it on, going to lock screen for it to shutdown on its own again sounds like weak power source
imagine above scenario happening several times (previous owner of the phone kept "reviving" it after shutdown due to battery 0%)
that would resulted in battery able to hold only fraction of its standard power - allowing you to just boot your phone before it shuts down.
I had similar situation with my laptop battery (this one was on AC all the time) - battery was so damaged that laptop was shutting down at windows login screen - if booted on battery alone.
When booted on AC and unplugged it said 100% battery, that went down to 0% in a matter of around 2 minutes, when laptop shuts down.
TLDR: are there any diagnostics I can do to verify that my battery needs to be replaced?
A few days ago, I turned on my phone to check the time and a half-second later it suddenly and instantly shutdown. I was not able to restart it at all. When I got home and plugged it in, it began a continuous boot loop, with only the motorola splash screen displaying, then nothing for a few seconds, then back to the splash screen over and over.
Fortunately, I was able to get to the"AP Fastboot Flash Mode" menu. I couldn't do anything from there on the phone itself though; every option just went into the boot loop again. I was able to get a fastboot connection with my PC and so reflashed the phone successfully.
After reflashing, it went into the boot loop again. I began looking for more solutions online and wasn't paying attention, but sometime in the next 5-10 minutes it made it to the login screen! I re-set up my phone and all seemed to be working fine!
Until the next day. I tapped an app and instead of opening, the phone immediately shutdown and went dead again. Took it home, plugged in, and it went into the boot loop again.
Anyway, I've read a few threads on here and elsewhere that the culprit may be the battery. I would like to have more than just a hunch before I shell out the money and time to replace the battery -- is there any way I can verify that the battery is indeed the problem? I didn't seem to be having any battery problems before - charging and usage seemed fine. I did drop the phone rather hard a few weeks ago, but didn't seem to effect anything (short term at least).
Also, could using a non-Droid Turbo 2 charger affect battery life? I actually got the phone used and didn't get the official charger with it, so I've been using just a random leftover one for ~6 months.
TIA!
walter77d said:
TLDR: are there any diagnostics I can do to verify that my battery needs to be replaced?
A few days ago, I turned on my phone to check the time and a half-second later it suddenly and instantly shutdown. I was not able to restart it at all. When I got home and plugged it in, it began a continuous boot loop, with only the motorola splash screen displaying, then nothing for a few seconds, then back to the splash screen over and over.
Fortunately, I was able to get to the"AP Fastboot Flash Mode" menu. I couldn't do anything from there on the phone itself though; every option just went into the boot loop again. I was able to get a fastboot connection with my PC and so reflashed the phone successfully.
After reflashing, it went into the boot loop again. I began looking for more solutions online and wasn't paying attention, but sometime in the next 5-10 minutes it made it to the login screen! I re-set up my phone and all seemed to be working fine!
Until the next day. I tapped an app and instead of opening, the phone immediately shutdown and went dead again. Took it home, plugged in, and it went into the boot loop again.
Anyway, I've read a few threads on here and elsewhere that the culprit may be the battery. I would like to have more than just a hunch before I shell out the money and time to replace the battery -- is there any way I can verify that the battery is indeed the problem? I didn't seem to be having any battery problems before - charging and usage seemed fine. I did drop the phone rather hard a few weeks ago, but didn't seem to effect anything (short term at least).
Also, could using a non-Droid Turbo 2 charger affect battery life? I actually got the phone used and didn't get the official charger with it, so I've been using just a random leftover one for ~6 months.
TIA!
Click to expand...
Click to collapse
Try the apps such as Ampere which shows battery info.
I don't think so Non-Turbo charger can lead to affect the battery life but using a cheap charger does.
Stock .21 firmware. Never tried any other ROMs. Battery went down to 1% last night, charged it on stock charger to 30% then moved it to a different charger. An hour after that I got a call, I hanged up and about 1 hour later I heard the phone buzzing every 30 sec or so, I looked at it and realized it's in bootloop. If I press Vol- and Power I can get it in fastboot and with Vol+ and Power in Recovery. Can't figure out what to do from there though.
Update: Pressed -+ and left it the whole day in that mode. Came home, and it booted up and looked fine for about 3 minutes then it shut down by itself. It seems to me that there's some sort of memory/storage corruption. Any suggestions on how to proceed from here?
Phone booted normally and I was able to use it for about 12 hours. I was doing a Whatsapp backup this morning when it shut down and got into the bootloop again.
nwaves said:
Phone booted normally and I was able to use it for about 12 hours. I was doing a Whatsapp backup this morning when it shut down and got into the bootloop again.
Click to expand...
Click to collapse
If you are using stock, immediately get rid of your usb c cable and buy a new one. There could be an issue with the cable that is causing problems with your battery.
Try to keep the charge percentage between 20% and 80%
Finally, your battery stats may be off. To resolve a battery stats issue you will need to reset the phone. Which again, if you are using stock and have never used a custom rom. You should definitely do a factory reset.
Same issue on 2 different chargers with 2 different cables that used to work well until now. None of the cables are stock. One of the chargers is stock, the other one aftermarket. My wife's S3 doesn't have any issues using the same cables and chargers. Issue seems to be happening when battery is full or almost full. Phone gets into a soft reset bootloop. I let it drain yesterday and was able to get in and do a factory reset. I then added my account and left it installing and updating apps overnight, while connected to the charger. Woke up with the phone off and after pressing power for 12 sec it got into the bootloop again. As you can imagine, it's impossible to keep the battery under 80%. Would it help if I try a custom rom? Maybe a new battery? I'm open to any suggestions as I really like this phone and can't find anything similar at a reasonable price.
So phone still reboots when battery is high. I can however get into Fastboot Mode and Tool All-In-One detects it. Tried to unlock the bootloader in the tool but it failed. I'm willing to try anything to get the phone back up and running but not sure where to start. Would really appreciate some guidance.
It really sounds like the battery is bad. You can buy a new battery for $8 .
If you replace the battery : Do NOT use a hairdryer to remove the screen. You will need a heat gun, they cost 7 dollars at harbor freight.
With a heat gun the lcd screen will practically fall off into your gloved hand.
I was going to offer to connect remotely and help with unlocking the bootloader and installing TWRP, Root and a Rom. But I sincerely believe that you need to get a new battery first.
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.