I9300 internation, Bootloop + Odin problems? - Galaxy S III Q&A, Help & Troubleshooting

Hey guys, recently got mugged for my new S5 and was given a unlocked, bootloop'd S3 i9300 international galaxy s3 (Im from Canada). My buddy told me he had dropped it from about knee high onto carpet when it started having some issues with restarting randomly. He attempted to root it to solve the problems and ended up getting it stuck in a bootloop without the possibility of entering recovery mode. However the phone does go into download mode, so I'm assuming this is a fixable semi brick?
Anyways I started doing my research and found out I should try and reflash the stock firmware using Odin. I found a firmware which I beleive to be the right one, and tried to use Odin.
I got the following message;
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>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
So I have no idea what this means, as every guide I've seen has said not to touch the PIT button etcetc
I'm not sure if this is helpful, but the writing in download mode is as follows : Odin Mode * Product Name (Blank) * Custom Binary Download : No * Current Binary : Samsung Official * System Status : Custom.
That's about all of the info I have, and seeing how this is the only phone I can afford right now any help would be very much appreciated. Thanks guys.

AlexD73 said:
Hey guys, recently got mugged for my new S5 and was given a unlocked, bootloop'd S3 i9300 international galaxy s3 (Im from Canada). My buddy told me he had dropped it from about knee high onto carpet when it started having some issues with restarting randomly. He attempted to root it to solve the problems and ended up getting it stuck in a bootloop without the possibility of entering recovery mode. However the phone does go into download mode, so I'm assuming this is a fixable semi brick?
Anyways I started doing my research and found out I should try and reflash the stock firmware using Odin. I found a firmware which I beleive to be the right one, and tried to use Odin.
I got the following message;
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>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
So I have no idea what this means, as every guide I've seen has said not to touch the PIT button etcetc
I'm not sure if this is helpful, but the writing in download mode is as follows : Odin Mode * Product Name (Blank) * Custom Binary Download : No * Current Binary : Samsung Official * System Status : Custom.
That's about all of the info I have, and seeing how this is the only phone I can afford right now any help would be very much appreciated. Thanks guys.
Click to expand...
Click to collapse
Have you tried more than one stock firmware. Where is the phone originally from? I'm not able to find and Canadian firmware.

Darke5tShad0w said:
Have you tried more than one stock firmware. Where is the phone originally from? I'm not able to find and Canadian firmware.
Click to expand...
Click to collapse
I was using UK stock firmwares, but I am unable to flash any firmwares at all successfully due to the error above. It wont go father then the "No Pit".

This try
http://www.ibtimes.co.uk/install-i9300xxugna5-android-4-3-stock-firmware-galaxy-s3-1434726

AlexD73 said:
I was using UK stock firmwares, but I am unable to flash any firmwares at all successfully due to the error above. It wont go father then the "No Pit".
Click to expand...
Click to collapse
Heres the link to the rescue firmware. All the info you gave me says you have pit problems.
This is an emergency firmware that will ever fix or brick the phone but the phone was given to you and you have nothing to lose.
http://forum.xda-developers.com/showpost.php?p=30087735

Darke5tShad0w said:
Heres the link to the rescue firmware. All the info you gave me says you have pit problems.
This is an emergency firmware that will ever fix or brick the phone but the phone was given to you and you have nothing to lose.
http://forum.xda-developers.com/showpost.php?p=30087735
Click to expand...
Click to collapse
The 4.3 download doesn't have the PIT file in it though, I'm guessing that's the important part? Edit *** repartition failed with the 4.1.2

AlexD73 said:
The 4.3 download doesn't have the PIT file in it though, I'm guessing that's the important part? Edit *** repartition failed with the 4.1.2
Click to expand...
Click to collapse
The pit file is in the rescue firmware file. That's the whole point of the rescue firmwares.
I'm sorry I can't help you any further. I'm not going to provide you a pit file etc as I have no knowledge with them or used them.
Sounds to me like it is bricked.
Good Luck.

