Google Play Music Customizations – XDA Xposed Tuesday

If Cyanogen Inc. has its way, you won’t be forced into the Google … more

Sony Xperia Z3 Lollipop Framework Ported to CM12

Android 5.0 for Xperia has a unique look and feel. You don’t have to get a Sony … more

Do You Use Recents as a Task Switcher?

Google introduced a revamped Recents interface with Lollipop in the hopes of making it easier for … more

YU Yureka All-in-One ToolBox (CM12S Only)

This packed toolbox by XDA Senior Member gohel.vishal makes many useful tweaks … more
Post Reply Subscribe to Thread Email Thread

[Q] Bricked S3 i9300

8th July 2014, 11:28 PM |#1  
OP Junior Member
Thanks Meter: 0
 
2 posts
Join Date:Joined: Jul 2014
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.m d5), 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
 
 
9th July 2014, 02:47 AM |#2  
tallman43's Avatar
Senior Member
Flag The Land of Android
Thanks Meter: 416
 
1,317 posts
Join Date:Joined: Aug 2011
More
Quote:
Originally Posted by blackbeardtwenty

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.m d5), 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

Use this if it fails it needs service repair >> http://forum.xda-developers.com/show...35&postcount=6 <<
9th July 2014, 03:37 PM |#3  
Junior Member
Thanks Meter: 0
 
2 posts
Join Date:Joined: Jul 2014
Quote:
Originally Posted by blackbeardtwenty

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.m d5), 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

Happened the same too me and i have CM11 too... If you get a fix contact me please
9th July 2014, 04:27 PM |#4  
tallman43's Avatar
Senior Member
Flag The Land of Android
Thanks Meter: 416
 
1,317 posts
Join Date:Joined: Aug 2011
More
Quote:
Originally Posted by emnt

Happened the same too me and i have CM11 too... If you get a fix contact me please

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.
9th July 2014, 06:04 PM |#5  
boomboomer's Avatar
Senior Member
Thanks Meter: 803
 
3,752 posts
Join Date:Joined: Jun 2010
Quote:
Originally Posted by blackbeardtwenty

The unusual thing about this crash was that it rebooted with a fuzzy, static-like screen,

Hardware issue, either damaged or corrupt emmc chip.
9th July 2014, 07:43 PM |#6  
OP Junior Member
Thanks Meter: 0
 
2 posts
Join Date:Joined: Jul 2014
Quote:
Originally Posted by tallman43

.Also I noticed the op above also flashed wrong root file for I9300 which didn't help.

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.md 5

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...
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes