Related
I thought I should share this with everyone in case it helps someone out there. I might have gotten lucky, so YMMV.
Basically like everyone else my SGS (I9000M from Bell) died due to an internal SD error, but in my case I haven't updated the phone since I got it in September 2010 (it had the JG9 firmware). The good thing is I was able to flash it to the stock Froyo 2.2, and I'm currently using it as normal and can access the internal SD without problems.
Summary of steps that most likely fixed the problem:
Go into recovery mode and "wipe data/factory reset". If your phone boots (but still have problems accessing the SD card) then it's a good indication that you maybe able to fix it.
Flash JL2 (from samfirmware.com) using ODIN. Not sure if this is needed, but you may need to ask ODIN to Re-partition. You still get an error "Can't mount DBDATA", and the phone won't boot. That's ok.
Flash the SpeedMod Kernel using ODIN (I used SpeedMod K12J with HZ=256). Your phone should boot into JL2 and the SD card should be accessible again.
At this point your internal SD card is fixed and you should be able to flash whatever you want. Just note that Kies will sometimes not work properly with the SpeedMod installed. In my case I flashed 2.1 (JH2) again (this won't work if you have 2.2 without speedmod kernel), then used Kies to update to 2.2 (JL2).
For those who are interested in the details, please read on.
Bought the phone in September, it's a Samsung Galaxy S I9000M from Bell. It says 10.07 on the back of the phone, and it had the JG9 firmware on it.
Since the 2.2 update came out I've been following closely the problem of the internal SD failures and the grief it's causing to a lot of people. So I decided to hold off updating until Samsung gets their act together. (I know it's better to update as soon as possible in case it dies so that I can use the warranty, but I had 9 months remaining so I decided to wait a little more.)
Close to the end of 2010 I noticed that my Android Market has changed, and that it now allows me to "Update All", so I just hit that and noticed that after updating several apps, all the remaining updates failed. I knew this wasn't a good sign. My SD card was still fine though.
After the above incident the phone felt a bit sluggish and less responsive than it used to be. I hadn't correlated this to anything yet, but now I know it was most probably due to the internal SD on its way to die.
On January 7 the phone suddenly died. When I rebooted it, I got the infamous symptom of seeing the S logo animation then black screen, then if I touch the two buttons at the bottom they light up indefinitely. At that point I knew it was the internal SD card.
I put the phone into recovery mode and confirmed my guess when I saw the red error message "Can't mount SDCARD".
I took the phone to the Bell store, the guy told me Bell now has an expedited shipping process for this problem and gave me a number to call to get a new replacement phone.
I called the number and they verified the symptoms with me, and said they're going to send me a new phone. I asked for the $100 credit but I was told I can't get it since I didn't update to 2.2. Apparently they only give you the credit if you actually tried to update and the update caused the phone to die (which doesn't make any sense to me).
So, while waiting for the new phone to arrive, I decided to try a few things. Here's what I did:
First thing I did was going into recovery mode and doing a "wipe data/factory reset". To my surprise, the phone actually booted after I did that, but I got force closes on almost all apps, and when I checked the internal SD card it wasn't mounted at all. The phone response was extremely slow and barely usable. I was able to make phone calls though.
I wondered if the SD problem is a corrupt partition rather than a physical error. After searching for a while I found someone posted a solution to fix a problem with his internal SD card by using the "parted" tool to mkfs the partition. Unfortunately I couldn't copy the tool using adb; my phone wasn't rooted and I couldn't access the SD card, so there was no place to copy the binary to. I get either a read-only error when trying to copy to the root, or a permission denied error when trying to copy to other mounted partitions.
Then I figured if I could flash 2.2 somehow (even if it doesn't work) I can try to ask Bell for the $100 credit Kies was useless as it couldn't recognize the phone, so I grabbed the stock JL2 firmware from samfirmware.com and used ODIN 1.7 to flash it. I asked it to Re-partition (not sure if this was needed). After reboot I saw another red error message, but this time it was complaining "Can't mount DBDATA" (as opposed to SDCARD). Then all reboots after that resulted in the same problem (S logo then black screen).
I searched for the "Can't mount DBDATA" error and found a post on xda that shows a method that should fix this by first using a 512 PIT file to repartition (no ROM involved), then flashing a stock firmware. I did that but it didn't help.
Then I found a site called "AKA skriller" that shows a way to reflash a stock firmware after the phone is bricked. So I followed the instructions by flashing a "nobrick" image (apparently made by someone called eugene), and then flashing a stock firmware. I flashed nobrick then JH2 in attempt to go back to 2.1. After doing this the phone went into a boot loop where it keeps showing the I9000M screen then rebooting. At that point I couldn't go into recovery mode, but I could go into download mode.
After searching again I found out that this was due to a new bootloader in 2.2 that prevents going back to a 2.1 firmware. I wanted to stop the boot loop so I flashed JL2 again, which stopped the boot loop but still the phone won't boot (black screen).
After more searching I found that I could go back to a 2.1 firmware only if I flash a custom kernel, someone suggesting the SpeedMod kernel (not sure if it has to be SpeedMod or any other kernel). So I flashed SpeedMod (I used SpeedMod K12J with HZ=256) using ODIN 1.52. First thing I got is a custom recovery menu with more options, I just skipped it and rebooted. THE PHONE ACTUALLY BOOTED this time into 2.2. Not only that, but the SDCARD problem was FIXED, and the phone was responsive and fast again.
I wanted to load my contacts again using Kies from a backup I made earlier. Kies recognized the phone but for some reason the contacts widget keep saying "please connect your phone" and I couldn't copy back my contacts.
I thought this might be due to the custom kernel and I was right. I flashed a stock 2.1 (JH2) with a bootloader included using ODIN. It just worked. I could copy my contacts again back to the phone.
I was also able to update to 2.2 (JL2) again using Kies this time, and it even kept my contacts. This is what I have now on the phone.
P.S. I can't post external links due to a restriction by the forum (since I'm new).
I had my doubts when I opened this thread... I've gone through 5 phones already and just finished killing my sixth...
I had tried flashing JL2 stock after killing it through the usual process (transferring over my music collection)... and got the EXACT same errors you wrote about.
What I didn't try was then flashing the custom kernel... so I tried that...
and it was too good to believe... didn't work for me. after the boot animation, display goes blank and buttons off... you can tell it's not going to work if it starts vibrating during boot.
I'm sorry it didn't work for you. As I said I might have been lucky.
Although that I just found another thread on androidforums where the guy managed to fix his sd card in a very similar way to what I described*. I actually haven't seen his post before I fixed my card, so it was independent.
Here are the commonalities between what I did and what he did:
* We both flashed a 2.2 firmware with a PIT file and Re-partition (using ODIN)
* We both got the black screen afterwards
* We both then flashed a custom kernel with no Re-partition
* We both got recovery menu right after flashing the kernel
* We both ended up in Android 2.2 aftwerwards with the SD card fixed
Here are the differences between us:
* I used JL2 firmware while he used JPM
* I used a 512 PIT while he used an 803 PIT (that's just what samfirmware.com said to use for each firmware)
* I flashed the firmware using ODIN 1.7 while he used ODIN 1.3
* I used the SpeedMod kernel while he used the YAOK kernel. He flashed using ODIN 1.3 while I flashed using ODIN 1.52.
* Once in the recovery menu I rebooted right away into 2.2, while he "ended up selecting every option that had something to do with mounting, formating, erasing. Anything to do and sounding to do with the SD card [he] pressed." then rebooted successfully with no SD card errors.
(*)http: //androidforums.com/samsung-galaxy-s/235987-clueless.html
what slaman encountered was REAL hardware failure, like I did
what you encountered was just a Corrupt SD card, which can be fixed all the time, using the process you described, and many other methods.
Real hardware failure, even if you manage to boot into the OS, it will show no internal SD, or 0 available space, or simply an error message complaining about the internal SD
You can only see that with custom ROMs, with a stock ROM you wont even get past the black and white SGS logo screen
internal SD card
Hi,
I have followed a few discussions on this board as also my internal and external SD card was "gone". I couldn't access or mount it any more after flashing with Odin to european JPY 2.2.1 ... and I found out where at least my internal memory has gone.
In fact the internal memory couldn't be accessed after installing an exchange email account. My OWA account requires security like password protection and NO external SD card.... but it seems that version 2.2.1 does not make a difference between internal and external SD card and removes the access to both away. It looks like disappeared but it comes back after uninstalling your exchange email account.
May be this is all known and logic but I couldn't find the explanation to it therefore I would like to post the information.
Thanks
Thank you very much for this! I indeed had the mpbk01 (whatever) error, and did exactly what was posted above (using 512 pit, and 1.7 odin) and now have my pone working just fine.
Again, thanks a lot for the post!
Edit: While all this is true.. seems like i have 0.00b of internal phone storage available, so I cannot install any apps. The internal SD card space is reporting normal at 13.03gb though.
Glad it worked for you. Hope you can solve the internal phone storage problem though.
As I mentioned I might have been lucky, I don't expect everyone to be able to fix the internal SD card problem by just flashing custom roms/kernels. If it works for a few people then I'm happy I saved them the hassle of going through Bell to replace the phone.
just a suggestion to send it out for repair, before you run out of warranty
Uss_Defiant said:
Thank you very much for this! I indeed had the mpbk01 (whatever) error, and did exactly what was posted above (using 512 pit, and 1.7 odin) and now have my pone working just fine.
Again, thanks a lot for the post!
Edit: While all this is true.. seems like i have 0.00b of internal phone storage available, so I cannot install any apps. The internal SD card space is reporting normal at 13.03gb though.
Click to expand...
Click to collapse
uys I have a very serious problem. I'm on Darkkys latest rom...
I took out my battery for 1 hour... put battery back in and the phone did not boot up.
All I got was the screen saver and the phone kept on virbarting...
I tried wiping cache through clock work recovery, resetting to factory settings via clock work.. still nothing..
I just updated phone via odin to latest JPY...the phone goes to black screen and keeps vibrating... It won't boot.
Guys what's wrong with my phone? I am really worried...and I need to use it
I appreciate your help.
Ps. Phone can go into download mode..
Edit: XWJM8 worked
jUsT2eXy said:
uys I have a very serious problem. I'm on Darkkys latest rom...
I took out my battery for 1 hour... put battery back in and the phone did not boot up.
All I got was the screen saver and the phone kept on virbarting...
I tried wiping cache through clock work recovery, resetting to factory settings via clock work.. still nothing..
I just updated phone via odin to latest JPY...the phone goes to black screen and keeps vibrating... It won't boot.
Guys what's wrong with my phone? I am really worried...and I need to use it
I appreciate your help.
Ps. Phone can go into download mode..
Edit: XWJM8 worked
Click to expand...
Click to collapse
well I have this problem and cant get it sorted at all, it seems to have also created another partion and i have no idea how to wipe the sd card clear of all partions so it can recreate them!!!!
please help !!!
Hii there,
this thread seems to be very helpful, so I want to value your help with something in return. if any of you can get me out of this mess I will donate you appropriately so that you can constantly offer this helps to others too.
some details are as follow:
1. my Galaxy S (korean) M110s was on USB downloading Market update when I disconnected it abruptly to make a call. It was downloading some updates then.
2. moment than its showing SD card damage error and even showing 00 for external SD card which I inserted post that.
3. this means neither internal nor external SD card are being detected. Though it shows that ext SD card is mounted when I insert in and also let me unmoutn it.
BTW I have tried flashiing using odin and eclair 2.1 version which didnt help much.
Need urgent help
usb jig only gets me into download mode. and not recovery mode
so can Odin still get it to work while in download mode instead
It worked for me but I can't access the internal memory nor the external one. Hence, I can't use the camera or install any app. I don't have any kind of warranty so I believe this is the best I can get, right?! At least I can use as a phone and browse the internet!
Thanks for your help, even though it worked half-way for me!
http://forum.xda-developers.com/showthread.php?t=1020278
Please take a look of this thread:
http://forum.xda-developers.com/showthread.php?t=1188482
It may fix your internal sd card problem permanently.
One more question, im not to sure of this program ODIN, but i remember i did a factory reset to get my GPS working a few weeks ago. I followed this post
""Fixing the GPS no fix issue on the Samsung Epic 4g requires you to do a manufacturer's reset by obtaining the MSL code from Sprint. Once you get the MSL Code, remove the SD Card and Enter ##786# on the dialer keypad. You will see two options: View and Reset. Tap on the Reset option and you will get a prompt to enter the MSL code. At this point you will be asked if you want to do a manufacter's reset, enter yes. The phone will shut down and reset itself after a few seconds. Once the process is complete, the phone will go through a hands free activation. After the activation process, updates may be downloaded and installed. Now that all updates have been performed, you may check to see if your GPS is working by going to Google Maps. You should be able to lock in GPS signal in under 10 seconds. Thats it. Your GPS woes are over."
After i did that and got a GPS lock, i went to CWM and did a ADVANCED data restore, and i back on DK28 and had GPS lock when i went into maps. COuldnt i jsut do the same factory reset, then open up CWM, flash the DEOXED eb13, and then do a advanced data restore??
Major question would be if i did ADVANCE, would it bring me back to DK28, or would i just do a DATA restore.
I really was hoping there would be a easier way to go from Dk28 to EB13, but this way seems alittle easier then ODIN.
Flashing the DK28 rom will NOT update the modem to EB13. Use Odin or samsung updater program. Both are very easy, just follow instructions.
Well to answer my own question, it says it does a MASTER RESET, but it DOES NOT!!! I ended up resetting my phone without my data but still am on DK28 with the ROM i flashed. And to make matters worse, somehow i ended up wiping all the data off my SD Card in the process, not sure how, Good thing i copied all my info to my laptop earlier today. I am now putting everythign back aswell as the DEOXED EB13 rom which im going to try and FLAsh the zip via CWM. worse case scenario i just advance rstore back to my CW backup from today and its like i didnt do any of this. ugg
If you are trying to get back to Stock (not rooted) just use the Samsung tool for EB13.
As far as going back to DI18 2.1, you will be better off with EB13 flashed, not the update.
im trying to go back to DK18 and stay rooted, to update to EB13.
urirx98 said:
im trying to go back to DK18 and stay rooted, to update to EB13.
Click to expand...
Click to collapse
Why not just use the samsung update tool, then use CWM 2.5.5
http://forum.xda-developers.com/showthread.php?t=770388
to root it. You will get a clean install (recommended) and root.
ok, so i actually was able to FLASH the DEOXED version of FROYO EB13 ontop of my DK28 , dont ask me how, it told me it didnt work, but it did. Now i tried to CWM my data and its saying its a non match. THis is not making me happy. I heard people had probs with this, any way to fix it??
Edit, i actually accidently swapped SD cards when i was copying and pasting and when i replace it with the correct card, i had no problems doing a FULL DATA restore.
I KNOW HAVE SUPERNOVA 2.2.2 EB13 Kernal version 2.6.32.9 running Firmware GENOCIDE 0.3a EB13 OC/UV kernal
Its KICKASS!!
I would odin to stock eb13 and if you really want everything to work try ACS FROZEN rom. Ive never been so happy with my device it ALL works
hi,
i have sim unlocked uk o2 phone which had i think ke1 (was 2.3.3) (not sure though) did multiple roots and roms but was an absolute idiot and did not do a nandriod backup. now whatever rom or even a stock firmware i am experiencing random shutdown (1-5 minutes) with everyone (i have to take the battery out play with it a couple of times for it to boot or even to get into download or recovery. it does not even charge in this condition). so i need this backup bad to see if anything is recoverable. here is the history
upgraded to kg2 via odin (from android advices via odin no issues)
rooted via cf3 (no issues)
litening 5.0 ( went well for a couple of days then disaster)
reverted to kg6 stock (same issue)
did villian rom (same issue)
my warranty is voided and dont have access to a jig. desperate
Sounds like a hardware issue....
Have you tried flashing the stock kernel first, then rebooting again into download to flash the stock ROM?
yeah kg6, but i have a suspicion it was kernel only..... am i missing something here
Since KG2 was the last one that worked fine for you, I recommend flashing the KG2 kernel first, then the KG2 ROM. Then confirm that everything works fine before flashing to KG6.
Sleepycat3 said:
Since KG2 was the last one that worked fine for you, I recommend flashing the KG2 kernel first, then the KG2 ROM. Then confirm that everything works fine before flashing to KG6.
Click to expand...
Click to collapse
not working same issue
try flashing ke7 from samfirmware, then wipe cache and data in recovery, then format internal storage, then factory reset......
all data will be lost on the phone but should give you a fresh install...
thankfully i hope its resolved now (>6 hours up)
this is what i did
official kg2 kernal
factory reset
official kg2 rom (sam firmwares)
was having the same issue till now
rooted with cf
did cache wipe and factory reset with dalvik wipe
now the same i had done before too but not the dalvik wipe. it seems to have done the trick.
one more thing since i didnt have the jig and wasnt going into dl mode. i hooked the mobile with pc. now it varied (15-1hour) but as soon as the diplay showed phone chargin i unhooked and took into dl mode
I have some related problems with my phone which started happening a couple of days ago after updating Google Maps and a few other programs from the Play Store (Twitter also). That may not be relevant.
It's an Australian i9505 from Telstra. I'm on an old version of Omega ROM - v12 - with Adam Kernel 3.4.0. It's the latest that (the currently stalled) jKay can run on.
The main issue is that the phone reboots frequently. It seems like a "soft reboot" - the uptime reported in System Settings - > About device -> Status doesn't reset, but the time reported by Battery, for instance, does (and the whole UI reloads, programs, widgets etc)
This can happen in my pocket, or can be pretty reliably triggered by uninstalling a program, sometimes installing/updating, and sometimes from using Google Maps (embedded or the program itself).
The first time it happened was after the programs updated on the 5th of Feb.
Related issues:
I can't update the modem in Odin or Mobile Odin.
I tried upgrading to the latest pre-KitKat version, v19, which requires updating the modem.
Flashing the modem I already have did succeed, but that doesn't prove much.
I can update the recovery though - but I haven't tried installing a new rom because of the modem problem.
Rebooting into Recovery or Download mode from software fails - i.e. any of the "boot menu" programs/features. The phone shuts down but then stays turned off.
I can boot into them using the hardware buttons though.
Things I've tested:
It's not the SD card - it happens with it removed.
It's not the battery - I've got 3 batteries, none of which suffer from bloat, and it happens with all.
It's not water damaged - the nearest it got to rain was a couple of days earlier
From what I can tell, rolling back Google Maps, clearing data/cache for Google Services Framework or Google Play Services, all don't fix it.
Any suggestions?
Is my phone toast? Is there a rom I can install with included modem, perhaps?
Or should I at try unrooting and going back to stock? Triangle Away currently fails too, so I'm concerned that if it's a hardware problem Samsung won't fix it for me anyway.
frogworth said:
I have some related problems with my phone which started happening a couple of days ago after updating Google Maps and a few other programs from the Play Store (Twitter also). That may not be relevant.
It's an Australian i9505 from Telstra. I'm on an old version of Omega ROM - v12 - with Adam Kernel 3.4.0. It's the latest that (the currently stalled) jKay can run on.
The main issue is that the phone reboots frequently. It seems like a "soft reboot" - the uptime reported in System Settings - > About device -> Status doesn't reset, but the time reported by Battery, for instance, does (and the whole UI reloads, programs, widgets etc)
This can happen in my pocket, or can be pretty reliably triggered by uninstalling a program, sometimes installing/updating, and sometimes from using Google Maps (embedded or the program itself).
The first time it happened was after the programs updated on the 5th of Feb.
Related issues:
I can't update the modem in Odin or Mobile Odin.
I tried upgrading to the latest pre-KitKat version, v19, which requires updating the modem.
Flashing the modem I already have did succeed, but that doesn't prove much.
I can update the recovery though - but I haven't tried installing a new rom because of the modem problem.
Rebooting into Recovery or Download mode from software fails - i.e. any of the "boot menu" programs/features. The phone shuts down but then stays turned off.
I can boot into them using the hardware buttons though.
Things I've tested:
It's not the SD card - it happens with it removed.
It's not the battery - I've got 3 batteries, none of which suffer from bloat, and it happens with all.
It's not water damaged - the nearest it got to rain was a couple of days earlier
From what I can tell, rolling back Google Maps, clearing data/cache for Google Services Framework or Google Play Services, all don't fix it.
Any suggestions?
Is my phone toast? Is there a rom I can install with included modem, perhaps?
Or should I at try unrooting and going back to stock? Triangle Away currently fails too, so I'm concerned that if it's a hardware problem Samsung won't fix it for me anyway.
Click to expand...
Click to collapse
Hi,
A couple of things that you might try:
1. Look HERE
This should help with the flashing of the modem.
2.Do you have the knox-pox?
Check in download mode.
Is there anything about knox?
malybru said:
Hi,
A couple of things that you might try:
1. Look HERE
This should help with the flashing of the modem.
2.Do you have the knox-pox?
Check in download mode.
Is there anything about knox?
Click to expand...
Click to collapse
Hi there,
Thanks - I'll try that, although I've attempted flashing the modem a number of times. I'll uncheck autoreboot, but it never gets there because it fails during Download Mode.
I don't have knox - I'm still on an earlier bootloader.
frogworth said:
Hi there,
Thanks - I'll try that, although I've attempted flashing the modem a number of times. I'll uncheck autoreboot, but it never gets there because it fails during Download Mode.
I don't have knox - I'm still on an earlier bootloader.
Click to expand...
Click to collapse
Hi,
If that fails , and you want to get back to stock, Google for the MGA firmware.
This is the knox-free version.
Bear in mind that this will wipe your phone clean.
It is flashed in odin , and will replace your ROM,kernel ,modem and recovery.
Triangle Away should also work and you could then send in your phone for repair.
One thing if you do that , they will probably upgrade your phone to the latest knox-pox version.
Good luck
I'm trying to flash the modem again, but I'm noticing this error:
There is no PIT partition.
Is it worth flashing with a .pit file?
Or can you *only* flash a pit file when flashing firmware, not modems or recoveries?
frogworth said:
I'm trying to flash the modem again, but I'm noticing this error:
There is no PIT partition.
Is it worth flashing with a .pit file?
Or can you *only* flash a pit file when flashing firmware, not modems or recoveries?
Click to expand...
Click to collapse
Hi,
I would go for the stock MGA firmware flash.
Back up your stuff first.
If you still get errors , post your questions HERE
samersh72 is the expert in pit files.
UPDATE: so, at home I only have a Mac and I do my Odin stuff in VMware. 99% of the time it's fine, but updating my modem in order to flash the latest Omega ROM wasn't working.
At work, I plugged in my Samsung cable to one of the back USB ports, and had no problem flashing modem and pit file.
The problem with rebooting (into download, recovery or whatever) via software has gone away - *phew*
Then I installed latest Omega, same problem.
So I tried installing with full wipe - and from what I can see, it wasn't randomly rebooting - I could use Maps and remove Play Store apps with no problems.
Unfortunately upon restoring apps & settings with Titanium Backup, the problem returned. But I'm confident now that it's settings, so I won't need to restore to stock and take it back to Samsung at least!
I'll wipe again and post here when I resolve where the problem lies. Next attempt will be to restore user apps + data but not system data, or vice versa, and to be more selective... I'll crack this
I've now reinstalled the ROM again with a full wipe, didn't allow Google to reinstall my apps but instead got Titanium Backup to restore only non-system apps and data.
Of system data I've restored SMS/MMS messages, accounts, and WiFi access points only I think. I've redone the settings for everything else.
So far, all systems go - no reboots.
Oh and conversely, restoring ONLY system apps/data immediately brought the problem back.
I'm not that keen to keep restoring system data till I encounter the problem, since for now I seem to be back in business. W00t! :laugh: :good:
I have had similar issues. It seems like the internal sd has been formatted incorrectly. So i Google the I9505 pit file for Odin and stock firmware Knox free and everything worked straight away. Odin will format the internal sd with the pit file and then it will begin to flash stock firmware and you will have fresh s4 to work with.
Sent from my GT-I9505 using XDA Premium 4 mobile app
glennd said:
I have had similar issues. It seems like the internal sd has been formatted incorrectly. So i Google the I9505 pit file for Odin and stock firmware Knox free and everything worked straight away. Odin will format the internal sd with the pit file and then it will begin to flash stock firmware and you will have fresh s4 to work with.
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks - yes, I did flash a pit file for i9505 and it did help the problem with booting into recovery/download mode via software.
But the crashing problem comes back anytime I restore all the system settings, so it's some weird bug with some buried setting - it's not Google Play Services or Google Maps, even though it's related to them. I've just stayed away from restoring practically any system settings and it's working for me.
Hi,
I recently got the I337m s4 that was originally under Bell (canadian carrier). The first mistake, I think I made was immediately flashing it by using the chainfire autoroot method with odin. After I did, I installed the gummy rom. Ever since then, I cannot get the sound to work on my phone. I am not sure if it is a modem issue. I hope it is not a hardware issue. I already tried going to
From searching different threads on here, one user of the i9505 variant was able to get sound working by using odin to flash the stock rom. I linked the thread below:
http://forum.xda-developers.com/showthread.php?t=2698073
Is this the proper way to start troubleshooting? I already tried getting back to stock by using odin 3.07 and the firmware below that did not work:
http://www.sammobile.com/firmwares/?page=1&model=SGH-I337M&pcode=0#firmware
Should I try flashing stock again but this time by doing the battery pull method (pulling the battery, before rebooting, after flashing is complete) that a lot people suggest? Did I select the correct firmware from sammobile?
P.S. When I did go back to stock, the boot screen samsung always played sound.
some ideas
try flashing the modems
reflash rom and check md5 before flashing
restore your nandroid
i think 3.09 is latest odin, but never used it
are you wiping all including system before flashing rom--i do it 3x
I have not tried flashing the modem but I read on xda that when you flash the whole stock firmware from sammobile, you end up re-flashing the modem since it is in the firmware. I will try flashing modem separately since I have not done that, yet.
When I flash, I always wipe dalvik cache, cache and do a factory reset before I start.
Btw, I did go flash the firmware from sammobile today and unrooted my phone. I still get no sound when playing music. The only sound I get is the samsung boot sound, when booting my phone.
rsd79 said:
I have not tried flashing the modem but I read on xda that when you flash the whole stock firmware from sammobile, you end up re-flashing the modem since it is in the firmware. I will try flashing modem separately since I have not done that, yet.
When I flash, I always wipe dalvik cache, cache and do a factory reset before I start.
Btw, I did go flash the firmware from sammobile today and unrooted my phone. I still get no sound when playing music. The only sound I get is the samsung boot sound, when booting my phone.
Click to expand...
Click to collapse
Only other thing I can think of is to back up personal data and wipe your cards.
It seems like every time I do factory reset from the phone or flash using odin, the sound works for 5 minutes, when I play a track. Then I have to restart the phone and sometimes the sound comes back sometimes it doesnt. Otherwise, everything else working fine.
[FIXED]
Partly, because I had misplaced my OEM battery, I did not mention this before. The whole time my phone would randomly restart and not play sounds, I was using the anker 7800mah batter. After, I put the OEM stock battery back in, everything is working fine now! I am still on stock firmware but was able to root using chainfire with no issues.:good: