Database Users

Kindle Fire got wet!

I'm new here so I'm hoping somebody can help me. My kindle fire got wet about a week ago and stupid me the first thing I did was wipe it down and turn it on to make sure it still worked. It did at that time and still a few hours later although the battery had died. Upon recharging it no longer worked. First it was stuck in the yellow triangle mode...then alternated between that and the kindle fire logo. My computer would recognize it for a second then the kindle would reboot and it was gone. I researched for days and tried so many things and nothing worked. The sd card cannot be mounted, it's like it disappeared so I can even do anything via TWRP. NOW it is stuck in a total BLUE kindle fire logo boot and doesn't ever stop!
Have I destroyed my kindle or can it be fixed via the factory cable?
Please help me

I'm assuming it was fine before the water incident. Maybe send it back to Amazon and see what they think? You never know, they might exchange one for you.
Otherwise, you can always sell it on eBay as is, and might even get a good price for it. Just make sure the starting bid price is reasonable, as not many people are going to bid for it, unless they are technical people who reckon they can fix it up and resell it.
A factory cable is unlikely to fix it, as it is obviously a hardware problem. Maybe a short in circuits or something. Your biggest mistake was that you turned it on as soon as you wiped it down. How long was it in the water? If it had any water inside it at all, you should have shut it down completely and let it dry out somewhere with good air circulation for at least a day.

are you running ICS?

jji7skyline said:
I'm assuming it was fine before the water incident. Maybe send it back to Amazon and see what they think? You never know, they might exchange one for you.
Otherwise, you can always sell it on eBay as is, and might even get a good price for it. Just make sure the starting bid price is reasonable, as not many people are going to bid for it, unless they are technical people who reckon they can fix it up and resell it.
A factory cable is unlikely to fix it, as it is obviously a hardware problem. Maybe a short in circuits or something. Your biggest mistake was that you turned it on as soon as you wiped it down. How long was it in the water? If it had any water inside it at all, you should have shut it down completely and let it dry out somewhere with good air circulation for at least a day.
Click to expand...
Click to collapse
i agree with everthing here
Taxion said:
are you running ICS?
Click to expand...
Click to collapse
what does that have to do with anything?

Taxion said:
are you running ICS?
Click to expand...
Click to collapse
Yeah that's a valid question. If you drop the Kindle in water and it's running ICS, it can get damaged. The best water protection comes with Jellybean. Jellybean prevents the water from leaking in and messing up the code. smh.

veeman said:
Yeah that's a valid question. If you drop the Kindle in water and it's running ICS, it can get damaged. The best water protection comes with Jellybean. Jellybean prevents the water from leaking in and messing up the code. smh.
Click to expand...
Click to collapse
i dont care who you are, thats funny right there

un4givn85 said:
i dont care who you are, thats funny right there
Click to expand...
Click to collapse
You know? I have to agree with you

jji7skyline said:
I'm assuming it was fine before the water incident. Maybe send it back to Amazon and see what they think? You never know, they might exchange one for you.
Otherwise, you can always sell it on eBay as is, and might even get a good price for it. Just make sure the starting bid price is reasonable, as not many people are going to bid for it, unless they are technical people who reckon they can fix it up and resell it.
A factory cable is unlikely to fix it, as it is obviously a hardware problem. Maybe a short in circuits or something. Your biggest mistake was that you turned it on as soon as you wiped it down. How long was it in the water? If it had any water inside it at all, you should have shut it down completely and let it dry out somewhere with good air circulation for at least a day.
Click to expand...
Click to collapse
Yeah I think you are right with the short circuit...and I realized my mistake directly after I did it It was only in the water a second. Embarrassingly my pool over-flowed while I was lying beside it. It flowed out onto my cellphone, my husbands cellphone and the kindle. I picked them all up immediately but water most def got inside...I'm sure of it

Yes, that is funny.
I asked because since i went to ICS if i use a USB charger for my droid i've been stuck in the same screen, in addition to having other charging issues. I was speculating the problem might not be water related but an unnoticed problem associated with charging (3.0)
I agree a short seems most likely, I was just looking for a possible alternative to check before sending it in with fingers crossed.

If you don't want to send it in, feel free to take it apart yourself and see if you can fix anything. Likely not, as the battery may have bust. There is an easy to follow guide on ifixit.com for taking apart a Kindle Fire.
Remember though, it voids the warranty, so I'd recommend just sending it to Amazon first.

If all else fails and you can ship to England. Then I want the motherboard
sent from my Gnex running Trinity kernel & Awesome's JB rom

My Paperwhite got wet and was still within Amazon's one year regular (didn't buy extended) warranty. I was honest with them and, even though water damage is not covered, they were nice enough to replace it anyway. I am long time Amazon Prime/Kindle Unlimited member and don't know if that swayed their decision, but go to their support website. It's worth a try! They are VERY nice. I did have to send mine to them, but they sent UPS return label, and I had replacement within 5 days!

