Last week I was minding my own business, doing usual stuff on my phone and the device spontaneously rebooted into a bootloop at the Google logo. So I think "OK, no problem... I can try wiping cache/dalvik or at worst I have a recent nandroid backup" and proceed to reboot into recovery... except that it still hangs on the Google logo. Stuck at work I did a bunch of googling and found one other user who had the same thing happen recently.
When I got home I tried to fastboot flash TWRP again... but alas was still stuck at the Google logo. Next was a full flash of Google stock images, but that did nothing either... so I relocked the bootloader and had my provider (TELUS) send it in for warranty repair. I just had it returned with the repair stating the main board was replaced.
I have noticed a few users posting about being stuck on the Google logo and this concerns me a bit, as it almost seems like there may be some inherent hardware flaw causing the issue.
So I'm throwing the questions out there: Has anyone else had similar problems and is this something we should start to be concerned with?
You're not alone buddy. I'm in the same boat. Have sent mine for repair yesterday.
Thats discouraging news. How long have you guys owned the phone? Did you buy it new?
I love my 6p but if enough of these units are defective they should probably be recalled. Hard to gauge if its an anomaly or a serious issue. Hope for the former...
I think I may have the same problem. My phone wont boot past the logo at all. IDK what to do at all.
I have the same problem, stuck on the google logo, I already wiped the cache partition and nothing, did a factory reset and nothing, what else can I do??
KLit75 said:
Thats discouraging news. How long have you guys owned the phone? Did you buy it new?
I love my 6p but if enough of these units are defective they should probably be recalled. Hard to gauge if its an anomaly or a serious issue. Hope for the former...
Click to expand...
Click to collapse
7 months...
Sent from my Nexus 4 using Tapatalk
---------- Post added at 09:51 AM ---------- Previous post was at 09:48 AM ----------
hgil said:
I have the same problem, stuck on the google logo, I already wiped the cache partition and nothing, did a factory reset and nothing, what else can I do??
Click to expand...
Click to collapse
Check if you can boot twrp. If you're not successful send the phone for repair. No option available to recover from this king of hard brick yet.
Weird thing is anything and everything is doable in fastboot. Moment you try to boot OS or recovery, gets stuck indefinitely in Google logo and reboot.
Sent from my Nexus 4 using Tapatalk
this exact thing literally just happened to me on Thursday. I was fully stock never unlocked the bootloader or anything. phone suddenly started looping, tried wiping cache, doing factory reset, finally went nuclear and unlocked the bootloader and flashed system images. nothing worked. warranty replacement is enroute.
I bought it on release day.
Old issue with Nexus devices. Has been going on since Nexus 5
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
I got the phone new from TELUS at the end of December, so about 6mo before I had the issue... Thankfully fastboot still worked so I could return to stock and relock the bootloader before warranty claim...
Starting to wish I had done the insurance option if these things are failing after 6mo and I'm on a 2yr contract
sunseb said:
I got the phone new from TELUS at the end of December, so about 6mo before I had the issue... Thankfully fastboot still worked so I could return to stock and relock the bootloader before warranty claim...
Starting to wish I had done the insurance option if these things are failing after 6mo and I'm on a 2yr contract
Click to expand...
Click to collapse
Did they give a new/refurb or was it they changed motherboard/memory chip?
Sent from my Nexus 4 using Tapatalk
Was my original exterior, the dings were still on the corners so it was just motherboard replacement
sunseb said:
Was my original exterior, the dings were still on the corners so it was just motherboard replacement
Click to expand...
Click to collapse
Thanks. Just was curious on what I could expect.
Sent from my Nexus 4 using Tapatalk
I'm also having this issue, but I get stuck at the boot animation instead.
I have Nexus 6P, Stock Android 6.0.1 July, SuperSu v2.74, franco kernel r23, Xposed v85. Everything was running fine when suddenly the phone rebooted and got stuck in boot. I reboot into recovery, deleted the /data/data/de.robv.android.xposed.installer/conf/modules.xml, flashed xposed unistaller zip, cleared cache and rebooted. Still stuck in boot. I reboot into bootloader, flash boot, system, vendor image of July factory image and reboot. Still get stuck at boot. This is happening for the third time to me. Happened in May, in June and now in July. Only thing that works is restoring a nandroid and then again flashing the latest factory image. But that way, I lose days / weeks of data, depending on when that last nandroid was created.
That really sucks, but doesn't sound like a hardware failure from my understanding... I lost ALL my data when I had to send it in, since my failure resulted in no access to the internal memory... Lost a few pictures which was a real bummer, but lesson learned and now I'll be backing up my memory more frequently and also setting up cloud backup for photos
bagarwa said:
I'm also having this issue, but I get stuck at the boot animation instead.
I have Nexus 6P, Stock Android 6.0.1 July, SuperSu v2.74, franco kernel r23, Xposed v85. Everything was running fine when suddenly the phone rebooted and got stuck in boot. I reboot into recovery, deleted the /data/data/de.robv.android.xposed.installer/conf/modules.xml, flashed xposed unistaller zip, cleared cache and rebooted. Still stuck in boot. I reboot into bootloader, flash boot, system, vendor image of July factory image and reboot. Still get stuck at boot. This is happening for the third time to me. Happened in May, in June and now in July. Only thing that works is restoring a nandroid and then again flashing the latest factory image. But that way, I lose days / weeks of data, depending on when that last nandroid was created.
Click to expand...
Click to collapse
It's likely a software failure. When you flash via fastboot, do you reboot back to bootloader after flashing radio and bootloader? If not then that's likely what's causing the fast boot method to fail for you. The first time after I did a complete fastboot flash of the software I fell asleep and woke up in the morning to my 6p still at the boot screen. When I re-traced my steps I found out that my mistake was not properly rebooting after flashing radio image, then doing another reboot after flashing bootloader.
Got my device back. Same exterior. Was told that motherboard was changed. I could notice that from fastboot.
eMMC changed from Samsung to Toshiba
DRAM changed from Hynix to Samsung.
My device joins this list. Gonna send it for repair tomorrow and hoping it is covered under warranty.
Additional update. I know I missed the bigger scheme that changed. My IMEI.
Just curious what happens if I restore my previous efs partition backup after backing up current.
Sent from my Nexus 6P using Tapatalk
update: My phone came back in 5 days. Mainboard failure. Replaced in Warranty!! New IMEI!!
Sent from my AO5510 using Tapatalk
sunseb said:
Last week I was minding my own business, doing usual stuff on my phone and the device spontaneously rebooted into a bootloop at the Google logo. So I think "OK, no problem... I can try wiping cache/dalvik or at worst I have a recent nandroid backup" and proceed to reboot into recovery... except that it still hangs on the Google logo. Stuck at work I did a bunch of googling and found one other user who had the same thing happen recently.
When I got home I tried to fastboot flash TWRP again... but alas was still stuck at the Google logo. Next was a full flash of Google stock images, but that did nothing either... so I relocked the bootloader and had my provider (TELUS) send it in for warranty repair. I just had it returned with the repair stating the main board was replaced.
I have noticed a few users posting about being stuck on the Google logo and this concerns me a bit, as it almost seems like there may be some inherent hardware flaw causing the issue.
So I'm throwing the questions out there: Has anyone else had similar problems and is this something we should start to be concerned with?
Click to expand...
Click to collapse
my phone randomly locked up, then rebooted today. But when it rebooted it was stuck with the white google logo flashing. I can get into the bootloader mode, but from there, choosing recovery or anything else gets back into the white google bootloop. I called service and they're sending me a replacement. Phone was stock with a locked bootloader.
Related
So, I have read a lot about TWRP sometimes bugging out and randomly encrypting phones and adding a password to which the user either never set it up or that TWRP doesn't accept it. This has recently happened to me and I cannot use my phone and I don't know what to do.
I have had the bootloader of my phone unlocked since day 1 when I bought my phone (release date last year) and have been running PA ever since. I have never had any problems with it, until about 5 days ago, when I grabbed my phone and everything started crashing and the camera was apparently not available. I didn't know what was the deal with it, so I rebooted the phone and it entered a bootloop (it hangs on the Google logo for about 5 minutes and then it hangs on the PA logo screen forever). I went on to the bootloader and started TWRP to see what was the deal. I originally wanted to grab certain files off the phone in case I had to do a system format, but when I got to TWRP, it asked me for a password which I have never set up and I tried every combination I could think of but it always failed. Everything was encrypted and without the password I couldn't get to it. I tried wiping everything including a factory reset before resorting to a system format (which I read about it and apparently is meant to be the solution). Everything failed because it couldn't access the /cache, /data, nothing. I went on to do a system format and although that is meant to wipe the phone and remove encryptions, it also failed to wipe the /cache and although TWRP says that the wipe is successful, the phone is still encrypted, the password is still around and it bootloops. I have tried the system format like 50 times and always the same.
Can anyone help me out with this? I am currently travelling around but am at a hostel where there is great internet and pcs, so I can install drivers, toolkits and such. I actually started looking around for new phones, since I cannot for the life of me get the phone to start again.
Note: The phone was working perfectly fine, I put it down to have dinner and once I finished, I tried to use it and it started to bug out. I also read around about this, and everyone's issue gets fixed after a system format.
Any help, would be greatly appreciated, that phone is the only net device I have on this trip and it sucks to not have any way to contact anyone.
Thanks.
Bump
Don't blame TWRP for something it doesn't do.
Looks like your device have an EMMC failure, sorry.
You can try installing factory image, or last resort restoring by download mode, but I think the flash memory in your phone is gone.
http://forum.xda-developers.com/showthread.php?t=2347060
sent from nexus 4
eksasol said:
Don't blame TWRP for something it doesn't do.
Looks like your device have an EMMC failure, sorry.
You can try installing factory image, or last resort restoring by download mode, but I think the flash memory in your phone is gone.
http://forum.xda-developers.com/showthread.php?t=2347060
sent from nexus 4
Click to expand...
Click to collapse
I didn't mean to blame TWRP. It is just that it was when I am on it that I get asked for the password and I was under the impression that it was TWRP that did the encrypting (I am in no way a developer or even very knowledgeable when it comes to the under the hood stuff, I usually only follow the tutorials). But thanks for the reply and the link, I will try that and hopefully get the phone back working.
Also, I did read in a thread that apparently this can occur due to hardware failure, I was just hoping this wasn't the case.
This happened to me on an old phone. Not sure why. Factory image fixed it. Could be a different issue but its worth a shot.
Sent from my Nexus 4 using XDA Premium 4 mobile app
It's happening to me now too
Sent using T-Mobile S4 4.3 MK2
LEGEND94 said:
It's happening to me now too
Sent using T-Mobile S4 4.3 MK2
Click to expand...
Click to collapse
Did it suddenly happen or did you change ROMs?
I tried a new rom for the first time and then went back to wicked 9.1, I'm thinking that triggered something.
I think I got a fix though, look here: http://forum.xda-developers.com/showthread.php?t=2588377
Sent using T-Mobile S4 4.3 MK2
Around a week ago everything was force closing on my N4 so I decided to reboot it, when I did it got stuck in boot loops. Because of this I went to wipe the data and cache so I could flash a Rom but when I did all my data from my SD partition had disappeared. This has happened to me before and the way I solved it last time was to unroot and flash back to stock using the Nexus 4 toolkit. However when I went to do that this time it said my boot loader was locked so I couldn't complete the task. So then I unlocked the bootloader which apparently is successful but when I refresh the bootloader it seems to be locked again. Over the last week I have tried sideloading zips, force flashing, unrooting, unlocking the bootloader and all this on both a mac and windows toolkit.
When researching this problem I only could find one thread which resembled my problem on xda however it was about the Nexus 7 and the person ended up sending it back to Asus. Would be great if someone good respond, thanks!
(Also my device is a Rooted UK 16gb if that helps)
It sounds like your emmc flash memory is bad. Not being able to lock or unlock the bootloader is a sign of that. You should warranty the device.
I agree. I faced a similar problem on my Optimus 2X. It started with occasional bootloops, and last week it got to the point where it was boot-looping after every boot w/ force closes, missing data, and e2fsck did nothing, because the fixed errors came back within hours. Definitely sounds like your memory chip has called it quits.
Hi guys,
So I had been using my Moto X Pure (3 months approx) and it had been perfectly fine. Except just a couple of days ago while I was on snapchat the phone suddenly shut down. While I tried to restart the phone it got stuck on the boot screen and didn't go past that. I initially tried to wipe cache partition & factory reset but nothing happened, it was still getting stuck on the boot screen.
My phone is unrooted and I haven't tried experimenting with the kernel or anything, mind you.
I left it alone for a couple of days and it started to boot up again, it was working perfectly, no issues whatsoever. But just yesterday the same situation occurred yet again :/ not while I was using snapchat but I unlocked the phone but the screen didn't turn on and it restarted by itself and got stuck onto boot screen again.
Is this an issue with the software or the hardware?
I talked to Motorola and they said they will issue a replacement phone, but I live overseas so it could be a hassle. Should I just send it in for replacement or try and reinstall the rom using factory image?
Thanks guys, really appreciate your help
could try reinstalling the factory image but if you havent messed with anything on the phone maybe its a hardware issue... i dont know
If the bootloader is still locked, i would definitely go through the replacement hassle. Should have no issues whatever after only 3 months and 100% stock.
DejektedZ76 said:
Hi guys,
So I had been using my Moto X Pure (3 months approx) and it had been perfectly fine. Except just a couple of days ago while I was on snapchat the phone suddenly shut down. While I tried to restart the phone it got stuck on the boot screen and didn't go past that. I initially tried to wipe cache partition & factory reset but nothing happened, it was still getting stuck on the boot screen.
My phone is unrooted and I haven't tried experimenting with the kernel or anything, mind you.
I left it alone for a couple of days and it started to boot up again, it was working perfectly, no issues whatsoever. But just yesterday the same situation occurred yet again :/ not while I was using snapchat but I unlocked the phone but the screen didn't turn on and it restarted by itself and got stuck onto boot screen again.
Is this an issue with the software or the hardware?
I talked to Motorola and they said they will issue a replacement phone, but I live overseas so it could be a hassle. Should I just send it in for replacement or try and reinstall the rom using factory image?
Thanks guys, really appreciate your help
Click to expand...
Click to collapse
Have you tried a simple factory reset? Basically a data wipe?
Sent from my One using XDA-Developers mobile app
bmeek said:
Have you tried a simple factory reset? Basically a data wipe?
Sent from my One using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes, tried a factory wipe and cleared cache but didn't seem to work.
DejektedZ76 said:
Yes, tried a factory wipe and cleared cache but didn't seem to work.
Click to expand...
Click to collapse
Yeah - I haven't heard of stock unrooted phones getting their system image corrupted such that a reset doesn't get back to proper "stock". Maybe a botched OTA, but if you've got that warranty option, probably be wise to take it.
I don't know this phone and Motorola well enough to say that unlocking your bootloader and starting from scratch, as I would be sorely tempted to do in your situation, won't void your warranty option.
Sent from my One using Tapatalk
Hi.
I've had numerous nexus phones and generally dont have many issues however randomly today my phone entered a bootloop. I decided to completely flash stock firmware (how i normally solve issues but no matter what I do it just continues to bootloop.
I can get into Fastboot but thats it.
Any ideas or experience of this anyone?
Thanks in advance
Gave up in the end, couldn't fix it.
google replacing under warranty
Just had to do the same thing last week. Using Uber Partner app and when I accepted a "call" phone crashed and began bootlooping. Tried fastbooting stock image but ended with "Phone is Corrupt" message and continuous boot loop before replacing under warranty. I was running August update Benzo ROM. Never experienced anything like this before and I've been flashing for 5 years now. Sorry about your device, the new one in the mail will make it all better best phone ever!
Oh god... I think my device is doing the same thing.... I've tried flashing stock through fastboot twice now. Still saying my device is corrupt. Even tried a different cable, and redownloading the firmware.
Stretlow said:
Gave up in the end, couldn't fix it.
google replacing under warranty
Click to expand...
Click to collapse
This happened to me too the same day out of nowhere. Google sent me a refurb. Battery in this replacement seems much better. I couldn't even get into the recovery.
Sent from my Nexus 6P using Tapatalk
My Nexus 6p just rebooted randomly, and it's stuck in a bootloop. I am on 6.0.1 (ignore the thread name, it's a typo), I did not upgrade to 7. I am rooted and bootloader unlocked. I can access recovery (TWRP). Can anyone help?
I just attempted to update to the latest build of 6.0.1 (since I had been putting it off) via fastboot, and that still didn't fix it. Still bootloops. Hoping to avoid a factory reset if possible.
Factory reset didn't help... Tried to format the data, didn't work.
Sadly it sounds like your 6P bit the dust. You can see if any of the posted possible solutions in this thread help, but...
https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528
Yeah, I don't know... I thought if I could boot to recovery, it would be easy to fix. But no matter how many times I wipe, factory reset, format, use adb to reinstall, it keeps bootlooping.
Yeah sounds like the boot loop of death. If you formatted data and fastbooted the factory image and still no go, that's pretty much that.
Great. I'm just over a month outside the warranty period and they want me to pay $160+ to get a replacement. And the replacement will have just a 90 day warranty, and if this issue occurs again, which is likely, I'll have to pay $160 again. Never getting Huawei again.