[AT&T Samsung Galaxy S 4 General] guut13:
FAQs

RETURNING TO STOCK / ODIN

What is ODIN and how does it work?

Odin is a 3rd party program that can restore your phone to factory settings. Post 5 has a step by step walkthrough for flashing the NB1 base image. (Those wishing to flash the MK2 base can follow the same guide, substituting in the MK2 files linked in post 1.)​

I took the NB1 OTA, can I Odin the MK2 files?

No. You can only restore your current base or newer. You cannot go backwards. Two exceptions... MLD leak and NC1 update. Those that flashed the MLD leak can Odin back to MK2. Those that took the NC1 update can Odin back to NB1.

Odin to NB1... from ANY base

Odin to MK2... from MLD, MK2, MF3, or earlier.

That said, if you are on NB1 and would like to flash 4.3 ROMs, you can follow the DOWNGRADING FROM NB1 TO MK2 guide linked in post 1.​

RECOVERY

Which recoveries can we use?

If you are on MK2, NB1, or NC1 base, then you have a locked bootloader. SAFESTRAP is the ONLY recovery you can use.​

ROMS

I am on ATT with safestrap. Which ROMs can I flash? Does that include i9505 ROMs too?

Every ROM listed in the thread have been confirmed to work with our phone. Yes... There are i9505 ROMs listed in the thread too.​

Can I flash AOSP or CM ROMs?

Sure. It's your phone. You can flash whatever you want... BUT IT WON'T WORK. Since our bootloader is locked, we can cannot change the kernel. This means only ROMs that are compatible with the stock touchwiz kernel will work.​

What's the deal with the updater-script?

Since Safestrap is designed to work around the locked bootloader, it works a little different that the other recoveries. There is one line that gives Safestrap trouble...

format("ext4", "EMMC", "/dev/block/mmcblk0p16", "0");

This is where the /system partition lives. While wiping /system is ok, formatting the entire block must delete a file or symlink that safestrap cannot restore.

Check the ROM list. There will be a note if the updater-script needs to be replaced. I have uploaded a copy for your convenience, but you are welcome to edit the script on your own. Instructions for replacing the updater-script are located in post 2.

***FAILURE TO REPLACE UPDATER-SCRIPT, WHEN NEEDED, WILL RESULT IN ENDLESS BOOTANIMATION***​

I'm stuck in the bootanimation after flashing a rom... What gives?

Did you wait long enough? Some ROM can take up to 10 min to come up on the initial boot.

Did you forget to replace the updater-script? Endless bootanimation is a symptom of formatting "/dev/block/mmcblk0p16" for safestrap users.

If you don't think the updater-script was the issue, try flashing a previously working ROM. If the other ROM works, it might have just been a bad download. Otherwise or if you know the updater-script was the cause, try restoring a previous backup. If that does not work, your only choice will be to Odin back to stock.​

ATT MODULES

Why do I need to flash the ATT Kernel Modules?

Locked bootloader means we are stuck with the stock kernel. In order for wifi to work, we need to make sure the modules in the "/system" partition match the kernel version.

If the ROM you are flashing has the same base as your kernel, you DO NOT need to flash the modules separately.​

Which version do I need to flash?

Took NI1 update --> ATT_NI1_modules.zip

Took NC1 update --> ATT_NC1_modules.zip

ODIN NB1 (rootable) --> ATT_NC1_modules.zip -- NC1 Kernel was added to Odin file in order for Towelroot to be compatible.

ODIN MK2 (running KitKat ROMs) --> ATT_MLD_modules.zip -- MLD Kernel is Odin'd as part of the Magic Tool process.

ODIN MK2 (running 4.3 ROMs) --> jflteatt-MK2-modules.zip

If you are not sure, you can run a script to check. More details can be found here...

http://xdaforums.com/showpost.php?p=51067793&postcount=4

NOTE - The NB1 kernel and NC1 kernel are so similar that either module can be substituted.​

I flashed the module zip and my wifi is still not working. Did I flash the wrong module?

In System Settings, can you flip the Wifi toggle to the ON position?

If NO, then you do not have the correct modules installed. Please run the script to verify your kernel.

If YES, then the modules are NOT the issue. Double check your wifi password or try reboot your router.​

THEMES AND MODS

Why does xxxx MOD work great on yyyy ROM or Stock, but it's not on zzzz ROM?

Each situation is different, but...

1. MOD was built using one base and your ROM is built with a different base.

2. Dev already modified that aspect of the ROM. (ie - Battery icon MOD might not work correctly if dev already baked in his own custom battery icon into his ROM.)​

OTHER STUFF

Do I need to use the Deadly Venom KitKat Magic Tool?

The Tool was created to allow MK2 users and NB1 users (who used the downgraded method in order to root) to run KitKat ROMs. Now that towelroot has been released, NB1 users can upgrade to NC1 to root and no longer need the magic tool.

MK2 users will still need to use the tool the first time they flash a KitKat ROM, as well as NB1 users wishing to flash 4.3 ROMs.​