[Q] hard bricked

today i accepted an OTA update,
i was previously root with an unlocked BL. i RDS lite back to facotry and i was unrooted, therefore thought it safe to
install update. the phone now wont turn on, no matter the combination of buttons.
i know it has a charge its been on the charger forever. no LED light of any kind, and plugging it by usb to PC has no results either.
im pretty sure i hard bricked this device.
at any rate i cant get a warranty for two reasons :
1. unlocked BL
2. denied replacement dude to crack in back glass..
so im a SOL?????

I havent heard of this procedure bricking anyone else, so maybe your phone just thinks the battery is dead. Team Black Hats factory adapter may fix this for you.

If it bricked because of the update, it's the provider's fault, so they should cover it. However, me thinks there is more to this story.
Sent from my Droid Razr M using xda app-developers app

Theres nothing more to the story.
It was on charge all night with the stock charger.. Nothing.
Phone was rooted I unrooted it. Boot loader still unlocked.
I accepted the ota and it won't do anything. I was denied a warranty replacement in store because the back glass has a crack.
Anyway the device is useless I bought an s4 today. And I'm selling the RAZR M to the highest bidder.

mustang5.0 said:
Theres nothing more to the story.
It was on charge all night with the stock charger.. Nothing.
Phone was rooted I unrooted it. Boot loader still unlocked.
I accepted the ota and it won't do anything. I was denied a warranty replacement in store because the back glass has a crack.
Anyway the device is useless I bought an s4 today. And I'm selling the RAZR M to the highest bidder.
Click to expand...
Click to collapse
Cool story. Do I believe that an OTA, by itself, bricked your phone? Nope. Have fun with that S.

if u tried to update and it died, charging it after wont do anything. so i will ask what was ur battery at when u started?

pbanj said:
if u tried to update and it died, charging it after wont do anything. so i will ask what was ur battery at when u started?
Click to expand...
Click to collapse
I charge it all night before work. Got up for work and on the drive to work I accepted the ota so the battery was probably at a good 97%
Im still trying to understand what happened lol

RikRong said:
Cool story. Do I believe that an OTA, by itself, bricked your phone? Nope. Have fun with that S.
Click to expand...
Click to collapse
But then again, nobody cares what you "believe" happened.

RikRong said:
Cool story. Do I believe that an OTA, by itself, bricked your phone? Nope. Have fun with that S.
Click to expand...
Click to collapse
I came here to ask for help on how to revive the phone. I didn't ask for an opinion. What I provided is a 100% accurate account of what led to my phone being bricked. In the hopes someone could give me and idea of what to do. I really could careless about your opinion of "what you believe". If you can't help then don't come here and attack me. Thanks.

mustang5.0 said:
I came here to ask for help on how to revive the phone. I didn't ask for an opinion. What I provided is a 100% accurate account of what led to my phone being bricked. In the hopes someone could give me and idea of what to do. I really could careless about your opinion of "what you believe". If you can't help then don't come here and attack me. Thanks.
Click to expand...
Click to collapse
Don't worry about alpha nerd. He gets his kicks by being smarmy in nearly every thread he posts in.
Sent from my Droid Razr M using xda app-developers app

Have you tried holding down on the power, volume up and volume down buttons at the same time for about 3 secs?

mustang5.0 said:
I came here to ask for help on how to revive the phone. I didn't ask for an opinion. What I provided is a 100% accurate account of what led to my phone being bricked. In the hopes someone could give me and idea of what to do. I really could careless about your opinion of "what you believe". If you can't help then don't come here and attack me. Thanks.
Click to expand...
Click to collapse
There's no attacking. Before we even had chance to help you, you scrapped the phone and went and bought another one. When you originally posted, you didn't give any details to help us out. Personally, I don't believe only the OTA would cause a brick, but as we all know, no one cares what I think.
If your battery is good, you should be able to get into your recovery menu and restore your backup. If you can't do that, you might try to get into the fastboot menu and fastboot back to stock. If you hold the power button, volume down, and volume up at that same time, you should be able to get into the fastboot menu. When in the menu, scroll down with vol- button and choose your choice by hitting the vol+ button. If you can't get the phone to boot into FB, then you are probably stuck. However, if you can get into recovery and/or fastboot, you don't have a brick.
Jersey846 said:
Don't worry about alpha nerd. He gets his kicks by being smarmy in nearly every thread he posts in.
Sent from my Droid Razr M using xda app-developers app
Click to expand...
Click to collapse
edit: I started a pissing match, so I'll end it.
As much as I enjoy being "smarmy", I'll try to ease up so I don't hurt some kids feelings.

