Database Users

[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] hyperdrive rls12 install problems

Hello peeps a Happy New Year to all!
I tried searching the forums and google but no luck on my case. I am trying to install hyperdrive and am following instructions, downloaded files multiple times on multiple computers and i337m itself. Aroma opens fine and works through fine untill it tries to flash kernel it says:
flashing kernel
file_getprop: failed to stat "/tmp/aroma/kernel.prop": No such file or directory.
So I thought it was just missing a kernel, so continued and installed the att compatibility pack and all i get is ODIN/download mode. I then tried flashing kstoonez kernel and same thing.
I am using Philz Touch latest version on Canadian s4
Any ideas?

The_SilverOne said:
Hello peeps a Happy New Year to all!
I tried searching the forums and google but no luck on my case. I am trying to install hyperdrive and am following instructions, downloaded files multiple times on multiple computers and i337m itself. Aroma opens fine and works through fine untill it tries to flash kernel it says:
flashing kernel
file_getprop: failed to stat "/tmp/aroma/kernel.prop": No such file or directory.
So I thought it was just missing a kernel, so continued and installed the att compatibility pack and all i get is ODIN/download mode. I then tried flashing kstoonez kernel and same thing.
I am using Philz Touch latest version on Canadian s4
Any ideas?
Click to expand...
Click to collapse
The kernel message was no problem for me.using safe strap?
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

the kernel error is common just proceed as you did
did you wipe all including system before flashing? i don't usually wipe in aroma unless no choice given
did you choose your correct carrier--who is your carrier--that info helps us tp help you--
i don't have i337m so can't be specific on things relating to that phone. you say i337m and i337 is in your sig
if you have i337 you need to flash loki-doki after rom
maybe try twrp--i use 2.5.0.2--i have, and there is a flashable zip for it (i337)
got to go for now--

rugmankc said:
the kernel error is common just proceed as you did
did you wipe all including system before flashing? i don't usually wipe in aroma unless no choice given
did you choose your correct carrier--who is your carrier--that info helps us tp help you--
i don't have i337m so can't be specific on things relating to that phone. you say i337m and i337 is in your sig
if you have i337 you need to flash loki-doki after rom
maybe try twrp--i use 2.5.0.2--i have, and there is a flashable zip for it (i337)
got to go for now--
Click to expand...
Click to collapse
Thank you both for your replys, your help is very much appreciated.
So I wiped it with recovery not aroma.
Carrier is Fido (Rogers subsidiary)
Phone is Canadian S4 variant (SGH-I337m) I believe it is the same as i337 (The m being a canadian designation) but don't quote me on that.
I was under the assumption that Canadian s4 Didn't need lokidoki.
Can you elaborate on safestrap?
No matter what I try it goes boots to download mode. Even if I plug it in to charge not pressing any power button.

Canadian s4 doesnt need loki doki. And your not on safestrap if you have twrp.
As far as your problem. Did it complete the install of the rom even after it said it failed the kernel?
I suggest installing then flashing a 4.3 tw kernel for your device before rebooting system. You shouldn't need a compatibility pack as your not att. Plus im pretty sure the compat pack has loki in it which may cause problems. I also remember philz recovery as having auto loki. So I dont know if you've used philz recovery b4 successfully. If you haven't then id suggest trying twrp. Definitely just try a kernel for your device though. Ktoons worked for me. Other kernels left me stuck at spash screen

SelfElevated2 said:
Canadian s4 doesnt need loki doki. And your not on safestrap if you have twrp.
Click to expand...
Click to collapse
I believe that my phone's bootloader is unlocked (as with most other jtflecan models), but again don't quote me. As a result I have never used safestrap. Should/could I still use it if my bootloader is unlocked?
SelfElevated2 said:
As far as your problem. Did it complete the install of the rom even after it said it failed the kernel?
Click to expand...
Click to collapse
It seemed that way as that was the only error, and aroma proceeded through. First time I tried without the ATT compatibility pack, no go, then with and still no go. Then i tried with a few kernels and same thing.
SelfElevated2 said:
I suggest installing then flashing a 4.3 tw kernel for your device before rebooting system. You shouldn't need a compatibility pack as your not att. Plus im pretty sure the compat pack has loki in it which may cause problems. I also remember philz recovery as having auto loki. So I dont know if you've used philz recovery b4 successfully. If you haven't then id suggest trying twrp. Definitely just try a kernel for your device though. Ktoons worked for me. Other kernels left me stuck at spash screen
Click to expand...
Click to collapse
I transitioned from cwm to philz for ntfs capability as my external sdcard is ntfs. I remember reading somewhere that autoloki was not included and some have complained about it so im not sure if it was added in a later build. In any case I just tried flashing twrp and got a mushy brick.
Now Im curious if I should restore to original and use safestrap or what as my phone does nothing but odin mode.
As always thanks for your valued input.

