{Q] Unable to write to nand VIA Odin Mode on SG3 - Galaxy S I9000 Q&A, Help & Troubleshooting

HI there
I had a bootloop issue with my sg3. I am unable to get into recovery mode so All I am able to do is get into Download mode ( Odin)
Tried to flash a stock firmware and this is what happens
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXEMF1_I9300TMUEMF1_I9300BVEMF1_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> tz.img
<ID:0/003> NAND Write Start!!
<ID:0/003> sboot.bin
<ID:0/003> system.img
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
I have tried this is on multiple computers and same issue. After a bit of googling I gather its to do with my partition being read only or something but I am too much of a noob to try and go play about with that stuff
can some one please help me and direct me .
I just want the phone to work again, Its outside warranty and i cant afford to buy a new one

Try getting different firmware and try again...
And, please, next time post in correct forum
Sent from my GT-I9300 using xda app-developers app

Related

S3 9305 LTE - Unable to do just about anything

You will have to ignore my lack of knowledge on this, still don't play around with phones much , but anyway.
Recently iv been using a custom Rom of 4.4 Kitkat cyanogen mod Unofficial.
It was working fine, nothing wrong.
If found my phone this morning stuck in a bootloop, so i threw it into recovery and had a look, iv now apparently go 0mb of storage, unable to mount any system, data etc.
Iv tried taking it back to stock with Odin, but no joy as it cant seem access it.
Im unable to flash a new ROM from extSD, it just fails.
Any suggestions, and if u want more info just say
Need more information like where does Odin fail .
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9305ZHALI7_I9305TGYALI6_I9305ZHALI1_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> system.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Is a copy from the odin text output
Damaged Nand you need a new motherboard .

[Q] Root after unroot with Kies?

I've come across various other threads concerning this topic with other devices, but none are exactly like my issue.
I rooted originally with Odin and CF autoroot with no issues. Now me being the noob that I am, I un-rooted with Kies to check for any updates. The process went fine, however my device status still says "custom" and I'm unable to re-root using the same method that I did before. I get a "fail" in Odin after the cache.img process and have to remove the battery to reboot device.
Has anyone had this issue or am I the only idiot to unroot this beast of a phone?
Best bet. Odin back to stock and then reroot and forget about updates.
BAD ASS NOTE 4 + BAD ASS GEAR S
I just tried that. Downloaded the firmware from sammobile and used Odin to install it. Then proceeded to re-root using CF autoroot again. Same "fail" message.
my Odin is as follows:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-trltetmo-trltetmo-smn910t.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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img.ext4
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
where's the issue?
I'd try a different version of Odin.
Razorfengraul said:
I just tried that. Downloaded the firmware from sammobile and used Odin to install it. Then proceeded to re-root using CF autoroot again. Same "fail" message.
my Odin is as follows:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-trltetmo-trltetmo-smn910t.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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img.ext4
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
where's the issue?
Click to expand...
Click to collapse
As said diff version or bad cf autoroot download. It can be many things. Try a fresh download of everything. Also when u Odin back to stock it went fine so it is something after. Bad download
BAD ASS NOTE 4 + BAD ASS GEAR S

need help fast..

i have problem.... my gfs samsung s i9070 somehow bricked and wont pass through the bootscreen. wont let me enter recovery,,but it goes to download mode. i tried to flash it with stock rom but every time i get fail msg and error on mby 20-30% progress... can anyone explain me what am i doing wrong ??
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9070XXLQE_I9070OXXLQE_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> kernel.bin.md5
<ID:0/003> NAND Write Start!!
<ID:0/003> modem.bin.md5
<ID:0/003> system.img.md5
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Kenannp said:
i have problem.... my gfs samsung s i9070 somehow bricked and wont pass through the bootscreen. wont let me enter recovery,,but it goes to download mode. i tried to flash it with stock rom but every time i get fail msg and error on mby 20-30% progress... can anyone explain me what am i doing wrong ??
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9070XXLQE_I9070OXXLQE_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> kernel.bin.md5
<ID:0/003> NAND Write Start!!
<ID:0/003> modem.bin.md5
<ID:0/003> system.img.md5
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Click to expand...
Click to collapse
Try other USB port. Let me known if it works.
Force said:
Try other USB port. Let me known if it works.
Click to expand...
Click to collapse
did try... even tried on other pc but still same problem... went to buddy to repair it in service shop... he said that something is wrong with usb on the phone... so i left it there to get fixed. thx tho

