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...
Related
I have the Bell GSIII (i747) and I bricked it while playing around with the Toolkit. I downloaded the stock firmware from here, but whenever I flash it, Odin says this:
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCALEM_I747ATTALEM_I747UCALEM_HOME.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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
and by phone says: "SECURE CHECK FAIL: aboot"
aboot.mbn is a file inside the tar.
I can access Recovery and Download mode easily, but the problem is that when my phone boots, It flashes SAMSUNG, and then Samsung Galaxy S III, but then the screen goes black. To reboot it again, I have to pull the battery.
Any help would be greatly appreciated, thanks!
--Jeremy
http://forum.xda-developers.com/showthread.php?t=1727443
You can try that thread there. The same thing you are experiencing has happened before I Hard Bricked my phone.
Just be careful when you are messing around with the S3 it can be so confusing with all the S3 Variants out there.
Hopefully this will workout for ya
Fuzz21 said:
http://forum.xda-developers.com/showthread.php?t=1727443
You can try that thread there. The same thing you are experiencing has happened before I Hard Bricked my phone.
Just be careful when you are messing around with the S3 it can be so confusing with all the S3 Variants out there.
Hopefully this will workout for ya
Click to expand...
Click to collapse
Yeah, I'm reading this now. I just did what it said, but still no dice.
JibbsIsMe said:
I have the Bell GSIII (i747) and I bricked it while playing around with the Toolkit. I downloaded the stock firmware from here, but whenever I flash it, Odin says this:
and by phone says: "SECURE CHECK FAIL: aboot"
aboot.mbn is a file inside the tar.
I can access Recovery and Download mode easily, but the problem is that when my phone boots, It flashes SAMSUNG, and then Samsung Galaxy S III, but then the screen goes black. To reboot it again, I have to pull the battery.
Any help would be greatly appreciated, thanks!
--Jeremy
Click to expand...
Click to collapse
Can you flash a rom in recovery? Also do you have Odin set to the correct settings?
I had a problem with mine where Odin wasn't doing anything at all. It would start but never finished. I changed the USB port and was good after that. Weird because my sgs2 and sgs3 international were fine using the one USB port. Just a thought to try a different port if it stops or fails
Sent from my SGH-I747M using xda app-developers app
brfield said:
Can you flash a rom in recovery? Also do you have Odin set to the correct settings?
Click to expand...
Click to collapse
I can't flash ROMs, since I can't seem to figure out how to get things onto my SD card or my External SD Card.
Problem solved!
JibbsIsMe said:
I can't flash ROMs, since I can't seem to figure out how to get things onto my SD card or my External SD Card.
Click to expand...
Click to collapse
OK, I got it. First, I followed this: http://www.epiccm.org/2012/06/cwm-recovery-on-all-sgs3-lte-variants.html
I stopped right after step 8. I then put my Ext SD into my old phone, formatted it, and put on this: http://forum.xda-developers.com/showthread.php?t=1732191
Then I went into recovery, and flashed that ROM. Then rebooted, and I'm fine now! YAY!
I almost wasted $730....
--Jeremy
Awesome stuff !!
Mine is still a 500$ paper weight, LOL hopefully I can fix it :S
Good luck, I would hate to lose my phone on it's first day...
JibbsIsMe said:
Good luck, I would hate to lose my phone on it's first day...
Click to expand...
Click to collapse
Thanks budd
I really hope I can resurrect it from the Dead.
JibbsIsMe said:
I have the Bell GSIII (i747) and I bricked it while playing around with the Toolkit. I downloaded the stock firmware from here, but whenever I flash it, Odin says this:
and by phone says: "SECURE CHECK FAIL: aboot"
aboot.mbn is a file inside the tar.
I can access Recovery and Download mode easily, but the problem is that when my phone boots, It flashes SAMSUNG, and then Samsung Galaxy S III, but then the screen goes black. To reboot it again, I have to pull the battery.
Any help would be greatly appreciated, thanks!
--Jeremy
Click to expand...
Click to collapse
I hate to threadjack, but this is the only thread I can find mention of this error with the sgs3 with.
mine did the same thing last night, thought I bricked.. but it didnt brick, used the phone all day today with no problems, tried to root again today with at&t method with odin, and I keep getting the same error. Its a bell i747m using odin 3.0.7
Any ideas?
Edit: Also I have tried several usb ports and a couple different cables.
Hey Folks,
My phone is bricked. Here are the events before and after the crash.
Model: I-9100
I had installed CM10 ROM (ver. 25-Aug-2012) on my phone. It worked fine for a week and then while using the camera app, the phone froze. I restarted it, but it kept getting stuck at the boot logo. I could get into the download mode but not recovery. So I used ODIN to re-flash the same ROM, but ODIN got stuck at NAND write step. I tried it several times - changed the laptop - changed the cable - changed the ROM - nothing happened. Same thing, it either gets stuck at NAND or SBL.BIN.
I went through a lot of XDA pages and tried flashing the ICS stock ROM - same result - stuck at NAND/SBL. Tried both the 1-file and 3-file as well as the one with repartition (PIT) file. Nothing works. In case of repartition, it gets stuck at repartition step itself.
Also, over my last 5 tries the binary count is not changing. It is stuck at 13 and current binary shows as Samsung Official.
My warranty is not valid as I bought it in India but am in the US now. It's only 2 months old.
Summary: Download mode - Yes, Recovery Mode - No, NAND / SBL.bin fail, Stock ROM fail
Please help.
1) Have I hard bricked it?
2) Do I have to JTAG it? Any idea if anyone does it in Minneapolis? Or do I have to send it to "mobiletechvideos"?
3) I have a CWM recovery file on my external SD card. Is it of any use?
ODIN Log:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLP7_I9100ODDLP9_I9100DDLPA_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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> zImage
<ID:0/005> NAND Write Start!!
Then it gets stuck here for more than half hr and i just unplug it.
Thanks
It doesn't seem like a hard brick so that is kindo of lucky! However I have never cime across anyone with that problem! Why don't you try using odin to flash latest siyah kernel then try entering recovery and wipe data+cache and re-flash rom, hopefully it will work!
Sent from my GT-I9100 using xda premium
insat3d said:
Hey Folks,
My phone is bricked. Here are the events before and after the crash.
Model: I-9100
I had installed CM10 ROM (ver. 25-Aug-2012) on my phone. It worked fine for a week and then while using the camera app, the phone froze. I restarted it, but it kept getting stuck at the boot logo. I could get into the download mode but not recovery. So I used ODIN to re-flash the same ROM, but ODIN got stuck at NAND write step. I tried it several times - changed the laptop - changed the cable - changed the ROM - nothing happened. Same thing, it either gets stuck at NAND or SBL.BIN.
I went through a lot of XDA pages and tried flashing the ICS stock ROM - same result - stuck at NAND/SBL. Tried both the 1-file and 3-file as well as the one with repartition (PIT) file. Nothing works. In case of repartition, it gets stuck at repartition step itself.
Also, over my last 5 tries the binary count is not changing. It is stuck at 13 and current binary shows as Samsung Official.
My warranty is not valid as I bought it in India but am in the US now. It's only 2 months old.
Summary: Download mode - Yes, Recovery Mode - No, NAND / SBL.bin fail, Stock ROM fail
Please help.
1) Have I hard bricked it?
2) Do I have to JTAG it? Any idea if anyone does it in Minneapolis? Or do I have to send it to "mobiletechvideos"?
3) I have a CWM recovery file on my external SD card. Is it of any use?
ODIN Log:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLP7_I9100ODDLP9_I9100DDLPA_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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> zImage
<ID:0/005> NAND Write Start!!
Then it gets stuck here for more than half hr and i just unplug it.
Thanks
Click to expand...
Click to collapse
I have had the same problem few months ago. Finally, I have managed to kill it when I tried to flash the bootloader - it got stuck at the beginning (just like with everything else that I tried to flash - ROMs, kernels...), no more signs of life (no charging, no download mode, nothing), andd after that Samsung service center replaced the motherboard. I think that's the only way, but you may try everything before you send it for repair. There's a thread in this forum dedicated to unflashable phones, try to get help there.
insat3d said:
Hey Folks,
My phone is bricked. Here are the events before and after the crash.
Model: I-9100
I had installed CM10 ROM (ver. 25-Aug-2012) on my phone. It worked fine for a week and then while using the camera app, the phone froze. I restarted it, but it kept getting stuck at the boot logo. I could get into the download mode but not recovery. So I used ODIN to re-flash the same ROM, but ODIN got stuck at NAND write step. I tried it several times - changed the laptop - changed the cable - changed the ROM - nothing happened. Same thing, it either gets stuck at NAND or SBL.BIN.
I went through a lot of XDA pages and tried flashing the ICS stock ROM - same result - stuck at NAND/SBL. Tried both the 1-file and 3-file as well as the one with repartition (PIT) file. Nothing works. In case of repartition, it gets stuck at repartition step itself.
Also, over my last 5 tries the binary count is not changing. It is stuck at 13 and current binary shows as Samsung Official.
My warranty is not valid as I bought it in India but am in the US now. It's only 2 months old.
Summary: Download mode - Yes, Recovery Mode - No, NAND / SBL.bin fail, Stock ROM fail
Please help.
1) Have I hard bricked it?
2) Do I have to JTAG it? Any idea if anyone does it in Minneapolis? Or do I have to send it to "mobiletechvideos"?
3) I have a CWM recovery file on my external SD card. Is it of any use?
ODIN Log:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLP7_I9100ODDLP9_I9100DDLPA_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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> zImage
<ID:0/005> NAND Write Start!!
Then it gets stuck here for more than half hr and i just unplug it.
Thanks
Click to expand...
Click to collapse
sounds to me like your internal storage is damaged. I guess it's a warrenty issue
alexkno said:
sounds to me like your internal storage is damaged. I guess it's a warrenty issue
Click to expand...
Click to collapse
I hope it is not a warranty issue. I spoke to sammy (US), they said they don't cover warranty from outside US. (
Is there any way to confirm hardware damange??
UltimateAnas said:
It doesn't seem like a hard brick so that is kindo of lucky! However I have never cime across anyone with that problem! Why don't you try using odin to flash latest siyah kernel then try entering recovery and wipe data+cache and re-flash rom, hopefully it will work!
Click to expand...
Click to collapse
pilgrim011 said:
I have had the same problem few months ago. Finally, I have managed to kill it when I tried to flash the bootloader - it got stuck at the beginning (just like with everything else that I tried to flash - ROMs, kernels...), no more signs of life (no charging, no download mode, nothing), andd after that Samsung service center replaced the motherboard. I think that's the only way, but you may try everything before you send it for repair. There's a thread in this forum dedicated to unflashable phones, try to get help there.
Click to expand...
Click to collapse
But my phone is not dead. I am able to boot it into download mode. So I am guessing it is softbricked right? Also, i tried flashing Siyah kernel (latest and the one before). It updated the binary count. So the binary counter is not stuck as I had mentioned earlier. But it still got stuck at the NAND write step.
From what I understand, the kernel does change from "Samsung official" when I flash stock ROM to "Custom ROM" when I flashed Siyah and back to "Samsung official" when I re-flashed it. But it gets stuck after that. Any ideas why?
Thanks
insat3d said:
I hope it is not a warranty issue. I spoke to sammy (US), they said they don't cover warranty from outside US. (
Is there any way to confirm hardware damange??
But my phone is not dead. I am able to boot it into download mode. So I am guessing it is softbricked right? Also, i tried flashing Siyah kernel (latest and the one before). It updated the binary count. So it is not stuck as I had mentioned earlier.
Any other ideas guys?
Thanks
Click to expand...
Click to collapse
Visit this thread: forum.xda-developers.com/showthread.php?t=1457458
If your phone doesn't work after that, then it's as good as dead
Swyped from my Samsung Galaxy SII
Supercharged ParanoidAndroid 2.12
Dorimanx kernel 5.78
GT I9100
Next phone: Galaxy NOTE II
Jokesy said:
Visit this thread: forum.xda-developers.com/showthread.php?t=1457458
If your phone doesn't work after that, then it's as good as dead
Click to expand...
Click to collapse
I tried both ICS and GB mentioned on this link. It always gets stuck after zImage when I try without PIT file or set partition when I try partition.
Is JTAG going to be of any help here?
insat3d said:
I tried both ICS and GB mentioned on this link. It always gets stuck after zImage when I try without PIT file or set partition when I try partition.
Is JTAG going to be of any help here?
Click to expand...
Click to collapse
have you tried everything there?
Swyped from my Samsung Galaxy SII
Supercharged ParanoidAndroid 2.12
Dorimanx kernel 5.78
GT I9100
Next phone: Galaxy NOTE II
Jokesy said:
have you tried everything there?
Click to expand...
Click to collapse
Yes, I did. I tried all possible combinations. I even tried the GB ROM.
I also tried Heimdall. It still gets stuck at the same place as ODIN. In both, the Kernel gets uploaded and then it just gets stuck indefinitely. (Heimdall crashes after a while).
Couple of ques:
1) If my NAND memory is corrupt. Can JTAG fix this?
2) If JTAG can't fix this and I were to try getting it repaired outside warranty. How much will it cost? Do I have to replace the entire motherboard?
I DONT have a valid warranty. Please let me know
insat3d said:
Yes, I did. I tried all possible combinations. I even tried the GB ROM.
I also tried Heimdall. It still gets stuck at the same place as ODIN. In both, the Kernel gets uploaded and then it just gets stuck indefinitely. (Heimdall crashes after a while).
Couple of ques:
1) If my NAND memory is corrupt. Can JTAG fix this?
2) If JTAG can't fix this and I were to try getting it repaired outside warranty. How much will it cost? Do I have to replace the entire motherboard?
I DONT have a valid warranty. Please let me know
Click to expand...
Click to collapse
I don't think so. You might have to replace your motherboard.
Swyped from my Samsung Galaxy SII
Supercharged ParanoidAndroid 2.12
Dorimanx kernel 5.78
GT I9100
Next phone: Galaxy NOTE II
insat3d said:
Yes, I did. I tried all possible combinations. I even tried the GB ROM.
I also tried Heimdall. It still gets stuck at the same place as ODIN. In both, the Kernel gets uploaded and then it just gets stuck indefinitely. (Heimdall crashes after a while).
Couple of ques:
1) If my NAND memory is corrupt. Can JTAG fix this?
2) If JTAG can't fix this and I were to try getting it repaired outside warranty. How much will it cost? Do I have to replace the entire motherboard?
I DONT have a valid warranty. Please let me know
Click to expand...
Click to collapse
if I am not mistaken JTAG will give access to core, but I guess (but I am not a technician) that if the internal storage is corrupted and not even repartition helps, then I guess only replacing it might help.
I'd advise to watch out for a repaircenter near you and ask
Ok...so the phone is 2 months old.....
Purchased in India but being used in the US?.......
I don't care what Samsung says.....it sounds to me like they are trying to 'fob you off'. I personally would take this further. ....contact Samsung HO, contact your local trading standards department (or whatever it's called).
No warranty. ....that's just corporate bulls**t.......the age of the phone (if it can be proved) is what's important.....I think you have a very strong case here.....go with it.
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
Similar problem i9100T
I have the same problem in that the phone stops at nand write when attempting to install package. I can only get into download but it will flash a bootloader but that is all. I believe that it may be necessary to reload the .pit file but I cannot find where this would be found. I presume if this were included it would reinstall this and would fix the internal storage. Any advise on this would be gratefully received.
Galaxy S2 stuck at NAND WRITE START
MODS.... please delete this post.
Help! I flashes Siyah's kernel on my S2 (it was on stock 2.3.3) and now it won't boot and all I get is the i9100 logo and a yellow triangle with a warning sign. I have searched the forums and googled but can't find anything on this :/ I'm not sure if this is the "yellow triangle" most people seem to be talking about as I can't really do anything to "remove" it as they suggest.
Dexter_prog said:
Help! I flashes Siyah's kernel on my S2 (it was on stock 2.3.3) and now it won't boot and all I get is the i9100 logo and a yellow triangle with a warning sign. I have searched the forums and googled but can't find anything on this :/ I'm not sure if this is the "yellow triangle" most people seem to be talking about as I can't really do anything to "remove" it as they suggest.
Click to expand...
Click to collapse
I'm assuming you picked up the latest siyah version. Its for ICS not GB.
Download the file from Jokesy's post here. http://forum.xda-developers.com/showthread.php?p=32689470
Siyah for gingerbread and install it via Odin.
Sent from my GT-I9100 using xda app-developers app
Ah, Jesus. I'm such an idiot!. After reading the forums for hours making sure I wasn't gonna make a mistake I ended up flashing an ICS kernel on a GB rom.
Anyway, I did it but it is still stock at boot :s What do I do? Should I flash a stock unbranded ICS rom? I mean, those come with a kernel, right?
Flashing siyah through odin didnt work? Then you might want to install a new stock firmware. Download one from sammobile.com and install again via Odin the same way you installed siyah. GB or ICS (4.0.3 only to avoid risk of the emmc bug) and then try again.
It does come with the stock kernel.
The thread link I provided talks about a similar problem. Reading that might help too.
Good luck
EDIT: if youre unsure about your correct formware. this link will provide you the ICS firmware for most regions. Pick the one matching region if possible. Best signal reception and all that. http://forum.xda-developers.com/showthread.php?p=23562857
Sent from my GT-I9100 using xda app-developers app
I am tryiong to find a stock rom but all come in zip format and odin asks for .tar
Where are tar roms for odin? :S
You must unzip them
I did and the flashing on ODIN failed, I got this:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100UHLPS_I9100UHLPG_I9100AROLP4_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!!
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<ID:0/009> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
and now it won't but and I get: "firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
What do I do?
god please help me I can't flash anything, it keeps failing! Please keep in mind I come from a stock gingerbread rom. it is because the bootloader and everything is locked or something?
I tried this and it won't flash either: http://forum.xda-developers.com/showthread.php?t=1457458
Sorry. Kinda busy atm so this thread slipped my mind.
Which version of Odin are you using? Some report problems with 3.4.. use 1.85 if you can.
Ensure your phone has sufficient charge
Do you have your phone drivers installed? They should be.
Is KIES running in the background? Kill it. KIES is known to interfere with Odin.
Sent from my GT-I9100 using xda app-developers app
HAXTREME said:
Sorry. Kinda busy atm so this thread slipped my mind.
Which version of Odin are you using? Some report problems with 3.4.. use 1.85 if you can.
Ensure your phone has sufficient charge
Do you have your phone drivers installed? They should be.
Is KIES running in the background? Kill it. KIES is known to interfere with Odin.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
I tried with both 3.4 and 1.83 from the recovery package.
I don't know if I can charge it as when I plug it it displays the same "firmware upgrade encountered an issue" message and I am unsure weather it is charging or not. Anyway, I charged it to 100% before all this madness began.
I uninstalled KIES before trying all of this.
pd: no problem man, I'm not complaining to your or anyone, it's just I got really nervous and don't know what to do. Plus the phone is out of warranty.
GOT IT.
Problem: I was not pluging the phone DIRECTLY to a USB port (AND ODIN DEMANDS YOU TO PLUG THE PHONE DIRECTLY TO A USB PORT, SO DON'T USE HUBS, PCI CARDS OR WHATEVER). My computer's usb ports stopped working months ago so I bought a PCI-to-USB card to have USB ports.
Solution: After hours of googling I came across this XDA thread: http://forum.xda-developers.com/showpost.php?p=26748860&postcount=2
As you can see, he mentions what I said about ODIN (I learned it from him/her).
So the solution is to use ODIN with the mobile phone connected directly to the usb port
And to fix my problem: I just used the recovery package from here: http://forum.xda-developers.com/showthread.php?t=1457458
which worked beautifully.
You wouldn't believe I just came back online to pm you to do just that...the USB bit. And to confirm you have an i9100 and not the G variant.
Anwyays glad it worked out fine mate. Sorry I couldn't be of much help. Good to hear you're sorted now. Enjoy the ICS/ JB goodness.
Cheers
Edit.Do remember to make all the necessary backups though. EFS, Nand et al.
Sent from my GT-I9100 using xda app-developers app
Hi everyone. I've been meaning to sell my old S4 for awhile now and I haven't been keeping up with the root scene, so clearly I might have screwed something up. I was originally running my S4 rooted with Hyperdrive S15 (Android 4.3) with TWRP + Safestrap 3.71. I deleted the hyperdrive slot and booted into the stock ROM. After that, I used TWRP to wipe everything (dalvik cache/cache/data/factory reset) then after rebooting the phone, it just stays loads up the "Samsung" Screen with the custom symbol under it. I've tried looking at guides online to try to unbrick/fix this phone, but still have no idea what to do. I've tried booting it into download mode, but for some reason, it only goes into recovery mode (I do Vol Up + Home + Power, then as soon as it vibrates, I don't press the power button anymore). I was trying to use Odin but I can't get it to go into download mode, so when I plug it in, Odin doesn't see it. Can anyone give me some ideas/info on how to fix this?
EDIT: Here are the things I have tried doing:
1. I have used both Odin v1.85 and 3.09 to try and flash the VRUEMK2 firmware and the absolute newest firmware (4.4.2 NK2). Here's the log:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUFNK1_I545VZWFNK1_I545VRUFNK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> modem.bin
<ID:0/003> NON-HLOS.bin
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Fails on both old and new Odins.....hmmmm...
2. Kies 2.6 and Kies 3 do not seem to be able to find the device when I load them.
Download mode is Power + Vol Down + Home. Press and hold all 3 until you see a warning on phones screen. Once you are at warning screen simply press Vol up once. If this doesn't work you may have to get a download mode jig. I had to buy one for my old S2, they can be found on ebay pretty cheap so you know.
Hope this helps!
Sent from my A0001 using XDA Free mobile app
Klown80 said:
Download mode is Power + Vol Down + Home. Press and hold all 3 until you see a warning on phones screen. Once you are at warning screen simply press Vol up once. If this doesn't work you may have to get a download mode jig. I had to buy one for my old S2, they can be found on ebay pretty cheap so you know.
Hope this helps!
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Wow I feel dumb now....thanks! It's in download mode now. I'll try to do the rest from here!
Hmmm..how long does it normally take for Odin to do it's thing? I'm following this guide:
http://www.androidrootz.com/2013/06/how-to-unroot-unbrick-galaxy-s4.html
It's been in the "downloading" screen for quite awhile.
EDIT: It says "failed". Hmmm. Figured I should have paid attention to when the article was written. I was previously on VRUEMK2 so I'm going to try this guide:
http://forum.xda-developers.com/showthread.php?t=2578209
Would these be the correct files?
ma70ent said:
Hmmm..how long does it normally take for Odin to do it's thing? I'm following this guide:
http://www.androidrootz.com/2013/06/how-to-unroot-unbrick-galaxy-s4.html
It's been in the "downloading" screen for quite awhile.
EDIT: It says "failed". Hmmm.
Click to expand...
Click to collapse
Sent from my A0001 using XDA Free mobile app
Looking at that link it shows 4.2.2 firmware for your VZW S4, going by your first post you were on a stock based 4.3 rom since you are using safestrap recovery. If that is correct then your issue is that you need a 4.3 or higher firmware, Samsung made it so you cannot downgrade most firmwares now. If I remember correctly, xda doesn't want us posting links to Samsung Web pages so please Google "sammobile" this will pull up Samsung mobile firmware download page as first result. Click on that link and then enter you model number in search box in top right of page. Enter model number and hit enter. This will pull up a list of firmwares for your model, make sure you choose 4.3 or higher firmware (4.3, 4.4, 4.4.2, or 4.4.4) and download it. Once downloaded please try Odin again.
You will have to make an acct on Samsung site to download firmware but it only takes a few mins and it's free.
Hope this helps, good luck!
Sent from my A0001 using XDA Free mobile app
Klown80 said:
Sent from my A0001 using XDA Free mobile app
Looking at that link it shows 4.2.2 firmware for your VZW S4, going by your first post you were on a stock based 4.3 rom since you are using safestrap recovery. If that is correct then your issue is that you need a 4.3 or higher firmware, Samsung made it so you cannot downgrade most firmwares now. If I remember correctly, xda doesn't want us posting links to Samsung Web pages so please Google "sammobile" this will pull up Samsung mobile firmware download page as first result. Click on that link and then enter you model number in search box in top right of page. Enter model number and hit enter. This will pull up a list of firmwares for your model, make sure you choose 4.3 or higher firmware (4.3, 4.4, 4.4.2, or 4.4.4) and download it. Once downloaded please try Odin again.
You will have to make an acct on Samsung site to download firmware but it only takes a few mins and it's free.
Hope this helps, good luck!
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Went to sammobile, registered, and downloaded the VRUEMK2 firmware (android 4.3). I tried using Odin 3.09 for this and it failed again. Should I try to flash 4.4 firmware on it? I'm only selecting the "AP" option. Should I use any other options other than f.reset, auto reboot, and AP?
Also, when I try to turn it on normally or even try recovery mode (vol up + home + power) it says "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
ma70ent said:
Went to sammobile, registered, and downloaded the VRUEMK2 firmware (android 4.3). I tried using Odin 3.09 for this and it failed again. Should I try to flash 4.4 firmware on it? I'm only selecting the "AP" option. Should I use any other options other than f.reset, auto reboot, and AP?
Also, when I try to turn it on normally or even try recovery mode (vol up + home + power) it says "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
Click to expand...
Click to collapse
You could try the 4.4, or you could just download Kies and see if it will restore it for you. Yes you are using correct space (AP) and right things checked. Another though would be to try a lower version of Odin and use the PDA slot to flash it, I vaguely remember someone having trouble on here using newest version to restore phone, he had to use older version.
Sent from my A0001 using XDA Free mobile app
Klown80 said:
You could try the 4.4, or you could just download Kies and see if it will restore it for you. Yes you are using correct space (AP) and right things checked. Another though would be to try a lower version of Odin and use the PDA slot to flash it, I vaguely remember someone having trouble on here using newest version to restore phone, he had to use older version.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Yup. Tried Kies 3 and it says device wasn't compatible, but Kies 2.6 seems to be "Connecting" forever. I'll just wait until my 4.4 firmware finishes downloading and I'll try both the new Odin and the old Odin.
Klown80 said:
You could try the 4.4, or you could just download Kies and see if it will restore it for you. Yes you are using correct space (AP) and right things checked. Another though would be to try a lower version of Odin and use the PDA slot to flash it, I vaguely remember someone having trouble on here using newest version to restore phone, he had to use older version.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Okay I just went at it again. Quick question, if Odin runs through but fails right at the end (literally write as the thing is almost over, it says "Complete Write Operation Failed"), should I just keep trying?
ma70ent said:
Okay I just went at it again. Quick question, if Odin runs through but fails right at the end (literally write as the thing is almost over, it says "Complete Write Operation Failed"), should I just keep trying?
Click to expand...
Click to collapse
What part is it failing on, system? That is strange that it's still failing since you are trying to flash the newest firmware available for your device. You can try it again but if it failed once it will most likely keep failing. You might want to check md5 sums on the downloads to be sure your not getting a corrupt download.
Sent from my A0001 using XDA Free mobile app
Klown80 said:
What part is it failing on, system? That is strange that it's still failing since you are trying to flash the newest firmware available for your device. You can try it again but if it failed once it will most likely keep failing. You might want to check md5 sums on the downloads to be sure your not getting a corrupt download.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Here's the log:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUFNK1_I545VZWFNK1_I545VRUFNK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> modem.bin
<ID:0/003> NON-HLOS.bin
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Fails on both Odins.....hmmmm...
Klown80 said:
What part is it failing on, system? That is strange that it's still failing since you are trying to flash the newest firmware available for your device. You can try it again but if it failed once it will most likely keep failing. You might want to check md5 sums on the downloads to be sure your not getting a corrupt download.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Alright. Actually, I did a lot of online searching and actually switched the usb port that I was using. After switching USB ports, I tried Odin again, flashed it, and it actually worked. Wow.
Anyways, I've thanked all of your posts, and of course, I thank you for spending the entire day with my problem.
ma70ent said:
Alright. Actually, I did a lot of online searching and actually switched the usb port that I was using. After switching USB ports, I tried Odin again, flashed it, and it actually worked. Wow.
Anyways, I've thanked all of your posts, and of course, I thank you for spending the entire day with my problem.
Click to expand...
Click to collapse
Sweet! Glad to hear you got it fixed! That was going to be my next suggestion. We're you by chance using a USB3 port? (it is blue if you look inside the USB port if it's usb3). For some reason most Android programming needs USB2 ports as they don't play very well with USB3.
Either way, Congratz on fixing your device, I may have given you a few pointers or helpful hints but you fixed it all on your own!
Sent from my SGH-I337 using XDA Free mobile app
Klown80 said:
Sweet! Glad to hear you got it fixed! That was going to be my next suggestion. We're you by chance using a USB3 port? (it is blue if you look inside the USB port if it's usb3). For some reason most Android programming needs USB2 ports as they don't play very well with USB3.
Either way, Congratz on fixing your device, I may have given you a few pointers or helpful hints but you fixed it all on your own!
Sent from my SGH-I337 using XDA Free mobile app
Click to expand...
Click to collapse
Actually my desktop has usb ports in the front (which aren't a direct connection to the mobo as far as I know) and of course, there are the normal usb ports in the back of it. I switched from the front one to the back one and all was well.
ma70ent said:
Actually my desktop has usb ports in the front (which aren't a direct connection to the mobo as far as I know) and of course, there are the normal usb ports in the back of it. I switched from the front one to the back one and all was well.
Click to expand...
Click to collapse
Yep it is usually best to connect directly to mobo instead any type of a USB hub, Android doesn't play very nice with those either!
Sent from my SGH-I337 using XDA Free mobile app
Klown80 said:
Yep it is usually best to connect directly to mobo instead any type of a USB hub, Android doesn't play very nice with those either!
Sent from my SGH-I337 using XDA Free mobile app
Click to expand...
Click to collapse
Hopefully this thread will help those in the future who make the same dumb mistakes I have. Haha...
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