My S7E is suddenly bootlooping. Dying? - Samsung Galaxy S7 Edge Questions and Answers

Really, I am super unlucky with my Samsung mobiles...
My S7 edge (international Exynos, unlocked) is stock and unrooted.
I had a SW update (small one, only 12Mb) a few days ago.
Then, all of a sudden, my S7 edge started to reboot itself during the night. Just once, but then on the next day again.
Once it froze and then rebooted, so I went into the recovery to perform a wipe cache.
First thing I noticed there: When entering the recovery it says something like "system update" and you see the droid standing there.
Then after a few seconds, the droid seems to be broken / system update failing with a big exclamation mark. I am sure you know what I am talking about.
Also when rebooting out of the recovery, it writes the error message "Unable to mount data (invalid argument)". You can just see that message for a millisecond before the reboot starts.
Sooo, anyway: In the recovery I wiped the cache and rebooted.
During the Samsung logo buildup the process froze. Then
--> Boot loop.
A few dozen loops, with the Samsung logo always freezing, later it came back to life, but still would boot loop when restarted.
So I did a factory reset. Did not fix it. Then I flashed my Firmware via ODIN again. Still not fixed.
As a last resort I used Smart Switch to do a emergency restore, you know the one where you have to input your mobile's serial number.
So Smart Switch flashed my initial stock firmware, BUT
Still the phone is behaving the same and looping. Sometimes I get it online and then everything seems to work fine, but after going to recovery:
Same broken droid guy, same loop afterwards.
I guess something is really corrupted or hw-wise dying.
Any further ideas if I can try something else? Or is Samsung Service my only hope :crying:

Sound like EPROM issue. Means memory problem. Take it to Samsung if is possible

Have you managed to fix your phone? I am experiencing this same thing except it all started back in November.

To be honest, you sound like you've done everything most people would suggest with reflashing etc. So this does really sound hardware based. Look at a warranty replacement?
Sent from my SM-G935F using XDA-Developers mobile app

Check this problem if some time reboot see it auto enter download mode and have message like can not read memory nand. Mean nand dying because device have run with hot along time.

Thx guys, I will bring it next week to Samsung service center.
It doesn't say anything about "Can't read memory" or something, I've seen that error already when the internal memory of my note 4 died. But as no flashing attempts fixed my S7, who knows what's really up... Samsung shall take care of it. I didn't root because of my experiences with my note 4, and good so... 3 months after I bought the S7 it's already f*ing corrupt

MisterKanister said:
Thx guys, I will bring it next week to Samsung service center.
It doesn't say anything about "Can't read memory" or something, I've seen that error already when the internal memory of my note 4 died. But as no flashing attempts fixed my S7, who knows what's really up... Samsung shall take care of it. I didn't root because of my experiences with my note 4, and good so... 3 months after I bought the S7 it's already f*ing corrupt
Click to expand...
Click to collapse
Can you still use your phone btw?
My phone just stopped working today. I tried to do a master reset hoping it would fix it but it didn't. Now I couldn't even get past the Welcome Screen with the languages selection because it just freezes from there. It has been on boot loop since and the phone is unusable.
Very sad.

iamkrystal00 said:
Can you still use your phone btw?
Click to expand...
Click to collapse
Well, not really. It's bootlooping and might eventually come online sometimes, but I leave it powered off for now.
iamkrystal00 said:
Very sad.
Click to expand...
Click to collapse
Yeh, this is rubbish. First my Note 4's internal memory died after 1 year, now my S7 edge's memory (?) dies after 3 months.

MisterKanister said:
Well, not really. It's bootlooping and might eventually come online sometimes, but I leave it powered off for now.
Yeh, this is rubbish. First my Note 4's internal memory died after 1 year, now my S7 edge's memory (?) dies after 3 months.
Click to expand...
Click to collapse
I ended up taking my phone to samsung's service center. I just got news from the technician today that I might have to replace the motherboard, and guess what, I have to pay for it because I bought this phone from another country and warranty is basically void. It sucks because the phone is very new and I never dropped it. Not even a scratch present.
I am totally disappointed.

