Does anybody knows how to fix the Sleep of Death? - Galaxy Tab 10.1 General

So here's the story, bought my Galaxy 10.1 7 days ago, It was working perfectly, I turned it off, and plugged for a nice charge... a couple of hours later..
I tried to turn it on.. and nothing..
So far I have tried:
Holding the power button for several minutes with the tab plugged did not woked.
Holding the power button for several minutes with the tab un-plugged did not woked.
Holded PWR+Volume Down
I connected the tab to my pc and the USB detects that there's something there but nothing else..
is there anyway to use adb or fastboot to kick the thing out?
Please help
Sorry if double posted but I'm going nuts with this problem

Pwr button alone for 15 sec kicked my tab over every time I've locked it, and I'm screwin with pershoots kernel and overclock
lbrenes said:
So here's the story, bought my Galaxy 10.1 7 days ago, It was working perfectly, I turned it off, and plugged for a nice charge... a couple of hours later..
I tried to turn it on.. and nothing..
So far I have tried:
Holding the power button for several minutes with the tab plugged did not woked.
Holding the power button for several minutes with the tab un-plugged did not woked.
Holded PWR+Volume Down
I connected the tab to my pc and the USB detects that there's something there but nothing else..
is there anyway to use adb or fastboot to kick the thing out?
Please help
Sorry if double posted but I'm going nuts with this problem
Click to expand...
Click to collapse
Sent from my SPH-D700 using XDA Premium App

Have same problem, exactly as yours dont know what to do. Should send it to support but i live abroad so im fuc...

condorazul said:
Have same problem, exactly as yours dont know what to do. Should send it to support but i live abroad so im fuc...
Click to expand...
Click to collapse
I have exactly the same problem I live in Costa Rica and now I need to send it to USA, and it is going to be very expensive...
Mine is not coming up with any button combination at all...

can't you simply let it deplete his charge using headphones or so?

dcc22 said:
can't you simply let it deplete his charge using headphones or so?
Click to expand...
Click to collapse
Don't know what do you mean by this... the tablet is not even turning on... how am I going to discharge it?

I Will try to reflash it if finally dont manage to send it to USA. I've been reading some post and the drivers it need are available to download, but the firmware has not been released yet, none the less I will charge all the tab to my home insurance cos it seems to be an electric failure.
If someone gets the solution please help us

condorazul said:
I Will try to reflash it if finally dont manage to send it to USA. I've been reading some post and the drivers it need are available to download, but the firmware has not been released yet, none the less I will charge all the tab to my home insurance cos it seems to be an electric failure.
If someone gets the solution please help us
Click to expand...
Click to collapse
Can you share those posts? how can it be flashed in this state?

I've read some Post about passing the information through cmd in windows but I would have to read it again, think it was in nvidia developers or something similar, I guess that if the Pc recognizes the apx something can be done but I'm not an expert and this is my first and Perhaps last android tablet. I'll take a look and told you if I find something

I have the same problem. Bought the tab on Friday in the US and then returned home to the UK. It died last night - 2 days later.
Samsung technical support said it would need to be returned to a service centre. UK service centers can't deal with it as the tab isn't out here yet.
I have called Samsung US this evening and spoke to a very helpful guy who said I can send it back to the us to be fixed under warranty, but will have to pay to ship it there and for them to ship it back to me.
Unfortunately samsung's systems can't cope with my uk address so I will have to speak to the warranty company company direct - who are closed today as it's 4th July.
As a final point - I also spoke to best buy - to see if I could return it to them. As I bought it in store, I have to return it to store. Bunch of ............
Sent from my GT-I9000 using XDA App

tmbk said:
I have the same problem. Bought the tab on Friday in the US and then returned home to the UK. It died last night - 2 days later.
Samsung technical support said it would need to be returned to a service centre. UK service centers can't deal with it as the tab isn't out here yet.
I have called Samsung US this evening and spoke to a very helpful guy who said I can send it back to the us to be fixed under warranty, but will have to pay to ship it there and for them to ship it back to me.
Unfortunately samsung's systems can't cope with my uk address so I will have to speak to the warranty company company direct - who are closed today as it's 4th July.
As a final point - I also spoke to best buy - to see if I could return it to them. As I bought it in store, I have to return it to store. Bunch of ............
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Yeap same here, I will be sending mine on wednesday if I cannot find a resolution on my own, I spoke to best buy as well and we have 14 days to get an exchange for a new one..
Just one question to all is anybody using the Invisi shield on your tab?

