In mode download
PRODUCT NAME :
CUSTOM BYNARY DOWNLOAD: NO
CURRENT BINARYñ Samsung Official
SYSTEM STATUS: CUSTOM
Help.
If you can get into download, try flashing a stock ROM
Sent from my GT-I9300 using Tapatalk 4
When do I get this message "There is not pit partition"
elmazter said:
When do I get this message "There is not pit partition"
Click to expand...
Click to collapse
You might need to send it in for service then. Sounds like SDS if I'm not mistakened or at least something to do with the memory
Sent from my Nexus 7 using Tapatalk 4
when I want to do the installation by odin I get this message
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9300_REV00_user_low_ship.tar.md5 is valid.
<OSM> CODE_I9300XXDLJ4_368423_REV00_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9300XXDLID_REV00_user_low_ship.tar.md5 is valid.
<OSM> CSC_BTU_I9300OXADLJ4_368423_MULTI_user_low_ship.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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Wrong forum .
You now require a service centre
What jje said.
Sent from my SGH-I747 using xda app-developers app
Classical SDS (dead eMMC). Take it to a service center. ("Custom" should not be an issue - it's a symptom of the failed eMMC.)
Sent from my GT-I9305 using xda app-developers app
got SGS3 LTE Shv-e210s in same Situation, no hope
any idea ?
umar_fiaz said:
got SGS3 LTE Shv-e210s in same Situation, no hope
any idea ?
Click to expand...
Click to collapse
SDS is a complete eMMC failure nothing you can do there. Only an official service center can help you by replacing your phone's motherboard.
Related
I have one Galalxy s3 I9300 no working I try software on odine but flashing fail see this log
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I9300XXELLA_I9300OXAELLA_742798_REV00_user_low_ship.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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
make sure things like usb debugging are on in the dev options.
aboody712 said:
I have one Galalxy s3 I9300 no working I try software on odine but flashing fail see this log
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I9300XXELLA_I9300OXAELLA_742798_REV00_user_low_ship.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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Q1. Why are you re-partioning your device?
Q2. If you are re-partitioning then are you using the 3 file method with mx.pit?
Q3. Have you tried different USB ports, cables, restarting your PC etc.?
I triad 3 flies with pit file same problem
zoot1 said:
Q1. Why are you re-partioning your device?
Q2. If you are re-partitioning then are you using the 3 file method with mx.pit?
Q3. Have you tried different USB ports, cables, restarting your PC etc.?
Click to expand...
Click to collapse
I triad 3 flies with pit file same problem
I second trying different USB ports. XXELLA took about 15 attempts before it passed for me
Sent from my GT-I9300 using xda app-developers app
Your phone is bricked. Most likely by the same thing which is causing the Sudden Death where it can't even reach Download mode. Take it to a Samsung Service centre to be repaired, and remember you've never heard of rooting, flashing, download mode, custom roms. You only know about XDA because a Google Search lead you to pages and pages of broken phones.
yess...your phone is bricked..same like mine last month..I sent to samsung centre..they change motherboard...
My phone appears to have stopped working. I have a custom ROM and it gets stuck on the boot screen (Samsung Logo)
I can get the phone into Download mode how ever when I run the PDA I recieve the following
<ID:0/006> 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/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>
<ID:0/006> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1).
Does anyone know what I can do to fix this?
Soft brick. Easy to fix browse the forum for tutorial if you cant find, pm me.
Sent from my GT-I9300 using xda premium
You have certainely check the case "Re-partition" in ODIN when you have try to flash the device. If the case "PIT" was empty, it only deletes the PIT file and you get soft-bricked.
To recover your phone, you must provide to your phone the PIT file (partition information file). You can easily find it on XDA:
Can you enter recovery mode?
Sent from my GT-I9300 using xda app-developers app
Hi Guys
First time writing here,hope to finde a soluttion.
I bought a Galaxy Note 2 Verizon(sch i605),since I was not using it in Verizon I was not able to send SMS and a pop up appears all the time,telling me that the SIM is not Verizon etc
To fix those things I rooted it and installed JEDI X ROM.Everything seems fine.
I saw that the version of rom says T Mobile when Jedi X was Installed
So i thought If I will install T mobile stock ROM,In my verizon,sms and everything will work fine and I will not have anymore a rooted phone.
I used ODIN to put the file,everything seems fine,but now it has stuck in a boot loop
When I turn it on it says samsung and get restarted,all the time just restart
I can not go to recovery ,but I can get to download mode
I have tryed everything I could for 9 hours,but nothing
I sent it to a Local Service repair and they said they have Tried J TAG and no results at all
So i wana ask,What can I do?
Thank you so much in advance
fredi0014 said:
Hi Guys
First time writing here,hope to finde a soluttion.
I bought a Galaxy Note 2 Verizon(sch i605),since I was not using it in Verizon I was not able to send SMS and a pop up appears all the time,telling me that the SIM is not Verizon etc
To fix those things I rooted it and installed JEDI X ROM.Everything seems fine.
I saw that the version of rom says T Mobile when Jedi X was Installed
So i thought If I will install T mobile stock ROM,In my verizon,sms and everything will work fine and I will not have anymore a rooted phone.
I used ODIN to put the file,everything seems fine,but now it has stuck in a boot loop
When I turn it on it says samsung and get restarted,all the time just restart
I can not go to recovery ,but I can get to download mode
I have tryed everything I could for 9 hours,but nothing
I sent it to a Local Service repair and they said they have Tried J TAG and no results at all
So i wana ask,What can I do?
Thank you so much in advance
Click to expand...
Click to collapse
Have you tried flashing the alternate restore and the PIT together in ODIN, while in DL mode, from droidstyles post? What about root66 along with the PIT? What about those 2 alone?
Your mistake was flashing Jedi in ODIN when it is supposed to be flashed in the custom recovery.
Sent from my SCH-I605 using XDA Premium HD app
fredi0014 said:
Hi Guys
First time writing here,hope to finde a soluttion.
I bought a Galaxy Note 2 Verizon(sch i605),since I was not using it in Verizon I was not able to send SMS and a pop up appears all the time,telling me that the SIM is not Verizon etc
To fix those things I rooted it and installed JEDI X ROM.Everything seems fine.
I saw that the version of rom says T Mobile when Jedi X was Installed
So i thought If I will install T mobile stock ROM,In my verizon,sms and everything will work fine and I will not have anymore a rooted phone.
I used ODIN to put the file,everything seems fine,but now it has stuck in a boot loop
When I turn it on it says samsung and get restarted,all the time just restart
I can not go to recovery ,but I can get to download mode
I have tryed everything I could for 9 hours,but nothing
I sent it to a Local Service repair and they said they have Tried J TAG and no results at all
So i wana ask,What can I do?
Thank you so much in advance
Click to expand...
Click to collapse
you could also try using a jig, but since it goes into download mode just flash the alt odin package.
shangrila500 said:
Have you tried flashing the alternate restore and the PIT together in ODIN, while in DL mode, from droidstyles post? What about root66 along with the PIT? What about those 2 alone?
Your mistake was flashing Jedi in ODIN when it is supposed to be flashed in the custom recovery.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
ALTERNATE RESTORE WITHOUT PITE FILE
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I605_VRALJB_Restore.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
ALTERNATE RESTORE WITH PITE FILE
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I605_VRALJB_Restore.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..
GETS STUCK HERE FOR 20 MIN AND MORE
The same with Root66
fredi0014 said:
ALTERNATE RESTORE WITHOUT PITE FILE
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I605_VRALJB_Restore.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
ALTERNATE RESTORE WITH PITE FILE
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I605_VRALJB_Restore.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..
GETS STUCK HERE FOR 20 MIN AND MORE
The same with Root66
Click to expand...
Click to collapse
Have you tried different cords?
Sent from my SCH-I605 using XDA Premium HD app
shangrila500 said:
Have you tried different cords?
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
Yes different cord,pc and operating systems
Hi guys!
My i9300 does not boot and instead keeps displaying the samsung logo. It doesn't enter the recovery mode either, but does enter the download mode. So I tried flashing 2 different official ROMs but I'm getting the error:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> CODE_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> CSC_I9300OXEEMH1_SER_FACTORY_user_low_ship.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> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
I downloaded the ROM here:
<tried posting a link but was not allowed>
Could you please help me with this problem?
Thanks in advance!
Try another version of odin, different lead, port or pc. Ensure kies is not running. Follow the guide on flashing to the letter.
Download the rom from sammobile and check the md5.
Sent from my GT-I9300 using Tapatalk
wicccked said:
Hi guys!
My i9300 does not boot and instead keeps displaying the samsung logo. It doesn't enter the recovery mode either, but does enter the download mode. So I tried flashing 2 different official ROMs but I'm getting the error:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> CODE_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> CSC_I9300OXEEMH1_SER_FACTORY_user_low_ship.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> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
I downloaded the ROM here:
<tried posting a link but was not allowed>
Could you please help me with this problem?
Thanks in advance!
Click to expand...
Click to collapse
I had a similar issue a while ago but it turned out to be an issue with the Kernel not being compatable with the Rom I flashed. I thought I had bricked it, until I flashed a stock kernal first then the stock ROM and it fixed it for me and it really does sound like you have the same issue, As for the rom not flashing its most likely a bad download try sammobile! let me know if it was the kernal!
jaggythistle said:
I had a similar issue a while ago but it turned out to be an issue with the Kernel not being compatable with the Rom I flashed. I thought I had bricked it, until I flashed a stock kernal first then the stock ROM and it fixed it for me and it really does sound like you have the same issue, As for the rom not flashing its most likely a bad download try sammobile! let me know if it was the kernal!
Click to expand...
Click to collapse
jaggythistle, thank you for the answer.
I downloaded the stock kernel, successfully flashed it, downloaded the matching ROM (1-file this time), but now when trying to flash I'm getting the following error:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300UBEMH3_I9300UBEMH1_I9300ECOEMH1_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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
What can I do?
boomboomer, Thanks for the reply. I have checked it all, now I'm getting the above error.
If you've tried all the connection issues then it appears your recovery positron is corrupt and can't be written. A rescue firmware, including pit might help but otherwise you'll need a new motherboard.
Search in general forum for the rescue firmware thread, follow the instructions.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
If you've tried all the connection issues then it appears your recovery positron is corrupt and can't be written. A rescue firmware, including pit might help but otherwise you'll need a new motherboard.
Search in general forum for the rescue firmware thread, follow the instructions.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
I have tried the rescue firmware and got the following error:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> CODE_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> CSC_I9300OXEEMH1_SER_FACTORY_user_low_ship.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> Get PIT for mapping..
<ID:0/005>
<ID:0/005> There is no PIT partition.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
PIT damaged new motherboard .
You can search for this thread where a claim was made to fix pit .
(SOLVED) PIT/Bricked/Dead problem on GT-I9300 international
Worth trying before buying a new motherboard as you have no warranty .
JJEgan said:
PIT damaged new motherboard .
You can search for this thread where a claim was made to fix pit .
(SOLVED) PIT/Bricked/Dead problem on GT-I9300 international
Worth trying before buying a new motherboard as you have no warranty .
Click to expand...
Click to collapse
Tried it, Odin was hanging at the "Erase..." step for ~5-10 mins, then I got the error:
Code:
<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> Erase...
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
white screen cant use odin its fail only can load download mode GT-I9300
odin 3.07
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGMK7_I9300OJKGNB1_I9300JKUGNB2_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>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
odin 1.85
STUCK AT
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGMK7_I9300OJKGNB1_I9300JKUGNB2_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..
OR
odin 1.85
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGMK7_I9300OJKGNB1_I9300JKUGNB2_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>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Untick repartition, tick "one package". If you already did that you may need to elaborate a little on what you've done to it.
Sent from my HTC One M9 using Tapatalk
shivadow said:
Untick repartition, tick "one package". If you already did that you may need to elaborate a little on what you've done to it.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
i got the phone from friend i dont sure if he checked re pratition or not I didn't
In that case i can tell you that the nand is dead. You can try flashing a .pit file via odin but i doubt it will do anything except fail to flash.
Sent from my HTC One M9 using Tapatalk
shivadow said:
In that case i can tell you that the nand is dead. You can try flashing a .pit file via odin but i doubt it will do anything except fail to flash.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
It's failing to flash even the pit is there anything I can do? A
Yes plenty to do. It depends on how creative you are.. I'd find some way to detonate it but throwing it in the bin is advised. It's broken beyond repair.
Sent from my HTC One M9 using Tapatalk