Database Users

Most ridiculous issue ever - please advise.

Okay so - recently my I9000m went into a boot loop (during normal use - though I did have voodoo installed) and I can not access recovery mode. I could however access download mode.
I attempted to install stock firmware from samfirmware - no luck.
I attempted to install stock firmware from the forums - no luck.
I attempted to install EZBase - no luck.
I even attempted to use Virniks 'stock everything' tutorial - no luck.
After all these attempt and various other attempts involving 3 button fixes I was still having boot-loops.
So I got desperate - and I installed the Odin One Click for captivate - I know...bad idea but like I said.. I was desperate.
Now my i9000m (bell canada) starts up with the AT&T Logo and then boot loops!
The worst part is I can't even access download mode anymore! I understand that this is probably due to the fact that the buttons are remapped - keeping that in mind I tried as many key combos as I could but still get nothing but the AT&T Logo looping over and over.
So to the point.. does anyone have a surefire way to get to captivate download mode on a I9000M?
I've read about the JIG solution but I'll use that as a last resort as I would have to order the pieces (I'm not much of a solderer).
So are there any non-JIG solutions to get back to download mode/restore my phone?
All input is appreciated and I'd like to thank everyone that has tried to help me these last couple of days!

Sounds like your internal SD card is dead.
I was having similar issues where the phone would just bootloop. I re-flashed 4-5 different stock roms which all did the same thing. One of the stock roms allowed me into recovery mode, which yielded no success only a no sd card message.
I have gone ahead and sent my phone out to Bell for repair.

Viper717 said:
Sounds like your internal SD card is dead.
I was having similar issues where the phone would just bootloop. I re-flashed 4-5 different stock roms which all did the same thing. One of the stock roms allowed me into recovery mode, which yielded no success only a no sd card message.
I have gone ahead and sent my phone out to Bell for repair.
Click to expand...
Click to collapse
I'm thinking of doing the same (bringing it to bell) though I'm not sure they'll honor the warranty with it booting up with the AT&T logo, hah :<

Yeah i dont think they would service that, i was fortunate enough to get back a stock i9000m rom so it still boot up with that.
You can try contacting samsung directly to see if they will be able to repair for you, or try the jig and re-flash to stock bell rom

Viper717 said:
Yeah i dont think they would service that, i was fortunate enough to get back a stock i9000m rom so it still boot up with that.
You can try contacting samsung directly to see if they will be able to repair for you, or try the jig and re-flash to stock bell rom
Click to expand...
Click to collapse
Called samsung last night - they said I have to bring it to bell first.
Worst case scenario I'll pay sammy to fix it =/
Update: Just got off the phone with Bell, described my problem, said that I messed with the software real hard and they said that as long as I didn't remove any warranty stickers I'll still be able to get it fixed by samsung foh freeee.

Viper717 said:
Sounds like your internal SD card is dead.
I was having similar issues where the phone would just bootloop. I re-flashed 4-5 different stock roms which all did the same thing. One of the stock roms allowed me into recovery mode, which yielded no success only a no sd card message.
I have gone ahead and sent my phone out to Bell for repair.
Click to expand...
Click to collapse
I have urgued him to flash any SGS firmware with recovery image, but he didn't listen.
And yes, I think that his internal storage bus is dead.
If so, he should write down IMEI of his phone, and send email to the Samsung Korea with the info, that his internal SD card is dead. They will send him brand new phone.
But in the case he would rather use warranty service of his provider, he will need to:
a) try reboot with adb, and fastest as he can, try to issue "reboot download" command with it
OR
b) make JIG, and reboot to download mode, and reflash stock ROM
Asking Samsung Korea for new phone with IMEI sent to them do not require any of above...
EDIT: I have missed your last reply. Good to know, that Bell will fix it for you. But I do not think that they will be able to fix it. They will more likely give you new phone.

Virnik0 said:
I have urgued him to flash any SGS firmware with recovery image, but he didn't listen.
And yes, I think that his internal storage bus is dead.
If so, he should write down IMEI of his phone, and send email to the Samsung Korea with the info, that his internal SD card is dead. They will send him brand new phone.
Click to expand...
Click to collapse
I did listen - no matter how many times I tried to flash the sgs firmware w/ recovery image it would just keep booting and wouldn't enable the functionality.
As i detailed above I tried several recommended methods to re-enable the recovery mode and none of them worked.
Thanks for your help - hopefully Bell honors what they said on the phone.

Sozage said:
I did listen - no matter how many times I tried to flash the sgs firmware w/ recovery image it would just keep booting and wouldn't enable the functionality.
As i detailed above I tried several recommended methods to re-enable the recovery mode and none of them worked.
Thanks for your help - hopefully Bell honors what they said on the phone.
Click to expand...
Click to collapse
OK. Just do not panic :-D
You will get your phone back, more likely new one.
And on other hand, this result is not your fault. Some "first-line" SGS phone models has been faulty. You are not the first one with such problem.

