[Q] SGH-I337 soft brick - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

I need help. I recently rooted my phone and tried to install goldeneye rom but it failed and now its stuck on Odin mode 'Downloading mode' and i have tried to use Odin to restore back to stock and the samsung kies method but everytime i get an error on odin it just says fail, and then when i do a samsung kies restore it says on my phone SW REV. CHECK FAIL : fused : 2, Binary : 1 or somthing like that the text it rlly small. Please i would like to use my phone again.

m34hell said:
I need help. I recently rooted my phone and tried to install goldeneye rom but it failed and now its stuck on Odin mode 'Downloading mode' and i have tried to use Odin to restore back to stock and the samsung kies method but everytime i get an error on odin it just says fail, and then when i do a samsung kies restore it says on my phone SW REV. CHECK FAIL : fused : 2, Binary : 1 or somthing like that the text it rlly small. Please i would like to use my phone again.
Click to expand...
Click to collapse
I'm guessing you have the MK2 firmware? The only thing available (at this time) for MK2 is a version of Safestrap. There is plenty of information about this available in the forums.

I fixed it
m34hell said:
I need help. I recently rooted my phone and tried to install goldeneye rom but it failed and now its stuck on Odin mode 'Downloading mode' and i have tried to use Odin to restore back to stock and the samsung kies method but everytime i get an error on odin it just says fail, and then when i do a samsung kies restore it says on my phone SW REV. CHECK FAIL : fused : 2, Binary : 1 or somthing like that the text it rlly small. Please i would like to use my phone again.
Click to expand...
Click to collapse
Nvm guys a fixed it all I needed to do was download the correct MD5 files from mega.co.nz/#!WEEzSA7Z!aB46731_AwM7P83eMdDlmFYd1hUZfFBcQAZjc1X7wAE

m34hell said:
Nvm guys a fixed it all I needed to do was download the correct MD5 files from mega.co.nz/#!WEEzSA7Z!aB46731_AwM7P83eMdDlmFYd1hUZfFBcQAZjc1X7wAE
Click to expand...
Click to collapse
That is the MF3 TAR file, so you must have been on MF3 firmware. The file is also available via links in the XDA forums, which I suggest everyone use instead of direct links or off site websites. You can avoid a lot of trouble in the future if you take a little time to read and learn about what it is you are trying to do before you try it. Good luck.

Related

odin error

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.

[Q] DOWNLOAD mode N9005 - 4.4.2 - UDC START?

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.

Seriously NEED HELP (S4 Bricked) !!!!!!

