Database Develop

Is this bricked?

To start i have no experience with "bricked" phones and could only assume to identify one if it just didnt work, so i could be way off here. I met a fellow who owns a Nexus One and he is trying to sell it as it no longer works. He tells me that he was preforming a firmware update, the phone "crashed" so he yanked the battery and since then he is unable to power it up. Im looking for more specifics on this to see exactly what is happening when he tries to power on. Given this info is it likely that his phone is bricked, and if so is there any way to fix it? Im inclined to think no, but would appre iate the opinions of others just like to make sure as he has offered it to me for next to nil. Thanks for any help.
-------------------------------------
Sent via the XDA Tapatalk App

If he pulled the battery while flashing a radio image update, it is likely bricked.... but a bricked phone should power on to the static X initial boot image, and would stay there indefinitely.
Sounds like something else might be going on (battery dead/malfunctioning?), but I don't think it's officially "bricked" as much as "broken"

If it can't power on, I don't think there's any good in it
-------------------------------------
Sent via the XDA Tapatalk App

Power buttons have been known to fail on a number of Nexus Ones.... maybe it's a case that the button is broke...
Think if you pull the batt while usb powered and put batt back in it will power on...

Thanks for the speedy replies. Ill wait for further info from the guy to see exactly what is happening and post again if its significant. Thanks again
-------------------------------------
Sent via the XDA Tapatalk App

brunswick000 said:
To start i have no experience with "bricked" phones and could only assume to identify one if it just didnt work, so i could be way off here. I met a fellow who owns a Nexus One and he is trying to sell it as it no longer works. He tells me that he was preforming a firmware update, the phone "crashed" so he yanked the battery and since then he is unable to power it up. Im looking for more specifics on this to see exactly what is happening when he tries to power on. Given this info is it likely that his phone is bricked, and if so is there any way to fix it? Im inclined to think no, but would appre iate the opinions of others just like to make sure as he has offered it to me for next to nil. Thanks for any help.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
If it doesn't even power on, I would just warranty the phone and get a new one.

prettyboy85712 said:
If it doesn't even power on, I would just warranty the phone and get a new one.
Click to expand...
Click to collapse
Our warranties are non-transferable, so don't get yourself stuck in a hardplace.

wesbalmer said:
Our warranties are non-transferable, so don't get yourself stuck in a hardplace.
Click to expand...
Click to collapse
I was actually referring to the original owner.

wesbalmer said:
Our warranties are non-transferable, so don't get yourself stuck in a hardplace.
Click to expand...
Click to collapse
where did you learn that? that's not what htc told me..

[Q] Rooted htc one won't turn on

Last night I was watching youtube and my phone got really hot. It was really late so I just turned it off and went to bed. Today I woke up and my phone wouldn't turn on, it had almost a full charge when I turned it off. I plugged it in and there is no LED light(it's been plugged in for about 7 hours).I've tried holding power and volume down for a full minute and I've also tried turning it on while shining a bright light on it. Nothing happened. My phone seems to have a little heat(I think because its been plugged in for 7 hours) so I think the battery is getting power. I've had the phone for about 3 months now and it has been working fine but it is rooted so I don't think I could get much support from verizon/htc
I have no idea what to do

It's probably a mainboard problem. Take it to Verizon, tell them the story (minus the rooting) and hopefully they wont be able to tell if you unlocked it's bootloader or not.

Arjen_Arg said:
It's probably a mainboard problem. Take it to Verizon, tell them the story (minus the rooting) and hopefully they wont be able to tell if you unlocked it's bootloader or not.
Click to expand...
Click to collapse
I have a custom splash screen
plus the cyanogenmod boot animation

Can you actually get to see that on your current phone's state?

Arjen_Arg said:
Can you actually get to see that on your current phone's state?
Click to expand...
Click to collapse
no, there is no led light, it wont turn on

parcotics said:
no, there is no led light, it wont turn on
Click to expand...
Click to collapse
So how does it matter?
Do it over the phone, they usually don't care and the overnight you a new phone.

aooga said:
So how does it matter?
Do it over the phone, they usually don't care and the overnight you a new phone.
Click to expand...
Click to collapse
if they were to send my a new phone i would be required to send them my broken one
since it's rooted I would have to pay for the new device($200)