Virnik0 said:
OK. Just do not panic :-D
You will get your phone back, more likely new one.
And on other hand, this result is not your fault. Some "first-line" SGS phone models has been faulty. You are not the first one with such problem.
Click to expand...
Click to collapse
They said they would send it to Samsung and give me a loaner until mine is back.
Not sure if they'll still honor it when I show up in person...but I'm hoping for the best.

So to give a final update:
After a couple commutes back and forth to the Bell store and a couple phone calls to Samsung it looks like I voided the warranty and I'm SOL on getting this phone repaired.
The (semi)bright side of the story is that I have an insurance policy with Bell and I'm getting a brand new SGS for $150.

Sozage said:
So to give a final update:
After a couple commutes back and forth to the Bell store and a couple phone calls to Samsung it looks like I voided the warranty and I'm SOL on getting this phone repaired.
The (semi)bright side of the story is that I have an insurance policy with Bell and I'm getting a brand new SGS for $150.
Click to expand...
Click to collapse
Little too much for a few hours of your time. If you'd reflashed stock ROM and ignored vibrant fw, as I've suggested, they would have no chance to find out what happened, and you've been given new phone for free. But you were in a hurry. Besides, your second, but in the circumstances of your haste not important misstake was, that you've told them what you have done.
Sent from my GT-I9000 using XDA Premium App

Virnik0 said:
Little too much for a few hours of your time. If you'd reflashed stock ROM and ignored vibrant fw, as I've suggested, they would have no chance to find out what happened, and you've been given new phone for free. But you were in a hurry. Besides, your second, but in the circumstances of your haste not important misstake was, that you've told them what you have done.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Exactly what I thought...you gave them extremely obvious reasons to put you at fault when you could have easily gotten a free replacement out of this. Don't answer questions that aren't asked
My father's I9000M had a failed SD and I got it replaced for free. Ironically his had a single ROM flashed on it and mine has had over 100 and been 100% fine.

chambo622 said:
Exactly what I thought...you gave them extremely obvious reasons to put you at fault when you could have easily gotten a free replacement out of this. Don't answer questions that aren't asked
My father's I9000M had a failed SD and I got it replaced for free. Ironically his had a single ROM flashed on it and mine has had over 100 and been 100% fine.
Click to expand...
Click to collapse
Btw, it does not matter how many times you'll reflash, this sd bus failure is pretty common in some first series of GT-9000 and GT-9000M
Sent from my GT-I9000 using XDA Premium App

chambo622 said:
Exactly what I thought...you gave them extremely obvious reasons to put you at fault when you could have easily gotten a free replacement out of this. Don't answer questions that aren't asked
My father's I9000M had a failed SD and I got it replaced for free. Ironically his had a single ROM flashed on it and mine has had over 100 and been 100% fine.
Click to expand...
Click to collapse
My BELL phone started up with an AT&T logo... even if I didn't volunteer the information they would have figured it out and sent me the bill.
As soon as they determine it is off warranty Samsung charges $35 dollars just to evaluate the problem and then charges you to fix it.
Yes I should have just brought it back when it first messed up but I figured my warranty was already voided due to the voodoo installation that I could not reverse (due to the boot loops).
Lesson learned.. probably won't tweak my phone too much in the future...especially if (like my last phone) I can't get into recovery mode - though I'm hoping this is fixed in the new phone I get.

Sozage said:
My BELL phone started up with an AT&T logo... even if I didn't volunteer the information they would have figured it out and sent me the bill.
As soon as they determine it is off warranty Samsung charges $35 dollars just to evaluate the problem and then charges you to fix it.
Yes I should have just brought it back when it first messed up but I figured my warranty was already voided due to the voodoo installation that I could not reverse (due to the boot loops).
Lesson learned.. probably won't tweak my phone too much in the future...especially if (like my last phone) I can't get into recovery mode - though I'm hoping this is fixed in the new phone I get.
Click to expand...
Click to collapse
$5 jig could have saved you $150
But at least you're having your phone repaired...

Kops said:
$5 jig could have saved you $150
But at least you're having your phone repaired...
Click to expand...
Click to collapse
Not repaired! New phone! Maybe even one without a faulty SD card!

Sozage said:
My BELL phone started up with an AT&T logo... even if I didn't volunteer the information they would have figured it out and sent me the bill.
As soon as they determine it is off warranty Samsung charges $35 dollars just to evaluate the problem and then charges you to fix it.
Yes I should have just brought it back when it first messed up but I figured my warranty was already voided due to the voodoo installation that I could not reverse (due to the boot loops).
Lesson learned.. probably won't tweak my phone too much in the future...especially if (like my last phone) I can't get into recovery mode - though I'm hoping this is fixed in the new phone I get.
Click to expand...
Click to collapse
The lesson you should've learn is to READ before you attempt anything.
I've flashed about anything to this phone and it's pretty hard to really brick the thing... Flashing the rom from a captivate is realy not in the line of "tweaking" rather than no-sens what so ever...

