Hello,
I had a GT-i9300 running custom ROM temasek V95. Today morning suddenly the display went off and I couldn't access my phone. On trying to restart the phone got stuck on the samsung screen and hasn't gone past it. I have clockworkMod recovery v.6.0.4.6 installed on my phone and when I open it it says the following:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_install
So, basically I can't do anything in the recovery. I have tried flashing with the SD card being out and in but has made no difference. I can get into download mode and have tried both Odin and heimdall but none of them work.
When I tried Odin and tried to flash stock ROM it just fails and says the following:
<ID:0/004> Added!!
<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> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
When I tried Heimdall and tried to flash stock ROM, it says "failed to confirm end of file transfer sequence" every time and I never get a blue progress bar showing that it is transferring. I have tried almost everything but the fact that I can get into download mode suggests me that there's still hope.
Looking at all the help I could find online, I believe the problem is with the recovery and not the actual ROM. I have tried flashing a different recovery but that hasn't made any difference either
Can anyone suggest me a way out of this? This is really frustrating and I would like to know if the phone is definitely bricked or not Looking forward to your suggestions.
Please need HELP!
Your emmc chip is either corrupt or broken. Try flashing the rescue firmware from general forum, including the pit.
If that doesn't work then you need a new motherboard.
Rescue firmware flash did not work
boomboomer said:
Your emmc chip is either corrupt or broken. Try flashing the rescue firmware from general forum, including the pit.
If that doesn't work then you need a new motherboard.
Click to expand...
Click to collapse
Tried rescue firmware including PIT. Did not work. Same problem with NAND write fail. Looks like I have to bid goodbye to this phone now.
Related
After my phone being fine for around 5 months, It suddenly bricked, and now is stuck in a boot loop. Download mode works, Recovery works, but when i try to flash with odin, I get this:
Code:
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
Recovery is fine, but I cant flash anything either.
Does my phone need repairing? If so can samsung find it's flashed? I was running 4.4.
Thanks in advance
Nand error fail is usually fatal, you can try a rescue firmware:
http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6&nocache=1&z=4402082341257483
But I wouldn't expect miracles. Your flash count/modified in download mode tells Samsung if your warranty is void.
Rores said:
After my phone being fine for around 5 months, It suddenly bricked, and now is stuck in a boot loop. Download mode works, Recovery works, but when i try to flash with odin, I get this:
Code:
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
Recovery is fine, but I cant flash anything either.
Does my phone need repairing? If so can samsung find it's flashed? I was running 4.4.
Thanks in advance
Click to expand...
Click to collapse
Change your computer or make a format. Trust me, it helps.
You can also try different USB ports, especially if you're using front one instead of back one.
Hi Devs,
I am stuck in a issue. I installed cm 12.0 (unofficial rom) to my Galaxy s3 GT-i9300 everything was working fine but suddenly it keeps on crashing randomly one day while calling my phone froze. I restarted the phone it stucked on SAMSUNG BOOT SCREEN.
I can go into download mode and recovery mode, currently using PhilzTouch 6 on recovery.
Things I have tried already.
Wiped Cache Partition
Wiped Data/Factory Reset
when i try to wipe cache or factory reset i get errors
E: can't mount /data or Formatting /sdcard/.android_secure
For some reason my phones internal memory is on the read only mode i tried to flash the stock rom as well so far no luck.
I tried 4 different stock roms none of them work they all stopped on nand write or setup connection
I followed the instruction below because thats what exactly happened to my phone but no luck when ever i try to load boot files into PDA it keeps failing.
http://forum.xda-developers.com/showthread.php?t=1840030
please guys i am tired and exhausted trying all different stuff guide me. I even tried PIT Files noting work. Thanks in advance
Try going back to stock/factory.
Boot in download mode (vol down+home+power).
Use Odin to flash stock recovery and firmware.
Once you are able to boot perfectly into touchwiz, can narrow down your points of failure and try again or try another ROM
blu88 said:
Try going back to stock/factory.
Boot in download mode (vol down+home+power).
Use Odin to flash stock recovery and firmware.
Once you are able to boot perfectly into touchwiz, can narrow down your points of failure and try again or try another ROM
Click to expand...
Click to collapse
Hi Blue,
Thanks for reply , so you meant to say i replace philztouch with stock recovery.
Correct me if i am wrong.
Replace philz with stock recovery and replace your rom with touchwiz. Figure out where you went wrong and then flash your custom rom again or flash a different custom rom.
Try flashing another recovery. Worked for me once
Thanks for Help
Can you send me link for GT-i9300 International Stock Recovery so i am installing exact thing it would be great help from you guys and i would really appreciate it.
blu88 said:
Replace philz with stock recovery and replace your rom with touchwiz. Figure out where you went wrong and then flash your custom rom again or flash a different custom rom.
Click to expand...
Click to collapse
Hi Blue i tried official recovery this what comes up and get fails
<ID:0/005> Added!!
<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> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
its problem with internal memory to read only is there any way to change it read write mod.
saqygee said:
Hi Blue i tried official recovery this what comes up and get fails
<ID:0/005> Added!!
<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> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
its problem with internal memory to read only is there any way to change it read write mod.
Click to expand...
Click to collapse
saqyee, you placed the stock recovery file in the PDA section right? DO NOT TOUCH THE PIT SECTION.
saqygee said:
Hi Blue i tried official recovery this what comes up and get fails
<ID:0/005> Added!!
<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> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
its problem with internal memory to read only is there any way to change it read write mod.
Click to expand...
Click to collapse
Nand write fail usually means emmc corrupt/damaged you could try the rescue firmware but this looks like hardware failure.
Sent from my LG-D855 using Tapatalk
Hello all,
I tried to search on internet and open a post on another forum to fix my problem but i had no success
Last friday I saw that my phone had a black screen and i was surprised because i didn't use it since the morning. I pressed the power button to turn it off or turn it on if it was already off and it's stuck on the "Samsung Galaxy SIII I-9300" logo without having any mood to go past that point.
I tried to remove the battery and put it in again.
I tried to let the battery run out of charge and charge it again for a bit.
I tried to remove the sd card.
Nothing solved it.
The phone can get into recovery and download mode.
In recovery mode there are some alerts at the bottom saying that "Can't mount /cache/recovery/command, /cache/recovery/log, /cache/recovery/last_log" and "Can't open /cache/recovery/log, /cache/recovery/last_log"
If i try to wipe or format cache i get an error: "format_volume: make_extf4fs failed on /dev/block/mmcblk0p8"
If i try to wipe Dalvik Cache nothing happen.
If i try to mount or format any of the /efs, /system, /cache, /preload, /data. it just gives me an error saying "error mounting /XYZ" or "error formatting /XYZ" with XYZ the various names.
My phone has ClockworkMod recovery v6.0.4.3 and a version of cyanogenmod (it's rooted).
The only thing i didn't try is to wipe data and factory reset. I want to keep this as the last resort.
I read online that it could even be an hardware problem so even a wipe data and a factory reset shouldn't work.
In any case i wonder if it's possible to recover any of the internal folders. I have made a backup two months ago but in the mean time I added phone numbers (that i haven't saved), photo, video and messages.
The download mode is recognized by Odin3 but since flashing another rom could cause a data loss, even in this case it's not what i'm trying to do.
If there's a way to use Odin3 as a data recovery tool, i'd be happy to know that.
If anyone has any idea i'm glad to hear them. Thanks in advance for any answer
Bumping it.
I tried to use adb to pull out the sdcard data, but since it can't mount it i had no success.
I'm tempted to flash a rom with odin without wiping data/factory reset, but i still am in doubt cause of a random data loss.
My priority is to recover most of the files in the phone. I even tried to backup on the external sdcard but even in this case it cannot mount /sdcard.
Please help!
Manuel.95 said:
Bumping it.
I tried to use adb to pull out the sdcard data, but since it can't mount it i had no success.
I'm tempted to flash a rom with odin without wiping data/factory reset, but i still am in doubt cause of a random data loss.
My priority is to recover most of the files in the phone. I even tried to backup on the external sdcard but even in this case it cannot mount /sdcard.
Please help!
Click to expand...
Click to collapse
What does it say when you cannot mount /sdcard?. I don't remember CWM but TWRP does include a file manager. I've just tried it and it can browse /sdcard right away. If CWM doesn't include a file manager perhaps as a last resort you could try flashing TWRP with Odin and then try accessing the internal memory from there.
andrescm said:
What does it say when you cannot mount /sdcard?. I don't remember CWM but TWRP does include a file manager. I've just tried it and it can browse /sdcard right away. If CWM doesn't include a file manager perhaps as a last resort you could try flashing TWRP with Odin and then try accessing the internal memory from there.
Click to expand...
Click to collapse
The "mounts and storage" menu has the folder inside the /sdcard (/efs, /system, /cache, /preload, /data). If i go to the "backup and restore" menu, any option refer to the /sdcard (backup to /sdcard, restore from /sdcard etc.) and every option simply show "E:Can't mount /sdcard", nothing else. I tried to see the log but it seems there's nothing regarding the /sdcard or it cannot load the log properly.
I could try to flash TWRP but it shouldn't erase my data right?
Manuel.95 said:
The "mounts and storage" menu has the folder inside the /sdcard (/efs, /system, /cache, /preload, /data). If i go to the "backup and restore" menu, any option refer to the /sdcard (backup to /sdcard, restore from /sdcard etc.) and every option simply show "E:Can't mount /sdcard", nothing else. I tried to see the log but it seems there's nothing regarding the /sdcard or it cannot load the log properly.
I could try to flash TWRP but it shouldn't erase my data right?
Click to expand...
Click to collapse
You will only write the recovery partition, nothing else. Here's a tutorial, you will be able to use the Odin method only. The latest version 2.8.6.1 works fine, I've been using it for about two months now.
https://twrp.me/devices/samsunggalaxys3internationalexynos.html
andrescm said:
You will only write the recovery partition, nothing else. Here's a tutorial, you will be able to use the Odin method only. The latest version 2.8.6.1 works fine, I've been using it for about two months now.
Click to expand...
Click to collapse
I tried but had no success. As i said the phone seems to be correctly recognized by odin but when i tried to flash TWRP it fails somehow.
Code:
<ID:0/010> Added!!
<ID:0/010> Odin engine v(ID:3.1100)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> SingleDownload.
<ID:0/010> recovery.img
<ID:0/010> NAND Write Start!!
<ID:0/010> FAIL!
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Manuel.95 said:
I tried but had no success. As i said the phone seems to be correctly recognized by odin but when i tried to flash TWRP it fails somehow.
Code:
<ID:0/010> Added!!
<ID:0/010> Odin engine v(ID:3.1100)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> SingleDownload.
<ID:0/010> recovery.img
<ID:0/010> NAND Write Start!!
<ID:0/010> FAIL!
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I am having similar issues..........my research points to me that its a hardware issue....emmc is gone !
tharmor said:
I am having similar issues..........my research points to me that its a hardware issue....emmc is gone !
Click to expand...
Click to collapse
Uhm, i reached that research too. So there's no hope...all data are lost and i can't even recover my phone?
Hey there,
i need some help please.
First things first.I never flashed my S3 and i never heard of Odin and Odin mode on my S3 until sunday.
On sunday i woke up and turned on my S3 and saw that it got stuck in a boot loop.
So i searched for solutions and found a post in which clearing the cache in the android recovery system would help.
So i took out the battery, put it back in and pressed the 3 buttons to get in the system.
I was shocked when i saw red text everywhere(E:failed to mount /efs(no such file or directory);E:failed to mount /system(no such file or directory) and so on)
So i searched again and found out that you may save your phone by flashing with Odin or try an emergency recovery via Kies.
I tried to do it with KIES but it was not recognizing my S3. It also didn't recognized it via Initialising by Model name and Serial number.
Also tried to deinstall and reinstall everything with no results.But the Name of the ROM was shown there so i started to search for it on sammobile.
i found it and tried to flash it. But it didnt work. Same with other Odin Versions.
I tried 3.07,3.09,3.10 and 3.10.7 but i always get the same error:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGNG3_I9300DBTGNG2_I9300XXUGNA8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I dont know what to do. I read that you can also do it with .pit files but that this should be the last option to try.
I would appreciate some help or if i can't do anything , at least some clarity htat i need to get me a new one.
I don't know if this Information is helpful but here are the infos from Odin mode:
Product name: GT-I9300
Custom binary download: No
Current binary: Samsung Official
System status: Official
If no one can help me, i thank you though for reading this.
Vehaboman said:
Hey there,
i need some help please.
First things first.I never flashed my S3 and i never heard of Odin and Odin mode on my S3 until sunday.
On sunday i woke up and turned on my S3 and saw that it got stuck in a boot loop.
So i searched for solutions and found a post in which clearing the cache in the android recovery system would help.
So i took out the battery, put it back in and pressed the 3 buttons to get in the system.
I was shocked when i saw red text everywhere(E:failed to mount /efs(no such file or directory);E:failed to mount /system(no such file or directory) and so on)
So i searched again and found out that you may save your phone by flashing with Odin or try an emergency recovery via Kies.
I tried to do it with KIES but it was not recognizing my S3. It also didn't recognized it via Initialising by Model name and Serial number.
Also tried to deinstall and reinstall everything with no results.But the Name of the ROM was shown there so i started to search for it on sammobile.
i found it and tried to flash it. But it didnt work. Same with other Odin Versions.
I tried 3.07,3.09,3.10 and 3.10.7 but i always get the same error:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGNG3_I9300DBTGNG2_I9300XXUGNA8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I dont know what to do. I read that you can also do it with .pit files but that this should be the last option to try.
I would appreciate some help or if i can't do anything , at least some clarity htat i need to get me a new one.
I don't know if this Information is helpful but here are the infos from Odin mode:
Product name: GT-I9300
Custom binary download: No
Current binary: Samsung Official
System status: Official
If no one can help me, i thank you though for reading this.
Click to expand...
Click to collapse
Instead of clearing cache from stock recovery,do a factory reset then go into download mode i try again with Odin.
Sent from my Nexus 4 using Tapatalk
Stevica Smederevac said:
Instead of clearing cache from stock recovery,do a factory reset then go into download mode i try again with Odin.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Tried it.No success.
This is the log i get when i do the the factory reset:
--Wipe data...
Formatting /data...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p12
Formatting /cache...
E:/format_volume: make_extf4fs failed on /dev/block/mmcblk0p8
Data wipe complete.
E:failed to mount /cache (Block device required)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Block device required)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Block device required)
E:Can't mount /cache/recovery/last install
E:Can't open /cache/recovery/last install
E:failed to mount /cache (Block device required)
The log in Odin stays the same.
Vehaboman said:
Tried it.No success.
This is the log i get when i do the the factory reset:
--Wipe data...
Formatting /data...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p12
Formatting /cache...
E:/format_volume: make_extf4fs failed on /dev/block/mmcblk0p8
Data wipe complete.
E:failed to mount /cache (Block device required)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Block device required)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Block device required)
E:Can't mount /cache/recovery/last install
E:Can't open /cache/recovery/last install
E:failed to mount /cache (Block device required)
The log in Odin stays the same.
Click to expand...
Click to collapse
I don't want to say outloud but it's not good. I think it's time to look for a replacement phone.(i hope i am wrong)
Sent from my Nexus 4 using Tapatalk
Stevica Smederevac said:
I don't want to say outloud but it's not good. I think it's time to look for a replacement phone.(i hope i am wrong)
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Kk. Thank you for your time and replies Stevica I'll watch this thread to see if more people have the same opinion.Just to be sure.
I wish you a nice day
Vehaboman said:
Kk. Thank you for your time and replies Stevica I'll watch this thread to see if more people have the same opinion.Just to be sure.
I wish you a nice day
Click to expand...
Click to collapse
I think you are down to repartitioning the device with a suitable pit file. The way I see it, it could have been a glitch that corrupted the NAND partitions.
Depending on how ODIN works (I don't know programming), it could spit out this error if it finds no partition(s). That would not necessarily mean nothing can be written to the NAND at all.
So then you might be able to get it back working by rebuilding those partitions with the pit file. But with the corrupted EFS I doubt you can revive it to the point where you can use cell connections again...
But then again, after rebuilding the partitions, could be possible with the KIES method which might work after that... (who knows how that black magic works with the serial number and all...)
I think it's worth a shot. Just for reference, I used pit flashing once on my GT-i9000. Worked flawlessly.
Hawaiihemd said:
I think you are down to repartitioning the device with a suitable pit file. The way I see it, it could have been a glitch that corrupted the NAND partitions.
Depending on how ODIN works (I don't know programming), it could spit out this error if it finds no partition(s). That would not necessarily mean nothing can be written to the NAND at all.
So then you might be able to get it back working by rebuilding those partitions with the pit file. But with the corrupted EFS I doubt you can revive it to the point where you can use cell connections again...
But then again, after rebuilding the partitions, could be possible with the KIES method which might work after that... (who knows how that black magic works with the serial number and all...)
I think it's worth a shot. Just for reference, I used pit flashing once on my GT-i9000. Worked flawlessly.
Click to expand...
Click to collapse
Thank you for your reply Hawaiihemd You gave me new hope. Can you eventually help me to find the right pit file? Since i read that using the wrong files can be devastating.
Vehaboman said:
Thank you for your reply Hawaiihemd You gave me new hope. Can you eventually help me to find the right pit file? Since i read that using the wrong files can be devastating.
Click to expand...
Click to collapse
I'd use the pit file from here if I were you: http://forum.xda-developers.com/showpost.php?p=52911794&postcount=2
Interesting thread over all by the way... Good luck. :good:
Hawaiihemd said:
I'd use the pit file from here if I were you: http://forum.xda-developers.com/showpost.php?p=52911794&postcount=2
Interesting thread over all by the way... Good luck. :good:
Click to expand...
Click to collapse
thank you how long does it usually take to get further than "Get PIT for mapping.."?
Ok.I tried every USB port and Odin stops always at "Get PIT for mapping..".
Do you guys have some ideas what else i could try?
Vehaboman said:
Ok.I tried every USB port and Odin stops always at "Get PIT for mapping..".
Do you guys have some ideas what else i could try?
Click to expand...
Click to collapse
Have you made sure that KIES is not running sth. in the background?
I suggest uninstalling KIES (including all drivers), reboot, reinstall drivers from here, reboot and then try again running ODIN as administrator.
Hawaiihemd said:
Have you made sure that KIES is not running sth. in the background?
I suggest uninstalling KIES (including all drivers), reboot, reinstall drivers from here, reboot and then try again running ODIN as administrator.
Click to expand...
Click to collapse
Did as you suggested but still stuck at Get PIT for mapping :crying:
Do i have to use another Firmware with the PIT file?
Currently i'm using the 4.3 DBT Firmware.DO i have to download an older one?
Btw thank you so much for helping me Hawaiihemd^^
Vehaboman said:
Did as you suggested but still stuck at Get PIT for mapping :crying:
Do i have to use another Firmware with the PIT file?
Currently i'm using the 4.3 DBT Firmware.DO i have to download an older one?
Btw thank you so much for helping me Hawaiihemd^^
Click to expand...
Click to collapse
You're welcome.
AFAIK should work with every firmware for the specific device. Would you please add another post with a screenshot of your odin settings and the odin log as text? I just want to check something for confirmation. But I don't want to keep your hopes up... I think your S3 is dead.
Hawaiihemd said:
You're welcome.
AFAIK should work with every firmware for the specific device. Would you please add another post with a screenshot of your odin settings and the odin log as text? I just want to check something for confirmation. But I don't want to keep your hopes up... I think your S3 is dead.
Click to expand...
Click to collapse
Alright hopefully this will be displayed^^
and here is the text log:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGNG3_I9300DBTGNG2_I9300XXUGNA8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
Vehaboman said:
Alright hopefully this will be displayed^^
and here is the text log:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGNG3_I9300DBTGNG2_I9300XXUGNA8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
Click to expand...
Click to collapse
First of all thanks for posting this. I'm sorry to say but my knowledge about this stuff has come to an end.
As I said before, I do not know how ODIN works behind the scenes. It just seemed logical to ME(!), that if nothing could be written to the NAND it should crash at "setting the pit file" instead of "getting pit for mapping". Maybe right, maybe wrong, no idea. I haven't seen an ODIN documentation as of yet but someone out there has to know what it does exactly... the programmer at least.
So, sorry mate, I have nothing more contructive to contribute. I hope someone can point to a documentation of some sort or can provide any more insight in any other way.
Hawaiihemd said:
First of all thanks for posting this. I'm sorry to say but my knowledge about this stuff has come to an end.
As I said before, I do not know how ODIN works behind the scenes. It just seemed logical to ME(!), that if nothing could be written to the NAND it should crash at "setting the pit file" instead of "getting pit for mapping". Maybe right, maybe wrong, no idea. I haven't seen an ODIN documentation as of yet but someone out there has to know what it does exactly... the programmer at least.
So, sorry mate, I have nothing more contructive to contribute. I hope someone can point to a documentation of some sort or can provide any more insight in any other way.
Click to expand...
Click to collapse
I gotta thank you for sticking here and trying to help me Thanks again for your time and effort
Hi all,
I need help to fix the S3 that i have here, model GT-I9300, I don't know what happened but I cant boot the phone it is stuck at Galaxy S3 screen, I can enter in recovery and Download mode but I am not being able to flash anything using Odin and KIES also does not work, what I have tried:
Flash stock room using Odin;
Flash TWRP Using Odin;
Update firmware using KIES, I do put the model and serial number but the KIES give a message that is not possible to start the process;
Odin fails in anything that I tried to flash:
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1101)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
If I enter in the recovery mode i saw a lot of red messages saying that is not possible to mount E: bla bla.
Any help Is appreciated.
Looks like a SDS
MGSGS said:
Looks like a SDS
Click to expand...
Click to collapse
I googled for it and seems that there is no fix for it... so, good bye
Tried different USB cables and ports?
audit13 said:
Tried different USB cables and ports?
Click to expand...
Click to collapse
Yes, also different computers, I think that it is a sds
Confirmed the model # in download mode? Using the latest stock ROM from sammobile.com?
audit13 said:
Confirmed the model # in download mode? Using the latest stock ROM from sammobile.com?
Click to expand...
Click to collapse
Yes, also tried to flash twrp, stock recovery, everything fails....