parcotics said:
if they were to send my a new phone i would be required to send them my broken one
since it's rooted I would have to pay for the new device($200)
Click to expand...
Click to collapse
Yes that's what I'm saying...they don't care. In store, they check, over the phone they just reset the device without even checking.
Sent from my Nexus 7 using Tapatalk
---------- Post added at 04:27 PM ---------- Previous post was at 04:25 PM ----------
parcotics said:
if they were to send my a new phone i would be required to send them my broken one
since it's rooted I would have to pay for the new device($200)
Click to expand...
Click to collapse
If it doesn't turn on, how are they supposed to check if its rooted or not.
Edit: I didn't mean it as a question, I'm saying that it isn't possible.
Sent from my Nexus 7 using Tapatalk

aooga said:
Yes that's what I'm saying...they don't care. In store, they check, over the phone they just reset the device without even checking.
Sent from my Nexus 7 using Tapatalk
---------- Post added at 04:27 PM ---------- Previous post was at 04:25 PM ----------
If it doesn't turn on, how are they supposed to check if its rooted or not.
Edit: I didn't mean it as a question, I'm saying that it isn't possible.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Have you done this before?

parcotics said:
Have you done this before?
Click to expand...
Click to collapse
Yeah, once, but I knew that rooting couldn't have fried it. If it doesn't turn on at all, they physically can NOT check if its rooted. As always though. I'm not responsible for what you do.
Sent from my Nexus 7 using Tapatalk

aooga said:
Yeah, once, but I knew that rooting couldn't have fried it. If it doesn't turn on at all, they physically can NOT check if its rooted. As always though. I'm not responsible for what you do.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
what I'm worried about is the red text that would appear while turning on my phone
something along the lines of "do not distribute...legal actions may be taken", i think it had to do with being s-off
if some how they managed to turn on the phone, i don't want them seeing that

parcotics said:
what I'm worried about is the red text that would appear while turning on my phone
something along the lines of "do not distribute...legal actions may be taken", i think it had to do with being s-off
if some how they managed to turn on the phone, i don't want them seeing that
Click to expand...
Click to collapse
There really is no other option for you. If it doesn't turn on, they won't try for hours to get it back on..they'll say its defective and send it back to htc.
Sent from my Nexus 7 using Tapatalk

aooga said:
There really is no other option for you. If it doesn't turn on, they won't try for hours to get it back on..they'll say its defective and send it back to htc.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Here is a question, when you make your phone s-off, is that information stored on internal storage or the sd card?

parcotics said:
Here is a question, when you make your phone s-off, is that information stored on internal storage or the sd card?
Click to expand...
Click to collapse
What information. The htc one doesn't even have an sdcard so I'm not sure what you're asking.

aooga said:
What information. The htc one doesn't even have an sdcard so I'm not sure what you're asking.
Click to expand...
Click to collapse
ok well thanks for your help, I think I'll tinker around with it a little bit before I try to send it in

Wife's Note 3 shows "custom" at bottom?

I never noticed this but couple days ago, my wife's note 3 started to lock up constantly throughout the day. I told her these things happen sometimes and to just take the battery out, and put it back in and let it restart. When she did this, I realized under the SAMSUNG on bootup, there was an unlocked padlock with the wording CUSTOM under it. I was shocked and confused how this can be...
I asked her about it, and she said it's been like that since we got the phones. She remembers at the AT&T store that the seal was broken off by the salesman, so there is no way it was a returned phone.
What gives? ATT is going to give her a refurb phone, but she's very mad because we've had the phone for 2 months and had no idea she had an unlocked phone, and she shouldn't be penalized for getting a 'used' phone.
They told her that it was the nova launcher that is causing the issues, becuase it's an unofficial app. these people....
I told her maybe she got lucky and got a dev phone (too bad dev phone keeps locking up lol)
any ideas on this?

try running the "root checker" app on it. Mine showed it after I first flashed it.
Sent from my SM-N900T using Tapatalk

They are stupid. It's not Nova.
I highly doubt it is a dev phone... But if it is, I would love to see the model number of the device and system info. Would you be willing to post that info?
Sent from my SAMSUNG-SM-N9005A using XDA Premium 4 mobile app

graydiggy said:
They are stupid. It's not Nova.
I highly doubt it is a dev phone... But if it is, I would love to see the model number of the device and system info. Would you be willing to post that info?
Sent from my SAMSUNG-SM-N9005A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
sure, i will try to get it to you guys.

This is hilarious, I installed nova before I root my phone, and there was no custom and pad lock when reboot, the custom and pad lock only showed up after I rooted my phone, the custom and pad lock had remained on the screen even I unroot the phone. I think your wife got a returned phone.

It still had all the seals on it!!!

