Related
Ok. So, today my gt-i9300 started working. I was using the Resurrection Remix rom 3.1.4 on my phone. Suddenly i wanted to check what's the time and the phone was one, the led was blipping but the phone wasn't working. I restarted it and app after app was crashing, whatsapp couldn't find the conversations, viber wasn't signed in, also the contacts weren't all found. I restarted it again, signed into viber, restored some contacts and i wanted also to restore my messages. I did it and it stopped again and i tried to restart again. Once i did, IT IS STUCK AT THE Samsung Galaxy S III GT-I9300 logo. I don't even know if this is a bootloop and how to fix it. Please help me guys, i really need it!!! And also if it's possible to save what's on my phone so i can put it back on the new software or something? How do to that?
Jokerbest2006 said:
Ok. So, today my gt-i9300 started working. I was using the Resurrection Remix rom 3.1.4 on my phone. Suddenly i wanted to check what's the time and the phone was one, the led was blipping but the phone wasn't working. I restarted it and app after app was crashing, whatsapp couldn't find the conversations, viber wasn't signed in, also the contacts weren't all found. I restarted it again, signed into viber, restored some contacts and i wanted also to restore my messages. I did it and it stopped again and i tried to restart again. Once i did, IT IS STUCK AT THE Samsung Galaxy S III GT-I9300 logo. I don't even know if this is a bootloop and how to fix it. Please help me guys, i really need it!!! And also if it's possible to save what's on my phone so i can put it back on the new software or something? How do to that?
Click to expand...
Click to collapse
If you can get in to recovery restore the backup you should have made before you installed the rom. can you get in to download mode?
Jokerbest2006 said:
Ok. So, today my gt-i9300 started working. I was using the Resurrection Remix rom 3.1.4 on my phone. Suddenly i wanted to check what's the time and the phone was one, the led was blipping but the phone wasn't working. I restarted it and app after app was crashing, whatsapp couldn't find the conversations, viber wasn't signed in, also the contacts weren't all found. I restarted it again, signed into viber, restored some contacts and i wanted also to restore my messages. I did it and it stopped again and i tried to restart again. Once i did, IT IS STUCK AT THE Samsung Galaxy S III GT-I9300 logo. I don't even know if this is a bootloop and how to fix it. Please help me guys, i really need it!!! And also if it's possible to save what's on my phone so i can put it back on the new software or something? How do to that?
Click to expand...
Click to collapse
Hey, you can enter download mode right? if yes you can flash stock firmware via odin or if you can have a access to recovery. how about to wipe data, cache and dalvik cache. it might or might not working. Have a try.
Yes, I can access download mode. So I should just flash the original firmware for the country i live in with odin by just putting it in the bootloader section and that's it?
Ok, what the hell, i download the stock firmware for my i9300 and when i'm flashing it with odin 3.04 i get this:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXEMA2_I9300TNLMA2_I9300BOLK3_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..
It happened when the .tar file was on pda and now on phone, and it's staying like this for 10 minutes without doing something....WTH?!?!? PLEASE HELP!!!!!
Jokerbest2006 said:
Ok, what the hell, i download the stock firmware for my i9300 and when i'm flashing it with odin 3.04 i get this:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXEMA2_I9300TNLMA2_I9300BOLK3_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..
It happened when the .tar file was on pda and now on phone, and it's staying like this for 10 minutes without doing something....WTH?!?!? PLEASE HELP!!!!!
Click to expand...
Click to collapse
chill. are you sure your downloaded firmware is not corrupted? put the .tar file at pda. i suggest you to look at ultimate guide there. it will assist you from A-Z
The file is not corrupted, it's download from sammobile.com, that's the thing. I will download it again and try again maybe it will work. Thanks
So, what to do in case the flashing thing doesn't work on my phone? maybe specialised service center would help or something, pls pls i need solutions!!!
Nono, don't put it in the bootloader field, put it in PDA field.
Seems like a driver issue, reinstall drivers and uninstall Kies, try a different cable, port, OS, pc
Jokerbest2006 said:
The file is not corrupted, i
How do you know its not corrupted ???
Information reads as file corrupt or user not following instructions .
Service
Cheapest method is to start with a JTag service .
jje
Click to expand...
Click to collapse
About setup connection (I'M NOT SURE !!) Insert your sd card .
I had this problem before with my old Galaxy Y . (The same problem 100%)
.......
Guys I need a little help ... my friend's phone (SGS3) can't boot , it just shows the samsung logo (logo begore bootanimation) .
can't enter recovery , but can enter download mode .
I tried to flash it with odin and it success ,, but the phone doesn't boot ??????
As far as I know the problem is with bootloaders . How to flash them ??
I'm very new with samsung , in LG devices we use a completely other tools .
Thanks on advance .
#------------------------------------------
echo "Sender.product.model=LG-P880" # (O4X) .
if [ $thanks -eq $pressed ] ; then
thanks_meter=$((${thanks_meter} + 1)) ; fi #Press it
I'd the flash was successful then boot to stock recovery and do factory reset, then it should boot
Note that this will wipe data AND internal sd card
Ok so i tried again to flash the stock jelly bean back and in odin it shows me like this:
<OSM> I9300XXELLA_I9300OROELL1_I9300BVELK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008>
<ID:0/008> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
The part where it says there's no pit partition worries me most. What should I do in this case, I really want to fix my phone? Should I flash the software again and tick "Re-partition''?
May help.
http://forum.xda-developers.com/showthread.php?t=1796062
jje
I have a Galaxy S3 GT-I9300 running the Samsung Stock 4.1.2 ROM.
It was rooted and I tried to flash CWM Recovery using Mobile Odinbut as soon as I did that the only thing that now appears when I try to boot the phone is the initial black screen with the "Samsung Galaxy SIII GT-I9300" words.
I cannot get into Recovery mode.
I can get in to download mode but no matter what I try with Odin it sticks at setupconnection. I have used Odin to try and re flash CWM to try and get back into Recovery mode but get stuck at setupconnection.
I have used Odin to try and re flash the stock ROM but again get stuck at setupconnection.
I get this whether I try using Odin on my laptop or my desktop PC
I did wonder if this would happen if my battery charge was low so I plugged the phone in the charger to see what the battery level was when it appeared but the battery will not appear and again I see only the words "Samsung Galaxy SIII GT-I9300" on the black background.
Can anyone suggest a way out of this?
Thanks
matrixmainframe said:
I have a Galaxy S3 GT-I9300 running the Samsung Stock 4.1.2 ROM.
It was rooted and I tried to flash CWM Recovery using Mobile Odinbut as soon as I did that the only thing that now appears when I try to boot the phone is the initial black screen with the "Samsung Galaxy SIII GT-I9300" words.
I cannot get into Recovery mode.
I can get in to download mode but no matter what I try with Odin it sticks at setupconnection. I have used Odin to try and re flash CWM to try and get back into Recovery mode but get stuck at setupconnection.
I have used Odin to try and re flash the stock ROM but again get stuck at setupconnection.
I get this whether I try using Odin on my laptop or my desktop PC
I did wonder if this would happen if my battery charge was low so I plugged the phone in the charger to see what the battery level was when it appeared but the battery will not appear and again I see only the words "Samsung Galaxy SIII GT-I9300" on the black background.
Can anyone suggest a way out of this?
Thanks
Click to expand...
Click to collapse
Which version of ODIN did you use? What kind of file(s) were you trying to flash?
Sent from my GT-I9300 using Tapatalk
I'm not sure but think it was Mobile Odin 3.65 and I was trying to flash CWM touch from xda.
Additionally, I think my battery charge may now be low after many attempts to recover it but will that matter bearing in mind I'm using Odin on my PC and the phone is connected to the PC by USB cable?
One flash Philz recovery and format system data cache and sd card .
Two check your USB drivers for Odin and make sure Kies is not running .
What do you mean Odin sticks at setup connection ??
If its before flashing its drivers or try another version of Odin .
JJEgan said:
One flash Philz recovery and format system data cache and sd card .
Two check your USB drivers for Odin and make sure Kies is not running .
What do you mean Odin sticks at setup connection ??
If its before flashing its drivers or try another version of Odin .
Click to expand...
Click to collapse
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.00.8-i9300.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..
and it stops there
matrixmainframe said:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.00.8-i9300.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..
and it stops there
Click to expand...
Click to collapse
I am reading that as fail before install .
wo check your USB drivers for Odin and make sure Kies is not running .
try another version of Odin .
JJEgan said:
I am reading that as fail before install .
wo check your USB drivers for Odin and make sure Kies is not running .
try another version of Odin .
Click to expand...
Click to collapse
Kies is not installed on my computer and I have tried Odin versions 1.83, 1.85, 3.04, 3.06, 3.07 and 3.09.
I have also tried 'Samsung_USB_Drivers_1.5.27.0.exe' and 'SAMSUNG_USB_Driver_for_Mobile_Phones.exe' and remembering to uninstall then reboot and then install.
On one occasion it got as far as (can't remember the exact words) "Get PIT Mapping" but then just stopped there.
I cannot believe I have done anything other than corrupt the CWM recovery because all I did was try to flash CWM Touch and as soon as I pressed OK the screen went black with the word "Samsung Galaxy SIII GT-I9300". Those words just stay there because since then I can't switch the phone off. I thought that if I just reflashed CWM via Odin on my computer I would be able to get back into recovery mode and just restore my backup.
Appears I am mistaken and have ruined a very new and vey expensive phone.
The only other thing I seem to recall is that before I tried the Mobile Odin flash the battery was below 50% charge but I'm not sure if that's relevant?
This is usually a wrong file flash symptom .
JJEgan said:
This is usually a wrong file flash symptom .
Click to expand...
Click to collapse
Do you mean I'm trying to flash something I shouldn't?
Initially I tried to flash CWM Recovery but then decided just to try and get it back the way it was by trying to flash Android 4.1.2 again.
The file I have been using is "KIES_HOME_I9300XXEMG4_I9300OXAEMG4_1314436_REV00_user_low_ship.tar.md5" which I believe is from Sammobile and which is, I believe again, the ROM that the Galaxy S3 comes pre-installed with. Do you think it worthwhile me trying some other ROM?
I have been doing a lot more web research and some say that the battery charge should be more than 80%. Does this matter?
Won't the battery have been charging all the while the phone was plugged into into the Computer via the USB lead?
If I buy a separate charger and charge my battery to 100% do you think the Odin reflash will work then?
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXELL5_I9300VFGELL1_I9300BUELK1_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> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
so close
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXELL5_I9300VFGELL1_I9300BUELK1_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> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
so close
matrixmainframe said:
I have a Galaxy S3 GT-I9300 running the Samsung Stock 4.1.2 ROM.
It was rooted and I tried to flash CWM Recovery using Mobile Odinbut as soon as I did that the only thing that now appears when I try to boot the phone is the initial black screen with the "Samsung Galaxy SIII GT-I9300" words.
I cannot get into Recovery mode.
I can get in to download mode but no matter what I try with Odin it sticks at setupconnection. I have used Odin to try and re flash CWM to try and get back into Recovery mode but get stuck at setupconnection.
I have used Odin to try and re flash the stock ROM but again get stuck at setupconnection.
I get this whether I try using Odin on my laptop or my desktop PC
I did wonder if this would happen if my battery charge was low so I plugged the phone in the charger to see what the battery level was when it appeared but the battery will not appear and again I see only the words "Samsung Galaxy SIII GT-I9300" on the black background.
Can anyone suggest a way out of this?
Thanks
Click to expand...
Click to collapse
Same here,and i have to load my battery 100% before it gets into 'download mode'again...
Lets see if we can get it up and running again...your not alone...
llcoolveer said:
Same here,and i have to load my battery 100% before it gets into 'download mode'again...
Lets see if we can get it up and running again...your not alone...
Click to expand...
Click to collapse
Nice to know I'm not alone but sorry you're having the same problem. Have sat down to do some more web searching and will let you know if I find a solution
Service centre new motherboard .
JJEgan said:
Service centre new motherboard .
Click to expand...
Click to collapse
Fixxed it by going in the OG recovery....did a hard factory reset and vavooom....fixxed it....:good:
btw,was it a problem that you rooted your phone....? Due to extra costs,or did they bring it under warranty...?
Thanx in advandce for the reply.....
Sincerely ,LLCOOLVEER
llcoolveer said:
Fixxed it by going in the OG recovery....did a hard factory reset and vavooom....fixxed it....:good:
btw,was it a problem that you rooted your phone....? Due to extra costs,or did they bring it under warranty...?
Thanx in advandce for the reply.....
Sincerely ,LLCOOLVEER
Click to expand...
Click to collapse
Please can you tell me what is "OG Recovery"?
Thanks
matrixmainframe said:
Please can you tell me what is "OG Recovery"?
Thanks
Click to expand...
Click to collapse
the Original Recovery....or Stock revovery.....http://www.youtube.com/watch?feature=player_detailpage&v=UvD6ZCENlJA
llcoolveer said:
the Original Recovery....or Stock revovery.....http://www.youtube.com/watch?feature=player_detailpage&v=UvD6ZCENlJA
Click to expand...
Click to collapse
Thanks for that but as I stated in my original post I cannot get into Recovery Mode
matrixmainframe said:
Thanks for that but as I stated in my original post I cannot get into Recovery Mode
Click to expand...
Click to collapse
I couldn't also....only when my battery was full charged....:good:
Succes....
The end
Okay, I started this thread so will end it now as follows:
1 Thank you to all those who offered help/advice/suggestions.
1a Some people do not read posts properly because even though I had specifically stated that I could not get into recovery mode some people proceeded to tell me to go into recovery mode and restore my rom.
2 Whilst I have recovered the full use of my phone I can no longer root it but that's ok because at least I have a phone that is comparable to the vast majority who choose not to root.
3 I will explain how I rescued it but obviously I don't really understand what the result is other than a usable phone so please don't copy.
4 Whilst I have no doubt one could damage a motherboard, that could only be done with very specialist software that most people would not have so the advice of some that I needed a new motherboard was ill informed. If you don't know the answer don't offer an unhelpful answer. Recommending a new motherboard is like a motorist taking his car into a garage with a blown fuse and the mechanic saying the only cure is a new car.
5 After a lot of research I found one lone website that explained that from July 2013 Samsung introduced a change to their ROMs which introduced an efs 2 file. Additionally it appears that once you have flashed/upgraded to an efs2 ROM you cannot then go back to an efs ROM.
6 This is above my understanding but I do know I did go from efs to efs2 and when I then encountered a problem I thought it a good idea to go back to my original (efs) ROM which I now believe caused my problem.
7 I did not know if I had found the answer but as I believed my phone was a paperweight at that point anyway I had nothing to lose and downloaded the GT-I9300.pit file and flashed with repartition selected. I then flashed Android 4.3 knowing it would be an efs2 ROM and my phone is now working again.
8 However, although my phone is now working again, I find that I cannot install a custom recovery nor can I root the phone but that is a small price to pay to have a brand new S3 working again.
9 Whilst it may not be wise to mess about with the pit file, it seems nothing can be lost to give it a go because even if it doesn't work you can still go for the new motherboard option happy in the knowledge you have tried everything.
10 I may start a new thread for advice on that matter but for the time being I'm just relieved to have my phone back and I stress again that it did work for my specific problem and whilst it might work for you please only do it knowing it may not work for your problem.
GS II i9100
Note: Warranty is already expired
Before I write anything further, I have been trying to get the most I can out of this thread: http://forum.xda-developers.com/showthread.php?t=1457458
Sadly, I can't seem to wrap my head around this problem, so here goes:
Yesterday I've found out, that the new CM11 came out. Of course I went off to download it, put it in my phone and started to install it through recovery (I had siyah at that time). Well, it failed, must've been corrupt or something, since I got the error status 7. Anyways, while exiting the install screen, siyah asked me, if I want to repair something, because something may have gotten corrupt (Sorry, can't remember the exact thing). Being the sloppy person I am, I clicked yes.
Five minutes later, after going back to stock firmware, because apparently during the install something did go corrupt, and the phone wouldn't boot, only play the boot sound, I've read, that I need the newest CWM for CM11 to work.
Another five minutes later I'm staring at this:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.07.9-i9100.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> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
I've tried changing computers, kicking KIES out through the window, using different USB slots and cables, but to no avail. It just keeps throwing this error at me every time I try to install anything through Odin. The strangest part is, though, that the phone is working perfectly fine.
What could be the problem, and if it is possible, how do I fix it?
Another quick note would be my counter in the download screen of my SII. It's 12 (yeah, I know, I kept forgetting about it, but now, since I'm unable to install anything through Odin, I can't even root the phone and reset the damn thing)
Don't flash nothing to this phone. Be happy it works or get rid of it while it does still works. Seen this before and this is the first stage of mb failure. Trust me don't flash nothing to this phone and get rid of it. If not start reading about the pit file
andrewwright said:
Don't flash nothing to this phone. Be happy it works or get rid of it while it does still works. Seen this before and this is the first stage of mb failure. Trust me don't flash nothing to this phone and get rid of it. If not start reading about the pit file
Click to expand...
Click to collapse
And apparently, this is now happening:
Baseband version - XXMS2
Build - XWLSS
I think I may have messed it up a little...
Please close the thread
This thread can be closed.
Should anyone need this:
After losing patience spending hours on the phone I have decided to JTAG it... Ant it worked. The phone is running like a charm now.
Hi everyone,
My head is spinning from what's just happened. My phone mysteriously decided to crash on me after being a little slow and unresponsive recently. I'm running CM11 M5 on my phone, I found this is the most stable of the roms for me. The unusual thing about this crash was that it rebooted with a fuzzy, static-like screen, so I tried to reboot into the Cyanogen bootloader thingy and it just brings up the crash screen. I tried to reboot into Odin Mode, hooked up the phone to my computer and tried to reinstall a new ROM. First I tried with Odin 3.07 with a ROM I loaded onto it last month (I9300XXUGNA5_I9300AUTGNA1_I9300XXUGMK6_HOME.tar.md5), but the Odin program on the computer crashes each time. I also tried with an updated version of Odin, v1.85 and also Odin Auto. I had an issue last month, looked around and fixed it by downloading this ROM just mentioned, but this time, no joy. I've tried with another that I just downloaded (root66_TMO_T999UVDLJA.tar.md5) and the same thing happens. At one point, I received a message on different attempts where the Odin program would spit back at me this:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T999UVDLJA.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>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1
So, how do I proceed from this point? I don't know enough to understand what the problem is with this, maybe something to do with the PIT mapping? I feel like I've covered every possible avenue that I can see posted online, I'm really not sure if there is anyone else with this problem, where the Odin program is so volatile. Your thoughts would be greatly appreciated, I suffer without my phone.
Stuart
blackbeardtwenty said:
Hi everyone,
My head is spinning from what's just happened. My phone mysteriously decided to crash on me after being a little slow and unresponsive recently. I'm running CM11 M5 on my phone, I found this is the most stable of the roms for me. The unusual thing about this crash was that it rebooted with a fuzzy, static-like screen, so I tried to reboot into the Cyanogen bootloader thingy and it just brings up the crash screen. I tried to reboot into Odin Mode, hooked up the phone to my computer and tried to reinstall a new ROM. First I tried with Odin 3.07 with a ROM I loaded onto it last month (I9300XXUGNA5_I9300AUTGNA1_I9300XXUGMK6_HOME.tar.md5), but the Odin program on the computer crashes each time. I also tried with an updated version of Odin, v1.85 and also Odin Auto. I had an issue last month, looked around and fixed it by downloading this ROM just mentioned, but this time, no joy. I've tried with another that I just downloaded (root66_TMO_T999UVDLJA.tar.md5) and the same thing happens. At one point, I received a message on different attempts where the Odin program would spit back at me this:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T999UVDLJA.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>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1
So, how do I proceed from this point? I don't know enough to understand what the problem is with this, maybe something to do with the PIT mapping? I feel like I've covered every possible avenue that I can see posted online, I'm really not sure if there is anyone else with this problem, where the Odin program is so volatile. Your thoughts would be greatly appreciated, I suffer without my phone.
Stuart
Click to expand...
Click to collapse
Use this if it fails it needs service repair >> http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6 <<
blackbeardtwenty said:
Hi everyone,
My head is spinning from what's just happened. My phone mysteriously decided to crash on me after being a little slow and unresponsive recently. I'm running CM11 M5 on my phone, I found this is the most stable of the roms for me. The unusual thing about this crash was that it rebooted with a fuzzy, static-like screen, so I tried to reboot into the Cyanogen bootloader thingy and it just brings up the crash screen. I tried to reboot into Odin Mode, hooked up the phone to my computer and tried to reinstall a new ROM. First I tried with Odin 3.07 with a ROM I loaded onto it last month (I9300XXUGNA5_I9300AUTGNA1_I9300XXUGMK6_HOME.tar.md5), but the Odin program on the computer crashes each time. I also tried with an updated version of Odin, v1.85 and also Odin Auto. I had an issue last month, looked around and fixed it by downloading this ROM just mentioned, but this time, no joy. I've tried with another that I just downloaded (root66_TMO_T999UVDLJA.tar.md5) and the same thing happens. At one point, I received a message on different attempts where the Odin program would spit back at me this:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T999UVDLJA.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>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1
So, how do I proceed from this point? I don't know enough to understand what the problem is with this, maybe something to do with the PIT mapping? I feel like I've covered every possible avenue that I can see posted online, I'm really not sure if there is anyone else with this problem, where the Odin program is so volatile. Your thoughts would be greatly appreciated, I suffer without my phone.
Stuart
Click to expand...
Click to collapse
Happened the same too me and i have CM11 too... If you get a fix contact me please
emnt said:
Happened the same too me and i have CM11 too... If you get a fix contact me please
Click to expand...
Click to collapse
Try the above rescue firmware as suggested above make sure you know what you are doing before flashing.. Exactly same advice if that doesn't work service required partition corrupt..Also I noticed the op above also flashed wrong root file for I9300 which didn't help.
blackbeardtwenty said:
The unusual thing about this crash was that it rebooted with a fuzzy, static-like screen,
Click to expand...
Click to collapse
Hardware issue, either damaged or corrupt emmc chip.
tallman43 said:
.Also I noticed the op above also flashed wrong root file for I9300 which didn't help.
Click to expand...
Click to collapse
Yeah, that was a desperate attempt at trying another root file which was recommended in another post. I initially used:
I9300XXUGNA5_I9300AUTGNA1_I9300XXUGMK6_HOME.tar.md5
and this worked fine last month, but now I'm back to square one again. Any ideas on other PIT files or root files I can download which might do the trick?
Thanks for your comments so far, you're all a bunch of wizards...
Hello, and excuse my poor English.
I got my hands over a white S3 GT-I9300 running 4.1.2 (I9300XXELLA), the phone was suffering some annoying failures (certain built-in apps crashes after the keyboard is displayed and the phone app dial freezes after you press the call button thus the device make the call), did the wipe/data&cache, factory reset using the settings menu and OTA updates, this last one keeps saying the phone couldn't connect to check updates after several wipes/attempts.
So I followed this tutorial www[dot]android[dot]gs/install-official-xxugna8-android-4-3-jb-on-galaxy-s3-i9300/ (pretty much the same procedures as I re-flashed one of my previous phones, a Galaxy S Duos so I was kinda confident) but instead of the XXUGNA8 update I downloaded the Argentinian variant I9300UBUGNK1_I9300UVOUGNK1_ARO, followed all the steps in the tutorial and ODIN flashed successfully, the phone insta-rebooted for less than one second and stuck there (always rebooting in loop, showing the "Samsung Galaxy S3 GT-I9300" logo for less than one second), tried pulling out the battery, no luck. I can't access the recovery either but can enter in download mode. Also tried the KIES method but after asking the S/N it says "the model information that you have entered cannot be verified, the device initialization cannot proceed."
Tried to flashing it again using the same steps and files but got a NAND write error once and I stopped after that, now I am downloading the XXUGNA8 version at 50kb/s from samsung-firmware page since I started getting a 502 bad gateway error from sammobile's page.
What did I wrong? Can someone point me the necessary steps to repair this phone if there is a fix?
Here's the re-attempt log from ODIN 3.07
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300UBUGNK1_I9300UVOUGNK1_I9300UBUGNK1_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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
In download mode it appears as follows:
ODIN MODE
PRODUCT NAME: GT-I9300
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
Any help would be more than welcome.
Regards.
I'm not a robot
dckmnn said:
Hello, and excuse my poor English.
I got my hands over a white S3 GT-I9300 running 4.1.2 (I9300XXELLA), the phone was suffering some annoying failures (certain built-in apps crashes after the keyboard is displayed and the phone app dial freezes after you press the call button thus the device make the call), did the wipe/data&cache, factory reset using the settings menu and OTA updates, this last one keeps saying the phone couldn't connect to check updates after several wipes/attempts.
So I followed this tutorial www[dot]android[dot]gs/install-official-xxugna8-android-4-3-jb-on-galaxy-s3-i9300/ (pretty much the same procedures as I re-flashed one of my previous phones, a Galaxy S Duos so I was kinda confident) but instead of the XXUGNA8 update I downloaded the Argentinian variant I9300UBUGNK1_I9300UVOUGNK1_ARO, followed all the steps in the tutorial and ODIN flashed successfully, the phone insta-rebooted for less than one second and stuck there (always rebooting in loop, showing the "Samsung Galaxy S3 GT-I9300" logo for less than one second), tried pulling out the battery, no luck. I can't access the recovery either but can enter in download mode. Also tried the KIES method but after asking the S/N it says "the model information that you have entered cannot be verified, the device initialization cannot proceed."
Tried to flashing it again using the same steps and files but got a NAND write error once and I stopped after that, now I am downloading the XXUGNA8 version at 50kb/s from samsung-firmware page since I started getting a 502 bad gateway error from sammobile's page.
What did I wrong? Can someone point me the necessary steps to repair this phone if there is a fix?
Here's the re-attempt log from ODIN 3.07
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300UBUGNK1_I9300UVOUGNK1_I9300UBUGNK1_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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
In download mode it appears as follows:
ODIN MODE
PRODUCT NAME: GT-I9300
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
Any help would be more than welcome.
Regards.
Click to expand...
Click to collapse
Hey brother I also had similar problem today midnight here in india . and i also tried several methods to restore my phone.
i tried kies also but but it required full rom package to download ,as my internet speed is slow I tried other method and it worked. I am very happy now :victory:
just connect your GT-I9300 in download mode. use odin 3.07. download CF-Auto-Root-m0-m0xx-gti9300.tar.md5 file that we normally use for rooting. Select pda in odin select CF-Auto-Root-m0-m0xx-gti9300.tar.md5 and click start.
Its just recovery related problem. my entire data is there as it is in my phone.
Hit thanks If I helped you
I'll try it as soon as I can, and let you know if it worked.
For now thanks for the help!
dckmnn said:
I'll try it as soon as I can, and let you know if it worked.
For now thanks for the help!
Click to expand...
Click to collapse
I flashed back to stock yesterday after 2 years of Custom - just felt like it!!
I too got stuck on Samsung logo immedidately after my carrier logo appeared for a couple of seconds.
Tried reflashing again twice - again with Odin - same result
Then I had a thought - why not boot into recovery mode and do a factory reset . I did this, the phone rebooted and immediately it went through 'normal' set up procedure.
Worth a try.
Homer
homer timpson said:
Then I had a thought - why not boot into recovery mode and do a factory reset . I did this, the phone rebooted and immediately it went through 'normal' set up procedure.
Worth a try.
Homer
Click to expand...
Click to collapse
That though is written in the sticky's.
homer timpson said:
I flashed back to stock yesterday after 2 years of Custom - just felt like it!!
I too got stuck on Samsung logo immedidately after my carrier logo appeared for a couple of seconds.
Tried reflashing again twice - again with Odin - same result
Then I had a thought - why not boot into recovery mode and do a factory reset . I did this, the phone rebooted and immediately it went through 'normal' set up procedure.
Worth a try.
Homer
Click to expand...
Click to collapse
Sorry for the late response! The phone wasn't able to enter recovery, only download mode.
Another not robot here
[UPDATE]
I sold the phone "as is", I got it cheap and sell it almost at the same price so any mod can mark this thread as "Solved".
Easy come, easy go they say.
Regards.