Here us the place where I read it it's inthat forum
http://forum.xda-developers.com/showthread.php?t=1130574
Think they are speaking about our problem

So if you send it to best buy they change it, but my problem is that my fifteen day will expire on the deliver, tomorrow I will try the solution posted before and see if it works, nothing to loose

condorazul said:
So if you send it to best buy they change it, but my problem is that my fifteen day will expire on the deliver, tomorrow I will try the solution posted before and see if it works, nothing to loose
Click to expand...
Click to collapse
Official policy is that if it was bought in store it has to be returned to store you got it from. The lady on customer services said some managers will accept returns by post but at their discretion. I got one that chose not to!
Sent from my GT-I9000 using XDA App

power button for about 10 seconds reboots for me (stock everything)

joebob1 said:
power button for about 10 seconds reboots for me (stock everything)
Click to expand...
Click to collapse
Lucky you... I was able to access my tab with nvflash and I think the problem is that my bootloader is broken
C:\nvflash>nvflash --bl bootloader.bin --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x037c704641bff4d7
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
download command failed NvError 0x120002
command failure: bootloader download failed (bad data)
bootloader status: Bct file not found (code: 21) message: flags: 1073840124
So if someone knows how to fix that It might bring the tab back up

same problem in mine lets wait for some illuminate to fix it

lbrenes said:
Lucky you... I was able to access my tab with nvflash and I think the problem is that my bootloader is broken
C:\nvflash>nvflash --bl bootloader.bin --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x037c704641bff4d7
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
download command failed NvError 0x120002
command failure: bootloader download failed (bad data)
bootloader status: Bct file not found (code: 21) message: flags: 1073840124
So if someone knows how to fix that It might bring the tab back up
Click to expand...
Click to collapse
can you get into odin or no?

I have also been able to access via nvflash. Tried Odin 1.3, 1.7 and 1.8 (might have been 1.83) and none detect it.
Sent from my GT-I9000 using XDA App

ericc191 said:
can you get into odin or no?
Click to expand...
Click to collapse
In this state it is impossible to get in to DOWNLOAD mode,and for what I have read the Tab is only flashable with a special service cable so I guess unless we get a very skilled Dev to find a workaround our only option is to return them

Related

dead O2 xda problem

