Greetings,
Right away, sorry if I'm posting this in the wrong spot.
My story:
One of my friends was about to throw away his tablet because of the "Firmware upgrade encountered an issue" problem. He took it to a "repair shop", they tried restoring the tablet with Kies and Smart Switch. They couldn't get it to work, so he gave it to me.
Kies does not detect the tablet.
Odin DOES detect the tablet, but flashing fails.
I've tried flashing absolutely anything I could find (apart from a custom rom, couldn't find one I could flash with odin).
I CANNOT flash ANYTHING with odin. Sometimes it fails on NAND write, other times it appears like the flash was successful because it says RESET in odin and the tablet turns off, but after turning it back on it goes right back to the "Firmware upgrade encountered an issue" screen.
The USB drivers are OK.
I've tried all ODIN version I could find from 1.85 to 3.11.1.
I CANNOT boot to recovery or download mode (if I could there wouldn't be a problem).
What could be wrong with it? What can I try to fix it? I'll try to list all of the things I tried to flash but forgive me if I forget some (there have been QUITE a few over the past 3 days of trying).
What I've tried to flash:
CF-Auto-Root-espresso10rf-espresso10rfxx-gtp5100
Clockworkmod_Recovery_for_P5100
espresso-any-root-kernel.v2.tar.md5
p5100-recovery.tar.md5
P5100XXAOF1_P5100BTUAOF1_BTU (stock rom region GB I think)
P5100XXDNA1_P5100NEEDNA1_NEE ([Pays Nordiques] 4.2
recovery-cache-fix.tar
philz_touch_6.03.8-jfltexx.tar.md5
CWM-root-P5100-v1
I've also tried flashing with PIT files:
gt-p5100_signed_espresso_20120220_16G
I've also tried to flash with NAND erase all (after everything else failed). That failed also.
I have no idea what else I can try.
I get this when I try to flash a stock rom:
<ID:0/007> Removed!!
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P5100XWALD7_P5100OXXALD9_P5100XXLD7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> system.img
<ID:0/007> NAND Write Start!!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any help would be GREATLY appreciated.
UPDATE:
I tried flashing P5100XXALD6_OXEALD5_v4.0.3_Repair_Firmware, it looked like it was going to succeed, but then the tablet powered off and now it doesn't turn on at all, not even to the "Firmware upgrade encountered an issue" screen. The battery only charges to 3.75 volts and then stops (measured with a multimeter). I tried removing the battery, completely discharging the circuitry (it was still showing 0.5 volts on the board after disconnecting the battery from the tablet). It didn't help. The tablet "turns on" just enough for my PC to play the USB CONNECTED sound, but the screen doesn't power on and it shuts down immediately (1 second in between the USB CONNECTED and USB DISCONNECTED sounds on the pc).
Did you manage to find a solution?
Related
Hi forum,
I'm having big problems with my galaxy tab 10.1 p7510. I was transferring files from my pc to the tab, the tab stop responding, I pulled the usb cable (big mistake). After that the tab wouldn't boot. Went into android recovery and wiped cache, some errors appeared and I wasn't able to turn on the tab for about a day. I held down the power button for a really long time and it went into a boot loop. Was able to get into recovery again, wiped cache again; since then I couldn't get into recovery any longer. But, I have been able to get into download mode. I downloaded the latest ROM (and the one before it) from sammobile.com; tried flashing both using odin 1.83, 1.85, and 1.87. Tried two different computers and various usb ports for each computer. installed drivers and kies, made sure kies was disabled when attempting flash. Result is always the same:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P7510XABLPL_P7510UELPL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.img
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I really don't know what else to do.
Should note, when i power off and power on, some red text appears quick (can't see it) and it automatically goes into download mode. At the top it says, "reason no kernel"
Please help!
Jim
focusbob said:
I was transferring files from my pc to the tab, the tab stop responding, I pulled the usb cable (big mistake). After that the tab wouldn't boot.
Click to expand...
Click to collapse
What exactly were you transferring? Were you flashing a new ROM, restoring a backup or adding an update?
No, I was just transferring videos from pc to tab via usb. It froze, but I think it was when I tried to clear cache in android recovery that things went down hill. There are some known problems with factory resets with galaxy tabs due to a faulty chip. Maybe it was that? who knows. I actually was able to get Samsung to take it in on warranty (though it's past warranty). So, that's the end of that...
focusbob said:
I actually was able to get Samsung to take it in on warranty (though it's past warranty). So, that's the end of that...
Click to expand...
Click to collapse
In that case, congratulations and better luck next time.
I was using the MIUI rom and I sold the phone. To deliver to the buyer I decided to go back to the stock rom but forgot to wipe and now I have the following situation:
- I can only get into download mode
- Odin recognizes the phone
- I tried to repartition the Odin reported successful operation (my model is 16gb)
- Tried to put other roms on the phone including those downloaded from the site sammobile, selecting only auto-reboot and f.reset.time
- With these steps could only get stuck in "nand write start ..."
- Tried installing kies but do not believe it can be something with the drivers because the odin recognizes the phone.
I read many posts but after two days decedi post to see if anyone would help me solve this issue
I'll be waiting for directions on how to proceed without worsening the scenario.
Odin log:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300UBBLG2_I9300VILG1_I9300ZVVBLG1_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..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> modem.bin
<ID:0/006> NAND Write Start!!
have you tried restarting your computer or using another computer? or even a different usb port or cable?
ages ago I had a similar problem - never moved beyond the start point - simple restart solved it for me...no idea if that's the same situation as you.
Just throwing out ideas here; otherwise I'm not sure.
Sent from my GT-I9300 using Tapatalk 2
Tried to do this, but still stucked at nand write start...
One thing I noticed is that the progress bar on the phone at the "downloading mode screen" runs quickly, and then it stops at nand write start.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300UBBLG2_I9300VILG1_I9300ZVVBLG1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> modem.bin
<ID:0/005> NAND Write Start!!
At least I'm not alone
I have the exact same problem you have. Intl i9300, cannot enter recovery, only download mode. Flashing 16gb pit file works ok, however attempting to flash Stock rom gets stuck at Nand Write Start. Not sure what to do now, I guess I'll wait for responses here as well.
RePartition .
Fail Nand write .
Assuming you have read and are following the basics re an Odin flash ( if not go and read them ) .
This sounds in both cases like a damaged Nand >>> service centre job .
jje
I've not done much to my S3. Trouble started when I decided to install an OTA of Foxhound 1.8. Installation completed successfully but during the application upgrade (...you know the first boot message of 'Android is updating x of 365 apps). It froze and stuck there for like 15min so I decided to reboot it and all hell broke loose.
Started with 'Foxhound cannot mount recovery command..' etc. Which made me decide to flash my 16gb pit file, and since then all attempts to flash back to stock stall at 'Nand write start'.
I have backups of everything, even my efs. Problem is I can't even get to recovery to restore anything.
I'll keep trying I guess, worst case I'll just return it back to Samsung.
pull usb devices except s3 and be sure to have correct drivers then try again. you may even try it on another pc of course with installing drivers. if none of them works try flashing a kernel or recovery if it flashes then try to flash stock rom.if stucks again at nand write there may be a problem at emmc sect. but dont worry just do what i said if it fails there should be a solution
if you can enter the recovery mode u should be happy
to kamau can u send me the pit file you flashed thanks
zhjackss said:
to kamau can u send me the pit file you flashed thanks
Click to expand...
Click to collapse
There it is. I"m now working on resetting the flash counter from odin since I obviously can't install triangle away in preparation of returning it to samsung.
I rooted my phone about 1.5 years ago when I got it. I remember I installed a custom ROM (can't remember which right now for sure - possibly omega?) and kernel (siyah) .. I'm not sure if that matters? I know I had clockworkmod installed.
Phone's worked fine for ages. Today it randomly crashed playing a youtube video and got stuck in a boot loop. On a couple of occasions it came up with a welcome/start screen as if it was a brand new stock s3 but then booted again.
It kept coming up with the b&w samsung galaxy s3. That's it, it'd sometimes turn off and on, same thing again.
I can't get it to go into recovery mode. It happened once or twice very briefly, but then just rebooted again.
I got it in download mode. I tried recovering using KIES but it failed. Tried using ODIN and a stock s3 ROM and it failed. Tried using ODIN with a "nowipe" root ROM and odin hung.
Now if I try to turn it on without download mode it just says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
Can anyone give me any suggestions/help? Am I screwed, is it permanently bricked?
jeemer said:
I rooted my phone about 1.5 years ago when I got it. I remember I installed a custom ROM (can't remember which right now for sure - possibly omega?) and kernel (siyah) .. I'm not sure if that matters? I know I had clockworkmod installed.
Phone's worked fine for ages. Today it randomly crashed playing a youtube video and got stuck in a boot loop. On a couple of occasions it came up with a welcome/start screen as if it was a brand new stock s3 but then booted again.
It kept coming up with the b&w samsung galaxy s3. That's it, it'd sometimes turn off and on, same thing again.
I can't get it to go into recovery mode. It happened once or twice very briefly, but then just rebooted again.
I got it in download mode. I tried recovering using KIES but it failed. Tried using ODIN and a stock s3 ROM and it failed. Tried using ODIN with a "nowipe" root ROM and odin hung.
Now if I try to turn it on without download mode it just says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
Can anyone give me any suggestions/help? Am I screwed, is it permanently bricked?
Click to expand...
Click to collapse
have a look here, maybe same challenge you are facing (I just flew over the thread).
I tried a few other things since.
Using Odin I tried flashing a stock ROM, after ending the Kies process and using a different USB. It all said it had worked, gave me a boot screen and said android is upgrading - optimising apps. It hung doing this at 10 of 70 or something. I tried resetting and it hung at 5 of 70, and when i reset again it just wouldn't get past that.
Tried flashing with a more recent stock ROM using Odin 1.3 as above, but it hung at system.img
Tried flashing with the more recent stock ROM using the latest Odin. The blue bar counted right up to full on my screen, then the phone reset.
It was sitting with the little 3d android character with the spinning 3d mesh sphere in his stomach. A blue line started counting up but has frozen about maybe 25% of the way along. After a short while Odin said PASS! and it all seems to have completed according to Odin
The android graphic was still spinning but nothing else was happening, the blue line would not progress any further.
After a few minutes the phone screen went black, and came up with the black and white Samsung Galaxy SIII screen for a second or so. Then it just went black again.
Here is the Odin log
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXELL4_I9300O2UELL1_I9300BWELK1_HOME.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> Firmware update start..
<ID:0/004> system.img
<ID:0/004> NAND Write Start!!
<ID:0/004> boot.img
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> recovery.img
<ID:0/004> modem.bin
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
When I turn it on now the same thing happens - the black and white Samsung Galaxy SIII screen comes on for a second or so and then the screen goes black.
If I try and put it in recovery mode the same thing happens. If I try to put it in download mode, that works.
Am I right in thinking I still have a hope to save it here since Odin still sees it? What do I try now? :/
http://forum.xda-developers.com/showthread.php?t=1840030
this is the only other suggestion I've found so far and it seems quite scary!
Flash a full stock rom using latest odin, immediately boot into recovery and factory reset.
Because you left the phone for so long on a firmware that was not SDS safe you may have nand memory damage, even if the file structure is still intact.
Sent from my GT-I9300 using Tapatalk
I tried doing a full flash again with the older stock firmware I started with. Got right through the whole process again, says it passed and it hung at the Android guy with the spinning mesh sphere.
I've never managed to get it into recovery mode since i got it in clockwork recovery mode a couple of occasions last night and it reset each time
Any suggestions as to what I could try to get it past this stage?
If it looks like I have nand memory damage would it be worth trying what's in that "scary" link i posted? :/
I tried flashing again to see if I could instantly get it into recovery and it failed for the first time
Here is the log
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXDLIH_I9300O2UDLI3_I9300BWDLI1_HOME.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> Firmware update start..
<ID:0/004> system.img
<ID:0/004> NAND Write Start!!
<ID:0/004> boot.img
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> recovery.img
<ID:0/004> modem.bin
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXELL4_I9300O2UELL1_I9300BWELK1_HOME.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> Firmware update start..
<ID:0/004> system.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
I'm guessing this is a nand issue then? Is my only option at that point the link above (http://forum.xda-developers.com/showthread.php?t=1840030) ?
really don't get it.. tried it again and this time the whole process passed according to odin
same again though, android guy with spinning mesh... nothing for a while
phone eventually goes black, resets, samsung galaxy s3 in black and white. goes black. if i leave it for a while that screen will come up again, then it'll go black etc.
do i bite the bullet and try that method that involves nand reset all? please advise i'm in a bit of a pickle here as i'm in the middle of interviewing for jobs so i could use my phone.. do need to try and fix this asap if i can...
You can try flashing the rescue firmware, search in general forum, but if that doesn't work then you need a new motherboard.
Sent from my GT-I9300 using Tapatalk
ok - that seems to be this one for the s3 - http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6
that look right?
downloading now. fingers crossed, thanks for your help i really do appreciate it.
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...