Dear rikrong.
First. Please read I supplied every detail I can absolutely express about my phone and what happened.
Second I do important business and there's no point in tying up time in waiting for a fix to my phone when I can get a new one. Why waste the time when I was expecting a customer to call about a $5000 job?
I'm not "some kid" and unlike you I have business to do and don't have time to troll on a forum for people seeking help with their devices. Hold your tongue and don't pass judgment on someone you don't know.
And don't worry about hurting my feelings. I GUARANTEE you don't have the mental capacity to offend me, friend.
I would like to revive the device and donate it to a family member or friend who could make better use of it than I.
To wrap this up, no button combos or ANYTHING will turn the device on, it literally is a brick, I heard of JTAG and this may be the route I will take..

mustang5.0 said:
Dear rikrong.
First. Please read I supplied every detail I can absolutely express about my phone and what happened.
Second I do important business and there's no point in tying up time in waiting for a fix to my phone when I can get a new one. Why waste the time when I was expecting a customer to call about a $5000 job?
I'm not "some kid" and unlike you I have business to do and don't have time to troll on a forum for people seeking help with their devices. Hold your tongue and don't pass judgment on someone you don't know.
And don't worry about hurting my feelings. I GUARANTEE you don't have the mental capacity to offend me, friend.
I would like to revive the device and donate it to a family member or friend who could make better use of it than I.
To wrap this up, no button combos or ANYTHING will turn the device on, it literally is a brick, I heard of JTAG and this may be the route I will take..
Click to expand...
Click to collapse
Well, that's nice, you tell me not to attack you and you come right back at me. I tried to tie it up in my last post and offer some help, but I guess you didn't get it. If you think I'm trolling, you need to put on your big girl panties and take a look at the other forums that aren't super newb friendly like these tech forums. I tried to offer peace, but you came right back at me. I also have plenty of of business to take care of every day. It just so happens that I like to come to these forums when I'm at home and finished busting my knuckles at work.
I tried to offer some help, after realizing how I did come off as an ass in my original post, but you fired right back at me. So,have fun.

I stand my my recommendation in post #2. It doesnt make sense that this procedure would brick your phone so my feeling is that its not bricked. I had a similar experience with my D2G back in day. For $10 team black hats factory adapter is worth a shot. Even if you stick with the S fixing your XT907 will fetch you more money on the market.