iamkrystal00 said:
I ended up taking my phone to samsung's service center. I just got news from the technician today that I might have to replace the motherboard, and guess what, I have to pay for it because I bought this phone from another country and warranty is basically void. It sucks because the phone is very new and I never dropped it. Not even a scratch present.
I am totally disappointed.
Click to expand...
Click to collapse
That sucks!
I also got mine back from Samsung Service and it's working again.
Since it took them only 1 day to repair and they even didn't remove my screen protector, I am quite sure that they just did some advanced reflashing and no hardware change was required.
Now I am wondering what they can flash which we can't :silly:

MisterKanister said:
That sucks!
I also got mine back from Samsung Service and it's working again.
Since it took them only 1 day to repair and they even didn't remove my screen protector, I am quite sure that they just did some advanced reflashing and no hardware change was required.
Now I am wondering what they can flash which we can't :silly:
Click to expand...
Click to collapse
That's awesome man! You seem really lucky. The techs that checked your phone were probably skilled enough to fix the issue. Those that checked mine couldn't even tell me what they found and just told me that a new motherboard is needed. I doubt they even tried.
Did your phone behave weirdly again after you got it back?

iamkrystal00 said:
Did your phone behave weirdly again after you got it back?
Click to expand...
Click to collapse
Actually I was wrong, the Samsung tech's really changed the mainboard - it wasn't just a reflash. Just had a look at the receipt where it was written
And yes, now it's working as it should.

MisterKanister said:
Actually I was wrong, the Samsung tech's really changed the mainboard - it wasn't just a reflash. Just had a look at the receipt where it was written
And yes, now it's working as it should.
Click to expand...
Click to collapse
Oh then that means my board is truly the problem. Did the tech tell you what caused it? I tried asking but they keep saying they don't know.
Now they are going to charge me $300 for a new board. :crying:

Related

Note 4 completly dead

My snapdragon phone started acting weird today. Was slow and locked up for many minutes doing just simple tasks.
Took a backup of the phone and ran a factory reset.
The phone was fast and smooth after this and i was satisfied. But then i did a reboot, and the phone never booted again.
It does not even charge. Just dead.
Anyone else had this issue? Had the phone since release, and it has never been rooted or anything that would break warranty, so i will contact the place i bought it from.
But can this might be battery related? In that case it would be much easier for me to get a new battery.
Have tried to charge it for a while without any result. Does not seem to draw any power either as the charger is cold..
but when i plug it in the pc, windows detects something for about 2 seconds, but claims it's unrecognizable...
Rocking my Nexus 4 now, smooth phone with android 6.0, but camera and battery sucks bigtime... I want my note back..
I have exact same problem. But my phone was rooted and service center told me my warranty is void. They told me the mainboard is bad and need to be replaced. It will cost about half of the new phone price...
Try pressing "Vol +" + "Vol -" + "Lock" + "Start" buttons for a few seconds
Pd: wrong section, this should go on troubleshouting
sbehring said:
I have exact same problem. But my phone was rooted and service center told me my warranty is void. They told me the mainboard is bad and need to be replaced. It will cost about half of the new phone price...
Click to expand...
Click to collapse
Take it to a different store from your carrier and this time don't tell them its been rooted. Tell them it hasn't been if they ask and they should replace it.
Have tried every combination possible with holding in buttons. No sign of life.. Good thing i got a backup while it was still "working"
I have had many plans to root the device and get in some custom ROM but i have been satisfied with stock and never found the time to do it, and i am happy for that now
Sorry for posting in the wrong place. Maby an admin can move this post?
Welcome to the party, almost the same thing happened to me except it failed to do a factory reset.
http://forum.xda-developers.com/not...-sm-n910w8-t3249970/post63890570#post63890570
Just taking out the battery and inserting it back again properly solved it for me... , Ur battery might not be fitting properly pls check ?
XproZayd said:
Welcome to the party, almost the same thing happened to me except it failed to do a factory reset.
http://forum.xda-developers.com/not...-sm-n910w8-t3249970/post63890570#post63890570
Click to expand...
Click to collapse
Thanks for the information. I guess my motherboard is dead then..
Senthil360 said:
Just taking out the battery and inserting it back again properly solved it for me... , Ur battery might not be fitting properly pls check
Click to expand...
Click to collapse
This has been checked and it's not the problem. But thanks for suggestion.
If i get a new Note 4 on warranty i will probably sell it and get a Nexus phone, or install an clean ROM right away. Stock android is so much smoother than touchwiz.
Samsura said:
Thanks for the information. I guess my motherboard is dead then..
This has been checked and it's not the problem. But thanks for suggestion.
If i get a new Note 4 on warranty i will probably sell it and get a Nexus phone, or install an clean ROM right away. Stock android is so much smoother than touchwiz.
Click to expand...
Click to collapse
Yeah, i don't know why the note 4s hard brick them selfs like that, must be a bug/glitch.
Seems like the store i bought it from has 2 years warranty. But in Norway we anyway have a 5 year "mini warranty" on electronics that is decided by law. So if the problem is not caused by mistreatment or water damage you should get it fixed for free within 5 years anyway.
Motherboard was faulty (as suspected)
Try to re-install a stock firmware (latest version) from sammobile with odin. This is the fast mode to revover your phone .

