Database Users

Note3 SM-9005 Continuous Reboot Loop When USB Wire Is Connected for Charging or to PC

Hello.
I'm having an International Unlocked Note 3 - SM-9005 using the method in this thread : http://forum.xda-developers.com/showthread.php?p=46511887#post46511887
It's been 2 months now, and there were no problems till now, and since the last 5 days, I've been noting something strange :
Whenever I connect the USB cable for charging, or when I connect the phone using the cable to my PC, the phone keeps rebooting. Continuously. Sometimes it resumes charging after 3 or 4 reboots. Sometimes the loop continues.
The only major changes I have made recently, was installing the Root External 2 Internal app to try swapping the cards. It didn't work fully though. And I have also installed one of those 64GB Sandisk cards. The card seems to work alright.
And I also recently bought a Yoobao 13000mAh YB-651 PowerBank.
I first noticed the reboots when I connected this powerbank at the 4th or 5th time. After that, the problem started whenever I connect the USB cable.
I tried changing the cables, still same result.
I have also tried full factory reset and data/cache wipe at recovery but still no change.
I have tried removing the battery and reinserted, but ditto. Also removing the SD card didn't do anything.
Could it be the powerbank somehow messed up my battery which is causing this problem?
Before I change the battery, I would like to know if the battery is causing this problem.
Today, after the factory reset I noticed the carrier signal is abysmal. Just one or 2 bars, and even complete no-signal. This never happened before, and the bars were almost always full previously from where I'm using it.
All other functions of the phone seems to be working well.
Thank you for any help.

Anyone noticed similar problems?

Flash this and see if it fixes your problems:
http://forum.xda-developers.com/showthread.php?t=2507403
Download the zip and flash it in CWM

zylor said:
Flash this and see if it fixes your problems:
http://forum.xda-developers.com/showthread.php?t=2507403
Download the zip and flash it in CWM
Click to expand...
Click to collapse
Thanks.
Is it safe to flash that in my phone? Currently my phone is working good. Except for the sudden drop in the carrier signal reception quality recently.
It's only when I connect a USB cable to the phone that it goes into continuous reboot loops. If I remove the cable or switch off the power source, then it goes away.
It does not have the random reboots as reported by some.
It goes out of the loop if I remove the cable and reconnect while it's rebooting, and then I can continue using it as it charges.
It's weird and annoying.
Currently I have already flashed the latest official rom from Samsung. And the knox is maintained at 0x0. And the System Status is Official.

Well if you still have it with knox untouched, go to a Samsung Repair Center...

zylor said:
Well if you still have it with knox untouched, go to a Samsung Repair Center...
Click to expand...
Click to collapse
Yes, I'm going to the Service Centre tomorrow. Thank You.

Hmm...I just noticed something.. the reboot problem went away after I removed and reinserted the SIM card....

The problem re-appeared.
So I just sent it to the Samsung Service Centre.
Took 4 days. They said that they have changed the PBA (Phone Board Assembly?).
Now everything's good.
Fortunately I didn't trip the knox, and my phone was still under warranty, even after rooting as I have mentioned in the link in my first post. I flashed the latest official rom to make the Device Status to Official again, before sending the phone for service.
And how do I edit the title of this thread? I would like to add "Solved" to it. Thanks.

The problem re-appeared.
So I just sent it to the Samsung Service Centre.
Took 4 days. They said that they have changed the PBA (Phone Board Assembly?).
Now everything's good.
Fortunately I didn't trip the knox, and my phone was still under warranty, even after rooting as I have mentioned in the link in my first post. I flashed the latest official rom to make the Device Status to Official again, before sending the phone for service.
And how do I edit the title of this thread? I would like to add "Solved" to it. Thanks.

please go in the developers settings and turn off debug usb
i had a similar problem with mine using win7 on vmware

[Q] Problem with galaxy s4 i9500 lollipop update(India)

Hello,
I updated my galaxy s4 gt-i9500 - Indian exynos version to android lollipop 5.0.1
After the update, the device is very fluidic and I never had any glitch. The update seems to be pretty stable as well. But around 2 weeks after this update I got this problem- my device got factory data reset on its own with everything erased from both internal memory and sd card as well. This happened when my device was kept on a table and when I saw it, it was turning on and then i found that startup screen that comes after the reset. After around 1 week, when I was using my phone a random message appeared on my screen saying "erasing sd card" I was pretty much sure that it was the same problem so I turned off my device, when I turned it on, everything from my sd card was erased, but nothing happened to phone memory. When I went to service centre, they were saying it could be a problem of the update. They seem to be not knowing about the problem and offered me to go back to kitkat. I dont want to go back to kitkat so my last resort was xda-developers. Please help.