Stock firmware with root access - Warranty Claim being denied... :(

Hey guys.
So, the worst case scenario seems to be playing out with my phone, and Samsung & the retailer are turning into villains. I've had my phone maybe 8 months, I flashed root to it in the first week. This is the stock firmware, just with root access so I could run Titanium Backup. The phone was working fine, had recently started to become a little bit chuggy due to lots of apps & data, though yesterday I opened a link from a friend which looks like it's killed my phone. I was in the middle of doing my Japanese lessons with Duolingo... received a Whatsapp message from a friend with a link to a sale ( I could post the link, but spam filters might block it)- the moment I opened the link in Chrome my phone had a heart attack. Froze, rebooted... but worse, the boot animation also froze. I tried the power reset (volume down + power button), and managed to get as far as the lock screen. Upon entering my PIN, the phone went black and it has been a brick ever since. I took my phone to the shop I bought it from this morning and regret being honest about having root access. I cannot possibly fathom how having full access to MY DEVICE could possibly kill any hardware or disable the device to this degree, and as such think this warranty voiding angle is a giant scam.
This post is seeking a few things... 1) sympathy (lots please).... 2) advice about warranty (are they within their rights to deny my warranty? I'm in Australia, imported phone) ... 3) How could this happen?!?!?!
Please, thanks, and woe is me....
:-/

loudboy77 said:
Hey guys.
So, the worst case scenario seems to be playing out with my phone, and Samsung & the retailer are turning into villains. I've had my phone maybe 8 months, I flashed root to it in the first week. This is the stock firmware, just with root access so I could run Titanium Backup. The phone was working fine, had recently started to become a little bit chuggy due to lots of apps & data, though yesterday I opened a link from a friend which looks like it's killed my phone. I was in the middle of doing my Japanese lessons with Duolingo... received a Whatsapp message from a friend with a link to a sale ( I could post the link, but spam filters might block it)- the moment I opened the link in Chrome my phone had a heart attack. Froze, rebooted... but worse, the boot animation also froze. I tried the power reset (volume down + power button), and managed to get as far as the lock screen. Upon entering my PIN, the phone went black and it has been a brick ever since. I took my phone to the shop I bought it from this morning and regret being honest about having root access. I cannot possibly fathom how having full access to MY DEVICE could possibly kill any hardware or disable the device to this degree, and as such think this warranty voiding angle is a giant scam.
This post is seeking a few things... 1) sympathy (lots please).... 2) advice about warranty (are they within their rights to deny my warranty? I'm in Australia, imported phone) ... 3) How could this happen?!?!?!
Please, thanks, and woe is me....
:-/
Click to expand...
Click to collapse
It depends on how you rooted but guessing as you rooted when you first got the device it probably tripped knox and voided your warranty... either way by the sounds of things you can fix this yourself by flashing official firmware with odin do you know how to do this?
In fact can you get into recovery mode?
while the phone is off try holding power button + home button + volume upfor around 10 seconds (this does not require the boot animation to load)
If you can do that use the volume keys to navigate down to "wipe data and factory rest" then navigate to yes and after that reboot your phone (might take 10 mins to boot) but should fix your problem

EasyAndroidPro said:
It depends on how you rooted but guessing as you rooted when you first got the device it probably tripped knox and voided your warranty... either way by the sounds of things you can fix this yourself by flashing official firmware with odin do you know how to do this?
In fact can you get into recovery mode?
while the phone is off try holding power button + home button + volume upfor around 10 seconds (this does not require the boot animation to load)
If you can do that use the volume keys to navigate down to "wipe data and factory rest" then navigate to yes and after that reboot your phone (might take 10 mins to boot) but should fix your problem
Click to expand...
Click to collapse
For a moment I was excited to get a reply, and then I read yours. Please read my post before replying. If I could flash anything or get any kind of response do you think I would have taken my phone in for repairs??! It's DEAD. They changed the battery, the display (so they tell me) and they like to refer to the remainder as "the motherboard" but they mean the whole damn phone... Can anyone report if this has happened to them? Seems so thoroughly weird.... and to blame it on the fact I have root access.... the same as thousands of others.... it's really dodgy.

loudboy77 said:
For a moment I was excited to get a reply, and then I read yours. Please read my post before replying. If I could flash anything or get any kind of response do you think I would have taken my phone in for repairs??! It's DEAD. They changed the battery, the display (so they tell me) and they like to refer to the remainder as "the motherboard" but they mean the whole damn phone... Can anyone report if this has happened to them? Seems so thoroughly weird.... and to blame it on the fact I have root access.... the same as thousands of others.... it's really dodgy.
Click to expand...
Click to collapse
Wow good look getting help with an attitude like that :good: i was offering beginner advice because from your post you sounded like an newbie. Good luck i won't be helping further.

EasyAndroidPro said:
Wow good look getting help with an attitude like that :good: i was offering beginner advice because from your post you sounded like an newbie. Good luck i won't be helping further.
Click to expand...
Click to collapse
Oh no... you're going to keep that awesome advice to yourself? Maybe someone else can suggest I try turning it off and on again?
Seriously- it's frustrating enough being put through the wringer of losing a device like this, and even moreso being held over a barrel by Samsung & the retailer. I'm doing my best to be clear and spell out my situation, in the interests of not only myself, but the whole Samsung community. When you're locked out of a device by design, and all you can do is press buttons in certain combinations, please assume that I meant it when I said I already tried pressing the buttons.
More frustrated. Thanks. =)

loudboy77 said:
Oh no... you're going to keep that awesome advice to yourself? Maybe someone else can suggest I try turning it off and on again?
Seriously- it's frustrating enough being put through the wringer of losing a device like this, and even moreso being held over a barrel by Samsung & the retailer. I'm doing my best to be clear and spell out my situation, in the interests of not only myself, but the whole Samsung community. When you're locked out of a device by design, and all you can do is press buttons in certain combinations, please assume that I meant it when I said I already tried pressing the buttons.
More frustrated. Thanks. =)
Click to expand...
Click to collapse
Come on, dude. I/we know the frustration of things like this but that's completely uncalled for. He offered genuine advice from the information given in your post.
I hope you get it sorted but I doubt you'll get much in the way of helpful responses if you are this rude.

It is completely within their rights to deny you warranty. You rooted the thing. The very act of rooting voids warranty. And yes, complete access to the device can do that to your phone because any rogue app can delete system files/programs that are essential to running the phone, or even turning it on. As it is, suck it up and accept you lost warranty and pay for the repair or get a new phone.
Sent from my SM-T231 using Tapatalk

what whatsapp message could do that much harm and has that done any harm to your friends (rooted) phone?
I think that after the freeze the phone has become damaged in software
Could be that it happens with any application that filled the memory.
If nothing can be saved with any trick and you have done everything I'm afraid there is nothing more possible than all the "tricks" here on XDA that are available after a good search.
Succes

loudboy77 said:
Hey guys.
So, the worst case scenario seems to be playing out with my phone
Click to expand...
Click to collapse
If u cant get into Download mode, then the people at service centre also cant
Go to a different service centre and play dumb. Just say that 'The phone stopped working when I was travelling. I dont know what happened. The phone just died'
Dont give anymore info than this. If u do then they might pin it on you
Just play dumb and deny everything lol
They cannot prove that the phone is rooted just by looking.
In your case the motherboard might be fried (IDK maybe) and if they replace motherboard then ur knox flag will be reset.
Visit another Service centre. Dont go to the same place again.

