Database Users

(New After JK4 Froyo) POLL:Bell I9000M Internal SD Failures

I think we need a new Poll for anyone that needs to change their answer after upgrading to JK4...Perhaps give JK4 a few days to make sure it's running smoothly before voting...
(Thanks Electroz for the original Poll!)

I got to experience 5 minutes of froyo before multiple force closes and then dead. It went into a reboot loop never getting past the white i9000m logo.
Updated with Kies (latest version--no registry mod)
I was stock JH2.
No lagfix ever installed
I've never flashed any rom.
Sorry guys, Kies is not safer...
Now I have to convince Bell to honor the warranty...

I don't think there are any issues with Kies or Odin for flashing. I've flashed many times, sometimes 4 times in one day and I've never had any issues. There does seem to be the usual SD issues but I also think there is a USB communications issue. There have been many reports of data corruption while writing to internal/external SD with large files. I personally had an issue pulling large files off of internal/external SD. I think if this problem occurs while flashing new firmware it could cause some corruption that could be noticeable right away or after a bit of use. The partitioning on this device seems to be more sensitive than others and a hiccup while flashing could cause some major issues.

trinitonesounds said:
I got to experience 5 minutes of froyo before multiple force closes and then dead. It went into a reboot loop never getting past the white i9000m logo.
Updated with Kies (latest version--no registry mod)
I was stock JH2.
No lagfix ever installed
I've never flashed any rom.
Sorry guys, Kies is not safer...
Now I have to convince Bell to honor the warranty even though I'm on Rogers...
Click to expand...
Click to collapse
They don't care.
I went today and they just took it and didn't ask anything that sounds like they cared about if I am not with Bells.
I gave them my bro's phone number and info since he is with Bell, just to avoid any problems.
Just don't say something like the phone is "unlocked" lol...the phone is dead so they won't find out anyways if you don't tell them. They won't ask either.
Just tell them that you upgraded through kies and it got the problem.

it's a hardware defect, if it dies it dies
after all the evidence we've seen (all the reports by our members)
if it's good it will work regardless of what firmware you use, and regardless of the way you flash the firmware
the lag fixes and froyo just accelerates the problem and makes it more evident sooner than later
which is good in a way, it's better to find out before your warranty runs out

ok im pretty sure mine is a full brick. maybe you can tell me.
less than 24 hours after updating to 2.2 i started getting all of these errors in various programs, so i rebooted the phone, but after it plays the little intro thingy the screen just goes black and thats it. cant do anything else. i tried a factory reset and still the same thing. so is that it?
also. i bought this phone at best buy, but network unlocked it to use on rogers. should i be contacting samsung directly about a replacement/fix? anyone here done that? im REALLY scared that are gonna give me a phone that i am unable to network unlock.
thanks for any info.

some one welcome me to the club of defund Bell Internal SD
http://forum.xda-developers.com/showthread.php?t=867157

@evil-doer
I am in the exact same boat as you! I bought from Best Buy, then unlocked to use on Rogers. Last night, I updated to official Froyo through Kies, and then it just died on me today (many app force closes and then just drop dead). When I get into recovery mode, it says can't mount the SD card.
I think I will just go to a Bell Store tomorrow and see what happens. I will let you know how it goes. Please let me know how yours go too. Thanks.

Mines a goner too
Same issue, have a forced app closure, shut the phone off and it wouldn't start up anymore. Just flashes the Galaxy S GT-I9000M white logo non-stop now.
I can put it into download mode and load up 2.1 (stock) and get to the coloured Galaxy S logo, but then it just goes to a black screen. In recovery mode, it shows stuff about not being able to mount the SD on E:\. I'd assume that's the internal flash?
Luckily I haven't had it for >30 days (on Virgin Mobile) so I'm hoping I can just exchange it and be on my way. I have to call them though apparently since I bought it online.

i did not have Force Close, the phone just got really really hot during batch restore of TitaniumBackup