i need help with my newly acquired note 4. boot looping, lagging, shutting down

I need help!!!!!!!!!!!!!!! I bought a note 4 ATT from someone on ebay and the phone is in mint condition. I turned it on and played with it for a bit and it rebooted, then got really hot then lagged and rebooted. I tried checking for a software update and it tried downloading an att security update but the phone showed the little green android guy and said
downloading do not turn off target
could not do normal boot
ddi: mmc_read failed
odin mode high speed
smn910a
samsung official
system status custom
lock off
warranty void:0x0
some other stuff.
Then i reset it and it booted fine until i took a few pictures and it started boot looping. should i install the stock rom and how do i do this ?
kernel: 3.10.40-5613584
security patch: 7-1-16
android:5.1.1
knox 2.4.1
device:sm-n910a
joeynox said:
I need help!!!!!!!!!!!!!!! I bought a note 4 ATT from someone on ebay and the phone is in mint condition. I turned it on and played with it for a bit and it rebooted, then got really hot then lagged and rebooted. I tried checking for a software update and it tried downloading an att security update but the phone showed the little green android guy and said
downloading do not turn off target
could not do normal boot
ddi: mmc_read failed
odin mode high speed
smn910a
samsung official
system status custom
lock off
warranty void:0x0
some other stuff.
Then i reset it and it booted fine until i took a few pictures and it started boot looping. should i install the stock rom and how do i do this ?
kernel: 3.10.40-5613584
security patch: 7-1-16
android:5.1.1
knox 2.4.1
device:sm-n910a
Click to expand...
Click to collapse
Check this out
http://androidromupdate.com/2015/11...e-4-sm-n910a-official-android-5-1-1-firmware/
thank you ! im downloading the ap file now and will try flashing it . The guy i bought it from said he was his daily phone until he got the note 7 and all he did was factory reset it before it was shipped. The phone is mint condition so i dunno whats going on
joeynox said:
thank you ! im downloading the ap file now and will try flashing it . The guy i bought it from said he was his daily phone until he got the note 7 and all he did was factory reset it before it was shipped. The phone is mint condition so i dunno whats going on
Click to expand...
Click to collapse
If it's getting hot something its not happy. Usually gets hot when it's working hard.
That's what I found on mine anyways. Kind of like a fever. Something's wrong with your body it gets hot.
Same on a phone.
Usually happens to me when I flash something wrong.
Late nights, building something and maybe put files in the wrong spot, like app instead of priv-app. Or forget to put them in at all.
Good luck.
so i flashed a new stock rom and now the phone still occasionally gets hot but if i take 4-6 pictures with or without the flash the phone turns off and i have to pop the battery out to get it to turn back on. it seems to do this whe nthe battery is below 20%. im trying to test this now. When im unable to edit the accounts area, i get an error that says settings has stopped? last but not least theres no way to disable the shutter sound. Before i flashed the new stock rom there was an option.
try boot your phone without sd card.
Sorry to tell you this.
joeynox said:
I need help!!!!!!!!!!!!!!! I bought a note 4 ATT from someone on ebay and the phone is in mint condition. I turned it on and played with it for a bit and it rebooted, then got really hot then lagged and rebooted. I tried checking for a software update and it tried downloading an att security update but the phone showed the little green android guy and said
downloading do not turn off target
could not do normal boot
ddi: mmc_read failed
odin mode high speed
smn910a
samsung official
system status custom
lock off
warranty void:0x0
some other stuff.
Then i reset it and it booted fine until i took a few pictures and it started boot looping. should i install the stock rom and how do i do this ?
kernel: 3.10.40-5613584
security patch: 7-1-16
android:5.1.1
knox 2.4.1
device:sm-n910a
Click to expand...
Click to collapse
Unfortunately, you have fallen into a sinking boat like a lot of Note 4 owners. From what I can feel, the ddi: mmc read fail issue is actually a hardware problem, but which hardware is unknown. Many speculate a failing eMMC chip, others speculate power IC. But from what I have experienced and no matter what I did, I couldn't fix mine. I have the same issue and actually bought mine off of Swappa. From what I have heard and experienced, the phone runs it's best on stock rom, and a temporary fix is to install a wakelock app and set it to Mode 4, but this is only to stop phone from crashing during sleep, and won't fix it crashing and lagging during use. I would immediately arrange a refund or a PayPal dispute if I were you. I apologize that you got into this situation but no one has found a concrete fix. Best bet is to refund it. Best of luck on getting your money back.
DaKillaz98 said:
Unfortunately, you have fallen into a sinking boat like a lot of Note 4 owners. From what I can feel, the ddi: mmc read fail issue is actually a hardware problem, but which hardware is unknown. Many speculate a failing eMMC chip, others speculate power IC. But from what I have experienced and no matter what I did, I couldn't fix mine. I have the same issue and actually bought mine off of Swappa. From what I have heard and experienced, the phone runs it's best on stock rom, and a temporary fix is to install a wakelock app and set it to Mode 4, but this is only to stop phone from crashing during sleep, and won't fix it crashing and lagging during use. I would immediately arrange a refund or a PayPal dispute if I were you. I apologize that you got into this situation but no one has found a concrete fix. Best bet is to refund it. Best of luck on getting your money back.
Click to expand...
Click to collapse
I dunno what's wrong with this thing. Still cant access accounts due to settings stopping (only settings issue). The ddi mmc_read thing hasn't happened again but using the camera sometimes makes the phone turn off and sometimes its getting very hot. I hate to give it up because its in such good cosmetic condition., it looks brand new. I filed the claim with eBay and I also contacted the seller so I guess its a waiting game.
Could a bad battery cause the camera to turn the phone off or make the phone get hot and laggy?
joeynox said:
I dunno what's wrong with this thing. Still cant access accounts due to settings stopping (only settings issue). The ddi mmc_read thing hasn't happened again but using the camera sometimes makes the phone turn off and sometimes its getting very hot. I hate to give it up because its in such good cosmetic condition., it looks brand new. I filed the claim with eBay and I also contacted the seller so I guess its a waiting game.
Could a bad battery cause the camera to turn the phone off or make the phone get hot and laggy?
Click to expand...
Click to collapse
In my experience, the battery isn't a problem, I have bought multiple off of Amazon and they all had the same effect on the phone, nothing. If the phone is getting very hot, the system might be overworking the poor SnapDragon 805 to where it has to throttle or even shutdown, if Knox is already tripped, you might want to try CyanogenMod to single out TouchWiz being the laggy slow OS it is. If Knox isn't tripped, I don't recommend anything like that because the eBay seller can refuse refund if you trip Knox (At least in the US). In US, at least, you don't have to prove that the customer's modification actually damaged the device to refuse refund because of it. Camera can make phone turn off if the eMMC is the problem, as the camera creates a buffer on the storage to help speed up picture taking. If you have a settings issue however, you can always try reflashing the stock software on with ODIN and see if you just had a bad flash on the device. That won't trip Knox. Good luck with the refund, and as future advice, since Note 4's have started failing like crazy, The Note 4 might not be a safe thing to buy online anymore. Almost ready to go back and buy an S5 again.
Thanks for the advice. I can't get a new phone right now and since I'm on a budget my choices r limited. Lgg4 seems like its a huge headache with its contact failure so a used one of those is out of the question. I figures the note 4 would be the best option.
joeynox said:
Thanks for the advice. I can't get a new phone right now and since I'm on a budget my choices r limited. Lgg4 seems like its a huge headache with its contact failure so a used one of those is out of the question. I figures the note 4 would be the best option.
Click to expand...
Click to collapse
Yeah, I know how you feel, unfortunately, I bought mine off of Swappa, it started acting up, seller wanted me to pay shipping to send back, but I am on such a tight budget I couldn't. I decided to hold onto it anyways just in case something could fix it. If I were you, I know it's a bit smaller, but the S5 is a pretty good choice, I had bought a used T-Mobile S5 before my faulty Note 4 and it ran amazing. Plus, the used S5's are fairing quite a bit better than the Note 4's are. I had gotten a Note 4 because I was thinking, it's like an S5, but bigger and better, and with a pen. Too bad this hardware failure is letting people down now. I don't even know if you can't find them new either.
joeynox said:
Thanks for the advice. I can't get a new phone right now and since I'm on a budget my choices r limited. Lgg4 seems like its a huge headache with its contact failure so a used one of those is out of the question. I figures the note 4 would be the best option.
Click to expand...
Click to collapse
My advice is return the phone to the seller and buy nexus 6p or 5x both are great phones
Sent from my SM-N910G using Tapatalk
DaKillaz98 said:
In my experience, the battery isn't a problem, I have bought multiple off of Amazon and they all had the same effect on the phone, nothing. If the phone is getting very hot, the system might be overworking the poor SnapDragon 805 to where it has to throttle or even shutdown, if Knox is already tripped, you might want to try CyanogenMod to single out TouchWiz being the laggy slow OS it is. If Knox isn't tripped, I don't recommend anything like that because the eBay seller can refuse refund if you trip Knox (At least in the US). In US, at least, you don't have to prove that the customer's modification actually damaged the device to refuse refund because of it. Camera can make phone turn off if the eMMC is the problem, as the camera creates a buffer on the storage to help speed up picture taking. If you have a settings issue however, you can always try reflashing the stock software on with ODIN and see if you just had a bad flash on the device. That won't trip Knox. Good luck with the refund, and as future advice, since Note 4's have started failing like crazy, The Note 4 might not be a safe thing to buy online anymore. Almost ready to go back and buy an S5 again.
Click to expand...
Click to collapse
I'd go with flashing stock ROM again also. What I should have also added was, after flashing with ODIN, boot into recovery and do a factory reset. Obviously something in there is still jacked.
Either ODIN flash then do a factory reset, or do a factory reset then ODIN flash. Can't hurt, may help.
Perhaps flash TWRP and do an advance wipe also.
http://forum.xda-developers.com/note-4/development/twrp-2-8-1-2-recovery-note-4-sm-n910c-t2977933
dicksteele said:
I'd go with flashing stock ROM again also. What I should have also added was, after flashing with ODIN, boot into recovery and do a factory reset. Obviously something in there is still jacked.
Either ODIN flash then do a factory reset, or do a factory reset then ODIN flash. Can't hurt, may help.
Perhaps flash TWRP and do an advance wipe also.
http://forum.xda-developers.com/note-4/development/twrp-2-8-1-2-recovery-note-4-sm-n910c-t2977933
Click to expand...
Click to collapse
just wanted to update the post. I contacted the seller who said they would give me $75 back to have the phone repaired if theres an issue. She still is insisting the phone was fine when she had it. I said i would like a full refund so im waiting to hear back. But i did flash a stock rom and due a wipe. i also bought a new battery and so far the it hasnt gotten the ddi mmc read failure . it does seem to get warm quickly and while using a cpu process app my cpu is always bouncing between 10-30%.iv only downloaded 2 apps into the phone so far. 1 app still crashes after a while and the phone rebooted once after taking about 50 pictures with the flash. on the original battery it would lock up and shut down after 5 pictures, i would have to wait like 20 minutes to turn it back on. it sucks because i love the phone and really need it. i only paid $180 for it and i doubt ill be able to get a similar phone for that price. Ive read here that the ddi mmc read failure is a precursor to alot of hardware failures so now my heart is broken. Anyway thank you all for responding.
joeynox said:
just wanted to update the post. I contacted the seller who said they would give me $75 back to have the phone repaired if theres an issue. She still is insisting the phone was fine when she had it. I said i would like a full refund so im waiting to hear back. But i did flash a stock rom and due a wipe. i also bought a new battery and so far the it hasnt gotten the ddi mmc read failure . it does seem to get warm quickly and while using a cpu process app my cpu is always bouncing between 10-30%.iv only downloaded 2 apps into the phone so far. 1 app still crashes after a while and the phone rebooted once after taking about 50 pictures with the flash. on the original battery it would lock up and shut down after 5 pictures, i would have to wait like 20 minutes to turn it back on. it sucks because i love the phone and really need it. i only paid $180 for it and i doubt ill be able to get a similar phone for that price. Ive read here that the ddi mmc read failure is a precursor to alot of hardware failures so now my heart is broken. Anyway thank you all for responding.
Click to expand...
Click to collapse
That is a hell of a price. She must not have known how much to sell it for or there was a problem.