chanchan05 said:
It is completely within their rights to deny you warranty. You rooted the thing. The very act of rooting voids warranty. And yes, complete access to the device can do that to your phone because any rogue app can delete system files/programs that are essential to running the phone, or even turning it on. As it is, suck it up and accept you lost warranty and pay for the repair or get a new phone.
Sent from my SM-T231 using Tapatalk
Click to expand...
Click to collapse
There was recently a ruling in the States that returned some rights to consumers to unlock their devices while keeping warranty. In Australia we have some pretty decent consumer protection laws. http://ausdroid.net/2012/10/22/warranties-and-bootloaders-what-you-should-know/
You're not showing an awful lot of compassion to the community of developers who spend their time trying to root phones... too bad if your phone dies? nice.

I suggest you read this.
http://www.samsung.com/au/support/warranty/
From the read of it. You have already violated 2 things.
1.Your phone was imported.
2.Modification(in this case root)
Also, if you think software can not kill hardware then you are wrong. Some hardware are also being controled by software. Of course something like the glue holding the display together come off is definite not caused by software but something like fried mainboard/electronic is possible.
Of course, this seem very unlikely in this case but still not impossible. If you still want warranty, you must prove yourself innocent enough for them to accept your claim which seem nearly impossible.
Also being honest about rooting when claiming your warranty will instantly have your warranty rejected, no question asked.
Well, you can still try using the customer right law or something like that to help you, if you don't mind wasting time.
Sent from my SM-G935F using Tapatalk

loudboy77 said:
There was recently a ruling in the States that returned some rights to consumers to unlock their devices while keeping warranty. In Australia we have some pretty decent consumer protection laws. http://ausdroid.net/2012/10/22/warranties-and-bootloaders-what-you-should-know/
You're not showing an awful lot of compassion to the community of developers who spend their time trying to root phones... too bad if your phone dies? nice.
Click to expand...
Click to collapse
Unlocking and rooting are two different things. Compassion? What are you talking about? Just accept that rooting voids warranty. Rooting opens the phone to exploits which may or may not cause problems. The manufacturer has every right to deny you service because they cannot prove if it is a fault on their part or yours. If you a friend bought an unrooted phone from you and roots it and bricks it, would you take back the phone and give him a new one free of charge? Or would you shoulder repair fees for your friend? No. Same thing. If you accidentally drop your chicken on the floor, KFC won't take it back.
There is consumer protection, and there is abuse.
And I appreciate the rooting community, but understand and accept the fact that doing so voids my warranty.
If my phones dies? I pay for the repairs. Simple.
Sent from my SM-T231 using Tapatalk

EasyAndroidPro said:
It depends on how you rooted but guessing as you rooted when you first got the device it probably tripped knox and voided your warranty... either way by the sounds of things you can fix this yourself by flashing official firmware with odin do you know how to do this?
In fact can you get into recovery mode?
while the phone is off try holding power button + home button + volume upfor around 10 seconds (this does not require the boot animation to load)
If you can do that use the volume keys to navigate down to "wipe data and factory rest" then navigate to yes and after that reboot your phone (might take 10 mins to boot) but should fix your problem
Click to expand...
Click to collapse
So I take it that there's a way around knox to root the phone without tripping it? I've got the Exynos variant of this phone, would you mind putting me in the right direction on rooting it? I've looked everywhere but never found a way that does not trip knox.

Alaa Joseph said:
So I take it that there's a way around knox to root the phone without tripping it? I've got the Exynos variant of this phone, would you mind putting me in the right direction on rooting it? I've looked everywhere but never found a way that does not trip knox.
Click to expand...
Click to collapse
I've not tried it myself nor have I looked into it myself I rooted the normal way as I don't care about Knox related apps I just remember seeing the reports around.
Here is a related thread https://forum.xda-developers.com/ga...ot-method-via-engkernel-t3423438/post68204186

Nexus 6P Stuck in a boot loop even after stock image