here are the pictures. she got a replacement phone, and that is messed up too. the screen fails to turn on. everytime you press ON, the phone vibrates, but nothing from screen. She said after she took battery out etc, THAT phone ended up with the custom logo at bottom too. I have no idea what she's doing to these phones!!!!

I thought the custom only happened when you rooted it and placed safestrap or a recovery on them.

Looks normal to me.its not a developer edition.
I am curious as to why it is throwing this Custom status when it isn't.
I assume both are complete stock. no root, etc.
Sent from my SM-N9005 using XDA Premium 4 mobile app

razorseal said:
here are the pictures. she got a replacement phone, and that is messed up too. the screen fails to turn on. everytime you press ON, the phone vibrates, but nothing from screen. She said after she took battery out etc, THAT phone ended up with the custom logo at bottom too. I have no idea what she's doing to these phones!!!!
Click to expand...
Click to collapse
i would use the return to MJ5 stock thread and flash the odin MJ5, then the MI9 fix and then the proper Mj5 files again and see if that clears up the issue. something seems to be lingering in the system that gives it the "custom" status.

coolmingli said:
This is hilarious, I installed nova before I root my phone, and there was no custom and pad lock when reboot, the custom and pad lock only showed up after I rooted my phone, the custom and pad lock had remained on the screen even I unroot the phone. I think your wife got a returned phone.
Click to expand...
Click to collapse
graydiggy said:
Looks normal to me.its not a developer edition.
I am curious as to why it is throwing this Custom status when it isn't.
I assume both are complete stock. no root, etc.
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
the2rrell said:
i would use the return to MJ5 stock thread and flash the odin MJ5, then the MI9 fix and then the proper Mj5 files again and see if that clears up the issue. something seems to be lingering in the system that gives it the "custom" status.
Click to expand...
Click to collapse
I might have to do that, but what a hassle. this woman just wants to use her phone! Might do a factory reset for her, see how that works out..
coolmingli said:
This is hilarious, I installed nova before I root my phone, and there was no custom and pad lock when reboot, the custom and pad lock only showed up after I rooted my phone, the custom and pad lock had remained on the screen even I unroot the phone. I think your wife got a returned phone.
Click to expand...
Click to collapse
graydiggy said:
Looks normal to me.its not a developer edition.
I am curious as to why it is throwing this Custom status when it isn't.
I assume both are complete stock. no root, etc.
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
100% stock. she wouldn't know a thing about root.

razorseal said:
I might have to do that, but what a hassle. this woman just wants to use her phone! Might do a factory reset for her, see how that works out..
100% stock. she wouldn't know a thing about root.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2559715
here is the link to the Back to MJ5 stock thread, in all honesty once you get the files downloaded it only takes about 20 min to have the phone booting back up to stock MJ5 "WithOut ROOT" i just did this about 2 weeks ago. it DID get rid of the "custom" status and recovered my brick at the same time.
def worth trying!!!

You can root with kingo and use triangle away to remove the custom status.
As far as the other issues, a factory reset might help but a restore will be more likely to get rid of everything causing problems
Sent from my SM-N9005 using XDA Premium 4 mobile app

My first note 3 did that too, a few days before it went into bootloops. Something was wrong with it. Att swapped it as it was within the first 2 weeks.
Swap it out is my suggestion, If you still can. It may start going wrong one day.
Sent from my SAMSUNG-SM-N900A using xda app-developers app

WHat I might do is, go to the ATT store with BOTH phones, and show them how this one keeps locking up (well I can't show that probably as it's random) but I can show the custom thing.
then I can show the refurbished phone that I just received and how the screen fails to turn on.
hopefully the corp store can get the idea, and give me a new phone or something

razorseal said:
WHat I might do is, go to the ATT store with BOTH phones, and show them how this one keeps locking up (well I can't show that probably as it's random) but I can show the custom thing.
then I can show the refurbished phone that I just received and how the screen fails to turn on.
hopefully the corp store can get the idea, and give me a new phone or something
Click to expand...
Click to collapse
OH CRAP NO!!!!
if they SEE the custom status, they will not even deal with you unless you get a really cool rep. They instantly think that you tried to ROOT the phone and that is why you have ANY ISSUE you are talking about. i would not bring that phone into the store looking like that bruh.
the custom status is a symbol for root/modded phones. just do the stock restore, and IF at that point you want to take it back go for it. at least you will not have the custom lock screen going against you.

