Hi all,
I am really hoping someone can help me. I have a Sprint Samsung Galaxy S4 (Non T version) that appears to be soft bricked. My phone was hanging on the yellow Sprint screen so after other procedures, I decided to try and ODIN a stock version. What I had before all this happened was MK2 (knox) stock with only CF Auto Root. I downloaded the MK2 stock ROM from XDA and tried to ODIN. It failed. It got through the majority of the process and then at the very end it said FAILED. Now if I try and boot the phone, it automatically goes into the firmware error screen. So I still have the ability to ODIN but it always fails. I have also downloaded the NAE stock ROM from XDA and tried that too. I have tried using Odin 3.07, 3.09, and even 1.85. All fail. On the screen I sometimes get these messages as the ODIN process fails. Either a start [2xx, 1440] and next line BAR [2xx, 1440], or I get a start and then a sw rev check fail fused 5 binary 4. These are all in red letters just underneath the download mode details. I really don't know what to do. Please help me recover my phone. Any help is greatly appreciated. Thanks so much!
IF your phnone was on an NAE firmware you will probably have problems going back to MK2.
Search for the NAE firmware .tar and try that.
@SuperG03
So great to see you posting back after asking for help.
So cool when people contribute to what worked and didn't so that others can be helped and help to contribute to the community at large.....
Oh, wait you didn't.
Guess all is good.
smmmeeesh.
leaderbuilder said:
IF your phnone was on an NAE firmware you will probably have problems going back to MK2.
Search for the NAE firmware .tar and try that.
Click to expand...
Click to collapse
As I mentioned in my OP, I tried the NAE firmware with multiple attempts on various editions of Odin. All without success.
leaderbuilder said:
@SuperG03
So great to see you posting back after asking for help.
So cool when people contribute to what worked and didn't so that others can be helped and help to contribute to the community at large.....
Oh, wait you didn't.
Guess all is good.
smmmeeesh.
Click to expand...
Click to collapse
I'm sorry, it's been like a day and a half and I've been trying like crazy to figure out how to fix this thing... Not sure how fast you expect me to reply, but I do appreciate any and all help.
SuperG03
Just really wondering if you attempted the suggestions. And or what you've done to get it to work.
It gets old trying to assist people, especially when they make it sound so urgent, and then never hearing back.
Hope you get it working.
Good luck!
leaderbuilder said:
Just really wondering if you attempted the suggestions. And or what you've done to get it to work.
It gets old trying to assist people, especially when they make it sound so urgent, and then never hearing back.
Hope you get it working.
Good luck!
Click to expand...
Click to collapse
I definitely understand trying to help and not ever hearing back would get annoying... However, for the first like half a day I checked back at this thread every hour or 2 and it had a lot of views but not any replies. Even as of now, there hasn't been a reply with a suggestion of what to do that I haven't already stated I did try in my OP (you suggested NAE and I had been trying that already). I do appreciate you at least trying though.
SuperG03
SuperG03 said:
Hi all,
I am really hoping someone can help me. I have a Sprint Samsung Galaxy S4 (Non T version) that appears to be soft bricked. My phone was hanging on the yellow Sprint screen so after other procedures, I decided to try and ODIN a stock version. What I had before all this happened was MK2 (knox) stock with only CF Auto Root. I downloaded the MK2 stock ROM from XDA and tried to ODIN. It failed. It got through the majority of the process and then at the very end it said FAILED. Now if I try and boot the phone, it automatically goes into the firmware error screen. So I still have the ability to ODIN but it always fails. I have also downloaded the NAE stock ROM from XDA and tried that too. I have tried using Odin 3.07, 3.09, and even 1.85. All fail. On the screen I sometimes get these messages as the ODIN process fails. Either a start [2xx, 1440] and next line BAR [2xx, 1440], or I get a start and then a sw rev check fail fused 5 binary 4. These are all in red letters just underneath the download mode details. I really don't know what to do. Please help me recover my phone. Any help is greatly appreciated. Thanks so much!
Click to expand...
Click to collapse
So now I would like to reply as to try and help anyone else that might have had something similar to this happen to their phone. I DID FIX my phone but using a CRAZY method that I have no good idea of why it worked. So here goes...
LONG VERSION (Short Version below for those that don't want to read about all my trials and efforts):
So as I mentioned I was on MK2 before the problem started. I tried to ODIN the MK2 Stock ROM I downloaded here but it failed. So then I decided ok maybe the issue was the older ROM, so I downloaded the NAE Stock ROM and tried to ODIN that. Again, failed. Now both of these 2 tries got far into the process before they failed. So again, through reading various posts here and on other forums it was suggested to try with other version of ODIN (I had been trying 3.07). I then tried the MK2 ROM again but with ODIN 3.09 but it failed almost immediately. That is when I noticed the lines "SW Rev Check Fail Fused 5 Binary X" every time it tried and failed. My guess is that this has something to do with the whole not being able to downgrade ROMs at any point and since I had almost completed the NAE stock ROM ODIN flash, it was stuck only with the option for NAE. So then onto trying NAE with ODIN 3.09. Once again, got most of the way done but failed toward the end of the system.img.ext4 part. I kept noticing that on the screen, almost as soon as I started the ODIN process it would output a line saying Start [220, 1440] and then soon after a line saying BAR [224, 1440]. Now I still have no idea what any of that means, but it was always failing, mostly toward the end of the flash. I then tried other ODIN versions including 1.85. All with the same results. I was at a loss. At that point I got desperate and decided I wasn't even going to try and save my DATA and thought maybe the partitions got corrupted so I found the NAE PIT file from these forums and attempted to ODIN both the PIT and the PDA with re-partition option. Once again, all attempts with all ODIN versions failed, with the same START and BAR messages showing up. I then broke down and decided to post here for help. I kept reading but everyone kept just saying in other threads about maybe KIES interfering if it was active in anyway, etc. so I check my processes and there were no KIES ones running. At that moment something occurred to me about another process by which to flash that I remember from my Galaxy S2 days. That was Heimdall. So, I decided to go on a mission to learn how to use Heimdall myself without a ready package. I finally learned how and decided to try it. I had to extract out all the .bin and .ext4, etc files out of the NAE tar and load them up manually. I started to flash and it looked to be working but then alas, it failed similarly to how ODIN did. I was at my wits end by this point. However, something occurred to me when I realized that the .tar had all these independent files in it that ODIN just tried to do all together. So here is what I did that finally WORKED. I used ODIN 3.09 with the NAE PIT file and the NAE ROM PDA file. I checked only Re-Partition and unchecked all others. I then watched exactly what ODINs log said was being flashed to the phone and what failed. I kept re-flashing until I got passed the system.img.ext4 file and the it failed on one of the others. I made note at which files out of the 13 that came from the .tar file were sent by ODIN successfully before it failed. I then closed ODIN and restarted phone in download mode and went to Heimdall. I used Heimdall to manually select only the remaining files left of the 13 that DID not go through successfully. I then flashed those I think 3 or 4 files and it said it was successful. I then rebooted my phone and to my SHOCK the phone booted up successfully and went into the OS as if it was factory wiped and ready for first time use. I was a bit bummed about having to redo all my settings, etc again and losing my old Text Messages, etc, but was so happy to have my phone back up and running. Thanks for reading this whole thing (I know it was quite long) and I hope it helps someone else out of a similar jam.
SHORT VERSION:
GET NAE Stock ROM
GET NAE PIT File
GET ODIN 3.09
GET Heimdall
YOU WILL LOSE YOUR DATA
Step 1) Use ODIN 3.09 (Run as Admin) and load up PIT file and PDA. Uncheck everything but RE-Partition
Step 2) (Hard Part) Keep flashing over and over again until you get at least the system.img.ext4 part to go through before ODIN says FAIL (It should fail on another file, like hidden.img.ext4 or NON-HLOS.bin
Step 3) Scroll through the ODIN log on the left and note every file that was successful. Basically any files it says was successful until the last one that it stops at and says FAIL
Step 4) You will need to extract out the contents of the NAE Stock ROM tar file to another directory
Step 5) Use Heimdall frontend (Run as Admin) and use the flash tab
Step 6) Load the PIT file into Heimdall as that is required for anything. But DO NOT use RE-Partition option
Step 7) Click Add and select each of the remaining files with their appropriate Partition Name and browse for those files from the ones you extracted from the tar. There are 13 files total from the tar file. Just load up (Add) starting with the file that failed in ODIN and then load up whichever ones that did not show up on the ODIN log at all. Click Start and cross your fingers
Step 8) If all went well, the phone should reboot and be up and running. If not you might have to start at Step 1 and try again
Step 9) Jump For Joy that your phone is Alive and working again!!!
Once again, I wanted to share my experience with everyone in hopes that it will help someone else out. I have no idea why I had to go to such great lengths of combining 2 versions of FLASHING and doing it piece by piece, but that is for greater minds then me to either know or figure out. I'm just happy my phone is working again! Good luck to anyone else having a similar issue.
SuperG03
Related
i think i smurfed up!!!!!! i started a Odin recovery to get back to factory settings after installing the new loki mod for att and verizon bootloaders and got 2 errors. im using odin 304 and the factory .tar file for the att galaxy s4. some one please save my baby i dont know what i would do without her :crying:
novacaine86 said:
i think i smurfed up!!!!!! i started a Odin recovery to get back to factory settings after installing the new loki mod for att and verizon bootloaders and got 2 errors. im using odin 304 and the factory .tar file for the att galaxy s4. some one please save my baby i dont know what i would do without her :crying:
Click to expand...
Click to collapse
You're not offering anything for people to help you. What errors? What were you trying to Odin? What settings? What machine (PC, Mac, Linux)? Odin has a 3.07 for this, so you might try that, but otherwise, you just said "it's broke -fix it!". More information gets better answers.
And you didn't even say what or why you started this in the first place.
that would be kinda important smh.
errors
start [224, 1440]
bar [240, 1440]
it gives a third one but it blinks out faster than i can read it....it started after i attempted to flash slimbeans rom onto it. it boots all the way up to att and just sits there if anymore information is needed just ask ill give all i can to fix this problem
i got it to go odin 307 didnt fix it if any one else has this problem on windows or any system that has kies just run emergency recovery and it will fix it
novacaine86 said:
i got it to go odin 307 didnt fix it if any one else has this problem on windows or any system that has kies just run emergency recovery and it will fix it
Click to expand...
Click to collapse
I had to use KIES emergency firmware recovery. ODIN flashed fine for me after loki, but I was stuck on the samsung custom screen afterwards. The KIES emergency firware recovery did the trick. Hopefully this helps others.
It looks like I got myself in a pickle. I have a GS4 running 4.2.2. I picked up my phone today and successfully rooted it with instructions from DroidView using files from chainfire. I then installed CWM recovery with ROM Manager and backed up my ROM with it. I decided to replace chainfires SU with the one fom CWM like I had on my S3. After rebooting from recovery mode I noticed I had lost root so I used the same method to root it again because I thought it had reset itself. Before the reboot occurred there was option to prevent the possibility of the ROM flashing itself to stock. I went to select the Yes option but bumped the power button which selected No. While trying to reroot and failing, the phone displayed the message "Invalid percent of drawing download progress bar." On reboot the error “Firmware upgrade encountered an issue“ along with a cone and a couple of other pics. I have tried to get into recovery mode several times but repeatedly get this error. I can get into download mode and have tried to flash the stock ROM for this phone but it fails in Odin 3.0.7. Odin sees my phone and verifies the md5 but fails very quickly upon clicking start. I tried this with KiesPDLR running in the background and disabled. I have not tried anything else out of concern for messing it up further. Attached are screenshots and log from ODIN along with the text that is being displayed in download mode. (I will have to post these later as the attachments option will not work properly on my wife's S3).
Two other notes. 1) I used ODIN 1.85 to root as that was what was included in the chainfire download. But I used ODIN 3.0.7 to try and unroot because that's what the DroidView directions said. Would it make any difference to use ODIN 1.85 to try and flash the stock firmware? It sees my phone as well but the F. Reset Time option is unchecked and grayed out and the directions says it needs to be checked. Don't know if that really makes a difference. 2) My phone is actually with US cellular but there is not a forum for this carrier. I chose this forum because my previous phone the Mesmerize had an identical model number as the Fascinate. Please do not pass over my request for help because of this as I am in dire need.
apel69 said:
It looks like I got myself in a pickle. I have a GS4 running 4.2.2. I picked up my phone today and successfully rooted it with instructions from DroidView using files from chainfire. I then installed CWM recovery with ROM Manager and backed up my ROM with it. I decided to replace chainfires SU with the one fom CWM like I had on my S3. After rebooting from recovery mode I noticed I had lost root so I used the same method to root it again because I thought it had reset itself. Before the reboot occurred there was option to prevent the possibility of the ROM flashing itself to stock. I went to select the Yes option but bumped the power button which selected No. While trying to reroot and failing, the phone displayed the message "Invalid percent of drawing download progress bar." On reboot the error “Firmware upgrade encountered an issue“ along with a cone and a couple of other pics. I have tried to get into recovery mode several times but repeatedly get this error. I can get into download mode and have tried to flash the stock ROM for this phone but it fails in Odin 3.0.7. Odin sees my phone and verifies the md5 but fails very quickly upon clicking start. I tried this with KiesPDLR running in the background and disabled. I have not tried anything else out of concern for messing it up further. Attached are screenshots and log from ODIN along with the text that is being displayed in download mode. (I will have to post these later as the attachments option will not work properly on my wife's S3).
Two other notes. 1) I used ODIN 1.85 to root as that was what was included in the chainfire download. But I used ODIN 3.0.7 to try and unroot because that's what the DroidView directions said. Would it make any difference to use ODIN 1.85 to try and flash the stock firmware? It sees my phone as well but the F. Reset Time option is unchecked and grayed out and the directions says it needs to be checked. Don't know if that really makes a difference. 2) My phone is actually with US cellular but there is not a forum for this carrier. I chose this forum because my previous phone the Mesmerize had an identical model number as the Fascinate. Please do not pass over my request for help because of this as I am in dire need.
Click to expand...
Click to collapse
Try odin 1.85 I use that to odin back to stock and dont worry about the other ones just make sure auto reboot is checked.
Also are you sure the phone you have is the sprint gs4 sph l720 jfltespr?? Cause odin a tar file not for the phone could potentially brick the phone.
Sent from my SPH-L720 using xda app-developers app
I would try to download the stock rom from a different source if you can. These tar files are so large for this phone that the possibility of a bad download is pretty high. Also, make sure you don't have to extract the actual .tar file first from the archive you download. Lots of these stock roms are repackaged into a zip file and you need to extract the tar file for use in Odin before installing.
I am back in business. I have my phone and home internet back now. Yeah. I used the same stock ROM I had since it was the same as sammobile which was also a zip file and I already had it on my system. I just used Odin 1.85 instead. I guess I could have done this earlier and prevented a near stoke but everything else I had done seemed to get me deeper in a hole. These large zip files have always made me a bit nervous but I haven't found where to get one otherwise.
I have some follow up questions.
1) Why would it flash with Odin 1.85 and not with 3.0.7?
2) Is CWM's SU not compatible with the S4? Everything was working fine until I switched this from chainfire to CWM using ROM Manager.
3) Is there a good source with unzipped ROM's?
Chainfires SuperSU is much better with JellyBean than cwm SU. For some reason most people that try to switch to SU from SuperSU have the same problem you had.
Sent from my icrap 2 using Tapatalk HD
Okay. I decided to go with chainfires after this fun little ordeal. The few small things I preferred from CWM is not worth it. Besides it looks like chainfire made some upgrades since I last looked at it. I guess I was lucky with my S3 because I converted several times.
Thanks for all the help everyone.
I tried installing Cyanogen Mod but it didn't work, I just got stuck at the boot screen and when I tired to flash back to stock something really went wrong.
Now all I see is an error saying "Firmware upgrade encountered an issue. Pleas select recovery mode in Kies & try again."
But I can still access download mode so from what I can tell I can fix this with the right files and right settings in Odin3.
I have the Sprint Galaxy S4 SPH-L720. I am currently running Odin3 v3.07.
I was trying to flash this in Odin3, qbking77.com/development/how-to-unroot-and-unbrick-the-samsung-galaxy-s4. I got as far as system.img.ext4 before it failed.
Any help would be greatly appreciated. I am still somewhat new to hacking my phone but an very tech savvy and feel comfortable following any directions you have for what to flash with odin3 and what options to use.
Thanks in advance.
Ryan990 said:
I tried installing Cyanogen Mod but it didn't work, I just got stuck at the boot screen and when I tired to flash back to stock something really went wrong.
Now all I see is an error saying "Firmware upgrade encountered an issue. Pleas select recovery mode in Kies & try again."
But I can still access download mode so from what I can tell I can fix this with the right files and right settings in Odin3.
I have the Sprint Galaxy S4 SPH-L720. I am currently running Odin3 v3.07.
I was trying to flash this in Odin3, qbking77.com/development/how-to-unroot-and-unbrick-the-samsung-galaxy-s4. I got as far as system.img.ext4 before it failed.
Any help would be greatly appreciated. I am still somewhat new to hacking my phone but an very tech savvy and feel comfortable following any directions you have for what to flash with odin3 and what options to use.
Thanks in advance.
Click to expand...
Click to collapse
Try these links from this post buddy
http://forum.xda-developers.com/showthread.php?p=46273175
The #1 misfit
of my crew of misfits
Ryan990 said:
I tried installing Cyanogen Mod but it didn't work, I just got stuck at the boot screen and when I tired to flash back to stock something really went wrong.
Now all I see is an error saying "Firmware upgrade encountered an issue. Pleas select recovery mode in Kies & try again."
But I can still access download mode so from what I can tell I can fix this with the right files and right settings in Odin3.
I have the Sprint Galaxy S4 SPH-L720. I am currently running Odin3 v3.07.
I was trying to flash this in Odin3, qbking77.com/development/how-to-unroot-and-unbrick-the-samsung-galaxy-s4. I got as far as system.img.ext4 before it failed.
Any help would be greatly appreciated. I am still somewhat new to hacking my phone but an very tech savvy and feel comfortable following any directions you have for what to flash with odin3 and what options to use.
Thanks in advance.
Click to expand...
Click to collapse
Been there (that screen is still odin mode). Should be recoverable through odin still. In my case, the problem was that I had a bad tar file. I'd start there, make sure you have the right file for your phone. If you have the right file, it may be a bad download. So I would try to re-download, or naybe try a different version.
Cheers.
Sent from my SGH-M919 using xda app-developers app
Oscar_david said:
Been there (that screen is still odin mode). Should be recoverable through odin still. In my case, the problem was that I had a bad tar file. I'd start there, make sure you have the right file for your phone. If you have the right file, it may be a bad download. So I would try to re-download, or naybe try a different version.
Cheers.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
I had used the exact file before so I know its correct and uncorrupted. I did figure it out.
Successfully flashed using another computer. Best I can figure, following the CM installation instructions have a step "Run the included zadig.exe in the drivers folder of the Heimdall Suite."
That does something with drivers that odin must not like. I tried uninstalling, restarting my computer than reinstalling the Samsung drivers but that was not enough. A new computer was the answer.
Ryan990 said:
I had used the exact file before so I know its correct and uncorrupted. I did figure it out.
Successfully flashed using another computer. Best I can figure, following the CM installation instructions have a step "Run the included zadig.exe in the drivers folder of the Heimdall Suite."
That does something with drivers that odin must not like. I tried uninstalling, restarting my computer than reinstalling the Samsung drivers but that was not enough. A new computer was the answer.
Click to expand...
Click to collapse
Wow what one file can do to mess everything up and glad you got it working again buddy
The #1 misfit
of my crew of misfits
Bigger question here is:
Why are some phones experiencing corrupt partitions after flashing AOSP-based ROMs? Myself included....
I'm installing the new firmware but i had an issue with odin...
I flashed again 4.4.2 but in download mode, the last line you can see " UDC START" in colour red... Is this normal? I think the phone works good, but i don't know why put on this...
Anyone have this new line??
I have the same problem with a N9005 I guess it was Hong Kong version for the kanjis in the back, but is stuck in odin mode with the UDC START line
UDC Start info.
Ok gent's little more knowledge about "udc start" I am guessing that the problem became clear as you installed 4.4.2 KK.
So did I and came across UDC Start the second time I booted into download mode.
As I played around i became aware that the "UDC Start" mode locks the download loader to certain criteria. This would be 4.4.2 KK,
so anything under 4.4.2 will get a MASSIVE RED FAIL. That including the CWR/TWRP recoveries and ROOT files.
So just to specify, yes phone is now locked/bricked to 4.4.2 KK software only.
Therefore I would please like some help to get the udc start away!? If anyone can help.
If I shared some light to the darkness please say thanks.:good:
Try this out:
Worked for me on a Hong Kong 16GB N9005 which was stuck on the 'Samsung Galaxy Note 3' screen after getting a 'Invalid: ext4 image' or 'Repartioning failed' errors while installing 4.4.2 OFFICIAL (Single File ROM) via Odin.
Binary: Custom
Knox: 0x1
Method:
In Odin mode
1. Flash the latest cf-autoroot (Kitkat support) [http://download.chainfire.eu/352/CF-...x-smn9005.zip]
2. Flash the Chenglu's latest CWM - 6.0.4.6 (the one that supports KitKat) http://forum.xda-developers.com/show....php?t=2454079
Download Sweet Rom and place it in ExtSDcard (http://forum.xda-developers.com/show....php?t=2487425)
I tried external sd-card with various format and could not install the ROM. After format my SD Card to FAT32, the ROM can be installed.
On Device
1. Boot in to Recovery mode by Volume up + Home + Power
2. Wipe Factory reset / Dalvik Cache
3. Format /System (under "mount and storage" menu) [IMPORTANT STEP]
4. Install Rom from SD Card
5. Say your prayer. You'll need it. (The installation could take sometimes. If the device screen shows Samsung boot animation, you're half way there)
How is that going to take away the udc start?
I have UDC Start in Odin/Download mode... It hasn't affected my flashing of custom ROMs nor Stock, everyone on KK has it.
Ok, but why if i try to install a previous version of TW rom 4.3 i get a massive fail?
But all the rest works?
Thanx in regards.
FdeKlerk said:
Ok, but why if i try to install a previous version of TW rom 4.3 i get a massive fail?
But all the rest works?
Thanx in regards.
Click to expand...
Click to collapse
Because you are locked into the new Bootloader (NA6) and it's unable to downgrade
So I am guessing there is no way to downgrade the boot-loader without unlocking it?
FdeKlerk said:
So I am guessing there is no way to downgrade the boot-loader without unlocking it?
Click to expand...
Click to collapse
There's no way full stop. Samsung have blocked downgrades within the bootloader itself.
Wow now that's some sort of a problem.
My 4.4.2 works but i love xposed modules to make everything transparent and as of yet kitkat does not support that.
And now i a stuck on 4.4.2..
But thanx for the assist.:good:
Same Problem with E330s
ManuH8 said:
I'm installing the new firmware but i had an issue with odin...
I flashed again 4.4.2 but in download mode, the last line you can see " UDC START" in colour red... Is this normal? I think the phone works good, but i don't know why put on this...
Anyone have this new line??
Click to expand...
Click to collapse
Hi. I have a unrooted SHV-E330 (I9506 to some) I was running the unrooted firmware and updating with Kies up until yesterday when the update to came up. I ran it as with every other update however on self rebooting the phone now goes to ODIN MODE (in red) and UDC Start (in red) i'm a root virgin and was happy with the phone running as it was AnTU TU score 36118 with the Korean bloatware running in the background. From what I have picked up after 4.3 firmware update to 4.4.2 there is no going back. I tired to root with earlier versions of firmware but get fail every time. I Picked up a zip SKT-E330SKSUCNA7 wich goes as far as checking the MD5 file successfully in Odin 3 v3.09. everywhere I look on the web it states the com box should be yellow however mine is blue.
After MD5 successful I get leave CS. I click start I get 'Get PIT for mapping. There id no PIT partion followed by a red box and the'FAIL!' box with 'all threads completed Failed 1.
I have never rooted a phone and a buff mentioned that I will not regret it. I figure thart i'm doing something wrong as there was no PIT file with the firmware.
On first trying a firmware recovery in Kies because the phone is stuck In ODIN MODE it will not recognise the phone even though the USB drivers are installed.
If their is a person out there that could talk me through rooting trough the stuck ODIN MODE I would appreciate contact.
I gather that I have no choice but to try ODIN MODE on phone as that's where the phone is stuck. Removing battery etc has been tried to death.
summan971 said:
Hi. I have a unrooted SHV-E330 (I9506 to some) I was running the unrooted firmware and updating with Kies up until yesterday when the update to came up. I ran it as with every other update however on self rebooting the phone now goes to ODIN MODE (in red) and UDC Start (in red) i'm a root virgin and was happy with the phone running as it was AnTU TU score 36118 with the Korean bloatware running in the background. From what I have picked up after 4.3 firmware update to 4.4.2 there is no going back. I tired to root with earlier versions of firmware but get fail every time. I Picked up a zip SKT-E330SKSUCNA7 wich goes as far as checking the MD5 file successfully in Odin 3 v3.09. everywhere I look on the web it states the com box should be yellow however mine is blue.
After MD5 successful I get leave CS. I click start I get 'Get PIT for mapping. There id no PIT partion followed by a red box and the'FAIL!' box with 'all threads completed Failed 1.
I have never rooted a phone and a buff mentioned that I will not regret it. I figure thart i'm doing something wrong as there was no PIT file with the firmware.
On first trying a firmware recovery in Kies because the phone is stuck In ODIN MODE it will not recognise the phone even though the USB drivers are installed.
If their is a person out there that could talk me through rooting trough the stuck ODIN MODE I would appreciate contact.
I gather that I have no choice but to try ODIN MODE on phone as that's where the phone is stuck. Removing battery etc has been tried to death.
Click to expand...
Click to collapse
Your phone does not have a pit file on it. Odin downloads the pit file from the phone to make sure that all the partitions are correctly flashed.
Try ticking the 'Re-partition' box in odin while flashing. Though I don't really think it will help, because your single file ROM most probably does not contain the pit.
Your best bet is to find somebody else with the same model as you, and get a pit from them.
PS- You are in the wrong forums.
[COLOR=[/COLOR]
feralfire said:
your phone does not have a pit file on it. Odin downloads the pit file from the phone to make sure that all the partitions are correctly flashed.
Try ticking the 're-partition' box in odin while flashing. Though i don't really think it will help, because your single file rom most probably does not contain the pit.
Your best bet is to find somebody else with the same model as you, and get a pit from them.
Ps- you are in the wrong forums.
Click to expand...
Click to collapse
do not tick re-partition without having a pit file, you will get a brick.
Feralfire, you just broke the first law of flashing with ODIN... If you don't know what to do then don't say anything...
Thanks for caring XDA developers - i fixed it
FeralFire said:
Your phone does not have a pit file on it. Odin downloads the pit file from the phone to make sure that all the partitions are correctly flashed.
Try ticking the 'Re-partition' box in odin while flashing. Though I don't really think it will help, because your single file ROM most probably does not contain the pit.
Your best bet is to find somebody else with the same model as you, and get a pit from them.
PS- You are in the wrong forums.
Click to expand...
Click to collapse
Hey thanks for the response the same day I managed to fix the problem a hour ago after 24 hours of banging my head on a wall.
I uninstalled all software including Odin remembering that ODIN MODE was the only option. most of the Boot Operating system was in Korean.
I followed a you tube guide from another root and noticed that although ODIN MODE and UDC start are new (according to other forums) that the other information insinuated that the screen I was looking at was also the download mode.
I reinstalled Kies and rather than asking me for the emergency recovery code it reset and was asking for the Model and serial number. After which it stated it could not recover the device only reinstall the stock firmware. I selected OK. the phone came back to life and reinstalled all data from cloud.
now on 4.4.2 and still thinking about rooting
however I must warn anyone that comes across the unlocker website that states its mod allows for E330S root. that clockwork mod does not cater for E330S.
ultramag69 said:
[COLOR=[/COLOR]
do not tick re-partition without having a pit file, you will get a brick.
Feralfire, you just broke the first law of flashing with ODIN... If you don't know what to do then don't say anything...
Click to expand...
Click to collapse
Au contraire, I have done a lot of research on pit file and played around a lot. Check out my threads.
If you tick re-partition without having a pit, it just gives you an error. Maybe in the olden days, it might have been an issue (I haven't always been a Samsung guy), but definitely not now.
FeralFire said:
Au contraire, I have done a lot of research on pit file and played around a lot. Check out my threads.
If you tick re-partition without having a pit, it just gives you an error. Maybe in the olden days, it might have been an issue (I haven't always been a Samsung guy), but definitely not now.
Click to expand...
Click to collapse
If so, then make sure they know which version of ODIN to use as this is the fastest way to kill a phone I know...
Right from the very first this was a cardinal sin but then you didn't have a phone anymore or much sympathy either... But to tell a noob to do this was in effect saying "put your phone in front of a steamroller, it'll be ok after its gone over it a couple of times"...
ultramag69 said:
If so, then make sure they know which version of ODIN to use as this is the fastest way to kill a phone I know...
Right from the very first this was a cardinal sin but then you didn't have a phone anymore or much sympathy either... But to tell a noob to do this was in effect saying "put your phone in front of a steamroller, it'll be ok after its gone over it a couple of times"...
Click to expand...
Click to collapse
He was using 3.09. Don't overcomplicate things.
But anyway, I apologize for making people put their phones in front of 20 ton vehicles.
re Pit File
FeralFire said:
Your phone does not have a pit file on it. Odin downloads the pit file from the phone to make sure that all the partitions are correctly flashed.
Try ticking the 'Re-partition' box in odin while flashing. Though I don't really think it will help, because your single file ROM most probably does not contain the pit.
Your best bet is to find somebody else with the same model as you, and get a pit from them.
PS- You are in the wrong forums.
Click to expand...
Click to collapse
I found this KS01LTE_KOR_SKT_32G.pit and ran it in Odin running download mode and it worked. It appears there are several Korean versions of the right ROM and unless the right rom is used flash in odin does not work.
I'm starting to sound like i know what i'm talking about!
summan971 said:
I found this KS01LTE_KOR_SKT_32G.pit and ran it in Odin running download mode and it worked. It appears there are several Korean versions of the right ROM and unless the right rom is used flash in odin does not work.
I'm starting to sound like i know what i'm talking about!
Click to expand...
Click to collapse
The different ROMs must have different pits. That would explain why only some specific ones work.
Anyway, congratulations.
Well, I broke my phone.
My earpiece boost stopped working and I could barely hear on the phone, the new Facebook app was crashing Facebook constantly and I was getting random reboots yesterday so I figured I would go for something new.
Because this was my first rom on my S4, I figured I should go back to stock first, bad idea. I loaded Odin up, went to flash the stock firmware to install the newest version of Sacs rom, and it failed right at NAND write start!!
I even went online and downloaded a newer firmware (February) and that failed also. I can't do the emergency fix in Kies and I can't use the other option in Kies because it says my serial is incorrect
I don't know what to do at this point, but I desperately need my phone ASAP in case my boss calls me.
Any help appreciated.
April
Well you REALLY don't give much info.
What version of Android were you on when you got your phone?
Do you have the T version of the phone or just the standard.
What ROM are you talking about 'bening your first'?
How did you install it?
What file did you try and Odin?
It is recommended you read, read some more, search and then read some more to keep just such things from happening.
Just a wild guess but you tried to Odin a .tar to a version 'previous' to the version you started with.
OR you tried to Odin a .tar for the wrong model - tried a non T .tar on a T model or vice-versa
Search for the FULL NAE .tar if you are on the 'standard' model and Odin that one.
Or, if on the T variant, hit up those threads, find the lates .tar and Odin that.
@aprilx
So great to see you posting back after asking for help.
So cool when people contribute to what worked and didn't so that others can be helped and help to contribute to the community at large.....
Oh, wait you didn't.
Guess all is good.
smmmeeesh.
Sorry, I worked 16 hours yesterday, so checking the forums was the last thing on my mind considering I got up at 5am and got home at 9:30pm.
I figured out what it was, after trying a million different things. I found a MJA stock firmware and I was able to flash that, and now I finally have Kitkat on my device.