jdrom said:
Mines a goner too
Same issue, have a forced app closure, shut the phone off and it wouldn't start up anymore. Just flashes the Galaxy S GT-I9000M white logo non-stop now.
I can put it into download mode and load up 2.1 (stock) and get to the coloured Galaxy S logo, but then it just goes to a black screen. In recovery mode, it shows stuff about not being able to mount the SD on E:\. I'd assume that's the internal flash?
Luckily I haven't had it for >30 days (on Virgin Mobile) so I'm hoping I can just exchange it and be on my way. I have to call them though apparently since I bought it online.
Click to expand...
Click to collapse
how did you load up 2.1? i can put my phone in download mode but nothing happens after that. and how do you get in to recovery mode?

Well I can load up 2.1 with Odin and with the auto reboot option checked, it'll go straight to recovery mode after flashing (for whatever reason). Otherwise I can't get to recovery mode.

Success so far... 12 hours after upgrade.
I sucessfully upgraded to Froyo yesterday.
I had problems with Kies at first and had to do a factory reset before the upgrade. The FileSearcherforKiesFix.exe altough it detected two bad files wasn't enough to make Kies happy.
This phone was bought in october and had the voodoo lagfix installed from the begining. I disabled the lagfix before the froyo upgrade.
My previous samsung phone; the GT-8000 (Omnia II) did have an internal SD card failure after a few months of operation... Also a Bell phone. I'm really concerned by that trend with Samsung and Bell...

I recommend NOT to upgrade. With JH2 I had NO problems. I upgraded to JK4 and about 24 hours later (this morning) I started getting force closes. XDA App. wouldn't open and just scrolling through memory management gave me haptic feedback (even though I had it disabled) and random closes. The phone became unusable fast. I tried a reboot and the phone booted to a black screen where only the buttons lit up. I went into recovery mode and I saw some dbdata error. I figured my phone was a goner. I ended up formatting the internal memory, clearing cache and then doing a factory reset. The phone is up and running now...but for how long.

Well... you're going to have upgrade eventually so best to do it now while you are under warranty in case something happens...
nemethb said:
I recommend NOT to upgrade. With JH2 I had NO problems. I upgraded to JK4 and about 24 hours later (this morning) I started getting force closes. XDA App. wouldn't open and just scrolling through memory management gave me haptic feedback (even though I had it disabled) and random closes. The phone became unusable fast. I tried a reboot and the phone booted to a black screen where only the buttons lit up. I went into recovery mode and I saw some dbdata error. I figured my phone was a goner. I ended up formatting the internal memory, clearing cache and then doing a factory reset. The phone is up and running now...but for how long.
Click to expand...
Click to collapse

How's that the case?

Stock JG9 w/ OCLF -> Stock JH2 (kies,voodoo lagfix) -> JK3 (Odin, Speedmod kernel w/ tweaks flashed through odin to get 2e back, no lagfix) -> JK4 (hacked kies, speedmod kernel w/ tweaks flashed through odin to get 2e back, no lagfix)
No SD failure so far, touch wood. Original phone purchased day after launch.

Mine died today, started getting FC and then the whole thing froze. I tried restarting it but after the samsung splash screen all I had were glowing buttons.
It ran fine for about a day on JK4 before that on JH2 it never gave any problems.
BTW it was stock updated through Kies.
The guy at the Bell store told me they never get these phones returned, this was a first for him. Either it was his first day on the job or it's typical Bell BS.

Just had my second phone die. The first one died after 28 days with no upgrade. This one after 8 days, 2 days after upgrading to Froyo...

Same thing happened to me this morning.. Froyo was working fine for just over a day and then this morning I turn on my phone, get a bunch of FCs.. I reboot.. get another bunch of FCs.. reboot.. and now it won't go through the "S" splash screen. When the screen disappears I press the buttons and it just glows..
I don't know if it's bricked or what.. when I run recovery I get this error.
E: can't mount /dev/block/mmcblkOp1 (I/O Error)
E: Copy_dbdata_media:can't mount SDCARD:
your storage not prepared yet, please use UI menu for format and reboot actions.
copy default media content failed.
Is this what everyone else is getting? And what are my alternatives?
If my phone is pooched then I'll be pretty pissed since this is my 3rd SGS, I gave the SGS up when it had issues in low reception and the 850 band lock fixed it. If this totally pooches my phone I'm never buying another Samsung mobile product again.

