[Q] Custom recovery on Galaxy s4 AT&T - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

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

Related

[RECOVERY] ClockworkMod Touch 6.0.2.3 flashable zip (update 2012-12-19)

Hey Guys
I am sharing the latest CWM recovery images; CWM 6.0.2.3.
To be straight, I used Koush's Recovery Builder to build these
latest recovery images in touch.
And so I do not take any credit, all of it to Koush. Also, I didn't
publish a thread for this in development section since I didn't
perform any development on this.
Download link:
ClockwordMod Touch 6.0.2.3-p3100
ClockwordMod Touch 6.0.2.3-p3110
ClockwordMod Touch 6.0.2.3-p3113
How to build on your own?
Visit the Recovery Builder
Click on the "Existing Devices" tab.
Now under the Existing Devices dropdown, select "p3100" or your device.
Tick "Touch Recovery" option if you desire for the touch variant, otherwise do not touch it.
Now click on the blue colored "Build" tab.
The page will then prompt you with a reference build ID, take note of it.
Now continue to build server.
Look for the corresponding build ID.
Once its done, click on it.
You can now download your "recovery.img" build.
How to flash?
Flash through CWM recovery.
Updated the OP with the newer version and a flashable zip.
Hope you enjoy it.
If You like just hit the thanks button.
I did instal on my tablet and worked without any problem.
I just want to say I´m not responsible for any brick, damage or anything else that happens to your tablet.
i need to sign in to the site to download right ?
any other testers here ?
thanks a lot for sharing...have you wiped and flashed files from it ?
You don't need to wipe. You flash it with Odin as another cwm recovery.
After installed I flashed some goodies and made a backup and worked perfectly.
If someone else test it will be great if and some feedback for other people.
Sent from my GT-I9300 using xda premium
And I think 4 shared need to subscribe
Sent from my GT-I9300 using xda premium
I went thru the steps for the p3113 (my version of the 7" tab 2) and it outputs a recovery.img file after about 5 minutes to build it, how do I make that an Odin flashable .tar like you have?
I have attached the recovery.img to this thread for the p3113 if it's simpler for you to do it then to walk me through it, any help would be appreciated.
image file can be flashed with mobile odin i read
thanks for second link
but havent flashed
will give yellow triangle ?
rraaka said:
image file can be flashed with mobile odin i read
thanks for second link
but havent flashed
will give yellow triangle ?
Click to expand...
Click to collapse
I've not rooted yet, I'm just getting setup for it and wanted the latest stuff to do it with.
CWM TOUCH 6.0.1.9 for P3110
https://hotfile.com/dl/183312759/30a80ea/recovery.img.html
Tested: works well.
Flash with Mobile Odin or Odin
@Marcelo.tti: thank You very much to make this possible
daniel644 said:
I went thru the steps for the p3113 (my version of the 7" tab 2) and it outputs a recovery.img file after about 5 minutes to build it, how do I make that an Odin flashable .tar like you have?
I have attached the recovery.img to this thread for the p3113 if it's simpler for you to do it then to walk me through it, any help would be appreciated.
Click to expand...
Click to collapse
I put the file link in the OP. Thanks to build the image file
rraaka said:
image file can be flashed with mobile odin i read
thanks for second link
but havent flashed
will give yellow triangle ?
Click to expand...
Click to collapse
No It won't.
I did an update to the thread with link for .tar images files to p3110 and p3113. Thanks to @daniel644 to build the image file for p3113 and @monfro to build the image file for p3110.
Here is a guide to build a .tar file to flash with odin.
You have to use the commands below with Linux. Just make sure you are in the correct folder to make the commands. It's good to put the file in the personal folder as the terminal always open in this folder.
$ tar -H ustar -c recovery.img > recovery.tar
$ md5sum -t recovery.tar >> recovery.tar
$ mv recovery.tar recovery.tar.md5
I have downloaded the 3113 version twice. Odin always says md5 does not match and then fails the flash. Any ideas?
Here is the output
<ID:0/003> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> ClockWordMod_touch-6.0.1.9-p3113.tar.md5 is invalid.
<OSM> End...
d11dog11 said:
I have downloaded the 3113 version twice. Odin always says md5 does not match and then fails the flash. Any ideas?
Here is the output
<ID:0/003> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> ClockWordMod_touch-6.0.1.9-p3113.tar.md5 is invalid.
<OSM> End...
Click to expand...
Click to collapse
remove the .md5 off the end of the file name, thats what I've done in the past in similar situations.
daniel644 said:
remove the .md5 off the end of the file name, thats what I've done in the past in similar situations.
Click to expand...
Click to collapse
Worked perfectly. Thanks!!
Sent from my Galaxy Nexus using Tapatalk 2
Finally decided to flash CWM and Root and ROM all in one night, wanted to see how long the stock ROM on a full charge would last using it as strictly a music player for when driving (22 DAYS for the record).
Honestly, as much as I like being able to TOUCH what I want to do it's just ugly and you have to scroll to see anything, but here is another user confirming the build for the P3113 works perfectly.
Now running this ROM as my first Custom on this device http://forum.xda-developers.com/showthread.php?t=2028663
Now all I need is for Supercurio to release his Voodoo Sound with Tab 2 support, he said when he releases the one for the WM1811 in the S3 it will also do our Tab 2's, OH YEAH!!!
Op Updated with the newer version.
Tested for p3100 end works good with no problem with the flashable zip.
If someone can test the other zips and say it's ok I'll be really grateful.
You can also get this CMW Recovery by downloading ROM Manager and let the app update it by itself.
Can You update the ClockworkMod Touch Recovery for p3100, p3110, p3113 to the version 6.0.2.7 ???
RrOoSsSsOo said:
Can You update the ClockworkMod Touch Recovery for p3100, p3110, p3113 to the version 6.0.2.7 ???
Click to expand...
Click to collapse
p3100 : http://forum.xda-developers.com/showthread.php?t=2064871
p3113 : http://forum.xda-developers.com/showthread.php?t=2073854
if you need 3110 then just build the recovery.img using the link in the OP and use winrar to "insert" that recovery.img into the zip replacing the one in the zip, thats how the p3113 builds where made.
I have a problem with flashing. I want to flash AOKP, but first I need CWM and root (obviously). I set USB debug settings. I'm using Odin, and I flash CWM, Odin says PASS and everything is green. But when I restart and boot into recovery the stock rcovery shows up. I'm on stock JB rom btw.
Other methods say that I should use Rom Manager which needs root which needs CWM in the first place.
I'm baffled here, what am I doing wrong?
sterby81 said:
I have a problem with flashing. I want to flash AOKP, but first I need CWM and root (obviously). I set USB debug settings. I'm using Odin, and I flash CWM, Odin says PASS and everything is green. But when I restart and boot into recovery the stock rcovery shows up. I'm on stock JB rom btw.
Other methods say that I should use Rom Manager which needs root which needs CWM in the first place.
I'm baffled here, what am I doing wrong?
Click to expand...
Click to collapse
your VERY FIRST boot up that you do has to be straight into CWM after using Odin to flash the .tar, which is why your supposed to uncheck auto reboot and f reset time in Odin, if your tablet boots up it will automatically revert back to stock recovery.

[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

Difficult Soft Brick - Need Urgent Help

I think it's a soft brick because I can get into download mode. Flashing anything in Odin fails. I posted this in xBeerDroidx's All In One Guide:
I went through the entire process of
1. returning to stock MF3 (I was using SafeStrap 3.65 and Hyperdrive 10.1 successfully...wanted to try the MK2 > SafeRoot > SafeStrap 3.71 > HD Rls 12)
2. Ran Update.zip successfully, got to MK2
3. Ran SafeRoot - successfully rooted phone
4. Installed SafeStrap 3.71 APK - no issues
5. From SS Recovery, installed HD Rls12 went OK but had an issue with the reboot menu
6. Installed the AT&T compatibility pack, still had issues with reboot menu, so I thought I'd re-run the HD RLS12 install
7. Went into SS Recovery, did a wipe but this time I did a system wipe...this is where I FU'd, I think
8. Still in SS recovery, I then hit the reboot button...my OS was gone so it stayed on the Samsung screen indefinitely.
I can still get into Download mode, but when trying to reflash the 4 MF3 files via Odin, I get a fail every time. I've tried to flash just the Platform, or all but the bootloader, (thinking this was where my write error occurred), and it seemed to go OK but still failed.
I'm stuck with a phone that can enter Download mode but that's it.
And was advised to get the .PIT file for my device. I found what was said to be the proper .PIT file for my build (MF3). I tried flashing the .PIT alone, and it seemed to do something, then reset my phone, but when the phone re-booted, it had a yellow triangle and a statement about unauthorized software. It would go no further. So I added the .PIT file to Odin, along with the other 4 MD5 files, and I get these results every time:
<ID:0/010> 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> PLATFORM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> MODEM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<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/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> sbl1.mbn
<ID:0/010> NAND Write Start!!
<ID:0/010> sbl2.mbn
<ID:0/010> sbl3.mbn
<ID:0/010> rpm.mbn
<ID:0/010> aboot.mbn
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can anyone help me?
JohnnyMac999 said:
Wanted to try the MK2 > SafeRoot > SafeStrap 3.71 > HD Rls 12)
Click to expand...
Click to collapse
This is where you went wrong... once you update to MK2 it is IMPOSSIBLE to downgrade to a lower firmware due to hardware related issues caused by the MF3 update. Go back the this thread and read how to go use your semi-bricked MF3 device to upgrade back to stock MK2. As for running stock MF3 your never again be able to unless the bootloader is unlocked at some point. This was stated multiple times in many threads around the forum... please take your time to read and search before jumping into things. It can be assumed with any future S4 upgrades that you are committing to that update with no chance of returning to a previous one.
You are the man! I've already flashed the MJ6 recovery successfully, and am in the process of downloading the MF3 emergency files. Hopefully, before too long, I'll have my S4 back, humming away on Hyperdrive RLS 12!! As a side note, I see you're on GPE 4.2.2. When I first loaded SafeStrap and was able to load ROMs, I tried using a GPE ROM and was running into nothing but trouble. Hyperdrive 10.1 ended up being my daily driver until I caused this mess. Did you have to do anything special to get the GPE ROM working properly?
JohnnyMac999 said:
You are the man! I've already flashed the MJ6 recovery successfully, and am in the process of downloading the MF3 emergency files. Hopefully, before too long, I'll have my S4 back, humming away on Hyperdrive RLS 12!! As a side note, I see you're on GPE 4.2.2. When I first loaded SafeStrap and was able to load ROMs, I tried using a GPE ROM and was running into nothing but trouble. Hyperdrive 10.1 ended up being my daily driver until I caused this mess. Did you have to do anything special to get the GPE ROM working properly?
Click to expand...
Click to collapse
Nope, flashed it to the stock slot, then the MF3 modules. It's one of the many reasons I haven't updated to MK2 yet... I have no desire to have my phone locked down further. I'm just monitoring how Safestrap evolves, along with the BypassLKM exploit.
Remember that u are on MK2 now prior to bricked . ...U CAN'T DOWNGRADE TO MF3. ... after u unbricked your device u would end up with stock mk2 ... and u should know the rest of the SS guide on how to install custom rom. ..... make sure try it first on slot 1 before u install to stock slot and ALWAYS DOUBLE CHECK WHICH ROM SLOT ARE ACTIVE BEFORE REBOOTING. ...... GOODLUCK. .........FOR MK2 FIRMWARE U CAN ONLY INSTALL 4.3TW ROM........U CAN'T INSTALL GPE,CM,AOSP,AOKP AS OF RIGHT NOW....... :crying::crying:
......MOD PLEASE MOVE THIS TO Q&A SECTION.....
Swyped from MF3 Deadly Venom SS
ted77usa said:
Remember that u are on MK2 now prior to bricked . ...U CAN'T DOWNGRADE TO MF3. ... after u unbricked your device u would end up with stock mk2 ... and u should know the rest of the SS guide on how to install custom rom. ..... make sure try it first on slot 1 before u install to stock slot and ALWAYS DOUBLE CHECK WHICH ROM SLOT ARE ACTIVE BEFORE REBOOTING. ...... GOODLUCK. .........FOR MK2 FIRMWARE U CAN ONLY INSTALL 4.3TW ROM........U CAN'T INSTALL GPE,CM,AOSP,AOKP AS OF RIGHT NOW....... :crying::crying:
......MOD PLEASE MOVE THIS TO Q&A SECTION.....
Swyped from MF3 Deadly Venom SS
Click to expand...
Click to collapse
Thanks Ted. Would you mind giving me a hand with this? NightHawk pointed me to your thread, but I am unsure whether to use the "
MK2_UNBRICKED_METHOD_(HARD-BRICKED)" or the separate files to recover from a soft brick - "ONLY USE THESE IF U (SOFT-BRICKED)". I tried both, unsuccessfully unfortunately, but maybe I missed something.
When going through the soft-bricked files, "Stock Recovery" and "Stock Modem" seems to check out fine, according to Odin's MD5 verification. The last one, labeled "Boot" failed the MD5 check. I put Stock Recovery in PDA, Stock Modem in Phone and was attempting to put BOOT in BOOTLOADER. Maybe I did something wrong? Should I flash them one at a time?
Thanks in advance, and yes, I did hit your Thanks button, and will keep doing so every time I log in!!
John
Also, I assume Deadly Venom is a TW 4.3 ROM? Maybe I'll give that one a shot if I ever recover this wonderful piece of equipment!
JohnnyMac999 said:
Thanks Ted. Would you mind giving me a hand with this? NightHawk pointed me to your thread, but I am unsure whether to use the "
MK2_UNBRICKED_METHOD_(HARD-BRICKED)" or the separate files to recover from a soft brick - "ONLY USE THESE IF U (SOFT-BRICKED)". I tried both, unsuccessfully unfortunately, but maybe I missed something.
When going through the soft-bricked files, "Stock Recovery" and "Stock Modem" seems to check out fine, according to Odin's MD5 verification. The last one, labeled "Boot" failed the MD5 check. I put Stock Recovery in PDA, Stock Modem in Phone and was attempting to put BOOT in BOOTLOADER. Maybe I did something wrong? Should I flash them one at a time?
Thanks in advance, and yes, I did hit your Thanks button, and will keep doing so every time I log in!!
John
Click to expand...
Click to collapse
Appreciated the Thank button. .... It was created for that purpose. .......BTW u should only flash it on PDA....one at the time and if md5 check failed or different ....please redownload the files......
JohnnyMac999 said:
Also, I assume Deadly Venom is a TW 4.3 ROM? Maybe I'll give that one a shot if I ever recover this wonderful piece of equipment!
Click to expand...
Click to collapse
Yes Sir. .... Both Deadly Venom and Dark Carnage are base from international rom 4.3 ML6. .... For ATT users. ..... For other US carrier might also work but Need to enter APN manually. ......As far as unbricking your phone follow post #3 from my thread and download all the MF3 emergency files. .... Recovery.mj6.tar.md5. .... and make sure u also download MF3>MK2 update. Zip files from OP (Original Post) coz u need it in the end of the unbricked_ Method. ..... Either u flash that update.Zip (mf3> mk2) from stock recovery by choosing apply update via external sd card or apply update via adb by using adb sideload.... check post#2 on how to update. ...... let me know which part that u don't understand. ......Goodluck. .....:thumbup::thumbup:
Swyped from MK2 Dark Carnage SS Edition
ted77usa said:
Appreciated the Thank button. .... It was created for that purpose. .......BTW u should only flash it on PDA....one at the time and ig md5 checked different....please redownload the files......
Yes Sir. .... Both Deadly Venom and Dark Carnage are base from international rom 4.3 ML6. .... For ATT users. ..... For other US carrier might also work but Need to enter APN manually. ......As far as unbricking your phone follow post #3 from my thread and download all the MF3 emergency files. .... Recovery.mj6.tar.md5. .... and make sure u also download MF3>MK2 update. Zip files from OP (Original Post) coz u need it in the end of the unbricked_ Method. ..... Either u flash that update.Zip (mf3> mk2) from stock recovery by choosing apply update via external sd card or apply update via adb by using adb sideload.... check post#2 on how to update. ...... let me know which part that u don't understand. ......Goodluck. .....:thumbup::thumbup:
Swyped from MK2 Dark Carnage SS Edition
Click to expand...
Click to collapse
One part I don't understand is in gtj0's guide, lines 7&8:
7. Force Reboot the phone back into Download mode (Voldown+Home+Power) and restart Odin.
8. The phone should now reboot to a black screen with the pulsing notification LED.U need to install...
He says force the phone into Download mode, and re-start Odin. The very next line says 'the phone should now re-boot'. What happens after line 7 that we needed Odin for?
That was If you coming from MJ6 his original thread to go back to Mj6 and then use the MJ9 update zip..... Since we coming from newer rom MK2. ... It would stuck on download mode .... That's when u need to install stock recovery .... Either Recovery.mj6.tar.md5 or i337mk2 stockrecovery.tar.md5 (either way worked) and then u need to force reboot to stock recovery. ..and then flash mf3> Mk2 update zip. ... follow post#2 on how to update. .... There is two method. ....apply update via external card or using adb sideload...... Goodluck
Swyped from MK2 Dark Carnage SS Edition
JohnnyMac999 said:
One part I don't understand is in gtj0's guide, lines 7&8:
7. Force Reboot the phone back into Download mode (Voldown+Home+Power) and restart Odin.
8. The phone should now reboot to a black screen with the pulsing notification LED.U need to install...
He says force the phone into Download mode, and re-start Odin. The very next line says 'the phone should now re-boot'. What happens after line 7 that we needed Odin for?
Click to expand...
Click to collapse
I went back through Post 3, re-downloaded all the files, everything has gone as you suggest it would to this point. I am re-downloading the update.zip file (MF3>MK2) from post 1 and am about to do the final step in the process. This is the exact same process I used yesterday when I tried to recover this the first time, but once I got to the step of side-loading the update file, I got an 'Error 7' failure from the 'asserts' line in the update script. Hopefully a re-DL will make things right this time! Keep wishing me luck!
Update: New DL for update.zip completed late. Just finished final step with the same failure as before:
Verifying current system....
assert failed: apply_patch_check( "system/SW_Configuration.xml", "acdd86b773e13cca512e4bb4f7c88a8489640994", "428f3b805bef7bc04df9eab6b262ff39f416cc41")
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
Any ideas?
Update: I'm back to MK2. The process was a bit painful, but if you follow the instructions in this post: http://forum.xda-developers.com/showthread.php?t=2618314, you will recover. Just read everything first!! I actually recruited help from a patient buddy that got me to MJ9, then I used the Update-mj9-mk2.zip file to takeme the rest of the way.
Special thanks to Ted77 for his patience, guidance and files!! (Yes, I will hit your 'Thanks' button!)
Moderators, please close this thread.

[ROM][Guide][FULL ODIN FILES][ATT][OC1][OTA with KEEP ROOT][Soft Brick FIX]

{
"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"
}
Stock AT&T Galaxy Note 3 ​
Update Software for Samsung Galaxy Note 3 (SM-N900A)
How to updated to OC2 if your OTA failed
1. Download and unzip and copy this Folder to OC1 stock root backup to your TWRP backup folder,
\TWRP\BACKUPS\0b70b440\N900A_OC1_Lollipop_Stock_Rooted_Backup
2. Copy OC1 kernel recovery installer to your sdcard SM-N900A_N900AUCUEOC1_KERNEL_Recovery-Flashable.zip
*** You can also go ahead and copy Safestrap-HLTEATT-NC2-3.75-B03[1].apk and NC2 Flasher to your sdcard ***
3 Download the OC2 OTA 2400258.cfg
rename the 2400258.cfg OC2 to 2400258.zip and copy to your sdcard
4 Install the OC1 backup,
N900A_OC1_Lollipop_Stock_Rooted_Backup.zip
5. Install OC1 Kernel
SM-N900A_N900AUCUEOC1_KERNEL_Recovery-Flashable.zip
6. (I did a factory wipe , but Warning you will loose UserData settings and Apps you installed) You might try without but if you had a custom SystemUI and Touchwiz as I did it might FC because you have setting in Userdata pertaining to the Custom apps that you will over write with the OC1 backup.
7. Select Reboot and then select Recovery to boot to stock recovery and install as a update from external storage. mine installed with no issues.
8. To get safe strap back working Download and copy Safestrap-HLTEATT-NC2-3.75-B03[1].apk to sdcard (if you have not done yet)
9. Download and copy NC2 Flasher by benwaffle
10. Install Safestrap-HLTEATT-NC2-3.75-B03, run app and install recovery ( do not press reboot to recovery, it will only take you to stock recovery)
11. Install NC2 Flasher app and then use it to boot to recovery.
12. Do a backup of your new OC2
Now you can customized and do what you want
_______________________________________________________________________________________________
How to updated to OC2 with a SafeStrap OC2 Backup (rooted)
1. Download the following stock-2015-08-14--10-18-08 LRX21V.N900AUCUEOC2.zip SafeStrap Backup
Unzip stock-2015-08-14--10-18-08 LRX21V.N900AUCUEOC2.zip and copy the stock-2015-08-14--10-18-08 LRX21V.N900AUCUEOC2 folder to your SafeStrap backup folder, should look like this,(your number might be diffrent)
\SAMSUNG-SM-N900A\Card\TWRP\BACKUPS\0b70b440\stock-2015-08-14--10-18-08 LRX21V.N900AUCUEOC2
https://mega.nz/#!6INyVRAY!Jjbp7xv2MFNb2Zf7vSEWVxoqG2S9EzJ3HojWampyado
3. Download and copy to sdcard the OC2 firmware SM-N900A_N900AATTEOC2_Firmware_Recovery-Flashable.zip UPDATED now has OC2 Recovery
https://mega.nz/#!iF8xBS6Z!XQNgLscWM5SOOddlkunQYBCQp2QO03raEMN91sF1g34
4. Do a factory wipe while in recovery, especially if your coming from a custom rom. (Highly recommend doing to prevent boot Fail and file FC's)
5. Install (restore) backup stock-2015-08-14--10-18-08 LRX21V.N900AUCUEOC2
6. Install the SM-N900A_N900AATTEOC2_Firmware_Recovery-Flashable.zip
_________________________________________________________________________________________________________________
OC2 Fix's and ADD-ON'S Install with a SafeStrap
Many Thanks to @Ticklefish for his TickleMyAndroid Modding tool Check it out !!..
OC2 Modem Recovery Flashable ( you must have OC1 modem for OTA modem Patch to work)
SM-N900A_N900AATTEOC2_Modem_Recovery-Flashable.zip (3.68 MB)
http://forum.xda-developers.com/attachment.php?attachmentid=3484080&stc=1&d=1443054905
Remember_WIFI_ATT_OC2_Lollipop_Note3.zip Install to remeber the WiFi password when you reboot your phone
https://mega.nz/#!jJMC3YAZ!1BtH0zv70nDZMgF2jcPNGdwFeBk8kcd6FjBqYnE7oxU
UPDATED Deletes the Knox files and stops the “Unauthorized actions have been detected. Restart your phone to undo any unauthorized changes.” Thanks @Hitmizzle
SafeStrap_OC2_Lollipop_Knox_Remover.zip
https://mega.nz/#!mYMAlQAB!lTGAIgOe0h-o-o6MntlkBnuP0L2-VsBho8Y6MD_i2_M
ATT_N900AUCUEOC2_StageFright_Files_recovery_installer.zip (For those on OC1 who want the fixed lib files)
https://mega.nz/#!7IdAGDAR!UZr1IbpvHIxm_SckOHOejqWcAdHfjKLO5hpC27c_-V4
ATT_OC2_Lollipop_Stock_5x6_TouchWizHome_K_Installer.zip Home Screen and App Drawer is 5x6
https://mega.nz/#!iMtG3ZCI!q9d41592Ii4LGG8fYuHdOC_cLaTOc9ShPM6D0E-OlhY
Unzip SafeStrap_Lollipop Debloater.zip, edit updater-script and delete anything you want to keep
rezip and install with safestrap to remove Bloat Stuff
Original Script Developer : @Kushan02 Aroma Installer
SafeStrap installer by carl1961
SafeStrap_Lollipop Debloater.zip
https://mega.nz/#!rV9HWYJS!d1o0HzGeMBLLUPQZ6cyR8kLucowawpdFhGEbSHTxTF0
Aroma Installer Script Developer : @Kushan02 Use FlashFire to install
Aroma_Lollipop_Debloater_by_Kushan02_signed.zip
http://forum.xda-developers.com/attachment.php?attachmentid=3263174&stc=1&d=1429071215
ATT_A8 Boot_Animations_Recovery_Installer.zip 1.2 MB
https://mega.nz/#!6VUizaSA!jl3YYeLmx6W_cbiL801rw5_dVImzyOo6qgoBlxRgVtY
ATT_A8__Note3_Weather_Recovery_Installer.zip 28.5 MB
https://mega.nz/#!GJ8imbjA!0OnF1mTdgQLQ3CLMQz6vZ0iYEzv6LdePDtSkXWP1fQ0
ATT_A8_Recovery_SBrowser_3.0.38_Installer.zip 29.2 MB
https://mega.nz/#!aFEHEIRD!rKxCLWpUUTBxCjZ0MpRibqoYpAccPo8Wn9SxvTO7a9o
ATT_A8_Sounds_Recovery_Installer.zip 8.5 MB
https://mega.nz/#!uBEBVCoC!A6x5VnuxI95dlIFtsZiEQW9mLAJ6kriTPT17FGdT7Gs
A8_Wallpapers_copy_to_sdcard.zip 5.8 MB Use Gallery to get them
https://mega.nz/#!3EM23SrK!FJyhQc1d6Zs2b98y7g8D5ax2qoukBKBT7_7G6fOBMnM
Remove_A8_Wallpapers_from_sdcard.zip 120 KB
https://mega.nz/#!7NcFgLTD!6M3uPY7zBZBd0jxhAh2vJx-mXRAXk20B5kjFbLhH_7c
Android_6_Nexus6_Bootanimation-recovery-flashable.zip 4.5 MB
https://mega.nz/#!DZt3TJgI!G0HX30FxgXjfiVvBg4bEmCrqmqLO0nqmuB_c4QNDios
******************************************************************************************************************
ATT-LRX21V-N900AUCUEOC1 LOLLIPOP
UPDATING TO LOLLIPOP AND KEEPING ROOT
FIRST DO THIS
1. You must have Safestrap Recovery working (you can boot to safestrap) If Not go to NC2 Files and Install NC2 Odin Files and get safestrap working.
2. First Do a TWRP Backup if you have not done one.
3. download below files and copy to your SDCARD
"N900A_NL1_Stock_Rooted_Backup" from [How-To] Root N900AUCUDNL1 4.4.4 (12-24-2014) THANKS !!! @muniz_ri and copy to your TWRP backup folder (here is my TWRP Folder TWRP\BACKUPS\0b70b440\N900A_NL1_Stock_Rooted_Backup
SM-N900A_NL1_Firmware_Recovery-Flashable.zip
N900A_NL1-OC1-KeepRoot_OTA.zip
UPDATE-SuperSU-v2.45.zip THANKS !!! @Chainfire
SM-N900A_N900AUCUEOC1_KERNEL_Recovery-Flashable.zip
1. Boot to safestrap recovery, Press Wipe and slide the slider to ok the wipe.
2. Restore Backup N900A_NL1_Stock_Rooted_Backup This gives us rooted NL1
3. Without leaving Recovery install SM-N900A_NL1_Firmware_Recovery-Flashable.zip This installs the NL1 firmware (or N900A_NL1-OC1-KeepRoot_OTA.zip will fail)
4. Without leaving Recovery install N900A_NL1-OC1-KeepRoot_OTA.zip
5. Without leaving Recovery install UPDATE-SuperSU-v2.45.zip to update SuperSu for Lollipop
6. Without leaving Recovery install SM-N900A_N900AUCUEOC1_KERNEL_Recovery-Flashable.zip to boot to New Lollipop Update.
Thanks to @muniz_ri
I compared his N900A_NC2-NJ5-KeepRoot_OTA.zip to original NJ5 OTA and seen what files he changed and did the same to OC1 OTA
Installing LOLLIPOP with Root Using TWRP Backup Of LOLLIPOP OC1 OTA
FIRST DO THIS
1. You must have Safestrap Recovery working (you can boot to safestrap) If Not go to NC2 File below and Install NC2 Odin Files and get safestrap working.
2. Do a TWRP Backup if you have not done one.
1. Download all your files needed and copy to SDCARD
N900A_OC1_Lollipop_Stock_Rooted_Backup.zip (unzip and copy folder to TWRP backup folder)
UPDATE-SuperSU-v2.45.zip
SM-N900A_OC1_Firmware_Recovery-Flashable.zip 49.0 MB
SM-N900A_N900AUCUEOC1_KERNEL_Recovery-Flashable.zip
1. Unzip N900A_OC1_Lollipop_Stock_Rooted_Backup.zip and copy to your TWRP backup folder (here is my TWRP Folder TWRP\BACKUPS\0b70b440\N900A_OC1_Lollipop_Stock_Rooted_Backup
2. Odin install the NL1 Firmware.. Bootloader, Modem and Recovery (If your not Running NL1 and your on NC2 ) (just install AP recovery, BL bootloader and CP modem)
3. Boot to safestrap recovery, Press Wipe and slide the slider to ok the wipe.
4. Restore the backup "N900A_OC1_Lollipop_Stock_Rooted_Backup"
5. Without leaving Recovery install the SM-N900A_N900AUCUEOC1_OC1_Firmware_Recovery-Flashable.zip
6. Without leaving Recovery install UPDATE-SuperSU-v2.45.zip to update SuperSu for Lollipop
7. Without leaving Recovery install SM-N900A_N900AUCUEOC1_KERNEL_Recovery-Flashable.zip to boot to New Lollipop Update.
8. Press Reboot to boot Your New OTA with Root
UPDATE:
Thanks to @benwaffle for NC2 Flasher and figuring out how to flash kernel in Safestrap recovery
Booting safestrap and using recovery without a PC
NC2 Flasher by benwaffle
From 4.4.4 Rom's
install and give SuperSU rights, Press "Flash NC2 Kernel" kernel will install. then press OK to Reboot , or use your back arrow if your not ready to reboot. @benwaffle Latest UPDATE app is AWESOME!!
SM-N900A_N900AUCUEOC1_KERNEL_Recovery-Flashable.zip
SM-N900A_NL1_KERNEL_RecoveryFlashable.zip
Download and copy recovery installable kernel installer to sdcard, after your finished in safestrap (installing 4.4.4 rom's or add-on's Install the kernel of choice) the installer will copy boot.img to your internal sdcard and flashboot.sh will install Kernel
Using Odin and PC to install kernels
NC2-NL1-Kernel-Switch-Odin_v3.09.zip 17.8 MB
https://mega.co.nz/#!WF8wgbhS!sBP6TAvjULq1wxZn21hbzMHvWGPxH75N8ceaa20kFaw
LOLLIPOP Fix's
Remember_WIFI_AT&T_Lollipop_Note3.zip (123.7 KB)
http://forum.xda-developers.com/attachment.php?attachmentid=3249092&stc=1&d=1428363383
com.google.process.gapps FC pop up FIX
package name is com.google.android.gms
Lollipo_ATT_com.google.process.gapps_FC_fix_Removed_Recovery_Installer.zip (174.3 KB)
http://forum.xda-developers.com/attachment.php?attachmentid=3292062&d=1430519896
LOLLIPOP BloatWare Remover's
ATT_Bloatware_Remover_Recovery_installer.zip 176 KB
https://mega.co.nz/#!WFNHHDaK!kjySXsGE-Bw2YMZPxVQrySJNe948iM9nqPgDabZmY0s
Aroma Installers Running on AT&T Note3 Require @Chainfire FlashFire to run Aroma
Aroma_Debloater_by_Kushan02_signed ( I just replaced with a working update-binary-installer for FlashFire) All credit to @Kushan02 for his debloater
Aroma_Lollipop_Debloater_by_Kushan02_signed.zip
http://forum.xda-developers.com/attachment.php?attachmentid=3263174&stc=1&d=1429071215
ATT_Lollipop_Stock_FlashLight_Volume-UP_Toggle_Installer.zip 24.7 MB Thanks to @kmokhtar79 Original Thread
https://mega.co.nz/#!idlgSbIY!WQw0jgX7MH5bwqkw6Z2T-AsN-1FPBHGpTHvFXufeKFw
LOLLIPOP S6 ADD-ON'S
ATT_Albe95_S5_TouchWiz-S6_Theme_Recovery_Installer.zip 22.0 MB
https://mega.co.nz/#!OFM2jY4I!IYx2elvl6XTLsWZgqmKbpF2METcPDLaoBRPutazhpgw
ATT_Albe95_N4_TouchWiz-S6_Theme_Recovery_Installer.zip 22.5 MB 5x5 Icon grid and smaller icon's
https://mega.co.nz/#!7YFGQZAD!HO0IeW8X55dyoupuUwL5xjD_whhBbN2PaI8V6VUVtNI
ATT_S5 Lollipop Message App_Installer.zip 6.1 MB
https://mega.co.nz/#!XINg3LZa!JTUEvNIT9PNG7wlxKEs_eoTwWKWACXrfVYAcKEAF-LI
ATT_S6_SBrowser_Installer.zip 29.1 MB ported by Manh_IT
https://mega.co.nz/#!SYVQnaTa!MZSVN-AB-XM7ETd2XHE8dLsWZcq0tA39dScyKgWPeoo
ATT_S6_SecMyFiles2015_Installer.zip 2.8 MB Ported by @mohnishkat
https://mega.co.nz/#!qIdjVSrZ!Fe6m-a1aQv2_15pLX8RMk1dWiOqbJ_Rcpwt7A4i2Bj0
ATT_S6_Weather_Installer.zip 35.2 MB Ported by @mohnishkat
https://mega.co.nz/#!7YtFXDJA!hR6dd5nNrBpSG-mhXKV1rU56k8cPibsMPxSyrJg_uKw
ATT_S6_alemtro_Weather_No-Shaddow_Installer.zip 35.5 MB
https://mega.co.nz/#!qNkFlIoC!LG3ReiaMOjHHJ1YgqY1R7_cLuClAQfJCPbT2Vh62nMU
ATT_S6_SecCalculator_Installer.zip 390 KB Posted by @mohnishkat
https://mega.co.nz/#!rEUF3ZqB!omn91fDAA-PD0zR3agvbPdgzQVqRW6JmZKur3T69jZg
ATT_S6_SamsungIME_Installer.zip 6.9 MB ported by Manh_IT @Manh_IT
https://mega.co.nz/#!aVMjCI5R!tfZwkP5Jdra2GEbQ5lyFyFaRPGvN4-CELG-12JPQoPc
ATT_S6_Music_Installer.zip 2.0 MB Posted by @mohnishkat
https://mega.co.nz/#!KRU30CZa!Pkf9nEQ4H7pnb-U-Jg6doZ6T61kBhj4PJ9OtCLPTGTc
ATT_S6_SPlanner_by_Manh_IT_Recovery_Installer.zip 4.1 MB
https://mega.co.nz/#!fUE0SJ4D!oCdn9MEvalm0RAqqcFWcMTN2hG1ta6hU5I1VKEEloE0
Guides
Thanks to @Walter.White Original Thread http://forum.xda-developers.com/note-3-att/general/100-stock-lollipop-5-0-n900aucueoc1-t3069609
Thanks to Anonymous Source
Build Number: N900AUCUEOC1/N900AATTEOC1/N900AUCUEOC1
Backup anything important you might have on your phone before proceeding any further
Odin: 3.10 http://forum.xda-developers.com/showthread.php?t=2711451
Individual/Wipe Tars
AP Slot AFH (MD5: 52a7be63a94f034d7d285d046e06420f)
BL Slot AFH (MD5: 40b3395b138ef8c657089a29df1239fb)
CP Slot AFH (MD5: 59476097cb52e6672e3a5302a10d5093)
CSC Slot AFH (MD5: cde59a77b4d45c62869a5dd318233a69)
All-in-one/Non-Wipe Tars.
AP Slot AFH (MD5: 55d66efab12932ac7d64e83951d28a5b)
Download/Odin Mode Flash Counter after OC1 update: S2, T2, R2, A3, P2.....
GOOD NEWS..... Downgrade to NL1/NC2 still possible!!!!!​
UPDATE NL1 [How-To] Root N900AUCUDNL1 4.4.4 (12-24-2014) Tanks!!! to @muniz_ri
Please Thank muniz_ri he is very talented with code and does all this work blind (without a note 3) he has polity corrected me more than once
[How-To] Install & Root N900AUCUDNJ5 @muniz_ri
SafeStrap NL1 ROM Installer
AT&T ROOT,BUSYBOX,INIT.D Safestrap Recovery Install NL1 ROM
Odin Install's UPDATED from @Walter.White Thanks!!
AT&T [100% Stock] KitKat 4.4.4 (N900AUCUDNL1) Odin Tars download these for safekeeping Thanks to @Walter.White (don't forget to press thank's button)
Kernel http://d-h.st/fvW
Modem http://d-h.st/F2q http://d-h.st/o2F
N900AATTDNL1_FIRMWARE.zip 48.0 MB
https://mega.co.nz/#!fctiwLaa!_ljwhXkj-lWyRe11zdwHK6EedsQikmfJDb35q-A1gPc
Thanks!! @larrybigbid for Donation
]*****************************************************************************************************NC2 Files ******************************************************************************************************
Installing ODIN
1. You do NOT have to unroot or remove anything from your phone
2. DOWNLOAD>>>>>>>>N900AUCUCNC2 ODIN Files @BlackRam1500 THANKS!!
HLTE_USA_ATT.pit
Media Fire Link's
AP_N900AUCUCNC2_722276_REV03_user_low_ship_MULTI_CERT.tar.md5 Mirror Link Mega
BL_N900AUCUCNC2_722276_REV03_user_low_ship_MULTI_CERT.tar.md5 Mirror LinkMega
CP_N900AUCUCNC2_722276_REV03_user_low_ship_MULTI_CERT.tar.md5 Mirror Link Mega
CSC_ATT_N900AATTCNC2_722276_REV03_user_low_ship_MULTI_CERT.tar.md5 Mirror LinkMega
N900AUCUCNC2_N900AATTCNC2_N900AUCUCNC2_HOME.tar.md5 Mirror LinkMega
Links from @andygev35 Thanks !!!
Here's a direct link to the Odin files. No ad-filled file hosting site nonsense, bandwidth throttling etc...
AP AP_N900AUCUCNC2_722276_REV03_user_low_ship_MULTI_CERT.tar.md5
BL
BL_N900AUCUCNC2_722276_REV03_user_low_ship_MULTI_CERT.tar.md5
CP
CP_N900AUCUCNC2_722276_REV03_user_low_ship_MULTI_CERT.tar.md5
CSC
CSC_ATT_N900AATTCNC2_722276_REV03_user_low_ship_MULTI_CERT.tar.md5
All-in-One N900AUCUCNC2_N900AATTCNC2_N900AUCUCNC2_HOME.tar.md5
Odin_3.09.zip
3. Boot into Download Mod and install Odin file's
4. Root with Towel Root
MIRROR LINK
5. Install BusyBox
MIRROR LINK
6. Install SafeStraphttp://forum.xda-developers.com/showthread.php?t=2572978​ MIRROR LINK
Samsung USB Driver (needed for ODIN)
(If you have weird issues, use the HLTE_USA_ATT.pit file (this reformat's the phone) But this does not touch your Internal sdcard
Warning !! Never Use the Pit file without installing all the firmware and software
If you want your internal sdcard OEM wiped, Boot into stock recovery and do a factory wipe WARNING!! you will loose all your Pictures and files on your Internal sdcard
Odin One File Install
Odin One File Install With Pit File ( Re-formats Your Phone Partitions)
********************************************************************************************************************************************************
Odin 4 File Install Will be Completely OEM NC2
WARNING!! you will loose all your Pictures and files on your Internal sdcard
Odin 4 File Install
Odin 4 File Install With Pit File ( Re-formats Your Phone Partitions)
DOWNLOAD>>>>>>>>N900AUCUCNC2 ODIN Files @BlackRam1500 THANKS!!​
NL1-NJ5-files-to-root.zip 9.0 MB
https://mega.co.nz/#!DIthBTBI!ClUC-5vCmoeys0byH9pcQfStcgH921m3_qsj4cc7_zY (busybox,Safestrap and tr.apk in one zip to copy to sdcard)
I'm on nc2. My phone isn't stuck in download mode. Can I use this method ?
Note 3 Secret CODES Great for testing your phone
Found these codes and tested working on my Note 3 N9005 : Original Thread thanks to @xdm9mm
*#06# -- To check IMEI No.
*#9090# -- Diagnostic Configuration
*#1234# -- to check software version of phone.
*#272*IMEI# -- Reset User data + Change Sales Code
*#12580*369# -- to check software and hardware information.
*#0228# -- Battery status (ADC, RSSI reading)
*2767*3855# -- Full factory reset (Don’t dial it does not ask you to confirm unless you have problem)
*#0*# -- This Code shows Screen Test Menu (LCD Test Menu) Hidden Menu
*#7353# -- Self Test Mode (2nd Hidden Menu)
thanks to vndnguyen for the following:
*#34971539# Camera firmware check/update
*#2263# Service Mode - Baseband selection
*#9900# SysDump
*#0011# Service Mode - Radio parameters
*#0808# USB Settings
*#2222# Service Mode - FTA HW Version
*#1111# Service Mode - FTA SW Version
shortcutmaster.lite
Description
Shortcut Master is a powerful tool for creating, capture, searching... shortcut. It can reveal any hidden shortcuts, hidden secret codes... in your device.
Updating Instructions
If You Looking For STOCK UrDroid Custom ROM Go Here​
THIS IS ONLY FOR THOSE WHO TOOK THE NC2 BOOTLOADER (A3) , OR IF YOU WANT TO UPGRADE TO NB2
DO NOT INSTALL IF YOU WANT TO KEEP YOUR OLDER BOOTLOADER !! YOU CANNOT GO BACK !!
If you or stuck at the Download Mode screen because of a bad OTA install, want to just update,want to return phone to factory or for just a Unknown or (I'm not telling) reason it happened
For those who cannot get back to NC2 and MJ5 from a boot issue.
Then You can install this Leaked N900AUCECMGL KitKat that designgears Posted, to get your phone back up running, Then install the NC2 Firmware, to replace MLG firmware
You Cannot Use this Copy of MLG KitKat to down-grade to 4.3
Once You Updated to NC2 KitKat You cannot go back, You are burn to fuse 3
SW REV Check Fail [aboot] Fused 3 Binary 2
User's Comment's​
KuRuPtIoN said:
Hey, I finally got a chance to do what you said, my phone took the ota with no problems at all and fixed the issues I was having. Thanks a lot!
Click to expand...
Click to collapse
__________________________________________________________________________________________________________________________________________________________________________________________​
K-Alzwayed said:
This thread saved my butt two nights ago. Soft bricked my phone and this got me back and running. I'd say this is the other "restore to mj5" thread. I had no ROM on my phone and rebooted then got stuck on galaxy note 3 screen. It's even way easier than the restore to mj5 method. Thank you so much, Carl!
If you have a fix that you think would help users, please share it here http://forum.xda-developers.com/showthread.php?t=2793441
Click to expand...
Click to collapse
__________________________________________________________________________________________________________________________________________________________________________________________​
larrybigbid said:
I got it installed!!!! I had to start over from the very beginning and it worked. Thanks for the help. I'm factory now.
Click to expand...
Click to collapse
__________________________________________________________________________________________________________________________________________________________________________________________​
carl1961 said:
since you did the MGL odin ver 2, you need to just odin install the NC2 firmware to replace MGL's apnhlos
NC2_Bootloader_N900AUCECMLG_VER_3 already had the correct NC2 firmware except the recovery, OTA will patch the recovery
also next time You have trouble with busybox uninstalling, just reboot the phone it will finish, when you try againg it shows it not installed, busybox app bug
Click to expand...
Click to collapse
Makman20 said:
Thanks man!!! back on stock %100. i should of read the OP better,
Click to expand...
Click to collapse
__________________________________________________________________________________________________________________________________________________________________________________________​
dieselford said:
My device was still on mj5. I used Odin and MLG ap and bl to run kk. I was able to revert to jb at anytime with a quick Odin flash. I now have used Carl's guide and upgraded to full NC2. I can no longer return to jb but the system seems to run better now and battery life is much better!
Click to expand...
Click to collapse
###########################################################################################################################################################​
Many thanks to ALL who helped and also provided files and firmware
@larrybigbid for NICE Donation and testing the OTA update
@jreed3786 for last NON modified NC2 backup files (except for the needed Safestrap , BusyBox and ROOT)
@K-Alzwayed for previous NC2 backup files (that fixed missing bin file)
@bri315317 For letting Us use his build.prop that get's Custom NC2 rom's running
@Walter.White for modem.bin and for LOT'S of advice and knowing how to get needed info and firmware
@1Zero3forlife for recovery and NON-HLOS.bin without his help OTA would not have worked
@MrFhenix How he said it could be done After taking the NC2 bootloader!
If I missed anyone please let me know
How to FIX a soft brick or Upgrade to NC2 Click HERE
****************************************************************************************************************************************************************************​
How to get NC2 OTA Update installed.
Video Installing AT&T NC2 OTA in 12 minutes !!
AP_N900AUCECNC2_FIRMWARE.tar.md5.zip Mirror MEGA Mirror>>>>>>>>Firmware Needed to install with odin so OTA works MD5 Number 5704164AAE4F65C5A86840F99C2B0823
ATT_Stock_KitKat_N900AATTCNC2_ROOT_OTA.zip >>> Stock NC2 Safestrap Recovery installer For OTA to work MD5 Number 38B9BAE5282AFAF53F7419130B800980
2400258.zip NC2 OTA Installer MD5 Number 0754E71B5DC1959497956243F295F89C MediaFire Link
2400258.zip NC2 OTA Installer MD5 Number 0754E71B5DC1959497956243F295F89C Mega Link
2400258.zip NC2 OTA Installer MD5 Number 0754E71B5DC1959497956243F295F89C Mega Link
Check Your downloads MD5 number
E01039EBEFC6AA6C7931D7467AF04057.......NC2_Bootloader_N900AUCECMLG_VER_3.zip
38B9BAE5282AFAF53F7419130B800980.......ATT_Stock_KitKat_N900AATTCNC2_ROOT_OTA.zip
5704164AAE4F65C5A86840F99C2B0823.......AP_N900AUCECNC2_FIRMWARE.tar.md5.zip
0754E71B5DC1959497956243F295F89C.......2400258.zip
Warning!!
Save pictures and personal files from Internal sdcard, Internal sdcard will be wiped !!
For those who took MLG Original Leaked KitKat firmware, You need to Odin install AP_N900AUCECNC2_FIRMWARE.tar.md5.zip For OTA to Work.
The OTA installer will patch your recovery to NC2
For those with NB4 or MJ5 and want to Upgrade to NC2 GO HERE then come back
Before Starting !!
YOU MUST Have SafeStrap Recovery installed.
You must have NC2 firmware installed.
1.copy 2400258.zip last OTA to external sdcard
2.copy ATT_Stock_KitKat_N900AATTCNC2_ROOT_OTA.zip to external sdcard ATT_Stock_KitKat_N900AATTCNC2_ROOT_OTA.zip is made from TWRP backup from jreed3786 stock phone, with supersu
3.copy also busybox, safestrap 3.75 to external sd card ( You need them to remove safestrap recovery afterATT_Stock_KitKat_N900AATTCNC2_ROOT_OTA.zip Install's )
4. Install ATT_Stock_KitKat_N900AATTCNC2_ROOT_OTA.zip This removes old ROM and installs all file needed by OTA installer
5. REMEMBER !!! For those with MJ5 and Safestrap 3.71 After phone reboots, boot into download mode and install the NC2 Firmware above (AP_N900AUCECNC2_FIRMWARE.tar.md5.zip)
also make sure you have a copy of SafeStrap 3.75 and BusyBox installer apps on your External SDcard to remove SafeStrap recovery later on...
6.Skip through setting up Rom, used My Files app to install busybox, safestrap 3.75,
7. then install busybox with app,
8. then Uninstall recovery with SafeStrap app,
9. then Uninstall BusyBox with BusyBox app,
10. Go to Application Manager, Uninstall, BusyBox and Safe Strap, Close out Applications manager
11. Use SuperSu to remove root (when supersu complains about knox let it disable it or root won't get removed)
12. verify you have 2400258.zip on external sdcard before you reboot phone, If you do not you will have reboot and put 2400258.zip there.
13. Boot to stock recovery and install the 2400258.zip ( hold Power, Volume UP and menu button until you see blue writing at top of screen then let buttons go)
when it's done your Official Stock Factory NC2
14. Verify by looking at these pictures below they show what 2400258.zip OTA should do.
if you see this picture bellow, then safestrap did not uninstall correctly and replace original e3fsck file.
If you see this picture below, the SuperSu did no uninstall correctly and replace original ddexe
these below show 2400258.zip OTA installing
Do not worry about:
E:unknown volume for path [/sdcard1]
E:unknown volume "/sdcard1"
REMEMBER !!! FOR Those who took MLG Firmware you need to odin install the AP_N900AUCECNC2_FIRMWARE.tar.md5.zip
then do these steps above
If You want STOCK Custom ROM
UrDroid_ATT_Stock_KitKat_N900AATTCNC2_Rooted_Deodexed_Ver_2
http://www.mediafire.com/?iy3yg4dzw998ncr
UrDroid_ATT_Stock_KitKat_N900AATTCNC2_Rooted_Odexed_Ver_2
http://www.mediafire.com/?9ml7i8uuin05owq
************************************************************************************************************************************************************************************************************************
Before You Install Read all you can about Installing Odin and stock Recovery on your phone. I am not responsible if anything happens to your device
For those Who Want to Upgrade from NB4 or MJ5 or If You Soft bricked, or who lost or wiped SafeStrap Recovery and cannot reload your rom.
************************************************************************************************************************​Quick Jump Start to Upgrade from NB4,MJ5 or to Recover From A Soft Brick
1 install with odin Mirror [URL="https://mega.co.nz/#!eNsSnZgS!0ZIjPBMXM-wwMYHPOlHyJPAlFLdlS85G3a-i-WRKIAI"]MEGA AP_NC2_FIRMWARE_N900AUCECMLG.tar.md5[/URL] It's inside NC2_Bootloader_N900AUCECMLG_VER_3.zip
2. after Leaked KitKat boots, skip through setup ( this is just to get your phone back)
3. reboot to download mod and odin install Mirror [URL="https://mega.co.nz/#!yANghRyA!H9lDyxktqrcYcQklLsOEdU_I0zxhdmIGjfkbIg5bU2o"]MEGA AP_N900AUCECNC2_RECOVERY.tar.md5[/URL]
4. Root with Towel Root
5. Install BusyBox
6. Install SafeStrap
7. Install Custom KitKat ROM
(If you have weird issues, use the HLTE_USA_ATT.pit file (this reformat's the phone))
Warning !! Never Use the Pit file without installing all the firmware and software (AP_NC2_FIRMWARE_N900AUCECMLG.tar.md5)
All files install with the one AP_NC2_FIRMWARE_N900AUCECMLG.tar.md5
aboot.mbn,boot.img,modem.bin,NON-HLOS.bin,rpm.mbn,sbl1.mbn,sdi.mbn,tz.mbn Firmware files from NC2 OTA Update, recovery and all other files or from MGL leaked kitkat
Installs:
Stock KitKat rom , All Credit to designgears for uploading Leaked KitKat MLG Rom​
Installing NC2_Bootloader_N900AUCECMLG_VER_3
Before You Install Read all you can about Installing Odin and stock Recovery on your phone. I am not responsible if anything happens to your device
FAST!! QUICK LINK--MediaFire------------------------------------------------------------------------->>>>>> NC2_Bootloader_N900AUCECMGL_VER_3.zip Mirror MEGA
MD5 Number E01039EBEFC6AA6C7931D7467AF04057​
Check MD5 Number with attached MD5 Checker (Verify a good download)​
--------------------------------------------------------------You can Also USE This Odin Installer For Fast Update to KitKat From Any Previous Firmware And Jump Straight to Custom Rom's-------------------------------------------------------------​
Download Files Explained:
NC2_Bootloader_N900AUCECMLG_VER_3.zip >>>>>>>NC2 Firmware MLG Recovery MLG ROM odin Installer Use to get a softed bricked Phone working MD5 Number E01039EBEFC6AA6C7931D7467AF04057
AP_N900AUCECNC2_RECOVERY.tar.md5.zip MEGA Mirror Install this after installing AP_NC2_FIRMWARE_N900AUCECMLG.tar.md5 to go straight to installing CUSTOM KK ROM'S, You can skip the OTA ( You would be over writing them anyway with your custom ROM)
tr.apk Used to get ROOT
busy box Needed for Safestrap
safestrap 3.75 Safestrap Recovery for KitKat Rom's
Install and Rooting Video by Face_Plant Thanks !! (Video is for previous Older install)
Face_Plant ROM Install Procedure :good:
1. Download NC2_Bootloader_N900AUCECMLG_VER_3.zip from the OP (should be ~1.5 gigs)
2. Once the file finishes downloading, right click and select "extract all".
3. Open the extracted folder and click on Odin3 v3.09.
4. Boot into Odin/download mode (volume down/home/power button all at the same time) and plug your phone into your PC (I used the USB 3.0 cable, but any USB cable should work).
5. Load AP_NC2_FIRMWARE_N900AUCECMLG.tar.md5 into the AP slot in Odin, click start, and wait for it to finish.
6. Your phone will boot up. Skip or complete the set up stuff. It's up to you.Odin should say "pass" (Give it time)
7. Root with Towelroot, install BusyBox and Safestrap, and get back to flashing!
Picture's or from previous Install, I will Update soon..
Unzip NC2_Bootloader_N900AUCECMGL_VER_3.zip to prefered folder
Have phone in Download Mode
Start Odin, Click AP
Select AP_NC2_FIRMWARE_N900AUCECMLG.tar.md5
Make sure your screen looks like photo below, Auto Reboot , F.Reset Time and AP checked, Binary Size = 2360.1MB
Do Not Check Re-Partition (Leave Unchecked)
Click Start if everything is ok
Progress Photo's
**************************************************************************************************************************************************************************************​
UPDATE!!!!!!​
Video Guide for Installing and Using Safestrap by Face_Plant
Installing Safestrap v3.72 by Face_Plant:good:
1. Download and install Busybox from the Play Store.
2. Download and install Safestrap v3.72
3. Open Safestrap and click on "install recovery"
4. Reboot and you should see a screen with a robot thing on it. Press the button on the lower left of the screen to boot into Safestrap
5. Make a backup of your stock ROM
6. Go to wipe and do a factory reset
7. Go to install and select the ROM you wish to install
8. Reboot after it's done installing
Tips:
1. I recommend saving all backups to your external SD card in case you accidentally wipe your internal storage
2. NEVER USE THE FORMAT DATA FEATURE!!! This will completely wipeout the stock slot on your phone and brick it. You will not be able to boot into Safestrap to recover (ask me how I know....)
You can use the ROM slots, but the reboot menu will not work. You have to pull the battery to shut it down. You will also get notifications that you're running out of storage. I looked at the storage info in settings after getting this notification and it said ~25 gigs were required to run the ROM as opposed to the 6GB or so that's normally required.
**************************************************************************************************************************************************************************************​ROOT FIX !!
Thanks to geohot
Install N900AATTCNC2_KERNEL.tar.md5 Kernel (3.4.0-722276) with Odin then
Towel Root will work TR.apk
Odin Install
Verify Kernel Install
Verify Root Root Checker
Now You can Install SafeStrap 3.7.2 and install any custom ROM YOU NEED BUSYBOX FOR SAFESTRAP to WORK
Do a factory reset from Safestrap
**************************************************************************************************************************************************************************************​NC2 Stock Recovery Installer
UrDroid_ATT_Stock_KitKat_N900AATTCNC2_Rooted_Odexed_VER_1.zip
UrDroid_ATT_Stock_KitKat_N900AATTCNC2_Rooted_Deodexed_Ver_1.zip
N900AATTCNC2_BOOTLOADER.tar.md5.zip
N900AATTCNC2_KERNEL.tar.md5.zip
SM-N900A_NC2_Modem.zip Thanks! Walter.White
SM-N900A_NC2_Modem_RecoveryFlashable.zip Thanks! Walter.White
**************************************************************************************************************************************************************************************​
PREVIOUS VERSION
FAST!! QUICK LINK--AndroidFileHost---------------------------------------------------------------->>>>>> NC2_Bootloader_N900AUCECMLG_VER_2.zip
**************************************************************************************************************************************************************************************​
ORIGINAL VERSION
FAST!! QUICK LINK--MediaFire---------------------------------------------------------------->>>>>> NC2_Bootloader_Odin3_Install_N900AUCECMGL.zip MD5 Number 56D40AC23546E015BEE4CDD28094D2C5
FAST!! QUICK LINK--MediaFire---------------------------------------------------------------->>>>>> sec_csc.zip Install with Stock Recovery MD5 Number B40994F984EEE97D5428E4EE96504A2F
First Copy sec_csc.zip to your external SD-Card ( you have to get one if you do not have one)
Then install with ODIN the 4 files from NC2_Bootloader_Odin3_Install_N900AUCECMGL.zip
Make Sure Your ODIN Looks Like the Picture here
After Odin reboots your phone, Immediately Hold Down POWER + MENU + VOLUME UP BUTTON and get into recovery and install sec_csc.zip
You Cannot Use this Copy of MGL KitKat to down-grade to 4.3
Once You Updated to NC2 KitKat Your stuck cannot go back, your are burn to fuse 3
The Only thing changed in the BL_N900AUCECMGL.tar
is the [aboot] file
from the OTA NC2 Update. So this is not a FULL NC2 Firmware
I used sgs2toext4 (created by drphrozen ) to convert cache.img.ext4 to cache.img.ext4.img
then used ext2explore to unpack cache.img.ext4.img
UnPacked You find the sec_csc.zip and command files in it.
command file did this with original Install :
--update_package=CACHE:recovery/sec_csc.zip
--carry_out=csc_factory
--wipe_data
unzipping sec_csc.zip we find security files and AT&T setup
Updater script in META-INF Folder
show_progress(0.100000, 0);
show_progress(0.500000, 0);
package_extract_dir("system", "/system");
But we have to do it manually with stock recovery
System Folder
Tools Used
TAR_MD5_PACKAGER
ext2explore-2.2.71.zip
sgs2toext4.zip
carl1961 said:
why would you want the leaked kitkat? and this version of kit kat might not run
Because you have the full NC2 Firmware
Click to expand...
Click to collapse
isn't the mgl firmware is downgradable to 4.3?
xuanphucn said:
isn't the mgl firmware is downgradable to 4.3?
Click to expand...
Click to collapse
Not This copy, once you update to OTA kitkat you cannot go back
Nice. Hopefully this will help out people who accidently only updated to NC2 bootloader. By the way, once the full NC2 is released you should flash that so that you can get future OTAs
Walter.White said:
Nice. Hopefully this will help out people who accidently only updated to NC2 bootloader. By the way, once the full NC2 is released you should flash that so that you can get future OTAs
Click to expand...
Click to collapse
yes, been watching for it :fingers-crossed:
It works on a bricked Note 3 AT&T after stock KitKat upgrade
Nothing else worked for me - dozens of "unbrick Note 3 AT&T" threads had the same outdated info and files, which the new bootloader of AT&T KitKat would not take. The phone was simply stuck in boot loop - neither system nor recovery would not boot. The only thing I could do was enter the Odin download mode with Volume down + Home + Power keys. Carl helped me with this file, flashed with Odin as described at the start of this thread and my phone started working at once. The system was upgraded to the leaked KitKat Android 4.4.2. My data was not lost nor the phone was reset, even after I flashed sec_csc.zip under recovery (I used adb sideload method, but it's not relevant, flashing from SD card or phone memory would probably work the same).
Thank you again, Carl, for your patience, preparing and uploading this huge file for us!!! You are really a very smart person to figure all of this out and get us out of a tight corner!
Greg
---------- Post added at 09:22 AM ---------- Previous post was at 09:03 AM ----------
carl1961 said:
yes, been watching for it :fingers-crossed:
Click to expand...
Click to collapse
I'll be rather watching for a root method for my phone, and when this is back, will see if I can get CyanogenMod working on my Note 3, or something similar (maybe OmniROM will start supporting it too?) Don't want anything from AT&T anymore, if I can avoid it! In the future probably won't buy another Samsung device.
Greg
This guide and method is really helpful when one accidentally installed NC2 bootloader before installing NC2 system.
Thank you! You are the man!
write fail
Recently I bricked my SM-900A Galaxy Note 3 by trying to install an older version of the ATT ROM, but I was unaware that I could not go back from 4.4.2. I'm trying to us this to fix my phone, but I get errors from odin. I'll link then below. Any help would be of help!
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_N900AUCUBMI9_1625098_REV03_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> AP_N900AUCUBMI9_1625098_REV03_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> CP_N900AUCUBMI9_1625098_REV03_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_N900AATTBMI9_1625098_REV03_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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
madpawn said:
Recently I bricked my SM-900A Galaxy Note 3 by trying to install an older version of the ATT ROM, but I was unaware that I could not go back from 4.4.2. I'm trying to us this to fix my phone, but I get errors from odin. I'll link then below. Any help would be of help!
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_N900AUCUBMI9_1625098_REV03_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> AP_N900AUCUBMI9_1625098_REV03_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> CP_N900AUCUBMI9_1625098_REV03_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_N900AATTBMI9_1625098_REV03_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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
N900AUCUBMI9 (MI9) is obsolete (Binary 1)
what SW REV does the download mode screen show? A2 or A3
and what if any Fused error's
Example SW REV Check Fail [aboot] Fused 3 > Binary 2
carl1961 said:
N900AUCUBMI9 (MI9) is obsolete (Binary 1)
what SW REV does the download mode screen show? A2 or A3
and what if any Fused error's
Example SW REV Check Fail [aboot] Fused 3 > Binary 2
Click to expand...
Click to collapse
RP SWREV: S2, T2, R2, A3, P2
ERRORS: SW REV CHECK FAIL : [sbl1]Fused 2 > Binary 1
madpawn said:
RP SWREV: S2, T2, R2, A3, P2
ERRORS: SW REV CHECK FAIL : [sbl1]Fused 2 > Binary 1
Click to expand...
Click to collapse
what rom was installed last? was it the official KK rom
if so try reinstalling the 2400258.zip from recovery, or sideloading with adb from stock recovery.
if all fails then you may be stuck with this MGL rom in this thread
carl1961 said:
what rom was installed last? was it the official KK rom
if so try reinstalling the 2400258.zip from recovery, or sideloading with adb from stock recovery.
if all fails then you may be stuck with this MGL rom in this thread
Click to expand...
Click to collapse
tbh, it is late and I last tried this rom and it failed. how do I go about reinstalling 2400258.zip from recovery? the phone only boots up into "firmware upgrade encountered."
---------- Post added at 12:12 AM ---------- Previous post was at 12:02 AM ----------
I'm so sorry. It seems to be working now, I was looking at wrong file...:silly: It's very late and was stressed
madpawn said:
tbh, it is late and I last tried this rom and it failed. how do I go about reinstalling 2400258.zip from recovery? the phone only boots up into "firmware upgrade encountered."
Click to expand...
Click to collapse
I'm uploaded AP_N900AUCECMGL_N900TUVUCNB4_NC2_BOOT.IMG_MGL_RECOVERY.tar.zip
try installing it with Odin, then see if you can boot into recovery and reinstall the OTA update, it will only work if your original OTA is still there and it can see in build prop
file_getprop("/system/build.prop", "ro.build.fingerprint") == "samsung/hlteuc/hlteatt:4.3/JSS15J/N900AUCUBNB4:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "samsung/hlteuc/hlteatt:4.4.2/KOT49H/N900AUCUCNC2:user/release-keys" ||
if it complains then you have to get this rom in this thread installed with odin
I was rooted, running NC2 ROM, made a newb mistake and had to use this so I'm on stock unrooted MLG. I never did the OTA to NC2 but I do have A3 status. Can I downgrade to regain root or no?
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
joe3681 said:
I was rooted, running NC2 ROM, made a newb mistake and had to use this so I'm on stock unrooted MLG. I never did the OTA to NC2 but I do have A3 status. Can I downgrade to regain root or no?
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No if your download mode shows a A3 then your stuck. what NC2 rom where you running with root? Some DEV's have used the build.prop from a NC2 OTA update so your phone showed it was NC2.
This threads OP warned that it contains the new bootloader (A3), so installing it would have installed the new bootloader.
Dynamic rom
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Can Samsung via best buy maybe flash it up to NC2 since nothing else is working. Being stuck might as well be current
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app

I have Soft-Bricked my s5, and tried almost everything. what to do?

Hello there xdadevelopers!
Today I made the brilliant descision to root my Samsung Galaxy S5 ( SM-G900F ) with a tool called KINGO ROOT.
Aware of the fact that there is a risk while rooting your phone, I procceed forward and now im left with a useless, expensive piece of electronic..
The tool i used said root was successfully installed, but my phone got stuck on the "samsung loading screen". after 40 minutes i decided to remove the battery and try again, same thing happend. I tried to use the "remove cahce/factory" setting ( or what ever its called) and that did not help. I have also tried to install the standard firmware through ODIN, but that failed over and over again at "img.ext4"..
I've also looked through this forum to find a solution, but nothing matches my problem it seems.
I really have no idea what to do anymore. :crying: I really hope someone could help me out with this problem, im sure there is others that would benefit from the same help aswell
Really should have done some research here on XDA first, but let's try and get you back up and running
You downloaded the stock ROM from sammobile .com for the G900F ?
Download and extract this PIT file
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091
Put the phone in Download Mode from a powered off state: (Volume Down & Home & Power) release when text appears, and hit Volume Up to enter download mode
Make sure samsung drivers are installed
Connect phone to PC > USB
Ensure ODIN 3.10.7 says connected and shows the COM port at the top
Add the PIT file to the PIT section
Add the ROM (Extracted to .MD5) to the AP or PDA section
Hit Start
--
All being well, it should begin the flashing process, and complete successfully, rebooting the phone back into Android
--
To root - extract and flash CF Auto Root for the G900F with ODIN in download mode again (Some G900Fs need a different method, but try this first)
http://download.chainfire.eu/397/CF-Root/CF-Auto-Root/CF-Auto-Root-klte-kltexx-smg900f.zip
Delete Kingo Root
*Detection* said:
Really should have done some research here on XDA first, but let's try and get you back up and running
You downloaded the stock ROM from sammobile .com for the G900F ?
Download and extract this PIT file
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091
Put the phone in Download Mode from a powered off state: (Volume Down & Home & Power) release when text appears, and hit Volume Up to enter download mode
Make sure samsung drivers are installed
Connect phone to PC > USB
Ensure ODIN 3.10.7 says connected and shows the COM port at the top
Add the PIT file to the PIT section
Add the ROM (Extracted to .MD5) to the AP or PDA section
Hit Start
--
All being well, it should begin the flashing process, and complete successfully, rebooting the phone back into Android
--
To root - extract and flash CF Auto Root for the G900F with ODIN in download mode again (Some G900Fs need a different method, but try this first)
http://download.chainfire.eu/397/CF-Root/CF-Auto-Root/CF-Auto-Root-klte-kltexx-smg900f.zip
Delete Kingo Root
Click to expand...
Click to collapse
Hello and thanks for answering that quickly!
I have now downloaded the stock rom from sammobile, along with the PIT file and ODIN 3.10.7 which you directed me to.
However I did not manage to get the flashing completed.
I added the .md5 file to the AP section in ODIN, and the PIT file was added to the PIT section. I left the options untouched ( Auto reboot ticked, re-partition ticked and F. reset time ticked aswell. everything else was unticked )
It did start the flashing and it kept going for a couple of minutes, but at the very end it failed at 99% completion this is the log:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> NON-HLOS.bin
<ID:0/004> rpm.mbn
<ID:0/004> sbl1.mbn
<ID:0/004> tz.mbn
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Size)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have no idea what this log means, but Im sure you do.
What did i do wrong? I tried it several times and i ended up with the same result..
I also had this problem but got out of it By downloading an earlier firmware for my phone. This is a tips guide I donei after I soft bricked due to me leaving the activation lock on! http://forum.xda-developers.com/galaxy-s5/general/read-flashing-rom-t3145703 hope this helps?
Along with the above ^^, when you put your phone in download mode, does is also say the model is the G900F ?
Some S5s have conflicting info about exactly which model they are, the section you need to trust, is download mode, double check it says G900F in download mode
*Detection* said:
Along with the above ^^, when you put your phone in download mode, does is also say the model is the G900F ?
Some S5s have conflicting info about exactly which model they are, the section you need to trust, is download mode, double check it says G900F in download mode
Click to expand...
Click to collapse
It says " Product name: SM-G900F "
deanr1977 said:
I also had this problem but got out of it By downloading an earlier firmware for my phone. This is a tips guide I donei after I soft bricked due to me leaving the activation lock on! http://forum.xda-developers.com/galaxy-s5/general/read-flashing-rom-t3145703 hope this helps?
Click to expand...
Click to collapse
Im downloading some earlier firmwares for my phone now. hope it works !
*Detection* said:
Along with the above ^^, when you put your phone in download mode, does is also say the model is the G900F ?
Some S5s have conflicting info about exactly which model they are, the section you need to trust, is download mode, double check it says G900F in download mode
Click to expand...
Click to collapse
I have now tried a 4 different firmwares, some older than the other to see if it would flash correctly.
I tried to flash only the firmware, then i tried firmware+ the PIT file you suggested in your first answer.
I also tried the PIT file all by itself, this worked , after that i tried the firmware, but that did not work..
I keep getting the same " FAIL!" over and over again when I try to flash the firmware.
At the end of the log it says " <ID:0/004> FAIL! (Size) " no matter what firmware i try to flash.
Any Ideas ?
deanr1977 said:
I also had this problem but got out of it By downloading an earlier firmware for my phone. This is a tips guide I donei after I soft bricked due to me leaving the activation lock on! http://forum.xda-developers.com/galaxy-s5/general/read-flashing-rom-t3145703 hope this helps?
Click to expand...
Click to collapse
Ive tried this several times now. but the end result is always the same : FAIL! (size)
Maybe I have done this so many times that my phone simply dont have enough space to successfully do a flash ?
Is it any way to wipe the phone clear maybe ?
babydash123 said:
I have now tried a 4 different firmwares, some older than the other to see if it would flash correctly.
I tried to flash only the firmware, then i tried firmware+ the PIT file you suggested in your first answer.
I also tried the PIT file all by itself, this worked , after that i tried the firmware, but that did not work..
I keep getting the same " FAIL!" over and over again when I try to flash the firmware.
At the end of the log it says " <ID:0/004> FAIL! (Size) " no matter what firmware i try to flash.
Any Ideas ?
Click to expand...
Click to collapse
You could try flashing a specific version of TWRP Recovery with ODIN, version TWRP 2.8.7.0
https://dl.twrp.me/klte/twrp-2.8.7.0-klte.img.tar
Flash from AP / PDA again, without extracting this time
If that flashes, try booting into recovery, Volume Up & Home & Power
If that is successful, try flashing a custom ROM from TWRP
*Detection* said:
You could try flashing a specific version of TWRP Recovery with ODIN, version TWRP 2.8.7.0
https://dl.twrp.me/klte/twrp-2.8.7.0-klte.img.tar
Flash from AP / PDA again, without extracting this time
If that flashes, try booting into recovery, Volume Up & Home & Power
If that is successful, try flashing a custom ROM from TWRP
Click to expand...
Click to collapse
TWRP 2.8.7.0 did flash without a problem. and now I did manage to boot into recovery - and now i have alot of options from Twam Win Recovery Project , and i guess im going in the right direction here hehe.
However I have no idea how to flash a custom ROM from TWRP. Do you mind walking me through the steps ?
you need to sideload a rom to your device or push it to sdcard
babydash123 said:
TWRP 2.8.7.0 did flash without a problem. and now I did manage to boot into recovery - and now i have alot of options from Twam Win Recovery Project , and i guess im going in the right direction here hehe.
However I have no idea how to flash a custom ROM from TWRP. Do you mind walking me through the steps ?
Click to expand...
Click to collapse
Great, OK well this is a popular ROM
http://forum.xda-developers.com/showthread.php?t=2732110
Instructions on how to install are on the main post
Basically copy the ROM to the MicroSD Card, and flash it using TWRP, but follow the instructions on this thread
Format / wipe everything apart from external SD from TWRP wipe menu
Go to the Install menu, and flash that ROM
Flash Gapps (Google apps) not sure if included, but not needed for flashing the ROM initially
Reboot, hopefully into the new ROM
*Detection* said:
Great, OK well this is a popular ROM
http://forum.xda-developers.com/showthread.php?t=2732110
Instructions on how to install are on the main post
Basically copy the ROM to the MicroSD Card, and flash it using TWRP, but follow the instructions on this thread
Format / wipe everything apart from external SD from TWRP wipe menu
Go to the Install menu, and flash that ROM
Flash Gapps (Google apps) not sure if included, but not needed for flashing the ROM initially
Reboot, hopefully into the new ROM
Click to expand...
Click to collapse
How am I suppose to copy the ROM to my MicroSD card ?
babydash123 said:
How am I suppose to copy the ROM to my MicroSD card ?
Click to expand...
Click to collapse
Put it in an adapter and put it in your PC, copy the ROM, put it back in your phone
{
"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"
}
If you don't have an adapter, you`ll have to buy one, they're cheap as chips - or find another device that works, you can use to copy the ROM to it with
You could try mounting the external SD (MicroSD) in TWRP, and plugging the phone into the PC and see if it is recognised, but I haven't tried that
*Detection* said:
Put it in an adapter and put it in your PC, copy the ROM, put it back in your phone
If you don't have an adapter, you`ll have to buy one, they're cheap as chips - or find another device that works, you can use to copy the ROM to it with
You could try mounting the external SD (MicroSD) in TWRP, and plugging the phone into the PC and see if it is recognised, but I haven't tried that
Click to expand...
Click to collapse
YOU are my hero, my saviour, my new idol. it actually worked!
I really cant thank you enough!
But I have some questions aswell hehe. This ROM that i downloaded installed. its not the "original" firmware that samsung provided right? what are the benefits of this VS the normal samsung one ?
babydash123 said:
YOU are my hero, my saviour, my new idol. it actually worked!
I really cant thank you enough!
But I have some questions aswell hehe. This ROM that i downloaded installed. its not the "original" firmware that samsung provided right? what are the benefits of this VS the normal samsung one ?
Click to expand...
Click to collapse
Pleased its working
No, that is not original firmware, it comes with benefits such as customisation, overclocking if the kernel allows, better speed, debloated (No crapware), more free storage, probably can install Xposed Framework for loads of tweaks and hacks and mods
Basically just about anything you want to change about your phone, you should be able to with a custom ROM, or at least request that change to the dev in that ROMs thread
But now that you have TWRP installed, you can pick and choose any custom ROM you want to try by using the same method you used to get this one installed
World is your oyster now
*Detection* said:
Pleased its working
No, that is not original firmware, it comes with benefits such as customisation, overclocking if the kernel allows, better speed, debloated (No crapware), more free storage, probably can install Xposed Framework for loads of tweaks and hacks and mods
Basically just about anything you want to change about your phone, you should be able to with a custom ROM, or at least request that change to the dev in that ROMs thread
But now that you have TWRP installed, you can pick and choose any custom ROM you want to try by using the same method you used to get this one installed
World is your oyster now
Click to expand...
Click to collapse
Ive now used it for a couple of days. and its just amazing! However I have encountered some problems with apps not working correctly. Snapchat wont load stories, and I cant watch any snapchat movies - but normal images works great when sending to my friends, which is weird. I get this errer " could not connect to server, please try again later". have tried to reinstall, clear cache etc but it seems it wont work. Ill read through the Xtrestolite thread and see if i find a solution now as Im a little more familiar with the forum
If I decide to install another ROM, is it any way that i can backup my whole phone ? so if i mess up again I can just reflash the one thats backed up, and all my apps and stuff will be just like it was ?
Yea sure, just boot back into TWRP, goto the 'Backup' section, and create a full Nandroid backup, tick all the boxes other than the caches
Make sure you have enough room on your external MicroSD (Select that as the backup location)
Once that is done, you can wipe, flash etc etc, play about with any ROM you like, and if and when you want to go back to your backup, just wipe the old one, and restore the backup from TWRP again, and your phone should be exactly the way it was when you backed it up once it finishes first boot
Very powerful recovery is TWRP
*Detection* said:
Yea sure, just boot back into TWRP, goto the 'Backup' section, and create a full Nandroid backup, tick all the boxes other than the caches
Make sure you have enough room on your external MicroSD (Select that as the backup location)
Once that is done, you can wipe, flash etc etc, play about with any ROM you like, and if and when you want to go back to your backup, just wipe the old one, and restore the backup from TWRP again, and your phone should be exactly the way it was when you backed it up once it finishes first boot
Very powerful recovery is TWRP
Click to expand...
Click to collapse
Thanks alot again!
Im experiencing some problems with some apps while using the Xtrestolite.
- Snapchat, wont load Stories at all, and wont open private video snaps, but normal pictures sent to my friends works. ( states that there was a problem connecting to the server, but when i use my Samsung S3 it works just fine )
- Dropbox - unable to preview any pictures and videoes
- larger apps/games that requires extra download ( like 3-500 MB ) wont open/load/download at all.
To me it seems that there is a problem with the phone writing temp files, such as snapschats, dropbox preview pictures.
Do you see any pattern here, maybe even some suggestions?
babydash123 said:
Thanks alot again!
Im experiencing some problems with some apps while using the Xtrestolite.
- Snapchat, wont load Stories at all, and wont open private video snaps, but normal pictures sent to my friends works. ( states that there was a problem connecting to the server, but when i use my Samsung S3 it works just fine )
- Dropbox - unable to preview any pictures and videoes
- larger apps/games that requires extra download ( like 3-500 MB ) wont open/load/download at all.
To me it seems that there is a problem with the phone writing temp files, such as snapschats, dropbox preview pictures.
Do you see any pattern here, maybe even some suggestions?
Click to expand...
Click to collapse
Did you do a FULL WIPE? Sounds like something went wrong, try SuperWipe, but make sure you have the Rom.zip on your external SD Card & not on you phone memory or you will not have nothing to flash & you will have to start mucking about. Hope this helps
Sent from my SM-G900F using Tapatalk

Categories

Resources