What exactly do you want from XDA?

I want a solution to my problem.
I want to know what is happening with my deviceand a possible solution for my problem.

NOTE 4 910F ddi: mmc_read failed

Hi! Lately I have problem with my Note 4 6.0.1 N910FXXS1DPHB (Germany). Phone wasn't rooted only on original firmware from 4.4.4
After latest upgrade from 5.1.1 to 6.0.1 I noticed the problems below:
1. more lags (a huge lags often!)
2. often logout with asking about password (fingerprint doesn't work after restart)
3. Odin screen with " ddi: mmc_read failed" similar like in that http://forum.xda-developers.com/showthread.php?t=2596979 from time to time
I consider to use odin and SmartSwitch to make factory reset and get fresh ROM. Nevertheless I am a bit anxious that odin screen. Can it be hardware problem (internal memory)?
Obviously I have warranty and I don't need to root my Note.
Thank you in advance!
Slawek

ask for a replacement

Can I check myself that is it mmc problem?

slawekj74 said:
Hi! Lately I have problem with my Note 4 6.0.1 N910FXXS1DPHB (Germany). Phone wasn't rooted only on original firmware from 4.4.4
After latest upgrade from 5.1.1 to 6.0.1 I noticed the problems below:
1. more lags (a huge lags often!)
2. often logout with asking about password (fingerprint doesn't work after restart)
3. Odin screen with " ddi: mmc_read failed" similar like in that http://forum.xda-developers.com/showthread.php?t=2596979 from time to time
I consider to use odin and SmartSwitch to make factory reset and get fresh ROM. Nevertheless I am a bit anxious that odin screen. Can it be hardware problem (internal memory)?
Obviously I have warranty and I don't need to root my Note.
Thank you in advance!
Slawek
Click to expand...
Click to collapse
use search, there are many threads that duscuss this issue:
http://forum.xda-developers.com/note-4/help/n910f-problems-emmc-read-fail-flashing-t3456721
http://forum.xda-developers.com/note-4/help/note-4-freezing-restarting-t3348821

slawekj74 said:
Can I check myself that is it mmc problem?
Click to expand...
Click to collapse
The best thing you can do is to flash another time the original firmware, adding the proper pit file for your model. This will repartition your internal memory. Worked for me on a completely dead 910f, so yours got more chance....
If after this steps the lags remains, only thing to do is asking for motherboard replace.....
Good luck

slawekj74 said:
Hi! Lately I have problem with my Note 4 6.0.1 N910FXXS1DPHB (Germany). Phone wasn't rooted only on original firmware from 4.4.4
After latest upgrade from 5.1.1 to 6.0.1 I noticed the problems below:
1. more lags (a huge lags often!)
2. often logout with asking about password (fingerprint doesn't work after restart)
3. Odin screen with " ddi: mmc_read failed" similar like in that http://forum.xda-developers.com/showthread.php?t=2596979 from time to time
I consider to use odin and SmartSwitch to make factory reset and get fresh ROM. Nevertheless I am a bit anxious that odin screen. Can it be hardware problem (internal memory)?
Obviously I have warranty and I don't need to root my Note.
Thank you in advance!
Slawek
Click to expand...
Click to collapse
Several threads exist on this issue and the conclusion we've come to in the T-Mobile Note 4 forums is replacement. In my experience, the issues got so bad that it rendered the phone unusable. Get it replaced under warranty while you still have it. Samsung denied my claim as I was out of warranty.

Phone has returned from service point - repaired. I will test it tomorrow

Good news, hopefully the issue has been sorted out.
My note4 has the same problem but although still under warranty, it's rooted. Highly doubt that Samsung will repair it for free.

xhanatos said:
Good news, hopefully the issue has been sorted out.
My note4 has the same problem but although still under warranty, it's rooted. Highly doubt that Samsung will repair it for free.
Click to expand...
Click to collapse
I held back myself from make my N4 rooted until Android 6 has appeared
So, mainboard has been changed and some parts of case ( very nice due to some scrapings on silver edge of phone).
New firmware was installed - XEF (France) instead of my previous DBT (Germany). Original CSC code is empty.

possible workaround
https://forum.xda-developers.com/note-4/help/workaround-mmcreadfailed-mmcwritefailed-t3564869

Swap Logic Board on Note 4 N910F 32GB possible? (due to dead/damaged eMMC)

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.

Note 4 G910F Snapdragon weird issues / flashing and usage

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