My Phone Keeps Randomly Rebooting

My G2 keeps randomly rebooting. Sometimes it will reboot without me doing anything to it, and sometimes it will reboot when I try to unlock it. The only thing I have done to the phone is root with the method in these forums. I haven't installed any non-market apps or anything. Since the root method was kind of suspicious, I suspect that is the problem. How do I un-root? I have tried the "back to stock" method, but nothing happened after I completed that. How can I resolve this issue? Does anybody else have this problem?
Edit: Even if rooting was not the cause of my problems I still need to un-root in case I need to take the phone back to Verizon.

paw123 said:
My G2 keeps randomly rebooting. Sometimes it will reboot without me doing anything to it, and sometimes it will reboot when I try to unlock it. The only thing I have done to the phone is root with the method in these forums. I haven't installed any non-market apps or anything. Since the root method was kind of suspicious, I suspect that is the problem. How do I un-root? I have tried the "back to stock" method, but nothing happened after I completed that. How can I resolve this issue? Does anybody else have this problem?
Edit: Even if rooting was not the cause of my problems I still need to un-root in case I need to take the phone back to Verizon.
Click to expand...
Click to collapse
I read something about beta chrome causing reboots...not sure if your using a beta version of chrome.

emplox said:
I read something about beta chrome causing reboots...not sure if your using a beta version of chrome.
Click to expand...
Click to collapse
Hmm I do not think that I have a beta version of chrome, but just in case, I disabled Chrome and installed Firefox instead. I will update if that appears to fix the problem.
Edit: Nope. The problem still exists.
Also, I managed to unroot using super SU. The problem is that it still says that my phone is rooted when I go to about>status.

I had the same problem today. It happened when I got a text. It rebooted like 3 times one after another. Then it just stopped. Weird.....
Anyone any ideas? I have the T-Mobile version. NOT ROOTED

Mine just shut off entirely no reboot I had to power it on. On the T-Mobile version
Sent from my LG-D801 using Tapatalk 2

Holy crap....mine just went into a reboot cycle for like 20 times. It happened while I was taking a photo. It also happened when I tried to unlock my device. Not very pleased right now. never had a single reboot on my gs4

Mines shut off like 5 times today no reboot it just shuts down lol so T-Mobile is sending me a brand new one and if that has problems to I may go back to my nexus 4 and wait for the nexus 5 or something this phone is amazing in every way except when I go to unlock and it is ******* shut down ugh
Sent from my LG-D801 using Tapatalk 2

[Q] Please help - S4 Keeps Rebooting - VIDEO

Hello All
My Samsung Galaxy S4 (GT-I9505) keeps on freezing then rebooting in an unusual way.
The problem is intermittent, it would constantly happen in certain periods and happen less frequently in other periods. At the moment, i can beerly use my phone for 1 minute before it does it again and again. And in this minute apps are just crashing. I get the pop-up messages of applications crashing. I tap ok only for the same message to instantly reappear.
Unfortunately, the process com.android.systemui has stopped
Unfortunately the process com.google.process.gapps has stopped
The issue would happen when the phone is in sleep mode (screen turned off), while im using it, in safe mode or even when its rebooting or on the splash screen.
I am using the original battery and charger that came with the phone and never flashed or rooted my phone. I have however had to flash it couple of months ago after it bricked all by itself. I used one of the firmwares from www.samsung-updates.com
See this video to understand exactly what is happening
https://drive.google.com/file/d/0B4l5hw87RbUXeUMzUkp5ZFZVMHM/view?usp=sharing
Please give me ideas/suggestions of what to do