The power button is stuck, try to flick it some times and it should stop the bootloop. i drop mine when i was getting it out of my pocket last week and same thing happen, the smd switch got stuck and eventually i broke it down trying to get it lose again.

Related

Help please. Odin won't complete flash.

I'm trying to flash stock firmware with Odin. It's stuck on factoryfs.img.
Here is what shows up on the screen:
<ID:0/009> Added!!
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> factoryfs.img
I am using the one click downloader from this link. Please tell me what I need to do to fix this. Thanks.
I found that sometimes its all in the technique of how you plug things in and the usb used. Try different usb cords. Try different usb ports. and then for some reason what worked for me is have odin open plug usb into computer, and then put the phone into download mode and finally connect the microUSB into the phone. Hope it works, hit back if it does or doesnt
[email protected] said:
I'm trying to flash stock firmware with Odin. It's stuck on factoryfs.img.
Here is what shows up on the screen:
<ID:0/009> Added!!
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> factoryfs.img
I am using the one click downloader from this link. Please tell me what I need to do to fix this. Thanks.
Click to expand...
Click to collapse
How long did you let it go for on the factoryfs.img?
It could be as simple as changing usb cable. Use the one that came with the phone. Or changing to a different usb port, preferably one directly connected to the mother board.
Beyond that, we would need to know more information about your situation. Why are you flashing stock firmware, from what condition of the phone, etc. Give as much detail as possible.
creepyncrawly said:
It could be as simple as changing usb cable. Use the one that came with the phone. Or changing to a different usb port, preferably one directly connected to the mother board.
Beyond that, we would need to know more information about your situation. Why are you flashing stock firmware, from what condition of the phone, etc. Give as much detail as possible.
Click to expand...
Click to collapse
I have tried it on all usb ports that I have on my laptop.
OK here's exactly what I did to my phone:
I downloaded the ICS version for i777 from sammobile and flashed it using ODIN. Then, I installed Siyah kernel using mobile odin. I then installed triangle away to get rid of the flash counter. I used my phone like this for a couple of days. Then today, I installed the AOKP rom. To do this, I first back up using CWM, then i booted in CWM recovery mode, did a complete wipe, deteled cache and dalvik, and then I proceeded to install the rom. Installation worked fine and everything, however the data wasn't working on my phone. So I then tried to enter the T-Mobile APN settings (it's an unlocked phone), however I couldn't save the APN settings. Tried to enter them multiple times and selected save from the menu, but it just wouldn't show up on the APN list. So, I tried to restore to my back up in CWM restore, however that failed. Admittedly, I should have asked for help at this point. However I was frustrated, so I decided to just use Odin again to flash the ICS stock firmware that I got from sammobile. However, it failed and had some error along the lines of completed writing but operation failed? I tried switching to different USB ports and restarted Odin with run as administrator, but kept getting the same error. On one of these numerous tries, I also tried to check the re-partition option just to see if that would change anything (probably not a very smart idea). Anyways, at some point during these numerous attempts, it got to the point where the phone wouldn't boot up and asked me to connect to samsung kies to restore. I tried that but my phone won't connect with kies. I then found your one-click odin stock firmware thing on these boards and used that. Tried multiple times at different ports, but it keeps getting stuck at factoryfs.img. I have left it in there for a good 30 minutes in this current try (4th). Also, this may or may not be relevant, the flash counter keeps going up.
PS: This is my first android phone so I'm pretty new at this, but I did try to read up a lot before trying anything (well, except for when I randomly checked re-partition that one time).
Edit: Sorry I should have made this clear - even though the phone will not boot, I can still get into download mode.
OK. It seems there is always AOKP in the mix somewhere, and I don't know that firmware at all well, but it seems to make some changes that are hard to fix sometimes.
Can you get into recovery mode at this point? You may still be able to depending on what has happened during the various Odin flashes. Try that and let me know, and if so what recovery do you have?
creepyncrawly said:
OK. It seems there is always AOKP in the mix somewhere, and I don't know that firmware at all well, but it seems to make some changes that are hard to fix sometimes.
Can you get into recovery mode at this point? You may still be able to depending on what has happened during the various Odin flashes. Try that and let me know, and if so what recovery do you have?
Click to expand...
Click to collapse
'
Thank you for the swift response. No, I am unable to get into recovery mode. It goes to a screen that says "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again."
I'm sort of guessing here based on information I've gleaned from various threads. You might try flashing just the siyah ICS kernel in Odin. You can download the tar for siyah 3.4.2 from here. It certainly can't make things worse at this point to try. Let me know.
While I didnt have your issues. I also recently bought an i777, my install went very smooth, everything worked more or less on the first try tried diff cords, ports and then finally it was the plug sequence that did it for me. Upon flashing AOKP, I immediately unlocked the phone via that galaxy S unlocker, I followed the steps to the T and my IMEI is still the same. I am also on tmobile, with working edge. I still have the pesky triangle, but I havent read too many good things about the triangle remover.
Perhaps you have a bad rom download? It might sound silly but flashing AOKP for a friend when I redownloaded the rom, everything worked fine. What the guy above me said, try recovery mode instead and then go from there. Good news is that your phone doesnt sound borked
creepyncrawly said:
I'm sort of guessing here based on information I've gleaned from various threads. You might try flashing just the siyah ICS kernel in Odin. You can download the tar for siyah 3.4.2 from here. It certainly can't make things worse at this point to try. Let me know.
Click to expand...
Click to collapse
Ok I tried this, and it completed successfully in Odin, however, the phone now gets stuck on the "Samsung Galaxy SII GT-I9100" screen.
But will it boot into recovery now?
creepyncrawly said:
But will it boot into recovery now?
Click to expand...
Click to collapse
No, it still does not boot into recovery.
OT: How long will I have the 5 min restriction on posting?
Also, I don't know if this is relevant, but when I try to turn off the phone, it turns off but then it'll automatically start back up within a few seconds and then get stuck on the samsung galaxy sII screen
Don't know. 10 posts?
I don't think the flash with partition checked would have caused a problem. You didn't put a path to a pit file in the pit slot did you?
The full UCKH7 firmware package should flash. Is that what you downloaded from sam firmware? You might try downloading that from the Download Repository (link in my signature) and try flashing it once again. It must be the UCKH7 stock though, because that one has the secondary bootloader and param.lfs file. The UCLE5 does not.
creepyncrawly said:
Don't know. 10 posts?
I don't think the flash with partition checked would have caused a problem. You didn't put a path to a pit file in the pit slot did you?
The full UCKH7 firmware package should flash. Is that what you downloaded from sam firmware? You might try downloading that from the Download Repository (link in my signature) and try flashing it once again. It must be the UCKH7 stock though, because that one has the secondary bootloader and param.lfs file. The UCLE5 does not.
Click to expand...
Click to collapse
No, I didn't put a pith file. Also just to make sure I'm flashing the right file, is it the one called "I777 UCKH7 stock param.lfs"?
Flash the firmware from the section titled I777UCKH7-CL503881 Stock Binaries.
You can use either the one-click downloadedr or the tar.md5 file.
Let me know if that flashes.
And also, is that the same file you downloaded from samfirmware? Because that is where this file came from. Or did you download the UCLE5 firmware from samfirmware?
creepyncrawly said:
Flash the firmware from the section titled I777UCKH7-CL503881 Stock Binaries.
You can use either the one-click downloadedr or the tar.md5 file.
Let me know if that flashes.
And also, is that the same file you downloaded from samfirmware? Because that is where this file came from. Or did you download the UCLE5 firmware from samfirmware?
Click to expand...
Click to collapse
It was the UCLE5 file. I'll try this one.
Now it gets stuck on Sbl.bin. Here is what it says:
<OSM> I777UCKH7-REV02-home-low-CL503881.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin v.3 engine (ID:10)..
<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> Sbl.bin
I'll let it run for another 5 or so minutes, then I'll try different ports and see what happens.
[email protected] said:
Now it gets stuck on Sbl.bin. Here is what it says:
<OSM> I777UCKH7-REV02-home-low-CL503881.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin v.3 engine (ID:10)..
<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> Sbl.bin
I'll let it run for another 5 or so minutes, then I'll try different ports and see what happens.
Click to expand...
Click to collapse
OK I tried it on all the USB ports that I have on my laptop. No luck. Still getting stuck at Sbl.bin. Any more ideas?
Yes. If it were my phone, I would start by flashing the param.lfs by itself and see if that allows it to boot, or makes progress.
If not, then I would flash the sbl.bin by itself and see if that allows it to boot, or makes progress.
If still not, then I would try the full UCKH7 package with the PIT file, and repartition checked.
You can get all the files from the Download Repository. Please bear in mind that there is risk in everything you are doing, (and have been doing.)

