Details of Phone
Model: SM-N910G (India)
Android: 5.0.1 (Stock, Official ROM)
Build: LRX22C.N910GDTY1BOK1
Details of Errors
1. Hangs and restarts every now and then. Problem started suddenly.
2. After restart, going to Download Mode with error >> Could not do normal boot. ddi : mmc read failed
3. Unable to restart, going to Download Mode always.
4. Removed battery, started in Recovery mode and rebooted from there to turn the phone on.
5. Again same problem, hangs and restarts -> Download mode.
Solution Tried
1. Full factory reset (from Recovery wipe data and within phone both)
2. Reloading of ROM from Samsung Kies
3. Reloading of ROM from Samsung Service Center
Nothing worked.
New Errors appeared
1. dm-verity verification failed in Recovery Mode
2. Attention Message: "An error has occurred with the fingerprint sensor"
3. Unable to store WiFi information (every-time need to connect)
Questions
1. What might be the issue of this? Hardware / Software / OS related?
2. As per Samsung Service Center it might be the issue with Motherboard. (Cost. INR 9000/- or USD 135) - They are not sure
3. My handset is out of warranty, should I try something else?
I am totally upset for this. Any help and suggestion will be highly appreciated.
Thanks a lot.
- Rahul
Sounds like a damaged EMMC (NAND) , you can try fixing it by flashing stock with a PIT file. If that fails it's a hardware defect and you should claim warranty.
SquirtingCherry said:
Sounds like a damaged EMMC (NAND) , you can try fixing it by flashing stock with a PIT file. If that fails it's a hardware defect and you should claim warranty.
Click to expand...
Click to collapse
Thanks mate.
Perhaps you are correct. Now phone is completely dead, upon boot it is showing: "Device Memory Damaged".
Can you suggest the possible solution. Can only internal memory be changed or I have to change the complete motherboard?
rahul319 said:
Details of Phone
Model: SM-N910G (India)
Android: 5.0.1 (Stock, Official ROM)
Build: LRX22C.N910GDTY1BOK1
Details of Errors
1. Hangs and restarts every now and then. Problem started suddenly.
2. After restart, going to Download Mode with error >> Could not do normal boot. ddi : mmc read failed
3. Unable to restart, going to Download Mode always.
4. Removed battery, started in Recovery mode and rebooted from there to turn the phone on.
5. Again same problem, hangs and restarts -> Download mode.
Solution Tried
1. Full factory reset (from Recovery wipe data and within phone both)
2. Reloading of ROM from Samsung Kies
3. Reloading of ROM from Samsung Service Center
Nothing worked.
New Errors appeared
1. dm-verity verification failed in Recovery Mode
2. Attention Message: "An error has occurred with the fingerprint sensor"
3. Unable to store WiFi information (every-time need to connect)
Questions
1. What might be the issue of this? Hardware / Software / OS related?
2. As per Samsung Service Center it might be the issue with Motherboard. (Cost. INR 9000/- or USD 135) - They are not sure
3. My handset is out of warranty, should I try something else?
I am totally upset for this. Any help and suggestion will be highly appreciated.
Thanks a lot.
- Rahul
Click to expand...
Click to collapse
Weird enough i had the same problem yesterday of emmc read failed as phone was rebooting suddenly and going into download mode
So i wiped data and flashed a new rom so the emmc problem went away and device just rebooted normally
Then i noticed device only rebooted when fb app was used
So i removed it and now everything working perfectly
Ashwin Prabhunerurkar said:
Weird enough i had the same problem yesterday of emmc read failed as phone was rebooting suddenly and going into download mode
So i wiped data and flashed a new rom so the emmc problem went away and device just rebooted normally
Then i noticed device only rebooted when fb app was used
So i removed it and now everything working perfectly
Click to expand...
Click to collapse
I tried the same flashing everything and reloading the same ROM but no luck
Ashwin Prabhunerurkar said:
Weird enough i had the same problem yesterday of emmc read failed as phone was rebooting suddenly and going into download mode
So i wiped data and flashed a new rom so the emmc problem went away and device just rebooted normally
Then i noticed device only rebooted when fb app was used
So i removed it and now everything working perfectly
Click to expand...
Click to collapse
What is fb, Facebook? Very strange if that was the issue!!
HAving a similar problem
I have flashed a lot of ROMs lately and have also being Dualbooting, I went back to stock and am still experiencing problems, random freezer, reboots and unfortunately the bad boot screen saying "ddi: mmc failed to read" hopefully I have not corrupted or damaged any internal memory.
---------- Post added at 09:21 AM ---------- Previous post was at 09:19 AM ----------
rahul319 said:
I tried the same flashing everything and reloading the same ROM but no luck
Click to expand...
Click to collapse
Any update?
joeb690 said:
What is fb, Facebook? Very strange if that was the issue!!
HAving a similar problem
I have flashed a lot of ROMs lately and have also being Dualbooting, I went back to stock and am still experiencing problems, random freezer, reboots and unfortunately the bad boot screen saying "ddi: mmc failed to read" hopefully I have not corrupted or damaged any internal memory.
---------- Post added at 09:21 AM ---------- Previous post was at 09:19 AM ----------
Any update?
Click to expand...
Click to collapse
Samsung told that entire motherboard needs to be replaced which costs INR. 18500/- (US$ 275)
I have given the phone to the local mobile shop, and eventually that shop is also a Samsung retail shop. They told that it is a problem with internal memory emmc and they are replacing the faulty part which costs INR. 2400/- (US$ 35). Lets hope for the best. Will update you as soon as get back my phone.
joeb690 said:
What is fb, Facebook? Very strange if that was the issue!!
HAving a similar problem
I have flashed a lot of ROMs lately and have also being Dualbooting, I went back to stock and am still experiencing problems, random freezer, reboots and unfortunately the bad boot screen saying "ddi: mmc failed to read" hopefully I have not corrupted or damaged any internal memory.
---------- Post added at 09:21 AM ---------- Previous post was at 09:19 AM ----------
Any update?
Click to expand...
Click to collapse
Gave back the phone for full refund
So cant help you
rahul319 said:
Samsung told that entire motherboard needs to be replaced which costs INR. 18500/- (US$ 275)
I have given the phone to the local mobile shop, and eventually that shop is also a Samsung retail shop. They told that it is a problem with internal memory emmc and they are replacing the faulty part which costs INR. 2400/- (US$ 35). Lets hope for the best. Will update you as soon as get back my phone.
Click to expand...
Click to collapse
How does the internal memory (emmc) gets damaged on a user error? I think that must be a manufacturing defect.
btw, I have a similar problem with random freezing and restarts since I updated my Note 4 (Tmobile) from 4.4.4 to 5.11
I used a Tekxodus URV5 (5.11) and these problems started, then I tried to fix the problem .. I flashed stock 5.11 (DOK2), TWRP, flashed the latest Tekxodus URV6.5 (after wiping my internal memory, cache, davlik.) ... Same problems.
I guess lesson learned is to stay a way from Lollipop and stay with Kitkat.
Ditto
I am also very curious about this.
I have a note 4 which exhibited these same symptoms and error messages. Although it was in any app at any stage or merely when the phone was in standby.
NB this was purchased direct from the Samsung store.
I sent it back to Samsung two or three times without them fixing the issue. On the last time I was told that they would not fix the phone – which is still well within warranty – because the phone “has been subjected to severe physical damage internally”.
The unit has always been well kept, there is no water damage and there is not a scratch on it….anywhere. also there was no indication of this severe physical damage during the previous Samsung inspections.
I can’t think of a good way to contest this prove this is a problem with the phone and not my use of it.
Samsung are not responsive when contacted. Is there any advice in the forum?? Many Thanks
lewis.james.750983 said:
How does the internal memory (emmc) gets damaged on a user error? I think that must be a manufacturing defect.
btw, I have a similar problem with random freezing and restarts since I updated my Note 4 (Tmobile) from 4.4.4 to 5.11
I used a Tekxodus URV5 (5.11) and these problems started, then I tried to fix the problem .. I flashed stock 5.11 (DOK2), TWRP, flashed the latest Tekxodus URV6.5 (after wiping my internal memory, cache, davlik.) ... Same problems.
I guess lesson learned is to stay a way from Lollipop and stay with Kitkat.
Click to expand...
Click to collapse
Strange thing that's EXATLY what happens to me too
it seems Samsung is trying to kill it's last Flagship Note phone with a MicroSD and removable battery.
Rahul, any update on replacement of emmc. My note 4 has also developed the same problem. Eagerly waiting for a solution.
raj0052 said:
Rahul, any update on replacement of emmc. My note 4 has also developed the same problem. Eagerly waiting for a solution.
Click to expand...
Click to collapse
Hi Raj. No luck
I have got an exchange offer from Flipkart with Rs. 23000/- and have replaced it with my old phone; because replacing motherboard with Rs. 18500/- with only 3 months warranty doesn't make any sense.
I have got a new phone with 1 year warranty with an option of further warranty extension.
Lesson learnt: For high-end phone always go for extended warranty.
emmc_read error
I am now very confident that the "emmc_read error" message is a caused by firmware problem.
I have a N910F for a long time, that was working like a Swiss watch, on the 5.0.x Android.
Recently I've got an update to 5.1.1 and installed it.
The update went through very smooth but after the phone started for the first time it began to freeze.
A few times i have got emmc_read failed message on boot screen and in the logcat the most notable error was SecureStorage TA driver related
it fails to write /efs partition :
I/SecureStorage( 4914): [INFO]: SPID(0x00000000)Secure Storage Daemon sent config to TA/driver
W/SecureStorage( 4914): [WARN]: SPID(0x00000000)system error
E/SecureStorage( 4914): [ERROR]:SPID(0x00000000)
E/SecureStorage( 4914): [ERROR]:SPID(0x00000000)
E/SecureStorage( 4914): [ERROR]:SPID(0x00000000)================================= ============================
E/SecureStorage( 4914): [ERROR]:SPID(0x00000000)It is failed to write a file to /efs partition.
E/SecureStorage( 4914): [ERROR]:SPID(0x00000000)Please check
E/SecureStorage( 4914): [ERROR]:SPID(0x00000000)(1) if there is a valid /efs partition, and
E/SecureStorage( 4914): [ERROR]:SPID(0x00000000)(2) if /efs directory has the correct permission.
E/SecureStorage( 4914): [ERROR]:SPID(0x00000000)================================= ============================
E/SecureStorage( 4914): [ERROR]:SPID(0x00000000)
E/SecureStorage( 4914): [ERROR]:SPID(0x00000000)
W/SecureStorage( 4914): [WARN]: SPID(0x00000000)Error sending config file to TA/driver!
I/SecureStorage( 4914): [INFO]: SPID(0x00000000)Secure Storage Daemon stopped
Although the directory and premissions are fine (i've checked many times)
Odin cannot flash with or without PIT file:
<ID:0/009> hidden.img.ext4
<ID:0/009> FAIL! (Write)
As a conclusion i can suggest that the update causes the problem.
I am pretty sure there could be a tool to check emmc, but i could not find any and i am lazy to develop it myself, but for the guys from TWRP this could be a good hint.
BR
Max
I'm not entirely sure the emmc fail is due to updates. i'm still on KK and today i experienced the emmc failure. Major lag so i restarted it but took forever. Then, about 2 hours later, it crashed while opening up snapchat. I try to restart the phone and it goes into download mode saying "emmc read fail". Can't believe so many people are being affected by this.
If you flashed stock ROM with PIT file and the phone doesnt work properly i think your EMMC is corrupted. EMMC can be corrupted by a lot of thing like bad custom rom, ported recovery, etc... Search for a tutorial to flash with PIT and REPARTITION and if that didnt work the EMMC is the fault for sure. You can change the EMMC only very easy if you go to a GSM service center... or buy a hot air station, a leaded solder wire, a wick wire and the EMMC chip.
So first try repartition the phone and if doesnt work just change that EMMC.
Its a software issue. I had the exact same issue with my T-Mobile version SM-N910T. I was able to resolve it by using ODIN to install the stock EPE3 along with the modem of COD6. After the phone restarted I placed the phone in download mode again and from there went on ODIN to install the EPE3 modem. After the phone restarts it should boot straight to the home screen.
maxrfon said:
A few times i have got emmc_read failed message on boot screen and in the logcat the most notable error was SecureStorage TA driver related
it fails to write /efs partition :
I/SecureStorage( 4914): [INFO]: SPID(0x00000000)Secure Storage Daemon sent config to TA/driver
W/SecureStorage( 4914): [WARN]: SPID(0x00000000)system error
E/SecureStorage( 4914): [ERROR]:SPID(0x00000000)
E/SecureStorage( 4914): [ERROR]:SPID(0x00000000)
E/SecureStorage( 4914): [ERROR]:SPID(0x00000000)================================= ============================
E/SecureStorage( 4914): [ERROR]:SPID(0x00000000)It is failed to write a file to /efs partition.
E/SecureStorage( 4914): [ERROR]:SPID(0x00000000)Please check
E/SecureStorage( 4914): [ERROR]:SPID(0x00000000)(1) if there is a valid /efs partition, and
E/SecureStorage( 4914): [ERROR]:SPID(0x00000000)(2) if /efs directory has the correct permission.
E/SecureStorage( 4914): [ERROR]:SPID(0x00000000)================================= ============================
E/SecureStorage( 4914): [ERROR]:SPID(0x00000000)
E/SecureStorage( 4914): [ERROR]:SPID(0x00000000)
W/SecureStorage( 4914): [WARN]: SPID(0x00000000)Error sending config file to TA/driver!
I/SecureStorage( 4914): [INFO]: SPID(0x00000000)Secure Storage Daemon stopped
Although the directory and premissions are fine (i've checked many times)
Odin cannot flash with or without PIT file:
<ID:0/009> hidden.img.ext4
<ID:0/009> FAIL! (Write)
As a conclusion i can suggest that the update causes the problem.
I am pretty sure there could be a tool to check emmc, but i could not find any and i am lazy to develop it myself, but for the guys from TWRP this could be a good hint.
BR
Max
Click to expand...
Click to collapse
I do believe that is similar to my issue, on TouchWiz, I will just get crashes that shut off the phone and the mmc issue. On Cyanogenmod, I don't get the mmc crashes, but at random times, my cell service will cut out and stop working, it eventually restores itself, or sometimes it triggers a kernel panic. I tried backing up my efs from TWRP and then restoring the back up multiple times, first time was 0 seconds, second was 104 seconds. Either time seems wrong. But after constant swipe to restores, It stopped doing the lag, I wonder if the update somehow wrote iffy data that was causing problems on the partition. From what I have also noticed, the mmc issue (at least for me) seems that the chip just becomes incredibly slow for a short time and then speeds back up, when I reboot from TWRP or the OS. It hangs at black for a while and then the phone seems to boot itself.
yaoers said:
I'm not entirely sure the emmc fail is due to updates. i'm still on KK and today i experienced the emmc failure. Major lag so i restarted it but took forever. Then, about 2 hours later, it crashed while opening up snapchat. I try to restart the phone and it goes into download mode saying "emmc read fail". Can't believe so many people are being affected by this.
Click to expand...
Click to collapse
I have your exact same problem: still on KK 4.4.4 (stock, no root) the phone always went well until yesterday... First it seems to freeze (also when using the power button) and then I cannot boot again until I removed the battery.
Then I got the emmc read fail error, removed the battery, restarted and it booted, but still sometimes there are major lags (never seen before).
Related
I am lost on this S5 Verizon phone repair any help would be appreciated. Below is everything I have already done. During each time I flashed the device with ODIN I have also went in and did a wipe catch and factory reset to make sure it wasn't anything getting "stuck" during the flash process.
First error message when this all started read:
“System software not authorized by Verizon Wireless has been found on your phone....”
Above this error message in red text reads: Secure Fail: Modem
I decided I would attempt to go back to stock firmware and unroot the device. I have downloaded and loaded step by step of the following software packages via odin.
ALL_VZW_G900VVRU1ANCG_G900VVZW1ANCG_964333_REV00_user_low_ship_MULTI_CERT.tar.md5
ALL_VZW_G900VVRU1ANE9_G900VVZW1ANE9_1556536_REV00_user_low_ship_MULTI_CERT.tar.md5
ALL_VZW_G900VVRU1ANHA_G900VVZW1ANHA_2525521_REV00_user_low_ship_MULTI_CERT.tar.md5
ALL_VZW_G900VVRU1ANI2_G900VVZW1ANI2_2525521_REV00_user_low_ship_MULTI_CERT.tar.md5
I have also attempted to reset the PIT with: KLTE_USA_VZW ( I tried this after the first software package did not correct the issue and did some more research)
After doing all of the above I still get the “System software not authorized by Verizon Wireless has been found on your phone.”
I attempted to use
G900VVRU1BOA8_G900VVZW1BOA8_G900VVRU1BOA8_HOME - which is 5.0 and I am downloading this from Sammobile.com as I type to try instead.
On 5.0 i get a different error instead reading:
Start Up Failed
Your device didn't start up successfully. Use the Verizon software repair assistant on a computer to repair your device.
Above this error message in red text reads: Secure Fail: Modem
I can not use kies as the device is recognized but says it is not supported.
Please note: I did purchase this device knowing the first error message thinking it would just be a simple re-flash back to stock.
My Background: I have worked in the mobile business as a Sprint tech for 2 years and now work for a private company in computer and mobile repair so a total of 3 1/2 years mobile experience. However, I have not run into an issue like this before.
Again any help is much appreciated as this one has me stumped on what to try next
Update
Update:
I have downloaded the firmware G900VVRU1BOA8_G900VVZW1BOA8_VZW from sammobile.com
When flashing with odin i get the same error " Your device didn't start up successfully......"
Also, I attempted to update from zip and I received an error "E footer is wrong" and "E signature verification failed"
Again any suggestion are appreciated.
tan0892 said:
I am lost on this S5 Verizon phone repair any help would be appreciated. Below is everything I have already done. During each time I flashed the device with ODIN I have also went in and did a wipe catch and factory reset to make sure it wasn't anything getting "stuck" during the flash process.
First error message when this all started read:
“System software not authorized by Verizon Wireless has been found on your phone....”
Above this error message in red text reads: Secure Fail: Modem
I decided I would attempt to go back to stock firmware and unroot the device. I have downloaded and loaded step by step of the following software packages via odin.
ALL_VZW_G900VVRU1ANCG_G900VVZW1ANCG_964333_REV00_user_low_ship_MULTI_CERT.tar.md5
ALL_VZW_G900VVRU1ANE9_G900VVZW1ANE9_1556536_REV00_user_low_ship_MULTI_CERT.tar.md5
ALL_VZW_G900VVRU1ANHA_G900VVZW1ANHA_2525521_REV00_user_low_ship_MULTI_CERT.tar.md5
ALL_VZW_G900VVRU1ANI2_G900VVZW1ANI2_2525521_REV00_user_low_ship_MULTI_CERT.tar.md5
I have also attempted to reset the PIT with: KLTE_USA_VZW ( I tried this after the first software package did not correct the issue and did some more research)
After doing all of the above I still get the “System software not authorized by Verizon Wireless has been found on your phone.”
I attempted to use
G900VVRU1BOA8_G900VVZW1BOA8_G900VVRU1BOA8_HOME - which is 5.0 and I am downloading this from Sammobile.com as I type to try instead.
On 5.0 i get a different error instead reading:
Start Up Failed
Your device didn't start up successfully. Use the Verizon software repair assistant on a computer to repair your device.
Above this error message in red text reads: Secure Fail: Modem
I can not use kies as the device is recognized but says it is not supported.
Please note: I did purchase this device knowing the first error message thinking it would just be a simple re-flash back to stock.
My Background: I have worked in the mobile business as a Sprint tech for 2 years and now work for a private company in computer and mobile repair so a total of 3 1/2 years mobile experience. However, I have not run into an issue like this before.
Again any help is much appreciated as this one has me stumped on what to try next
Click to expand...
Click to collapse
tan0892 said:
Update:
I have downloaded the firmware G900VVRU1BOA8_G900VVZW1BOA8_VZW from sammobile.com
When flashing with odin i get the same error " Your device didn't start up successfully......"
Also, I attempted to update from zip and I received an error "E footer is wrong" and "E signature verification failed"
Again any suggestion are appreciated.
Click to expand...
Click to collapse
Try a factory data reset and clear cache from the stock recovery. You can also try Nand Erase All and Phone EFS Clear in Odin with the tar and pit files..
clarification
I have never done a Nand Erase All and a bit hesitant to do so with out clarification.
Is the suggestion to have the full tar file.
G900VVRU1BOA8_G900VVZW1BOA8_VZW.tar in AP
KLTE_USA_VZW.pit in PIT
and have the following
Auto Reboot
F. Reset Time
Nand Erase All
Phone EFS Clear
Then click start?
Misterxtc said:
Try a factory data reset and clear cache from the stock recovery. You can also try Nand Erase All and Phone EFS Clear in Odin with the tar and pit files..
Click to expand...
Click to collapse
tan0892 said:
I have never done a Nand Erase All and a bit hesitant to do so with out clarification.
Is the suggestion to have the full tar file.
G900VVRU1BOA8_G900VVZW1BOA8_VZW.tar in AP
KLTE_USA_VZW.pit in PIT
and have the following
Auto Reboot
F. Reset Time
Nand Erase All
Phone EFS Clear
Then click start?
Click to expand...
Click to collapse
Yes that should do it for you. I forgot exactly what Nand erases but it won't hurt, I've done it many times.
Still failed with same error messages. I have tried this with ALL_VZW_G900VVRU1ANHA_G900VVZW1ANHA_2525521_REV00_user_low_ship_MULTI_CERT.tar.md5 and G900VVRU1BOA8_G900VVZW1BOA8_VZW with no luck.
Misterxtc said:
Yes that should do it for you. I forgot exactly what Nand erases but it won't hurt, I've done it many times.
Click to expand...
Click to collapse
tan0892 said:
Still failed with same error messages. I have tried this with ALL_VZW_G900VVRU1ANHA_G900VVZW1ANHA_2525521_REV00_user_low_ship_MULTI_CERT.tar.md5 and G900VVRU1BOA8_G900VVZW1BOA8_VZW with no luck.
Click to expand...
Click to collapse
I would take it to a Verizon or BestBuy store and see if they will try seeing that this isn't working for you.
Update 2
Best Buy - can not do anything with it.
Verizon- Since I am prepaid and never had this device on this line they can not help
Samsung - offered me to send in the device to be re flashed. However, it is "out of warranty" due to more then 1 year old manufacture. --- Yes it was released April 11 2014 and I explained this to the friendly fella on the other line for about 45 minutes till he got me to his supervisor. Which then told me the only person that can over ride the out of warranty statues is the repair service center. The flash would be free. However, if anything is physically wrong with the device it will not be covered. With how non of the flash seem to work I am leaning towards this being a failure with the on board storage.
If any one has any suggestions before Monday please let me know otherwise I will send the phone in to see what Samsung has to say. I will update the posting once I find out more. .
tan0892 said:
Best Buy - can not do anything with it.
Verizon- Since I am prepaid and never had this device on this line they can not help
Samsung - offered me to send in the device to be re flashed. However, it is "out of warranty" due to more then 1 year old manufacture. --- Yes it was released April 11 2014 and I explained this to the friendly fella on the other line for about 45 minutes till he got me to his supervisor. Which then told me the only person that can over ride the out of warranty statues is the repair service center. The flash would be free. However, if anything is physically wrong with the device it will not be covered. With how non of the flash seem to work I am leaning towards this being a failure with the on board storage.
If any one has any suggestions before Monday please let me know otherwise I will send the phone in to see what Samsung has to say. I will update the posting once I find out more. .
Click to expand...
Click to collapse
What they mean by physically wrong is if there is water damage or something that YOU did. If the phone crapped out and blew a capacitor then they should still cover it.
Also they would call you and ask if you wanted to go through the repair if there was damage in which case you would decline and ask them to send it back
Sent from my SM-G900V using XDA Free mobile app
harrytery said:
What they mean by physically wrong is if there is water damage or something that YOU did. If the phone crapped out and blew a capacitor then they should still cover it.
Also they would call you and ask if you wanted to go through the repair if there was damage in which case you would decline and ask them to send it back
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
Nope the phone is in good shape no cracks/liquid damage.
However, the system that Samsung has shows the phone out of warranty which is on my RMA ticket too and that's what I debated with their phone rep about for 45 minutes since release date was April 11 2014.
*02/12/2015//20:04:53//0001773863//Telephone//ASC*
2/12/2015 7:04 PM-Chien Tran: The unit is shipped.
*02/12/2015//18:34:06//0001773863//Telephone//ASC*
2/12/2015 5:33 PM-PBA Inspection: The unit has left the technician. SOLUTION: BER
*02/12/2015//18:34:05//0001773863//Telephone//ASC*
DEVICE ROOTED/Software not authorized has been found on device
*02/12/2015//09:14:28//0001773863//Telephone//ASC*
2/12/2015 8:13 AM-Degitu Yismaw: The unit has been received. Pack Condition: Fair Packaging (Box & Cushion)
thread from Samsung tracking
I am guessing this means it is bricked and Samsung will not help.
I should be getting the phone next week. Any other suggestions appreciated.
Hey man let's try to help each other out... I'm also in the same exact situation...
My phone keeps rebooting to the "Samsung powered by Android" logo and turns off and then repeats it again until I take out the battery.
I can't even download the stock 5.0 file from the samsung website because my internet is too slow...
Try only clicking "auto reboot" and "reset time F" and run the "G900VVRU1BOA8_G900VVZW1BOA8_VZW.tar.md5" file on AP.
Btw, do you have the unzipped file by any chance?
jkim204 said:
Hey man let's try to help each other out... I'm also in the same exact situation...
My phone keeps rebooting to the "Samsung powered by Android" logo and turns off and then repeats it again until I take out the battery.
I can't even download the stock 5.0 file from the samsung website because my internet is too slow...
Try only clicking "auto reboot" and "reset time F" and run the "G900VVRU1BOA8_G900VVZW1BOA8_VZW.tar.md5" file on AP.
Btw, do you have the unzipped file by any chance?
Click to expand...
Click to collapse
Sammobile site is slow because they want you to pay for the faster downloads.
I have downloaded 1 from sammobile.com as well overnight but didn't do anything different for my issue.
Your's sounds a bit different. If you can get one of these stock full tar files you should be good to flash in ODIN.
If that doesn't work do a reset/wipe device with Home + Vol Up + Power before and after flash sometimes helps
This thread has some good links to stock tar with everything.
http://forum.xda-developers.com/showpost.php?p=53447942
galaxy S5 sm-g900v firmware problem
hey man mine do the same , SM-G900V its a samsung from verizon, i just bought it because i thought it was a software problem,
it keeps rebooting and on the startup screen appears a padlock and it say "COSTUM"
sometimes it keeps a few minutes on, somtimes its frozen and restart,
This is crazy, right now i live in the dominican republik, and i dont know if i must send it to verizon
temd said:
hey man mine do the same , SM-G900V its a samsung from verizon, i just bought it because i thought it was a software problem,
it keeps rebooting and on the startup screen appears a padlock and it say "COSTUM"
sometimes it keeps a few minutes on, somtimes its frozen and restart,
This is crazy, right now i live in the dominican republik, and i dont know if i must send it to verizon
Click to expand...
Click to collapse
Sorry to all that had this problem and didn't find a fix but to those that still have a Verizon s5 this may help.
I had the same problem with this S5 I'm playing with and I fix it by using odin3 v3.10 to flash the kernel again.
Dropped the Kernel the AP in odin. Everything was still there after i flashed it pic's / text and app all still there.
And the COSTUM on the screen means you have unlocked the kernel and one need to be flash.
hit thanks if this help
sounds to me like you guys have the wrong bootloader and are trying to downgrade to older firmware than the bootloader will allow. Try downloading one of the latest 6.0 firmware packages and flash that. I would imagine that will solve your issue.
Hello all. I'm here today seeking help with a problem I've been having with my note 4. A few weeks ago, the phone randomly started lagging really bad, reboots by itself and sometime fails to boot giving the "mmc read error". Usually requires several battery pulls to get it working again. Had this problem during 5.1.1, upgrading to 6.0.1 has done nothing. I have tried booting in to safe mode, clearing cache partition and a factory reset, all in vain. Phone is stock and clean, called Samsung and was politely told to "go f*** myself" since the 1 year warranty is over. Phone is Canadian. Thanks to all those who can help.
Hello - I've just had this very same error in the past 2 weeks and only fixed it today.
MAKE SURE YOU BACK EVERYTHING UP ASAP - NO EXCUSES.
Its a hardware failure I'm afraid.
I had to take my phone into the Samsung service centre today, and they replaced the motherobard after they confirmed it as dead.
My phone has the exact same symptoms as yours (lag, reboots, booting only into download mode), except that mine eventually refused entirely to turn on. Im not joking; the next time that it does turn on, make ure you do a phone and SD card full back up before you lose everything (pictures and such like).
I dont know about you, or where you are located, but my Note 4 has a 2 year warranty (Im in the UK) and I received it a year last March ago. Still well within warranty.
Alternatively, you could have a look on ebay for a new motherboard and replace it yourself.
Good luck!
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.
I didn't see an explanation of the purpose of the pit process ; could someone explain?
I am very familiar with custom roms and kernels, Pit is new to me..
Thanks
Wilsonb said:
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.
I didn't see an explanation of the purpose of the pit process ; could someone explain?
I am very familiar with custom roms and kernels, Pit is new to me..
Thanks
Click to expand...
Click to collapse
Hi Wilson,
welcome to the club, I am having the exact same problem now.
And bad news first, nothing will help you/us except a change of the motherboard... So bring it to a Samsung service center, the only thing you could do.
Believe me, I tried everything there is to try, including full wiping with flashing PIT files, etc. etc.
Forget it!
This is a hardware issue, as the mmc's are faulty and die after a year. Great.
Just to inform you, a pit file contains the infos about the partitions on the phone, their sizes, file system, etc.
So if you somehow compromised the structure or filesystem of the partitions, you could revert them back to the stock format.
Yeah, but doesn't help if your flash memory is corrupt on hw level...
Hello guys,
I am wondering if one could swap the logic board on a Note 4. A friend of mine gave me her Note 4 that showed signs of a hardware defect (mmc), e.g. random reboots, restarting into recovery mode or even fails to start at all.
I tried everything to fix the phone like flashing a repair Firmware including Pit-File and so on - but the phone keeps saying mmc_read fail and Odin won't flash.
So it seems to be a hardware problem, that is, the eMMC is very possibly damaged since TWRP keeps telling me that it cannot repair the file system due to Invalid Partition.
I found this exchange board on ebay: It's from a Note 4 N910F 32GB - Exact my model. However, mine is from Germany, and the one from ebay is from the US... would this be a problem?
Also I read about an EMEI code that is different on every board - anyway to solve this?
Thank you in advance!
PS: I've managed once to flash the repair FW (after a lot of tries) and it indeed worked out for a couple of hours. But then, restart and the phone didn't went back on. After battery being pulled out and back in, I only could go into recovery -> mmc_read fail. So this underpins my suggestion of a corrupted eMMC...
How did you get on with this - any solution? Where did you source your mobo? Mine's developed an issue and I'm struggling to find a replacement.
Hey guys!
I'm posting here in hopes someone could help me with my issues.
First and foremost, the phone is behaving erratically since the latest official update.
Phone was unrooted and untouched, only by official OTA updates.
-After the latest official OTA update, the phone hangs, reboots, sometimes when I try to unlock my phone it just doesn't respond to commands, sometimes it doesn't get past the first screen that shows when you power up the phone.
-I tried flashing a custom ROM for the first time and I got "mmc write error". I couldn't flash any other ROM, neither using Odin or by trying to restore the phone through Kies. The phone encountered the MMC write error with anything I tried to flash (this was happening at system img).
-I then tried the "fix mmc write error" guide here on XDA which promised to fix the error, but it didn't work. I followed all the steps and even used the repartition option with the provided .PIT file.
-Then I flashed the Philz touch recovery, rooted, and I formatted every partition besides the most important ones like EFS.
-Now I was able to restore the phone with Kies and afterwards I was able to flash any custom ROM (tried a bunch and the phone behaves bad (the same) on any ROM. Some ROMs don't even boot).
-I don't remember where, but I've read that the latest official update for the N910F screws something in the bootloader, and makes the phone behave eratically. Is there any known fix for this? Is there any bootloader I can flash so that the phone will work fine as before? And if so, what version should I use?
-I've read around and it was suggested that the battery might be causing these issues. So I went out and bought a new genuine note 4 battery and replaced it.. Sadly it didn't fix the issue.
I'm now on the custom RamRom with their custom RamKernel (for the 910F variant) and sometimes it works perfectly, other times it just hangs and is unresponsive until I pull the battery out and do a fresh boot.
I would of returned the phone in a heartbeat, but it's out of warranty, and it's such a shame it worked perfectly fine before the latest update. I feel it's Samsung's fault for the bad behavior of the phone but there's no way I can hold them responsible now, with the phone out of warranty and with the knox counter tripped.
Sorry for posting this big block of text and thanks to anyone reading it / shedding some light on my problems
Thanks!
Bro something similar happened to me as well .. even I did purchase new battery as everyone and also repair service guy said it's due to battery but that didn't solved the issue ..
Kindly check this xda post by me , it may help you.
https://forum.xda-developers.com/note-4/help/weird-white-bar-booting-sm-n910g-t3529413
adrscu said:
Hey guys!
I'm posting here in hopes someone could help me with my issues.
First and foremost, the phone is behaving erratically since the latest official update.
Phone was unrooted and untouched, only by official OTA updates.
-After the latest official OTA update, the phone hangs, reboots, sometimes when I try to unlock my phone it just doesn't respond to commands, sometimes it doesn't get past the first screen that shows when you power up the phone.
-I tried flashing a custom ROM for the first time and I got "mmc write error". I couldn't flash any other ROM, neither using Odin or by trying to restore the phone through Kies. The phone encountered the MMC write error with anything I tried to flash (this was happening at system img).
-I then tried the "fix mmc write error" guide here on XDA which promised to fix the error, but it didn't work. I followed all the steps and even used the repartition option with the provided .PIT file.
-Then I flashed the Philz touch recovery, rooted, and I formatted every partition besides the most important ones like EFS.
-Now I was able to restore the phone with Kies and afterwards I was able to flash any custom ROM (tried a bunch and the phone behaves bad (the same) on any ROM. Some ROMs don't even boot).
-I don't remember where, but I've read that the latest official update for the N910F screws something in the bootloader, and makes the phone behave eratically. Is there any known fix for this? Is there any bootloader I can flash so that the phone will work fine as before? And if so, what version should I use?
-I've read around and it was suggested that the battery might be causing these issues. So I went out and bought a new genuine note 4 battery and replaced it.. Sadly it didn't fix the issue.
I'm now on the custom RamRom with their custom RamKernel (for the 910F variant) and sometimes it works perfectly, other times it just hangs and is unresponsive until I pull the battery out and do a fresh boot.
I would of returned the phone in a heartbeat, but it's out of warranty, and it's such a shame it worked perfectly fine before the latest update. I feel it's Samsung's fault for the bad behavior of the phone but there's no way I can hold them responsible now, with the phone out of warranty and with the knox counter tripped.
Sorry for posting this big block of text and thanks to anyone reading it / shedding some light on my problems
Thanks!
Click to expand...
Click to collapse
Your facing emmc failure *your internal storage is corrupted* After a certain amount of read/writes, it ends up crapping out.
short note you may find a workground for this problem but at the end changing the motherboard is the only solution for you..
Sent from my SM-N910G using Tapatalk
Hey guys and thanks for the replies.
Amar.B said:
Your facing emmc failure *your internal storage is corrupted* After a certain amount of read/writes, it ends up crapping out.
short note you may find a workground for this problem but at the end changing the motherboard is the only solution for you..
Sent from my SM-N910G using Tapatalk
Click to expand...
Click to collapse
While this might seem plausible, it is very hard for me to accept, because prior to having these problems, I never flashed anything to the phone, apart from official OTA updates. I find it really hard to accept that the part of the MMC - internal memory which is assigned to the operating system has been written so many times as to cause failure..
adrscu said:
Hey guys and thanks for the replies.
While this might seem plausible, it is very hard for me to accept, because prior to having these problems, I never flashed anything to the phone, apart from official OTA updates. I find it really hard to accept that the part of the MMC - internal memory which is assigned to the operating system has been written so many times as to cause failure..
Click to expand...
Click to collapse
Believe me i use to feel the same but now i am all careful not to loose my warranty i am on stock rom too knox is not triggered.. Emmc failure is a time bomb lots of people are having the same problem it's a hardware defect doesn't matter if you're custom rom or stock rom.. my phone is almost new 8 month old and am having a problems with phone already. phone shutting down at 20% and going into bootloop i have to charge the phone so it could boot up normally now i found many users are facing the issues..
The weird part is only the snapdragon variants are facing emmc failure while exynos don't
Sent from my SM-N910G using Tapatalk
Amar.B said:
Your facing emmc failure *your internal storage is corrupted* After a certain amount of read/writes, it ends up crapping out.
short note you may find a workground for this problem but at the end changing the motherboard is the only solution for you..
Sent from my SM-N910G using Tapatalk
Click to expand...
Click to collapse
Amar.B said:
Believe me i use to feel the same but now i am all careful not to loose my warranty i am on stock rom too knox is not triggered.. Emmc failure is a time bomb lots of people are having the same problem it's a hardware defect doesn't matter if you're custom rom or stock rom.. my phone is almost new 8 month old and am having a problems with phone already. phone shutting down at 20% and going into bootloop i have to charge the phone so it could boot up normally now i found many users are facing the issues..
The weird part is only the snapdragon variants are facing emmc failure while exynos don't
Sent from my SM-N910G using Tapatalk
Click to expand...
Click to collapse
Thanks for your help, Amar! I've put some thought into it and I'm considering looking for a new motherboard. Maybe even an exynos one if it fits.
I'm very puzzled as I own other phones too and it's the first time something like this is happening.
Thanks again!
adrscu said:
Thanks for your help, Amar! I've put some thought into it and I'm considering looking for a new motherboard. Maybe even an exynos one if it fits.
I'm very puzzled as I own other phones too and it's the first time something like this is happening.
Thanks again!
Click to expand...
Click to collapse
All the best mate and it's my pleasure.. cheers
Sent from my SM-N910G using Tapatalk
My note 4, randomly crashed, running completely stock.
Began bootlooping and hasn't stopped.
Have downloaded firmwares from Samsung-Firmware . org, as SamMobile will literally not allow me to download anything for free??
No firmware has worked on the device, Have tried numerous PDA versions as I am unsure which the phone originally is.
The first firmware gave the error "dm-verity verification failed" in the recovery menu.
Have wiped cache and data.
Note: This is actually the second N910F which had corrupted itself and stopped working.
Help! :angel:
Do you want to recover some data from it?
If Not than you can try factory reset from Recovery menu.
Other than that it might be memory corrupted or your battery.
Try to change the battery.
a602820922 said:
Do you want to recover some data from it?
If Not than you can try factory reset from Recovery menu.
Other than that it might be memory corrupted or your battery.
Try to change the battery.
Click to expand...
Click to collapse
No data to recover, have tried factory reset from recovery menu, sure will try another battery.
a602820922 said:
Do you want to recover some data from it?
If Not than you can try factory reset from Recovery menu.
Other than that it might be memory corrupted or your battery.
Try to change the battery.
Click to expand...
Click to collapse
New battery: Allowed the phone to boot past the first "Samsung Note 4" screen to : "Samsung" logo, but the phone made a loud beep/screech.
If you want to reflash the Stock ROM search for a version on https://updato.com
I just reflashed mine (g910f) even twice as I had an Infini-Boot, too. After cleaning Dalvik/Cache and formatting data, taking out the battery, after some time it suddenly displayed that it's going to setup apps and it works since then ...
So maybe just be patient.
TheEnda619 said:
My note 4, randomly crashed, running completely stock.
Began bootlooping and hasn't stopped.
Have downloaded firmwares from Samsung-Firmware . org, as SamMobile will literally not allow me to download anything for free??
No firmware has worked on the device, Have tried numerous PDA versions as I am unsure which the phone originally is.
The first firmware gave the error "dm-verity verification failed" in the recovery menu.
Have wiped cache and data.
Note: This is actually the second N910F which had corrupted itself and stopped working.
Help! :angel:
Click to expand...
Click to collapse
to get the latest stock rom for your device, free and fast
look what you have to do:
download this (windows ) application and install it on your windows pc.
This is the aplication that will allow you to search and download the latest stock rom for your phone.
It connect to Samsung servers and in very little time you will have a new stock rom on your pc.
choose samfirm 3.06
extract it on a folder on your PC and run samfirm.exe
in the opening menu type
SM-N910F(or T/V/W etc your phones model)
REGION..... xxx (your region code)
these 2 you can find in a sticker under your battery if you open the phone and take off the battery
tick '' BINARY NATURE''
(If you dont tick BINARY...'' you will get the whole stock rom in one file xxxx.tar.md5 to flash it in the oding using the AP tab)
CHECK UPDATES>DOWNLOAD
THIS WAY YOU WILL GET THE LATEST STOCK ROM FOR YOUR PHONE/REGION
Binary nature means the rom split in 4 files
1. BL- bootloader
2.AP - rom
3. CP - modem
4. CSC - Customer support code(region/country)
This is what a stock rom is consist of
this kind of rom is also called REPAIR ROM, because you can use it to repair your phone.
If you look in odin you will find exactly these 4 entries.
So you can put each in the appropriate box and flash them all and so have a stock rom.
push start
Wait until rom flashes and phone reboots.
Hopefully it will solve your problem and everything will go as we all wish to.
BUT, from what you are describing, i am afraid for 2 things:
1. Your battery is almost dead, thats the good scenario .
With 20 $ you will solve it.
So new battery, new rom> problem solved, or
2. You are starting to have the emmc failure on your phone.
Thats a tough one.
Lets hope its not the case.
Just in case
https://forum.xda-developers.com/note-4/help/note-4-freezing-restarting-t3348821
https://forum.xda-developers.com/note-4/snapdragon-dev/note-4-debrick-img-t3488114
good luck my friend