omaral92 said:
Hello All
My Samsung Galaxy S4 (GT-I9505) keeps on freezing then rebooting in an unusual way.
The problem is intermittent, it would constantly happen in certain periods and happen less frequently in other periods. At the moment, i can beerly use my phone for 1 minute before it does it again and again. And in this minute apps are just crashing. I get the pop-up messages of applications crashing. I tap ok only for the same message to instantly reappear.
Unfortunately, the process com.android.systemui has stopped
Unfortunately the process com.google.process.gapps has stopped
The issue would happen when the phone is in sleep mode (screen turned off), while im using it, in safe mode or even when its rebooting or on the splash screen.
I am using the original battery and charger that came with the phone and never flashed or rooted my phone. I have however had to flash it couple of months ago after it bricked all by itself. I used one of the firmwares from www.samsung-updates.com
See this video to understand exactly what is happening
https://drive.google.com/file/d/0B4l5hw87RbUXeUMzUkp5ZFZVMHM/view?usp=sharing
Please give me ideas/suggestions of what to do
Click to expand...
Click to collapse
Have you tried to do a factory reset?

iJo09 said:
Have you tried to do a factory reset?
Click to expand...
Click to collapse
Yes I did a factory reset and wiped the cache

omaral92 said:
Hello All
My Samsung Galaxy S4 (GT-I9505) keeps on freezing then rebooting in an unusual way.
The problem is intermittent, it would constantly happen in certain periods and happen less frequently in other periods. At the moment, i can beerly use my phone for 1 minute before it does it again and again. And in this minute apps are just crashing. I get the pop-up messages of applications crashing. I tap ok only for the same message to instantly reappear.
Unfortunately, the process com.android.systemui has stopped
Unfortunately the process com.google.process.gapps has stopped
The issue would happen when the phone is in sleep mode (screen turned off), while im using it, in safe mode or even when its rebooting or on the splash screen.
I am using the original battery and charger that came with the phone and never flashed or rooted my phone. I have however had to flash it couple of months ago after it bricked all by itself. I used one of the firmwares from www.samsung-updates.com
See this video to understand exactly what is happening
https://drive.google.com/file/d/0B4l5hw87RbUXeUMzUkp5ZFZVMHM/view?usp=sharing
Please give me ideas/suggestions of what to do
Click to expand...
Click to collapse
1. It seems you recovered one image of one backup with the recovery.
2. SOLUTION: Reflash the firmware through ODIN. The latest for your phone is this one: HERE.

omaral92 said:
Yes I did a factory reset and wiped the cache
Click to expand...
Click to collapse
Try to flash firmware package with the latest version of ODIN and Sammy drivers, also use the original cable that came with the phone. Often, cables that aren't Samsung genuine fail to flash firmware.
If this doesn't solve your problem, then you might try a firmware reflash with PIT file. If nothing works, your processor (or motherboard) it's likely fried. Take it to a service centre

Joku1981 said:
1. It seems you recovered one image of one backup with the recovery.
2. SOLUTION: Reflash the firmware through ODIN. The latest for your phone is this one: HERE.
Click to expand...
Click to collapse
I have reflashed it using the firmware provided in the link but it is still playing up. any other suggestions?

[Q] Reboots after Lollipop

Verizon Note 3 here, I received the Lollipop ota today and thought no harm in taking it as I was already stuck without root on 4.4.4.
It worked ok for the first couple minutes, then a reboot, then same thing, about 5 minutes and a reboot. Sometimes ~2 minutes, seems using it in any situation made the reboots happen. I did a factory reset thinking that would clear things up. Unfortunately now it is even worse, as it's rebooting anywhere from the first touch to the screen, to about 15 seconds of activity, literally dozens of reboots.
I downloaded the update on my pc and installed via Odin hoping that the ota was just corrupted or some bad luck like that. Nothing changed at all.
It will idle after booting just fine, I just can't do much of anything, every touch of the screen feels like a roll of the dice. Every few reboots or so I can make it to settings maybe but haven't been able to actually change much of anything, not that it would seem to matter here.
I've flashed via Odin twice, cleared the cashe many times, factory reset 3 or 4 times. Am I screwed here? What else to try?
*UPDATE* I flashed back to 4.4.4 with Odin and no more issues. It appears that my device alone is completely incompatible with the new firmware.