ODIN flash fail (no pit partition)

A friend of mine over at a Swedish forum is having problems with his SGS3 i9300. His phone just died, completely random, and refused to boot. he can only boot to download mode, nothing else.
He tried flashing a stock nordic ROM, which failed since ODIN threw him a "there is no pit partition" message. He tried flashing various PIT files, but it all stops with "there is not PIT partition" He did not do anything to his device for this to happen, it just died on him and that's where it all started.
Shot in the dark, but has his NAND memory somehow crashed, which caused the error of not booting/not accepting PIT files?
Theshawty said:
A friend of mine over at a Swedish forum is having problems with his SGS3 i9300. His phone just died, completely random, and refused to boot. he can only boot to download mode, nothing else.
He tried flashing a stock nordic ROM, which failed since ODIN threw him a "there is no pit partition" message. He tried flashing various PIT files, but it all stops with "there is not PIT partition" He did not do anything to his device for this to happen, it just died on him and that's where it all started.
Shot in the dark, but has his NAND memory somehow crashed, which caused the error of not booting/not accepting PIT files?
Click to expand...
Click to collapse
Hi! It just happened to me today! In the morning I was using the phone - calling someone.
Then put it into my pocket, went to work, and there it was already at the boot page, and staying there when resetting.
Tried to flash with odin, and I get the same error message as your friend.
I had a stock 4.0.4 rom, never touched anything on the phone yet.....
Any idea from someone?
edit:
as i9000 has linked to newer firmware with everything in post bellow, so just use that.
http://forum.xda-developers.com/show....php?t=1825272
niches said:
Hi! It just happened to me today! In the morning I was using the phone - calling someone.
Then put it into my pocket, went to work, and there it was already at the boot page, and staying there when resetting.
Tried to flash with odin, and I get the same error message as your friend.
I had a stock 4.0.4 rom, never touched anything on the phone yet.....
Any idea from someone?
Click to expand...
Click to collapse
Return under warranty .
jje
JJEgan said:
Return under warranty .
jje
Click to expand...
Click to collapse
yeah, problem is I bought it from amazon.de so I have to send it then via Post :S
tumult said:
full firmware flash with pit, bootloader, tz, etc..
hooe the link still works, if not i can make mirror tomorrow
also check in Odias thread in original android development if pit for 16 & 32 is same, but as far as i remember it is.
ps. i have flashed this firmware (without pit, but it is safe to download , no viruses, etc).
hope it helps
Click to expand...
Click to collapse
Thanks, I'll try it when I arrive home from celebrating the 253rd birtday of Mr. Guiness
Theshawty said:
A friend of mine over at a Swedish forum is having problems with his SGS3 i9300. His phone just died, completely random, and refused to boot. he can only boot to download mode, nothing else.
He tried flashing a stock nordic ROM, which failed since ODIN threw him a "there is no pit partition" message. He tried flashing various PIT files, but it all stops with "there is not PIT partition" He did not do anything to his device for this to happen, it just died on him and that's where it all started.
Shot in the dark, but has his NAND memory somehow crashed, which caused the error of not booting/not accepting PIT files?
Click to expand...
Click to collapse
All ROMs have full set images of partitions and may be flash with pit and repartition, pit - attached...
http://forum.xda-developers.com/showthread.php?t=1825272
as i9000 said:
All ROMs have full set images of partitions and may be flash with pit and repartition, pit - attached...
http://forum.xda-developers.com/showthread.php?t=1825272
Click to expand...
Click to collapse
edit: i was wrong, all partitions are there.
when you say full partition, you mean sboot.bin and tz.img also? sorry, don't think so , but if so good to know.
that's why i posted link above, that was only full firmware I could find.. but maybe it's just me.
tumult said:
when you say full partition, you mean sboot.bin and tz.img also? sorry, don't think so , but if so good to know.
that's why i posted link above, that was only full firmware I could find.. but maybe it's just me.
Click to expand...
Click to collapse
You can watch attached screen, 9 images:
sboot.bin
param.bin
tz.img
boot.img
recovery.img
system.img
cache.img
hidden.img
modem.bin...
You upload link of ROM full service ROM for Russia...
Why swedish man csc ser, russian location?
all the more so very old...
as i9000 said:
You can watch attached screen, 9 images:
sboot.bin
param.bin
tz.img
boot.img
recovery.img
system.img
cache.img
hidden.img
modem.bin...
You upload link of ROM full service ROM for Russia...
Why swedish man csc ser, russian location?
all the more so very old...
Click to expand...
Click to collapse
and i said sorry if i missed it .. anyway, i will delete my link then as yours are uptodate.
tumult said:
and i said sorry if i missed it .. anyway, i will delete my link then as yours are uptodate.
Click to expand...
Click to collapse
should not be deleted link, and the Russian people attend the xda forum ...
tumult said:
edit:
as i9000 has linked to newer firmware with everything in post bellow, so just use that.
http://forum.xda-developers.com/show....php?t=1825272
Click to expand...
Click to collapse
this is all great, but I think that does not work, I have met with this diagnosis: "there is no pit partition"
INTERNAL MMC IS DEAD... ((((
I'm having a similar problem. Except mine is a GT-I9300. Odin gives me this error.
<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.
<ID:0/006> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
TinyGrasshopper said:
I'm having a similar problem. Except mine is a GT-I9300. Odin gives me this error.
<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.
<ID:0/006> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Hey all, I have exactly the same error message. Running cm10 and my phone just froze, after re-boot i'm stuck on boot screen, no recovery and can only enter download mode....HELP!!!!
Someone reported that they had success with flashing the CF-Root to gain CWM recovery back and then flashing DarkyROM from it. But I don't know if that is even true.
PjotrFias said:
Someone reported that they had success with flashing the CF-Root to gain CWM recovery back and then flashing DarkyROM from it. But I don't know if that is even true.
Click to expand...
Click to collapse
thanks for the reply, i tried it but to no avail :crying:
Where did it stop? The first part?
PjotrFias said:
Where did it stop? The first part?
Click to expand...
Click to collapse
yeah i got the no pit message, tried flashing the pit file but won't do it...
I've just received this error on my phone too, Has there been any progress on solutions to this?
Another problem is that I can get into download mode and my system status is "Custom", How will this effect a return to manufacturer?
alot of replies with this errors lately...u guys used any custom FW ?

Int'l S3 (GT-I9300) no longer booting & Possible issues with flashing GT-I9300?

Hello,
I have an International (or UK I guess) Galaxy S3, Model No.: GT-I9300. One day it wasn't responding, so I took the battery out and put it back in, and when I restarted it, it got stuck at the boot screen indefinitely. I tried going to the Recovery Mode to do the factory reset but it wouldn't respond to that (Many people have tried), but I can go into Download mode however.
My first question is what could this issue possibly be, where it doesn't respond to going into Recovery Mode, but still Download mode works? Is flashing the phone likely to fix the issue? I've searched this forum but couldn't find anything that seemed close to my issue. The phone has never been rooted and is running the most up to date stock ROM that I could get from Kies (Well, I ran a firmware update a few months ago using Kies and it's been working fine since then)
So I thought that reflashing it with the stock firmware using Odin would solve my problems. I found this link on the wiki which led me to this thread on the forum. So I have set up my machine to follow those instructions with the UK stock rom which in the thread is detailed as
XXALE8
Firmware Info
PDA: XXALE8
Phone: XXLE8
Date: 13/05/2012
Android Version: 4.0.4
where I selected the BTU link below it.
I was about to start the flash, but then my friend who's on xda all the time said that he saw threads with people who've been having problems with the International S3 with Odin. I've searched and found nothing. It seemed unlikely but I figure I should make a post to get the opinion on this.
Have there been issues with using Odin with the International Galaxy S3? Is there anything that people recommend that I be certain that I do before attempting this?
EDIT: I tried it and got this message:
<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.
<ID:0/006> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
It's often file permission error, fix it with cwm recovery.
Howto in stiky threds. Nwm did not ser the pit stuff.
Sent from my GT-I9300 using xda app-developers app
http://forum.xda-developers.com/showthread.php?t=1760683&page=2 seems to have happened to others google the fauld to see what you can find?

Samsung i9300 Re-Partition failed after try flashing with Odin

After try to recover my S3 ('cause i get a brick the typical problem that Samsung screen and then nothing happend, i put my cell into download mode and then try to flash only with PDA file i got the next error "There is no pit partition" ), following this steps from another post
http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6
i take the
4.1.2
I9300XXELLA_KOR_MULTI_FACTORY
i got a new message from Odin
see image1 in attachements
Now i don't know what to do... just i know is a little hope 'cause it can start a downloading mode...
So Please HELP!
there is the problem
<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> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
What i need to do...!!! PLEASE HELP
Same problem
GaboBigale said:
there is the problem
<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> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
What i need to do...!!! PLEASE HELP
Click to expand...
Click to collapse
Got the same problem man, if you resolve it first, let me know.:good:
Same problem
lumogox said:
Got the same problem man, if you resolve it first, let me know.:good:
Click to expand...
Click to collapse
got this same problem also, please, anyone? any help?
pit file missing
you have to download pit file so it can create a partition. download it and flash it together with the tar file of your desired firmware. i had the same problem but it couldn't create a partition as it is full bricked and i sent it for a warranty
re-partition fails
panais86 said:
you have to download pit file so it can create a partition. download it and flash it together with the tar file of your desired firmware. i had the same problem but it couldn't create a partition as it is full bricked and i sent it for a warranty
Click to expand...
Click to collapse
thanks for the replay, unfortunately i have already tried that, it fails every time i am trying to re-partition.
echoen99 said:
thanks for the replay, unfortunately i have already tried that, it fails every time i am trying to re-partition.
Click to expand...
Click to collapse
try to flash only the .PIT file.
you have nothing to loose
nand problem
echoen99 said:
thanks for the replay, unfortunately i have already tried that, it fails every time i am trying to re-partition.
Click to expand...
Click to collapse
try this link
http://www.droidevelopers.com/f363/...-files.html?11722-Download-OPS-amp-PIT-files=
if you have a problem as well then probably you have a problem with nand so you have to send it for warranty as well
Thanks for all the replys, i will check and update
Thanks
Sent from my GT-I9300 using Tapatalk 2
stuck same problem
hi
i have a smasung galaxy s3 international I9300
i think i soft bricked it cause i can go into download mode but when i swithch on the phone it gives me a screen
//i276.photobucket.com/albums/kk29/mlijfu/photo.jpg
how i reached here was i flashed my phone with 3-4 roms got bit stuck and then removed my battery in the middle of a reboot there here i was
so i used ur RESCUE FIRMWARE SGSIII I9300 - I9300XXEMC2_KOR_MULTI_FACTORY
same used in the first thread
but did not help
i got this
//i276.photobucket.com/albums/kk29/mlijfu/Untitled1.png
//i276.photobucket.com/albums/kk29/mlijfu/Untitled.png
pls help
mlijfu said:
hi
i have a smasung galaxy s3 international I9300
i think i soft bricked it cause i can go into download mode but when i swithch on the phone it gives me a screen
//i276.photobucket.com/albums/kk29/mlijfu/photo.jpg
how i reached here was i flashed my phone with 3-4 roms got bit stuck and then removed my battery in the middle of a reboot there here i was
so i used ur RESCUE FIRMWARE SGSIII I9300 - I9300XXEMC2_KOR_MULTI_FACTORY
same used in the first thread
but did not help
i got this
//i276.photobucket.com/albums/kk29/mlijfu/Untitled1.png
//i276.photobucket.com/albums/kk29/mlijfu/Untitled.png
pls help
Click to expand...
Click to collapse
What ROM and what Kernel did you use before it happened (Kernel version is also important)? And what did you mean with you got stuck? Details are important when you are dealing with cases like this.
I saw this kind of screen before, some guy had the same problem. However he couldn`t fix himself. Ever heard of Sudden Death?
Scarface1991 said:
What ROM and what Kernel did you use before it happened (Kernel version is also important)? And what did you mean with you got stuck? Details are important when you are dealing with cases like this.
I saw this kind of screen before, some guy had the same problem. However he couldn`t fix himself. Ever heard of Sudden Death?
Click to expand...
Click to collapse
thanks for the reply
CyanogenMod 9 stable version with its own kernel
i installed it and the gapps with it then when the phone rebooted it got stuck at lock screen then i reebooted it again but it was taking a bit long time at samsung logo so i took off the battery and there the phone became like this
//i276.photobucket.com/albums/kk29/mlijfu/photo.jpg
i can go into download mode
ODIN MODE
Product name:
custom binary download:no
currant binary: samsung official
system status : custom
as u can see product name is blank
with odin i tried ti flash stock Samsung firmware - it wanted some pit
so i used RESCUE FIRMWARE SGSIII I9300 - I9300XXEMC2_KOR_MULTI_FACTORY
same used in the first thread
but did not help
i got this
//i276.photobucket.com/albums/kk29/mlijfu/Untitled1.png
//i276.photobucket.com/albums/kk29/mlijfu/Untitled.png
mlijfu said:
thanks for the reply
CyanogenMod 9 stable version with its own kernel
i installed it and the gapps with it then when the phone rebooted it got stuck at lock screen then i reebooted it again but it was taking a bit long time at samsung logo so i took off the battery and there the phone became like this
//i276.photobucket.com/albums/kk29/mlijfu/photo.jpg
i can go into download mode
ODIN MODE
Product name:
custom binary download:no
currant binary: samsung official
system status : custom
as u can see product name is blank
with odin i tried ti flash stock Samsung firmware - it wanted some pit
so i used RESCUE FIRMWARE SGSIII I9300 - I9300XXEMC2_KOR_MULTI_FACTORY
same used in the first thread
but did not help
i got this
//i276.photobucket.com/albums/kk29/mlijfu/Untitled1.png
//i276.photobucket.com/albums/kk29/mlijfu/Untitled.png
Click to expand...
Click to collapse
This is half sds. Needs to go to a service centre and have the motherboard swapped probably
Sent from my GT-I9300 using Tapatalk 2
rootSU said:
This is half sds. Needs to go to a service centre and have the motherboard swapped probably
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
will a Samsung Galaxy S III JTAG Brick Repair help me ?
mlijfu said:
will a Samsung Galaxy S III JTAG Brick Repair help me ?
Click to expand...
Click to collapse
No one has been successful with that method yet. The issue will be that the wear levelling bug has wiped out your eMMC and it needs replacing.
Have a read in the general forum of the "ultimate SDS thread" or whatever its called. There is also my "important - are you covered" thread stuck at the top of general.
So thats the sudden death ? Were you on 4.1.2 before you bricked?
Sent from my GT-I9300 using xda app-developers app
KayKrate said:
So thats the sudden death ? Were you on 4.1.2 before you bricked?
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
before rooting was on what ever the latest firmware was
i did not use triangle away
i was using paranoid android 4.2.2
then went to cmod9
so i think i am screwed
CM9 has no SDS fix.
All you can do is try and get warranty repair if you're still in warranty. Otherwise pay for a Mobo repair / replacement.
Someone posted a how to to fit a new eMMC and the cost of the eMMC was cheap, but the effort was a lot.
People gotta take care what firmware to flash :/ Stock 4.1.2 is safe , I used DFG and didnt get any freeze for like a week so my phone's stable now ... maybe samsung come up with a new firmware which makes your phone explode or ruin our devices ... Who knows >.< ?
rootSU said:
CM9 has no SDS fix.
All you can do is try and get warranty repair if you're still in warranty. Otherwise pay for a Mobo repair / replacement.
Someone posted a how to to fit a new eMMC and the cost of the eMMC was cheap, but the effort was a lot.
Click to expand...
Click to collapse
will this help i know its not for s3 but still as am desperate
1. ://forum.xda-developers.com/showthread.php?t=1670651
2. ://forum.xda-developers.com/showthread.php?p=26428986
3. //forum.xda-developers.com/showpost.php?p=26285877&postcount=12
just wanted to know from an expert will one of then work for me?

Samsung s4 rooted unknown method unknown firmware stuck in download mode

So I was given this phone that is stuck in download mode and am having quite a few problems getting it flashed with odin.... it seems to fail every time. not sure on the original android version it was rooted on .. The only information I was given is that it was rooted at one point and then they did a factory wipe getting it stuck in download mode... Seeing as Im new to this whole scene any help would be much appriciated
Tried 3 different firmwares from a post here
and also tried to get kies to recognize the phone .. It will not ,It is stuck at connecting
<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)
Update:
On download screen : sw rev check fail....
If i have to choose a certain version of the firmware is there anyway to check the version I need without having to turn on the phone?
Does the sw rev check fail error mention a fuse and or binary with a number next to it?
Matthew M. said:
Does the sw rev check fail error mention a fuse and or binary with a number next to it?
Click to expand...
Click to collapse
fuse 0 binary 5
So .. I got the phone working by doing a firmware upgrade or initialization in kies, So I suppose It is fixed now .. I would still like to know what the problem could be using odin? I tried 5 different firmware upgrades from oldest to newest and couldnt get it to work. It is still kinda vexxing me, im sure I was doing somthing wrong . Any extra insight would be helpful to avoid this headache in the future?
You should go back to kies and see what version it flashed. That way if this ever happens again you can download that version and flash it through odin
Deleted
Serioussamuel said:
So .. I got the phone working by doing a firmware upgrade or initialization in kies, So I suppose It is fixed now .. I would still like to know what the problem could be using odin? I tried 5 different firmware upgrades from oldest to newest and couldnt get it to work. It is still kinda vexxing me, im sure I was doing somthing wrong . Any extra insight would be helpful to avoid this headache in the future?
Click to expand...
Click to collapse
Can you explain how you did this? I am running into a similar problem and neither a firmware upgrade nor a kies initialization is working.
Same problem here, I also don't know what my phone bootloader or firmware, I'm also stock in download mode...hope someone can answer and help us...

Categories

Resources