Samsung SM-G870A ATT Stuck in Downloading Mode - need help please

Issues began when I installed Lollipop on rooted phone. When flashing a custom rom it will not boot up. I cannot get to a recovery screen but can put it in download mode (Odin). I have downloaded the stock ATT rom and attempted to flash with odin but it fails everytime. I get the following on the screen.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1100)..
<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> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
I have updated the samsung drivers and do not know where to go from here. any help is appreciated.
Gdogius

Phone hard bricked out of nowhere, need some advice on what to do next.

I was using an app to disable the Android APK Signature verification to install the Youtube Vanced APK. Phone rebooted and suddenly I no longer had a system partition. I've tried going through ODIN and flashing the CSC, HOME_CSC, AP, PIT, etc., and in most cases it simply hangs when it tries to write to a partition, then tells me "Complete(Write) operation failed.", I've also tried toggling the Re-Partition option in the Options tab of Odin, but that doesn't help either.
I want to try to do a nand erase, as nothing else seems to working, but I don't know the consequences of that. I can currently still boot into TWRP, as no flashing attempts in Odin were successful, and I've already backed up everything other than the System and System Image options to an SD card. If I do a nand erase, what should I do after?, should I just flash everything normally with that option checked? I'll also post a log from a failed Odin flash if that helps at all.
Code:
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 808 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> param.bin
<ID:0/003> up_param.bin
<ID:0/003> cm.bin
<ID:0/003> keystorage.bin
<ID:0/003> recovery.img
<ID:0/003> modem.bin
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> modem_debug.bin
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> cache.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Daniel41550 said:
I was using an app to disable the Android APK Signature verification to install the Youtube Vanced APK. Phone rebooted and suddenly I no longer had a system partition. I've tried going through ODIN and flashing the CSC, HOME_CSC, AP, PIT, etc., and in most cases it simply hangs when it tries to write to a partition, then tells me "Complete(Write) operation failed.", I've also tried toggling the Re-Partition option in the Options tab of Odin, but that doesn't help either.
I want to try to do a nand erase, as nothing else seems to working, but I don't know the consequences of that. I can currently still boot into TWRP, as no flashing attempts in Odin were successful, and I've already backed up everything other than the System and System Image options to an SD card. If I do a nand erase, what should I do after?, should I just flash everything normally with that option checked? I'll also post a log from a failed Odin flash if that helps at all.
Code:
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 808 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> param.bin
<ID:0/003> up_param.bin
<ID:0/003> cm.bin
<ID:0/003> keystorage.bin
<ID:0/003> recovery.img
<ID:0/003> modem.bin
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> modem_debug.bin
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> cache.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
"Total Binary size: 808 M"
You aren't flashing all the required files in odin. Total binary size should be between 4000 and 6000 M (Mb).
Frick_trump said:
"Total Binary size: 808 M"
You aren't flashing all the required files in odin. Total binary size should be between 4000 and 6000 M (Mb).
Click to expand...
Click to collapse
Yup, I was skipping out on the AP file since I didn't want to flash the system yet, only recovery because the real system ap wouldn't flash in another attempt.
For anyone reading in the future, I had to do a nand erase and reflash the latest version of the the system software (all files). An older version wouldn't work, then had to reset a few times to be able to toggle the OEM Unlock option.

Categories

Resources