the2rrell said:
OH CRAP NO!!!!
if they SEE the custom status, they will not even deal with you unless you get a really cool rep. They instantly think that you tried to ROOT the phone and that is why you have ANY ISSUE you are talking about. i would not bring that phone into the store looking like that bruh.
the custom status is a symbol for root/modded phones. just do the stock restore, and IF at that point you want to take it back go for it. at least you will not have the custom lock screen going against you.
Click to expand...
Click to collapse
The point is not how to get rid of the custom logo, the point is why OP's wife brand new Note 3 sealed in the box has the logo, ATT should exchange it with a new phone not an refurbished.

coolmingli said:
The point is not how to get rid of the custom logo, the point is why OP's wife brand new Note 3 sealed in the box has the logo, ATT should exchange it with a new phone not an refurbished.
Click to expand...
Click to collapse
i feel that, but what you are saying is that you want ATT ( big brother so to speak ) to admit that sent him a modded phone? WONT HAPPEN!!!
they will accuse her/him of tinkering and that is what caused the custom logo. even IF it came that way. i dont see them eating that blame as im sure they have quality control and procedures in place that should catch that kind of slip. and if it did slip through....you expect them to say yep your right we screwed up.
things happen, but i dont see them being ok with that....lol

I did be real mad if I bought the phone contract or not only found out it's been tempered.

coolmingli said:
I did be real mad if I bought the phone contract or not only found out it's been tempered.
Click to expand...
Click to collapse
i would too, but being mad will not change there view of a custom phone. best you can do is either fix it yourself ( stock odin packages ).
Orrr go into the store and HOPE you get a rep that doesnt know what the CUSTOM logo means.

HELP! My Phone is Dead!

After about a month of being rooted I decided to flash a custom rom, so I flash twrp then my custom rom which happened to be the wrong one because it was a bacon rom and I have a shamu phone so the flash didnt work (wish instructions would have made that more clear.) So after the first fail I flashed the CM12 updater zip thinking that would help but it didnt. So I go to restore my backup image, it was successful! After a successful restore I hit reboot to reboot my phone and from their it never came back up. My phone is dead as can be, no signs of life not a light or anything comes on. If their anything I can do or am I doomed. I do have insurance so I can get another phone, thats after a $200 deposit of course

With the phone off, what happens if you press and HOLD the lower volume key and the power button?

Ghetto Geeksta said:
After about a month of being rooted I decided to flash a custom rom, so I flash twrp then my custom rom which happened to be the wrong one because it was a bacon rom and I have a shamu phone so the flash didnt work (wish instructions would have made that more clear.) So after the first fail I flashed the CM12 updater zip thinking that would help but it didnt. So I go to restore my backup image, it was successful! After a successful restore I hit reboot to reboot my phone and from their it never came back up. My phone is dead as can be, no signs of life not a light or anything comes on. If their anything I can do or am I doomed. I do have insurance so I can get another phone, thats after a $200 deposit of course
Click to expand...
Click to collapse
download any rom via your computer, and gapps. then boot into your recovery and adb push them to your phone. be sure its a nexus 6 rom, as thats all a nexus 6 can flash. or, boot into your bootloader and flash the factory img via fastboot.
generally, you shouldnt mod your phone until you learn all the basics about modding your phone.

kelmar13 said:
With the phone off, what happens if you press and HOLD the lower volume key and the power button?
Click to expand...
Click to collapse
Absolutely nothing

simms22 said:
download any rom via your computer, and gapps. then boot into your recovery and adb push them to your phone. be sure its a nexus 6 rom, as thats all a nexus 6 can flash. or, boot into your bootloader and flash the factory img via fastboot.
generally, you shouldnt mod your phone until you learn all the basics about modding your phone.
Click to expand...
Click to collapse
Cant boot into recovery mode, no power at all.

I believe my phone is bricked

Just a quick question... the phone isn't flat out of battery, is it?

Ghetto Geeksta said:
I believe my phone is bricked
Click to expand...
Click to collapse
nothing at all?
try plugging it in. let it sit for a minute. then press the power button, and keep pressing it for 20-30 seconds. then let go and press it normally. if nothing, then its dead
maybe the battery died?
---------- Post added at 10:35 PM ---------- Previous post was at 10:34 PM ----------
machNex said:
Just a quick question... the phone isn't flat out of battery, is it?
Click to expand...
Click to collapse
its possible.

This happened to me. As hard as it was, I plugged it in and went to sleep. In the morning I could boot into bootloader, and I flashed stock firmware. I had to flash each file separately, as the flash-all file wouldn't work.
Sent from my Nexus 6