I should also note that I tried airplane mode, safe mode, and removing the sd card with no improvements.

After hours of messing with this thing and nearly giving up, not half an hour after I post here for help, I seem to have found a solution, although hopefully not a permanent one. The problem was happening when I would touch the screen, not scrolling ever, but making selections. On a whim I turned off sound and bam, no crashes.
I would still love it if someone had some insight about this problem, or better yet a solution.
I'm not sure yet if it is just the keypress sound that is killing it, or all sounds. I never did have any issues with the stock keyboard clicks now that I think of it, only the menu press sound. In any case it's not every time it made the sound, just half the time or so. Anything anybody could add to this would be appreciated.
*Edit* Not a solution, but it did help.

Well it's not as stable as I'd hoped. More like before the first factory reset now, but still not good at all. The various sounds definitely trigger crashes quickly(menu options, volume pings, mp3 songs from sd card), but regular silenced menu presses do sometimes as well still. Phone also bootloops several times often before it can get booted stable and 100% always crashes immediately if I try to unlock the screen in the first 5-10 seconds after booting up. Not sure if I'll be able to call or text as it's too late to test that atm. I'll update tomorrow, any insight appreciated.

I would say a bad download but I don't remember if ODIN checks MD5 sums (pretty sure it does). I would do a full wipe and reflash the stock image with odin

I am 100% stock not rooted never been rooted 5.0 vzw and I have had a couple of reboots. Never ever had one on this phone before. My old note 3 was rooted but I got this replacement after the root exploits had all been closed.

ehh not all have been closed

What is the root exploit for Verizon Note 3 with 5.0?

recDNA said:
What is the root exploit for Verizon Note 3 with 5.0?
Click to expand...
Click to collapse
None at the current time but CVE-2014-8609 seems like it could be some use

I spoke too soon when I said the phone was usable now. At best 5 minutes of light use as anything seems to crash it now. I did get a fresh image and used it with Odin with exactly the same result which makes me think its my phones hardware or something. Just seems crazy that it was working just fine before the update. The reason I pushed to 4.4.4 and lost root is because my phone suddenly started an issue where it would crash when making or receiving calls. It wasn't caused by any new apps or anything, just out of nowhere. I tried everything then updated as a last resort, carelessly I went to 4.4.4 instead of staying at 4.4.2 and lost chance of root, but it solved the problem I was having. I wonder if the issue is related somehow.

I was able to odin back to 4.4.4 and it's working fine so far, I assumed that you would not be able to revert back like the last ota and just tried it as a nothing to lose last effort. This is very important news to anybody that is having major issues with 5.0. Maybe, just maybe I'll try it again if they make an update patch for reported issues.
But for now, 4.4.4 it is for me.

VZW Note 3 update to Lollipop
I just finished the Lollipop update and my phone is working great for the past 30 minutes. Seems a little slower then usual but have had no issues besides my phone locking up after downloading the update, may have been due to my phone running down to 14%, but after removing the battery for 20 secs and putting it back on, phone came back on, I plugged into charger and started the update. Will post later if I have any issues.

I have been trying unsuccessfully through odin to downgrade but it keeps failing in odin, I downloaded the official firmware from sammobile.

Just curious if u r tried reinstalling newer odin? Try different USB port and cable. At this point maybe even try different pc if u have access to 1

SM910F Note 4 5.1.1 Random Freezes and Restarts