Your boot loader is definitely not locked. If it was you wouldnt have a custom recovery. So you don't need safestrap. Just restore and reroot and get a recovery. What you put on your phone after that is up to you. I know hyperdrive wouldn't boot for me with most kernels it was just stuck on the splash screen. But it booted for kt kernel. I would honestly find another Rom if I was in the same position

MINI UPDATE:
Phone was bootlooping so I tried to restore to stock 4.2.2 but ODIN failed continuously. Tried 4.3 stock (mk6) and odin failed, tried older odin and succeeded but it bootlooped and went to the kies upgrade error. Tried multiple Computers (2PC 1OSX) multiple ports and cables and all failed.
Trying to figure this out but not much help out there with regards to canadian s4, att guides ok? any suggestions? trying kies restore now but kies hangs after it downloads firmware. urgh
ODIN Outuput:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUEMK6_I337MOYAEMK6_I337MVLUEMK6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> __Xmit Write fail
<ID:0/003> XmitData Fail..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Added!!
ODIN seems to fail at different points, sometimes in recovery, or modem or etc.
do i need to repartition?if so where do i find the pit file for my device?
im reading that im screwed and praying its not true.
Thanks for any help

You cant get into recovery? Only odin? Just keep looking around. I bet its because the aroma flashed a incomplete flash. But I dont know the difference between i337 and i337m so I dont know what to tell you. I suggest keep trying to Odin. If it doesn't work I believe theres a tool to force a stock image onto the phone but I cant remember what its called

SelfElevated2 said:
You cant get into recovery? Only odin? Just keep looking around. I bet its because the aroma flashed a incomplete flash. But I dont know the difference between i337 and i337m so I dont know what to tell you. I suggest keep trying to Odin. If it doesn't work I believe theres a tool to force a stock image onto the phone but I cant remember what its called
Click to expand...
Click to collapse
no i only get odin.
phone only turns on when plugged in to usb on pc, otherwise unresponsive to hardkeys.
Every instance of ODIN flashing fails. No matter which firmware or computer i used, either write failure or PIT failure. both of which im attributing to an incomplete flash, and its making me think that the partition tables are chewed.
im stumped and phonless
any idea what that app was called? google yields no results
thanks for your help

Heres something to read. I dont know if you need the.Canadian pit or reg att pit. Dont just flash one. Get informed first
http://www.droidviews.com/how-to-unbrick-your-bricked-samsung-galaxy-s4-gt-i9500-gt-i9505/

SelfElevated2 said:
Heres something to read. I dont know if you need the.Canadian pit or reg att pit. Dont just flash one. Get informed first
http://www.droidviews.com/how-to-unbrick-your-bricked-samsung-galaxy-s4-gt-i9500-gt-i9505/
Click to expand...
Click to collapse
Thank you very much for that link. It summed up everything i have been reading for the past 24 hours, but alas i have yet to figure out which pit to use, whether I can use the att pit, wind (different provider, uses aws (2 different frequencies from gsm standard) as opposed to gsm although they may have changed that recently),find a rogers pit, since they and fido are essentially the same network or continue searching for a fido pit.
Knowing what the pit does, would it really be carrier specific (asides from the difference in radios between fido/rogers and wind)? Is it ROM version and android version specific?

