Would appreciate any advice, please.
My daughter's Nexus 7 Wifi (grouper/nakasi) is bootlooping.
[Yesterday, an app wouldn't install from Play Store (error code -24); went to go to Settings, to clear Play Store cache, but Settings wouldn't open. Rebooted, now it's bootlooping]
The device is still locked, so I'm obviously very limited in what I can do. Is there any way at all I can recover things, without having to do a wipe?
Failing that, I'd like to at least save her app data, and SD contents, before a wipe.
I've tried clearing /cache from (stock) Recovery, no change.
I can connect with adb, but only when in Recovery sideload. I can't connect with adb when it's bootlooping.
I can't flash a factory image, with wipe disabled, since it's still locked.
I tried to sideload an update, but the update fails, since they're all from->to, and it is already on the latest 4.4.2.
I tried mtpfs, but it won't mount.
Anything else I can try, please, before resorting to wiping, and losing all her app data and any pics she may have taken?
Since your N7's bootloader is locked and is on stock recovery, your hands are pretty much tied. I can't think of any solution then a unlocking and fastboot flashing a stock image.
But maybe someone with more knowledge comes by and can help you.
So, I did a wipe/reset from Recovery, which re-formatted /data & /cache.
And it still won't boot... I wonder what is wrong?
What is the recommended procedure now? Would that be to oem unlock then flash a factory image, and oem lock?
Just to follow-up - it was just less than 1 year old, so I rang Google, who did an RMA over the phone, and are sending me a replacement.
They no longer have stock of wifi-only, so are sending a 3G model. Not that I need that. I have heard that this model uses more battery even when there's no SIM in it. Hope not.
Can't fault the service.
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.
Good morning.
I was running 7.1.1 Dev 1 until yesterday afternoon.
The upgrade to Dev 2 popped up and I said no.
When I came back to my phone it was stuck in a boot loop.
I turned the device off and back on but it still was in a boot loop.
I decided to flash Stock NBD90X.
There was no issue with the flash.
The phone though is still in a boot loop and I am unsure where to go from here.
When I was running Dev 1 7.1.1 it was rooted and running Google assistant with the Pixel build prop. Could that be the issue?.
Any help gratefully received.
Matt
MATTHEWLONG said:
Good morning.
I was running 7.1.1 Dev 1 until yesterday afternoon.
The upgrade to Dev 2 popped up and I said no.
When I came back to my phone it was stuck in a boot loop.
I turned the device off and back on but it still was in a boot loop.
I decided to flash Stock NBD90X.
There was no issue with the flash.
The phone though is still in a boot loop and I am unsure where to go from here.
When I was running Dev 1 7.1.1 it was rooted and running Google assistant with the Pixel build prop. Could that be the issue?.
Any help gratefully received.
Matt
Click to expand...
Click to collapse
This has been an ongoing thing with the 6P and 5X, there are multiple threads on this bootlopop issue some recoverable, some not. Check this out see if it helps..
http://forum.xda-developers.com/android/help/guide-revive-angler-bootloop-t3454938/page5
Thanks for the support, I will take a look.
I've read too many threads about 7.1 and the beta program causing boot loops and bricks....this is ridiculous!
Do you have a nandroid on hand? If so, try restoring it and see if that works.
I have only boot looped twice with this phone. Each time I went into TWRP and did a full wipe (everything except internal storage). I completed the full wipe three times consecutively. After the third wipe I boot into fastboot and flash the latest stock images from Google. Reboot.
Let the phone sit for 10-15 minutes then boot back into fastboot to flash custom recovery (TWRP). Then boot into recovery to flash SuperSU. Reboot. Let phone sit for another fifteen before continuing with setup.
I know wiping the device three times probably doesn't do anything extra than wiping once before flashing but it's what I've always done and what's always worked for me.
Hi all, I ve updated my device to 7.1.2 beta via OTA the day before. Several hours ago, it started bootlooping after experiencing a battery drain.
Locked, out of warranty, cannot get into recovery mode.
I am giving up this device but does anyone know how can I restore my data from the phone?
Vince.L said:
Hi all, I ve updated my device to 7.1.2 beta via OTA the day before. Several hours ago, it started bootlooping after experiencing a battery drain.
Locked, out of warranty, cannot get into recovery mode.
I am giving up this device but does anyone know how can I restore my data from the phone?
Click to expand...
Click to collapse
If you are fully on stock and an OTA boot looped your phone I would contact Google and see if they will do anything to help you. Even out of warranty Google should accept responsibility for screwing up people's phones with their OTA. I had the same problem with the OTA but my bootloader was unlocked so I could flash a factory image and get my phone back. I was able to get to fastboot menu by playing with the power and volume keys for a while. If you can get to that menu you might be able to factory reset your phone or side load the Feb OTA. I don't think you can recover your phone data in the phone's current state.
if you have only access to Fastboot so you cannot backup any data unless somehow install recovery boot to recovery.
Geeks Empire said:
if you have only access to Fastboot so you cannot backup any data unless somehow install recovery boot to recovery.
Click to expand...
Click to collapse
Why are you spamming this forum? Please leave your personal advertisements out of your posts.
can't you sideload the ota file of a 7.1.1 rom? you should be able to access bootloader screen.
if it's not the bootloop of death that's been happening around here (included me) you can download an ota file from google factory image page and sideload it
jhs39 said:
If you are fully on stock and an OTA boot looped your phone I would contact Google and see if they will do anything to help you. Even out of warranty Google should accept responsibility for screwing up people's phones with their OTA. I had the same problem with the OTA but my bootloader was unlocked so I could flash a factory image and get my phone back. I was able to get to fastboot menu by playing with the power and volume keys for a while. If you can get to that menu you might be able to factory reset your phone or side load the Feb OTA. I don't think you can recover your phone data in the phone's current state.
Click to expand...
Click to collapse
Maybe i could donate to the websiteand we can get a thread up and runnig becuaseit took my over an hourto find a fix i havnt even tried yetin regards to the 71.1.1 bootloos onthe Goggle screen as well as the spash scrren, ihave sence lost the spalh screen now its juts black and white google
Some people have reported that the Skipsoft Toolkit got them out of a bootloop. I haven't tried it myself but I think you are giving up too easily. I've gotten lost of phones into boot loops but I don't panic because there is usually a way out. That isn't always the case with the 6P since there is the boot loop of death issue, but I still wouldn't give up just yet.
Hi Guys,
Hoping someone can help and tell me that Ive not bricked my brand new S7 edge
I have experience in rooting / flashing a number of android devices so I was quite confident in what I was doing.
So I was trying to root my stock rom, I flashed TWRP using Odin which worked fine then I flashed the Super SU. When I booted it then asked for a PIN to boot, it definitely wasn't what I set and would have only set it to 1 thing. So I did some googling and found that I could clear data or remove the pin key files but in TWRP it couldnt mount data and I tried re-formatting but it sat there for over half an hour and I had to hard reboot. TWRP now just freezes at the splash screen during boot which confuses me cause even if I switched off during re-formatting, I was only on the userdata so surely that shouldnt affect TWRP? I then got to the stage where I thought entering the max PIN attempts would just wipe data but no it tried to boot into TWRP which is useless cause it doesnt get past the splash screen.
I can still get into Odin mode, is there something else I can try flash? I had tried reflashing TWRP before but it was still freezing at the splash screen
I thought of maybe wiping data over adb but I dont think I can do that unless the phone boots or gets fully into TWRP?
Any help much appreciated.
Thanks
Stewart