Vibration motor stopped

i've had the s7 Edge since launch. ive treated it like an egg on a spoon. never was in water, never dropped it. i've had a case on it at all times, and too many screen protectors to count on at all times. not cuz they broke, just cuz of the obvious TGSP never sitting right, then back n forth with Armorsuits, and IQ Shields, case friendly and non, etc. Anyway, last week, i noticed while typing it wasnt vibrating.
checked all my settings, they were fine
rebooted, shut down, over n over.... not it
went into service mode to check it. nothing showed failed
booted into safe mode incase of a rogue app, nada
last resort was a factory reset. also did squat.
very disappointed as i treated this phone so delicately being it is after all, made of glass.
and i did come from a long line of bootlooped LG G4's before jumping ship to Sammy.
So i had to RMA my phone. Samsung Smart Switch made the transfer relatively painless. but i hope in another 4 months, im not in the same boat again. im posting this because i couldnt find any other results with this issue, except over on reddit i saw a post about this with the regular S7. oh, and im on an AT&T variant, non rooted, fully updated just incase this thread develops.
rant over
Vibration motor are pretty rare to go, they usually get stuck, unless you have a lemon, which just happens to be the luck of the draw. They're relatively easy to replace if its out of warranty though, so not a big issue. You probably should had tried reflashing the phone before returning it. Just my 2 cent as a phone repairman.
WingedCow said:
Vibration motor are pretty rare to go, they usually get stuck, unless you have a lemon, which just happens to be the luck of the draw. They're relatively easy to replace if its out of warranty though, so not a big issue. You probably should had tried reflashing the phone before returning it. Just my 2 cent as a phone repairman.
Click to expand...
Click to collapse
this was the one thing i did not try. but i havent sent it back yet. just reflashed with odin, and guess what ? still doesnt work.
mixxxk said:
this was the one thing i did not try. but i havent sent it back yet. just reflashed with odin, and guess what ? still doesnt work.
Click to expand...
Click to collapse
Now you know you have a lemon for sure, send that back, its like 5 dollar to fix a vibrator but if its under warranty, get a new one.

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?