Hello there xda.
I have a Samsung Galaxy Note 4 SM910F.
So what is happening to my phone is that whenever I am in any random app lets say reddit or even chrome for example. It will like freeze for a minute or two and then unfreeze.
In more extreme cases it will reboot.
So this happened randomly because I flashed a Stock unbloated 5.1.1 ROM from here back in december and everything was working smoothly and stuff. I had xposed installed and all my apps. Then in February it started with this random freeze/reboot. I had not installed anything else apart from what I had for the last 3 months.
So I restarted the phone, changed the battery and stuff to see whether that will fix it. However it didn't. So I formatted the phone (the soft type) just so I can install another ROM. So I tried another ROM, flashed the correct CP and BL and stuff and then just installed chrome and whatsapp. After an hour or two the same thing happened. So this time I factory reset he phone, like a complete wipe and I installed the unbloated ROM once again with few apps. Same thing happened...
So my last resort was to install Cyonagen Mod. After an hour or two same thing happened...
I don't know what is the problem. I read about some peoples phones emmc failing and thus the freezing, but I am not sure yet.
Please could you guys explain what I should do to fix this?
Thank in advance!

I have the same problem. Starting on mid january. I'm on stock 5.1.1 with root and twrp recovery
Tried backup and factory reset

I went back to stock after I factory reset the phone. And still had the same problems.
People say that its a hardware problem... So I guess I'll have to send it back to Samsung soon.
I think I tripped the knox. I just have to unroot and get it back once again to stock and send it back. I hope that they accept it.

i have the same problem. my model is SM-N910W8 and I bought it from 2nd hand, so no receipt and no prove of purchase.
can I still send it back to samsung to fix it?

same problem as you and now my phone died completely .
my phone was 4 months and he has not supported any longer he died naturally lol.
my operator gave me another free under warranty because the phone had a faulty motherboard and after several back galaxy note 4

This started happening to me a week or so ago and my phone just got stuck in a boot loop after it froze and rebooted. I'm on the latest stock firmware. Tried factory reset, reflashed stock firmware, nothing helps. It still reboots (sometimes it almost gets booted completely, other times it reboots after 2 seconds.

Just disable finger print. Yes that magic feature offered by Samsung is causing more hungry that happiness since S5

EclipseX said:
Just disable finger print. Yes that magic feature offered by Samsung is causing more hungry that happiness since S5
Click to expand...
Click to collapse
Many thanks. This was driving me mad for a few days, I had tried three different ROMS, completely wiping everything. I eventually went back to stock, which I'm still running and it was the same; it would run fine for a few hours and then start to lock up until eventually it would either reboot or stop responding and I'd have to pull the battery to restart it.
Just not selecting fingerprint security doesn't work, you have to force stop "Fingerprints" in Application Manager (All).

just do not setup the finger print lol. I was having those problemes too when I bought the note 4 until someone tell "do not setup the finger print" lol, not I'm a happy user.... I hope that android 6.0.1 solve the probleme
HXOY said:
Many thanks. This was driving me mad for a few days, I had tried three different ROMS, completely wiping everything. I eventually went back to stock, which I'm still running and it was the same; it would run fine for a few hours and then start to lock up until eventually it would either reboot or stop responding and I'd have to pull the battery to restart it.
Just not selecting fingerprint security doesn't work, you have to force stop "Fingerprints" in Application Manager (All).
Click to expand...
Click to collapse

EclipseX said:
just do not setup the finger print lol. I was having those problemes too when I bought the note 4 until someone tell "do not setup the finger print" lol, not I'm a happy user.... I hope that android 6.0.1 solve the probleme
Click to expand...
Click to collapse
Spoke too soon, it's started rebooting itself again.

Same problems here since 2 days. I was on original 5.1.1 software... Very strange all those people with the same problems

did the problem was resolved ? started to have the same problem 3 days ago ! was on 6- flashed stock with full wipe..nothing ! downgraded to 5.1 with full wipe via odin...again nothing !
WTF [email protected]!

Davids said:
did the problem was resolved ? started to have the same problem 3 days ago ! was on 6- flashed stock with full wipe..nothing ! downgraded to 5.1 with full wipe via odin...again nothing !
WTF [email protected]!
Click to expand...
Click to collapse
Still having the same issue around the same time everyone else started experiencing it.
I also was rooted and had xposed installed on 4.4.4 before the issue started happening.

Try the solution provided here & report back..
http://forum.xda-developers.com/note-4/help/note-4-sm-n910f-freeze-restart-issue-t3439111