Database Users

[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.

need help guys at&t s4 brick. desperately

hi xda guys this is my story
i have an at&t samsung s4 on android 4.2 i have tried to update it via wifi to 4.4
but no use. a message appear say's " your device is up to date "
i have tied "loki way" it failed
i have tried "odin tool way' it failed it won't complete the process
i have tried samsung kais it fail's too a message says no update for this device
***** i managed to root the device
and then i found the safestrap apk i have insert the TWRP recovery
i have made a backup in case something go's wrong
and i have tries to flash a clean google s4 4.4.4 rom
**** and then the the phone stuck of samsung logo and vibrate often .the TWRP is lost
**** i have tried to recover the the via samsung kias it made it wors
now it have message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
i have tried via odin using the official firmware that i have downloaded. but did not work also
i have tried the kais recovery mode but i did not get the recovery code
help my friend what should i do
nead you help desperately

When you try Odin what fails? Are you using the mdl firmware? I assume you're on MDL? You haven't updated the firmware?
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app

jd1639 said:
When you try Odin what fails? Are you using the mdl firmware? I assume you're on MDL? You haven't updated the firmware?
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
Click to expand...
Click to collapse
Every time I have had and issue with a ROM or forget to flash loki I have no issues just ODIN back to 4.2.2 MDL. I say try it again.

MF3
jd1639 said:
When you try Odin what fails? Are you using the mdl firmware? I assume you're on MDL? You haven't updated the firmware?
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
Click to expand...
Click to collapse
yes my friend
the device firmware ends with MF3
i think it's MDL
it had a 4.2.2 official firmware
but i tried ti flash this rom using safestrap recovery : "GalaxyS4-CWM-6.0.4.4-GT-i9505.tar"
after that my device stuck in samsung logo screen with vibration
i hop hear from you soon

myounis said:
yes my friend
the device firmware ends with MF3
i think it's MDL
it had a 4.2.2 official firmware
but i tried ti flash this rom using safestrap recovery : "GalaxyS4-CWM-6.0.4.4-GT-i9505.tar"
after that my device stuck in samsung logo screen with vibration
i hop hear from you soon
Click to expand...
Click to collapse
YOU DONT FLASH .tar files in recovery ........... i9505 is not your device i337 is yours .. No wonder it bricked ...
this will unbrick your phone FOLLOW INSTRUCTIONS Exactly ... If you are on MF3 your bootloader is locked
http://forum.xda-developers.com/showthread.php?t=2663545
It in the second post ..Full Nb1 update .. Or Mk2 which ever you desire
GalaxyS4-CWM-6.0.4.4-GT-i9505.tar This is not a ROM its a recovery .. I suggest reading a lot more before proceeding .. Your device has a locked bootloader if firmware is MF3 ... Read the Q/A and much more it will save you a ton of time .. You need to flash device specific roms and recoveries else you are gonna crash and burn
If you are on MF3 like you said then you can only flash Safestrap compatible roms .. I need a little more info ???

myounis said:
yes my friend
the device firmware ends with MF3
i think it's MDL
it had a 4.2.2 official firmware
but i tried ti flash this rom using safestrap recovery : "GalaxyS4-CWM-6.0.4.4-GT-i9505.tar"
after that my device stuck in samsung logo screen with vibration
i hop hear from you soon
Click to expand...
Click to collapse
You are on mf3 firmware. Flashing the mdl firmware won't work. That's the problem you're having. I would recommend you upgrade and flash the nb1 tar file. Read this http://forum.xda-developers.com/showthread.php?p=53758227
Sent from my Nexus 5 using XDA Free mobile app

spirodave said:
YOU DONT FLASH .tar files in recovery ........... i9505 is not your device i337 is yours .. No wonder it bricked ...
this will unbrick your phone FOLLOW INSTRUCTIONS Exactly ... If you are on MF3 your bootloader is locked
http://forum.xda-developers.com/showthread.php?t=2663545
It in the second post ..Full Nb1 update .. Or Mk2 which ever you desire
GalaxyS4-CWM-6.0.4.4-GT-i9505.tar This is not a ROM its a recovery .. I suggest reading a lot more before proceeding .. Your device has a locked bootloader if firmware is MF3 ... Read the Q/A and much more it will save you a ton of time .. You need to flash device specific roms and recoveries else you are gonna crash and burn
If you are on MF3 like you said then you can only flash Safestrap compatible roms .. I need a little more info ???
Click to expand...
Click to collapse
yes my friend
sorry my misstake i have flashed this room : Danvdh-GE-4.4.4-07172014.zip

And it works--

rugmankc said:
And it works--
Click to expand...
Click to collapse
no my friend this rom made my device bootloop / brick
samsung logo only with vibration
***
i think onid is the answer
can any one link me an MF3 stock rom
to try??!!
i can't not find any

I think you missed something--
You can't run aosp roms at all
On MF3 only 4.3 afaik
As mentioned do a lot of reading in those threads before going on--saves headaches--:good:
Best would be to upgrade to NB1, those instructions are in those threads too--:good:

myounis said:
no my friend this rom made my device bootloop / brick
samsung logo only with vibration
***
i think onid is the answer
can any one link me an MF3 stock rom
to try??!!
i can't not find any
Click to expand...
Click to collapse
Im gonna save you a bunch of time ................You are on MF3 ...Your BootLoader is locked ... You can only flash Safe Strap Roms aka HyperDrive or GoldenEye based off stock .. You can only use safestrap to install recovery ... Anything else will render your device useless.
Check the General Section ... Send you a link isn't gonna help ... You need to read multiple threads ...CHECK THE GENERAL SECTION
LOCKED BOOTLOADER= NO AOSP ROMS = ONLY ROMS BASED OFF STOCK
LOOK FOR A THREAD IN THE GENERAL SECTION CALLED DEBRICK

thank for you help all
i have fix it
i have download this link :
https://mega.co.nz/#!WEEzSA7Z!aB46731_AwM7P83eMdDlmFYd1hUZfFBcQAZjc1X7wAE
from
http://forum.xda-developers.com/showthread.php?t=2502003
and flash it with oden
what a relief
:highfive:

myounis said:
thank for you help all
i have fix it
i have download this link :
https://mega.co.nz/#!WEEzSA7Z!aB46731_AwM7P83eMdDlmFYd1hUZfFBcQAZjc1X7wAE
from
http://forum.xda-developers.com/showthread.php?t=2502003
and flash it with oden
what a relief
:highfive:
Click to expand...
Click to collapse
:good::good::good:

Same issue but mk2 has me struggling
Sorry to hijack, but I didn't want to start a new thread on this same issue.
I have the AT&T S4 i337 , running MK2. I bought it used, and every time it boots up it shows "safestrap disabled" with 2 buttons below: recovery or system. Recovery button takes you to the TWRP recovery, the other button boots the phone. The phone worked well but the stock rom and bloat were killing me (my previous phones were rooted Epic and Relay). I wanted to root and flash a custom ROM but I wasn't aware of the locked bootloader and mk2/mf3 issues with this phone. Now I am soft bricked, and I've tried many ways to fix (odin, recovery flash,adb ), but it always fails. Here is my path, and what I've tried:
1. I rooted using Saferoot.
2. Tried to flash Philz Touch CWM from SD card in recovery (1st BIG mistake). Didn't work, but didn't brick either.
3. I saw guut13's index and ran backups on twrp recovery and on kies.
4. decided to update (before proceeding with a new rom). tried to OTA update, but it failed.
5. tried to install nb1 (stock odin tar) using heimdall (it couldn't find pit file) and odin (failed to complete write).
6. unrooted (hoping to fix update issues) and then tried Kies firmware upgrade. This process hung and I had to force quit. And thus began the soft brick.
This pattern repeated a few times:
7. flash stock mf3 tar with odin [Complete(Write) operation failed]
8. odin'd mk2 tar , then md1, then mf3 again, all fail to complete write.
9. Phone freezes and will only go into download mode (or bootloop).
10. the ONLY thing that odin can flash is a mj9 recovery file (sometimes). then recovery comes up, I wipe dalvik/cache/system (everything but the sd card) and fix permissions.
11. rinse and repeat. lol
12. I find a jflte pit file that will flash by odin.
13. I start trying stock tars again in odin, hoping the pit helps. same failure.
14. tried to odin an entire mf3 package (bootloader, modem, csc, the works). still same write fail.
15. the only file that flashes other than the pit, is a stock mk2 recovery file.
16. tried to slip a stock mk2 rom zip on my sd and flash from there... failed.
17. installed sdk and tried to sideload, but my computer won't recognize my S4. also can't run adb shell. (yes, i installed the platform tools, and opened prompt window from inside the platform tools folder). {perhaps my vmware fusion (Win8) running on my mac (OS 10.9) is causing a port id issue, but odin connects easily every time....hmm....}
18. Tried rubbing the phone against my head and laughing while trying not to cry, softly whispering "I hate your soul...."
19. Tried 5 different usb cables, including 2 blackberry cables that always connect other samsungs to odin.
20. tried factory reset thru stock recovery , which I can still reach by booting and holding volume up. odd note, this recovery says "i337ucufnb1".
So, I have tried odin-flashing every stock rom for i337 (mdl-nc1), but odin fails to write complete, and my phone says "bar 240, 400" or "sw rev check fail".
What can I try next? I can only think maybe to try using a different PC (not easy since I don't know anyone here but mac users) or smashing the phone under my tire..... would uninstalling safestrap help? I feel like theres a confilct between the stock nb1 recovery and safestrap..... but I can't get in the adb shell to delete it.
anyone had these write fails with odin before? I have always thought no matter what happens, I could always factory wipe and start over with a stock rom in odin, but now, the locksmith says no dice.
Thanks for any advice, I am sure I've forgotten a few details, but I hope I gave enough info for those who wish to assist. Thanks.

I would try to find a Windows pc and flash the nb1 tar in Odin
I'm assuming you're using this but if not it's what you want http://forum.xda-developers.com/showthread.php?p=50912149
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
I would try to find a Windows pc and flash the nb1 tar in Odin
Click to expand...
Click to collapse
yeah, 4 years ago I had trouble getting virtual pc's to let my mac and epic both speak odin. But I thought now that they connect easily (and flash pits and some recovery with no prob) it was a better match (as in , vmware's Windows 8, running on a 2.8ghz macbook pro).
What stinks is I have a real pc (old tower running xp) for exactly this purpose, but I never got a licensed version of windows on it and the crap I got off torrents doesnt work anymore. I hate the thought of buying a crap PC OS that I will only use once every 3 years.

Epiclectic said:
yeah, 4 years ago I had trouble getting virtual pc's to let my mac and epic both speak odin. But I thought now that they connect easily (and flash pits and some recovery with no prob) it was a better match (as in , vmware's Windows 8, running on a 2.8ghz macbook pro).
What stinks is I have a real pc (old tower running xp) for exactly this purpose, but I never got a licensed version of windows on it and the crap I got off torrents doesnt work anymore. I hate the thought of buying a crap PC OS that I will only use once every 3 years.
Click to expand...
Click to collapse
Yea, my 16 year old has a crap Mac now all he ever uses is my crap Windows pc to play his games. Go figure.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Yea, my 16 year old has a crap Mac now all he ever uses is my crap Windows pc to play his games. Go figure.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
For a wide selection of games (and upgradable graphics), PC has a definite edge over Mac. PC also has the advantage of being cheaper to buy and upgrade. If I were going to game all day or outfit 50+ employee workstations, PC would be the obvious choice. But for day to day, I still like the way Mac works, hands down. (Tho as PC improves, and Mac continues dumbing down for the masses, this gap is starting to shrink, much like the import vs domestic car market.)
If my old PC tower could run Win8, I would just buy a licensed copy and use that for Odin. But I'm pretty sure it's maxed out at xp, tho it might run vista really slowly, lol. My other option is to try bootcamp to boot up my macbook as an actual Win8 PC, but if that doesnt solve the Odin issues, then I've spent money on a microsoft product I can't even use. I like android phones' customizing options and layout better than iphone (no back button? wtf? lol), so unless android starts making latop OS, I guess I'm stuck in this Mac/android limbo...

Epiclectic said:
Sorry to hijack, but I didn't want to start a new thread on this same issue.
I have the AT&T S4 i337 , running MK2. I bought it used, and every time it boots up it shows "safestrap disabled" with 2 buttons below: recovery or system. Recovery button takes you to the TWRP recovery, the other button boots the phone. The phone worked well but the stock rom and bloat were killing me (my previous phones were rooted Epic and Relay). I wanted to root and flash a custom ROM but I wasn't aware of the locked bootloader and mk2/mf3 issues with this phone. Now I am soft bricked, and I've tried many ways to fix (odin, recovery flash,adb ), but it always fails. Here is my path, and what I've tried:
1. I rooted using Saferoot.
2. Tried to flash Philz Touch CWM from SD card in recovery (1st BIG mistake). Didn't work, but didn't brick either.
3. I saw guut13's index and ran backups on twrp recovery and on kies.
4. decided to update (before proceeding with a new rom). tried to OTA update, but it failed.
5. tried to install nb1 (stock odin tar) using heimdall (it couldn't find pit file) and odin (failed to complete write).
6. unrooted (hoping to fix update issues) and then tried Kies firmware upgrade. This process hung and I had to force quit. And thus began the soft brick.
This pattern repeated a few times:
7. flash stock mf3 tar with odin [Complete(Write) operation failed]
8. odin'd mk2 tar , then md1, then mf3 again, all fail to complete write.
9. Phone freezes and will only go into download mode (or bootloop).
10. the ONLY thing that odin can flash is a mj9 recovery file (sometimes). then recovery comes up, I wipe dalvik/cache/system (everything but the sd card) and fix permissions.
11. rinse and repeat. lol
12. I find a jflte pit file that will flash by odin.
13. I start trying stock tars again in odin, hoping the pit helps. same failure.
14. tried to odin an entire mf3 package (bootloader, modem, csc, the works). still same write fail.
15. the only file that flashes other than the pit, is a stock mk2 recovery file.
16. tried to slip a stock mk2 rom zip on my sd and flash from there... failed.
17. installed sdk and tried to sideload, but my computer won't recognize my S4. also can't run adb shell. (yes, i installed the platform tools, and opened prompt window from inside the platform tools folder). {perhaps my vmware fusion (Win8) running on my mac (OS 10.9) is causing a port id issue, but odin connects easily every time....hmm....}
18. Tried rubbing the phone against my head and laughing while trying not to cry, softly whispering "I hate your soul...."
19. Tried 5 different usb cables, including 2 blackberry cables that always connect other samsungs to odin.
20. tried factory reset thru stock recovery , which I can still reach by booting and holding volume up. odd note, this recovery says "i337ucufnb1".
So, I have tried odin-flashing every stock rom for i337 (mdl-nc1), but odin fails to write complete, and my phone says "bar 240, 400" or "sw rev check fail".
What can I try next? I can only think maybe to try using a different PC (not easy since I don't know anyone here but mac users) or smashing the phone under my tire..... would uninstalling safestrap help? I feel like theres a confilct between the stock nb1 recovery and safestrap..... but I can't get in the adb shell to delete it.
anyone had these write fails with odin before? I have always thought no matter what happens, I could always factory wipe and start over with a stock rom in odin, but now, the locksmith says no dice.
Thanks for any advice, I am sure I've forgotten a few details, but I hope I gave enough info for those who wish to assist. Thanks.
Click to expand...
Click to collapse
my friend
if the mk2 is the same mf3
then download this link : https://mega.co.nz/#!WEEzSA7Z!aB46731_AwM7P83eMdDlmFYd1hUZfFBcQAZjc1X7wAE
more details here : http://forum.xda-developers.com/showthread.php?t=2502003
place the 4 files in to odin
and flash them... it worked for me
and if not the same as mf3
look for mk2 ota update build from 4 files
it will reset you phone to factory firmware
i hop it will work for you

Epiclectic said:
For a wide selection of games (and upgradable graphics), PC has a definite edge over Mac. PC also has the advantage of being cheaper to buy and upgrade. If I were going to game all day or outfit 50+ employee workstations, PC would be the obvious choice. But for day to day, I still like the way Mac works, hands down. (Tho as PC improves, and Mac continues dumbing down for the masses, this gap is starting to shrink, much like the import vs domestic car market.)
If my old PC tower could run Win8, I would just buy a licensed copy and use that for Odin. But I'm pretty sure it's maxed out at xp, tho it might run vista really slowly, lol. My other option is to try bootcamp to boot up my macbook as an actual Win8 PC, but if that doesnt solve the Odin issues, then I've spent money on a microsoft product I can't even use. I like android phones' customizing options and layout better than iphone (no back button? wtf? lol), so unless android starts making latop OS, I guess I'm stuck in this Mac/android limbo...
Click to expand...
Click to collapse
Consider installing Win7. Licenses can be had cheaply or just install, use for couple days for Odin (before it license locks) then wipe...
Sent from my SAMSUNG-SGH-I337 using Tapatalk

[Q] How to install stock ROM on I9505

Hi,
Currently there is not much on the phone, at least nothing to start up. I had CM, but had to go back so I tried the guide posted on this forum. With little success. So now im not sure where I stand as the phone is in a state without a ROM. When I try to start up normally i get "firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
Anyone can help me with installing fresh stock Samsung ROM?
Thanks in advance!
Sincerely,
Tho_kva2

Which was your last stock rom bevor you installed cm?
And which stock rom did you try to flash after cm?
Did they had the same product key?
Was the flashing process successful or did odin say "fail"?
And how is your current knox status? 0x1?
Send from my Galaxy S4 using Tapatalk

Not sure, but my phone was up to date with the latest update from Samsung.
I first tried to use "Norway (telenor)" first as, and when that failed I tried "Norway 4.4.2" Both found in the second post of the Guide.
Product key?
Odin said Fail. I tried multiple times with different odin versions and with PIT file.
Is it the "Knox warranty void" is so 0x1

And the latest original firmware running on your phone was it a Norway (telenor) firmware?
With product key i meant the csc.
The old firmware and the one you want to flash now have to have the same csc, i guess.
You can also flash a custom recovery and try to wipe and then flash again.
Send from my Galaxy S4 using Tapatalk

I'm not sure what the original firmware was, but it was the stock firmware i got with the phone when i bought it + updates.
CSC is TEN (Norway)
I do not know how to do a custom recovery, im a total noob on this subject of flashing and modding phones. Got any kind of guide or directrions to point me in? Sorry for not knowing squat, but hope you or someone else here can help me!

Hi,
okay, before you flash a recovery, you can try to flash another firmware but it have to be android 4.4.2 norway TEN
Did you also follow this note here?
"Odin troubleshooting:*If Odin accidentally gives you "fail" try the following:
- Repeat procedure.
- Make sure that all actions of Kies are disabled from task manager.
- Change usb port.
- Try another usb cable (make sure it is the original).
- Try another Odin version.
- Uninstall and re-install driver.
- Use pit file.
- Try another computer."
When odin will continue failing then try this.
http://www.usp-forum.de/downloads.php?do=file&id=1531
This is a 4 part open Europe firmware. Try to flash it...First time without pit,when odin failed try with pit...
If nothing helped, then you can install a custom recovery.
You once installed a recovery, before you flashed CM, remember?
But I will look for a guide and the right files.
Send from my Galaxy S4 using Tapatalk

It worked with the European version! Cheers mate Oh, it was without the pit.
Atleast android is installed hehe. but keyboard keeps crashing so cant type anything, and I cant turn on wifi; I get "Security notice, your device's security has blocked an action that is not permitted. No further action is required" -Knox Notification Manager.?
Oh and I got no SIM card to try at the phone atm. will get it later
So waht should be the next step?

Did you rooted this firmware already?
Try to fullwipe again. I thought this message only pops up, when the devise is rooted and Knox still not deleted... mysterious
Send from my Galaxy S4 using Tapatalk

I did not root it. I will try to wipe
Edit:
****ed up. Tried flashing the same again, and it failed lol.. so now im back to where I was before the phone "worked" again.
So I think I should get a recovery. Any thought?

Lol that's crazy. Also tried 4 part with pit?
And when you flash a Norway firmware again? Maybe it will work now, i don't know what's going on there
http://forum.xda-developers.com/showthread.php?t=2397108
This is CWM recovery for i9505, you have to flash the .tar file with odin in PDA or AP. It's your choice, whether you install the touch or non touch version.
Edit: anything new?
Send from my Galaxy S4 using Tapatalk

[Q] (for me) unrecoverable softbrick

Guys, I need a hand here, as I hit a solid brick wall and no amount of scouring the forums helped me find a suitable solution.
Hardware involved:
Galaxy Note 3 N9005 that was running 4.4.2 (bought unlocked)
iMac with Yosemite and Parallels with Ubuntu and Windows 10 with Heimdall and Odin 3.09 installed
What I set out to do: root & install clockworkmod recovery with the ultimate goal to install Linux on Android. I had my previous Note 2 and LG P990 rooted too, so I was not entirely new to the procedure.
What I "achieved": Heimdall would not work at all due to a problem that apparently affects all Samsung 4.4.2 devices. So I got Parallels on my Mac and installed Windows 10 Technical Preview to run Odin. After several attempts I finally managed to got Odin to say "PASS" on the CF Auto-Root procedure. However, the phone would not boot anymore and always return to it's ODIN state. But I also succeeded to get Clockworkmod installed.
With that I installed Cyanogen, thinking to be able to get around the booting problem. I wasn't. Now when booting Cyanogen, I get a message that encryption was unsuccesful and the device needs to be restored.
I would like to comply and downloaded the stock files for restoring through Odin, but now even with the device in the proper ODIN download state, the phone is no longer recognized by the Software. Tried about a hundred times now with reboot etc. and nothing seems to work. Even KIES does note recognize the phone anymore.
I can enter CWM and Odin modes just fine. I just can't boot and I can't get it recognized by my Mac anymore. My best guess is I unintentionally screwed up the partition table / PIT file and now I can't restore it anymore.
I am at the end of the rope here and getting desperate, any suggestions (preferably step by step) would be most welcome!

psearcher said:
Guys, I need a hand here, as I hit a solid brick wall and no amount of scouring the forums helped me find a suitable solution.
Click to expand...
Click to collapse
It's very weird that in Download Mode Odin don't recognize your device. Remember that you need Kies 3 for android 4.4.2 and Kies 3 has to be completely closed for use ODIN.

Joku1981 said:
It's very weird that in Download Mode Odin don't recognize your device. Remember that you need Kies 3 for android 4.4.2 and Kies 3 has to be completely closed for use ODIN.
Click to expand...
Click to collapse
Ok, I tried on my Win Laptop from work now and Odin can recognize the Smartphone there. I will take it home on the weekend to go further.
However, a hasty try to flash the stock rom (Vodafone NL Lollipop) resulted in the same "encryption failed" error I had before. Any ideas what I am doing wrong?

psearcher said:
Ok, I tried on my Win Laptop from work now and Odin can recognize the Smartphone there. I will take it home on the weekend to go further.
However, a hasty try to flash the stock rom (Vodafone NL Lollipop) resulted in the same "encryption failed" error I had before. Any ideas what I am doing wrong?
Click to expand...
Click to collapse
Your phone is unlocked. You had to try the POLAND Lollipop firmware or wait till future udpates.

Joku1981 said:
Your phone is unlocked. You had to try the POLAND Lollipop firmware or wait till future udpates.
Click to expand...
Click to collapse
Hi there Joku!
Just tried the Polish Lollipop Firmware and it still keeps displaying the "Encryption failed" error. It looks like it does not matter which file I flash, it will keep showing the same error.
Like I said, I believe I somehow broke the PIT file of the phone. Any ideas how to fix this?
Regards,
Rene

Try this pit file.
https://meocloud.pt/link/4ebb315a-867c-4469-bfdf-c234ca9f4d1e/PIT-File-DBT VFG-UK-MSM8974.zip/
Put it on pit field. Set repartition on and auto reboot. If all goes well then try to flash the Vodafone NL 4.4.2 rom (it's the one I use so I know that this pit file works with it).
Sent from my SM-N9005
---------- Post added at 09:42 PM ---------- Previous post was at 09:38 PM ----------
If it doesn't work try to go in TWRP and wipe the /data partition and then reflash the stock rom.
Sent from my SM-N9005

Question solved!
DeuXGod said:
Try this pit file.
Put it on pit field. Set repartition on and auto reboot. If all goes well then try to flash the Vodafone NL 4.4.2 rom (it's the one I use so I know that this pit file works with it).
Sent from my SM-N9005
---------- Post added at 09:42 PM ---------- Previous post was at 09:38 PM ----------
If it doesn't work try to go in TWRP and wipe the /data partition and then reflash the stock rom.
Sent from my SM-N9005
Click to expand...
Click to collapse
Thanks DeuXGod, but by now I more or less stumbled on the solution by trial and error. I'll post it here, hoping that somebody may benefit from my endeavours in the future. As a n00b I can't post links though. Sorry for that.
I do not know if all the steps are necessary or correct, but in the end they did lead me back to a working device. :fingers-crossed:
After trying a few PIT files here in the forums, the problems did not go away. Some of them would lead to a phone that just got stuck at the "Samsung" screen and would not fully boot up.
So I got the idea to flash back the "old" Dutch 4.4.2 ROM, which I downloaded from Sammobile and flashed in ODIN. After booting it showed a bit of a different error message, saying the file system was corrupted
I googled for this and stumbled on a small ZIP file that is supposed to fix "cannot mount DATA / EFS errors". I loaded this on my SDXC.
Flashed aforementioned ZIP file through the recovery from the SDXC.
After rebooting it still showed the same error, so I got back to recovery, did a factory reset and a cache wipe.
Another reboot and much to my surprise (and great relief) the phone booted up normally again!
From there I thought that if this worked, the Polish 5.0 should work too. I flashed it. Flashed CF Auto Root after that and everything seems to be working fine!
I set everything up and the phone is now restoring the apps etc. So far looking very good!

Restore not working for me

Hi Everyone I'm not even sure if anyone is going to reply to this but heres the deal. yesterday i flashed a custom rom to my phone s4 (sgh-i337m unlocked carrier) i have twrp3 installed for custom restore and i did make a restore file when my phone was still on lollipop, and i think that the backup worked because the boot screen is back to stock but now heres my issue, i power up my phone i get past the "galaxy s4" screen but get stuck on the samsung animation, i gave up on it after it sitting there for 2 hours then i removed the battery and then flash installed 7.x nougut onto it, but cant get playstore but thats just minor but what i do want is to go back to full stock no root, i feel that ive made a mistake and im just not comfortable with it anymore even if i loose all my stuff thats fine ive had the phone for a week, i do have odin on my computer but dont know how to use it because theres icons like bl, ap, cp and csc i dont know what those are well i know ap for installing twrp. I'm needing help like yesterday

You will have to download the stock ROM and flash it with Odin. Stock ROMs can be downloaded from sammobile.com, but download speeds are slow for non-premium users.
Flash guides can be found with everywhere.

Confirm that the model # is sgh-i337m in download mode. If it is, do this:
download Odin 3.07: https://www.google.ca/url?sa=t&rct=...168421&usg=AFQjCNHMbaSWjgVwWQGtMVr1TvJSsXWUcA
download the latest 5.01 firmware from here: https://www.sammobile.com/firmwares/galaxy-s4/SGH-I337M/BMC/download/I337MVLSGQB1/125370/ (This is for Bell but it doesn't matter because Rogers, Bell, Telus, Koodo, and Fido use the same ROM with some minor carrier customization). Unzip the file once to create a tar.md5 file;
put the phone into download mode;
open Odin and click on PDA, select the tar.md5 file;
connect the phone to the computer using the original Samsung USB cable;
uncheck everything except f reset time and flash the phone;
when you see the word RESET in the status window, remove the USB cable from the phone, remove the battery, replace the battery; boot the phone into recovery mode, factory reset, and reboot.
How to get into download mode: https://www.youtube.com/watch?v=7nC2vX492wI
How to get into recovery mode: https://www.youtube.com/watch?v=LkrUVSxGW9g
The correct forum for the sgh-i337m is here: https://forum.xda-developers.com/galaxy-s4-att

audit13 said:
Confirm that the model # is sgh-i337m in download mode. If it is, do this:
download Odin 3.07: https://www.google.ca/url?sa=t&rct=...168421&usg=AFQjCNHMbaSWjgVwWQGtMVr1TvJSsXWUcA
download the latest 5.01 firmware from here: https://www.sammobile.com/firmwares/galaxy-s4/SGH-I337M/BMC/download/I337MVLSGQB1/125370/ (This is for Bell but it doesn't matter because Rogers, Bell, Telus, Koodo, and Fido use the same ROM with some minor carrier customization). Unzip the file once to create a tar.md5 file;
put the phone into download mode;
open Odin and click on PDA, select the tar.md5 file;
connect the phone to the computer using the original Samsung USB cable;
uncheck everything except f reset time and flash the phone;
when you see the word RESET in the status window, remove the USB cable from the phone, remove the battery, replace the battery; boot the phone into recovery mode, factory reset, and reboot.
How to get into download mode: https://www.youtube.com/watch?v=7nC2vX492wI
How to get into recovery mode: https://www.youtube.com/watch?v=LkrUVSxGW9g
The correct forum for the sgh-i337m is here: https://forum.xda-developers.com/galaxy-s4-att
Click to expand...
Click to collapse
Thankyou i did fully verify everything before hand and yes it is sgh-i337m i actually got a different rom fully working and i do thank all users that did view and help me out. I did find a way to get gapps installed wothout issues. I still cant restore the device back to stock but i actually bought a replacement stock phone and use this one that were communicating on now. So now i have two phones completely identical minus the fact that one is unlocked from at&t and the other was never locked to anything.

Pwnycorn said:
You will have to download the stock ROM and flash it with Odin. Stock ROMs can be downloaded from sammobile.com, but download speeds are slow for non-premium users.
Flash guides can be found with everywhere.
Click to expand...
Click to collapse
Took a while but finally acquired 2 stock roms one telus and one sasktel. I will probably do a rom swap one day

The non-aws version of the s4 sold in Canada is the sgh-i337m. You can cross flash roms from any carrier as they are all the same except for a bit of customisation by adding their own apps.
A quick download source is updato.com.
Btw, the Canadian s4 forum is here: https://forum.xda-developers.com/galaxy-s4-att

I'm stuck also on the samsung animation screen, and flashing a stock rom does nothing for me it's stuck. I can't even go into stock recovery. everytime i do try it just say recovery booting and loops back into samsung screen. is there any way to fix this?

Thanks I'm new to the site and didn't know there was a Canadian s4 forum, I thought it was a specific device forum because my phone isn't att because att is not active on my area, we have telus, koodo, rogers, sasktel and bell

SPheDaGhost said:
I'm stuck also on the samsung animation screen, and flashing a stock rom does nothing for me it's stuck. I can't even go into stock recovery. everytime i do try it just say recovery booting and loops back into samsung screen. is there any way to fix this?
Click to expand...
Click to collapse
One thing I did because I was in the same boat and it sounds like your stuck in a soft boot is download lots of roms to a SD card and trial and error, use the latest version of twrp and flash the first version of twrp to the phone with Odin there's lots of YouTube videos to assist you, also when using a custom rom (in my experience) is that you also have to download gapps to gain the full google/android experience and it's safer to download apps with Google playstore compared to using a browser. Also when flashing remember to wipe catche and delvic before rebooting. Hope this helps and if your using the same kinda device as me I'd recommend the 7.1.2 rom by JDC it works pretty good and it feels like the s8