Phone Not Booting HELP

This morning I had to force reboot my phone because it froze. But it never rebooted. Here I am 11 hours later, and it still won't boot up. I've tried everything; charging it, and trying to boot into recovery mode. No luck. Can someone please help me out?! The carrier will not send it to essential due to the fact that I did a sim card swap, and that voided the warranty. (BTW that's the stupidest thing I've in my life) HELP!!
Thomas Cloutier said:
This morning I had to force reboot my phone because it froze. But it never rebooted. Here I am 11 hours later, and it still won't boot up. I've tried everything; charging it, and trying to boot into recovery mode. No luck. Can someone please help me out?! The carrier will not send it to essential due to the fact that I did a sim card swap, and that voided the warranty. (BTW that's the stupidest thing I've in my life) HELP!!
Click to expand...
Click to collapse
What firmware? Stock or custom rom?
garywojdan81 said:
What firmware? Stock or custom rom?
Click to expand...
Click to collapse
Latest stock firmware. Has been sent to essential for repair/ replacement. Would still be nice to know what else I could have done.
You held the power button down until the phone completely powered off? I'm assuming you did but just checking. If Essential is taking the phone for repair presumably they made sure you did all the obvious things first.
jhs39 said:
You held the power button down until the phone completely powered off? I'm assuming you did but just checking. If Essential is taking the phone for repair presumably they made sure you did all the obvious things first.
Click to expand...
Click to collapse
Yes I did everything the the girl on customer service told me to do. I'm wondering if maybe cause of it freezing had something to do with the ram?
Thomas Cloutier said:
This morning I had to force reboot my phone because it froze. But it never rebooted. Here I am 11 hours later, and it still won't boot up. I've tried everything; charging it, and trying to boot into recovery mode. No luck. Can someone please help me out?! The carrier will not send it to essential due to the fact that I did a sim card swap, and that voided the warranty. (BTW that's the stupidest thing I've in my life) HELP!!
Click to expand...
Click to collapse
First, where are you? Country that is? In the US that is not a valid reason to void a warranty if you have the receipt.
Also how long are you holding the power button?
In some cases you might have to attach the charger and hold the button for 30-45 seconds.
Does the charging light come on?
Hold all three buttons for about 30 seconds, this forces a hard reboot
Thomas Cloutier said:
Yes I did everything the the girl on customer service told me to do. I'm wondering if maybe cause of it freezing had something to do with the ram?
Click to expand...
Click to collapse
It could be caused by bad memory or a bad CPU. It's hard to say but if Essential customer support had you try different things they must think it's hardware failure. If you are in the US they aren't going to fix your phone and send it back to you. They're going to replace it with a refurbished phone. Hopefully they aren't like Google who more often than not sends customers refurbished phones that are defective when someone does an RMA. I haven't heard any similar horror stories about Essential so far. Essential also makes its own phones while Google uses an outside manufacturer so their situations are a bit different but owning two Google phones (Nexus 6P & Pixel XL) has made me wary where refurbished replacements are concerned. But Essential probably couldn't get away with what Google does without getting slammed in the tech press so you are likely pretty safe. Good luck.
jhs39 said:
It could be caused by bad memory or a bad CPU. It's hard to say but if Essential customer support had you try different things they must think it's hardware failure. If you are in the US they aren't going to fix your phone and send it back to you. They're going to replace it with a refurbished phone. Hopefully they aren't like Google who more often than not sends customers refurbished phones that are defective when someone does an RMA. I haven't heard any similar horror stories about Essential so far. Essential also makes its own phones while Google uses an outside manufacturer so their situations are a bit different but owning two Google phones (Nexus 6P & Pixel XL) has made me wary where refurbished replacements are concerned. But Essential probably couldn't get away with what Google does without getting slammed in the tech press so you are likely pretty safe. Good luck.
Click to expand...
Click to collapse
We'll see what they end up sending back next week, I'm I get a different phone, so I won't end up having the same issues. But then again I hope they can fix the issue on my phone

Categories

Resources