So my unrooted, Jellybean SG2 decided to crap out on me. It's stuck in the dread boot loop! OH NOES! I got a new SG2, so I don't care if my SG2 what software is put on it. I just want my precious data (music, photos, videos). Some said it couldn't be done, but I found this thread on here that said otherwise.
Making use of SiyahKernal, it should be possible to mount my SG2 to my laptop. I decided to Odin this puppy up. I wanted to go by the tutorial the other thread posted, so I tried using the Jellybean T-Mobile rom (which my SG2 was using). I used the ROM, for my device, from Samsung Updates. I made sure to restart my PC, shut down any processes by Kies, etc, etc before starting Odin. When I went to flash the ROM, Odin froze for a good 15 minutes. I decided that nothing was going to happen and unplugged my S2.
So, here I am, stuck with the message, "firmware upgrade encountered an issue in Samsung Galaxy S2." I, somehow, made the problem worse. I just want my data. As you can see, I'm a total noob with this stuff. Please help!
Get a stock rom from Samfirmware, AndroidFirmwares.net or Samsung-Updates.com, flash it with Odin following instructions in thread stickied near top of Q&A titled 'Flash stock firmware...'. Clean slate. You shouldn't lose your stuff, but there are never guarantees with this or even that this will definitely fix your phone & enable it to boot normally (it shouldn't & it should though).
MistahBungle said:
Get a stock rom from Samfirmware, AndroidFirmwares.net or Samsung-Updates.com, flash it with Odin following instructions in thread stickied near top of Q&A titled 'Flash stock firmware...'. Clean slate. You shouldn't lose your stuff, but there are never guarantees with this or even that this will definitely fix your phone & enable it to boot normally (it shouldn't & it should though).
Click to expand...
Click to collapse
Thanks. I'll give it a try and post my results.
Ricequakes said:
Thanks. I'll give it a try and post my results.
Click to expand...
Click to collapse
well loosing data is something that i've experienced alot of times (my case i9100g)
i guess flashing the clean stock rom will help out.. but recently when my friend messed up his s2 i9100 i flashed the stock through odin which made him all the data its uncertain whether you loose your data or not.. fingers crossed flash the stock you may or may not loose data
thuva06 said:
well loosing data is something that i've experienced alot of times (my case i9100g)
i guess flashing the clean stock rom will help out.. but recently when my friend messed up his s2 i9100 i flashed the stock through odin which made him all the data its uncertain whether you loose your data or not.. fingers crossed flash the stock you may or may not loose data
Click to expand...
Click to collapse
Let's hope. If only it would even flash. Just tried and this is what I got on Odin:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T989UVMC6_T989TMB_T989UVMC6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> aboot.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> amss.bin
<ID:0/008> FAIL!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
And what it said on my SG2:
nand_write: flash write fail
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-s2-tmobile
Post in correct forum
S4 victim
theunderling said:
http://forum.xda-developers.com/galaxy-s2-tmobile
Post in correct forum
S4 victim
Click to expand...
Click to collapse
I'm a bigger noob than I thought. Sorry, guys.
Mod Edit
Thread closed
[OP] found correct forum
malybru
Forum Moderator
Related
Hey guys,
First up, this is what I was running.
-Samsung Galaxy S3 GT-I9300
-FCC ID: A3LGTI9300A
-SSN: -I9300GSMH
-RootBox v3.8
So I installed RootBox v3.8 a few weeks ago and the update for v3.9 appeared on my phone along with the GAPPS update. I made the mistake of ONLY flashing the first update. So when my phone rebooted it kept on giving me the error 'Android.process.acore has stopped unexpectedly'. I was forced to then revert back to v3.8 and everything seemed peachy. Up until the other night where I turned on my phone and it showed, 'Firmware upgrade encountered an issue. Please select recovery mode in kies and try again'. I accessed 'Download Mode' and tried to flash my stock rom back on but it failed in ODIN and gave me this error.
'<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXEMA2_I9300OPSEMA1_I9300XXELLA_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.img
<ID:0/007> NAND Write Start!!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<ID:0/007> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/007> Removed!!'
Also if I switch on my phone, this is what appears, I can still access 'Download Mode'. Any help would be greatly appreciated.
AW: [Q] [HELP] Soft-Bricked Galaxy S3-I9300
Baraa01 said:
Hey guys,
First up, this is what I was running.
-Samsung Galaxy S3 GT-I9300
-FCC ID: A3LGTI9300A
-SSN: -I9300GSMH
-RootBox v3.8
So I installed RootBox v3.8 a few weeks ago and the update for v3.9 appeared on my phone along with the GAPPS update. I made the mistake of ONLY flashing the first update. So when my phone rebooted it kept on giving me the error 'Android.process.acore has stopped unexpectedly'. I was forced to then revert back to v3.8 and everything seemed peachy. Up until the other night where I turned on my phone and it showed, 'Firmware upgrade encountered an issue. Please select recovery mode in kies and try again'. I accessed 'Download Mode' and tried to flash my stock rom back on but it failed in ODIN and gave me this error.
' Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
I9300XXEMA2_I9300OPSEMA1_I9300XXELLA_HOME.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin v.3 engine (ID:7)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
boot.img
NAND Write Start!!
Complete(Write) operation failed.
Added!!
All threads completed. (succeed 0 / failed 1)
Removed!!'
Also if I switch on my phone, this is what appears, I can still access 'Download Mode'. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Heya!
Your SIII looks bad with this stripes!
Have you flashed your StockROM via Odin while you were in DownloadMode? If it don't be in DownloadMode, it also can't be flashed.
Try to download a firmware from samfirmware.com and to flash it via Odin in the PDA field while your device is in DownloadMode!
And when you have finished, go to Recovery and Wipe your Data&Cache!
Greetings...
Sent from my GT-I9300 using xda app-developers app
Of course I used ODIN to flash stock rom, it didn't work.
AW: [Q] [HELP] Soft-Bricked Galaxy S3-I9300
Of course I used ODIN to flash stock rom, it didn't work.
Click to expand...
Click to collapse
Sorry that I ask, but have you flashed it in Downloadmode?
Sent from my GT-I9300 using xda app-developers app
TheRealFelix0212 said:
Sorry that I ask, but have you flashed it in Downloadmode?
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
If you read my first post, yes, I did flash it in Download Mode via ODIN.
Well, it obviously had a problem writing the rom into the phone (nand write failed). You may have a hardware fault. Do you have the nand chip that suffers from sds?
Sent from my GT-I9300 using xda premium
I've had similar issues before, not that exact screen, but issues with Odin. It worked eventually.
Try Odin3 v.1.85 from here (CF-Auto-Root thread).
Next, be sure you got a valid file, those from sammobile (Choose your country for).
Next, use only PDA button, nothing else, make sure it's the same settings as in root thread above.
Also make sure all Kies processes are closed.
Now, try until it works. It might take a few tries. This is what worked for me, hope it does for you too.
ratatattata said:
I've had similar issues before, not that exact screen, but issues with Odin. It worked eventually.
Try Odin3 v.1.85 from here (CF-Auto-Root thread).
Next, be sure you got a valid file, those from sammobile (Choose your country for).
Next, use only PDA button, nothing else, make sure it's the same settings as in root thread above.
Also make sure all Kies processes are closed.
Now, try until it works. It might take a few tries. This is what worked for me, hope it does for you too.
Click to expand...
Click to collapse
Still failed in ODIN. You reckon the eMMC chip is damaged?
Baraa01 said:
Still failed in ODIN. You reckon the eMMC chip is damaged?
Click to expand...
Click to collapse
That's what it sounds like keep trying to flash, try a different usb cable and computer if you can. Also remove any sim or sd card.
Also maybe the partition table is messed up but emmc is Ok?
Sent from my GT-I9300 using xda premium
jmpmjmpm said:
That's what it sounds like keep trying to flash, try a different usb cable and computer if you can. Also remove any sim or sd card.
Also maybe the partition table is messed up but emmc is Ok?
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Same isssue here, same screen and everything.... I tried for over a month and nothing... got an expensive door steep. If you have any lights about this... let me know!!
try flashing recovery only and then flash 3.8 again through recovery.
try flashing the resurrection rom from the checkrom site through odin in download mode..
galaxys3lover said:
try flashing the resurrection rom from the checkrom site through odin in download mode..
Click to expand...
Click to collapse
Been there, done that. Nothing happens. Same error, Re-Partition failed.
please help?
-Samsung Galaxy S3 GT-I9300
-FCC ID: A3LGTI9300A
-SSN: -I9300GSMH
I hope I've not ended up with this phone mentioned in this thread....purchased a phone from ebay and the seller said its stuck on Android SIII logo...I can get into download mode but before I attempt anything can someone tell me if this is a UK phone so I can apply the correct ROM (if it works!).
Also, currently the phone does not charge, battery is fine as i've tried the battery from own s3 and vice versa...both batteries are fine but the phone does not appear to charge...I'm hoping this is ROM related....
Any help will be much appreciated otherwise its an expensive gamble!
BTW...In the download mode the product bit is blank and does not say Samsung galaxy s3 like my own working phone does...
I tried to flash SCH-I545_MD2_423399_Kernel.tar onto my Galaxy S4, and it said boot.img Fail. I have a SCH I545 and I have been looking everywhere for a fix but this is sort of a last resort. Does anyone know what do to? Thanks in advance.
Incaendium said:
I tried to flash SCH-I545_MD2_423399_Kernel.tar onto my Galaxy S4, and it said boot.img Fail. I have a SCH I545 and I have been looking everywhere for a fix but this is sort of a last resort. Does anyone know what do to? Thanks in advance.
Click to expand...
Click to collapse
Was your S4 on the MDK bootloader/release before you tried flashing the MD2 kernel with Odin?
If it was NOT on MDK, then you can't root using that method; you'll need to flash the MK2 Odin tar from here: http://forum.xda-developers.com/showthread.php?t=2578209
And then root using saferoot: http://forum.xda-developers.com/showthread.php?t=2565758
You will not be able to install TWRP/CWM on a non-MDK S4.
bleh
I have already rooted, the problem is that I can't flash and custom ROM's, This is exactly what happens whenever I try to flash anything onto my device.
I will put it in PDA or its specified placement, and make sure everything that is needed to be checked is checked, then I will press start.
Odin will proceed to fail at boot.img, and I will then get frustrated.I can't send you a link to a screenshot yet, so if you want one I might be able to send you it in a private message, just let me know.
Along with the full message that Odin gives me <ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I545_MDK_562219_Kernel.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
I had to use a different MD5, but this is exactly what happens with everything.
When and where did you buy your S4?
I bought it at Verizon about a month or two ago
You can't flash a custom recovery on it at all then, only the first S4s bought around when it was released and then never updated can have custom recoveries.
If your phone won't boot (now or in the future), you'll need to flash the MK2 Odin tar from the thread I linked to restore it to stock.
Your only option for flashing roms will be safestrap, and only TouchWiz-based roms will work.
Safestrap: http://forum.xda-developers.com/showthread.php?t=2441441
Compatible roms: http://forum.xda-developers.com/showthread.php?t=2634408
Any reccomendations? I have never seen these.
Incaendium said:
Any reccomendations? I have never seen these.
Click to expand...
Click to collapse
If you want AOSP, Eclipse is probably the closest (themed) you can get to it: http://forum.xda-developers.com/showthread.php?t=2351840
Otherwise maybe try Bonestock, BajaROM, Hyperdrive... find whatever you like best.
Nevermind again, how do I install a rom using safestrap
Alright so I did a data wipe atempting to open up a rom slot, but I couldent get enough storage open so I just rebooted. Now my phone is stuck on the samsung custom screen that you get after you try to reboot. Did I just brick my phone?
Incaendium said:
Alright so I did a data wipe atempting to open up a rom slot, but I couldent get enough storage open so I just rebooted. Now my phone is stuck on the samsung custom screen that you get after you try to reboot. Did I just brick my phone?
Click to expand...
Click to collapse
You may or may not have bricked it. To me though it sounds like you may just want to start fresh and Odin MK2 back on your phone.. Use Saferoot, then install SafeStrap.
I'd suggest saving anything you don't want to lose and use the full wipe Odin image.
A fresh start sometimes is just the way to go. You can of course fiddle with things and see if that's not needed... But that's what I would do
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
Good Day!
I have a kcc-cmm-sec-shve330k 32GB that i flashed using odin 3.09 and E330KKKUBML1_FULL_20140103.tar but it failed!
here is what happened with odin,
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> E330KKKUBML1_FULL_20140103.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> tz.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> sdi.mbn
<ID:0/008> sbl1.mbn
<ID:0/008> rpm.mbn
<ID:0/008> recovery.img
<ID:0/008> NON-HLOS.bin
<ID:0/008> modem.bin
<ID:0/008> hidden.img.ext4
<ID:0/008> boot.img
<ID:0/008> aboot.mbn
<ID:0/008> FAIL! (Auth)
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1) i dont have any clue why it works with others and not with my cp
this fw (E330KKKUCNC1_PROXYME20140319.tar) is ok and it works for me and im using it but this has issues with apps working on 4.2 and not working in 4.4. like my navigator sygic. any suggestions guys ???
Another question is, Is it normal that after flashing for few times testing 4.3 & 4.4 FW that when it done, all my sms, apps, name of carrier Oleh is there and not erased?
Thanks in advance!
Odin is failing on the modem, it seems. What baseband do you have installed at the moment? Many of the newer Samsungs have certain protections built in that cause issues with downgrading past official 4.3.
But it is normal for your stuff to still be there. Most firmware packages do not automatically wipe the phone while it flashes, which is why you will see the recommendation to factory reset after Odin flashes when you get stuck in a boot loop.
es0tericcha0s said:
Odin is failing on the modem, it seems. What baseband do you have installed at the moment? Many of the newer Samsungs have certain protections built in that cause issues with downgrading past official 4.3.
But it is normal for your stuff to still be there. Most firmware packages do not automatically wipe the phone while it flashes, which is why you will see the recommendation to factory reset after Odin flashes when you get stuck in a boot loop.
Click to expand...
Click to collapse
E330KKKUCNC1
KERNEL 3.4.0-683274
[email protected]#1
Many thanks for the quick reply
Yep, you're trying to downgrade, and the modem partition is protected by the new bootloader crap Samsung has been adding since 4.3. So, you should be able to flash a custom 4.2 or 4.3 rom, as often times the newer modems are backwards compatible, but can not officially downgrade with Odin. Some people have actually bricked phones from trying, though is rare. Usually it just fails like yours, but is not a good idea to take those chances. Please make sure to do a nandroid backup and also, more importantly, make sure your EFS folder is backed up and saved somewhere safe before you get too crazy with the mods.
es0tericcha0s said:
Yep, you're trying to downgrade, and the modem partition is protected by the new bootloader crap Samsung has been adding since 4.3. So, you should be able to flash a custom 4.2 or 4.3 rom, as often times the newer modems are backwards compatible, but can not officially downgrade with Odin. Some people have actually bricked phones from trying, though is rare. Usually it just fails like yours, but is not a good idea to take those chances. Please make sure to do a nandroid backup and also, more importantly, make sure your EFS folder is backed up and saved somewhere safe before you get too crazy with the mods.
Click to expand...
Click to collapse
Thanks again for the info. i guess I'll stick to 4.4 for now
ricotek14 said:
Thanks again for the info. i guess I'll stick to 4.4 for now
Click to expand...
Click to collapse
No problem. Yea, it sucks. Stuff like that is actually a deal breaker for me and makes me not near as interested in Samsungs (see my sig for phones I've used - many Samsungs) as I used to be, no matter the specs / features. If I wanted to be locked in like that, I'd probably be more interested in iPhones. You'd probably have more luck trying to sort out why the certain apps aren't working for you or wait for the developers to upgrade for KK - which is kind of ridiculous they haven't yet as it has been out since November.
I have recently rooted my phone and using MIUI and Siyah-s2-v6.0b4 Kernel. I followed steps from a tutorial. It was working fine until yesterday. I was on Instagram when the phone froze on that screen. I left it as it is. It stayed like that for some time and then it rebooted automatically. The phone shows initial Samsung Galaxy S2 screen and after that it goes blank. The boot animation doesn't load. If the press the Home Key 4 times, it shows a bright white screen continuously and stays like that. And the screen turns off when I press the home screen 4 times. Nothing else happens. When I try to get into recovery mode it gives me error Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. The phone worked perfectly and suddenly this happened. I had tried updating when I got the MIUI update notification. It downloaded the update, rebooted the phone automatically and phone started normally and I got the update notification again. Please help me fix my phone. I need it as soon as possible. And sorry if I posted in the wrong section.
Download stock rom for country/carrier from Samfirmware, boot into download mode, flash with Odin following instructions in thread stickied near top of Q&A titled 'Flash stock firmware', problems with flash = find Hopper8's 'Odin troubleshooting' thread stickied in General, it has all the info you need to get a successful flash.
Once you've done that, re-root your phone & restore nandroid backup or re-flash custom rom/kernel & start again.
But frankly, you should already know this stuff if you're modding your phone. Not knowing how to recover when things go wrong (and they do for everyone sooner or later) potentially leaves you without a working phone for hours (at least), especially given S2 Q&A doesn't get as many posters or people answering other people's questions as it used to.
MistahBungle said:
Download stock rom for country/carrier from Samfirmware, boot into download mode, flash with Odin following instructions in thread stickied near top of Q&A titled 'Flash stock firmware', problems with flash = find Hopper8's 'Odin troubleshooting' thread stickied in General, it has all the info you need to get a successful flash.
Once you've done that, re-root your phone & restore nandroid backup or re-flash custom rom/kernel & start again.
But frankly, you should already know this stuff if you're modding your phone. Not knowing how to recover when things go wrong (and they do for everyone sooner or later) potentially leaves you without a working phone for hours (at least), especially given S2 Q&A doesn't get as many posters or people answering other people's questions as it used to.
Click to expand...
Click to collapse
Have downloaded the stock ROM, tried flashing it but it got stuck on
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLST_I9100ODDLSE_I9100DDLS9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> boot.bin
<ID:0/009> NAND Write Start!!
No progress after this point.
ansariaamir_leo said:
Have downloaded the stock ROM, tried flashing it but it got stuck on
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLST_I9100ODDLSE_I9100DDLS9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> boot.bin
<ID:0/009> NAND Write Start!!
No progress after this point.
Click to expand...
Click to collapse
Did you even read what my thread said? Or what MistahBungle wrote?
MistahBungle said:
problems with flash = find Hopper8's 'Odin troubleshooting' thread stickied in General, it has all the info you need to get a successful flash.
Click to expand...
Click to collapse
The whole purpose of my thread is to troubleshoot Odin flashing errors. Time to read it and do what it says. As MistahBungle says, there's nothing missed out in that thread. If, after trying everything in that thread multiple times, you don't get it to 'take' a flash, then time for a service centre/new motherboard.
OK...
You're obviously not someone who pays attention to the help they're given, so I'm going to repeat what I said in my last post once, and then I'm not posting to this thread again...
'Problems with flash = find Hopper8's 'Odin troubleshooting' thread stickied in General, it has all the info you need to get a successful flash'.
If you want your phone fixed, you go through as many of the troubleshooting steps in Hopper's thread as many times as you need to.
You are the only person who can fix it. We can't fix it for you. I've given you the tools to fix it, go fix it. Or not. I don't care. But I can guarantee you one thing, if all you do is post 'But it won't work !' to this thread when I've given you the tools to get it fixed, your phone will probably still be busted this time tomorrow.
Hey guys. I've run into an issue with my GT-i9300 International version just yesterday at it's racking my brains up.
Here's the lowdown about the device
It's the international GTi9300 (3G version)
It runs ArchiDroid v2.1.4 ROM
This rom was installed a year ago and gave no issues what so ever.
Just yesterday the device did not boot up. i Managed to get it into philz recovery to see whats the problem. i get the error message that it couldnt mount /data, /system & etc.
I have posted the screenshots. I've tried backing up, mounting and even factory wiping but it does not work
I have a feeling the eMMC flash storage has failed and therefore i have a hardware failure :crying:
I hope this is not the case since i have lots of important data on this phone (it's my secondary phone)
Have a look at the screens. lemme know the fate of my S3, whether it is possible to recover this device or not
p.s: I've checked all over the net. i've only come across the /efs not mounting issue. not what im going through
Naweed Reza said:
Hey guys. I've run into an issue with my GT-i9300 International version just yesterday at it's racking my brains up.
Here's the lowdown about the device
It's the international GTi9300 (3G version)
It runs ArchiDroid v2.1.4 ROM
This rom was installed a year ago and gave no issues what so ever.
Just yesterday the device did not boot up. i Managed to get it into philz recovery to see whats the problem. i get the error message that it couldnt mount /data, /system & etc.
I have posted the screenshots. I've tried backing up, mounting and even factory wiping but it does not work
I have a feeling the eMMC flash storage has failed and therefore i have a hardware failure :crying:
I hope this is not the case since i have lots of important data on this phone (it's my secondary phone)
Have a look at the screens. lemme know the fate of my S3, whether it is possible to recover this device or not
p.s: I've checked all over the net. i've only come across the /efs not mounting issue. not what im going through
Click to expand...
Click to collapse
Have you flashed stock firmware with Odin yet? This is the first thing you need to do to see if Odin works or gives errors....don't forget to factory reset after flashing. I'm afraid you may have to live with losing your data if you can't back it up in recovery.
tallman43 said:
Have you flashed stock firmware with Odin yet? This is the first thing you need to do to see if Odin works or gives errors....don't forget to factory reset after flashing. I'm afraid you may have to live with losing your data if you can't back it up in recovery.
Click to expand...
Click to collapse
i'll try flashing the stock rom via odin
Yeah, now i gave up on caring about the data. i really need the phone to work tho
i'll get back on the progress
@tallman43
Status report.
I tried flashing a stock rom which is on 4.3
It says NAND write failure. screenshot uploaded.
So i'm guessing my eMMC is corrupt or has failed :crying:
I did more research and found out that i could repartition it using a .pit file
This thread shows the relevant pit files
http://forum.xda-developers.com/showthread.php?p=30547929#post30547929
GT-I9300_mx_20120220.pit is for the 16 gb s3.
i'll flash with with the ROM
Lemme know if this is alright :good:
Naweed Reza said:
@tallman43
Status report.
I tried flashing a stock rom which is on 4.3
It says NAND write failure. screenshot uploaded.
So i'm guessing my eMMC is corrupt or has failed :crying:
I did more research and found out that i could repartition it using a .pit file
This thread shows the relevant pit files
http://forum.xda-developers.com/showthread.php?p=30547929#post30547929
GT-I9300_mx_20120220.pit is for the 16 gb s3.
i'll flash with with the ROM
Lemme know if this is alright :good:
Click to expand...
Click to collapse
Be careful the thread is for verizon you can't flash any pit files from there be 100% sure the pit file is for S3 international try looking here this is the rescue firmware >> http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6 << there is a pit file in the 4.1.2 download but you need to flash the 4.3 in the link to stop efs issues. But to be honest it doesn't look too good if this fails I recommend a service repair.
tallman43 said:
Have you flashed stock firmware with Odin yet? This is the first thing you need to do to see if Odin works or gives errors....don't forget to factory reset after flashing. I'm afraid you may have to live with losing your data if you can't back it up in recovery.
Click to expand...
Click to collapse
Tried flashing the pit. I got the following error messages on odin
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGMK6_I9300OXAGMK6_I9300XXUGMK6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
tallman43 said:
Be careful the thread is for verizon you can't flash any pit files from there be 100% sure the pit file is for S3 international try looking here this is the rescue firmware >> http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6 << there is a pit file in the 4.1.2 download but you need to flash the 4.3 in the link to stop efs issues. But to be honest it doesn't look too good if this fails I recommend a service repair.
Click to expand...
Click to collapse
I had downloaded the pit from another site. it was the international one
But i'll try your link. i just saw your reply
I'm downloading the 4.3 GT-I9300XXUGMJ9_KOR_MULTI_FACTORY package
Naweed Reza said:
Tried flashing the pit. I got the following error messages on odin
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGMK6_I9300OXAGMK6_I9300XXUGMK6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
You need to flash everything at once pit file and rom look at the link I sent you but it looks like you need a new motherboard:crying:
tallman43 said:
You need to flash everything at once pit file and rom look at the link I sent you but it looks like you need a new motherboard:crying:
Click to expand...
Click to collapse
Oh maan
Last resort is the link you gave. i'm downloading the 4.3 package. will put everything and flash at once. if this doest work. rip i guess :/
I never did anything. I installed the custom rom a year ago and let the phone be. didnt bother tweaking or adding to the custom rom
Then all of a sudden it doesnt boot
Naweed Reza said:
@tallman43
Status report.
I tried flashing a stock rom which is on 4.3
It says NAND write failure. screenshot uploaded.
So i'm guessing my eMMC is corrupt or has failed :crying:
I did more research and found out that i could repartition it using a .pit file
This thread shows the relevant pit files
http://forum.xda-developers.com/showthread.php?p=30547929#post30547929
GT-I9300_mx_20120220.pit is for the 16 gb s3.
i'll flash with with the ROM
Lemme know if this is alright :good:
Click to expand...
Click to collapse
I have a feeling the eMMC flash storage has failed and therefore i have a hardware failure
This is true
So flashing all 4 stock files (including pit) via odin turned out to be a Fail
I guess the eMMC is not functional resulting in a hardware failure
Thanks for the help @tallman43
If anyone else has suggestions, feel free to post them here
Dz-Horse said:
I have a feeling the eMMC flash storage has failed and therefore i have a hardware failure
This is true
Click to expand...
Click to collapse
Has this happened to your S3?
I havent tinkered with anything and this happens
I just installed a ROm and left it for a year
Oh well
Yes it happened to me same problem