i have a verizon s4. i tried to install custom rom in it now i am stuck at this screen which says " downloading.." "do not turn off target"
i tried every version of odin and multiple roms to flash but it says " SW RV. CHECK FAIL : FUSED 5 : BINARY 1"
WHAT ???? IS THAT ??
You might probably have flashed the wrong firmware for your device or Downgraded to older version. I am Attaching a link here please go through it carefully and try recovering your phone with care.
http://forum.xda-developers.com/showthread.php?t=2511880
This is for Note 3 but you can follow the same for yours, download the stock and latest available firmware (KITKAT 4.4.2) for your phone and flash via odin.
tune345 said:
i have a verizon s4. i tried to install custom rom in it now i am stuck at this screen which says " downloading.." "do not turn off target"
i tried every version of odin and multiple roms to flash but it says " SW RV. CHECK FAIL : FUSED 5 : BINARY 1"
WHAT ???? IS THAT ??
Click to expand...
Click to collapse
You are at the wrong forum. This is not for the verizon s4. Go there for anwsers.
Probably you just need to reflash stock firmware or something.
Aamirx12 said:
You might probably have flashed the wrong firmware for your device or Downgraded to older version. I am Attaching a link here please go through it carefully and try recovering your phone with care.
http://forum.xda-developers.com/showthread.php?t=2511880
This is for Note 3 but you can follow the same for yours, download the stock and latest available firmware (KITKAT 4.4.2) for your phone and flash via odin.
Click to expand...
Click to collapse
secure check fail sbl1
tune345 said:
secure check fail sbl1
Click to expand...
Click to collapse
what you did this time, please post in detail.
Get your official firmware from http://www.sammobile.com/firmwares/
register there, then download the firmware for your phone( Please check beneath your battery the proper info about your phone and download the same for your phone)
Aamirx12 said:
what you did this time, please post in detail.
Get your official firmware from http://www.sammobile.com/firmwares/
register there, then download the firmware for your phone( Please check beneath your battery the proper info about your phone and download the same for your phone)
Click to expand...
Click to collapse
i am downloading the firmware from sammobile it was showing me 3 hours to download so i download the same file from a different location , that might be a problem i guess.
but i used odin 3.07 and 3.04
it is showing me the same error
i am about to tried the official rom in a few minutes from the sammobile.
flash the appropriate one.. and reply after flashing
ok so after trying the rom from sammobile it's showing me the same error.
i am attaching pictures for details , please help !!! .... am goingggggg nutssss !!:crying:
took off from work just to do this lol
tune345 said:
ok so after trying the rom from sammobile it's showing me the same error.
i am attaching pictures for details , please help !!! .... am goingggggg nutssss !!:crying:
took off from work just to do this lol
Click to expand...
Click to collapse
Which ROM you were using before all this happened
tune345 said:
ok so after trying the rom from sammobile it's showing me the same error.
i am attaching pictures for details , please help !!! .... am goingggggg nutssss !!:crying:
took off from work just to do this lol
Click to expand...
Click to collapse
You should go to the forum for you device. This forum is NOT for you device.
http://forum.xda-developers.com/sitesearch.php?q=SW REV. CHECK FAIL
And because you posted little usefull information in this topic it's hard to help.
Aamirx12 said:
Which ROM you were using before all this happened
Click to expand...
Click to collapse
i was using the stock ROM when i tried to install cyanogen few months back but the processed did not go through successfully so now when i start the phone i get the samsung custom logo.
so i was using that for months now because it did let me go thru normally even though the process of installing cyanogen didn't completed. So i think i messed up some internal files.
but phone was working good and everything until when i wanted to factory reset , it goes into odin mode and then gives me that error no matter
what version or Stock rom i use
Mod Edit
Please post in your variant's forum:
http://forum.xda-developers.com/forumdisplay.php?f=2314
Thread closed
malybru
Forum Moderator

[Q] Help needed bricked my SM-N900

So today I was trying to update my phone to a newer version of 4.4.2 I downloaded N900ZSUDNG1_N900OZSDNG1_BRI also Odin v3.09, Odin detects my phone perfectly but flashing fails every time i tried 4 different USB ports and same thing at the end of flashing it says FAILED but i see no error on the log it goes all the way to where it writes CACHE it seems and then says FAILED any ideas as to what to do to recover my phone would be appreciated.
Hey good morning,
I would suggest you to flash root (knox will be flagged 0x1)
Then flash cwm (or any recovery you like)
Put a nice ROM in your SD card (use another device or a card reader for pc)
Boot into recovery, wipe all data and flash the rom.
(* the steps above WILL void your warranty)
bligui said:
So today I was trying to update my phone to a newer version of 4.4.2 I downloaded N900ZSUDNG1_N900OZSDNG1_BRI also Odin v3.09, Odin detects my phone perfectly but flashing fails every time i tried 4 different USB ports and same thing at the end of flashing it says FAILED but i see no error on the log it goes all the way to where it writes CACHE it seems and then says FAILED any ideas as to what to do to recover my phone would be appreciated.
Click to expand...
Click to collapse
Download again may what u download is corrupted.
bligui said:
So today I was trying to update my phone to a newer version of 4.4.2 I downloaded N900ZSUDNG1_N900OZSDNG1_BRI also Odin v3.09, Odin detects my phone perfectly but flashing fails every time i tried 4 different USB ports and same thing at the end of flashing it says FAILED but i see no error on the log it goes all the way to where it writes CACHE it seems and then says FAILED any ideas as to what to do to recover my phone would be appreciated.
Click to expand...
Click to collapse
Try a different region other than Hong Kong.
Flash again stock with odin and check md5 before
rayman95 said:
Flash again stock with odin and check md5 before
Click to expand...
Click to collapse
Usually Odin checks the MD5 validity of the file before it begins anything. If he just gets stuck on cache, the MD5 check must have passed.
bligui said:
So today I was trying to update my phone to a newer version of 4.4.2 I downloaded N900ZSUDNG1_N900OZSDNG1_BRI also Odin v3.09, Odin detects my phone perfectly but flashing fails every time i tried 4 different USB ports and same thing at the end of flashing it says FAILED but i see no error on the log it goes all the way to where it writes CACHE it seems and then says FAILED any ideas as to what to do to recover my phone would be appreciated.
Click to expand...
Click to collapse
try a different usb cable, or use the original samsung cable that you got from the box...
nicholaschum said:
Try a different region other than Hong Kong.
Click to expand...
Click to collapse
Fixed thank you guys it was the actual file I downloaded the problem downloaded a different regions an all worked Ok, will mark as solved.
bligui said:
Fixed thank you guys it was the actual file I downloaded the problem downloaded a different regions an all worked Ok, will mark as solved.
Click to expand...
Click to collapse
Clicking thanks will suffice

