Database Users

really need help. think I really did it

So I tried alot of ways to root my samsung galaxy s4 I337. After multiple attempts I got it to root. With the program called: kingo android root
I wanted to put cm10 on here but I needed a custom recovery i tried odin to put twrp on and It kept on failing giving me errors over and over.
so I found a program called: casual that did a root and custom recovery.
well after that it said reboot. So It did and then It got to odin downloading saying error cant normal boot.
I cant restore my phone, get into recovery, the only way I can get on my phone is if I press power down and the home button. Then it boots up.i want it to be fixed without going through all this haggle.
is there anyway besides kies cuz that aint working to fix my phone.
I check root checker basic and I am no longer rooted.
like I said odin is not working for my phone for whatever reason.
maybe if I wait for 4.3 on the 13th and do the ota update will that help.
im so lost please help me someone.

Need to know what firmware you're on. Mf3? Most likely

This might work, but it will delete everything on your phone and reset it. I hope this works :fingers-crossed:
Follow these steps (On your own risk):
1) get on your phone
2) Make sure you have unknown sources enabled (Settings--More--Security--Unknown Sources)
3) install Safestrap 3.62 (download given below)
4) Open app and click "Install Recovery"
5) then press "Reboot to Recovery"
6) It should boot into Safestrap, if not then turn off your phone and the boot it up as you would to use it and then click the menu button on the phone.
7) Then click Wipe
8) Swipe to Factory Reset
9) Reboot
10) Enjoy!

mrwilson1991 said:
So I tried alot of ways to root my samsung galaxy s4 I337. After multiple attempts I got it to root. With the program called: kingo android root
I wanted to put cm10 on here but I needed a custom recovery i tried odin to put twrp on and It kept on failing giving me errors over and over.
so I found a program called: casual that did a root and custom recovery.
well after that it said reboot. So It did and then It got to odin downloading saying error cant normal boot.
I cant restore my phone, get into recovery, the only way I can get on my phone is if I press power down and the home button. Then it boots up.i want it to be fixed without going through all this haggle.
is there anyway besides kies cuz that aint working to fix my phone.
I check root checker basic and I am no longer rooted.
like I said odin is not working for my phone for whatever reason.
maybe if I wait for 4.3 on the 13th and do the ota update will that help.
im so lost please help me someone.
Click to expand...
Click to collapse
You are most probably on MF3, therefore you cannot install TWRP or CWM recoveries. You can only use Safestrap as of right now.

jd1639 said:
Need to know what firmware you're on. Mf3? Most likely
Click to expand...
Click to collapse
firmware 4.2.2. originally. but after doing whatever I did and connecting to kies it says: Current Firmware version: PDA:MF3 / PHONE:MF3 / CSC:MF3 (ATT)
I am going to try safestrap and let you guys know if it worked.

installed safestrap... had to re-root with kingo did re-root. and did a factory wipe. ok so if i cant use twrp. how should I go along installing cm10 rom?

mrwilson1991 said:
installed safestrap... had to re-root with kingo did re-root. and did a factory wipe. ok so if i cant use twrp. how should I go along installing cm10 rom?
Click to expand...
Click to collapse
You can't install Cyanogenmod. Read through the Safestrap thread and the Q/A thread to see what works.
Sent from my SGH-I337 running Foxhound 2.0

mrwilson1991 said:
installed safestrap... had to re-root with kingo did re-root. and did a factory wipe. ok so if i cant use twrp. how should I go along installing cm10 rom?
Click to expand...
Click to collapse
You can't. On MF3 you cannot run AOSP/AOKP/CM/MIUI based roms. Only custom TW.
Sent from my SGH-I337 using XDA Premium 4 mobile app

mrwilson1991 said:
installed safestrap... had to re-root with kingo did re-root. and did a factory wipe. ok so if i cant use twrp. how should I go along installing cm10 rom?
Click to expand...
Click to collapse
You can only use the roms listed in this thread

Thanks guys,
This means a lot with the help. Now if I can get the WiFi to work on the hyperdrive rom. I'll be good as gold tell y'all what from. Going from a jailbreak iOS themer to android rooting user. It's very different and a lot of looking into and reading.
Now back into looking to get this WiFi to work. Just wanted to say thanks

Did you flash the ATT compatibility package zip that you should have downloaded along side of the Hyperdrive rom ,after those two zips did you flash the MF3 kernel module zip.
I use the Hyperdrive rom now and don't have any issues
Sent from my ATT S4 MF3 using Tapatalk

jball said:
Did you flash the ATT compatibility package zip that you should have downloaded along side of the Hyperdrive rom ,after those two zips did you flash the MF3 kernel module zip.
I use the Hyperdrive rom now and don't have any issues
Sent from my ATT S4 MF3 using Tapatalk
Click to expand...
Click to collapse
no i only installed the hyperdrive rom. I am not sure what to do for the rest.

mrwilson1991 said:
no i only installed the hyperdrive rom. I am not sure what to do for the rest.
Click to expand...
Click to collapse
When you downloaded the rom it is in the same page. You need the compatibility package and the MF3 kernel module on Safestrap for it to work right.go back to the Hyperdrive thread and search for it
Sent from my ATT S4 MF3 using Tapatalk

Use Odin and the files here
Just went through this myself and I'm back and running
http://forum.xda-developers.com/showthread.php?t=2502003
You can root with kingo fine, I rooted again right after recovering but do not install any recovery like twrp or clockwork
Sucks but it's how it is
Sent from my Nexus 7 using xda app-developers app

tevil said:
Use Odin and the files here
Just went through this myself and I'm back and running
http://forum.xda-developers.com/showthread.php?t=2502003
You can root with kingo fine, I rooted again right after recovering but do not install any recovery like twrp or clockwork
Sucks but it's how it is
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
here is my issue now.
I rooted with kinggo android root. Then for custom recover I have Safestrap. I rooted to see what all i could do but after trying different Roms I have noticed I don't care. Much for it.
I unrooted via the kinggo app. And verified with root checker.
But i want to go back to full stock. I noticed Safestrap is still there running in background. But the custom logo is gone.
I just want to go back to stock and have nothing to do with root.
I used the code to remove safestrap. and used kingo to unroot. but when I get the offical files for odin and try to push them into my phone. yes I am in download mode when I enter download mode i get:
odin mode
product name: SGH - 1337
current binary: Samsung official
system status: official
CSB-CONFIG-LSB: 0X30
write protection enabled
when I enter odin put thi the tar file for 4.2.2 I get a pass then a fail. the message log says: <ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and then there is this in red on my phone:
start [224, 1440]
SW REV. CHECK FAIL : fused : 2, Binary : 1
I know I changed the topic. but after thinking there is really nothing that bennifets me with being rooted. and personally I would rather be stock.
can you guys please help.

[Q] Custom recovery on Galaxy s4 AT&T

Hello. I have a rooted AT&T Samsung Galaxy s4 running 4.2.2. I am trying to flash cyanogenmod11 and have had no luck even loading a recovery. I first tried to flash twrp 2.6.3.1 from GooManager. It said that it flashed successfully, but when I tried to boot into recovery, it looked like it was in download mode and I got the message:
Could not do normal boot.
ODIN MODE
PRODUCT NAME: SGH-I337
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
CSB-CONFIG-LISB: 0X30
WRITE PROTECTION: Enable
The only way I can get out of this mode is by pulling the battery, going into download mode, then pressing cancel. I tried the same thing with ROMManager using both CWM and TWRP. Same problem.
Does anyone have this problem or know how to fix it?
Thanks!