t1mman said:
The lesson you should've learn is to READ before you attempt anything.
I've flashed about anything to this phone and it's pretty hard to really brick the thing... Flashing the rom from a captivate is realy not in the line of "tweaking" rather than no-sens what so ever...
Click to expand...
Click to collapse
Right, it should be enought to use common sense, and think a little before any further action. I have tried almost anything, starting with dualboot to xubuntu linux, or editing apk's, modding and themming apps (not always successful), erasing all data partitions, created new ones, installed (or at least tried) to install gentoo linux with simple routing capability, and so on. And I'm still here.
Truth is, that some first lines of SGS were affected with faulty sd bus. But there is no need for paying warranty service, and no need to be few days without my phone. If common sense is used, then User would not:
1) install captivate firmware
2) flash anything before cwm is working
if both above fails, he'll reboot to the download mode, flashed canadian or any other fw containing Sbl.bin, alias recovery.
After that, he would flash standard stock firmware which is used by his operator. As a last thing, he would wipe sdcard from recovery.
Phone will look, behave and WILL BE same as he'd bought it.
So they will look on it, and will see standard, untouched phone, which is unknowingly rebooting itself.
Voila! They'll have no other chance then give you brand new phone right on the spot.
So for the next time, keep your mouth shut at least, when you deal with operator ;-)
Sent from my GT-I9000 using XDA Premium App

t1mman said:
The lesson you should've learn is to READ before you attempt anything.
I've flashed about anything to this phone and it's pretty hard to really brick the thing... Flashing the rom from a captivate is realy not in the line of "tweaking" rather than no-sens what so ever...
Click to expand...
Click to collapse
I wish people would read the entire thread before posting more bs like this.
Trying to put the captivate software on my phone via Odin One Click was the 10th or so thing I tried to do to restore my phone. Nothing would work - recovery mode did not work on my phone nor was I able to restore it.
Flashing the captivate software was an attempt to get recovery working (a desperate attempt) and had nothing to do with my comment about tweaking.
diaf.

I know there is nothing you can do but out is bs that you' voided' warranty. they make you pay $150 for THEIR hardware failure.

Might buy boot-looping Xoom, questions

Hello,
So I bought my Xoom over the weekend when I never heard back from a Craigslister about a Xoom they have that is bootlooping.
Finally got back to me today and I am looking to fix it, and make a little profit.
Guy explained he knows it can get into Fastboot and mentioned RSD lite so I know he has done some research but ultimately he said he is not good at computers and cannot fix it.
My question is what do I need to consider? If I can access hboot ( from power off wait til see M and hit Vol - right?) I should be good to go is my understanding. Is there any way to run a diagnostic and see if there is hardware issues going on?
What would you do I guess lol
He said I could tinker with it first. I am familiar with ADB and rooting / custom roms on Android but have only had my Xoom for about 3 days.
Thanks

If you can definitely get into fastboot, you can recover it; simple as that. Whether there are hardware issues is another matter.

MoreGone said:
Hello,
So I bought my Xoom over the weekend when I never heard back from a Craigslister about a Xoom they have that is bootlooping.
Finally got back to me today and I am looking to fix it, and make a little profit.
Guy explained he knows it can get into Fastboot and mentioned RSD lite so I know he has done some research but ultimately he said he is not good at computers and cannot fix it.
My question is what do I need to consider? If I can access hboot ( from power off wait til see M and hit Vol - right?) I should be good to go is my understanding. Is there any way to run a diagnostic and see if there is hardware issues going on?
What would you do I guess lol
He said I could tinker with it first. I am familiar with ADB and rooting / custom roms on Android but have only had my Xoom for about 3 days.
Thanks
Click to expand...
Click to collapse
The question is, how much are you willing to pay if you can't fix it, then if you can you will be happy, if not you should stay happy.
Bootloop can be software but they can easily be hardware too so better be safe than sorry

take a laptop with you and do "fastboot devices' on the spot.
If the computer can see it then it can be wiped clean and fixed

It's $300 and it wouldn't kill me, obviously wouldn't be ideal but not the end of the world either.

ydaraishy said:
If you can definitely get into fastboot, you can recover it; simple as that. Whether there are hardware issues is another matter.
Click to expand...
Click to collapse
That's what everyone told me when mine went into a boot loop. I was able to flash the new images in fastboot, but it never came out of the boot loop.