Update:
-Have Tried all options for recovery in KIES on multiple Pcs and Multiple Macs
-Download/Odin Mode Reads:
ODIN MODE
PRODUCT NAME: SGH-I337M
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: enabled
START [224,1440]
BAR [240,1440​
Questions:
Before this whole fiasco ODIN didnt show KNOX. I assume thats from the 4.3 revert i tried?
Does Write Protection have anything to do with it? I do recall being able to odin flash with this before.
eMMC Burst is new to me, havent seen this before
BAR pops up before failing but not seconds before, maybe a minute before.
Still Stumped
Edit: Even if i were to find the pit file, i cant seem to find modem, csc, and bootloader to add to odin. (unless they are all combined in that md5 file) so i wouldnt be able to flash until having all the necessary items as pit rewrites the partitions and all data is lost.
i also remembered one odd thing, may or may not apply here, but just before flashing to hyperdrive, i was not able to properly format. it would take a few tries to format data or whichever for example, before files were actually gone.
tried reverting to MDJ got vibrate loop
trying again to MK6

The_SilverOne said:
Hello peeps a Happy New Year to all!
I tried searching the forums and google but no luck on my case. I am trying to install hyperdrive and am following instructions, downloaded files multiple times on multiple computers and i337m itself. Aroma opens fine and works through fine untill it tries to flash kernel it says:
flashing kernel
file_getprop: failed to stat "/tmp/aroma/kernel.prop": No such file or directory.
So I thought it was just missing a kernel, so continued and installed the att compatibility pack and all i get is ODIN/download mode. I then tried flashing kstoonez kernel and same thing.
I am using Philz Touch latest version on Canadian s4
Any ideas?
Click to expand...
Click to collapse
Hi, I am currently having this problem after trying to install RLS15.
After trying to flash the new ROM, phone would not boot, and I was no longer able to install ROMS or Restore backups.
When I would try to restore a backup, it would get to Restoring Data, and immediately fail.
When installing the ROM and its kernel, I got the same message as you:
flashing kernel
file_getprop: failed to stat "/tmp/aroma/kernel.prop": No such file or directory.
I've tried:
flashing kernels before flashing the ROM
re-install of Loki + TWRP + Motochopper Casual (Did not revert back to stock before doing this)
flashing the AT&T Compatibility pack.zip for RLS15 Before and After flashing the ROM
Fixing permission
I've noticed once or twice, when trying to restore a backup, a message in TWRP saying that SuperUser was not installed, and it asked if I wanted to install it. So I did the "Swipe to install" in TWRP, but the phone quickly reboots and again doesn't get passed the boot logo.
Sooo, I'm not too sure where to start on this one

d9vabder said:
Hi, I am currently having this problem after trying to install RLS15.
After trying to flash the new ROM, phone would not boot, and I was no longer able to install ROMS or Restore backups.
When I would try to restore a backup, it would get to Restoring Data, and immediately fail.
When installing the ROM and its kernel, I got the same message as you:
flashing kernel
file_getprop: failed to stat "/tmp/aroma/kernel.prop": No such file or directory.
I've tried:
flashing kernels before flashing the ROM
re-install of Loki + TWRP + Motochopper Casual (Did not revert back to stock before doing this)
flashing the AT&T Compatibility pack.zip for RLS15 Before and After flashing the ROM
Fixing permission
I've noticed once or twice, when trying to restore a backup, a message in TWRP saying that SuperUser was not installed, and it asked if I wanted to install it. So I did the "Swipe to install" in TWRP, but the phone quickly reboots and again doesn't get passed the boot logo.
Sooo, I'm not too sure where to start on this one
Click to expand...
Click to collapse
What variant do you have?

So I figured out my problem. In TWRP recovery, I went to mounts, and mounted my micro SD card. It was mounted to internal memory and I guess that was screwing up flashes. Hope this works for you too!
Sent from my SAMSUNG-SGH-I337 using xda premium

Need help, my Sansung S4 is total dead

My samsung Galaxy is totaly dead after I try to root the system.
Noy my phone is stay in Downloading mode, can't boot up, or recover mode.
I was using ATT OS and uppdrage to Android 4.3, after I upgrade, rood function is not working any more. Super user is ask my to manual root again.
my recover mode is still original can't back up or install any ROM.
can any one please help me provide how to flash my phone, may need some .md5 or .tar by using Odin3-v1.85 to reflash boot rocover mode that I can install other rom from web.
thank you , thank you please help.......................
Sam

sammaspda said:
My samsung Galaxy is totaly dead after I try to root the system.
Noy my phone is stay in Downloading mode, can't boot up, or recover mode.
I was using ATT OS and uppdrage to Android 4.3, after I upgrade, rood function is not working any more. Super user is ask my to manual root again.
my recover mode is still original can't back up or install any ROM.
can any one please help me provide how to flash my phone, may need some .md5 or .tar by using Odin3-v1.85 to reflash boot rocover mode that I can install other rom from web.
thank you , thank you please help.......................
Sam
Click to expand...
Click to collapse
What is your baseband?
AT&T Galaxy S4 SGH-I337 RUNNING HYPERDRIVE 12

[email protected] said:
What is your baseband?
AT&T Galaxy S4 SGH-I337 RUNNING HYPERDRIVE 12
Click to expand...
Click to collapse
thank you for help...
my is ATT I337 xxxxMF3, ..not sure, I try to root, after root ...is brick, please please help.

sammaspda said:
thank you for help...
my is ATT I337 xxxxMF3, ..not sure, I try to root, after root ...is brick, please please help.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2502003
Download the md5 tar file. And flash via odin
AT&T Galaxy S4 SGH-I337 RUNNING HYPERDRIVE 12

[email protected] said:
http://forum.xda-developers.com/showthread.php?t=2502003
Download the md5 tar file. And flash via odin
AT&T Galaxy S4 SGH-I337 RUNNING HYPERDRIVE 12
Click to expand...
Click to collapse
thank you for your help.
Can you please let me know how should I choose this file? by using Odin3
which one I have to choose........Filedownload form "Bootloader" or "PDA"
thank you,

sammaspda said:
thank you for your help.
Can you please let me know how should I choose this file? by using Odin3
which one I have to choose........Filedownload form "Bootloader" or "PDA"
thank you,
Click to expand...
Click to collapse
I try all of them, now phone is asking me
Firmware upgrade encountered an issue. please selete recover mode in Kies & try again.
But I try to connect Kies to recover, but Kies can;t connected phone.....still need help.....
please please ...
thank you

sammaspda said:
I try all of them, now phone is asking me
Firmware upgrade encountered an issue. please selete recover mode in Kies & try again.
But I try to connect Kies to recover, but Kies can;t connected phone.....still need help.....
please please ...
thank you
Click to expand...
Click to collapse
Follow this guide by gtj0 http://forum.xda-developers.com/showthread.php?t=2526964
Or
There is a link to a guide to show you how to use this. You need to use Odin 3.07 or 3.09 http://www.droidviews.com/how-to-unbrick-your-bricked-samsung-galaxy-s4-gt-i9500-gt-i9505/
AT&T Galaxy S4 SGH-I337 RUNNING HYPERDRIVE 12

<ID:0/006> Added!!
<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..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> recovery.img
<ID:0/006> persdata.img.ext4
<ID:0/006> system.img.ext4
<ID:0/006> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
Still failed.....screen always ask me use Kies to update firmware, but Kies still unable to undate............
still need more help.....
thank you

sammaspda said:
<ID:0/006> Added!!
<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..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> recovery.img
<ID:0/006> persdata.img.ext4
<ID:0/006> system.img.ext4
<ID:0/006> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
Still failed.....screen always ask me use Kies to update firmware, but Kies still unable to undate............
still need more help.....
thank you
Click to expand...
Click to collapse
Go to best buy and have them reflash your firmware.
AT&T Galaxy S4 SGH-I337 RUNNING HYPERDRIVE 12

I went best buy this morning but they unable reflash my phone.
they ask call 1800 to get repair.......

If you were trying to upgrade to 4.3 and it failed, you might have to follow these directions: http://forum.xda-developers.com/showpost.php?p=48927617&postcount=3

sammaspda said:
I went best buy this morning but they unable reflash my phone.
they ask call 1800 to get repair.......
Click to expand...
Click to collapse
Your going to lose mf3. Follow that guide I posted earlier by gtj0 download the emergency files flash via Odin in PDA then adb sideload mf3-mj9 then mj9-mk2
AT&T Galaxy S4 SGH-I337 RUNNING HYPERDRIVE 12
---------- Post added at 06:49 PM ---------- Previous post was at 06:48 PM ----------
DeadlySin9 said:
If you were trying to upgrade to 4.3 and it failed, you might have to follow these directions: http://forum.xda-developers.com/showpost.php?p=48927617&postcount=3
Click to expand...
Click to collapse
I think he was trying to reflash the mf3 firmware
AT&T Galaxy S4 SGH-I337 RUNNING HYPERDRIVE 12

thank you for your help....I total give it up now....
I already try over weekend spend over 48HRs to working with phone.
always get problem, I have to send to JTAG not, thank you for your help.
How do you think JTAG repair service?
http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=190990521197&ssPageName=ADME:X:RTQ:US:1123
thank you
Sam

sammaspda said:
thank you for your help....I total give it up now....
I already try over weekend spend over 48HRs to working with phone.
always get problem, I have to send to JTAG not, thank you for your help.
How do you think JTAG repair service?
http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=190990521197&ssPageName=ADME:X:RTQ:US:1123
thank you
Sam
Click to expand...
Click to collapse
Don't give up so easy. ... If you tell us what kinda root method did u use it might help us to help you figure it out what is your firmware. ....MF3 use jortex method to root. ...(format your sd card to exfat and use terminal emulator)......If already on 4.3 MK2 u should use SAFEROOT METHOD from Verizon forum. .... follow my thread..... http://forum.xda-developers.com/showthread.php?t=2573080.... it will get u back on track. ...... If u are MF3 just use MF3.tar files from first post. ....If u think u are Mk2 using that one click tool..... (Most likely u are MK2 already. ... Since u said u upgraded to 4.3 and root doesn't work anymore).... Then u should go to post#3 follow the guide. .....u should be ok..... save that money.... If u need more help PM me......
Swyped_from_SS_MK2_Tapatalk

