[Completed] Samsung Galaxy Grand Prime SM-S920L Soft Brick - XDA Assist
I've been trying for more than 2 weeks now to get my phone back to working condition, I finally decided to just register and ask, maybe I'll get lucky right?...
So, I've been using all kinds of threads found mainly on this site thus far. A few from other sites but mainly here, it seems like the trusted place online for this kind of stuff. I had rooted my phone without much knowledge prior to doing so, and was very careful with it after root. Then one dark day... I was uninstalling something and hit cancel. From there, my troubles began. Soft bricked, freezes at logo.
https://forum.xda-developers.com/gr...files-sm-s920l-straight-talk-verizon-t3411688
This thread here is the last place I was looking to fix my phone, but just couldn't get it to work. Finally got my phone to at least show up in odin, I'm pretty sure that's only because I fired up a virtual PC which installed win. 7 drivers (The OS I wanted to emulate so I could see my phone again). I didn't have to actually install the OS on my virtual PC, the simple installation of the program and the win7 setup (I'm pretty sure at least) made my phone recognizable by odin. Here are the details:
On Downloading Screen -
Odin Mode
Product Name: SM-S920L
Current Binary: Samsung Official
System Status: Custom
Reactivation Lock(kk): On
Qualcomm Secureboot: Enable (CSB)
RP SWREV: S1, T1, H1, R1, A1, P1
Secure Download: Enabled
Secure Check Fail: Boot (Has changed many times, I've seen system, recovery, and boot so far. I usually don't pay attention though, so possibly more)
With Odin using files from the above thread and other threads, the furthest I have gotten was with a combination of files in the above thread. It actually started writting, but then failed. Generally doesn't get that far.
Here are several attempts I've made in the last half hour
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> boot.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> system.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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Removed!!
<ID:0/003> Added!!
<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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<OSM> All threads completed. (succeed 0 / failed 0)
<OSM> All threads completed. (succeed 0 / failed 0)
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/003> Removed!!
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/003> Added!!
<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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> system.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> stock.sm-s920l.recovery.tar.md5 is invalid.
<OSM> End...
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have the ability to start the phone with options to use system recovery, clear cach, etc. Actually, it's probably smarter to just restart my phone and list my options so you know exactly what is showing.. Before I do, I sometimes leave the SIM card in, sometimes have it out. Doesn't seem to make a difference.
Reboot System Now
Apply Update from ADB
Apply update from external storage
Apply update from Cache
wipe data/factory reset
wipe cache partition
reboot to bootloader
power down
view recovery logs
I've tried nearly every combination of things I could think of, and it remains the same. I've read several threads saying my problem is the reactivation lock, yet most of those threads had someone saying they fixed theirs in some unique way. If anyone at all knows step by step what I need to do, please please let me know. I'm running a windows 8.1 (Recently upgraded from win. 8 with several notable problems (missing system files/drivers))
Thank you in advance! If any extra info is needed, please let me know. Please keep in mind that until I soft bricked my phone, the most I knew about phones beyond your typical user was that rooting existed, and the stuff you could use/do after rooting was awesome, until I accidentally hit cancel.
(Almost forgot to mention, my wife has exact same phone/model as I do. Can something be done knowing that? I just, can't do anything that would risk her phone's operating condition)
I don't know how! But I think I got a little further!
<ID:1/003> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:1/003> Odin v.3 engine (ID:3)..
<ID:0/004> File analysis..
<ID:1/003> File analysis..
<ID:0/004> SetupConnection..
<ID:1/003> SetupConnection..
<ID:1/003> Initialzation..
<ID:1/003> Get PIT for mapping..
<ID:1/003> Firmware update start..
<ID:1/003> system.img.ext4
<ID:1/003> NAND Write Start!!
<ID:1/003> Transmission Complete..
<ID:1/003> Now Writing.. Please wait about 2 minutes
<ID:1/003> Receive Response from boot-loader
<ID:1/003> FAIL! (Auth)
<ID:0/004> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 2)
<ID:1/003> Removed!!
<ID:0/004> Added!!
I feel like I'm talking to myself but oh well, if someone see's this and knows how to help, worth it. I think I made more headway (think).
<ID:0/004> Removed!!
<ID:0/003> Added!!
<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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Now I need to learn more about the pit file (I think I read it had something to do with partitioning the phone correctly) but not sure where to look for this file
I've now downloaded Android Studio, in case that opens my options for me
Hi !
I`m not much knowledgeable into samsung Odin unbrick methods but what I can suggest first is to perform all the Odin commands on a clean installed windows system
Sometimes failures occurs from window`s side and Odin won`t tell you that , it will just say "fail"
Don`t use emulated operating systems , some commands aren`t recognized on virtual systems
And no , other similar device won`t help you , the only files you can use are those officially provided by manufacturer
Also be sure you use an original usb data transfer cable
Good luck !
I'm very sure. My wifes phone, again same exact phone to the model, connects to the computer just fine. Also, I'm not trying to do anything at all from a virtual PC. That initially was my plan, but then upon setting up the vpc, windows 10 started recognizing my devices. I believe that has something to do with the files installed to run the old drivers supporting windows 7. Either way, I don't even launch the virtual pc app anymore yet alone run it. I have aquired so many files now that people, here and there, have made available for my phone. Recently I read that it's possible Odin can't install then because those files came from the same phone but different country, and I guess cross country sharing of these kinds of files was restricted somehow. Lately I've been attempting to understand flashboot and android studios. Flashboot is over my head, ever so slightly. Studios is way over my head. I somehow, no clue how I did it, sideloaded (I think it's called) something from studio to my phone. Don't know what it was, didn't help, seemingly hasn't hurt either. No change. I feel this has a solution, I just don't know how to come about it. I've scoured these forums, there is a stock kernal in one of these threads, along with a I believe a stock recovery. Don't know how to go about flashing them. I'm way too new at this. I've been to tutorials, guides, taken leaps of faith on not so sure about this flashes (which didn't matter because I havn't successfully flashed a single thing with Oden, the phone is in the exact same state as when it first started freezing on tracphone screen. Sadly, I feel like unless someone gives me instructions a toddler could understand fixing my problem, or remote assists me, I am not going to have a phone for a long time Take a look at how much **** I've accumulated lol. Odd, screenshot is not working. There are min. 50 files, some duplicates that I wanted in certain, multiple folders. Programs for flashing and recovering. Files for my phone. There's just so much lol.
Related
Soft brick
Phone will not boot anything but stock recovery, trying .pit and EE4 fails in Odin <ID:0/003> Added!! <OSM> Enter CS for MD5.. <OSM> Check MD5.. Do not unplug the cable.. <OSM> Please wait.. <OSM> CI510_VZW_EE4_ALL_ONE-LTE-CP_REV03_user_CL1014954.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> boot.bin <ID:0/003> <ID:0/003> Complete(Write) operation failed. <ID:0/003> Removed!! <OSM> All threads completed. (succeed 0 / failed 1)
We need a little more information than that. What version were you on before (EP4, FP1, etc.)? Were you on RFS or EXT4? Was your phone soft bricked before this happened and if so why?
Some basics, is the battery in while trying to Odin, is it charged? Also try plugging in putting phone in download mode, putting battery back in then flash. Finally if that didn't work pull battery and leave for a little then retry Sent from Tyler`s Tweaked Charge
[Q] Quick Help please
Hi Below is the error I am getting while flashing the N8000 <ID:0/003> Added!! <OSM> Enter CS for MD5.. <OSM> Check MD5.. Do not unplug the cable.. <OSM> Please wait.. <OSM> KIES_HOME_N8000DDBLL2_N8000ODDBLL2_541027_REV00_user_low_ship.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> boot.img <ID:0/003> NAND Write Start!! <ID:0/003> recovery.img <ID:0/003> system.img <ID:0/003> modem.bin <ID:0/003> <ID:0/003> Complete(Write) operation failed. <OSM> All threads completed. (succeed 0 / failed 1) There is then a big red fail box and nothing else happens. During this whole process (about a minute) the screen on the note doesn't change at all. The file I used in the PDA box is as follows: KIES_HOME_N8000DDBLL2_N8000ODDBLL2_541027_REV00_user_low_ship.tar.md5, only the Auto reboot, F reset and PDA were selected. Please help
Usual if firmware file is faulty or the wrong format . jje
It is fixed now.I will write small tutorial over this .. Its like everywhere its written but nowhere solution is given ...I will start a new thread to discuss step by step fix ...
[Q&A] [ODIN][UCLB3] UCLB3 Unbrick - Return to stock - Working PIT included
Q&A for [ODIN][UCLB3] UCLB3 Unbrick - Return to stock - Working PIT included Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Before posting, please use the forum search and read through the discussion thread for [ODIN][UCLB3] UCLB3 Unbrick - Return to stock - Working PIT included. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help. Thanks for understanding and for helping to keep XDA neat and tidy!
Attempted to follow the guide here on my old Infuse to breathe some life back into it, but I can't get it to work. Installed the drivers through Kies, Odin detects my phone in yellow. I follow the guide to the letter, but after flashing 'reset' in blue and getting the green 'pass' my phone simply doesn't reboot, nor can I boot it manually. I've removed the battery a few times and it doesn't change the situation. I can still boot into download mode with no issue and have tried flashing a few times, but I'm having no success booting the phone after Odin is done, nor can I get into recovery mode. <ID:0/003> Added!! <OSM> Enter CS for MD5.. <OSM> Check MD5.. Do not unplug the cable.. <OSM> Please wait.. <OSM> PHONE_UCLB3.tar.md5 is valid. <OSM> PHONE_UCLB3.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> Set PIT file.. <ID:0/003> DO NOT TURN OFF TARGET!! <ID:0/003> Get PIT for mapping.. <ID:0/003> Firmware update start.. <ID:0/003> modem.bin <ID:0/003> modem.bin <ID:0/003> Removed!! <ID:0/003> Completed.. <OSM> All threads completed. (succeed 1 / failed 0) Any ideas?
SG2Tiger said: Attempted to follow the guide here on my old Infuse to breathe some life back into it, but I can't get it to work. Installed the drivers through Kies, Odin detects my phone in yellow. I follow the guide to the letter, but after flashing 'reset' in blue and getting the green 'pass' my phone simply doesn't reboot, nor can I boot it manually. I've removed the battery a few times and it doesn't change the situation. I can still boot into download mode with no issue and have tried flashing a few times, but I'm having no success booting the phone after Odin is done, nor can I get into recovery mode. <ID:0/003> Added!! <OSM> Enter CS for MD5.. <OSM> Check MD5.. Do not unplug the cable.. <OSM> Please wait.. <OSM> PHONE_UCLB3.tar.md5 is valid. <OSM> PHONE_UCLB3.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> Set PIT file.. <ID:0/003> DO NOT TURN OFF TARGET!! <ID:0/003> Get PIT for mapping.. <ID:0/003> Firmware update start.. <ID:0/003> modem.bin <ID:0/003> modem.bin <ID:0/003> Removed!! <ID:0/003> Completed.. <OSM> All threads completed. (succeed 1 / failed 0) Any ideas? Click to expand... Click to collapse I never tried this flash before, but I do have a couple questions before proceeding... Is your phone AT&T or Rogers? Are you able to get back into download mode (that is, by method of device fully turned off, holding down both Volume Buttons and inserting the USB cable)?
joel.maxuel said: I never tried this flash before, but I do have a couple questions before proceeding... Is your phone AT&T or Rogers? Are you able to get back into download mode (that is, by method of device fully turned off, holding down both Volume Buttons and inserting the USB cable)? Click to expand... Click to collapse AT&T, the model is I997. I can still get into download mode, but I can't boot normally, nor into recovery mode (by holding volume up + volume down + power button; Samsung logo never appears). I used the included version of Odin with both the UCLB3_Unbrick_1.1.zip and UCLB3_Unbrick_root_1.1.zip files on the linked thread (I tried both).
SG2Tiger said: AT&T, the model is I997. I can still get into download mode, but I can't boot normally, nor into recovery mode (by holding volume up + volume down + power button; Samsung logo never appears). I used the included version of Odin with both the UCLB3_Unbrick_1.1.zip and UCLB3_Unbrick_root_1.1.zip files on the linked thread (I tried both). Click to expand... Click to collapse I always recommend this one for AT&T (could never try it myself, as I was a Rogers user), but you may have more luck with this (option A or D). http://forum.xda-developers.com/showthread.php?t=1613523
joel.maxuel said: I always recommend this one for AT&T (could never try it myself, as I was a Rogers user), but you may have more luck with this (option A or D). http://forum.xda-developers.com/showthread.php?t=1613523 Click to expand... Click to collapse Tried this a few times and it keeps failing. It'll get about 1/3 of the way there and then my computer will make the 'device disconnected' noise and Odin will fail. I left it in download mode, plugged in, without attempting the download to see if it was an issue with my cable or port, and it didn't disconnect...it seems to only be happening when I attempt to flash the md5. <ID:0/003> Added!! <OSM> Enter CS for MD5.. <OSM> Check MD5.. Do not unplug the cable.. <OSM> Please wait.. <OSM> I997UCLB3-CWM-root-deodex-extras.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> cache.rfs <ID:0/003> factoryfs.rfs <ID:0/003> Complete(Write) operation failed. <OSM> All threads completed. (succeed 0 / failed 1) <ID:0/003> Removed!!
SG2Tiger said: Tried this a few times and it keeps failing. It'll get about 1/3 of the way there and then my computer will make the 'device disconnected' noise and Odin will fail. I left it in download mode, plugged in, without attempting the download to see if it was an issue with my cable or port, and it didn't disconnect...it seems to only be happening when I attempt to flash the md5. <ID:0/003> Added!! <OSM> Enter CS for MD5.. <OSM> Check MD5.. Do not unplug the cable.. <OSM> Please wait.. <OSM> I997UCLB3-CWM-root-deodex-extras.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> cache.rfs <ID:0/003> factoryfs.rfs <ID:0/003> Complete(Write) operation failed. <OSM> All threads completed. (succeed 0 / failed 1) <ID:0/003> Removed!! Click to expand... Click to collapse Even with option D? I see C was used, based on the log... Sent from my Asus MeMO Pad 8"
joel.maxuel said: Even with option D? I see C was used, based on the log... Sent from my Asus MeMO Pad 8" Click to expand... Click to collapse For some reason option D is taking an unreasonable amount of time to download (it's been over an hour now), so I had initially skipped it and tried options A and C, with the same results. I'll report back once I am actually able to get option D downloaded.
Same problem with every option. Progress reaches about halfway, then fails. <ID:0/003> Added!! <OSM> Enter CS for MD5.. <OSM> Check MD5.. Do not unplug the cable.. <OSM> Please wait.. <OSM> I997UCLB3-CWM-root-deodex.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> cache.rfs <ID:0/003> factoryfs.rfs <ID:0/003> Complete(Write) operation failed. <OSM> All threads completed. (succeed 0 / failed 1) <ID:0/003> Removed!!
SG2Tiger said: Same problem with every option. Progress reaches about halfway, then fails. <ID:0/003> Added!! <OSM> Enter CS for MD5.. <OSM> Check MD5.. Do not unplug the cable.. <OSM> Please wait.. <OSM> I997UCLB3-CWM-root-deodex.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> cache.rfs <ID:0/003> factoryfs.rfs <ID:0/003> Complete(Write) operation failed. <OSM> All threads completed. (succeed 0 / failed 1) <ID:0/003> Removed!! Click to expand... Click to collapse Last thing I can think of, you are using the Odin that comes with the package right?
joel.maxuel said: Last thing I can think of, you are using the Odin that comes with the package right? Click to expand... Click to collapse Yes, it should be Odin3 v1.7.
The dev-host file mirrors are down? Does anybody have copies of them to upload? I need the one with root.
Umaroth said: The dev-host file mirrors are down? Does anybody have copies of them to upload? I need the one with root. Click to expand... Click to collapse Sorry, no option A here, but I do have option C (with CWM, deodex, etc) on mirror. See the following link: http://forum.xda-developers.com/showpost.php?p=58392432 Hope this helps.
Link Are Broken Umm the link cant be downloaded.. i m trying to restore my infuse but most of the downloadable file is broken or file not found
ZExNos said: Umm the link cant be downloaded.. i m trying to restore my infuse but most of the downloadable file is broken or file not found Click to expand... Click to collapse Good evening, Try my mirror: http://forum.xda-developers.com/showpost.php?p=58392432 Options are limited, only "Option C" but it should be enough to get the job done. Cheers.
[Completed] Softbricked a Galaxy S3 Virgin phone. Help?
I guess i goofed and got softbricked. here is the Odin log. I used the video on the xda-developers youtube channel, but i cant post a link on the thread due to the 10 post rule. <ID:0/003> Added!! <OSM> Enter CS for MD5.. <OSM> Check MD5.. Do not unplug the cable.. <OSM> Please wait.. <OSM> root66_BMC_I747MVLUEMK5.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> FAIL! (Auth) <OSM> All threads completed. (succeed 0 / failed 1) Any way to fix this? Id like to continue with the root, however if absolutely necessary ill go back to stock provided anyone knows where to get it.
Hi, Here is a dedicated help thread in your device section that you can ask for help in, http://forum.xda-developers.com/galaxy-s3/help/help-thread-galaxy-s3-question-t2690307 I suggest you add more detail when you post there... Specifically, exactly what you tried to flash. Good luck!
Odin error: There is no PIT partition.
I gave the gf's kid an old S2 Skyrocket to use with CM9 I believe on it. Something went wrong and the kid couldn't boot it anymore. I took a look. Flashed it with an old Odin but tried something else, flashed it with a newer Odin and completely screwed it up now. It's been a couple months since I tried fixing it so what I can remember is I think i accidentally wiped Clockwork recovery somehow and then the PIT file. Tried using a newer ODID to flash and just kept getting errors. The only way I can get into download mode now is with that little USB device that boots it into download mode. Otherwise it just stalls at SAMSUNG logo. So i tried messing with it again today. Using Odin 3.04 I tried flashing to stock firmware and just get this <ID:0/004> Added!! <OSM> Enter CS for MD5.. <OSM> Check MD5.. Do not unplug the cable.. <OSM> Please wait.. <OSM> KIES_HOME_I727UCMC1_I727ATTMC1_844945_REV02_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> There is no PIT partition. <ID:0/004> Added!! <OSM> All threads completed. (succeed 0 / failed 1 Cant seem to find any PIT files for the i727 Skyrocket. I found something called SGH-I727-PIT(modified_6GB) but no clue what that is. Tried it anyway and just get this: <ID:0/003> Added!! <OSM> Enter CS for MD5.. <OSM> Check MD5.. Do not unplug the cable.. <OSM> Please wait.. <OSM> KIES_HOME_I727UCMC1_I727ATTMC1_844945_REV02_user_low_ship.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> Complete(Write) operation failed. <ID:0/003> Added!! <OSM> All threads completed. (succeed 0 / failed 1 After messing with hours I'm about to give up and throw it in the trash...but read that if you can get into download mode then it could be fixed and i'm just doing it wrong. Any ideas?
Odin can be quite finicky. Keep trying and with different usb ports (the ones in the back of the pc if you're using a desktop) and cables. You shouldn't need a pit file. Do not have re-partition checked in Odin. Sent from my Nexus 9 using XDA-Developers mobile app
I've flashed a bunch of phones with Odin before no problem. But with this phone I really screwed with stuff. I'm usually good about being careful but not this time. I might have had repartitioned checked the one time. I can't remember. I think I screwed up the pit on the phone. Hence the no. Pit error. Never had that before. Ill try the other USB ports thought. Can't use Kies emergency restore because it won't connect to the phone. I have all drivers installed. First time I'm baffled as to flashing a Samsung phone. I don't even need the phone but my OCD just wants it working again.
u can read this, might help, http://forum.xda-developers.com/showthread.php?t=2023328
Thanks for the link vincon. Gave it a shot but still no love. Tried to flash that celox PIT file with Odin 1.85 but all I get is the same damn error <ID:0/005> Added!! <ID:0/005> Odin v.3 engine (ID:5).. <ID:0/005> File analysis.. <ID:0/005> SetupConnection.. <ID:0/005> Initialzation.. <ID:0/005> Set PIT file.. <ID:0/005> DO NOT TURN OFF TARGET!! <ID:0/005> Complete(Write) operation failed. <OSM> All threads completed. (succeed 0 / failed 1) Tried it again selecting the PIT and a stock ATT firmware file and same thing...the darn Complete(Write) operation failed. If i try just using the stock tar file I get: <ID:0/005> Added!! <ID:0/005> Odin v.3 engine (ID:5).. <ID:0/005> File analysis.. <ID:0/005> SetupConnection.. <ID:0/005> Initialzation.. <ID:0/005> Get PIT for mapping.. <ID:0/005> There is no PIT partition. <OSM> All threads completed. (succeed 0 / failed 1) Tried different USB ports, rebooted computer...nothing. I'm about to give up on it