P00r said:
The question is, how much are you willing to pay if you can't fix it, then if you can you will be happy, if not you should stay happy.
Bootloop can be software but they can easily be hardware too so better be safe than sorry
Click to expand...
Click to collapse
At what point would I be able to run that command? When powering up, at the M etc?

Zargon335 said:
That's what everyone told me when mine went into a boot loop. I was able to flash the new images in fastboot, but it never came out of the boot loop.
Click to expand...
Click to collapse
Stock images?

Zargon335 said:
That's what everyone told me when mine went into a boot loop. I was able to flash the new images in fastboot, but it never came out of the boot loop.
Click to expand...
Click to collapse
That's certainly a concern

ydaraishy said:
Stock images?
Click to expand...
Click to collapse
Yes.
10chars

@OP
If seller knows about Fastboot & RSD Lite, he's probably on this forum. Might even be in this thread.
HEY SELLER just let me figure this out and I'll buy it right off ya, OK?

If you CAN get out of it that certainly a very good price. Most cases I think I have seen have been recoverable. Maybe ask the seller how he got into this situation in the first place, might give you a better understanding of how to fix it.

Help!! my Angler is dead (bootloop)

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.

Zuk Z1 bootloop for 20 minutes then goes back to working almost okay

Hello, I have a zuk Z1 unrooted and today it just turned off and went into a bootloop then I shut it down through CM recovery and after rebooting another few times it got back up, the bootloop occures at the animation of the boot and it just "breaks" and goes back, I have no idea what to do... would you recommend returning it to the store and asking them to check it out or see what I can do by myself?( I have the phone for 7 months or so and I have another year or warranty at least)
SOLVED

Gvina said:
Hello, I have a zuk Z1 unrooted and today it just turned off and went into a bootloop then I shut it down through CM recovery and after rebooting another few times it got back up, the bootloop occures at the animation of the boot and it just "breaks" and goes back, I have no idea what to do... would you recommend returning it to the store and asking them to check it out or see what I can do by myself?( I have the phone for 7 months or so and I have another year or warranty at least)
Click to expand...
Click to collapse
You can try a factory reset in cm recovery. But first clear cache in recovery, maybe that help.

strongst said:
You can try a factory reset in cm recovery. But first clear cache in recovery, maybe that help.
Click to expand...
Click to collapse
I already tried that, didn't really help and just deleted stuff that I'll have to move back :/ guess I'll take it to the store I bought it at today and see what they'll do.

Seems like qpst will solve your problem. It should fix damaged parts (such as boot sector).
You can find detailed tutorial here:
http://forum.xda-developers.com/zuk-z1/general/qpst-method-how-to-unbrick-to-stock-t3506833

psyckoze said:
Seems like qpst will solve your problem. It should fix damaged parts (such as boot sector).
You can find detailed tutorial here:
http://forum.xda-developers.com/zuk-z1/general/qpst-method-how-to-unbrick-to-stock-t3506833
Click to expand...
Click to collapse
But it can be a risk, if he had warranty. So if there's no warranty, go for this option

strongst said:
But it can be a risk, if he had warranty. So if there's no warranty, go for this option
Click to expand...
Click to collapse
I just gave it to the shop they'll send it to a lab to check it.

strongst said:
But it can be a risk, if he had warranty. So if there's no warranty, go for this option
Click to expand...
Click to collapse
Thank you Captain Obvious, you saved our lives again. :good:

psyckoze said:
Thank you Captain Obvious, you saved our lives again. :good:
Click to expand...
Click to collapse
I'm too long here to know when people don't get all details to think about, then they can make a mistake (brick device, no warranty), so better to tell all options(warranty =better to return to store) so they can make an decision for their own. I know everybody is responsible for his own doing but hey, better to tell the whole story, instead of sending them into possible more problems

strongst said:
I'm too long here to know when people don't get all details to think about, then they can make a mistake (brick device, no warranty), so better to tell all options(warranty =better to return to store) so they can make an decision for their own. I know everybody is responsible for his own doing but hey, better to tell the whole story, instead of sending them into possible more problems
Click to expand...
Click to collapse
I respect your presence here and appreciate your contributions, however, being here for a long time doesn't give you a right to judge people. What I do is telling people that there are other options to try. Don't feel offended, I just think that you are a bit agressive to the newbies. This is my opinion.

strongst said:
You can try a factory reset in cm recovery. But first clear cache in recovery, maybe that help.
Click to expand...
Click to collapse
This is a really old thread. Already went to warranty at the time. Device replaced by a refurbished one it had a motherboard problem later on.
Please do not respond here anymore this is a year old

Gvina said:
This is a really old thread. Already went to warranty at the time. Device replaced by a refurbished one it had a motherboard problem later on.
Please do not respond here anymore this is a year old
Click to expand...
Click to collapse
Please change thread title to "solved or contact a moderator to close it.

Nexus 6P BOOTLOOP after using Facebook

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?