I'm pretty adept when it comes to adb/fastboot/flashing etc but I'm running out of ideas here.
Yesterday my phone rebooted twice on its own --- didn't think much of it (but probably should have in hindsight). Happened a third time and now all I get is the white "Google" splash screen with constant reboots.
Holding volume down does get me to bootloader --- however cannot get into recovery (same issue with google screen). Tried plugging phone into multiple PCs in bootloader mode but I get device cannot be recognized (usb device malfunction). Tried manually updating the driver - nothing.
All I want is to retrieve the photos/videos of my kids --- hoping there is some last resort that someone can suggest before I give up on this thing.
Ideas anyone?
UPDATE: Got phone to recognize via fastboot ---- still can't get to recovery. Anyway to get files?
Same happened to me, something is horribly wrong with the build(s) that came out this month as more and more people are having this exact issue. I was able to barely get mine to boot initially with the latest stock image, just long enough to upload all my pictures via Google Photos before it would freeze and go right back to the constant rebooting.
Eventually even trying a stock image stopped working, I RMA'd my phone.
This seems to be a ticking time bomb and is going to be a huge issue very soon. It's really going to be rough for anyone beyond their warranty period unless Google/Huawei steps up after they realize what's going on. I'm not even sure what I'm going to do with my phone once I get it back for fear of causing the issue again.
My bootloader is locked so I feel like I'm SOL here.... hoping for a miracle
Just got off the phone with Huawei tech support.... apparently its a known issue with no resolution currently. This is some bs
That's not gonna help you ATM but you should really always backup important stuffs. My important stuffs are also kid photo and they are backed up in my cloud AND in Google photos.
From bootloader screen, can you give us your device specs? Like emmc, date, sku,.. ?
NYYFan325 said:
Just got off the phone with Huawei tech support.... apparently its a known issue with no resolution currently. This is some bs
Click to expand...
Click to collapse
Wow really? Are you saying they wont allow you to RMA it? Are you still covered by the warranty?
Seanmiz said:
Wow really? Are you saying they wont allow you to RMA it? Are you still covered by the warranty?
Click to expand...
Click to collapse
Trying to find out now....
Is there anyway to reflash stock images with only being able to access fastboot and a locked bootloader?
NYYFan325 said:
Trying to find out now....
Is there anyway to reflash stock images with only being able to access fastboot and a locked bootloader?
Click to expand...
Click to collapse
I would grab the Nexus Root Toolkit (that's what I used for all of my resurrection attempts, makes it super easy)
http://www.wugfresh.com/nrt/
Use it to flash stock (and unlock the bootloader in the process) from Fastboot. Let it sit (and bootloop many times) afterwards as the popup suggests and see if you can get lucky with some access to your phone. Either way you can then relock your phone with the toolkit and you're ready to RMA.
The bootloader is not able to be unlocked since the setting was never checked within android itself. I let the phone sit trying to boot for a solid half hour or so just rebooting at the google logo. I think its just a brick at this point
NYYFan325 said:
The bootloader is not able to be unlocked since the setting was never checked within android itself. I let the phone sit trying to boot for a solid half hour or so just rebooting at the google logo. I think its just a brick at this point
Click to expand...
Click to collapse
I'm not sure what you mean, I could lock and unlock the bootloader at will, without anything but fastboot functionality.
Seanmiz said:
I'm not sure what you mean, I could lock and unlock the bootloader at will, without anything but fastboot functionality.
Click to expand...
Click to collapse
You probably had the box ticked in developer settings or had previously unlocked it.
I believe rootjunky posted a video on how to do it with bootloader being locked
Just got off the phone with tech support again.... phone is under warranty and they are going to send me a new one. Sucks about the pictures/videos but what can you do
Is it the recent updates that's the issue? I'm still on pure Nexus 7.0
Same happend to me and someone in another thread too.i think there is a big problem with the last build
Envoyé de mon HUAWEI VNS-L31 en utilisant Tapatalk
Wish I knew the cause.... as stated I was bone stock - locked bootloader and all (that's never going to happen again since I couldn't re-flash stock images because of this). Huawei was no help as to the cause other than to blame google.
NYYFan325 said:
Wish I knew the cause.... as stated I was bone stock - locked bootloader and all (that's never going to happen again since I couldn't re-flash stock images because of this). Huawei was no help as to the cause other than to blame google.
Click to expand...
Click to collapse
Well, to be fair, this issue seems to have just started popping up with a handful of us in the last week or two.
I'm sure they are in the process of trying to figure out what happened and why with the RMA units they have. Since we were all just fine prior to this month and suddenly had this happen on various 6P phones of different ages, I'm guessing some code that Google added lately can potentially corrupt the memory/storage in certain scenarios.
This is an escalating issue
ArN0V said:
Same happend to me and someone in another thread too.i think there is a big problem with the last build
Envoyé de mon HUAWEI VNS-L31 en utilisant Tapatalk
Click to expand...
Click to collapse
Have you requested RMA? The same happened to me too last monday night just browsing Chrome, but it isn't just the build people have in common but also the TWRP version 3.0.2-1, so everyone with their 6P still running, update your TWRP and change your ROM it sucks being a week without your phone besides losing all your files :crying:
GKti22 said:
Have you requested RMA? The same happened to me too last monday night, but it isn't just the build people have in common but also the TWRP version 3.0.2-1, so everyone with their 6P still running, update your TWRP and change your ROM it sucks being a week without your phone besides losing all your files :crying:
Click to expand...
Click to collapse
Yes i send it back to amazon.i'm waiting news from it
Related
Hi everybody, I enjoyed my stock N4 for almost a year and today several apps started to crash suddenly, after that the device rebooted itself and never got out of the bootloop. I immediatly booted into recovery and tried to wipe the cache memory and perform a factory reset but I cannot do either of the two, the error I get is something like "can't mount cache partition".
What should I do? How did this happen?!? I really need my phone back asap.
Thanks everybody!
Flash the stock images.
Chromium_ said:
Flash the stock images.
Click to expand...
Click to collapse
Ok I will but...How can this happen? A fully stock phone who never had a problem suddenly corrupts it's partitions?! (This is my understanding of the situation, correct me if I am wrong)
Thanks again for the link
Update: unlocking the bootloader works but when I reboot it appears to be locked again.
flashing the bootloader img file fails.
chikosneff said:
Update: unlocking the bootloader works but when I reboot it appears to be locked again.
flashing the bootloader img file fails.
Click to expand...
Click to collapse
sounds like your storage itself fails. thats the same issue that happens when the storage goes bad.
simms22 said:
sounds like your storage itself fails. thats the same issue that happens when the storage goes bad.
Click to expand...
Click to collapse
Thanks for helping, yes it looks like..so I can throw away my phone or there's something more I can try?
It feels so weird because it's one of the few phones I always kept stock, never fell, never had a single problem. Damn.
chikosneff said:
Thanks for helping, yes it looks like..so I can throw away my phone or there's something more I can try?
It feels so weird because it's one of the few phones I always kept stock, never fell, never had a single problem. Damn.
Click to expand...
Click to collapse
You could give this a try, but I really doubt it'll do much. I guess its worth a shot though.
chikosneff said:
Ok I will but...How can this happen? A fully stock phone who never had a problem suddenly corrupts it's partitions?! (This is my understanding of the situation, correct me if I am wrong)
Thanks again for the link
Click to expand...
Click to collapse
chikosneff said:
Update: unlocking the bootloader works but when I reboot it appears to be locked again.
flashing the bootloader img file fails.
Click to expand...
Click to collapse
Tried to Toolkit yet ? http://forum.xda-developers.com/showthread.php?t=1766475
Why did it happen? A phone is basically a mini computer, same as when you have to reload a computer OS sometimes,(failing hardware, bad app???)
Timboe73 said:
Tried to Toolkit yet ? http://forum.xda-developers.com/showthread.php?t=1766475
Why did it happen? A phone is basically a mini computer, same as when you have to reload a computer OS sometimes,(failing hardware, bad app???)
Click to expand...
Click to collapse
I'll give it a shot thanks, but I am afraid that the fastboot flash error is pretty clear :crying:
I get the phone being a computer, and I am totally ready to reload an OS...but I am not so ready to see the storage fails so suddenly leaving me with no phone, especially because this phone has received more care than any other phone I ever had..
Timboe73 said:
Tried to Toolkit yet ? http://forum.xda-developers.com/showthread.php?t=1766475
Click to expand...
Click to collapse
If its failing when he does it manually via fastboot commands, its very unlikely that using a toolkit will change anything. A toolkit simply runs the same fastboot commands behind a GUI.
Switched to windows to give the toolkit a try, then I will follow the unbrick procedure...I still cannot believe that this phone is lost without even having experienced the fun to mess it up with my own hands
chikosneff said:
Switched to windows to give the toolkit a try, then I will follow the unbrick procedure...I still cannot believe that this phone is lost without even having experienced the fun to mess it up with my own hands
Click to expand...
Click to collapse
As expected: toolkit not working. Since the bootloader " relocks" itself after rebooting the toolkit is unable to flash it afterwards.
Will try to contact google support but I am currently living in Europe I don't think it will be easy to get help.
Any other help is greatly appreciated. Thanks everybody.
1. if its within the warrenty period, this is something that would be covered.
2. its fixable. it can be professionally repaired, or you can try to do it yourself with the right parts.
but you will lose whatever you had in your storage, if you havent already.
another case reported :/
i think some batches of nexus 4 contains emmc brick bugs
just see this thread, more then 5 or 6 have been reported here.
http://forum.xda-developers.com/showthread.php?t=2259334
so after reading that thread i **** my self, because if this occured to my nexus i will have no warranty no google claims no nothing because i live in Pakistan.
So i ran emmc check app on my phone to check what it shows.
my emmc check shows i have "NO, Sane chip"
this means i am safe? if it give me "Yes, Insane chip" then i,m not safe according the my theory.
EMMC check app also shows the chip type, my chip type is "016g92"
googling this chip type i came across no specific results, one from S3 sudden death thread discussion. one person reports he have the 016g92 type and it is a safe chip according to other folks.
and one person having a galaxy s3 bricked his emmcs chip and claim the warranty. after the phone returns his chip type change to 016g92
http://smartphone.usofttech.com/t85915.html
so they change the emmc chip to 016g92.
can i surely assume that my nexus is safe from this serious hardware defect?
also any one here run the emmc chip and do give there chips type here, as i want to confirm if i,m safe or not. if not i,m going to sale my phone here. because the lose will be unbearable for me if the brick did occured
---------- Post added at 11:48 AM ---------- Previous post was at 11:37 AM ----------
simms22 said:
1. if its within the warrenty period, this is something that would be covered.
2. its fixable. it can be professionally repaired, or you can try to do it yourself with the right parts.
but you will lose whatever you had in your storage, if you havent already.
Click to expand...
Click to collapse
Dear Sir do advice me
simms22 said:
1. if its within the warrenty period, this is something that would be covered.
2. its fixable. it can be professionally repaired, or you can try to do it yourself with the right parts.
but you will lose whatever you had in your storage, if you havent already.
Click to expand...
Click to collapse
I still have 2 weeks of warranty left but I'll be in Europe till next year..I will try to ask the warranty service if I can send it in at my own expense.
Damn a worldwide warranty service doesn't look so useless now as it looked when I bought it :laugh:
PHONE BACK FROM THE DEAD!!!
So I got in touch with google's customer care to arrange the RMA and just to show them that my phone was impossible to recover I jumped ahead and told 'em: ok let's do a factory reset together so that I can show you what's the problem....
Fastboot>recovery>>data wipe....COMPLETED!
I cannot understand why did it work, I tried to wipe it at least ten times yesterday.
So now I have my N4 back working. What's your opinion on what happened? Do you feel like the problem is going to show up again soon? Is there anything I should do now that it's working? I just did a factory reset, not the cache wipe.
Just FYI: RMA from oversea is a pain in the ass, you have to ship the phone back to somebody in the U.S. and THEN ask for the RMA.
I wish I had your luck, mine did the same thing about 2 weeks ago. Couldn't get it to factory reset either. Mounting issue. My RMA came in yesterday. I'm enjoying the new phone though. It's even got the little nubs on the back. Mine original was a creaky 1st or 2nd batch one, I think. I will miss all the memories, pics, and data on my old one though.
SefEXE said:
I wish I had your luck, mine did the same thing about 2 weeks ago. Couldn't get it to factory reset either. Mounting issue. My RMA came in yesterday. I'm enjoying the new phone though. It's even got the little nubs on the back. Mine original was a creaky 1st or 2nd batch one, I think. I will miss all the memories, pics, and data on my old one though.
Click to expand...
Click to collapse
Since I feel this problem is hardware related I do not feel completely safe and I believe you were the lucky one getting the RMA
I had no choice, I should have sent the phone back to the US and then ask for the RMA...big pain in the ass
:fingers-crossed: let's hope this thing holds
Hi guys,
Right so I really need some help right now,
My nexus 6p is enrolled with the beta program but I am unsure which particular version of nougat it is on...
So I was sending a snapchat last night, and the phone randomly crashed and restarted. It then did it again when I attempted to do the same again. It kept on repeating do to this till the point where it wont boot anymore, it gets to the google logo and crashes or occasionally gets to the part of the boot with the shapes and crashes. So its stuck in some kind of bootloop?
So the phone is enrolled in the Beta, but I have not done anything else to it such as rooting etc.
This is a really stressful situation for me right now, my phone is essential for me right now, as a student from the UK studying abroad in Canada, I cant do any exchanges or afford to buy a new phone.
I was wondering if someone could help me fix this, I really dont know anything about Android when it comes to this kind of thing, and if possible I really don't want to void the warranty.
A guide on what to do would be really appreciated, keeping in mind Im not experienced in doing this kind of thing on androids.
Thanks,
Ben
Can you boot into the bootloader/fastboot mode?
benhawley2711 said:
Hi guys,
Right so I really need some help right now,
My nexus 6p is enrolled with the beta program but I am unsure which particular version of nougat it is on...
So I was sending a snapchat last night, and the phone randomly crashed and restarted. It then did it again when I attempted to do the same again. It kept on repeating do to this till the point where it wont boot anymore, it gets to the google logo and crashes or occasionally gets to the part of the boot with the shapes and crashes. So its stuck in some kind of bootloop?
So the phone is enrolled in the Beta, but I have not done anything else to it such as rooting etc.
This is a really stressful situation for me right now, my phone is essential for me right now, as a student from the UK studying abroad in Canada, I cant do any exchanges or afford to buy a new phone.
I was wondering if someone could help me fix this, I really dont know anything about Android when it comes to this kind of thing, and if possible I really don't want to void the warranty.
A guide on what to do would be really appreciated, keeping in mind Im not experienced in doing this kind of thing on androids.
Thanks,
Ben
Click to expand...
Click to collapse
i have the same issue, i have tried using toolkits and even using fastboot commands and the phone just keeps getting stuck on the google logo screen. at this point i think i might have to get a replacement. unless some can offer a solution
Same issue
I have exactly the same issue. I am on Angler 7.1.1 Beta/NPF10C. Since the OTA came out everything was fine, until yesterday while trying to send a picture on Hangouts the phone froze and rebooted, and rebooted and rebooted. The bootloader is locked and no USB debugging enabled. So far I tried:
- wipe data/factory reset through recovery - first try, the phone reset and let me set it up, but then froze after 5 minutes and kept rebooting; after that any factory reset just get's stuck at Google logo at boot
- tried to adb sideload rescue OTA - previous build NBD90X starts verification and fails at 50% with the error: can't flash older over newer (duh!); and the ota build npf10c can't be read. I tried on Mac and Windows. No matter what I do adb can't read zip file. Also tried updated sdk tools and everything, no luck.
Read on Google forums that there is a chance of hardware issue and the phone must be returned for exchange if still under warranty.
Update: I was able to sideload rescue OTA on Linux, but the phone is still in bootloop. Only showing Google logo and reboots. I'll wait till next DP2 comes out and I will try to sideload it and see if it fixes the issue.
redduc900 said:
Can you boot into the bootloader/fastboot mode?
Click to expand...
Click to collapse
Yes I can, any suggestions as to what I can do?(sorry im a noob, but the bootloader is the power button and volume down menus right? haha)
Is there any way I can get my data off the phone?
.
So I followed these instructions for the rescue OTA (I cant post the links because im new to the site)
You can find it by going to the google help forums
Well I Got to Step 9 and it didnt work and it says a warranty or repair is the only recourse.
Is there no other way of fixing this? As I said before, a warranty replacement is not possible for me as I'm in the wrong country
benhawley2711 said:
Yes I can, any suggestions as to what I can do?(sorry im a noob, but the bootloader is the power button and volume down menus right? haha)
Is there any way I can get my data off the phone?
Click to expand...
Click to collapse
I don't think there is a way, since the phone is encrypted, boot-loader locked and oem unlocking is disabled. I think that is the whole purpose of having device secured, so none can get files from your phone.
---------- Post added at 01:29 AM ---------- Previous post was at 01:26 AM ----------
benhawley2711 said:
So I followed these instructions for the rescue OTA (I cant post the links because im new to the site)
You can find it by going to the google help forums
Well I Got to Step 9 and it didnt work and it says a warranty or repair is the only recourse.
Is there no other way of fixing this? As I said before, a warranty replacement is not possible for me as I'm in the wrong country
Click to expand...
Click to collapse
Looks like your recovery is bad and that is when warranty suppose to be used. However, even if there is warranty, Huawei website states that they won't cover improper testing of the devices, which I think falls under beta testing category.
denys2000 said:
I don't think there is a way, since the phone is encrypted, boot-loader locked and oem unlocking is disabled. I think that is the whole purpose of having device secured, so none can get files from your phone.
---------- Post added at 01:29 AM ---------- Previous post was at 01:26 AM ----------
Looks like your recovery is bad and that is when warranty suppose to be used. However, even if there is warranty, Huawei website states that they won't cover improper testing of the devices, which I think falls under beta testing category.
Click to expand...
Click to collapse
At this point, I'm not too bothered about my data, because all my photos have backed up to google photos.
Should I just attempt a factory restore? I know someone above said their phone just froze after 5 mins, but I suppose I could try and unenroll from the beta in that time and hopefully take me back to a stable release without the bug.
- I'm not sure if that will work though :/
benhawley2711 said:
At this point, I'm not too bothered about my data, because all my photos have backed up to google photos.
Should I just attempt a factory restore? I know someone above said their phone just froze after 5 mins, but I suppose I could try and unenroll from the beta in that time and hopefully take me back to a stable release without the bug.
- I'm not sure if that will work though :/
Click to expand...
Click to collapse
If you have no worries about losing data then you should try a factory reset, after all it might help. IMO you should definitely unenroll from beta at this point.
denys2000 said:
If you have no worries about losing data then you should try a factory reset, after all it might help. IMO you should definitely unenroll from beta at this point.
Click to expand...
Click to collapse
Yeah, so it wont let me go into recovery mode just bootloops, safe to say its pretty f***ed.
Suppose trying to claim warranty is all I can do, but can't do that for two months.
At this point, I'm gonna have to admit defeat and buy a new phone until I can claim the warranty back in the UK when I return.
benhawley2711 said:
Yeah, so it wont let me go into recovery mode just bootloops, safe to say its pretty f***ed.
Suppose trying to claim warranty is all I can do, but can't do that for two months.
At this point, I'm gonna have to admit defeat and buy a new phone until I can claim the warranty back in the UK when I return.
Click to expand...
Click to collapse
Good luck with the warranty. Unfortunately, mine has ended and I am currently using my girlfriend's old iphone 5s with a tiny tiny tiny screen
I used adb and sidecar and all the stuff mentioned by others. it says 100% and i rebooted my device and still google logo occuring and its not fixed. Any other option that i can try now?
[Guide] Fool/Noob proof way to do clean installs on Nexus Devices
http://forum.xda-developers.com/nexu...talls-t3518311
try this clean install should work
KKPGAME said:
I used adb and sidecar and all the stuff mentioned by others. it says 100% and i rebooted my device and still google logo occuring and its not fixed. Any other option that i can try now?
Click to expand...
Click to collapse
use these commands in bootloader.
adb shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
adb shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
I need help, my phone went into a Bootloop. I have tried to flash the factory image (7.0 and 6.0.1) using NRT and manually and still does not pass the Google logo. It does not let me enter the recovery, it only restarts continuously. When flashing the factory image did not give me any error, even the computer detects it in fastboot mode.
All this happened when I was about to open an application and suddenly I shut down and began to restart continuously. I had using android 7.0 stock.
Exact thing happened to me and I flashed both 7 and 6.0.1 and wiped data and caches multiple times.. nothing seems to work.. any ideas?
Tried everything but still bootloops.
Same thing here, although I was on a 7.1 build. There must be a flaw that can cause this to happen in recent build(s), I was trying to share a picture and it froze and bricked like this suddenly. I tried every combination of formatting and flashing stock images and whatnot but no luck.
Seanmiz said:
Same thing here, although I was on a 7.1 build. There must be a flaw that can cause this to happen in recent build(s), I was trying to share a picture and it froze and bricked like this suddenly. I tried every combination of formatting and flashing stock images and whatnot but no luck.
Click to expand...
Click to collapse
Your Nexus 6P uses Samsung eMMC doesn't?
I've seen countless threads here and on reddit about this.
My phone hard bricked last week and I suspect the Samsung emmc is to blame, too many people are having the exact same issue without a solution in sight. I am absolutely unable to access the recovery or anything on the emmc for that matter.
See if you're still covered under warranty (mine was 5 days past its warranty, and Google refused to help), otherwise you're SOL. I think we need to make some noise about it and have AP or another site pick up on this.
darksmartz said:
Your Nexus 6P uses Samsung eMMC doesn't?
Click to expand...
Click to collapse
I believe it was Samsung, yes. I RMA'd it right away after exhausting all flashing efforts.
darksmartz said:
Your Nexus 6P uses Samsung eMMC doesn't?
Click to expand...
Click to collapse
How do I know if my 6p uses Samsung eMMC? What is this, btw?
Edit
Nevermind. I just figured out. Mine is Toshiba, btw.
Rafsxd said:
How do I know if my 6p uses Samsung eMMC? What is this, btw?
Edit
Nevermind. I just figured out. Mine is Toshiba, btw.
Click to expand...
Click to collapse
how did you find this out ? would be nice to tell people so they can check to find out if they will be at risk
brichardson1991 said:
how did you find this out ? would be nice to tell people so they can check to find out if they will be at risk
Click to expand...
Click to collapse
You can find this information on the Bootloader screen listed under eMMC about halfway down the list.
Same problem, samsung memory here
Same for me too,i send my phone back to amazon
Envoyé de mon HUAWEI VNS-L31 en utilisant Tapatalk
Mine uses a Toshiba eMMC and bootloops nevertheless. Not sure if this is actually what's causing it. At this point my only thought is that there was a bad batch of devices as so far no one could find a pattern on what exactly causes the bootloops.
seco2004 said:
Mine uses a Toshiba eMMC and bootloops nevertheless. Not sure if this is actually what's causing it. At this point my only thought is that there was a bad batch of devices as so far no one could find a pattern on what exactly causes the bootloops.
Click to expand...
Click to collapse
Yeah, it doesn't actually seem to be related to eMMC brand. It was very strange, because after it happened, I was able to flash 7.0 stock and regain OS use on a very touchy level. I couldn't access USB connectivity, the home button didn't work most of the time, and if I tried to do too much with it, it would go right back into infinite bootloops. After accomplishing this 2 or 3 times, I could never again get back into the OS.
I could wipe and flash all of the partitions with no errors, I could always get into stock recovery, but TWRP never worked.
Was anyone *not* on the November patch level of v7.0+?
Seanmiz said:
Yeah, it doesn't actually seem to be related to eMMC brand. It was very strange, because after it happened, I was able to flash 7.0 stock and regain OS use on a very touchy level. I couldn't access USB connectivity, the home button didn't work most of the time, and if I tried to do too much with it, it would go right back into infinite bootloops. After accomplishing this 2 or 3 times, I could never again get back into the OS.
I could wipe and flash all of the partitions with no errors, I could always get into stock recovery, but TWRP never worked.
Was anyone *not* on the November patch level of v7.0+?
Click to expand...
Click to collapse
When this first started for me I was on the latest beta build, October security patch.
Same issue here - 64MB Samsung memory.
Google support are aware of the issue, they sent out a replacement no questions asked. For some reason, the guy suggested (but he said unofficially) tapping on the power button. Anybody have any clue why this would be relevant?
Regardless, I'm in a position where I can access fastboot, but nothing else. Can anyone think of any data recovery options at this point?
---------- Post added at 12:26 PM ---------- Previous post was at 12:20 PM ----------
To follow up on my previous post - just before I hit a reboot that threw me into the bootloop, I encountered a hard freeze. I received a bug report after the hard freeze and this is now sitting in my gmail drafts. Would this bug report have any pertinent information here?
thisisgil said:
For some reason, the guy suggested (but he said unofficially) tapping on the power button. Anybody have any clue why this would be relevant?
Click to expand...
Click to collapse
I know exactly why it's relevant!
He's trying to make sure it's not a shoddy power button. My Galaxy SII back in the day had a common power button failure where it would think that you are just constantly hitting/holding the power button if you even breathed on it. My phone would bootloop or suddenly reboot constantly because it was getting power button commands from the poor quality button. Better quality buttons along with other methods of locking/unlocking the phone to reduce power presses have mostly prevented this sort of thing these days.
Since I got my Nexus 6P sometimes it could just hang and then restart, I thought this was nothing major so I did nothing about it. Today however, I got a couple of these restarts in one day and after the last one I can't boot. The unlocked bootloader message appears, then the Google logo and after that it keeps looping. I can get into bootloader, however when I try anything there (boot into recovery, BP tools or "factory") it just starts looping again. I have tried restoring nexus 6p system images with Google's "flash-all" bat file, and with Heisenberg's method on 2 different android versions and it goes through without problem, however I'm still stuck in a bootloop.
Any help would be appreciated.
Thanks.
Try flashing all of the factory image files manually. If it still fails to boot, contact Google / Huawei for an RMA.
RoyJ said:
Try flashing all of the factory image files manually. If it still fails to boot, contact Google / Huawei for an RMA.
Click to expand...
Click to collapse
I've been through 5 so far. I'll give them a call tomorrow morning and see how it goes. Hopefully the warranty still covers me. I've done some digging around, and what is happening to me is the exact same thing as what is happening to some people through the OTA nougat update, with the only solution being exactly what you said.
I just really hope I can actually get a replacement as I have done nothing wrong on my side, it seems to be purely Huawei's fault. Thanks anyway.
Called them this morning. The person on the phone said that because the phone was rooted, it would need out of warranty repairs (which is ridiculous as this exact issue happens to people that were never rooted and didn't even unlock the bootloader, who can get a replacement for free). I'll see how it goes.
domdomrys said:
Called them this morning. The person on the phone said that because the phone was rooted, it would need out of warranty repairs (which is ridiculous as this exact issue happens to people that were never rooted and didn't even unlock the bootloader, who can get a replacement for free). I'll see how it goes.
Click to expand...
Click to collapse
How did they saw if your phone was rooted? Did you told them?
GKti22 said:
How did they saw if your phone was rooted? Did you told them?
Click to expand...
Click to collapse
The guy at Huawei didn't really know what the warranty covers. I mentioned trying to restore from Google's factory images (implying that I unlocked the bootloader) and he said that this might have voided the warranty (which I'm pretty sure it hasn't) as it is a software modification in a sense, but he's not entirely sure. They're going to send me a box to send the phone to them, and through that they'll be able to tell that no modifications have happened I hope (it's technically all stock and unrooted now, it just doesn't boot up). If they do try and charge me, I'll call the actual repairs team (as they're not available today) and explain the situation. No way am I paying for something like this as it hasn't happened through my own fault.
Under Europe regulations THEY have to formally prove the software modifications lead to the hardware fault (if that's a hardware fault) and that would be really bad publicity for Huawei. Not sure how UK applies that to its local right.
Root may very well void the warranty based on an old thread on XDA here that's buried in the general section somewhere, but an unlocked bootloader absolutely will not void the warranty.
Hi, can someone please upload the build.prop for nexus 6p 7.1 dev preview, I did some changes and now stuck in boot loop, also the backed up copy that I have has previous version names and all according to 7.0 , I am stuck in twrp and don't have computer then how is it possible to make changes directly from twrp terminal, I tried "vi build.prop" and was able to see build.prop but couldn't edit, Thanks
Here you go https://paste.debian.net/897221
For anyone wondering, I got the phone the other day and they fixed it under warranty. No extra costs or anything (I enclosed a letter giving proof as to why I believe it should still be under warranty, and it worked fine). The serial number and IMEI has changed, so it leads me to think that it was indeed a motherboard failure. Thanks for the help!
1 hour ago, I was checking Facebook, and a moment later, my phone started to restart... After a few moments, I realized that my phone was in bootloop. I tried booting into recovery, but It started a bootloop again. Flashed TWRP, nothing happens, still bootloop. Flashed vendor, system, boot, cache, recovery, radio, bootloader from lastest factory image. I have very important data on my phone, so the last thing I want to do is to do a factory reset. But I still hope that I can somehow get the userdata partition from bootloader or somehow make it boot. Can you help me? The only thing I can open right now is bootloader.
I'm having an exactly the same problem with you.
The only difference is that I didn't use Facebook.
I dared to lose my every data so I formatted userdata partition of my phone and flashed stock image, but it didn't fix mine.
I failed at figuring out the solution yet, but there's still one hope.
When I contacted with huawei, they said there's an upcoming update, and it will fix bricked phones.
I don't know if it will work, but considering you had your bootloader unlocked and can access it, and you have some important datas that you don't wanna lose, I recommend you keep your phone until the update gets released, then manually flash it without wiping your user data.
Given our phone's symptom is exactly the same and you tried similar methods I've tried, this is the best way I think you can try.
Good luck. You're in the same boat with me.
frostydawn said:
I'm having an exactly the same problem with you.
The only difference is that I didn't use Facebook.
I dared to lose my every data so I formatted every partition of my phone and flashed stock image, but it didn't fix mine.
I failed at figuring out the solution yet, but there's still one hope.
When I contacted with huawei, they said there's an upcoming update, and it will fix bricked phones.
I don't know if it will work, but considering you had your bootloader unlocked and can access it, and you have some important datas that you don't wanna lose, I recommend you keep your phone until the update gets released, then manually flash it without wiping your user data.
Given our phone's symptom is exactly the same and you tried similar methods I've tried, this is the best way I think you can try.
Good luck. You're in the same boat with me.
Click to expand...
Click to collapse
Yes, but we can wait for this update for months.. Also, when you flash a factory image, you lose you data (correct me if I'm wrong). So, it doesn't matter to me, if I try to format user data, or wait for the update. Hm...
fftorettol said:
Yes, but we can wait for this update for months.. Also, when you flash a factory image, you lose you data (correct me if I'm wrong). So, it doesn't matter to me, if I try to format user data, or wait for the update. Hm...
Click to expand...
Click to collapse
Well, android 7.1.2 beta for nexus 5x, pixel, or etc was released a few days ago, and for nexus 6p, it'll be released soon.
This is just my imagination, but maybe they're taking some times fixing boot loop so the release for 6p is getting late.
Also, you can flash factory images without user data lose by manually flashing it using fastboot commands.
The released image will contain some .img files, then you can extract it and then only flash required files without formatting userdata partition.
Don't use flash-all.bat, and use fastboot commands to selectively install image files except for userdata.
frostydawn said:
Well, android 7.1.2 beta for nexus 5x, pixel, or etc has been released a few days ago, and for nexus 6p, it'll be released soon.
This is just my imagination, but maybe they're taking some times fixing boot loop so the release for 6p is getting late.
Also, you can flash factory images without user data lose by manually flashing it using fastboot commands.
The released image will contain some .img files, then you can extract it and then only flash required files without formatting userdata partition.
Don't use flash-all.bat, and use fastboot commands to selectively install image files except for userdata.
Click to expand...
Click to collapse
Right! I've just got an idea to try older factory image versions for Nexus 6P... Mabye I get it working . I will let you now
I'm on the same boat as both of you guys. I tried installing TWRP but it continues to bootloop.
I have some important data I didn't get a chance to backup. and would not want to send it back/factory reformat.
Here's my thread:
https://forum.xda-developers.com/nexus-6p/help/nexus-6p-bootloop-to-recover-files-t3551455
Please keep us updated.
stillwind said:
I'm on the same boat as both of you guys. I tried installing TWRP but it continues to bootloop.
I have some important data I didn't get a chance to backup. and would not want to send it back/factory reformat.
Here's my thread:
https://forum.xda-developers.com/nexus-6p/help/nexus-6p-bootloop-to-recover-files-t3551455
Please keep us updated.
Click to expand...
Click to collapse
frostydawn said:
Well, android 7.1.2 beta for nexus 5x, pixel, or etc was released a few days ago, and for nexus 6p, it'll be released soon.
This is just my imagination, but maybe they're taking some times fixing boot loop so the release for 6p is getting late.
Also, you can flash factory images without user data lose by manually flashing it using fastboot commands.
The released image will contain some .img files, then you can extract it and then only flash required files without formatting userdata partition.
Don't use flash-all.bat, and use fastboot commands to selectively install image files except for userdata.
Click to expand...
Click to collapse
Guys, did you manage to fix it? I was doing some research, talking to some persons, and they said that it is probably a hardware problem. So, I went to the nearest Huawai servis, and they told me, that if the problem is really on hardware, it will cost me around 340€ (363 dollars) to replace motherboard... I can't afford that much... Its is almost a price of a new phone. I hope you came up with some better solutions.
fftorettol said:
Guys, did you manage to fix it? I was doing some research, talking to some persons, and they said that it is probably a hardware problem. So, I went to the nearest Huawai servis, and they told me, that if the problem is really on hardware, it will cost me around 340€ (363 dollars) to replace motherboard... I can't afford that much... Its is almost a price of a new phone. I hope you came up with some better solutions.
Click to expand...
Click to collapse
For now, I failed.
New 7.1.1 minor build update didn't fix my phone.
And google said they can't assure there will be update that will fix my phone.
I'm waiting for 7.1.2 beta, and if that doesn't work, well.. I don't know.
Maybe I should await 7.1.2 official, or.. just give up everything.
My hope is getting faded, and yeah.. for now, I can do nothing but wait for update.
Actually, I don't think those updates will work.
I'm just giving it a last chance, since repair service at here also costs about 350$, and if I fail, I should keep using Nexus 5.
Ah... It didn't took 2 weeks for my phone to be bricked after I bought this phone.
I really want to get this phone back, but the hope is too faint.
frostydawn said:
For now, I failed.
New 7.1.1 minor build update didn't fix my phone.
And google said they can't assure there will be update that will fix my phone.
I'm waiting for 7.1.2 beta, and if that doesn't work, well.. I don't know.
Maybe I should await 7.1.2 official, or.. just give up everything.
My hope is getting faded, and yeah.. for now, I can do nothing but wait for update.
Actually, I don't think those updates will work.
I'm just giving it a last chance, since repair service at here also costs about 350$, and if I fail, I should keep using Nexus 5.
Ah... It didn't took 2 weeks after I bought this phone.
I really want to get this phone back, but the hope is too faint.
Click to expand...
Click to collapse
Exactly... I was thinking... What if we lock the bootloader and send the phone to repair service with warranty papers... Do you think that can actually work out? Can they see that the phone was rooted, if we lock the bootloader with ADB Shell?
fftorettol said:
Exactly... I was thinking... What if we lock the bootloader and send the phone to repair service with warranty papers... Do you think that can actually work out? Can they see that the phone was rooted, if we lock the bootloader with ADB Shell?
Click to expand...
Click to collapse
I live in South Korea and in my country, they provide repair by post service for devices in the warranty period.
For me, my warranty is expired, so I had to bring it to the service center myself.
I've locked the bootloader and brought it the center.
They didn't check if it was ever unlocked or rooted.
The engineer only tried rebooting my phone several times, and said he should replace the motherboard. And they said they couldn't fix it for free because the warranty is expired.
I don't know how Huawei in your country will handle it, but I think if you flash the stock image and lock your phone, maybe they won't see that was ever rooted.
But I also don't know if they will provide free repair.
No luck on my end. I tried everything... I've been flashing and repairing problems like these since the nexus one but I'm totally stumped. Lucky/Unlucky for me I've only had the device for 3 months so I have an RMA ready since it is under warranty.
Most importantly tho is that I want to recover the files on the device which will not happen if I take it to the repair center as they reflash all the devices before proceeding to fix it.
I tried getting TWRP but the device reboots back into the boot as soon as I select recovery.
Also tried flashing everything but user data using flashboot and the nexus 6 .img files but still in the same situation.
I just wished they would've at least added a microsd option so I could at least have some of my files back...
I don't think I will ever get a phone without microsd option again or root and unlock bootloader on every device I get. This was the first phone I decided not to mess around with since everyone kept telling me to enjoy the stock experience....
Worse experience to date with android.
Well I gave up trying to fix it by software, and found another solution.
My warranty is expired, so it wasn't cost-efficient to bring my phone to official service center.
Now I bought a display-broken phone at about 60 dollars.
Gonna bring it to an engineer and replace my phone's motherboard with its intact one.
frostydawn said:
Now I bought a display-broken phone at about 60 dollars.
Click to expand...
Click to collapse
That's a great price. Is it the H1512 (International) and where did you purchase? Haenguneul bileoyo.
v12xke said:
That's a great price. Is it the H1512 (International) and where did you purchase? Haenguneul bileoyo.
Click to expand...
Click to collapse
It seems like you're Korean like me.
I bought it from Naver Cafe Google Reference Nexus Forum's market.
And yeah. It's H1512.
No, i'm not Korean but I spent a couple of years working in Okpo and Ulsan on several projects. There is a guy from KL in another thread looking for an H1512 motherboard. I'll pass your info on to him. Thanks.
v12xke said:
No, i'm not Korean but I spent a couple of years working in Okpo and Ulsan on several projects. There is a guy from KL in another thread looking for an H1512 motherboard. I'll pass your info on to him. Thanks.
Click to expand...
Click to collapse
Well, then tell him this too.
Naver Cafe 'Joonggonara'
This is one of the largest market for used stuffs.
frostydawn said:
Well, then tell him this too.
Naver Cafe 'Joonggonara'
This is one of the largest market for used stuffs.
Click to expand...
Click to collapse
Link Product
VN_Optimus said:
Link Product
Click to expand...
Click to collapse
It was a one-off purchase of a broken phone on a Korean market equivalent of Craigslist. You'll have to dig around and find one locally... and be lucky, too.
I just had reboots today for the first lasting about 20 minutes. I was able to get into Recovery and clear the cache and then shut down the phone. Upon restart it looped a few times and then fully booted (thankfully). I have placed the latest firmware in the phone in the hope that if this happens again I can flash the firmware and access the phone.
I hope this helps a bit.
I am rooted and running N2G47H.
Doc
DocEsq said:
I just had reboots today for the first lasting about 20 minutes. I was able to get into Recovery and clear the cache and then shut down the phone. Upon restart it looped a few times and then fully booted (thankfully). I have placed the latest firmware in the phone in the hope that if this happens again I can flash the firmware and access the phone.
I hope this helps a bit.
I am rooted and running N2G47H.
Doc
Click to expand...
Click to collapse
Hopefully it will but realistically this could be the beginning of the end for your phone given the 6P history with the boot loop of death. Presumably your phone is out of warranty?