Thanks for the suggestions guys but I think my phone is dead to the water, had it on the charger for 6hrs and still nothing. Well its back to my tried and true Note 2 til I can afford $200 for a new phone :crying:

Why would you go through insurance when you have manufacturer warranty?... Unless you bought it second hand

Bought it through ATT Next Plan, does the manufacturer warranty still hold up?

Ghetto Geeksta said:
Bought it through ATT Next Plan, does the manufacturer warranty still hold up?
Click to expand...
Click to collapse
yes, but through motorola, not google in this case.

Ghetto Geeksta said:
After about a month of being rooted I decided to flash a custom rom, so I flash twrp then my custom rom which happened to be the wrong one because it was a bacon rom and I have a shamu phone so the flash didnt work (wish instructions would have made that more clear.) So after the first fail I flashed the CM12 updater zip thinking that would help but it didnt. So I go to restore my backup image, it was successful! After a successful restore I hit reboot to reboot my phone and from their it never came back up. My phone is dead as can be, no signs of life not a light or anything comes on. If their anything I can do or am I doomed. I do have insurance so I can get another phone, thats after a $200 deposit of course
Click to expand...
Click to collapse
I could see the phone not booting but not starting to at least get into bootloader, That seems strange to me . Is there and you did you didn't include in your OP ?

simms22 said:
yes, but through motorola, not google in this case.
Click to expand...
Click to collapse
Ill give Motorola a call tomorrow, I guess the good news is that since its completely dead they cant prove it was my fault.

call ASAP
Ghetto Geeksta said:
Ill give Motorola a call tomorrow, I guess the good news is that since its completely dead they cant prove it was my fault.
Click to expand...
Click to collapse
They bro the same happened to me im pretty sure I installed something that was
Not for the shamu bamm bricked my phone there was nothing I could do
It was completely dead I think it was the cm updater idk but I tried everything
After that decided to call Motorola and here I am writing all of these
From my new nexus 6 oh they also have me the 64 gigs yea lucky me
,I really love Motorola they really stand behind their products at least
For me I didn't pay anything 2 days after I called I had my new phone in the mail box
Of course I have a security deposit so I can have the phone faster
Then when I get my me phone I send then the bad one and then
They have me back my money from the deposit call them ASAP you might
Also get lucky and get a64 one tell them you was watching aa movie
And all of a sudden it just died on you and never came back. Any questions I'm here

darryim said:
Also get lucky and get a64 one tell them you was watching aa movie
And all of a sudden it just died on you and never came back. Any questions I'm here
Click to expand...
Click to collapse
So, what you are saying, is that he/she should commit insurance fraud? Man, look if you don't know what you are doing and brick/destroy your phone that is on you. Pay the money for a new one and learn your lesson. All you are doing is making RMA processes more and more difficult because of cheats like you. OP is to blame here if he/she flashed a ROM made for a different phone, that's on them not the MFG, Motorola.

Circaflex said:
So, what you are saying, is that he/she should commit insurance fraud? Man, look if you don't know what you are doing and brick/destroy your phone that is on you. Pay the money for a new one and learn your lesson. All you are doing is making RMA processes more and more difficult because of cheats like you. OP is to blame here if he/she flashed a ROM made for a different phone, that's on them not the MFG, Motorola.
Click to expand...
Click to collapse
absolutely disagree with you.
manufacturers must make phones that will not be so easy breakable.
thanks for sharing your problem,
now again I'm confirmed that CM is sucks as always it was and should not even try it.

x111 said:
absolutely disagree with you.
manufacturers must make phones that will not be so easy breakable.
thanks for sharing your problem,
now again I'm confirmed that CM is sucks as always it was and should not even try it.
Click to expand...
Click to collapse
He is right. People understand that you void your warranty when you flash your device. XDA doesnt condone fraud in any way shape or form. If you brick your device because you were messing with it then you accept it and buy a new one. Why do you think just about every rom thread tells you that you have now voided your warranty. Flashing your device is not something that should be taken lightly or done because it is cool.

so?
zelendel said:
He is right. People understand that you void your warranty when you flash your device. XDA doesnt condone fraud in any way shape or form. If you brick your device because you were messing with it then you accept it and buy a new one. Why do you think just about every rom thread tells you that you have now voided your warranty. Flashing your device is not something that should be taken lightly or done because it is cool.
Click to expand...
Click to collapse
So is OK for them to sell phones to us that are defective? Anyway my phone had the
Screen burning and also the
Pink color issue when you lower the brightness I didn't fell like returning it because I had
Already set everything up the way I like it . so just like us they also have to face
The consequences which they do pretty good for me and should do for everyone we are
Taking about a 700 hundred dollars phone here not a 100 dollars phone ,I would like to see.
Those who are taking crap saying to buy another phone if they were in my shoes
I'm pretty sure they would have done the same so stop with that bs . return that phone get your new one end of story thanks.