I've a feeling this is a back to shop job but I thought I'd check with you guys first
I've had my exec for a couple of years now and I'm extremely happy with it, I've installed flash, along with some of the standard apps, synced with my PC regularly and generally used it without incident, it's very definitely out of warranty
I had some PDF's I wanted to look at on it so I got my supplied apps disk and decided to put the clearvue pdf viewer on it, connected the xda to my PC, synced, and ran the install from the PC, it got all the way through to the final success screen then activesync locked and the xda locked
I disconnected the xda and rebooted the PC which was fine
I had to take the battery out of the xda before it would do anything, then on power on I got to the splash screen with the radio and rom versions and it stopped
I tried a soft reset followed by a hard reset but still got stuck on the splash screen
I phoned O2 who said take it to the shop
I looked on here and followed instructions to get onto the bootloader with mtty
now the "task 28" command returned
DOCInfoTableinitHW+
Binary0 Size: 0x100000
FAT0 Size: 0x4000000
FAT1 Size: 0xA00000
FAT2 Size: 0x2900000
All Size: 0x7400000
FAT0_ADDR=0x100000,FAT1_ADDR=0x4100000,FAT2_ADDR=0x4B00000
which didn't match the example in the wiki which had these differences
FAT2 Size: 0x2C70000
All Size: 0x7770000
which is a difference of around 3.5 Mb on FAT2 (which I'm guessing is set up to look like a FAT partition and it's pretending to be a disk drive)
now I'm thinking if it thinks the flash size is wrong then I've probably lost a chip and as I'm guessing from the above that it's set up to look like a disk drive losing a chunk has corrupted the disk and I can't read it any more hence the hang
is it worth me trying a reflash with standard roms or is my idea of a chip failure the right one and taking it back to the shop is the only way to go
------
additional info
now I don't even get to a splash screen and pressing the two softkeys brings up the hard reset menu without having to press the reset button as well, I've tried all the fixes for being stuck in the bootloader with no joy
I say, try the official ROM or one of the better ROMs on here, what have you got to lose? Make sure you know the process and go for it.
Don't forget to update us on whether it solved the problem
Best of luck.
Try typing "task 28 55aa" in MTTY.
enigma1nz said:
I say, try the official ROM or one of the better ROMs on here, what have you got to lose? Make sure you know the process and go for it.
Don't forget to update us on whether it solved the problem
Best of luck.
Click to expand...
Click to collapse
I'm going to find out what an official repair would cost first of it's too much then I'll have it back and try the reflash option, cheers
igord said:
Try typing "task 28 55aa" in MTTY.
Click to expand...
Click to collapse
Done that and I get the same table as above, and also tried "set 14 0" to get it out of the bootloader with no success
and failing all of this it looks like ebay may be a way to go
Hi esme! Wouldn't you consider selling the dead UNI?
kestabacsi said:
Hi esme! Wouldn't you consider selling the dead UNI?
Click to expand...
Click to collapse
well I'm still hopeful of having it repaired or reflashing it myself, it's the best phone/pda I've ever had and I want it to work again, but if it turns out to be beyond O2 and my ability to fix then I'll probably be looking to sell it for spares, so I can finance another off ebay
quick update on this
a week ago I wandered into the O2 shop handed over my dead phone plus some "looking at" money and it was sent off to be "looked at"
I eagerly awaited the call back saying it was going to cost several limbs to fix and could I come in for the amputation but it never came
today the shop called saying it's been "looked at" and sent back to the shop, could I pick it up sometime
"it's working ?" I said
"apparently" they said
"but they were supposed to call me and tell me how much before doing a repair" I said
"there's no further charge" they said
a few moments later whan I came to I said "huh ? wha ?" or something equally erudite and urbane
they said "no charge" rustling of paperwork "... nope no charge"
"and it works? and I'm not on some cruel reality TV show and you are just playing with my emotions to get a cheap laugh ?" I interjected
"according to this paperwork yep, dunno about the reality show but no I'm not playing with your emotions, so it's here when you want it" the man patiently explained
"erm ..... ok, see you soon"
so I'm off to town tomorrow to see if it's really true
.... I'm not going to sleep a wink tonight am I
my god ..... it's full of stars ....
she's alive! I have my arm back, I can do things
so to all the kind people offering to purchase my phone while it was bricked, thank you for your interest but I don't think I'll be selling it now
so a quick hard reset to get rid of the O2 add ons and I'm good to go
thanks for the advice guys

Update Statement on B7O root

http://androidroot.mobi/2011/10/03/no-we-havent-given-up-or-yet-another-post-about-the-current-state/
No, we haven’t given up or: Yet another post about the current state ....... by rayman
Hi, been a while since our last post…
Rumors are starting to surface that indicates that we have given up on working on this. This is by no means the case. We are still hard at work. Things are definitely taking longer than expected.
There is one main issue:
The BootROM in B70+ devices has been bumped to a newer revision. Nvflash works by sending a miniloader to the device, which then handles receiving the actual bootloader.bin. The miniloader included in current nvflash binaries appears to crash well before the bootloader.bin is sent.
So, how do we move on? Well, I hate to say it, but I really need to get my hands on a new SBK device (B70 or B80). Bricked is OK. As long as APX mode works over USB, it’s ok. Heck, even a broken screen is OK.
Requirements:
Cheap
APX Mode works
Within EU
Can charge ok
Cheap
There’s no requirement that any accessories are included. I already have a B50 TF with working charger.
perhaps this will help you?
http://forum.xda-developers.com/showpost.php?p=18054125&postcount=1
Thanks, but I am just re-posting rayman's post from over at androidroot.mobi. He seems to be taking the lead in cracking the new locked bootloader.

[Q] Does asus rma know about root/roms/unlock