Hey guys, I was using my phone today as per usual but for some reason, the app I was using crashed and then the phone shut off. The phone then went into a boot loop and I thought it'd be an easy fix to just reformat the phone/factory reset, however, these solutions didn't work.
So I went to Factory Image for Nexus and installed 7.1.2 (N2G48B, Jul 2017) with the script and line by line but there is still no success. The phone just turns on, has the "Google" boot screen then turns back off. I am unable to get into recovery and nothing that I tried worked.
I tried looking around for a fix and there are some wacky solutions that people have used and had some success like using a heat gun on it and letting it die out but I feel like that's unsafe.
I also tried this but it also didn't work.
Can anyone help me with this issue?
(Also my 6P is out of warranty so I'm pretty much screwed)
Update:
I contacted Google first, then Contacted Huawei about the same issue. Explained to Google what was wrong, then Huawei and Huawei told me to just contact a 3rd party repair shop to see if they can fix it. I looked at motherboard replacements for my 6P and it costs around $200-$300. I thought that was a bit insane, so I contacted Google again in hopes of them replacing my 6P despite it not being under warranty. I explained to them that I contacted Huawei about to issue, then looked all over the internet to find a solution to the problem and they understood that I was frustrated with this problem so they replaced my device! Took a lot of explaining but it all worked out.
tl;dr contacted google to RMA my device even though it is not under a warranty. Also, as far as I know there is no solution to this problem except replacing the motherboard.

vraj1470 said:
Hey guys, I was using my phone today as per usual but for some reason, the app I was using crashed and then the phone shut off. The phone then went into a boot loop and I thought it'd be an easy fix to just reformat the phone/factory reset, however, these solutions didn't work.
So I went to Factory Image for Nexus and installed 7.1.2 (N2G48B, Jul 2017) with the script and line by line but there is still no success. The phone just turns on, has the "Google" boot screen then turns back off. I am unable to get into recovery and nothing that I tried worked.
I tried looking around for a fix and there are some wacky solutions that people have used and had some success like using a heat gun on it and letting it die out but I feel like that's unsafe.
I also tried this but it also didn't work.
Can anyone help me with this issue?
(Also my 6P is out of warranty so I'm pretty much screwed)
Click to expand...
Click to collapse
First, check a few things. Can you enter recovery mode? When flashing stock, did you flash all the images separately after extracting the stock zip and run the format user data command afterwards?. What do you see in device manager when plugging your phone in while in bootloader?

DEVILOPS 007 said:
First, check a few things. Can you enter recovery mode? When flashing stock, did you flash all the images separately after extracting the stock zip and run the format user data command afterwards?. What do you see in device manager when plugging your phone in while in bootloader?
Click to expand...
Click to collapse
I cannot enter recovery mode. I called Huawei and they said "When you are in bootloader, go to Recovery mode option and then when you press the power button, hold the power button in and the Volume Up button to get into recovery." I tried these steps but it doesn't work.
I first used the script that was given in the folder to flash the stock image but it didn't work. So I did the steps manually and still had no luck. I do not know what you mean when you say "format user data" command. The instructions on the google website doesn't say to do this step. Also, I assumed that all the data is erased when I locked and unlocked the bootloader.
When I plug it into my computer, My device manager says this: https://puu.sh/wJBzI/f7fa02b291.png

i am literally having the same problem. Just a random bootloop in the middle of the day. cant get to recovery, did a full factory reset, even relocked, stuck in a google logo bootloop. followed step 10 in this thread

Same issue here. I can get into bootloader and recovery. Have tried flashing all sorts of different firmwares, sideloaded many OTA's.
in TWRP if I try to backup or restore it craps out a few percent in.

Andrewbud said:
Same issue here. I can get into bootloader and recovery. Have tried flashing all sorts of different firmwares, sideloaded many OTA's.
in TWRP if I try to backup or restore it craps out a few percent in.
Click to expand...
Click to collapse
Have you tried formating partions?

Wow this seems like a common issue..I'm surprised that there isn't a fix for it already. I'll keep this post updated if I find a fix for the issue, but as for now, I'm waiting for my phone to die out and seeing if I can do anything from there.

vraj1470 said:
Wow this seems like a common issue..I'm surprised that there isn't a fix for it already. I'll keep this post updated if I find a fix for the issue, but as for now, I'm waiting for my phone to die out and seeing if I can do anything from there.
Click to expand...
Click to collapse
BLOD is a hardware issue. No recovery mode= S.O.L. Time to move on.

Exodusche said:
Have you tried formating partions?
Click to expand...
Click to collapse
Some but not all.
If I wanted to format all possible partitions which would they be?

Andrewbud said:
Some but not all.
If I wanted to format all possible partitions which would they be?
Click to expand...
Click to collapse
Not sure I just did data and cache. Don't believe mine was true BLOD but presented same symptoms.

DEVILOPS 007 said:
First, check a few things. Can you enter recovery mode? When flashing stock, did you flash all the images separately after extracting the stock zip and run the format user data command afterwards?. What do you see in device manager when plugging your phone in while in bootloader?
Click to expand...
Click to collapse
v12xke said:
BLOD is a hardware issue. No recovery mode= S.O.L. Time to move on.
Click to expand...
Click to collapse
I find it hard to belive it's ****ed beyond all repair...It's a pretty new phone and there still isnt any solution for it? That's insane.

vraj1470 said:
I find it hard to belive it's ****ed beyond all repair...It's a pretty new phone and there still isnt any solution for it? That's insane.
Click to expand...
Click to collapse
Out of warranty? Well, sure you can buy a motherboard and swap it out for more than the phone is worth... or just buy another phone?

v12xke said:
Out of warranty? Well, sure you can buy a motherboard and swap it out for more than the phone is worth... or just buy another phone?
Click to expand...
Click to collapse
It's out of warranty.
But why would a phone that was made in 2015 break in 2017. A 2 year life cycle? It's so infuriating that I spent $550 on a phone and now the only other option for me to use this phone after a year and a half is to either buy a new motherboard for the phone or get a new one.

Got an rma with Huawei Canada. Purchased from telus Dec 1 2015

I don't wanna sound like an ass but clearly folks are not reading and searching before posting. This BLOD issue has so many different threads it's now silly. Boot loop with no recovery equals dead. Period. If you have recovery available, them keep plugging away at the options people's have offered in countless threads. As a parting note, just scroll down passed this past for say the next 40 and count the number of posts about boot looping. It might surprise you... Sorry for the rant...

I have the BLOD as well. 16 month old phone bought from Best Buy, so Google and Huawei have both given me the middle finger. I'm so [email protected]#king pissed about it.
I've been able to do the hairdryer trick to get the phone up and running again, but I can't really do anything beyond texting. The moment I do anything proc-intensive that would cause it to flip to the big cluster I'm back to the BLOD and fishing out my wife's hairdryer again. It's lunacy.
I'm curious as to how big of a fraction of the N6Ps are affected by this. Like CyberpodS2 said, there are a bazillion threads about this now, so how many Nexuses have sh$t the bed at this point? Seems like a lot (although the internet is admittedly a very noisy place)...

mustardayonnaise said:
I have the BLOD as well. 16 month old phone bought from Best Buy, so Google and Huawei have both given me the middle finger. I'm so [email protected]#king pissed about it.
I've been able to do the hairdryer trick to get the phone up and running again, but I can't really do anything beyond texting. The moment I do anything proc-intensive that would cause it to flip to the big cluster I'm back to the BLOD and fishing out my wife's hairdryer again. It's lunacy.
I'm curious as to how big of a fraction of the N6Ps are affected by this. Like CyberpodS2 said, there are a bazillion threads about this now, so how many Nexuses have sh$t the bed at this point? Seems like a lot (although the internet is admittedly a very noisy place)...
Click to expand...
Click to collapse
I saw all of the posts about the bootloop. I just couldn't find a solution to the problem so I posted again with a post thst had detailed things on what I did. It's insane how there is no fix for it though. It's even a common problem and Google/Huawei doesn't cover it unless its under warranty...
I was able to contact Google about the situation and they sent me a replacement. I'm considering selling the unit they sent me..

vraj1470 said:
I saw all of the posts about the bootloop. I just couldn't find a solution to the problem so I posted again with a post thst had detailed things on what I did. It's insane how there is no fix for it though. It's even a common problem and Google/Huawei doesn't cover it unless its under warranty...
I was able to contact Google about the situation and they sent me a replacement. I'm considering selling the unit they sent me..
Click to expand...
Click to collapse
You should unload it on Craigslist/Ebay/whatever ASAP, in my opinion. Use the equity to buy a better, more stable phone... I love the Pixel but it costs a lot... at least it's not ****ing Huawei. Screw this goddamn phone.
I've picked up an LG G5 as a stopgap until I can figure out what my next move is. I'm just really annoyed because I had planned on keeping the 6P for at least 3 years; I'm not big on constantly upgrading.. I like to buy a high-end product that will last me a long time and that I won't have to worry about. I didn't even make halfway to that ownership goal.

mustardayonnaise said:
I have the BLOD as well. 16 month old phone bought from Best Buy, so Google and Huawei have both given me the middle finger. I'm so [email protected]#king pissed about it.
I've been able to do the hairdryer trick to get the phone up and running again, but I can't really do anything beyond texting. The moment I do anything proc-intensive that would cause it to flip to the big cluster I'm back to the BLOD and fishing out my wife's hairdryer again. It's lunacy.
I'm curious as to how big of a fraction of the N6Ps are affected by this. Like CyberpodS2 said, there are a bazillion threads about this now, so how many Nexuses have sh$t the bed at this point? Seems like a lot (although the internet is admittedly a very noisy place)...
Click to expand...
Click to collapse
Oh the same thing happened here with my 64gig version. My warranty expired in April and Phone BLOD in June in the middle of the day while i was listening to music at office. Had to spend the rest of the day jumping through loops with either google and huawei. The end result was motherboard replacement and since i had no warranty they wanted to give 25k (390$) (New 32gb comes at around 22k). I tried all the options that were available here on XDA but nothing worked. I am so disappointed in huawei and google, I've seen cases in US where they replace the device even when warranty is expired but not here, the customer care services are sorely lacking at my place. Week after bought One Plus 5 which is loads better than 6P and you don't even need to root it as most of things that needed root comes per-loaded in their Settings and no bloatware whatsoever.

mustardayonnaise said:
You should unload it on Craigslist/Ebay/whatever ASAP, in my opinion. Use the equity to buy a better, more stable phone... I love the Pixel but it costs a lot... at least it's not ****ing Huawei. Screw this goddamn phone.
I've picked up an LG G5 as a stopgap until I can figure out what my next move is. I'm just really annoyed because I had planned on keeping the 6P for at least 3 years; I'm not big on constantly upgrading.. I like to buy a high-end product that will last me a long time and that I won't have to worry about. I didn't even make halfway to that ownership goal.
Click to expand...
Click to collapse
Yeah, I'm probably gonna sell it and wait for the Galaxy Note 8 maybe. I'm going to stick with my 3 year old HTC one M8 in the meantime...Also, What do you think the asking price is for the Nexus 6P 64GB model is?

Help! How to fix Hard-Bricked Samsung Galaxy S4?

Hard Bricked Phone: A Phone that won't turn on by any means. Booting to the OS or even opening the Custom/Stock recovery or Download Mode simply won't work.
I've searched plenty of forums regarding Android phones that are "Bricked". But it seems to me that most of the instructions laid out by the "replyer" require the phone to be opened up using special combinations of buttons that would either lead to the Custom/Stock recovery mode or the Download mode which is basically a definition of a "Soft Bricked Phone". A phone wherein it would still turn on and simply has problems with how the OS/Kernel/whatever runs.
Problem: I toyed with my Samsung Galaxy S4 in such a way that it would deal with underclocking my phone. I know that underclocking is a risky thing to do. But I was lowering it to the point where My phone would still run stable... until one day it just suddenly gave out. My phone would still turn on but for about 2 seconds and it would turn itself off immediately. That means that even if i was fast enough to go into the download mode or to my Custom Recovery mode, it would still shut off completely as if I pulled my battery out of my phone.
I'm not really in an INSANE need of help to repair my phone, but a good "Fixing a Hard-Bricked Phone is impossible." or something would definitely help as it would give me a sense of peace around all the threads claiming that they can fix such said phones that are in the same working condition as a brick.
thank you for any help.

:Bump:

Yeah, if the device doesn't turn on through any manner of key press combinations, you're pretty much screwed. I assume when you connect the device to the PC you get nothing?

If I use some type of flashing program from my pc that detects my phone on download mode, it sort off detects it for half to a full second until my phone will give in.
Thanks for the reply.

:Bumping:
- Just to keep dusts away.

friend is totally repairable but you have to disarm and perform jtag will return as magic JTAG samsumg you team only will be damaged the initializer in 95% of cases is so

larrywilson said:
friend is totally repairable but you have to disarm and perform jtag will return as magic JTAG samsumg you team only will be damaged the initializer in 95% of cases is so
Click to expand...
Click to collapse
JTAG? As in that Jtag brick repair where in you disassemble the back part of your phone and you have to connect the Riff/Jtag box to the 6 small pins and use a software on the computer to use the "resurrection" button? . Looking at that process, it does make it possible to unbrick insanely bricked phones. However I do need a device for that and a bit of electronic skills in which I have no background on. Not to mention that buying such device almost costs the same as buying another Samsung galaxy s4 from where I come from. Seems like overkill at this point haha.
Thanks for the reply as it did answer my question, but I think I'll try sticking to other possible alternatives if any. :fingers-crossed:

@gobbler6000: Not to mention owning one of those devices is questionable legality, depending on where you are.
To be honest, after five years, it's not worth trying to resurrect a dead S4. Sell it for parts and purchase a newer device. Used devices should be easy to come by, and I'm sure you could get a good bargain that way.

Strephon Alkhalikoi said:
@gobbler6000: Not to mention owning one of those devices is questionable legality, depending on where you are.
To be honest, after five years, it's not worth trying to resurrect a dead S4. Sell it for parts and purchase a newer device. Used devices should be easy to come by, and I'm sure you could get a good bargain that way.
Click to expand...
Click to collapse
Thanks! It's the hard and cold truth but I guess s4 is definitely not worth the trouble now. I thought I could probably use my old phone without spending a few bucks. I'll just use my 13 year old appeal and lotsa chores to get my parents' appeal for a new phone.
In one way or another, the questions were answered. How do I lock this thread? :fingers-crossed:

gobbler6000 said:
In one way or another, the questions were answered. How do I lock this thread? :fingers-crossed:
Click to expand...
Click to collapse
You don't. Report the thread to a mod and ask them to close it.

harry779 said:
I have faced the same situation once and one of the blog has helped me that I have mentioned below.
Click to expand...
Click to collapse
Link seems kinda scammy. It's also of no help to the OP. Besides the fact this thread is from last year, the OP's device was hard-bricked. Your link spends most of its bandwidth on soft-brick solutions, devoting only a single paragraph on hard bricks. That one paragraph on the page can be summed up in two words: you're screwed.