Jtag service man told me..."It looks like the bootloader is permanentaly locked with the rom you tried flashing"
do you know how to solve?
thank you

sammaspda said:
Jtag service man told me..."It looks like the bootloader is permanentaly locked with the rom you tried flashing"
do you know how to solve?
thank you
Click to expand...
Click to collapse
sammaspda said:
My samsung Galaxy is totaly dead after I try to root the system.
Noy my phone is stay in Downloading mode, can't boot up, or recover mode.
I was using ATT OS and uppdrage to Android 4.3, after I upgrade, rood function is not working any more. Super user is ask my to manual root again.
my recover mode is still original can't back up or install any ROM.
can any one please help me provide how to flash my phone, may need some .md5 or .tar by using Odin3-v1.85 to reflash boot rocover mode that I can install other rom from web.
thank you , thank you please help.......................
Sam
Click to expand...
Click to collapse
From my understanding that u are on MF3 and u updated to 4.3 MK2 firmware but your root isn't working (coz MK2 use different ROOT method....it called SAFEROOT) ....so i'm guessing u used terminal emulator ( same root method ) from MF3....or i dunno what u did manually (ADB shell maybe) ....u don't give enough information so other can help u......and then u hit bricked wall.......FOLLOW MY THREAD ON POST#3 MK2_UNBRICKED_METHOD from gtj0 guide that i edited .....make sure u download MF3>MK2update.zip from OP(Original Post) coz u gonna need it in the end .....download and extract all MF3-emergencypart 1 and 2 files......recovery-mj6.tar.md5....(or i337MK2stockrecovery.tar.md5...it also work with some user)....and follow the guide flashing via ODIN.....READ OP,post#2,post#3 make sure u understand everything before u damage more your expensive S4......need more help just PM me.....GOODLUCK.....U SHOULD BE OK....:good:....To show your appreciation in the future .......instead of typing thank you.....thank you....thank you......hit THANK button.....