So I sent my tab to asus because it went into apx mode and would not come out. I've been reading asus unlock tools send asus servers info about the fact that a device was just unlocked including serial number. I'm wondering if they will know as my tab was completely dead. Also I sent it in a week ago and there online rma tracker has not updated at all. Thanks how long do repairs usually take regarding the texas repair center and nexus 7?
Nexus7<3 said:
So I sent my tab to asus because it went into apx mode and would not come out. I've been reading asus unlock tools send asus servers info about the fact that a device was just unlocked including serial number. I'm wondering if they will know as my tab was completely dead. Also I sent it in a week ago and there online rma tracker has not updated at all. Thanks how long do repairs usually take regarding the texas repair center and nexus 7?
Click to expand...
Click to collapse
I had my original TF101 serviced by this facility 3 times. The first time (it couldnot power on) I had a customed ROM with OC settings. I think they just simply hooked it up to restore a factory image then test to determine what the issues were. All three times, it came back with the original factory ROM. I havenot heard anyone got rejected due to customed ROM was found onboard.
(it had a corrupted flash memory and Texas kept saying no-problem-found --> I had to call Asus/San Jose to get the mainboard replaced --> it's been working beautifully since)
It normally came back very fast (to CA) within a week (maybe that's why they couldnot find the issue). The 3rd RMA took two weeks since I told them I wouldnot accept it without a new mainboard or a different unit.

SM-N910F - mmc_read_failed Error

Hi All,
I have a SM-N910F that I have been using as my daily phone for about 18 months. I have NEVER ROOTED.
Recently I started encountering lags, freezes and restarts. In general, the phone became unusable.
I factory reset the phone and set the whole phone again from scratch, but in a few days I'm back where I was.
If I restart the phone, OR power down, the phone does not start. I have to pull the battery out, and re-insert for the phone to start again.
I even tried Firmware Recovery via KIES but that too failed, and after that I'm beginning to see a new variant to my problem.
Now, the phone mostly boots into Download Mode, where I see the below:
Could not do normal boot.
ddi : mmc_read failed
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-N910F
CURRENT BINARY: Samsung Official
System Status: Custom
REACTIVATION LOCK: OFF
KNOX WARRANTY VOID: 0x1 (0)
I'm a little worried about the above highlighted lines, as I plan to take the Phone down to Samsung (Samsung Chat confirmed that the phone is still in Warranty).
As I have never rooted the phone, I'm quite surprised why the phone is showing System Status as Custom. Is this something to worry about, or should it be fine and considered still under warranty?
Any advice would be great, as I really need to get this phone working normal again.
The problem is "mmc_read failed" message. It seems that your internal memory got damaged. It's like a computer without a hdd. Good luck
You are fine for warranty.
popic_u said:
The problem is "mmc_read failed" message. It seems that your internal memory got damaged. It's like a computer without a hdd. Good luck
You are fine for warranty.
Click to expand...
Click to collapse
Thanks but the System Status Custom message, is that normal??
And what will they do under Warranty? that is what will they change?
dg170775 said:
Thanks but the System Status Custom message, is that normal??
And what will they do under Warranty? that is what will they change?
Click to expand...
Click to collapse
No its not normal, if you've never rooted it, it should be Official and not Custom.
You bought it from a 2nd hand or new ?
EDIT : And its the same for the "Knox 0x1(0)" wich isn't normal too, it should be on 0x0 and not 0x1.
It was bought new.. Infact I pre ordered
Sent from my Nexus 6P using Tapatalk
dg170775 said:
It was bought new.. Infact I pre ordered
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Are you really sure you've never attempted to root it or did something wich can void the knox warranty ?
KeTuRr74 said:
Are you really sure you've never attempted to root it or did something wich can void the knox warranty ?
Click to expand...
Click to collapse
No.. only thing out of the ordinary that I tried was to try Emergency Firmware recovery via KIES, but that too failed halfway, with some messages about unable to write or something
So, what do I do now? To get it back on warranty? Problem is that phone's pretty much un-usable, to even try anything at the moment.
dg170775 said:
Hi All,
Any advice would be great as I really need to get this phone working normal again.
Click to expand...
Click to collapse
Taking a look on Reddit and you will see hundreds of comments complaining about MMC errors for Note 4. I too just got it and was pissed.
Note 4's are dropping like fly's after a year and half of use. Like Xbox and RROD.
I called Samsuck and they told be to fly a kite and wouldn't cover anything.
Call them and give them crap! Hopefully the calls will add up.
To fix, I found a broken Note 4 on eBay and swapped the working motherboard from it. If you need any help fixing it just PM.
The phone will only get worse over time.
dg170775 said:
Hi All,
I have a SM-N910F that I have been using as my daily phone for about 18 months. I have NEVER ROOTED.
Recently I started encountering lags, freezes and restarts. In general, the phone became unusable.
I factory reset the phone and set the whole phone again from scratch, but in a few days I'm back where I was.
If I restart the phone, OR power down, the phone does not start. I have to pull the battery out, and re-insert for the phone to start again.
I even tried Firmware Recovery via KIES but that too failed, and after that I'm beginning to see a new variant to my problem.
Now, the phone mostly boots into Download Mode, where I see the below:
Could not do normal boot.
ddi : mmc_read failed
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-N910F
CURRENT BINARY: Samsung Official
System Status: Custom
REACTIVATION LOCK: OFF
KNOX WARRANTY VOID: 0x1 (0)
I'm a little worried about the above highlighted lines, as I plan to take the Phone down to Samsung (Samsung Chat confirmed that the phone is still in Warranty).
As I have never rooted the phone, I'm quite surprised why the phone is showing System Status as Custom. Is this something to worry about, or should it be fine and considered still under warranty?
Any advice would be great, as I really need to get this phone working normal again.
Click to expand...
Click to collapse
Don't worry about the custom status.
Mine has started doing the same after about 14 months - freezing, restarting, switching off. I got the mmc read fail and custom status on a reboot as well (mines never seen root or a custom firmware) but if I manually boot it in to download mode , the status reads official. Try it on yours.
Apparently it's down to having a 64gb card installed when the phone fails ti boot but I can't varify that.
James.Miller said:
Don't worry about the custom status.
Mine has started doing the same after about 14 months - freezing, restarting, switching off. I got the mmc read fail and custom status on a reboot as well (mines never seen root or a custom firmware) but if I manually boot it in to download mode , the status reads official. Try it on yours.
Apparently it's down to having a 64gb card installed when the phone fails ti boot but I can't varify that.
Click to expand...
Click to collapse
You are so right.. I just checked it, and if I get into Bootloader manually I see that the SYSTEM STATUS is Official
Even the Knox Warranty line is slightly different
KNOX WARRANTY VOID: 0x1 (4)
So, I guess I'll take the trip down to Samsung Centre, and as the Engineer in the chat confirmed, they'll repair for FREE, under Warranty
Also curious if you've got your phone sorted?? and If so, what did you do?
dg170775 said:
You are so right.. I just checked it, and if I get into Bootloader manually I see that the SYSTEM STATUS is Official
Even the Knox Warranty line is slightly different
KNOX WARRANTY VOID: 0x1 (4)
So, I guess I'll take the trip down to Samsung Centre, and as the Engineer in the chat confirmed, they'll repair for FREE, under Warranty
Also curious if you've got your phone sorted?? and If so, what did you do?
Click to expand...
Click to collapse
Unfortunately no. My phone is useable but getting worse. Luckily Im only a few miles from my closest Samsung centre so I'm going to take it in on Saturday
Me too going on Saturday to the Wembley centre (my nearest)
My phone is totally unusable and only boots into the bootloader.
Sent from my Nexus 6P using Tapatalk
Ok so i thought i'd post an update for you guys:
I took my phone in to samsung in Milton Keynes on saturday. At first they were'nt sure about the phone as it had a third party battery (the original failed at 13 months) and german firmware on it (offical, was the only way to get 5.1.1 at the time..). But they eventually took it in. They were busy, which is fair enough it was a Saturday after all, but gave the german firmware as an excuse not to test it that day. The girl told me quite clearly that they would have to reflash the correct firmware before they can test it, again, fine, it was busy.
When they took the phone, they took the sim and my 64gb memory card.I questioned this at the time but i was told it was fine. so OK.
Fast forward a bit and yesterday i get the email to say its fixed. YEY. So i visited the samsung store today to pick it up, only the find the sim and card missing. The guy i dealt with said he'd seen the card when it was being repaired. it was a 64gb sandisk Sandisk ultra, so red and grey - quite distinctive. He then heads ouyt back to speak to somebody and comes back out saying "you're not going to like this, but they've been disposed of".
REALLY? YOU THREW THEM AWAY?
Then he proceeds to point to the small print stating they are not responsible for sims or cards left in the phones. FFS. I asked for them back when i handed them phone over and was told it was fine and at no point was i shown this small print OR advised that they cant take them. Anyway he himself was quite helpful so it was hard to be mad with him. He's given me the number of head office and their branch code, so im going to ring them and see what i can do.
So, at this point the phone is fixed. It needed a new mainboard as expected and a new charging board as well - didnt expect that but it could have been damaged when they took the screen off. but, i have no sim and no memory card. The card can wait - everything is backed up so ive lost nothing but the card itself but it is the principal, here. Having no sim i had to go visit the three store in the hopes that they could provide another for me. They could, luckily, and my sim was registered and up and running as soon as i inserted it and turned the phone on so at least i have a working phone. Great service from Three. Samsung/carphone warehouse...not so much.
so that's where i am. Oh and they didnt reflash the right firmware on the phone, apparently they arent even allowed to do that. So the girl i dealt with on saturday wasnt right about that either.
James.Miller said:
Ok so i thought i'd post an update for you guys:
I took my phone in to samsung in Milton Keynes on saturday. At first they were'nt sure about the phone as it had a third party battery (the original failed at 13 months) and german firmware on it (offical, was the only way to get 5.1.1 at the time..). But they eventually took it in. They were busy, which is fair enough it was a Saturday after all, but gave the german firmware as an excuse not to test it that day. The girl told me quite clearly that they would have to reflash the correct firmware before they can test it, again, fine, it was busy.
When they took the phone, they took the sim and my 64gb memory card.I questioned this at the time but i was told it was fine. so OK.
Fast forward a bit and yesterday i get the email to say its fixed. YEY. So i visited the samsung store today to pick it up, only the find the sim and card missing. The guy i dealt with said he'd seen the card when it was being repaired. it was a 64gb sandisk Sandisk ultra, so red and grey - quite distinctive. He then heads ouyt back to speak to somebody and comes back out saying "you're not going to like this, but they've been disposed of".
REALLY? YOU THREW THEM AWAY?
Then he proceeds to point to the small print stating they are not responsible for sims or cards left in the phones. FFS. I asked for them back when i handed them phone over and was told it was fine and at no point was i shown this small print OR advised that they cant take them. Anyway he himself was quite helpful so it was hard to be mad with him. He's given me the number of head office and their branch code, so im going to ring them and see what i can do.
So, at this point the phone is fixed. It needed a new mainboard as expected and a new charging board as well - didnt expect that but it could have been damaged when they took the screen off. but, i have no sim and no memory card. The card can wait - everything is backed up so ive lost nothing but the card itself but it is the principal, here. Having no sim i had to go visit the three store in the hopes that they could provide another for me. They could, luckily, and my sim was registered and up and running as soon as i inserted it and turned the phone on so at least i have a working phone. Great service from Three. Samsung/carphone warehouse...not so much.
so that's where i am. Oh and they didnt reflash the right firmware on the phone, apparently they arent even allowed to do that. So the girl i dealt with on saturday wasnt right about that either.
Click to expand...
Click to collapse
i doubt you needed a new charging usb board. Place sounds shady.
Sent from my SM-N910C using XDA-Developers mobile app
dg170775 said:
Hi All,
I have a SM-N910F that I have been using as my daily phone for about 18 months. I have NEVER ROOTED.
Recently I started encountering lags, freezes and restarts. In general, the phone became unusable.
I factory reset the phone and set the whole phone again from scratch, but in a few days I'm back where I was.
If I restart the phone, OR power down, the phone does not start. I have to pull the battery out, and re-insert for the phone to start again.
I even tried Firmware Recovery via KIES but that too failed, and after that I'm beginning to see a new variant to my problem.
Now, the phone mostly boots into Download Mode, where I see the below:
Could not do normal boot.
ddi : mmc_read failed
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-N910F
CURRENT BINARY: Samsung Official
System Status: Custom
REACTIVATION LOCK: OFF
KNOX WARRANTY VOID: 0x1 (0)
I'm a little worried about the above highlighted lines, as I plan to take the Phone down to Samsung (Samsung Chat confirmed that the phone is still in Warranty).
As I have never rooted the phone, I'm quite surprised why the phone is showing System Status as Custom. Is this something to worry about, or should it be fine and considered still under warranty?
Any advice would be great, as I really need to get this phone working normal again.
Click to expand...
Click to collapse
Hi, was there a definite solution? I have the same problem.
I was wondering..
I came across this Forum group since I was looking for boot problems with my SM-N910T3
I hope flashing pit will resolve this..
I recently started to have some low level issue and was hoping it was partition/boot related and not hardware.
Randomly phone boot directly into Download mode with error;
ddi: mmc_read failed
Often I have to pull battery and hold down /power / home for 10 sec to boot up again.
Thanks
Ahh welcome to the club, my Note 4 got the same errors now after > 1 year. Suddenly and without me doing anything wrong.
And nothing helped to repair it, no flashing of FWs or PIT files or anything. So - I guess a new mainboard would be the only solution.
Problem is, I am also Knox 0x1 - yes, I rooted the phone, and now I am worried that I won't get it repaired by Samsung on warranty.
Which would be an utter shame, since nobody can be blaimed for the faulty mmcs except Sammy.
So I rooted my note 4 910g on MM using Twrp and SuperSU 2.74 Beta. The problem is that it has started behaving weird with random freezes and bootloops. Formatting and Reflashing PIT, ROM, etc causes it to get stuck at Android is upgrading and it goes on for like 10mins and then the cycle repeats. Is my eMMC dying? Do help if someone can help me revive my phone somehow.
I know i shouldnt be hoping for much of a solution but still if theres hope then do post a reply.
I started experiencing this issue since last week. Out of nowhere, my Note 4 started to lag and freeze. At first I thought maybe it was the battery too, so I got myself a brand new Anker Battery. And hey, nope it's not a battery issue. Then I reformatted my phone, and yes, it was still lagging and freezing.
Fast forward to this week, last night, I got the mmc_read failed message. Shoot me.
Now I've been using the Wake Lock app and it's set to Level 4 (Partial Wake Lock). It's been much better with this App running. Of course, my battery takes a hit. But at least the phone is usable, as long as I don't restart the Phone.
My gf's phone is exactly the same as mine, Note 4, and we're exactly on the same firmware version. She has no issue at all. We've switched batteries as well and her phone works fine with any battery.
I never rooted my phone, and I've been using only the original, official firmware pushed by T-mobile. My phone is running the latest firmware (EQB1) released last month. The problem didn't start right after my phone was updated. Only since last week.
Now, I've been scouring the Internet and many say this is a hardware issue, but some say too that this is probably caused by the firmware. Does anyone now know better if this is a hardware or software issue?
I was going to get myself another Note 4 but then if this is a firmware issue, it could happen too to a new Note 4. If this is a hardware issue, then a new Note 4 may not get this problem.
There's also a conspiracy theory saying that Samsung purposely did this so as to force all Note 4 users to upgrade their phones. If this is a firmware issue, can we file a class suit? Sigh.
UPDATE 1:
I just came back from the Samsung Experience Center. I also talked with Samsung, T-mobile over the Phone today.
So basically, from what the guy over at the Samsung Experience Center told me, a few months ago, many Note 4 Sprint users had this exact same issue. Basically the firmware update caused the phone to malfunction. In the end Samsung replaced all the affected phones. I went there, talked to him, and initially I wanted him to reflash my phone but he then told me that this issue was basically a faulty firmware. Reflashing wouldn't really help because the firmware itself is faulty. The firmware could have affected (damaged) the hardware. That this exact same issue has happened in the past with Sprint users.
I then called Samsung hotline up and talked with, fortunately, a friendly and helpful rep who was willing to document everything and escalate the issue on my behalf. She told me that she would call me back in a few days to update me on how the case is going.
At this point, I'll just have to wait and see.
UPDATE 2:
And apparently I just learned that Note 4 in Europe and Sprint here in the US just received a latest firmware update around 300-400mb in size.
"The firmware update description reveals that it brings better stability and performance as well as optimizations for improving battery efficiency. This Galaxy Note 4 update also comes with the March security patch that has 73 fixes for Android OS vulnerabilities and fixes for a dozen vulnerabilities that Samsung found in its own software."
Fingers-crossed, hopefully this update will soon come to T-mobile and other carriers and fix our issue.
T-mobile recently released a firmware update for Galaxy Note 4 (EQC1): https://support.t-mobile.com/docs/DOC-28899
I'm wondering if anyone has installed this and can confirm if this firmware update has fixed the mmc_read failed issue along with the constant lagging/freezing problem?

Note 4 completely dead, eMMC issue?

I recently bought a "soft bricked" Note 4 (N910F, Snapdragon). Seller claimed a friend of his wanted to flash a custom ROM based on a newer Android version, however that failed and it only boots to Recovery and Download mode since. So he wanted to sell it since he's not experienced with phones. The listing actually shows a photo of the phone in download mode and one in recovery mode.
After I got the device, I plugged it in to charge the battery and to my surprise, nothing happens. No charge LED, no charge animation. I tried to get into recovery mode (volume up, home + power) and download mode (volume down, home + power), with USB cable attached and without, still nothing. If I plug it into my PC, it's recognised as Qualcomm HS-USB Loader. Suspecting the worst, I prepared a microSD with the debrick image on it. And sure enough, on the first try, the phone fires up into Odin mode. Interestingly, the bootloader is locked and Knox is not triggered. Which to me indicates that noone ever even attempted flashing a custom ROM, right?
Once in Odin mode, I tried flashing the stock ROM - it fails on the first step and the phone shows the dreaded "eMMC write fail: aboot". So I guess it encountered the well-known eMMC problem?
Since the seller refuses to take the phone back (despite the wrong description), I took on getting it to work myself. Sure enough, after a night in the freezer I could flash and boot a stock ROM before it stopped working. Another freeze to set it up, and a third one to install a wakelock app and set up a partial wakelock. That uses ~5% battery per hour, but the phone is still running after nearly a day.
Does that still fit to the eMMC issue? And since I have a T-962 IR reflow oven - do you think there is a chance to successfully reflow the board so that the phone can operate normally again?
Thanks a lot!
Bought on eBay?
Open a dispute claim as doesn't work as it's not working even in the way how was described on the listing.
Sent from my K10 using Tapatalk
id just get a new motherboard https://www.aliexpress.com/w/wholesale-galaxy-note-4-motherboard.html
a602820922 said:
Bought on eBay?
Open a dispute claim as doesn't work as it's not working even in the way how was described on the listing.
Click to expand...
Click to collapse
Yeah, from eBay, But I can't open a claim since it only allowed payment with wire transfer so there's no buyer's protection. The seller also keeps being unreasonable, claims I don't know what I'm doing and broke it myself, after he sold it as "he doesn't know anything about it and can't flash a new ROM". I gave him negative feedback (and had his revenge feedback deleted by eBay) but that's all they can do for me.
bluefender said:
id just get a new motherboard https://www.aliexpress.com/w/wholesale-galaxy-note-4-motherboard.html
Click to expand...
Click to collapse
That actually sounds good, do you have any experience with such a new board? Are they refurbished or "new old stock"? Do they keep working for at least some time?
YassinTP said:
Yeah, from eBay, But I can't open a claim since it only allowed payment with wire transfer so there's no buyer's protection. The seller also keeps being unreasonable, claims I don't know what I'm doing and broke it myself, after he sold it as "he doesn't know anything about it and can't flash a new ROM". I gave him negative feedback (and had his revenge feedback deleted by eBay) but that's all they can do for me.
That actually sounds good, do these keep working for at least some time?
Click to expand...
Click to collapse
there are a few sellers, of the same board, id read the reviews on each seller..worth a punt considering the price of the note 4 originally.
https://www.aliexpress.com/w/wholesale-galaxy-note-4-logic-board.html

Categories

Resources