My tablet do a boot loop so i wanted to put back the stock rom. When i start whit pit file and pda it stop at boot.img 5 minute and after tell me that hit failed. Do you know what i can do??
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P7500RUXLH2_P7500RRWCLH2_P7500RUXLH2_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> 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> boot.img
<ID:0/003> __Xmit Write fail
<ID:0/003> XmitData Fail..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Try the latest version of Odin, if you don't already have it:
http://forum.xda-developers.com/showthread.php?t=1738841
If that still doesn't work, try heimdall instead:
http://forum.xda-developers.com/showthread.php?t=755265
It's telling me "firmare.xlm is missing from package" after uncompressing it in Heimdall.
I'm using a rom i dowloaded on sammobile ans redownloaded it to be sure it was ok.
Took an old version of odin and it worked. Flash and reset data and it boot like a new one!
Gadgervais said:
Took an old version of odin and it worked. Flash and reset data and it boot like a new one!
Click to expand...
Click to collapse
Be VERY CAREFUL if you flash stock firmware and do a factory reset from stock android recovery. You could very easily hard brick your tablet due to the emmc brick bug that many of our tablets are at risk for.
In the future I would recommend wiping this way:
1) reboot to your custom recovery, or flash one with odin if you need to
2) make sure your stuff is backed up on a computer or dropbox etc., then do a full wipe of everything including a format /sdcard if you want to truly start over
3) reboot to download mode and THEN flash stock firmware.
SQUEAKY clean and you can avoid needing to factory reset from stock recovery. I did that about two weeks ago and its like the tablet is brand new again.
Sent from my Infamous Tab.
I hope you have solved this case
Related
Hello, I'd be grateful for some assistance. This morning my s3 was in my pocket and felt really warm. I pulled it out and it was stuck on the boot logo. I'm assuming it had been on that for a while which is why it heated up.
Now, the phone doesn't boot up. I can get into download mode but not recovery.
I did have the Siyah Kernel installed as well as a JB rom.
I have downloaded the latest firmware image for my region UK - (I9300XXEMB5_I9300OXAEMB5_BTU) and tried installing but have had no luck. Below is the message I get. Please help.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I9300XXEMB5_I9300OXAEMB5_996085_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> Get PIT for mapping..
<ID:0/003>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
miahmad said:
Hello, I'd be grateful for some assistance. This morning my s3 was in my pocket and felt really warm. I pulled it out and it was stuck on the boot logo. I'm assuming it had been on that for a while which is why it heated up.
Now, the phone doesn't boot up. I can get into download mode but not recovery.
I did have the Siyah Kernel installed as well as a JB rom.
I have downloaded the latest firmware image for my region UK - (I9300XXEMB5_I9300OXAEMB5_BTU) and tried installing but have had no luck. Below is the message I get. Please help.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I9300XXEMB5_I9300OXAEMB5_996085_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> Get PIT for mapping..
<ID:0/003>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Have you tried with another usb port and are you using stock samsung usb cable?
Your partition structure of the internal storage card is corrupt, the phone is soft bricked. You can usually format and recover if you have backups, particularly of the efs folder.
If you don't then there are a few solutions here on the forum you can try, otherwise it's a Samsung repair.
boomboomer said:
Your partition structure of the internal storage card is corrupt, the phone is soft bricked. You can usually format and recover if you have backups, particularly of the efs folder.
If you don't then there are a few solutions here on the forum you can try, otherwise it's a Samsung repair.
Click to expand...
Click to collapse
Hello, thanks for your reply. I don't have a backup. Would you please point me in the right direction? I'm not sure what I need to do?? where would I get the recovery??(Is that the bootloader?Kernel?Rom?)
Search and read here in Q&A, without a backup of your efs it is less likely to succeed. Otherwise return to Samsung for repair.
boomboomer said:
Search and read here in Q&A, without a backup of your efs it is less likely to succeed. Otherwise return to Samsung for repair.
Click to expand...
Click to collapse
From what I can make out I need to reformat the internal storage. To do this I need the correct pit file. I can't find it on samfirmware.com.
miahmad said:
From what I can make out I need to reformat the internal storage. To do this I need the correct pit file. I can't find it on samfirmware.com.
Click to expand...
Click to collapse
i dont know if this will work ... but try the resurrection rom!
I can't bet into recovery.installing from Odin also gives error.
flash the correct pit file, use search, it's been posted
Glebun said:
flash the correct pit file, use search, it's been posted
Click to expand...
Click to collapse
I have attached the Pit file I have used. No luck. It does nothing, I have left it for ages.
<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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
Service centre then but their is a big queue judged by todays bricked phone posts .
jje
I am from India, and I was using the Galaxy s2 with Jelly Bean 4.1.2(installed from KIES). The phone suddenly crashed and only download mode is accessible. I downloaded the stock firmware from sammobile and tried odin3 v3.07, but it isnt working and the 0:[com3] background is blue.
The firmware i tried booting it with is I9100XWLST_I9100ODDLSE_I9100DDLS9_HOME.tar.md5
i uploaded this by clicking on the PDA button and this how far it got to:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLSK_I9100ODDLSA_I9100DDLS9_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.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> factoryfs.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've run out of ideas and forums that I've gone through ! Some one please help!
Look for @Hopper8 thread. Great thread lots of info on Odin problems
No Luck!
andrewwright said:
Look for @Hopper8 thread. Great thread lots of info on Odin problems
Click to expand...
Click to collapse
Hi,
I read through and tried flashing with siyah v6 but even that failed.
Not really sure what the issue is!
mosesadarsh said:
I am from India, and I was using the Galaxy s2 with Jelly Bean 4.1.2(installed from KIES). The phone suddenly crashed and only download mode is accessible. I downloaded the stock firmware from sammobile and tried odin3 v3.07, but it isnt working and the 0:[com3] background is blue.
The firmware i tried booting it with is I9100XWLST_I9100ODDLSE_I9100DDLS9_HOME.tar.md5
i uploaded this by clicking on the PDA button and this how far it got to:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLSK_I9100ODDLSA_I9100DDLS9_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.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> factoryfs.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've run out of ideas and forums that I've gone through ! Some one please help!
Click to expand...
Click to collapse
Doesnt seem like the phone is charging either!!
Flash philz kernel and then you should be able to get to recovery then flash a custom Rom
Read this bro
http://forum.xda-developers.com/showthread.php?t=2101610&page=2
Hope it helps !!
I tried everything possible but nothing worked. . I got stuck at factoryffs every time then hit xmit data failure. . M sure I hard bricked it now! ! Must be the motherboard. .
can someone please post links to the philz kernel and a stable india version JB firmware !! Please please ... im desperate!!
Search!! Dont be lazy its not hidden or hard to find.
seriously bro?? I found the thread to that kernel but that list is never ending.. God knows which kernel is for my phone!!
Only comment if you have answers please !!!!
All the videos that i watched online show how to install philz kernel on a working phone.
My phone is kinda dead... so what needs to be done after flashing philz kernel? Tell me the next steps please..
Does it still go to download mode? Does odin still see it?
I tried flashing my phone with philz kernel but even that failed...
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PhilZ-cwm6-XWLSK-ODD-4.92.8.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!!
<OSM> All threads completed. (succeed 0 / failed 1)
Make is easy on your self and flash lss firmwear and flash lss kernel "near the top of download list" chances are you dont have an os now odin has failed to flash. Hooper8 thread has good info on flashing problems! Read that before you try.
Pics clicked a minute back... does this help...
Pls read hooper8 thrsad
Any joy now op?
Nope.. No luck... nothing goes beyond the nand write start! message.. Im done trying stock rom from sammobile, siyah v6, philz kernel.. nothing succeeded
mosesadarsh said:
Nope.. No luck... nothing goes beyond the nand write start! message.. Im done trying stock rom from sammobile, siyah v6, philz kernel.. nothing succeeded
Click to expand...
Click to collapse
Same problem here, my phone was working fine then all of a sudden i noticed it was dead, tried rebooting it, nothing happened, boot loop, tried to access CWM, i got the lower section menu of CWM but nothing else, a black screen with the buttons.
So next i said, let me use odin to flash a new kernel. That failed and ever since that failed, i cannot do anything except enter download mode. If i power the phone on, i get a [phone-problem-computer] image in yellow with text that says somehting like problem loading software, please conntect to kies recovery mode. of course that never works.
And everytime i try to flash absolutely anything on this device, Odin DOES see the device, and the second i press flash/start, when it reacher nand write start, it hangs there, stuck doing nothing.
I took the phone to a friend who has an Riff jtag box, he soldered his jtag to the phone and said the memory chip is not dead, i can read its capacity normally. But when he tried to write to it, it did not work, kept giving him errors, he said he has never encountered such a behavior before. And then i had to leave.
Up to now, my phone is still dead and i have no idea what to do. It only enters download mode, but at the same time, this is useless since flashing anything simply does not work. Anyone knows what the reason could be?
FYI, i was on NeatROM 5.5, which comes with Philz Kernel.
NAND is stuffed/corrupted. How/why - who knows ? Motherboard replacement if you've already tried JTAG. Could be something hardware going on that caused the chip to become 'damaged'.
Hi all,
I have a Samsung galaxy S3 GT-I9300. 2 days ago it crashed and won't boot anymore. The reason was can't mount /cache, can't mount system ... on recovery mode. I tried only the wipe cache option and it did nothing.
I started looking at the forum to understand how to fix it. I deciced first to make a backup of my data if possible so I downloaded Odin v3.07 and philz_touch_6.07.9-i9300.tar.md5. I read in another thread that we can manage to copy data from the phone using philz tools.
The problem here is that flashing philz tools with Odin fails all the time. Now I can only access the download mode. At boot, I have a "Firmware upgrade encountered an Issue..." I tried with Kies recovery but it failed too.
In my sdcard, I have no folder clockwordmode ! In download mode
PRODUCT NAME : GT-I9300
CUSTOM BINARY DOWNLOAD : Yes (3)
CURRENT BINARY : Custom
SYSTEM STATUS : Ofiicial
I am bit lost as there seem to be a lot of options in other threads. I don'y know where to start or what to do ? is it the PIT files to restore ? the firmware, the kernel ? the whole OS ?
Many thanks
Don't use pit file. pit is Last resort!!!! Get stock firmware from sammobile.com and flash it through Odin. Forget kies. Read about Odin before flashing.
You'll need to flash with a *.pit file, and the ROM downloaded from sammobile in order to restore your device. Use the *.pit file as the absolute last option to restore your phone. It will repartition your phone, and any power loss of either the machine you are flashing from, or your phone will render it a permanent brick.
Thank you
I am downloading the latest firmware from sammobile (1.1 GB) and Odin 3.09. There are specific instructions for Odin on sammobile website so I don't think i'm goint to mess it up. I will let you know if it did work for me.
I tried to flash the image from sammobile but it failed. There is no log I can read to understand why
Here is the name of image I downloaded I9300XXUGML2_I9300FTMGML2_I9300BVUGML1_HOME.tar
Concerning Odin, its the 3.09 GS3 by l0gan
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGML2_I9300FTMGML2_I9300BVUGML1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> SingleDownload.
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Shall I try with an older image (this one is the latest) ? or retry by messing the PIT ?
Nand write fail = motherboard replacement.
Keep trying to flash and don't give up but please leave pit till the end. Yes try three part recovery firmware and older firmware "not ics" SDS on ics firmware and you don't want that. But at the end of the day nand write fail means hardware failure.
Hi again,
I succeeded to flash one image from 2013. Odin says PASS!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXELL1_I9300FTMELL1_I9300BVELK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Added!!
<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> SingleDownload.
<ID:0/006> system.img
<ID:0/006> NAND Write Start!!
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> cache.img
<ID:0/006> hidden.img
<ID:0/006> modem.bin
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Removed!!
<ID:0/006> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
However, I still have the "Firmware upgrade encountered an issue" at boot I removed the phone when I saw the message Removed in Odin. I am not sure whether it didn't let the process finish well or I did right. Any ideas or suggestions ?
I succeeded to reinstall the latest firmware and I got back the samsung logo at boot. However It still doesn't go any further and no recovery mode ... Is there a way to check the status of the system ?
Omg its alive!! Odin said pass! Just keep flashing that firmware till you get recovery and then factory reset.
Try the rescue firmware in general thread, follow the instructions exactly.
Sent from my GT-I9300 using Tapatalk
Hello
An update of my case. After struggling 2 days with NAND write fail and trying lots of firmwares... I succeeded to install CMW recovery tool. From that, I installed Cyanogenmod 10.0.2. I struggled to make it boot too as it looped on cyanogen logo many times.
Now I must confess that I am afraid of rebooting the phone as I thought it was dead :angel:
Hope it helps someone else :highfive:
Great feed back for others. and go's to show never give up flashing with Odin. Odin is a pain in the ....
Congrats :thumbup:
I made the mistake of trading phones with a guy whose GS4 was rooted with SS recovery and there were no MSD in it when we traded. I brought it home, restarted it. And it began to get stuck on the "FIRMWARE UPGRADE ENCOUNTERED AN ISSUE. PLEASE SELECT RECOVERY MODE IN KIES & TRY AGAIN." which I know to not use Kies as it was useless to me when I had my first GS4 at time of launch. I am fairly new at this with a gs4. I have tried and tried with ODIN v3.07. I have been on here and looking through forums and I went to other forums besides xda with countless different trials. NONE have been even the slightest bit helpful...
I was wondering since it was stuck on the devilish yellow triangle screen. I can not even get past this to get the launcher... could ADB be the problem since I can't get it to even boot up to enable it?
before anyone asks, to which will waste both our time....
yes, i have used the stock vz firmware and placed it in the PDA section in ODIN
THIS IS WHAT I GET EVERY TIME.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUAME7_I545VZWAME7_I545VRUAME7_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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
ALL HELP IS MUCH APPRECIATED!!:good:
Are you sure you were on ME7? You might need to flash a newer firmware.
Sent from my NCC-1701 using Tapatalk.
Definitely need to flash newer firmware
degradedtree69 said:
I made the mistake of trading phones with a guy whose GS4 was rooted with SS recovery and there were no MSD in it when we traded. I brought it home, restarted it. And it began to get stuck on the "FIRMWARE UPGRADE ENCOUNTERED AN ISSUE. PLEASE SELECT RECOVERY MODE IN KIES & TRY AGAIN." which I know to not use Kies as it was useless to me when I had my first GS4 at time of launch. I am fairly new at this with a gs4. I have tried and tried with ODIN v3.07. I have been on here and looking through forums and I went to other forums besides xda with countless different trials. NONE have been even the slightest bit helpful...
I was wondering since it was stuck on the devilish yellow triangle screen. I can not even get past this to get the launcher... could ADB be the problem since I can't get it to even boot up to enable it?
before anyone asks, to which will waste both our time....
yes, i have used the stock vz firmware and placed it in the PDA section in ODIN
THIS IS WHAT I GET EVERY TIME.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUAME7_I545VZWAME7_I545VRUAME7_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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
ALL HELP IS MUCH APPRECIATED!!:good:
Click to expand...
Click to collapse
This has happened to me about four times with my phone. I was able to fix through a process of Kies and Odin. It seems that if you do all that you can in Kies, as far as attempting to re-install the stock firmware. Kies has the drivers you need in order for Odin to work. You will need to run through the Kies process (it will fail), but you will get the drivers you need. You will then need to boot into download mode and do the Odin flash process. This is all assuming you have the correct files for Odin. You will need to flash the stock build afterwards unless you have a backup and are able to access safestrap which i doubt you will have.
Hi,
A few days ago, my device spontaneously soft-bricked itself (haven't installed any mods or stuff), and after a quick regression, it is now only able to boot into download mode (recovery mode sends it to a screen with white horizontal and diagonal lines..)
In download mode, it reads:
ODIN MODE:
product name: GT-I9300
Custom binary download: NO
Current Binary: samsung official
System status: custom
I have tried setting up cyanogenmod but haven't been able to flash their provided custom recovery, due to my computer being unable to download the PIT from the device.
I also tried using the master version of heimdall to do that, with no success.
I also tried recovering my device with KIES, but after downloading the firmware update to my computer, it gets into a load where it would be uploading said update into my device, but just hangs at 0%
I tried uploading a stock firmware using odin 3.07, and I recieved some error regarding my PIT file.
Finally I tried repartitioning with a downloaded PIT file but I got this message: <ID:0/003> Can't open the serial(COM) port.
My phone's status remained the same so I am pretty certain that I haven't caused any further damage to it.
Sooo, any ideas?
If possible, I would very much prefer to install CM on it, and am considering rooting it, but most importantly i'm dissapointed with samsung's default os.
Thanks in advance,
Macro
If odin cant see it you've buggered it proper.
The method was
Install cfautoroot
Install clockwork recovery (official, custom borks your phone).
Install cyanogenmod (via cwm).
The error with the pit file would most likely be a bad file or wrong version. Playing with the partition table is a no-no and a last resort only.
If you can get odin to see the device in download mode you can flash stock and start over. If not, you have an expensive paperweight.
Samsungs "os" is bada. I think you mean "overlay". I agree. Touchwiz is rubbish but i think samsung only do it to grate some apple.
I wish I stole my HTC M9.
Hi! Thank you for the reply
I tried earlier to download a stock and flash it with odin (3.07) and got the same pit file error, specifically this:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGMK7_I9300OJKGMK1_I9300JKUGML1_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)
What kind of wrong files would I have? Are you talking about the cfautorout version for my model, or do you mean that I should use a different odin version?
macrokrome said:
Hi! Thank you for the reply
I tried earlier to download a stock and flash it with odin (3.07) and got the same pit file error, specifically this:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGMK7_I9300OJKGMK1_I9300JKUGML1_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)
What kind of wrong files would I have? Are you talking about the cfautorout version for my model, or do you mean that I should use a different odin version?
Click to expand...
Click to collapse
As I see you should send your device for a repair. It says there is no pit partition that as I know it mean there is no pit partition in your device!! So you totally messed it up and don't know what you have done but it needs a repair.
As oddly as it sounds, I had practically nothing on it. Never messed with it or anything. Barely any apps, no root/mod/whatever.
After looking into it with a friend, it seems like this problem is called SDS, and I saw some references to it over here:
http://forum.xda-developers.com/galaxy-s3/general/ultimate-gs3-sudden-death-thread-t1993044
I will look into it tomorrow afternoon once I'm free, but according to my friend, this would require a replacement motherboard... Might as well buy a new phone, lol
Still, if you have any ideas, I'd be happy to hear them. Thanks for your help up until now