You're kidding right? Do some reading.

I have read up on this, but there's nothing I can find that works. Everywhere just tells me how to get it into the OS, not how I can load a ROM.
jd1639 said:
You're kidding right? Do some reading.
Click to expand...
Click to collapse

gradymcd said:
I have read up on this, but there's nothing I can find that works. Everywhere just tells me how to get it into the OS, not how I can load a ROM.
Click to expand...
Click to collapse
Look for mf3 and safestrap

gradymcd said:
Hello. I have a rooted AT&T Samsung Galaxy s4 running 4.2.2. I am trying to flash cyanogenmod11 and have had no luck even loading a recovery. I first tried to flash twrp 2.6.3.1 from GooManager. It said that it flashed successfully, but when I tried to boot into recovery, it looked like it was in download mode and I got the message:
Could not do normal boot.
ODIN MODE
PRODUCT NAME: SGH-I337
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
CSB-CONFIG-LISB: 0X30
WRITE PROTECTION: Enable
The only way I can get out of this mode is by pulling the battery, going into download mode, then pressing cancel. I tried the same thing with ROMManager using both CWM and TWRP. Same problem.
Does anyone have this problem or know how to fix it?
Thanks!
Click to expand...
Click to collapse
Where are all these noobs coming from just having phones that are already magically rooted and just automatically think they can flash a custom recovery. Great you just lost your stock recovery..... But no fear, search mf3 md5 files. flash it fresh through odin 1.75 and then root not using a one click. You don't deserve root if you can't format a card and run a few simple terminal commands.... Just my opinion. Oh is your gs4 red also....?
---------- Post added at 05:20 PM ---------- Previous post was at 05:11 PM ----------
Here is a little tut I wrote some time ago. Providing everything for you besides the main files you'll need so you'll learn how to search.
You should realy read.... All of us on MF3 know that !!... That was one of the fist ways to boot back up. Safe strap is going to be a savior for you.... Basically this has been discussed a million times..... If you are on MF3 you cannot downgrade you can only upgrade or stay on MF3, If you want 4.3 sooooo bad I will link it for you. But I suggest staying patient. There is nothing really that improved over 4.2.2. So I would advise you not to upgrade but I will post the links and tell you how to do it. One if you were smart you would have made a nandroid backup thru SS and then when you boot into that you stay on the stock rom slot. Hit then go in and write your backup just the system folder.... So you won't lose all of your data. Now if you didn't make a nandroid backup. Then you can try flashing the stock recovery and fixing the permissions thru safe strap..... IF that doesn't work well you are just up the creek.....
HAHAHAHA. JK Get odin and get the MF3 Tar.MD5 files But your phone manually into odin mode and Go back to stock MF3. Seriously read, read, read. I will make it real easy for you this time. By posting links but you are just asking for it. So first grab these files: https://mega.co.nz/#!WEEzSA7Z!aB46731_AwM7P83eMdDlmFYd1hUZfFBcQAZjc1X7wAE These are the stock MF3 files that were contributed to the community by Shockndrop: http://forum.xda-developers.com/showthread.php?t=2502003
Now grab Odin, I prefer this one: ODIN 1.85 http://forum.xda-developers.com/showthread.php?t=1262272
Now put the MD5 files in their proper places in odin and and hook your phone up with a Good **** Solid Universal Serial Bus Cable: Like pitured here:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Put her down into a coma AKA, ODIN Recovery mode manualy by holding power, home, and volume down. Then when prompt after the warning volume up to continue. Flash with Odin to restore to stock MF3. Brand Spaking new!!!!
Use your favorite root Method, New root method is the only one we support here on XDA, Which involves an SD Card,and the Terminal from the Play store. Or if you want the fast and dirty way because you are lazy do the Kingo root, I don't indorse it, but I have yet to hear anything negative about it, other than speculation. Links: http://www.kingoapp.com/android-root/download.htm - one click method Easy.
Old proper way: Quoting Jortex "HOWTO:
Use a card reader to format the micro SD card to exFAT (FAT32 or other formats does not work) in Windows. I haven't tried Linux or MacOS X, so they may not work.
Download the attached file (Root_for_ATTSG4_FM3.rar) http://forum.xda-developers.com/attachment.php?attachmentid=2165629&d=1375669716 and extract it into the root of your EXTERNAL microSD card using the card reader in Windows. (You can do the extraction using WinRAR, http://www.rarlab.com/download.htm or 7-zip, http://www.7-zip.org/download.html ).
Put the SD card back to the phone and download the Android Terminal Emulator app.
Open the Terminal Emulator app and run below 3 commands:
Code:
cd /mnt/extSdCard
./pwn
./script.sh
Then, open SuperSU and check everything looks good.
Then open a root app and it should be working properly.
Reboot your device once to confirm root is still working after reboot.
Come back to the post and press the THANKS button
Notes:
I uploaded a screenshot from the Terminal screen where the instructions are entered. Yours should be the same except you don't need to enter the "ls -l" command. It's just to show what files I have on the SD card. Ignore LOST.DIR directory.
Remove any SuperSU apps from your phone before following the above steps. script.sh installs it automatically.
You can use adb shell instead of a terminal app which is more convenient but requires Android SDK. Follow these steps only if you are about to use adb:
Download and install all Samsung Galaxy S 4 drivers from here: http://www.samsung.com/us/support/owners/product/SGH-I337ZWAATT#
Activate Developer options -> USB Debugging mode. To have the phone show the Developer options, go to Settings -> More -> About device. Tap on "Build number" 6 times.
You have to use an external SD card. No other alternative have been found yet. Using the device storage, i.e. /mnt/sdcard, or /data/local/tmp, DOES NOT work.
Warning (suggested by rushi.1986): "We have root for MF3 but we neither have a working recovery, nor an ODIN back to stock package. Be very careful what you do with your root. At this point, there is no way to recover even from a soft brick. (unless you know exactly what caused the soft brick and can correct it using adb)"
For those who do not know how to format an SD card on Windows (thanks to jee'sgalaxy):
Insert the micro SD into the computer (may have to use a reader or a micro SD adapter).
Go to "My Computer".
Right click on your SD card that showed up.
Click Format.
Choose exFAT as the format.
Click "OK".
Don't forget to press the THANKS button.
Credits:
***Exploit adapted for AT&T by Jortex***
***Original Guide by Open1Your1Eyes0 for Verizon Galaxy S 4***
***Original Exploit by DooMLoRD***
Next install your only way as of now to run custom roms period in your current situation and you should be incredibly grateful instead of saying that you want 4.3 soooooo bad....... really not tooo many benefits at all. Now 4.4 KittyKit lol is a different story..... So grab the latest and greatest version of safestrap from here: http://forum.xda-developers.com/devdb/project/dl/?id=1814&task=get
After Flashing Any Compatable Rom flash these every time Link: http://forum.xda-developers.com/devdb/project/dl/?id=508
They are the MF3 modules you will need them for wifi to work.
Transfer to sd card install just as you would a regular unknown source APK File..... Tick that in settings Security tab. Also hit your build number 20 times to unlock developer options and always have usb debugging on.
Now boot into safe-strap and dump a nandroid backup and you will be good to go. All thanks to the HashMan aka HashCode, And his sexifing SS. Okay now that you have a backup do anything of your hearts content. Just don't be fooling around with the bootloaders code.... this can really turn your cell phone into a paper weight.
Now here is a list of known compatable roms with SS:
Confirmed working ROMs Thanks to graydiggy http://forum.xda-developers.com/showthread.php?t=2428254
Google Play Edition 4.2.2
http://forum.xda-developers.com/showthread.php?t=2356276
http://forum.xda-developers.com/showthread.php?t=2341376
Deadly Venom
SHOStock
Darth Stalker
Graviton (Installs fine for some, will not install for others)
Goldeneye (May have issues)
Wicked ROM (T-Mobile) Input correct APN and change network mode to Auto LTE/GSM Will most likely lose root.
All Infamous TW Roms should work
Input correct APN settings for non AT&T ROMs (ie i9505 ROMs) to get LTE
Omega ROM i9505
Echo ROM i9505
Vision X i9505
BoBCaTROM i9505 (May not need to change APN)
Hyperdrive ROM. (May not be able to send SMS while on LTE)
Grab one create a rom slot and flash to your hearts content.
As for the 4.3 Odin files...... I think you can find them yourself it would be ignorant for me to post them for you.

You are right. I am a newb at this. My last phone was a Motorola Triumph, and I had no problems flashing ROMs on that. So I would flash the md5 file (d-h.st/AuY) through odin 1.75 and then flash CWM? My phone is white. Didn't even know they made it in red.
Thank!
JohnMonsour said:
Where are all these noobs coming from just having phones that are already magically rooted and just automatically think they can flash a custom recovery. Great you just lost your stock recovery..... But no fear, search mf3 md5 files. flash it fresh through odin 1.75 and then root not using a one click. You don't deserve root if you can't format a card and run a few simple terminal commands.... Just my opinion. Oh is your gs4 red also....?
Click to expand...
Click to collapse

gradymcd said:
You are right. I am a newb at this. My last phone was a Motorola Triumph, and I had no problems flashing ROMs on that. So I would flash the md5 file (d-h.st/AuY) through odin 1.75 and then flash CWM? My phone is white. Didn't even know they made it in red.
Thank!
Click to expand...
Click to collapse
I was just giving you a hard time... LOL. That is why we are here is to help not bring you down. I remember my first line of code.... Boy! jk. Any questions. v 1.85 works best for me. But just make sure you have a very good usb cable and strong connection. I have bricked a phone with Odin on MF3.

Are the only supported ROMs the ones listed, because I want to flash the cm11 nightly for KitKat?
JohnMonsour said:
Where are all these noobs coming from just having phones that are already magically rooted and just automatically think they can flash a custom recovery. Great you just lost your stock recovery..... But no fear, search mf3 md5 files. flash it fresh through odin 1.75 and then root not using a one click. You don't deserve root if you can't format a card and run a few simple terminal commands.... Just my opinion. Oh is your gs4 red also....?
---------- Post added at 05:20 PM ---------- Previous post was at 05:11 PM ----------
Here is a little tut I wrote some time ago. Providing everything for you besides the main files you'll need so you'll learn how to search.
You should realy read.... All of us on MF3 know that !!... That was one of the fist ways to boot back up. Safe strap is going to be a savior for you.... Basically this has been discussed a million times..... If you are on MF3 you cannot downgrade you can only upgrade or stay on MF3, If you want 4.3 sooooo bad I will link it for you. But I suggest staying patient. There is nothing really that improved over 4.2.2. So I would advise you not to upgrade but I will post the links and tell you how to do it. One if you were smart you would have made a nandroid backup thru SS and then when you boot into that you stay on the stock rom slot. Hit then go in and write your backup just the system folder.... So you won't lose all of your data. Now if you didn't make a nandroid backup. Then you can try flashing the stock recovery and fixing the permissions thru safe strap..... IF that doesn't work well you are just up the creek.....
HAHAHAHA. JK Get odin and get the MF3 Tar.MD5 files But your phone manually into odin mode and Go back to stock MF3. Seriously read, read, read. I will make it real easy for you this time. By posting links but you are just asking for it. So first grab these files: https://mega.co.nz/#!WEEzSA7Z!aB46731_AwM7P83eMdDlmFYd1hUZfFBcQAZjc1X7wAE These are the stock MF3 files that were contributed to the community by Shockndrop: http://forum.xda-developers.com/showthread.php?t=2502003
Now grab Odin, I prefer this one: ODIN 1.85 http://forum.xda-developers.com/showthread.php?t=1262272
Now put the MD5 files in their proper places in odin and and hook your phone up with a Good **** Solid Universal Serial Bus Cable: Like pitured here:
Put her down into a coma AKA, ODIN Recovery mode manualy by holding power, home, and volume down. Then when prompt after the warning volume up to continue. Flash with Odin to restore to stock MF3. Brand Spaking new!!!!
Use your favorite root Method, New root method is the only one we support here on XDA, Which involves an SD Card,and the Terminal from the Play store. Or if you want the fast and dirty way because you are lazy do the Kingo root, I don't indorse it, but I have yet to hear anything negative about it, other than speculation. Links: http://www.kingoapp.com/android-root/download.htm - one click method Easy.
Old proper way: Quoting Jortex "HOWTO:
Use a card reader to format the micro SD card to exFAT (FAT32 or other formats does not work) in Windows. I haven't tried Linux or MacOS X, so they may not work.
Download the attached file (Root_for_ATTSG4_FM3.rar) http://forum.xda-developers.com/attachment.php?attachmentid=2165629&d=1375669716 and extract it into the root of your EXTERNAL microSD card using the card reader in Windows. (You can do the extraction using WinRAR, http://www.rarlab.com/download.htm or 7-zip, http://www.7-zip.org/download.html ).
Put the SD card back to the phone and download the Android Terminal Emulator app.
Open the Terminal Emulator app and run below 3 commands:
Code:
cd /mnt/extSdCard
./pwn
./script.sh
Then, open SuperSU and check everything looks good.
Then open a root app and it should be working properly.
Reboot your device once to confirm root is still working after reboot.
Come back to the post and press the THANKS button
Notes:
I uploaded a screenshot from the Terminal screen where the instructions are entered. Yours should be the same except you don't need to enter the "ls -l" command. It's just to show what files I have on the SD card. Ignore LOST.DIR directory.
Remove any SuperSU apps from your phone before following the above steps. script.sh installs it automatically.
You can use adb shell instead of a terminal app which is more convenient but requires Android SDK. Follow these steps only if you are about to use adb:
Download and install all Samsung Galaxy S 4 drivers from here: http://www.samsung.com/us/support/owners/product/SGH-I337ZWAATT#
Activate Developer options -> USB Debugging mode. To have the phone show the Developer options, go to Settings -> More -> About device. Tap on "Build number" 6 times.
You have to use an external SD card. No other alternative have been found yet. Using the device storage, i.e. /mnt/sdcard, or /data/local/tmp, DOES NOT work.
Warning (suggested by rushi.1986): "We have root for MF3 but we neither have a working recovery, nor an ODIN back to stock package. Be very careful what you do with your root. At this point, there is no way to recover even from a soft brick. (unless you know exactly what caused the soft brick and can correct it using adb)"
For those who do not know how to format an SD card on Windows (thanks to jee'sgalaxy):
Insert the micro SD into the computer (may have to use a reader or a micro SD adapter).
Go to "My Computer".
Right click on your SD card that showed up.
Click Format.
Choose exFAT as the format.
Click "OK".
Don't forget to press the THANKS button.
Credits:
***Exploit adapted for AT&T by Jortex***
***Original Guide by Open1Your1Eyes0 for Verizon Galaxy S 4***
***Original Exploit by DooMLoRD***
Next install your only way as of now to run custom roms period in your current situation and you should be incredibly grateful instead of saying that you want 4.3 soooooo bad....... really not tooo many benefits at all. Now 4.4 KittyKit lol is a different story..... So grab the latest and greatest version of safestrap from here: http://forum.xda-developers.com/devdb/project/dl/?id=1814&task=get
After Flashing Any Compatable Rom flash these every time Link: http://forum.xda-developers.com/devdb/project/dl/?id=508
They are the MF3 modules you will need them for wifi to work.
Transfer to sd card install just as you would a regular unknown source APK File..... Tick that in settings Security tab. Also hit your build number 20 times to unlock developer options and always have usb debugging on.
Now boot into safe-strap and dump a nandroid backup and you will be good to go. All thanks to the HashMan aka HashCode, And his sexifing SS. Okay now that you have a backup do anything of your hearts content. Just don't be fooling around with the bootloaders code.... this can really turn your cell phone into a paper weight.
Now here is a list of known compatable roms with SS:
Confirmed working ROMs Thanks to graydiggy http://forum.xda-developers.com/showthread.php?t=2428254
Google Play Edition 4.2.2
http://forum.xda-developers.com/showthread.php?t=2356276
http://forum.xda-developers.com/showthread.php?t=2341376
Deadly Venom
SHOStock
Darth Stalker
Graviton (Installs fine for some, will not install for others)
Goldeneye (May have issues)
Wicked ROM (T-Mobile) Input correct APN and change network mode to Auto LTE/GSM Will most likely lose root.
All Infamous TW Roms should work
Input correct APN settings for non AT&T ROMs (ie i9505 ROMs) to get LTE
Omega ROM i9505
Echo ROM i9505
Vision X i9505
BoBCaTROM i9505 (May not need to change APN)
Hyperdrive ROM. (May not be able to send SMS while on LTE)
Grab one create a rom slot and flash to your hearts content.
As for the 4.3 Odin files...... I think you can find them yourself it would be ignorant for me to post them for you.
Click to expand...
Click to collapse

gradymcd said:
Are the only supported ROMs the ones listed, because I want to flash the cm11 nightly for KitKat?
Click to expand...
Click to collapse
Only SafeStrap recovery works with MF3 4.2.2. Currently there is a test going on for 4.3 MK2. It only flashes 4.2.2 if on MF3 or 4.3 on MK2. Only Touchwiz roms can be flashed although certain GE roms also do work.
You wont be able to flash kitkat roms or any aosp roms sadly.

Kaze105 said:
Only SafeStrap recovery works with MF3 4.2.2. Currently there is a test going on for 4.3 MK2. It only flashes 4.2.2 if on MF3 or 4.3 on MK2. Only Touchwiz roms can be flashed although certain GE roms also do work.
You wont be able to flash kitkat roms or any aosp roms sadly.
Click to expand...
Click to collapse
The closest you will get to the pure vanilla android we all have become accustomed to is the GPE roms. Just Usb does't work. Personally my fine was on hyperdrive. Originally a Verizon rom but made compatible to all other variants. It is an awesome rom. Anything with 4.2.2. will work so just look for those in the link's in the dev section on the titles of roms. Make sure you flash those modules after. Good luck.

cannot load the MF3 modules
Hi all,
I have been trying to go through the whole process multiple times only to be blocked when trying to load the MF3 kernel modules.
- I have a AT&T MF3 S4
- installed SS 3.65
- tried a couple ROMS, ge4.2.2clean-20130907, INTIKA.LOCKY.MF3.MH8.ST.DEODEX, I9505_-_Google_Edition_Final-v1_by_Jamal2367
- all boot, even if only after a couple minutes
- LTE 4g works
- Bluetooth works
- installed the MF3 modules. I even checked that they are identical from the modules used in the Stock ROM.
- None of the modules can load within the custom ROMS. To verify, I tried to insmod manually, I get this error :
insmod: init_module 'dhd.ko' failed (Exec format error)
Looking at the messages :
4>[ 3120.892608] TIMA: lkmauth--launch the tzapp to check kernel module; module len is 620372
<3>[ 3120.898956] QSEECOM: __qseecom_get_fw_size: error with request_firmware
<3>[ 3120.899200] TIMA: lkmauth--cannot get tzapp handle from kernel.
This happens with any modules, not only the dhd wifi driver. I verified that I could rmmod/insmod everything fine when running the stock ROM.
I researched this as much as I could. There are comments about non-signed modules, but here, the modules are the exact ones from Samsung stock image.
Has anyone seen something like this ?
Since it seems that many people are successful with this, is there something that I am missing ?
Thanks,
Philippe

pmoutarlier said:
Hi all,
I have been trying to go through the whole process multiple times only to be blocked when trying to load the MF3 kernel modules.
- I have a AT&T MF3 S4
- installed SS 3.65
- tried a couple ROMS, ge4.2.2clean-20130907, INTIKA.LOCKY.MF3.MH8.ST.DEODEX, I9505_-_Google_Edition_Final-v1_by_Jamal2367
- all boot, even if only after a couple minutes
- LTE 4g works
- Bluetooth works
- installed the MF3 modules. I even checked that they are identical from the modules used in the Stock ROM.
- None of the modules can load within the custom ROMS. To verify, I tried to insmod manually, I get this error :
insmod: init_module 'dhd.ko' failed (Exec format error)
Looking at the messages :
4>[ 3120.892608] TIMA: lkmauth--launch the tzapp to check kernel module; module len is 620372
<3>[ 3120.898956] QSEECOM: __qseecom_get_fw_size: error with request_firmware
<3>[ 3120.899200] TIMA: lkmauth--cannot get tzapp handle from kernel.
This happens with any modules, not only the dhd wifi driver. I verified that I could rmmod/insmod everything fine when running the stock ROM.
I researched this as much as I could. There are comments about non-signed modules, but here, the modules are the exact ones from Samsung stock image.
Has anyone seen something like this ?
Since it seems that many people are successful with this, is there something that I am missing ?
Thanks,
Philippe
Click to expand...
Click to collapse
Try downloading the modules again. I've never had issues with any of those ROMs. You got the module zip from the Safestrap OP?

DeadlySin9 said:
Try downloading the modules again. I've never had issues with any of those ROMs. You got the module zip from the Safestrap OP?
Click to expand...
Click to collapse
Just re-downloaded it from here :
http://forum.xda-developers.com/devdb/project/?id=680#downloads
still failing with the same message .. weird since it seems to work fine with everyone else ..
Do we need to restore the original kernel as well (boot.img from stock) ?
Thanks,
Philippe

pmoutarlier said:
Just re-downloaded it from here :
http://forum.xda-developers.com/devdb/project/?id=680#downloads
still failing with the same message .. weird since it seems to work fine with everyone else ..
Do we need to restore the original kernel as well (boot.img from stock) ?
Thanks,
Philippe
Click to expand...
Click to collapse
When using safestrap it never touches the kernel, so your stock should be in place and you can't restore it except by reflashing the whole MF3 system, which you may have to do. I'm not sure why it would be blocked. You flashed them right after installing the ROM and before booting into the ROM right?

My GS4 I337 keep getting stuck on download mode when I am using Odin 3.07.. also tried 1.85
On phone:
in download mode it says:
ODIN MODE
PRODUCT NAME: SGH-I337
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: CUSTOM
KNOX KERNEL LOCK: 0X0
KNOX WARRANTY VOID: 0X1
CSB-CONFIG-LSB: 0X30
WRITE PROTECTION: ENABLE
eMMC BURST MODE: ENABLE
START [224,1440]
SW REV. CHECK FAIL : FUSED : 4 , BUNARY : 2
ON ODIN:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PLATFORM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_ATT_I337ATTAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
plz help..

Just to confirm, you were on MF3 instead of MK2?

Kaze105 said:
Just to confirm, you were on MF3 instead of MK2?
Click to expand...
Click to collapse
Honestly I dont know. I am downloading the MK2 at the moment to try it again. I been trying with MF3.
I had 4.2.2 then att OTA update changed it to 4.3
---------- Post added at 11:05 AM ---------- Previous post was at 10:17 AM ----------
c5downlow said:
Honestly I dont know. I am downloading the MK2 at the moment to try it again. I been trying with MF3.
I had 4.2.2 then att OTA update changed it to 4.3
Click to expand...
Click to collapse
UPDATE: MK2 is working so far.. I am doing it as we speak.
yay it worked!!!!

[Q] S4 Stuck in a Boot Loop

I have searched everywhere - Google, XDA, AndroidCentral, everything.
I am very savvy with computers and phones - I'm a programmer myself.
I had CM11 nightly installed for weeks. All of a sudden, my phone restarts itself into an infinite boot loop (doesn't go past the SAMSUNG Galaxy S 4 screen).
I have tried EVERYTHING. Restoring an old nandroid backup, reflashing CM11 and Gapps - nothing.
Every time I try to install the stock firmware - both L720VPUAMDC_L720SPTAMDC_L720VPUAMDC_HOME.tar.md5 (acquired directly from Samsung) and L720VPUEMK2_L720SPTEMK2_L720VPUEMK2_HOME.tar.md5 (again, direct download) it always fails at the same spot:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUEMK2_L720SPTEMK2_L720VPUEMK2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I flashed the MK2 modem when flashing the MK2 stock ROM... no dice. Same thing for the NAE modem + ROM.
Please, help me. I have no clue what to do at this point. The only backup I have, which is of Android 4.2.2, also doesn't work. Same bootloop.
I have tried all of the above things with three different version of Odin: 1.805, 3.04 and 3.07.
I re-installed the Samsung USB drivers, in case that was the issue.
I am completely clueless.
The main problem (I believe) is this:
aboot.mbn
Please and thank you.

rpnunez said:
I have searched everywhere - Google, XDA, AndroidCentral, everything.
I am very savvy with computers and phones - I'm a programmer myself.
I had CM11 nightly installed for weeks. All of a sudden, my phone restarts itself into an infinite boot loop (doesn't go past the SAMSUNG Galaxy S 4 screen).
I have tried EVERYTHING. Restoring an old nandroid backup, reflashing CM11 and Gapps - nothing.
Every time I try to install the stock firmware - both L720VPUAMDC_L720SPTAMDC_L720VPUAMDC_HOME.tar.md5 (acquired directly from Samsung) and L720VPUEMK2_L720SPTEMK2_L720VPUEMK2_HOME.tar.md5 (again, direct download) it always fails at the same spot:
I flashed the MK2 modem when flashing the MK2 stock ROM... no dice. Same thing for the NAE modem + ROM.
Please, help me. I have no clue what to do at this point. The only backup I have, which is of Android 4.2.2, also doesn't work. Same bootloop.
I have tried all of the above things with three different version of Odin: 1.805, 3.04 and 3.07.
I re-installed the Samsung USB drivers, in case that was the issue.
I am completely clueless.
The main problem (I believe) is this:
aboot.mbn
Please and thank you.
Click to expand...
Click to collapse
I know this sounds redundant or maybe you've done this too.
Charge the phone fully - while powered off. Take the battery out for 15 earth minutes. Then run Odin as administrator on your PC 1st (use the full NAE tar put in the PDA slot (in the dev section read the thread for some other tips too)) Then put phone into download mode and then plug into computer
ALSO I know this too sounds silly, but try a brand new USB cable. Can't tell you how many times that has caused problems for me.
Good luck

leaderbuilder said:
I know this sounds redundant or maybe you've done this too.
Charge the phone fully - while powered off. Take the battery out for 15 earth minutes. Then run Odin as administrator on your PC 1st (use the full NAE tar put in the PDA slot (in the dev section read the thread for some other tips too)) Then put phone into download mode and then plug into computer
ALSO I know this too sounds silly, but try a brand new USB cable. Can't tell you how many times that has caused problems for me.
Good luck
Click to expand...
Click to collapse
Thank you for such a quick response!
The phone won't go into the "charging mode" which I know is what you're talking about
The USB cable is fine, every time I flash one of the stock ROMs on the phone I have to re-flash the recovery, so we can cross that one off the list.
Am I not using the correct tar file? The file was zipped in a file entitled "Samsung-Updates.com-SPH-L720-SPR-L720VPUAMDC-1365579188.zip" which I downloaded yesterday.
It's charging now in Philz Recovery. Once it's at 100%, I will take out the battery for 15 minutes (hell, probably even 30! lol) and see what happens.
Any other suggestions my friend? Once again, thank you!

rpnunez said:
Thank you for such a quick response!
The phone won't go into the "charging mode" which I know is what you're talking about
The USB cable is fine, every time I flash one of the stock ROMs on the phone I have to re-flash the recovery, so we can cross that one off the list.
Am I not using the correct tar file? The file was zipped in a file entitled "Samsung-Updates.com-SPH-L720-SPR-L720VPUAMDC-1365579188.zip" which I downloaded yesterday.
It's charging now in Philz Recovery. Once it's at 100%, I will take out the battery for 15 minutes (hell, probably even 30! lol) and see what happens.
Any other suggestions my friend? Once again, thank you!
Click to expand...
Click to collapse
If your phone had an MJA or later - MK2 or NAE bootloader you CANNOT flash any Odin ROM previous because of the Knox bootloader.
You're trying the MDC - that won't work.
Keep the phone charging and try the NAE
Here is a similar post and similar problem with my response (includes the link to the NAE .tar)

leaderbuilder said:
If your phone had an MJA or later - MK2 or NAE bootloader you CANNOT flash any Odin ROM previous because of the Knox bootloader.
You're trying the MDC - that won't work.
Keep the phone charging and try the NAE
Here is a similar post and similar problem with my response (includes the link to the NAE .tar)
Click to expand...
Click to collapse
Ahhh... that makes sense.
I just tried flashing the MDC modem, because I believe my 4.2.2 backup is on MDC...but now I have the weirdest message saying "System software not authorized by Samsung has been found on your phone".
Now I think I messed things up...
I'm downloading the NAE file. Hopefully flashing that will fix everything.
Why can't I just delete *everything*? Like a reformat on a Windows PC? Literally, destroy everything - and just flash the stock NAE firmware?
I appreciate your help now so much my friend. Thank you.

rpnunez said:
Ahhh... that makes sense.
I just tried flashing the MDC modem, because I believe my 4.2.2 backup is on MDC...but now I have the weirdest message saying "System software not authorized by Samsung has been found on your phone".
Now I think I messed things up...
I'm downloading the NAE file. Hopefully flashing that will fix everything.
Why can't I just delete *everything*? Like a reformat on a Windows PC? Literally, destroy everything - and just flash the stock NAE firmware?
I appreciate your help now so much my friend. Thank you.
Click to expand...
Click to collapse
Because of the Knox bootloader you can't wipe everything. Read my other thread as to why. Knox bootloader is in the chips security container and once tripped is not, as of now removable.
Flashing the tar should get you all good to go.
Sent from my SPH-L720 using XDA Premium 4 mobile app

leaderbuilder said:
Because of the Knox bootloader you can't wipe everything. Read my other thread as to why. Knox bootloader is in the chips security container and once tripped is not, as of now removable.
Flashing the tar should get you all good to go.
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I was able to successfully flash to the TAR you linked me to!
However, I am still stuck in a bootloop...
It won't even let me boot into recovery.
You've been such a help buddy. Any other ideas?

If the tar flashed successfully try power off completely.
Then boot to stock recovery - Power on + Volume up (kind of tricky on the S4, I often miss the right length of time to hold both kind of freaks me out/pissed me off, but eventually after many battery pulls I'll get it on boot. )
Then try a factory reset.
Edit if that fails then try this also:
You can also try to Odin a custom recovery - http://goo.im/devs/philz_touch/CWM_Advanced_Edition/jfltespr/philz_touch_6.08.9-jfltespr.tar.md5 [download mode, odin in PDA slot - do NO check f-reset or autoreboot - once odin is finished do a battery pull]
Then try to get to custom recovery and flash the stock NAE kernel if it doesn't boot
Here's Philz http://forum.xda-developers.com/showpost.php?p=51411121&postcount=1955

leaderbuilder said:
If the tar flashed successfully try power off completely.
Then boot to stock recovery - Power on + Volume up (kind of tricky on the S4, I often miss the right length of time to hold both kind of freaks me out/pissed me off, but eventually after many battery pulls I'll get it on boot. )
Then try a factory reset.
Edit if that fails then try this also:
You can also try to Odin a custom recovery - http://goo.im/devs/philz_touch/CWM_Advanced_Edition/jfltespr/philz_touch_6.08.9-jfltespr.tar.md5 [download mode, odin in PDA slot - do NO check f-reset or autoreboot - once odin is finished do a battery pull]
Then try to get to custom recovery and flash the stock NAE kernel if it doesn't boot
Here's Philz http://forum.xda-developers.com/showpost.php?p=51411121&postcount=1955
Click to expand...
Click to collapse
Can't get to stock recovery - it just says "RECOVERY BOOTING..." then reboots.
Installed Philz Recovery, installed CF-Auto-Root since Philz complained that I wasn't rooted, when I tried to flash the NAE kernel, it says:
Using legacy property environment for update-binary...
Please upgrade to latest binary...
Currently installing kernel
format() expects 4args, got 5
E:Error in /storage/sdcard1/Negalite_NAE_Stock_Kernel.zip (Status 7)
Installation aborted.
Click to expand...
Click to collapse
Why me

That's okay. Status 7 is an updater script error. There are a few things.
Let's try another kernel.
OR another recovery (I keep multiple recoveries on my externaSD for this reason.
Here is Reverepats TWRP You can flash the recovery from recovery and reboot recovery. Say that five times..
Since you did get to custom recovery you're heading the right way.
Try flashing the stock kernel from the TWRP recovery and
You can try another kernel too.
Ktoonsez' latest kernel is here You can grab the 4.4 TW one (take note of the build prop edit you may have to do to get wifi working - that'll require rooting (cf-autoroo) and a root explorer to get to it)
All seems kernel related to me.
Here is a vid on disabling script checking tha may work too. I relize that it's for full ROMs but it may help.

leaderbuilder said:
That's okay. Status 7 is an updater script error. There are a few things.
Let's try another kernel.
OR another recovery (I keep multiple recoveries on my externaSD for this reason.
Here is Reverepats TWRP You can flash the recovery from recovery and reboot recovery. Say that five times..
Since you did get to custom recovery you're heading the right way.
Try flashing the stock kernel from the TWRP recovery and
You can try another kernel too.
Ktoonsez' latest kernel is here You can grab the 4.4 TW one (take note of the build prop edit you may have to do to get wifi working - that'll require rooting (cf-autoroo) and a root explorer to get to it)
All seems kernel related to me.
Here is a vid on disabling script checking tha may work too. I relize that it's for full ROMs but it may help.
Click to expand...
Click to collapse
I tried flashing Recerepats TWRP via Philz... no dice. I guess it's just not my day lol. I tried Odin'ing openrecovery (2 versions) and noooo dice.
So I went back to the Philz 6 (I tried flashing Philz 5 and.. no luck), flashed the kernel you linked to, it flashed fine.
....still in a boot loop. I'm so sorry for taking up your time buddy, you've been such a great help.
I'm guessing I should re-odin the NAE tar now, since the kernel has been modified?
I feel like a mechanic who can't change his own car oil lol. I'm a programmer and write PHP/JavaScript daily, none of these things scare me - but nothing is working!

Ya,
I'd try re-odining the tar again.
Just put in the pda slot as usual, but this time try unchecking the Auto Reboot and F. reset time. and when done just battery pull and restart.
Edit/Add:
Oh and you might still have to 'factory reset' from stock recovery' if it gets stuck on bootloop.
BUT remember the first boot takes a freaking long time - 5-10 earth minutes for first boot! wait and then try the reset if it doesn't get past it

leaderbuilder said:
Ya,
I'd try re-odining the tar again.
Just put in the pda slot as usual, but this time try unchecking the Auto Reboot and F. reset time. and when done just battery pull and restart.
Edit/Add:
Oh and you might still have to 'factory reset' from stock recovery' if it gets stuck on bootloop.
BUT remember the first boot takes a freaking long time - 5-10 earth minutes for first boot! wait and then try the reset if it doesn't get past it
Click to expand...
Click to collapse
Just finished re-odinining the tar file. Nothing. Still in a bootloop.
How can my device be so ruined? All I would do is install new CM nightlies - the right way, too. I remember I was in a shopping market yesterday, everything was nice and dandy, and when I get in my car, this bootloop thing started happening,
I'm baffled by this... I really, really am. With your help, along with other things I've tried, I've tried everything under the sun.
The only thing I haven't thought of is using ADB/working on the phone via command line.
What do you think?

Worth a shot.
One thing though.
Before you give up pull the battery again for about 15+ minutes. then put it back in and then try to Odin. I had to do that on my old Epic a few times.
Couldn't hurt to try adb.
One last thing - in custom recovery (philz say) wipe the cache and then wipe the Dalvik cache (in advanced I think) then try booting again. Sometimes that helps bootloops.
But for sh*ts and giggles how about trying to install a custom ROM? Maybe Negalites's Here's his release version
To install boot to Philz recovery; wipe cache, wipe dalvik and the wipe to install new ROM/Factory reset then select the negalite.zip and run throught the install.

@rpnunez haven't seen a post back. Hope you got it going.

leaderbuilder said:
@rpnunez haven't seen a post back. Hope you got it going.
Click to expand...
Click to collapse
Leaderbuilder, thank you so much for following up like that - it really means alot!
Unfortunately, I tried your latest suggestions, and still nothing - both unchecking Auto Reboot and F. Reset Time + battery pull for 15 mins, and the wiping of the cache and dalvik cache.
I should try flashing a custom ROM, but may I ask why flashing CM + Gapps would be different? I've tried flashing CM countless times :/
Also, could any of this be happening because of Knox? I've read about Knox, but I don't really know much about it. Before I posted this thread, I downloaded a multi-tool kit (Dr. Ketan's Multitool v6 - I followed this guide: http://techbeasts.com/2014/01/17/how-to-deknox-samsung-galaxy-s3-s4-note-2-note-3/) and it was to "reset" the Knox counter, but it didn't get me out of the boot loop.
I just wish there was a "Format" function for my phone lol. Is there anything else you can think of? I really don't understand how a phone can get so... destroyed. No water damage, no fall, nothing - from one moment to the next, boot loop.
Would the stock recovery help? When I flash the NAE tar, I hold Volume Up + Power, I see "RECOVERY BOOTING..." and then... boot loop! Can that give any clues?
What's odd is that it won't go past the Samsung Galaxy S4 screen - it's like a computer not being able to go past the BIOS screen.
Once again, I greatly appreciate your time and effort.

Well you can Odin a custom recovery again. And wipe the crap out of everything - caches, system, DATA for sure do that, wipe to install new ROM. (if you use TWRP - there is an option to use rm vs format which may help in advanced I think.)
Then flash Philz maybe and again try another ROM like Negalite
I'm pretty stumped but that's what I'd do - wipe the sh*t out of it, reboot recovery wipe again then try installing ROM.

leaderbuilder said:
Well you can Odin a custom recovery again. And wipe the crap out of everything - caches, system, DATA for sure do that, wipe to install new ROM. (if you use TWRP - there is an option to use rm vs format which may help in advanced I think.)
Then flash Philz maybe and again try another ROM like Negalite
I'm pretty stumped but that's what I'd do - wipe the sh*t out of it, reboot recovery wipe again then try installing ROM.
Click to expand...
Click to collapse
It's really odd that I can't flash any recovery other than PhilZ "philz_touch_6.25.0-jflte.tar.md5". I can't even flash a slightly older version, "philz_touch_5.18.2-jfltespr.tar.md5". Hell, I've tried all of these:
OUDHS-Recovery-jfltespr-1.0.3.3.tar
openrecovery-twrp-2.7.0.1-jfltespr.tar
openrecovery-twrp-2.6.3.0-jfltespr.tar
clockworkmod_6.0.3.2_jfltespr.img
GalaxyS4-CWM-6.0.4.4-Sprint.tar
openrecovery-twrp-2.6.0.0-jfltespr.tar
And NONE of them work.
In PhilZ, I formatted everything (wipedata, wipe to install new rom, formatted /boot, /preload/ cache, /system, everything that can be formatted - flashed NAE tar again and nothing.
I'm going to go ahead and try to flash Negalite's ROM. I'm about to just take the damn phone to Best Buy because luckily have I have insurance on it... but geez, I really cannot fathom what is going on with this device. But I still want to try a few more things.
Do you know of any ADB commands/guides or something that can perhaps generate a "log file" as to what's going on during the boot process? Or something to that effect?
Thank you for your time my friend. :angel:
Edit/Update:
Flashed Negalite's ROM... nothing. I'm getting tired of looking at the Samsung Galaxy S4 boot screen lol.
Would using "Re-partition" help? Maybe something got partitioned? I'm really running out of ideas..

rpnunez said:
It's really odd that I can't flash any recovery other than PhilZ "philz_touch_6.25.0-jflte.tar.md5". I can't even flash a slightly older version, "philz_touch_5.18.2-jfltespr.tar.md5". Hell, I've tried all of these:
OUDHS-Recovery-jfltespr-1.0.3.3.tar
openrecovery-twrp-2.7.0.1-jfltespr.tar
openrecovery-twrp-2.6.3.0-jfltespr.tar
clockworkmod_6.0.3.2_jfltespr.img
GalaxyS4-CWM-6.0.4.4-Sprint.tar
openrecovery-twrp-2.6.0.0-jfltespr.tar
And NONE of them work.
In PhilZ, I formatted everything (wipedata, wipe to install new rom, formatted /boot, /preload/ cache, /system, everything that can be formatted - flashed NAE tar again and nothing.
I'm going to go ahead and try to flash Negalite's ROM. I'm about to just take the damn phone to Best Buy because luckily have I have insurance on it... but geez, I really cannot fathom what is going on with this device. But I still want to try a few more things.
Do you know of any ADB commands/guides or something that can perhaps generate a "log file" as to what's going on during the boot process? Or something to that effect?
Thank you for your time my friend. :angel:
Edit/Update:
Flashed Negalite's ROM... nothing. I'm getting tired of looking at the Samsung Galaxy S4 boot screen lol.
Would using "Re-partition" help? Maybe something got partitioned? I'm really running out of ideas..
Click to expand...
Click to collapse
Okay, by chance is your device the T model? - the Triband one?
Because I can see and think of no reason why all this wouldn't work unless it was not the Sprint SPH-L720.

leaderbuilder said:
Okay, by chance is your device the T model? - the Triband one?
Because I can see and think of no reason why all this wouldn't work unless it was not the Sprint SPH-L720.
Click to expand...
Click to collapse
I do believe it is the Triband one... it has a SIM card, and I remember seeing options like "GSM, GSM/CDMA, GSM/CDMA/LTE" when selecting network mode or w/e it's called. Is there a way to determine if it is Triband?

please help before I brick it

good evening
I am in a bit of tight spot
and before a srew it up (more) I wonder if you could help
I have a SM-G900V which is rooted and I had TWRP working just fine
I tried to flash a rom (project infinity) with aroma which freezed on installing aroma
the developer replied to me that the problem was from TWRP which had a bus and that I should instal CWP
I tried to install CWP on top of TWRP through ODIN and got a failure message
as of now I have neither TWRP or CWP or any rom flashed in mydevice
once I go into recovery mode and try to flash the previous rom that I had through the sdcard it says "footer is wrong signature fail" an reboots and gets stuck with no rom
just tried to reinstall TWRP through ODIN and got the failure message again
with the folowing message:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth) <OSM> All threads completed. (succeed 0 / failed 1)
please help

Hey man,
Sounds like you're in a bit of a pickle. Not sure if this would be a bit extreme, but I'd download the stock firmware and flash it through Odin. After that, reflash recovery and retry your rom.
I kind of see flashing back to stock a 'fail safe' in most cases, so it's always handy to have the stock firmware stored somewhere anyway. ?
Sent from my SM-G900I

..

fffft said:
Don't flash anything until someone discerns what went wrong..
being impatient at this point will put you at high risk of bricking or worse.
The phone boots normally up until the footer error?
What is the exact error message that you see?
What version of TWRP did you have?
Any backups? If so, do they include your baseband, EFS & PIT?
16 GB ROM?
Did you have a Verizon ROM when this happened?
Rooted?
.
Click to expand...
Click to collapse
let me start by thank you for your time!
I am a bit new to all this, I have flashed some roms in the past so I am also familiar with some stuff...
The phone doesn't boot it gets stuck like the attached picture, the OS doesn't start.
I don't see any message as it is stuck like I mentioned before, I just saw a message of "FAIL!" in Odin when I tried to install CWM on top of TWRP
my version of TWRP was 2.7.1.0
I had a backup on TWRP but as I dont see TWRP working anymore I dont know if its still available
my phone is 16GB
my SM-G900V is rooted and at the moment I had working perfectly SpeedROM v1 Rev2
if you would like to contact me through chat let me know, and again thank you very much!!

Try this
..

fffft said:
Okay, on the positive side there isn't anything to suggest that your bootloader is corrupt which would make this a lot harder. Probably the failed aroma install just messed your kernel up. But I don't want to recommend messing around with shortcut solutions e.g. just flashing the kernel that may or may not work, but would put you at unnecessary further risk.
The earlier suggestion to flash a full stock image is generally sound advice, but it does not apply to all situations. My questions were basically aimed at getting a sense of whether you have corrupted the bootloader or partitioning which has a bearing on how to best recover your phone.
First, I am assuming that you do not have the Dev (unlocked bootloader) version S5. If you have the Dev edition with the unlocked bootloader, do not proceed with the rest of this post until we discuss that.
On the assumption that you have a regular 16 GB Verizon SM-G900V S5, then I would like to see you Odin flash a full stock S5 Verizon image that has been rooted. Unfortunately I couldn't find anyone who has made and posted a stock rooted Verizon S5 image like that. I don't mean a stock rooted (custom) ROM.. I mean the full stock firmware image, including the bootloader, but rooted.
That's fine. The rooted part would just be a little extra insurance put against theoretical possible snags i.e. Knox issues. So I will suggest that you use Odin to flash a full stock Verizon S5 image, with an explicit partition table. Normally we don't touch the partition information (PIT) in Odin, but in your case we need to.
Download the files below from this thread
Unless you already have the file on your PC
Verizon S5 Retail Tar 4.4.2 NCG baseband and Mar 31 kernel
MD5: 699a949b57c771b00db9f3ed675c7a5e
NCG Pit
MD5: 3dd82f91a02c82e60e0a1f9964fdb5c0
Odin 3.09
MD5: 810ad286967d0a33881fd8181d35959f
You should thank the OP in that thread for collating the files that you need in one place.
Particularly that all important PIT file.
Start Odin and check these three boxes only: Auto reboot, Re-Partition, F. Reset Time
Choose the PIT file in the PIT window. Note that the PIT file needs to be extracted. Do not leave it zipped.
Choose the stock firmware tar.md5 file in the PDA window. The tar.md5 file needs to remain tarred i.e. tar.md5 or .tar
Put your phone into download mode. Ensure that your phone is off, remove the battery for a few seconds if necessary, then press volume down + home + power until you see the android robot screen come up. If it doesn't go into download mode, repeat these steps. And in the very unlikely event that you can't get into the download mode at all, stop and post that information
Connect your phone to your PC, Odin should say that it has detected your phone
Press start and let Odin flash your phone
Basically we are replacing all of the system files and assuring that your partitioning has not been corrupted
When Odin finishes with a success message your phone should be back to normal. Do a normal reboot to confirm
If you did not backup your phone, your user files in the /data partition might still be accessible
Decide if you wish to back them up or not. Do so if you need them. Then do a factory reset from the Settings menu
You will need to re-root and reinstall your apps, etc
If you run into any difficulties:
If the Odin write fails, note the error message and double check that your Odin settings were correct
Do not close Odin. Pull the battery from your phone for ten seconds.
Then replace the battery and go into download mode again (vol down + home + power)
Note whether Odin detects the phone
Then try flashing with Odin again. Note that you are not closing the Odin program if the first flash attempt fails
Odin can be a bit picky and it is not unheard of to have to reset the phone like this and run the session a second time
Odin is also picky about USB cables. If you still continued trouble, try a different USB cable and USB port
Don't despair if anything goes astray. There is almost always an alternate way to go about something.
Let us know your results so that we can (hopefully) celebrate. Or at least regroup.
.
Click to expand...
Click to collapse
you senior member??? pppffffffff
you should OWN this forum!!! thanx a lot for your extended time in this explanation mate, I will proceed and let you know

Agreed. I use a Dell and sometimes I have problems with odin using the front usb. I have to use the read usb and then no problems.

Hi Guys!!
I am back, back with my phone completely restored
A special THANX to fffff for your help!!

..

[Q] [Urgent] Can't unroot i337 MDL version via Odin

I have the AT&T Samsung Galaxy S4 i337 with MDL firmware and I needed to flash back to the stock ROM to bring to AT&T to fix an unlocking issue. I googled and found two top guides and a video where they all did the same thing so I thought it was safe to follow it--the guides did not specify that I needed to use a specfic firmware even if it's an AT&T variant (I assumed all AT&T variants had the same firmware and so did the guides apparently) so I think I used the wrong PDA on Odin 1.85 and now I get the issue "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I can no longer boot the device even to my custom ROM.
How do I fix this and then be able to flash back to stock so I can return it to AT&T? Some guides required a PIT file along with the PDA, some required both PIT and bootloader along with the PDA, and some just required PDA. Which ones am I required for my purpose and where do I get them? (I went to several sources after googling and they offered different ones).
Here's my Odin 3.07 output:
<ID:0/007> Firmware update start..
<ID:0/007> sbl2.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/007> Removed!!
I will be checking back on this thread every chance I can get--this problem needs to be fixed by Monday because I desperately need it for work. Thank you!

I'm going to try to help you out. Bear in mind that I do not currently have this phone, and have very little actual experience with it.
I don't know you experience level. Did you perform a wipe data/factory reset from within recovery before the first time you flashed the stock firmware? If not, can you now enter recovery? If so, perform a wipe data/factory reset and see if the phone will then boot into system. If you can boot into recovery, but the wipe data/factory reset does not resolve the issue, please make note of the details of the recovery. It will tell you which version and we need to know that.
The MDL firmware is the second stock firmware distribution on the SGH-I337 (MDB was first) and was able to be cracked with Loki, by-passing the bootloader to allow installation of custom kernels. All subsequent stock firmware distributions, MF3, MK2, MLD, NB1, NC1, NI1, NJ4, or OC3 are locked, allowing only the stock kernel. So the first important question is what exactly did you flash onto the phone on the first try?
If you flashed the stock MDL firmware, it would be something like I337UCUAMDL, then your boot loader is still by-passable. However, if you flashed any of the subsequent stock distributions, then you will have a locked boot loader. So it's very important to know exactly what was done so far so that the recovery attempt can be done correctly.
I'll need this information, and anything else you can think to tell me, to give you further advice.