Frustrated with Note 4

So, I've been using this wonderful device for a while now, since early October. I've finally got it set up the way I like it and all. Now, I'm just flashing ROMs to see which I prefer. Just a few hours ago, I decided to revert to the T-Mobile ANK3 (or AN-whatever) stock ROM because on Lollipop 5.0.1+ the battery dies much quicker than I'd like it to. Yet, that ROM would constantly either:
A) Die whenever it wanted to
B) Freeze and just not respond
C) Require a battery pull
D) Send me to D/L mode with "mmc_read fail".
So I decided to revert back to stock 5.0.1 because I was tired of all the bugs I was encountering with 4.4.4.
Now, every hour or so, the phone dies and gets stuck on the splash screen (with the obvious SEAndroid not enforcing + Set Warranty Bit). Or if it isn't that, the phone just outright freezes when I'm using a light application (i.e. Kik Messenger).
I'm starting to think that my eMMC is dying, because the phone was not acting like this when I first got it in early October. Every once in a while D/L mode keeps repeating my fears. I cannot send it in to Samsung because I already voided my warranty, and I am a prepaid subscriber on T-Mobile. (So, no, T-Mobile will not help me, likely.)
Any ideas on what's happening, or what I should do?

First thing I would do Is flash a different kernel

Odin back to stock and reroot the device. Sounds like something got messed up.
Sent from my SM-N910T using XDA Free mobile app

ShrekOpher said:
Odin back to stock and reroot the device. Sounds like something got messed up.
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
Did that, ended up having the same problems. I said screw it, and am now using CM12.1...
Although I really don't like it (because TW is now a good thing as opposed as to how bad it was on the S3), I'll settle with it. It's not so bad.
---
LMAO OOOOO I LIED TO MYSELF
even CM is force rebooting itself wwwwhat

Why can't u take it in for warranty? Out of warranty they just replaced my note 4 under warranty and it was rooted

sqmala4321 said:
Why can't u take it in for warranty? Out of warranty they just replaced my note 4 under warranty and it was rooted
Click to expand...
Click to collapse
I bought the phone second hand, and it is out of warranty. I can't fork over money right now, as seeing how replacing the eMMC chip is probably expensive. I'll probably find some hackjob way of finding a replacement, or just live with it. I also don't think reflashing the bootloader will help.
Each time I power on the phone, it seems that it keeps getting worse each time. I get the "ddi: mmc_read fail" message more often, and off a cold boot, the phone will not actually boot and I have to battery pull like 2 times before it actually boots. Gee, looks like I'm screwed.

Good news...since they know that the eMMC chip is bugging out, they'll do a free repair. Success! Now, time to go into the repair shop and hope they accept my reference ticket, since I'll be a walk in.
I can't call right now, seeing as my phone has difficulty doing ANYTHING now...

eduardog131 said:
I bought the phone second hand, and it is out of warranty. I can't fork over money right now, as seeing how replacing the eMMC chip is probably expensive. I'll probably find some hackjob way of finding a replacement, or just live with it. I also don't think reflashing the bootloader will help.
Each time I power on the phone, it seems that it keeps getting worse each time. I get the "ddi: mmc_read fail" message more often, and off a cold boot, the phone will not actually boot and I have to battery pull like 2 times before it actually boots. Gee, looks like I'm screwed.
Click to expand...
Click to collapse
actually i am having the same exact problem....i had the tmobile note 4, and its doing the same thing about 1 month ago...reboots, black screens; and all that you have mentioned. so i started to look into rooting/flashing tekxodus hd onto my phone...still the same problem...phones restarts to boot loop time to time...bad screens....i'm still trying to find outwhat the hack is going on...and the phone's warranty expireds about 1 month ago right before the phone start to act up....let me know if you find a solution to that..lol...thanks:good:
---------- Post added at 11:25 PM ---------- Previous post was at 11:17 PM ----------
ShrekOpher said:
Odin back to stock and reroot the device. Sounds like something got messed up.
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
yes, i did that too...odin back to stock, still same problem...my phone was on stock when these problems started. i hoping different roms would solve the problem...so i started rooting and intalled tedxodus and the same problems...hopefully someone could help please.