[Q] 910F "bricked"

Hi
Flashed CM12 and all was good, but i didnt get 4G+ with it and couldnt get the gear s to connect. So i downloaded a file from sammobile to get it to 5.0.1. Started up odin3 v1.85 and it says failed everytime. on the cell it says "odin : invalid ext4 image" Anyone that could point me in the right direction? Trying to download an older version now 4.4.4 and that didnt work either... Someone please help me?
jiframnes said:
Hi
Flashed CM12 and all was good, but i didnt get 4G+ with it and couldnt get the gear s to connect. So i downloaded a file from sammobile to get it to 5.0.1. Started up odin3 v1.85 and it says failed everytime. on the cell it says "odin : invalid ext4 image" Anyone that could point me in the right direction? Trying to download an older version now 4.4.4 and that didnt work either... Someone please help me?
Click to expand...
Click to collapse
Have you tried hooking it up to your PC and using Kies recovery? Thats got me out of a couple of jams on Sumsung phones over the years.
Yeah, and it sits forever without connecting. . This sucks, i have to use my s6 edge and it sucks...
jiframnes said:
Yeah, and it sits forever without connecting. . This sucks, i have to use my s6 edge and it sucks...
Click to expand...
Click to collapse
Lol I wish I had an s6 as a "backup phone". Anyway, try a different version of Odin. 1.85 is way old. 3.07 & 3.09 work pretty well. Also try downloading the firmware again, perhaps some part of it got corrupted. If nothing else there is a flashable version of lollipop, you could flash it (or restore a TouchWiz backup if you have one) to get it back on TouchWiz and then Odin it. (Sometimes I've had trouble with Odin coming back from cm/aosp roms so I flashed a TW rom & Odin worked fine)
jiframnes said:
Hi
Flashed CM12 and all was good, but i didnt get 4G+ with it and couldnt get the gear s to connect. So i downloaded a file from sammobile to get it to 5.0.1. Started up odin3 v1.85 and it says failed everytime. on the cell it says "odin : invalid ext4 image" Anyone that could point me in the right direction? Trying to download an older version now 4.4.4 and that didnt work either... Someone please help me?
Click to expand...
Click to collapse
You never said u put the phone in Download mode...did you??? Cheers:fingers-crossed:
If not...remember power off...then...power+home+volume down all together...the open odin...3.09...
Take a look at my posts on page 3 of this thread.
http://forum.xda-developers.com/note-4/general/sm-n910f-official-roms-mega-links-t3091605/page3
It seems like your problem is the same as mine. Does Odin fail on the hidden.img.ext4 with an error about incorrect image size?
If it does, try flashing a ROM with your original CSC.
If that produces the same error, flash one with a smaller hidden.img.ext4 file. The BTU ROM seems to have a quite small one.
By the way, what's your original CSC?
Can i kiss you???
way forward
Can i flash 5.0.1 now or does it come OTA??

Categories

Resources