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.
Related
Hey guys
I got the notification that a new update is available for my stock GT-I9300 (Vodafone New Zealand) a few days ago. When I clicked on install it complained because I was on mobile data and so I decided to wait until I am at home. But when I got within range of a wifi it must have automatically downloaded and installed the update, because the next time I pulled the device out of my pocket it was stuck at the initial boot screen.
I have since tried to do a firmware recovery through Kies, which downloaded the firmware and then failed to install it saying that it does not know the device or something along those lines (I unfortunately did not save a screenshot of the exact message). Then I tried Odin, which simply fails with the log output below. I know that this is a ROM for the UK, but I haven't found a ROM for NZ yet and thought that it might work anyway.
The status printed when I go into the recovery mode is a bit strange:
ODIN MODE
PRODUCT NAME:
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
Why is there no product name and why is the system status "custom"? I have only had the phone for three weeks and I have not rooted or flashed it yet.
Any suggestions would be much appreciated
Odin output:
<ID:0/015> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXBLFB_I9300OXABLFB_I9300XXLFB_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Get PIT for mapping..
<ID:0/015>
<ID:0/015> There is no PIT partition.
<ID:0/015> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Nuld said:
Hey guys
I got the notification that a new update is available for my stock GT-I9300 (Vodafone New Zealand) a few days ago. When I clicked on install it complained because I was on mobile data and so I decided to wait until I am at home. But when I got within range of a wifi it must have automatically downloaded and installed the update, because the next time I pulled the device out of my pocket it was stuck at the initial boot screen.
I have since tried to do a firmware recovery through Kies, which downloaded the firmware and then failed to install it saying that it does not know the device or something along those lines (I unfortunately did not save a screenshot of the exact message). Then I tried Odin, which simply fails with the log output below. I know that this is a ROM for the UK, but I haven't found a ROM for NZ yet and thought that it might work anyway.
The status printed when I go into the recovery mode is a bit strange:
ODIN MODE
PRODUCT NAME:
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
Why is there no product name and why is the system status "custom"? I have only had the phone for three weeks and I have not rooted or flashed it yet.
Any suggestions would be much appreciated
Odin output:
<ID:0/015> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXBLFB_I9300OXABLFB_I9300XXLFB_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Get PIT for mapping..
<ID:0/015>
<ID:0/015> There is no PIT partition.
<ID:0/015> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
download original firmware for galaxy i9300 and flash through odin
that will take you through
or download any rom ZerOne or foxhound they are really nice roms and flash via cwm
vegeta1 said:
download original firmware for galaxy i9300 and flash through odin
that will take you through
or download any rom ZerOne or foxhound they are really nice roms and flash via cwm
Click to expand...
Click to collapse
I am trying to install the original firmware through Odin, but I always get the error message shown at the end of my original post. When I try it a second time directly after it failed, then it does not complain about the PIT but instead fails to connect to the COM port:
<ID:0/011> SetupConnection..
<ID:0/011> Can't open the serial(COM) port.
<ID:0/011> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
I have gone through the process of taking out the battery, reinserting it, going into download mode, connecting it to all USB ports on my laptop and trying to flash several times now, always with the same result
I am currently downloading another ROM (I9300XXALF6_I9300ITVALF1_ITV). Maybe that'll work...?
Nuld said:
I am trying to install the original firmware through Odin, but I always get the error message shown at the end of my original post. When I try it a second time directly after it failed, then it does not complain about the PIT but instead fails to connect to the COM port:
<ID:0/011> SetupConnection..
<ID:0/011> Can't open the serial(COM) port.
<ID:0/011> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
I have gone through the process of taking out the battery, reinserting it, going into download mode, connecting it to all USB ports on my laptop and trying to flash several times now, always with the same result
I am currently downloading another ROM (I9300XXALF6_I9300ITVALF1_ITV). Maybe that'll work...?
Click to expand...
Click to collapse
Doesn't look like your computer found your phone, remove/reinstall the USB drivers. You can use KIES, click troubleshoot connection, it will reinstall them.
Hope that helps,
-CC
P.S> Make sure ODIN is not open when you run KIES and make sure KIES isn't open when you run ODIN.
clockcycle said:
Doesn't look like your computer found your phone, remove/reinstall the USB drivers. You can use KIES, click troubleshoot connection, it will reinstall them.
Hope that helps,
-CC
P.S> Make sure ODIN is not open when you run KIES and make sure KIES isn't open when you run ODIN.
Click to expand...
Click to collapse
Odin says "<ID:0/011> Added!!" (or some other port of course) whenever I connect the phone, doesn't that mean that it detected the phone?
I actually did the troubleshoot connection in Kies yesterday and it reinstalled the driver. I have since removed Kies (not the driver) from my computer, as I thought that this might be the reason why Odin fails.
Ok I am getting really desperate, I have spent a large part of the weekend trying to get this to work and still no luck. Any further suggestions would be highly appreciated
I have re-installed the USB driver a few times now and Kies is not installed to make sure that there are no conflicts between ODIN/Kies. I have also found a ROM for Vodafone NZ (I9300XXALE8_I9300VNZALE4_VNZ) which is where I got the phone.
ODIN detects when I plug the phone into my computer, but fails with the following:
<ID:0/011> Get PIT for mapping..
<ID:0/011>
<ID:0/011> There is no PIT partition.
<ID:0/011> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
What is the cause for this error and do I need a PIT file and do a re-partition to fix it?
Is it normal that when in download mode, the product name shown on the phone screen is empty?
Thanks!
Your partition table is corrupted. No point trying to fix.
Quickly send to samsung to reflash your phone.
So there is no way I can fix this myself (without risking to make things worse)?
I am not a happy Samsung customer right now, all this time wasted because I installed an official over the air update and who knows how long it'll take to get it fixed...
Thanks for your replies.
Nuld said:
So there is no way I can fix this myself (without risking to make things worse)?
I am not a happy Samsung customer right now, all this time wasted because I installed an official over the air update and who knows how long it'll take to get it fixed...
Thanks for your replies.
Click to expand...
Click to collapse
You are in a position now where further repairs by yourself are even more likely to end up with no warranty .
Phone broke during official update return under warranty .
Flashing other firmwares risks invalidating warranty .
jje
guys i have rooted galaxy s3 i was trying to instal chainfire 3d to my phone just installed and pushed the button that says install driver and restart it istalled drivier and restarted but phone stucks at galaxy s3 logo how can i go to recovery whiout opening the phone so i can flash new rom or something help me out please i am flashing recovery to phone but cant open it
archeuscaine said:
guys i have rooted galaxy s3 i was trying to instal chainfire 3d to my phone just installed and pushed the button that says install driver and restart it istalled drivier and restarted but phone stucks at galaxy s3 logo how can i go to recovery whiout opening the phone so i can flash new rom or something help me out please i am flashing recovery to phone but cant open it
Click to expand...
Click to collapse
Off the phone. Then press power button + volume up + home button
Sent from my GT-I9300 using xda app-developers app
Dear all there is a good news for all of you about SIII product name blank now it can be consider under warranty as Samsung policy.
I have never rooted my phone, always used official updates. Upgraded to Android 4.1.1 last night and after few hours my phone just stuck wiht the "Samsung Galaxy S3 startup logo". The phone wont reboot at all. I tryed to factory reset (volume up + home + power), wont work.. one time it tryed to do something and failed. I can boot to odin download menu and i tryed to reset to official stock firmare and it says something about partition corrupted or broken. After that i tryed again with the new partition option, it failed again. Is there anything i can do to get this phone working again?
aeinola said:
I have never rooted my phone, always used official updates. Upgraded to Android 4.1.1 last night and after few hours my phone just stuck wiht the "Samsung Galaxy S3 startup logo". The phone wont reboot at all. I tryed to factory reset (volume up + home + power), wont work.. one time it tryed to do something and failed. I can boot to odin download menu and i tryed to reset to official stock firmare and it says something about partition corrupted or broken. After that i tryed again with the new partition option, it failed again. Is there anything i can do to get this phone working again?
Click to expand...
Click to collapse
Send it back for repair if you've never routed or anything. It can likely be fixed by routing and whatnot but if you've never done it, why risk it.
Parva4 said:
Send it back for repair if you've never routed or anything. It can likely be fixed by routing and whatnot but if you've never done it, why risk it.
Click to expand...
Click to collapse
Send it for repairs and wait for several weeks to get it back? Very tempting. :cyclops: Lets call that plan B.
If i can do something to wake this baby up today or tomorrow i'll take it.
It sounds like you somehow softbricked your phone without even rooting it lol.
Anyway, if you can go into ODIN download mode, you might wanna try rooting the phone to see if it works. Cos once the phone's rooted, you can easily flash a stock ROM to save it. If you're worried about voiding the warranty, you can unroot the phone after everything's done.
Instructions for unrooting: http://galaxys3root.com/galaxy-s3-unroot/how-to-unroot-galaxy-s3-i9300/
Hope this helps!
chunghanjie92 said:
IAnyway, if you can go into ODIN download mode, you might wanna try rooting the phone to see if it works. Cos once the phone's rooted, you can easily flash a stock ROM to save it. If you're worried about voiding the warranty, you can unroot the phone after everything's done.
Click to expand...
Click to collapse
I did try that and it did not work. Maybe i did something wrong? Dont know... Im pretty sure the problem is with broken partition. I had the Auto Reboot, Re-Partition and F. Reset Time checked. Got file for PIT and got file for PDA. It just wont work. Odin says every time FAILED!
Do not use pit or repartition unless you know what you are doing.
jje
Sent from my GT-I9300 using xda premium
aeinola said:
I had the Auto Reboot, Re-Partition and F. Reset Time checked. Got file for PIT and got file for PDA. It just wont work. Odin says every time FAILED!
Click to expand...
Click to collapse
NEVER CHECK RE-PARTITION trololololo .... and never use PIT unless you are know what you doing.
Wow! These "never use PIT unless you are know what you doing"-comments are really helpful. Thank you guys! :good:
Follow the instructions on this site:
http://galaxys3root.com/galaxy-s3-root/how-to-root-galaxy-s3/
The site tells you how to root a phone (look at the picture to see what you need/don't need to check; usually all you need to check is Auto-Reboot and nothing else)
After the phone's rooted you can download a ROM from this site http://samsung-updates.com/device/?id=GT-I9300 and flash it into the phone using the same method you flashed the file to root your phone
Thanks for the help. Odin says: "There is no PIT partition" and FAILS.
So i NEED to Re-Partition, any help would be appreciated.
I try to Re-Partition and here is what Odin says:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9300XXBLH1_I9300OLBBLH1_I9300DXLH1_ROOT_DEODEX.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
The files (including mx.pit) is from these forums. What should i do?
aeinola said:
I try to Re-Partition and here is what Odin says:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9300XXBLH1_I9300OLBBLH1_I9300DXLH1_ROOT_DEODEX.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
The files (including mx.pit) is from these forums. What should i do?
Click to expand...
Click to collapse
Same thing for me, and I'm stuck with this problem for 2 months now!!!
I read that for some reason unknown, some S3 got these fuc*** motherboards!!!
If u can solve this without samsung service center, please post!!!:good:
Of course you can manage it without Samsng Service center, if you want.
The procedure is:
1. download to PC the I9300 Service Manual;
2. buy motherboard;
3. replace it by yourself.
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.
My phone: SPH-L710 Sprint Galaxy S3
This is what my ODIN says after trying to flash with stock ROM.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L710VPUCMK3_L710SPRCMK3_L710VPUCMK3_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> aboot.mbn
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
This is what is on the top left corner in the DL mode.
"ODIN MODE
PRODUCT NAME: SPH-L710.
CUSTOM BINARY:Custom
SYSTEM STATUS:Custom
QUALCOM SECUREBOOT: ENABLE
Warranty Bit: 1
Bootloader AP SWAEV: 2
SW REV CHECK FAIL : Fused 2 > Binary 1"
Here's my story:
My phone was displaying "No error" in Google Play Store. So I factory reset my phone but it didn't resolve my problem. So I flashed a stock ROM and it failed. My device was 4.4.2 ROOTED before flashing a lower version. (Cannot remember the version number though.) Now it displays, "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again." My phone, however, DOES go into Download mode but not the recovery mode. I tried to flash multiple times but ODIN kept on failing. I tried multiple USB cables, different USB ports, computers, and reinstalled USB drivers, etc. However ODIN keeps on failing. I tried to recover it through KIES but it will not detect my device. I am thinking about sending this into Mobiletechvideos.com but I heard some devices could not be restored because of EMMC failure. Do you think my device's emmc failed? (I spent 200 bucks on this and do not wanna buy another one )
Soooo..
Is there anything I can do before I send it into mobiletechvideos.com for 50 bucks?
I've tried this http://forum.xda-developers.com/showthread.php?t=1840030 but it didn't work because I couldn't find Sprint bootchain. Does anyone have one for Sprint?
I'm also trying to use this method http://forum.xda-developers.com/showthread.php?t=2369125 but do you think it will work? (I don't have a SD card so I can't try just yet.) It was meant for hardbricked people. But mine is not completely bricked. It turns on and goes into DL mode.
** I've just noticed some signs of hardbrick. WITHOUT my battery and I hook my phone up to my PC with a USB cable, it shows that Red LED light and vibrates. Doesn't turn on though. WITH the battery, it turns on and goes into DL mode. Is my phone hard bricked?**
SUMMARIZED QUESTIONS:
1) Is my phone hard bricked?
2) Do you think JTAG can fix my phone? My phone may be in Read only state. Wouldn't that prevent the JTAG method?
3) Will the SD card method work?
4) Does anyone have Sprint bootchain? (I think my phone might be at Read Only state)
5) What are some signs of EMMC failure? I would really hate it if my phone had EMMC failure -_-
6) Did my phone brick because my phone was rooted and I flashed unrooted Sprint Stock ROM?
PLEASE PLEASE help me. Donations will be considered! (Really, I'm desperate to get my phone fixed. T_T )
Thank you alot in advance. Please leave replies if you need more information.
You have posted in the wrong forum, anything you flash from here will hard brick it.
Report your own post and ask a moderator to move it for you.
Fail at nand write is usually a dead emmc chip, try flashing full firmware with a pit as last resort.
As long as you can get into D/L mode, then you're fine. If you can get into D/L mode and your phone can turn on, it isn't hardbricked.
Try using this file (in case you're wondering, it's the 4.4.2 stock ROM). If it doesn't work on Odin 3.xx, try using it on Odin 1.85. I had the same problem, too.
Sent from my SPH-L710 using XDA Free mobile app
Hi All,
I recently got a S3 GT-I9300 from a friend. This was bought from some Romanian provider, so I believe it is the International version. The phone came with already rooted and had CM10 installed. Unfortunately, is not a firmware I enjoy using so, I wanted to install MIUI.
I managed to get MIUI to install and was using it. However, the phone crashed and reset the phone by taking battery out and putting back in.
Problems:
1) Phone does not boot anymore
2) Phone Shows Samsung Galaxy S3 logo and stays on the screen
3) I am unsure what version of the firmware I should be restoring to
4) Phone can boot into download mode but does not show the product name. Here is what I see:
[*]ODIN MODE
PRODUCT NAME: <blank>
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
Fixes tried so far:
1) PDA - and choosing the latest firmware download - I9300XXUGNB4_I9300NZCGNB1_I9300XXUGNB1_HOME.tar.md5 - ODIN gets stuck on: <ID:0/004> SetupConnection..
Is there anything I have missed?
Cheers.
Fiddlestix said:
Hi All,
I recently got a S3 GT-I9300 from a friend. This was bought from some Romanian provider, so I believe it is the International version. The phone came with already rooted and had CM10 installed. Unfortunately, is not a firmware I enjoy using so, I wanted to install MIUI.
I managed to get MIUI to install and was using it. However, the phone crashed and reset the phone by taking battery out and putting back in.
Problems:
1) Phone does not boot anymore
2) Phone Shows Samsung Galaxy S3 logo and stays on the screen
3) I am unsure what version of the firmware I should be restoring to
4) Phone can boot into download mode but does not show the product name. Here is what I see:
[*]ODIN MODE
PRODUCT NAME: <blank>
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
Fixes tried so far:
1) PDA - and choosing the latest firmware download - I9300XXUGNB4_I9300NZCGNB1_I9300XXUGNB1_HOME.tar.md5 - ODIN gets stuck on: <ID:0/004> SetupConnection..
Is there anything I have missed?
Cheers.
Click to expand...
Click to collapse
After selection of PDA wait for at least 4-5 minutes sometimes it requires some time to load and make sure you are using ODIN v3.09
anish100 said:
After selection of PDA wait for at least 4-5 minutes sometimes it requires some time to load and make sure you are using ODIN v3.09
Click to expand...
Click to collapse
hmmm I have done that before, still no fix. I left it running for the whole night. Just hung there doing nothing
Fiddlestix said:
hmmm I have done that before, still no fix. I left it running for the whole night. Just hung there doing nothing
Click to expand...
Click to collapse
Try emergency recovery software >> http://forum.xda-developers.com/showpost.php?p=30087735 << if that fails service repair (product name blank)
I think the problem is, is that ODIN is not actually talking to the phone. While the phone can be made to enter download mode, I believe the phone may have been re-partitioned and everything; as in the phone partition table has been deleted/updated/screw up some how.
I have tried, on numerous occasions to try and full-flash the phone but it has not worked. Will give this a try and update with findings.
Edit 1:
So I downloaded the package from your suggestion and just tried to flash the bootloader. Got an instant fail with:
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9300XXUGMJ9_1902166_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Cheers.
any other suggestions guys?