Im having similar woes. I had problems installing a ROM, softbricked, tried restore to 4.2.2, wouldnt go, tried updating (stupidly) to 4.3 got obKNOXious (had no clue then about knox) tripped knox by trying to go back to 4.2.2 and got firmware update fail. Stuck with no recovery, nor any way of repairing. I tried many versions of ODIN, both kies emergency firmware update options, and heimdall. Heimdall seems promising as i have been able to flash a custom recovery with --no-reboot and reboot using pwr+home+vlup, and i get a warning about tripping knox but it boots into custom recovery. I am able to flash (CM11 for example) but it gives me kernel trips on knox and shuts down on boot. i saw your other thread about the mf3 and mk3 but im not sure if they would work for my variant. no matter what i try i cant get this paperweight to its former glory. local repair center said they wont do anything as knox warranty = tripped. no best buy samsung centers in my area. someone please help.

ted77usa said:
From my understanding that u are on MF3 and u updated to 4.3 MK2 firmware but your root isn't working (coz MK2 use different ROOT method....it called SAFEROOT) ....so i'm guessing u used terminal emulator ( same root method ) from MF3....or i dunno what u did manually (ADB shell maybe) ....u don't give enough information so other can help u......and then u hit bricked wall.......FOLLOW MY THREAD ON POST#3 MK2_UNBRICKED_METHOD from gtj0 guide that i edited .....make sure u download MF3>MK2update.zip from OP(Original Post) coz u gonna need it in the end .....download and extract all MF3-emergencypart 1 and 2 files......recovery-mj6.tar.md5....(or i337MK2stockrecovery.tar.md5...it also work with some user)....and follow the guide flashing via ODIN.....READ OP,post#2,post#3 make sure u understand everything before u damage more your expensive S4......need more help just PM me.....GOODLUCK.....U SHOULD BE OK....:good:....To show your appreciation in the future .......instead of typing thank you.....thank you....thank you......hit THANK button.....
Click to expand...
Click to collapse
sammaspda said:
Jtag service man told me..."It looks like the bootloader is permanentaly locked with the rom you tried flashing"
do you know how to solve?
thank you
Click to expand...
Click to collapse
OK im shocked but somehow i made this work. i used to kies to download firmware by using firmware upgrade and initialization under tools and grabbing the firmware from windows user/appdata/local/temp folder after kies finished downloading (as it starts decompressing)(faster than waiting to download from sammobile). i then pulled all files out of md5 using 7zip, and used heimdall to flash all files to their respective partitions/mountpoints. rebooted still no recovery nor boot. tried again and nothing. i then tried a custom recovery and it gave me seandroid enforcing RECOVERY and restart. so then i tried flashing custom recovery again using heimdall with --no-reboot switch and rebooted with volup+home+pwr and then i was able to enter custom recovery. so i wiped data and cache rebooted got nothing, no recovery no boot just dl mode. so i then reflashed stock rom through heimdall and rebooted, got stock recovery which would try to do something (progress bar appeared) and bootlooped. so i reflashed custom recovery again wiped cache and data and /data /media option (which took longer even though no extsdcard present, which puzzled me) and this time i tried to mount system in recovery and got an error. so i formated /system and it mounted fine. rebooted no boot no recovery. flashed custom recovery wiped /data /media, /cache, /dalvik, formated /sdcard, /system, /data, /cache, mounted /system and rebooted right into download mode and flashed stock image but this time with --no-reboot switch and once finished i manually rebooted into recovery. recovery did its thing and i finally i got a boot animation and glowing led, left it for 10 minutes and it was at samsung setup screen. unplugged my phone instantly died. no boot no recovery. repeated last step but once in samsung os i went to settings backup and reset menu and reset the phone from there. it went into recovery on its own, erased and rebooted and it seems to work fine now (fingers crossed, its only been ten minutes (relatively little compared to this 2 week ordeal.) Oddly enough kies downloaded a bell version although my phone is fido

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!!

..

Soft Brick G900V using Odin Stuck in Recovery Mode

My GS5 G900V is stuck to recovery mode while I was trying to root. My mistake was I used odin to flash it back to a older version to try to root it and I did not did my research I know im a dummy. Now its Soft brick. I looked around and looked around to find answers but nothing seems to work for me. Ive tried using odin again to flash it back to the current firmware but Odin does not work.
It will be stuck on the Samsung GS5 screen and will go straight to recovery mode. Ive tried wiping cache and restore to factory settings still did not work. Tried taking out the battery for some time still did not work. I tried flashing through sd card still did not work.
This is the current log I have. Been trying different things since last night. Nothing works.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Found this link here but not sure how to use it: http://forum.xda-developers.com/showthread.php?t=2446269
I saw one thread with my similar problems. I think this is how they fixed it but I do not know how to do it. Can someone tell me how to use it? It will be greatly appreciated.
Thanks for all the help!

j0mz said:
My GS5 G900V is stuck to recovery mode while I was trying to root. My mistake was I used odin to flash it back to a older version to try to root it and I did not did my research I know im a dummy. Now its Soft brick. I looked around and looked around to find answers but nothing seems to work for me. Ive tried using odin again to flash it back to the current firmware but Odin does not work.
It will be stuck on the Samsung GS5 screen and will go straight to recovery mode. Ive tried wiping cache and restore to factory settings still did not work. Tried taking out the battery for some time still did not work. I tried flashing through sd card still did not work.
This is the current log I have. Been trying different things since last night. Nothing works.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Found this link here but not sure how to use it: http://forum.xda-developers.com/showthread.php?t=2446269
I saw one thread with my similar problems. I think this is how they fixed it but I do not know how to do it. Can someone tell me how to use it? It will be greatly appreciated.
Thanks for all the help!
Click to expand...
Click to collapse
What version (3 letter) are/were you on?
How I unbricked my phone was to do #4 in Notes in the first post: http://forum.xda-developers.com/ver...w-to-update-to-g900voe1-5-0-keeproot-t3149784
BEWARE the warnings...you might be up the creek if you are on OE1 firmware

simplepinoi177 said:
What version (3 letter) are/were you on?
How I unbricked my phone was to do #4 in Notes in the first post: http://forum.xda-developers.com/ver...w-to-update-to-g900voe1-5-0-keeproot-t3149784
BEWARE the warnings...you might be up the creek if you are on OE1 firmware
Click to expand...
Click to collapse
I believe mine was on OD5
I cant use flashfire because my phone is stuck on recovery mode. I cant get pass that.

j0mz said:
I believe mine was on OD5
I cant use flashfire because my phone is stuck on recovery mode. I cant get pass that.
Click to expand...
Click to collapse
you don't use flashfire...
I'm not saying to do the whole thing on the first post...just NUMBER #4 IN THE NOTES...
You use Odin and the file given to unbrick your phone back to NCG...
again, just go to NOTES and do #4 to unbrick the phone. You should be safe/fine if you are on OD5. Don't forget to root again and install a superuser...
Then you can go here to install whatever version you are interested in... http://forum.xda-developers.com/showthread.php?t=2784880

simplepinoi177 said:
you don't use flashfire...
I'm not saying to do the whole thing on the first post...just NUMBER #4 IN THE NOTES...
You use Odin and the file given to unbrick your phone back to NCG...
again, just go to NOTES and do #4 to unbrick the phone. You should be safe/fine if you are on OD5. Don't forget to root again and install a superuser...
Then you can go here to install whatever version you are interested in... http://forum.xda-developers.com/showthread.php?t=2784880
Click to expand...
Click to collapse
I tried it but Odin cant find it. Its a rar file?

Stuck in recovery mode loop. SM-G900V Verizon G900VVRU2BOG5
Im in the exact same situation... i have been literally sitting in front of my PC for hours on end to try and resolve this issue. I cant get back my current firmware now even. Just stuck on the recovery mode. I flashed NCG kernal and it went through as normal, however, all it does not is after the samsung loading sign it goes back into system recovery. I have tried everything from cache wipe to factory reset, system reboot, everything! it just does the same thing - goes back into recovery mode- it is getting really frustrating for me. I would really appreciate it if someone could tell me exactly how to get out of it and use the phone as normal again.
I am on sm-g900v
G900VVRU2BOG5
Verizon mobile S5
I have tried to flash almost all the available ROMS and nothing works everytime this come up: ( i am using the latest Kies drivers, Odin 3.10.6, etc)..
<OSM> Please wait..
<OSM> ALL_VZW_G900VVRU1ANCG_G900VVZW1ANCG_964333_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Added!!
<ID:0/007> Odin engine v(ID:3.1005)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping.. - - i have the pit file and if i use it to flash i get the same output failed completion.
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
PLEASE HELP. THANK YOU.

Tried rooting my SM-G900V. I managed to flash a kernel on it, but kept getting "FAIL!" in Odin when I tried flashing a custom rom. Even after I flashed a kernel on my phone still worked fine. One day it said some nonsense about securtiy updates, I clicked on it and BOOM. Stock OS, GONE. Kernel, GONE. It started giving me a message "use Verizon recovery assistant" I tried getting the program, no dice. I don't have root and I'm on the latest version of lolipop that they have released for the SM-G900V.
CAN ANYONE HELP, PLEASE. IF MY MOM KNEW I WAS MESSING WITH MY PHONE SHE'D KILL ME. SHE THINKS I'VE BEEN CHARGING IT FOR 3 DAYS!!!

m0bk3yn1nj4 said:
Tried rooting my SM-G900V. I managed to flash a kernel on it, but kept getting "FAIL!" in Odin when I tried flashing a custom rom. Even after I flashed a kernel on my phone still worked fine. One day it said some nonsense about securtiy updates, I clicked on it and BOOM. Stock OS, GONE. Kernel, GONE. It started giving me a message "use Verizon recovery assistant" I tried getting the program, no dice. I don't have root and I'm on the latest version of lolipop that they have released for the SM-G900V.
CAN ANYONE HELP, PLEASE. IF MY MOM KNEW I WAS MESSING WITH MY PHONE SHE'D KILL ME. SHE THINKS I'VE BEEN CHARGING IT FOR 3 DAYS!!!
Click to expand...
Click to collapse
can you boot into download mode? if go here http://forum.xda-developers.com/ver...w-to-update-to-g900voe1-5-0-keeproot-t3149784 and flash the full NCG tar then re root your device remember you always wanna flash ni2 kernal or nk2 then flash the rom then the kernal that works with your rom never flash the kernel that works with your rom before you flash the rom

m0bk3yn1nj4 said:
Tried rooting my SM-G900V. I managed to flash a kernel on it, but kept getting "FAIL!" in Odin when I tried flashing a custom rom. Even after I flashed a kernel on my phone still worked fine. One day it said some nonsense about securtiy updates, I clicked on it and BOOM. Stock OS, GONE. Kernel, GONE. It started giving me a message "use Verizon recovery assistant" I tried getting the program, no dice. I don't have root and I'm on the latest version of lolipop that they have released for the SM-G900V.
CAN ANYONE HELP, PLEASE. IF MY MOM KNEW I WAS MESSING WITH MY PHONE SHE'D KILL ME. SHE THINKS I'VE BEEN CHARGING IT FOR 3 DAYS!!!
Click to expand...
Click to collapse
If you were on the latest version of Lollipop and were not yet rooted, you cannot root your phone, flash custom ROMs, and I don't think you can flash kernels. You need to get your hands on a full ODIN stock tar file for the build your phone was on. OG5 is available, but I don't think the OK3 file is available yet. If you took an update in the past 2 or 3 days prior to trying this, you are stuck for a while with no way out. If you did not take an update on your phone in the past 2 or 3 days, look for the OG5 full stock ODIN file to flash to your phone.
---------- Post added at 05:36 PM ---------- Previous post was at 05:34 PM ----------
Veid71 said:
can you boot into download mode? if go here http://forum.xda-developers.com/ver...w-to-update-to-g900voe1-5-0-keeproot-t3149784 and flash the full NCG tar then re root your device remember you always wanna flash ni2 kernal or nk2 then flash the rom then the kernal that works with your rom never flash the kernel that works with your rom before you flash the rom
Click to expand...
Click to collapse
He said he was on the latest Lollipop version when he tried to root. If so, he cannot flash the NCG file. He wasn't already rooted, he was trying to root on the latest Lollipop build which can't be done at this time.

landshark68 said:
If you were on the latest version of Lollipop and were not yet rooted, you cannot root your phone, flash custom ROMs, and I don't think you can flash kernels. You need to get your hands on a full ODIN stock tar file for the build your phone was on. OG5 is available, but I don't think the OK3 file is available yet. If you took an update in the past 2 or 3 days prior to trying this, you are stuck for a while with no way out. If you did not take an update on your phone in the past 2 or 3 days, look for the OG5 full stock ODIN file to flash to your phone.
---------- Post added at 05:36 PM ---------- Previous post was at 05:34 PM ----------
He said he was on the latest Lollipop version when he tried to root. If so, he cannot flash the NCG file. He wasn't already rooted, he was trying to root on the latest Lollipop build which can't be done at this time.
Click to expand...
Click to collapse
ah okay i see then his post was kinda confusing

I don't know how to do that ODIN stuff, is there a video guide out or something?

landshark68 said:
If you were on the latest version of Lollipop and were not yet rooted, you cannot root your phone, flash custom ROMs, and I don't think you can flash kernels. You need to get your hands on a full ODIN stock tar file for the build your phone was on. OG5 is available, but I don't think the OK3 file is available yet. If you took an update in the past 2 or 3 days prior to trying this, you are stuck for a while with no way out. If you did not take an update on your phone in the past 2 or 3 days, look for the OG5 full stock ODIN file to flash to your phone.
Click to expand...
Click to collapse
I have no idea what any of this means. Please, can you help me?!

m0bk3yn1nj4 said:
I don't know how to do that ODIN stuff, is there a video guide out or something?
Click to expand...
Click to collapse
m0bk3yn1nj4 said:
I have no idea what any of this means. Please, can you help me?!
Click to expand...
Click to collapse
No offense intended, but if you don't know how to use ODIN and you don't have any idea what any of what I wrote means, you shouldn't be trying to root your phone without understanding all of it. I'm not aware of a video guide for using ODIN but I'd be willing to bet you could probably find one on youtube. If you can't find a video guide, found in post #4 of this thread is an old picture guide that should give you a pretty good understanding of using ODIN:
http://forum.androidcentral.com/ver...=1.251820425.1215152510.1443888191#post542513
I believe the PDA button is now called the AP button. Follow the video guide you found or the attached picture guide and flash the full BOG5 ODIN tar file found in this thread:
http://forum.xda-developers.com/verizon-galaxy-s5/general/g900vvru2bog5-factoryodintarimage-t3179527
There may even be a guide for using ODIN found here at XDA if you dig around some. Not sure.

landshark68 said:
No offense intended, but if you don't know how to use ODIN and you don't have any idea what any of what I wrote means, you shouldn't be trying to root your phone without understanding all of it. I'm not aware of a video guide for using ODIN but I'd be willing to bet you could probably find one on youtube. If you can't find a video guide, found in post #4 of this thread is an old picture guide that should give you a pretty good understanding of using ODIN:
http://forum.androidcentral.com/ver...=1.251820425.1215152510.1443888191#post542513
I believe the PDA button is now called the AP button. Follow the video guide you found or the attached picture guide and flash the full BOG5 ODIN tar file found in this thread:
http://forum.xda-developers.com/verizon-galaxy-s5/general/g900vvru2bog5-factoryodintarimage-t3179527
There may even be a guide for using ODIN found here at XDA if you dig around some. Not sure.
Click to expand...
Click to collapse
Much obliged

simplepinoi177 said:
What version (3 letter) are/were you on?
How I unbricked my phone was to do #4 in Notes in the first post: http://forum.xda-developers.com/ver...w-to-update-to-g900voe1-5-0-keeproot-t3149784
BEWARE the warnings...you might be up the creek if you are on OE1 firmware
Click to expand...
Click to collapse
i have a sm-g900v BOG5. i bricked mine phone so i tried #4 as you said and get FAIL! in Odin. am i doing something wrong?

rachelrgr said:
i have a sm-g900v BOG5. i bricked mine phone so i tried #4 as you said and get FAIL! in Odin. am i doing something wrong?
Click to expand...
Click to collapse
You can grab the stock firmware, either OG5. OK3, or PB1 (newest), and flash with odin in the AP slot, I also recommend grabbing the PIT file (goes in the PIT slot). If you want root, then just go ahead and grab the PB1 and follow the directions on this link.
Firmware Link: http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370