Odin stuck in Get PIT for mapping (Galaxy S3 GT-i9300) - Galaxy S III Q&A, Help & Troubleshooting

I'm trying to install Philz Touch or TWRP on my Galaxy S3(GT-i9300) using Odin(I have tried using Odin 1.85, 3.09, 3.10.7, and 1.3)
I'am using the motherboard's USB ports.
But everytime it stops at the "Get PIT for mapping.." step...
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.48.4-i9300.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..
Click to expand...
Click to collapse
(That log above is from Odin 1.85)
Can anyone help me? I'm trying to do this for weeks...
Thanks in advance.

Related

[Q] Rooting"stuck at boot.img

This is my first time rooting any android device.
I have done the following already
1. Installed Drivers with Kies
2. Installed Odin3
3. Downloaded the .md5.tar pre-rooted file 1.1 gb
4. Went into Odin, And selected PDA and choose the .tar file
5. Unchecked the Re-Partion
But! for some reason, it will stop at boot.img
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> prerooted.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> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> boot.img
And it will stop. Im using the Samsung USB, and ive changed ports. Nothing seems to work! Help! D:
xxtoxicriotxx said:
This is my first time rooting any android device.
I have done the following already
1. Installed Drivers with Kies
2. Installed Odin3
3. Downloaded the .md5.tar pre-rooted file 1.1 gb
4. Went into Odin, And selected PDA and choose the .tar file
5. Unchecked the Re-Partion
But! for some reason, it will stop at boot.img
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> prerooted.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> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> boot.img
And it will stop. Im using the Samsung USB, and ive changed ports. Nothing seems to work! Help! D:
Click to expand...
Click to collapse
would be best if you download stock firmware from sammobile for your sgs3 and flash it again and than download cf auto root for rooting sgs3. u should read guides properly on how to root sgs3 here at xda. i ts available in general sgs3 forum.. if any problem presist or if u need help u can pm me..
Odin won't work with kies installed, you only needed the drivers which come separately.
xxtoxicriotxx said:
This is my first time rooting any android device.
Nothing seems to work! Help! D:
Click to expand...
Click to collapse
Make sure Kies is not running at the same time as Odin and use CF auto root as suggested by suyash1629 the link is in my signature

Need Help Bricked GT-I9300

hi guys. my i9300 is bricked. I tried to flash roms with odin.
it stucked at samsung gt-i9300 galaxy s3 text. no samsung logo.
Also I can't get in to recovery mode.
When i try to flash any rom (included stock rom) i get this error
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CheckROM_V4_LG8.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>
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
I tried many of PIT files. Still the same error.
Sorry for my english
This belongs in q/a
Sent from my GT-I9300 using Tapatalk

[Q] Galaxy Tab 10.1 Stuck in odin3 boot.img

Hello,
After trying unsuccessfully to update my tab from 3.2 to 4.0 I get stuck with well know message "firmware upgrade encountered an issue". Well, after trying a couple of tutorials (all of them using odin) I always hit the same problem :
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P7500XXLQ8_P7500OXALQ8_P7500XXLQ8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> SingleDownload.
<ID:0/015> boot.img
I can`t get passed throw the boot.img step. Anyone had a similar issue with that and may share some ideas with me ? Thanks
Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Stand by
Good luck
hsr38 said:
Hello,
After trying unsuccessfully to update my tab from 3.2 to 4.0 I get stuck with well know message "firmware upgrade encountered an issue". Well, after trying a couple of tutorials (all of them using odin) I always hit the same problem :
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P7500XXLQ8_P7500OXALQ8_P7500XXLQ8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> SingleDownload.
<ID:0/015> boot.img
I can`t get passed throw the boot.img step. Anyone had a similar issue with that and may share some ideas with me ? Thanks
Click to expand...
Click to collapse
Try using Odin 1.87 and/or make sure Odin runs as administrator.
If that fails then it could be a corrupt download so try downloading again.
Sent from my Nexus 7 using XDA Free mobile app

how to enable usb debugging mode

hi guys,
my phone is soft-bricked and it freezes samsung logo screen on the startup.
How can I enable usb debugging mode on this situation ? Do you have any solution ??
My phone is: Samsung Galaxy S3 GT-I9300 International..
husamba said:
hi guys,
my phone is soft-bricked and it freezes samsung logo screen on the startup.
How can I enable usb debugging mode on this situation ? Do you have any solution ??
My phone is: Samsung Galaxy S3 GT-I9300 International..
Click to expand...
Click to collapse
There is no way how to enable USB debugging mode if is device soft bricked.. Download official FW ,then go to download/bootloader mode and flash it via Odin.
DejVidKo said:
There is no way how to enable USB debugging mode if is device soft bricked.. Download official FW ,then go to download/bootloader mode and flash it via Odin.
Click to expand...
Click to collapse
Hi DejVidKo,
I just get official FW from sammobile, I went to download mode and I am getting an error like below on ODIN. Do you have any guess about what I am doing wrong.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGNB6_I9300OJVGNB3_I9300XXUGNA8_HOME.tar.md 5 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> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
husamba said:
Hi DejVidKo,
I just get official FW from sammobile, I went to download mode and I am getting an error like below on ODIN. Do you have any guess about what I am doing wrong.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGNB6_I9300OJVGNB3_I9300XXUGNA8_HOME.tar.md 5 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> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
If you have another version of Odin,try Odin v3.04
DejVidKo said:
If you have another version of Odin,try Odin v3.04
Click to expand...
Click to collapse
No wayyy. I tried it too. And I am getting same error. There are more than one rom in sammobile. May I download the wrong rom from sammobile.. :S
<ID:0/006> Added!!
<ID:0/006> Removed!!
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGNB6_I9300OJVGNB3_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> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<ID:0/006> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)

Need Help, not able to re flash same firmware

Hi
i updated my S III with stock firmware with 4.3 (I9300XXUGNB6_I9300OJVGNB3_I9300XXUGNA8_HOME.tar.md5) via Odin. It was successful and worked fine for a few days, but after 3 or 4 days my phone get stucked on Samsung logo screen, i tried wiping data and cache from recovery, but problem is same. So i am trying to re flash my phone with same stock rom. But i am not able to do it.
I am using Odin 3.07,
Here is the Log:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGNB6_I9300OJVGNB3_I9300XXUGNA8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
I also used to Root it with cf auto root,
Here is the Log:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-m0-m0xx-gti9300.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Tried using different USB ports and USB cables?
audit13 said:
Tried using different USB ports and USB cables?
Click to expand...
Click to collapse
Yes Tried, Recently my S III was updated via same port and USB Cable,
Have you tried flashing the stock ROM with a pit file?
It's also possible that the internal memory chip is damaged.
audit13 said:
Have you tried flashing the stock ROM with a pit file?
It's also possible that the internal memory chip is damaged.
Click to expand...
Click to collapse
Yes I tried, Here is result:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGNB6_I9300OJVGNB3_I9300XXUGNA8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
Stuck on Get PIT for mapping,
Since it is stuck on the pit file, this leads me to believe that the cable is not compatible or the internal memory is damaged.
I have flashed many different Samsung phones over several years and I find that USB cables can cause the flash to fail when Odin is trying to read the partition information (PIT), flash a bootloader, or flash the system image.

Categories

Resources