Develop Bugs

EK02 update on stock EG30 rooted with CWM bootimage

Will I be okay? Or will I possibly brick my phone?
I only want to ask this once, so for future reference, do official updates wipe EVERYTHING on the phone, or just the modem/kernel?? If so, why will EK02 not work on EG31?

It will be fine I had the same on my fiance epic
Sent from my SPH-D710 using XDA App

Gomenkiyo said:
Will I be okay? Or will I possibly brick my phone?
I only want to ask this once, so for future reference, do official updates wipe EVERYTHING on the phone, or just the modem/kernel?? If so, why will EK02 not work on EG31?
Click to expand...
Click to collapse
The official OTA "patch" update will fail if you have CWM because the integrity check for your zImage will fail.
You can use one of the modified EK02 patch updates which bypass this problem.

sfhub said:
The official OTA "patch" update will fail if you have CWM because the integrity check for your zImage will fail.
You can use one of the modified EK02 patch updates which bypass this problem.
Click to expand...
Click to collapse
I'm on EG30 rooted with your auto root script. I haven't changed my zImage, but I have 'tinkered' in system, specifically clearing battery stats and attempting to replace the voice talk apk with google voice search apk (a rename trick I stumbled upon). I have reversed the voice talk apk, overwriting it with the original that I backed up first. Given all that, would you have any idea what my odds are that the OTA will pass validation on my device? If it won't, is my best option to use your "Option C" to apply the EK02 zImage, then flash the EK02 modem? I wanted to ask this in your thread, but I don't have the posts yet.
Thanks

wraith404 said:
I'm on EG30 rooted with your auto root script. I haven't changed my zImage, but I have 'tinkered' in system, specifically clearing battery stats and attempting to replace the voice talk apk with google voice search apk (a rename trick I stumbled upon). I have reversed the voice talk apk, overwriting it with the original that I backed up first. Given all that, would you have any idea what my odds are that the OTA will pass validation on my device? If it won't, is my best option to use your "Option C" to apply the EK02 zImage, then flash the EK02 modem? I wanted to ask this in your thread, but I don't have the posts yet.
Thanks
Click to expand...
Click to collapse
I can answer my own question in part now. I just got the update, and it installed successfully. So at very least, clearing battery data doesn't affect the verification, nor do timestamps of apks in system/bin as long as they are the right versions.

wraith404 said:
I'm on EG30 rooted with your auto root script. I haven't changed my zImage, but I have 'tinkered' in system, specifically clearing battery stats and attempting to replace the voice talk apk with google voice search apk (a rename trick I stumbled upon). I have reversed the voice talk apk, overwriting it with the original that I backed up first. Given all that, would you have any idea what my odds are that the OTA will pass validation on my device? If it won't, is my best option to use your "Option C" to apply the EK02 zImage, then flash the EK02 modem? I wanted to ask this in your thread, but I don't have the posts yet.
Click to expand...
Click to collapse
The auto root portion is fine. When you installed EG30+CWM, that basically changed your zImage. The linux "kernel" is still stock, but the initramfs was repacked with CWM, which changes the checksum on zImage. You should use Option C to reinstall EG30 and that will take care of that.
As to the file changes, if you look in the updater-script file in the OTA update.zip, you'll see all the files it is checking for validity (all the asserts). If you changed or removed any of them, it will fail.
Honestly if you started making changes to /system besides what the rooting package put in place, unless you are very organized, you might have forgotten which changes you made. If you can really reverse your changes/removals, then go for it. If you can't remember, it is probably quicker just to flash the stock EG30 kernel/ROM in ODIN. That will guarantee all the ROM files and kernel are present and the stock versions.
http://forum.xda-developers.com/showthread.php?t=1282420

sfhub said:
The auto root portion is fine. When you installed EG30+CWM, that basically changed your zImage. The linux "kernel" is still stock, but the initramfs was repacked with CWM, which changes the checksum on zImage. You should use Option C to reinstall EG30 and that will take care of that.
As to the file changes, if you look in the updater-script file in the OTA update.zip, you'll see all the files it is checking for validity (all the asserts). If you changed or removed any of them, it will fail.
Honestly if you started making changes to /system besides what the rooting package put in place, unless you are very organized, you might have forgotten which changes you made. If you can really reverse your changes/removals, then go for it. If you can't remember, it is probably quicker just to flash the stock EG30 kernel/ROM in ODIN. That will guarantee all the ROM files and kernel are present and the stock versions.
http://forum.xda-developers.com/showthread.php?t=1282420
Click to expand...
Click to collapse
I don't quite understand the relationship of the different version zImages you provide - I get CWM vs stock, just not version 'traversal'. From the sound of it, I should use that script to perhaps swap back and for between CWM/stock for whatever version I am at, but not to try to use them to swap between versions. Is that accurate? And is that because they aren't overwriting the system partition?
Thanks, this has been informative.

sfhub said:
The official OTA "patch" update will fail if you have CWM because the integrity check for your zImage will fail.
You can use one of the modified EK02 patch updates which bypass this problem.
Click to expand...
Click to collapse
Could you link me to this specific patch, and please?
Sent from my SPH-D710 using XDA App

Gomenkiyo said:
Could you link me to this specific patch, and please?
Click to expand...
Click to collapse
All the relevant EK02 links are in the Reference Section (2nd post) of the Auto Root sticky:
[ROOT][NCIQ][EG30/EG31/EK02] Auto root your existing stock ROM (w/o ODIN/ROM Flash)
Specifically look at Referece Section #A10
Sprint OTA is the official update, which requires everything to be stock EG30, Modem/Kernel/Recovery/ROM
Rooted OTA is a very slightly modified version that only requires stock EG30 Modem/ROM
---------- Post added at 11:48 PM ---------- Previous post was at 11:44 PM ----------
wraith404 said:
I don't quite understand the relationship of the different version zImages you provide - I get CWM vs stock, just not version 'traversal'. From the sound of it, I should use that script to perhaps swap back and for between CWM/stock for whatever version I am at, but not to try to use them to swap between versions. Is that accurate? And is that because they aren't overwriting the system partition?
Click to expand...
Click to collapse
In theory it is best to match your Kernel and Modem release version #s. In practice, so far, it has been ok to mix/match kernel and modem version #s.
I provide the different versions for people who want to
1) have the kernels match their modems
or
2) try different stock kernels to see if problems are addressed
The kernels have their own partition. They have no effect on the files kept in /system (ie your ROM). That's not to say they have no effect on the behavior of the ROM, just no effect on the files themselves.

sfhub said:
A
In theory it is best to match your Kernel and Modem release version #s. In practice, so far, it has been ok to mix/match kernel and modem version #s.
I provide the different versions for people who want to
1) have the kernels match their modems
or
2) try different stock kernels to see if problems are addressed
The kernels have their own partition. They have no effect on the files kept in /system (ie your ROM). That's not to say they have no effect on the behavior of the ROM, just no effect on the files themselves.
Click to expand...
Click to collapse
I think I get it now, thanks. I've also been looking at your scripts and the copy2sd files, which also shed some light. I'm used to my N1, and the way Samsung has things combined sort of threw me.

wraith404 said:
I think I get it now, thanks. I've also been looking at your scripts and the copy2sd files, which also shed some light. I'm used to my N1, and the way Samsung has things combined sort of threw me.
Click to expand...
Click to collapse
I came from another platform also. The biggest surprise for me was this phone uses the same Kernel+initramfs for both Recovery and Android. I'm used to having them separate and independently updatable.
I think it is actually an oversight or bug because they actually have a separate partition for recovery which duplicates the contents of the boot image. They just aren't using it.

I'm on EG30 rooted with your auto root script. I haven't changed my zImage, but I have 'tinkered' in system, specifically clearing battery stats and attempting to replace the voice talk apk with google voice search apk (a rename trick I stumbled upon). I have reversed the voice talk apk, overwriting it with the original that I backed up first. Given all that, would you have any idea what my odds are that the OTA will pass validation on my device? If it won't, is my best option to use your "Option C" to apply the EK02 zImage, then flash the EK02 modem? I wanted to ask this in your thread, but I don't have the posts yet.
Thanks

If you are disciplined about your changes you have a reasonable chance of having the OTA work. Any changes to config files, binaries, drivers, apps would need to be undone. If you made changes to build.prop undo those. If you removed apps, put them back.
Make sure you have EG30 (not EG30+CWM) BEFORE accepting the OTA, which it sounds like you have.
If it doesn't work, theres a post in the FAQ section of the auto root thread that explains what to do. I believe it is FAQ #E12.

[Q] Need help with rooted EK02 --> EL29 upgrade.

I cant post in the developers area, so here goes. I had to manually root my epic 4g touch using adb, now when I do my compliance check with e4gtauto-sfx.exe it says the following files are missing:
missing: /system/app/socialhub.apk
missing: /system/app/sprintzone.apk
So when I try to install the update (both: update_SPH-D710_EK02_to_EL29-rooted & ive tried: update_SPH-D710_EK02_to_EL29-rooted-cwm), they both fail to update.
The only thing I have done was root the phone, stock kernal, etc. I do have RomManager installed. I have tried to find the missing files and install the .apk's but haven't been sucessful at that.
Can anyone help me please?

davis31b said:
I cant post in the developers area, so here goes. I had to manually root my epic 4g touch using adb, now when I do my compliance check with e4gtauto-sfx.exe it says the following files are missing:
missing: /system/app/socialhub.apk
missing: /system/app/sprintzone.apk
So when I try to install the update (both: update_SPH-D710_EK02_to_EL29-rooted & ive tried: update_SPH-D710_EK02_to_EL29-rooted-cwm), they both fail to update.
The only thing I have done was root the phone, stock kernal, etc. I do have RomManager installed. I have tried to find the missing files and install the .apk's but haven't been sucessful at that.
Can anyone help me please?
Click to expand...
Click to collapse
Are you sure you didn't use titanium to remove some bloatware?
If you read the instructions for the rooted el29 ota update, it gives you a couple if options to resolve your issue. It is in the section about running ota compliance check.

If you go to calkulins or anyones for that matter,and download the full version not the debloated one, you should be able to extract it and find the 2 files in there. Ill download it and look aswell and will update post with some links if i find them.
dam your fast sfhub

verify you have root access, try pushing the update tar through odin, or the cwm zip through recovery, those missing apks should not effect you updating modem or kernal

Neomorpheos said:
verify you have root access, try pushing the update tar through odin, or the cwm zip through recovery, those missing apks should not effect you updating modem or kernal
Click to expand...
Click to collapse
I tried the cwm through recovery, it said it failed because of the two .apk's. I can try odin, but not to familiar with that process.
sfhub said:
Are you sure you didn't use titanium to remove some bloatware?
If you read the instructions for the rooted el29 ota update, it gives you a couple if options to resolve your issue. It is in the section about running ota compliance check.
Click to expand...
Click to collapse
Yes, I have titanium and got rid of the bloatware.. I did know this was going to screw me later down the road.

Mynaga said:
If you go to calkulins or anyones for that matter,and download the full version not the debloated one, you should be able to extract it and find the 2 files in there. Ill download it and look aswell and will update post with some links if i find them.
dam your fast sfhub
Click to expand...
Click to collapse
Im downloading the file now, Ill give that a shot too.. thank you!

I extracted both of the files I needed from the calkulins file into the system/app folder and I am still getting this error when installing in recovery mode:
assert failed: apply_patch_check ("/system/app/socialhub.apk", [a bunch of numbers])
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
And now the compliance check says:
SHA1FAIL: zImage/Kernel
SHA1FAIL: /system/app/socialhub.apk
SHA1FAIL: /system/app/sprintzone.apk
SHA1FAIL: /system/build.prop (I attempted to modify this file to stop OTA update message, didn't work)

zImage failing is fine if I remember correctly.
Do you have any issue with just using sfhubs OneClick EL29 the no data version so you dont have to reinstall your apps, or even better doing so and just using the full one and putting your things back on.
You dont have to do the OTA compliant install he posted, just flash the whole phone. It will be EL29 with root modem and all on stock kernel and then you can take the e4gt auto and put it to EL29 + CWM if you like.
http://forum.xda-developers.com/showthread.php?t=1433101 specifically the SPH-D710.EL29_CL852097_ROOTED_NODATA-oc-sfx.exe version if you want to keep everything youd have after the update normally.

RainMotorsports said:
zImage failing is fine if I remember correctly.
Do you have any issue with just using sfhubs OneClick EL29 the no data version so you dont have to reinstall your apps, or even better doing so and just using the full one and putting your things back on.
You dont have to do the OTA compliant install he posted, just flash the whole phone. It will be EL29 with root modem and all on stock kernel and then you can take the e4gt auto and put it to EL29 + CWM if you like.
http://forum.xda-developers.com/showthread.php?t=1433101 specifically the SPH-D710.EL29_CL852097_ROOTED_NODATA-oc-sfx.exe version if you want to keep everything youd have after the update normally.
Click to expand...
Click to collapse
Okay, I used Odin and the thread you gave me.. it installed EL29, everything works great except it erased all my apps.. oh well.. thanks again though.. my issue has been solved.

davis31b said:
Okay, I used Odin and the thread you gave me.. it installed EL29, everything works great except it erased all my apps.. oh well.. thanks again though.. my issue has been solved.
Click to expand...
Click to collapse
There are 2 versions provided, Full and NoData. Full would have reset your user data (including user apps) but NoData would have kept them (unless you kept all your apps in /system)

davis31b said:
Okay, I used Odin and the thread you gave me.. it installed EL29, everything works great except it erased all my apps.. oh well.. thanks again though.. my issue has been solved.
Click to expand...
Click to collapse
You welcome but as i was trying to say, specifically the SPH-D710.EL29_CL852097_ROOTED_NODATA-oc-sfx.exe version was the one you would have wanted to use if you wanted to keep your data. As of course sfhub has also noted. Sorry if I was not more clear about that.

[HOWTO] [ROOT] No Tripping Flash Counter - Root Injected L900VPALJC +[TWRP] + more

This is a root injected FACTORY Stock L900VPALJ1 Odin Flashable Image. You flash this in Odin just as you would the completely stock ROM from samsung. I've simply injected the su binary and SuperSu app so you now have rooted stock image.
So if you want to keep your device stock yet have the functionality of root without tripping the counter or messing up OTA updates then this would be your best bet.
You can get ODIN here
and the drivers for the SPH-L900 so ODIN can detect your phone can be found at Samsung's site. Click on the Manuals & Downloads tab at the bottom and then on Software for the latest driver.
Instructions:
First, Download Image:
New Full Rom VPALJC
Mirror 1: root66_SPR_L900VPALJC.7z
Orig Release JB 4.1.1
Mirror 1: root66_SPR_L900VPALJ1.7z
Mirror 2: root66_SPR_L900VPALJ1.7z
Second, Extract and Flash:
Extract the root66_SPR_L900VPALJ1.tar.md5 from the .7z file you downloaded.
Use Odin, put phone into download mode [with phone off, hold vol. down + home + power ], connect to computer and open Odin.
once in odin click the PDA field and select the root66_SPR_L900VPALJ1.tar.md5 you downloaded.
Leave Auto Reboot and F. Reset Time checked.
click start and
when done let phone reboot.
If you have issues flashing with Odin please ensure you are using the microusb cable that came with the phone, users have had issues using other cables.
If you just want a stock, rooted phone with no custom recovery, no plans to flash custom roms, etc. then you can stop HERE.
OTA Updates:
Stock Recovery: Once rooted with above method, if you receive a notification for an OTA update, it has been verified you can use OTA RootKeeper to retain root through the update process.
Non-Stock Recovery: If you have loaded a non-stock recovery (per below) you can simply use it to flash the OTA update flashable zip I've created.
Mirror 1: OTA Update LJ1 to LJC
Mirror 2: OTA Update LJ1 to LJC
Optional, Recovery (will trip counter):
It seems loading any custom recovery will trip the download mode flash counter. Loading a non stock recovery will also prevent you from successfully applying any OTA updates however here is a procedure for any who want a non-stock recovery:
Currently I see TWRP has support for this device so the instructions here will install that recovery.
Option 1: Download GooManager from the Play store. Once installed click the menu and select "Install OpenRecovery Script".
Option 2: Download the TWRP recovery image here. Copy it to the /sdcard of your phone.
Connect your phone to your computer and use adb
type adb shell
once in the shell run su
then
dd if=/sdcard/openrecovery-twrp-2.3.1.1-t0ltespr.img of=/dev/block/mmcblk0p9
Alternate if unfamiliar with adb commands
Grab android terminal emulator from the play store and run the same commands starting with su and then the dd command.
De-Bloater
If you've made it this far with a stock, rooted phone with CWM or TWRP and you don't want to flash a custom rom (which will do its own de-bloating) you can check out my mrRobinson Note II De-Bloater to easily get rid of bloat system apps you no longer want to see. Simply flash in CWM or TWRP like anything else and you will be presented with a menu system to choose what to remove. If you are unsure it is safe to pick Minimal and still get a decent de-bloat.​
Bonus Files
ODIN Flashable LJC Stock Recovery: SPR_recovery_L900VPALJC.tar.md5
CWM Flashable LJC Modem: modem_CWM_L900VPALJC.zip
History:
I've injected root into other stock images and those threads have a lot of valuable information which could answer some questions that may arise here. If you have time to do some reading here are a few of the informative ones:
Samsung Galaxy S3 [ATT / Bell / Telus / Rogers / Sasktel ]
Samsung Galaxy S3 [TMO / Wind / Mobilicity]
Also did sprint and vzw but there isn't much there that won't be covered above.
FAQ
Does this remove the Sprint bloatware?
A: No. It is same as stock, nothing is removed.
Does this use an unsecured boot.img
A: No. This flashes the stock boot.img in the VPALJ1 image.
If my flash counter has been tripped, and I flash this and reset the counter, will it stay at 0.
A: Yes, as long as you don't then flash a non-stock recovery.
Can I still get OTA updates?
A: Yes if you do not load a custom recovery or remove any system apps OTA updates will still come and be able to be successfully applied. If you want to retain root through the OTA process I'd recommend trying the SuperSU survival mode.

okay will this reset my phone completely? or just install root

Question can this be implemented in to custom roms the "not tripping the counter"
Sent from >> here <<

steviee7 said:
okay will this reset my phone completely? or just install root
Click to expand...
Click to collapse
Just root.

moose1313 said:
Question can this be implemented in to custom roms the "not tripping the counter"
Sent from >> here <<
Click to expand...
Click to collapse
No. Custom roms would trip.

Nice work!

mrRobinson said:
No. Custom roms would trip.
Click to expand...
Click to collapse
Thanks I only asked because I figured if it could be injected as in tricking the phone this is coming from the manufacturer you could also tweak other things and still get away with it. ..Also without an OTA released yet can you say 100% an OTA will go through with no problems if we used this Thanks again
Sent from >> here <<

mrRobinson said:
No. Custom roms would trip.
Click to expand...
Click to collapse
maybe im just a lil special at the moment, i haven't tripped the flash counter yet i learn something when i had the s3 i think that after you flash the tar for the recovery wait till its done (uncheck reboot before u flash) and then pull the battery and it doesnt trip the counter. if im wrong someone please correct me.

Just wanted to let everyone know I did this method then accepted the OTA update and I'm still rooted. Thanks for this!

Very nice! Thank you very much! This will make it easy to go back to stock AND have custom recovery!

wraptor said:
Just wanted to let everyone know I did this method then accepted the OTA update and I'm still rooted. Thanks for this!
Click to expand...
Click to collapse
Anyway u could get this in the hands of devs particularly joshbeach so he can start getting this in the jellybomb rom?
Sent from my SPH-L900 using xda app-developers app

If I odin this, does it reset everything? Seems large for just a reocvery

JBizzleFoSho said:
If I odin this, does it reset everything? Seems large for just a reocvery
Click to expand...
Click to collapse
Its not just a recovery. that's a root method that trips the counter. Maybe you responded in wrong thread.
This will reset nothing, just fyi.

yay gonna run this and flash the new update .... ive been doing dirty jellybomb flashes for quite awhile time a start with a fresh base :good:
---------- Post added at 11:14 AM ---------- Previous post was at 10:28 AM ----------
wraptor said:
Just wanted to let everyone know I did this method then accepted the OTA update and I'm still rooted. Thanks for this!
Click to expand...
Click to collapse
I did it and lost root

fatboypup said:
yay gonna run this and flash the new update .... ive been doing dirty jellybomb flashes for quite awhile time a start with a fresh base :good:
---------- Post added at 11:14 AM ---------- Previous post was at 10:28 AM ----------
I did it and lost root
Click to expand...
Click to collapse
yes you should as it overwrites all /system. use an ota rootkeeper or supersu survival mode to retain root through the ota process.

mrRobinson said:
yes you should as it overwrites all /system. use an ota rootkeeper or supersu survival mode to retain root through the ota process.
Click to expand...
Click to collapse
thanks

Yes sorry must of been delirious last night. Some of my programs that need root (like mybackuppro) still work after the OTA so I just assumed all was good. Titanium backup doesn't however confirming no root =/. Best method to get it back?

wraptor said:
Yes sorry must of been delirious last night. Some of my programs that need root (like mybackuppro) still work after the OTA so I just assumed all was good. Titanium backup doesn't however confirming no root =/. Best method to get it back?
Click to expand...
Click to collapse
i ran CF auto root then installed rootkeeper than flashed the update again ..... still tying to get custom recovery going at the moment TWRP from goo manager says it installed but its not sticking i goto recovery and its still stock

actually i looked at the patch.... I don't see where it would be removing root.... I must be missing something.

fatboypup said:
i ran CF auto root then installed rootkeeper than flashed the update again ..... still tying to get custom recovery going at the moment TWRP from goo manager says it installed but its not sticking i goto recovery and its still stock
Click to expand...
Click to collapse
if you have a root explorer go to /system/etc and delete the install-recovery.sh file you see there. Or just rename it something else like install-recovery.bak

[HOWTO][Advanced] Update from LH1 (4.0) to LK4 (4.1) using CWM OTA (Bell)

Applying the OTA update via CWM for the official JB update (LK4) is a trivial matter of modifying the updater-script to remove some of the asserts that normally trip up CWM.
Download the modified OTA here
In this modified OTA, based on the official Bell LK4 OTA, I've done the following:
1) Remove the d2can property checks that normally fail
2) Remove assertions on /system/app patches (in case you've uninstalled some system apps)
3) Remove the recovery update (so you'll keep your current CWM recovery)
4) Reset the permissions on /system/xbin/su so that you keep root after the update
Click to expand...
Click to collapse
Before flashing, you can do some additional customization of the OTA:
1) Remove any apps you don't want from /system/app
2) Remove Bell apps from /system/csc/[BMC/BWA/common]/system/app
Options for flashing:
1) Use CMW
If you've uninstalled any system apps, you may get some assertion failures on some /system/lib modules. If that happens, modify the update-script and remove those assertions if you're confident the modules are unimportant.
2) Use Mobile Odin Pro
Again, you may get some assertion errors. If you're confident that they are inconsequential files, just choose to ignore the errors.
Click to expand...
Click to collapse
Remember, if you choose to disable some assertions/patches on critical system files, then you'll end up with a half-updated OS that probably won't boot. Fair warning.
I tried this on a rooted, modified Bell LH1 using CWM 5.8.4.7 (my most trusted recovery) and it worked perfectly. Everything working 100% after the update and root still in tact. This process may work on non-Bell LH1 ROMs with some tweaking.

Is it fair to assume this would also work with TWRP ?

HiKsFiles said:
Is it fair to assume this would also work with TWRP ?
Click to expand...
Click to collapse
Worked perfectly for me.

[GUIDE][I337UCUAMF3][STOCK][NEUTERED] MF3 OTA Update - Keep Recovery and Root! [7-12]

Notice (4/16/14): I'm no longer here. I've said "goodbye" to AT&T and their locked bootloader schemes. I'm voting with my wallet - I've sold my I337 and switched to T-Mobile. My apologies to the community, but you're now on your own here.
NOTICE: These instructions are pretty much obsolete. If you'd like to run a pure stock MF3 rom based on this exact method of neutering the MF3 OTA update, then read this thread. This thread shall remain for informational purposes only.
A quick THANKS to djbliss (motochopper root exploit), TeamWin (TWRP recovery), Chainfire (SuperSU), and all of the Guinea pigs that tested some of this stuff out for me in this thread.
What is this?
This is not technically a ROM, but by the time you are done, you will be running the stock, (albeit rooted) I337UCUAMF3 ROM provided by AT&T. Unlike the original MF3 OTA patch, if you perform the steps outlined in this thread, you will not lose your custom recovery, and your bootloader (including aboot) will remain untouched.
Here's what the neutered version does:
It will flash a new boot.img, which primarily includes the MF3 Kernel.
It will flash the RPM partition, which as far as I can tell is strictly for power management. I kept it in the package because it seems harmless.
It will update many files in your /system partition, bringing you up to the latest MF3 build (the whole point).
It will flash the new MF3 modem/Baseband, along with its counterpart, the NON-HLOS partition as well. The NON-HLOS partition will cause some problems with your sound (keep reading), but I've added a patch here that will solve this problem while creating another (WiFi breaks). I've kept this included in the original neutered patch, just in case someone is able to find a very easy fix for the sound and/or WiFi.
Can I go back?
From my experience, if you do not update the bootloaders, it is fully possible to return to the I337UCUAMDB or I337UCUAMDL stock versions. I used Odin, personally, but you could simply restore nandroid backups or flash a new rom. Your modem/Baseband will stay at I337UCUAMF3, along with your RPM partition - unless you use Odin or otherwise flash older versions manually. Personally, I found ZERO side-effects of performing these steps and then restoring my MDL-based nandroid backup.
Bugs?
At this time, you will have to choose between either having sound, or having WiFi. Can't have both. This is completely related to the NON-HLOS modem that's included and expected in the MF3 build. As mentioned above, the new NON-HLOS modem will kill your sound capabilities without having the new bootloaders, etc. I have no idea why, so I've provided a "fix" for this - a flashable .zip that will restore your NON-HLOS modem back to the MDL version. If you revert to this MDL NON-HLOS modem, you will lose WiFi capabilities. If someone finds a more proper fix for this, please let everyone know. Otherwise, you're welcome to keep switching back and forth as you please. See the section in this post about flashing just the modems.
Anything else?
In addition to all this, I've provided a modified, deodexed SecSettings.apk that will not scan for SysScope and will not mark your system as "Custom". This add-on package also removes SysScope entirely from the OS. This add-on optional, and you can choose not to flash this part if you wish. This package is based on my previous mod, located here (some minor changes in Status.smali to match the new MF3 build, but otherwise the same steps were performed to create this new SecSettings.apk). Basically, if you perform all of the steps outlined in this method, you will find yourself with an "official" status, and will have the original "Galaxy S4" boot logo (not the custom/padlock logo), regardless of the root or custom recovery.
Warnings and Caveats:
I have not extensively tested the I337UCUAMF3 operating system, and I WILL NOT be providing tech support for this operating system. Take it AS-IS, and ask your questions about the OS in the Q&A forum. This thread will be only for the process of getting you to I337UCUAMF3.
NOTICE: This is only intended for the I337 - a.k.a. the AT&T Galaxy S4. I have only tried this on my 16Gb, original device. You may try it on other devices, but there is of course a very high risk of bricking your non-i337 device. You've been warned.
WARNING: I am not responsible if you brick your device. Follow the instructions very, very closely, and you will be fine.
ANOTHER WARNING: There are mixed reports about certain things being broken with the MF3 update, such as the "free unlock with hidden menu" and tethering, etc. If these are important to you, you might want to make a full backup of your EFS just in case. Most custom recoveries (including the provided TWRP recovery) can help you do this. The EFS partition does not appear to be touched during the update, but just in case the new kernel or new modem does something to it on-the-fly, it would be a good idea to have a backup.
Okay, great. So what do we do?
Click the "Click to show content" button below to begin.
Download all these prerequisites. Get the downloads started now, and just read-ahead so you are familiar with the next steps.
openrecovery-twrp-2.6.0.0-jflteatt.img
Original is found on TWRP's website.
NOTE: You can download your own recovery.img if you'd like. Continue reading instructions for more details.
MDL-noSecure.zip
MF3-Neutered.zip
UPDATE-SuperSU-v1.41.zip
Original is found on Chainfire's website.
remove-SysScope.zip
modem-fix.zip
motochopper-mod.zip
Put each and every one of these downloads onto the root of your internal SDCard (/sdcard/).
Make a full Nandroid backup of your device - include system, data, and everything.
Make a backup of everything that is on your internal SDCard - it's possible to accidently wipe it.
Wipe data. Be careful not to wipe your SDCard!
Odin to stock, unrooted MDB package. Instructions here.
Allow the device to reboot fully into the clean, stock MDB. This will clear your "Custom" status, by the way.
When returning to MDB, some apps will likely force-close when they start. This is due to data problems with these apps. You could wipe data again to remove these, but there is risk of wiping your SDcard if you do it wrong. Otherwise, just clock OK and get through them all before continuing.
Run Motocopper - Use custom version that I've provided, OR you can download the original version here http://forum.xda-developers.com/showthread.php?t=2252248
NOTE: If you use the original version, be sure not to allow it to restart your device! At the end when it prompts you to "Press Enter to reboot..." - DO NOT REBOOT.
Install a custom recovery using your ADB shell. Do NOT mistype the partition number at the end, or you can easily hard-brick your device.
Code:
# dd if=/sdcard/openrecovery-twrp-2.6.0.0-jflteatt.img of=/dev/block/mmcblk0p21
# reboot recovery
Note: You should be able to use your own recovery. You will need to install it using the method above, however. Programs like GooManager will not work at this stage.
Allow the device to reboot directly into recovery. Do not leave recovery until instructed to do so.
Flash MDL-noSecure.zip
NOTE: This is the original AT&T I337UCUAMDL update, but with the "ro.secure" check removed, and the recovery removed. Otherwise it is the same thing.
Flash MF3-Neutered.zip
Flash UPDATE-SuperSU-v1.41.zip
Flash remove-SysScope.zip
NOTE: This package will also clear your dalvik cache, just in case.
Flash modem-fix.zip
NOTE/BUG: If you skip this, you will lose all audio. If you flash this modem-fix, you will lose WiFi. Currently working on investigating this!
Wipe Data/Cache.
Reboot the device into system.
Enjoy I337UCUAMF3.
Click the "Thanks" button if this has helped you.
But I only want to flash the new modem (Baseband). Do I have to do all that crazy stuff?
Certainly not! You can flash just the modem itself, very easily. You need to be rooted, or have a custom recovery first.
The Manual Method - requires root (advanced users, but technically easier and quicker!):
Download the .zip I created of all the modems I've ever had here.
Make a nandroid backup for safekeeping. Note that a nandroid backup will not typically backup your current modem - this is just a precaution in case you mess things up and have to use Odin to restore your modems or something. Better safe than sorry!
Unzip contents to your sdcard.
Fire up your ADB shell.
Type the following very carefully. DO NOT GET THE PARTITION NUMBER WRONG or you could easily brick your device. Badly.
Code:
su
dd if=/sdcard/modem-MF3.bin of=/dev/block/mmcblk0p2
reboot
Start testing it out!
NOTE: The included NON-HLOS.bin is intended for mmcblk0p1. If you are on an MDL-based ROM and/or Kernel, don't flash this file yet, unless you're being experimental. Here's why:
If you have an MDL-based ROM/Kernel... said:
If you have an MDB NON-HLOS.bin and an MF3 modem.bin, Wi-Fi will break.
If you have an MF3 NON-HLOS.bin and an MF3 modem.bin, sound will break.
If you have an MDL NON-HLOS.bin and an MF3 modem.bin, .... Nothing seems broken. Sound and Wi-Fi are working.
Click to expand...
Click to collapse
The Automatic Method - requires custom recovery (recommended for flashaholics):
CPA Poke has offered a flashable version of the modem as an option here.
I just want the original, unaltered I337UCUAMDF patch. Where can I find it?
You can download it here. This was taken straight from \cache\fota\2400258.cfg. You can rename it as a .zip if you'd like to mess with it. Please note that this file may not be flashable on your device if you have customized your /system partition or have made other modifications to your device. This patch performs a series of integrity checks, and will not install if it fails any of them. If it fails, you should be safe, as the patch sequence aborts before making changes if it fails the checks.
BE FOREWARNED: Flashing this file directly will cause you to lose root, lose your custom recovery, and lose the ability to obtain root in the future (as far as we know). In other words, DO NOT install this unaltered, original update if you EVER want to have root again, flash custom ROMs, or have the ability to make/restore nandroid backups. You've been warned.
How can I make my own neutered version of the OTA patch?
Check out post #2 in this thread for all the details on how to customize your OTA patch file, including the warnings and potential ways you can hard brick your device.
What was changed in this patch?
If you were to flash the original patch without neutering it first, you'll be stuck with a stock MF3 build (or higher). As far as we can tell, this patch does blow some e-fuses in the device, incrementing a number such that it is impossible to return back to an older build (MDB or MDL). There is currently no known cure for this condition if this is the case, especially considering we have locked bootloaders on the I337 at this time.
For a complete list of all the files that this patch touches on your system, you can check out my previous post here.
Can I use this in my own ROM?
Certainly! In fact I encourage it. I'd like to see some cool ROMs be built using the MF3 base. It's got some nice improvements on the MDL base, so any stock-based ROMs should benefit. You have my full permission to use this complete process or any parts/pieces/packages/methods herein. I would like to see my name mentioned in your "thanks" list if you have one, but this is of course completely optional.
Where can I download a full system and kernel dump of the work you did? (ADDED 7-12-13)
You can download it right here. Apart from the SysScope mod mentioned above and injecting root, this is the full, stock image. This is NOT directly flashable, so don't even try. This will only be useful for ROM developers and advanced users. The modems and bootloaders have nothing to do with these packages, but these might be required for everything to work correctly (i.e. sound and WiFi).
This was created from my device after performing all the steps above, using these commands while the device was in recovery, from a root ADB shell:
Code:
dd if=/dev/block/mmcblk0p16 of=/sdcard/system-MF3.img
dd if=/dev/block/mmcblk0p20 of=/sdcard/boot-MF3.img
Do you have this available as a ROM I can flash? (ADDED 8-6-13)
Indeed! If you want to install this as a ROM, check out my newer thread here.
Anything I can do to help here?
If this information and tutorial helped you out, just simply hit the "THANKS" button. It's great to know the work was appreciated. Another way that you can help is to provide feedback in this thread about how it worked for you, and if there's any improvements that can be made. Lastly, if you're interested in helping financially to help recover the costs of the JTAG box I now need to recover my S4, you're certainly welcome to assist by using the donate link on the left. Keep in mind that I'm not technically a Dev here - I'm just another forum member that's providing information to other members. It's what this whole community is about.

How can I make my own neutered version of the OTA patch?
With lots of careful snipping. But first, you need a copy of the original OTA patch. You can download this from my post above, or you can download one yourself straight from AT&T.
To download your own copy, the process is not terribly complicated - just risky. Here's the steps I performed to obtain the original update file from AT&T:
Make sure you have root before continuing. If you screw this up and allow the update to install, you're pretty much SOL.
If you are running the stock MDL rom, you can simply launch the updater in Settings -> More... -> About device -> Software update and let it download. Just don't reboot your phone until you've then frozen the AT&T update applications (all 3 of them) from performing the update. Keep in mind that your device will eventually reboot on its own, thanks to AT&T and their way of forcing updates.
Pull the update file from /cache/fota/2400258.cfg, and put it somewhere on your computer that you can work with it. It's just a .zip file in disguise, so you can simply rename it appropriately.
Delete the original .cfg from the device.
As mentioned, freeze or disable the updater applications.
You now have your own copy of the OTA update.
Great - you've got the file. Time to grab the scissors and perhaps something to steady the hands and numb the pain. A keyboard works too in this case. Here's what to do:
Save a backup copy of your update file. One copy for safekeeping (in case you want to start over) and another to work on. Do it now.
Open the update file using basically any .zip editor. I used 7zip because it performed quickly, whilst Win7's zip capabilities were VERY SLOW dealing with this file.
[*]From the root directory of the file, delete:
aboot.mbn
sbl2.mbn
sbl3.mbn
tz.mbn
The entire "recovery" directory.
Within the file, browse to META-INF\com\google\android and pull a copy of the updater-script. This file does all the magic.
Edit the updater-script using a text editor, preferably something like Notepad++ (great program! I recommend it). Make the following changes:
Remove the following line:
Code:
assert(getprop("ro.secure")=="1");
Edit the following line from:
Code:
"/system/tts/lang_SVOX/svox-lh0pt2en-US22.pil",
to
Code:
"/system/tts/lang_SVOX/svox-lh0pt2en-US22.pil");
Remove the following line (it's right after the last one you edited):
Code:
"/system/recovery.img");
Remove the following lines:
Code:
delete("/system/recovery-from-boot.p",
"/system/etc/install-recovery.sh");
and remove:
Code:
ui_print("Unpacking new recovery...");
package_extract_dir("recovery", "/system");
and remove:
Code:
set_perm(0, 0, 0544, "/system/etc/install-recovery.sh");
and remove:
Code:
ui_print("Update sbl2 ota");
assert(write_backup_fota("/dev/block/mmcblk0p4", "/dev/block/mmcblk0p22"));
assert(package_extract_file("sbl2.mbn", "/dev/block/mmcblk0p4"));
assert(erase_backup_fota("/dev/block/mmcblk0p22"));
ui_print("Package sbl2 Done.");
ui_print("Update sbl3 ota");
assert(write_backup_fota("/dev/block/mmcblk0p5", "/dev/block/mmcblk0p22"));
assert(package_extract_file("sbl3.mbn", "/dev/block/mmcblk0p5"));
assert(erase_backup_fota("/dev/block/mmcblk0p22"));
ui_print("Package sbl3 Done.");
ui_print("Update aboot ota");
assert(write_backup_fota("/dev/block/mmcblk0p6", "/dev/block/mmcblk0p22"));
assert(package_extract_file("aboot.mbn", "/dev/block/mmcblk0p6"));
assert(erase_backup_fota("/dev/block/mmcblk0p22"));
ui_print("Package aboot Done.");
and remove:
Code:
ui_print("Update tz ota");
assert(write_backup_fota("/dev/block/mmcblk0p8", "/dev/block/mmcblk0p22"));
assert(package_extract_file("tz.mbn", "/dev/block/mmcblk0p8"));
assert(erase_backup_fota("/dev/block/mmcblk0p22"));
ui_print("Package tz Done.");
Save it, and put the modified updater-script back inside the update file where you found it, replacing the old one.
Upload it to your SDCard and flash. See all the warnings here in this post and in the original post about what to do with this thing.
NOTES and WARNINGS:
A careful reader will be able to easily tell what each part of the updater-script does, and you can choose whether or not to keep it, modify it, or delete it.
Keep in mind that the update will fail if it does not pass all of those integrity checks. You can technically remove all of the integrity checks, and the update will still process, patching files left-and-right. However, depending on how heavily you have modified your system, you will probably run into extreme problems (soft brick most likely).
CRITICAL WARNING ABOUT BOOTLOADERS: At this time, do NOT allow the update package to only partially update your bootloader! Failure to update the entire bootloader will result in a hard brick. For example, if you were to include the parts that update sbl2 and sbl3, but not include tz and aboot... your chain of trust will be violated, and the device will refuse to boot normally (a.k.a. QDL Mode or Emergency Boot). The only theoretically known way out of this is JTAG. You don't want to go there. So, simply put: regarding bootloaders, it's all or nothing. The bootloader updates included in this package are: sbl2.mbn sbl3.mbn aboot.mbn tz.mbn. It's like any good D&D campaign - if you separate these party members, the campaign is toast.
REMINDER: At this time, it appears that flashing the new bootloader will trip an e-fuse. This is a hardware device that is only capable of incrementing a number. If the number on the e-fuse is higher than the bootloader you are trying to flash (with Odin, for example), the device will refuse to take the update. In other words, if you flash the MF3 bootloader, there is no known way to return to the MDB or MDL bootloaders at this time.

Nice...as usual. Just to help make it clear, are you allowing other developers to use this to put into their ROMs (with credit given of course)?
Again, thanks for your work.

scott14719 said:
Nice...as usual. Just to help make it clear, are you allowing other developers to use this to put into their ROMs (with credit given of course)?
Again, thanks for your work.
Click to expand...
Click to collapse
Certainly! I've updated the OP with, "You may also use any of the packages created or modified here for inclusion in your ROMs." at the end of it to clarify. Thanks for bringing it up. :good:

thanks man!!.. you put alot of work into this!!! very nice job:good:

Aou said:
Certainly! I've updated the OP with, "You may also use any of the packages created or modified here for inclusion in your ROMs." at the end of it to clarify. Thanks for bringing it up. :good:
Click to expand...
Click to collapse
Just an fyi... Dropbox ha temporally disabled the down load. At least that's the error in getting.
Sent from my SAMSUNG-SGH-I337 using xda premium

spdwiz18 said:
Just an fyi... Dropbox ha temporally disabled the down load. At least that's the error in getting.
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
Figures. >_<
Looks like I'll need a better place to upload these... I'll upload them elsewhere and update the OP as soon as I can find a good place to put them.
Thanks for notifying me!!

Aou said:
Figures. >_<
Looks like I'll need a better place to upload these... I'll upload them elsewhere and update the OP as soon as I can find a good place to put them.
Thanks for notifying me!!
Click to expand...
Click to collapse
You dida great job, but think there may be an easier way to update if you are interested.
Food for thought.
This will only work with yours since you are updated.
dd if system and boot to the sdcard as system.img and boot.img.
Use kitchen to extract system and build update zip from that. This would create less flashes as it would have root and everything else built in.
Just a thought. If it sound likeva c goid idea. Great! If not its ok.
Again. Great job.
Sent from my SAMSUNG-SGH-I337 using xda premium

Just wondering what's up with sound. So weird modem would mess with that
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

spdwiz18 said:
You dida great job, but think there may be an easier way to update if you are interested.
Food for thought.
This will only work with yours since you are updated.
dd if system and boot to the sdcard as system.img and boot.img.
Use kitchen to extract system and build update zip from that. This would create less flashes as it would have root and everything else built in.
Just a thought. If it sound likeva c goid idea. Great! If not its ok.
Again. Great job.
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
I haven't actually build a ROM yet, but this might be a good time to try!
jetlitheone said:
Just wondering what's up with sound. So weird modem would mess with that
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
iknorite? Perhaps a more experienced Dev could shed some light on what's going on with this. If a solution is found, I would love to incorporate it into this project.
Also, an update: I added instructions in post #2 on how you can obtain and neuter your own OTA update file. I have no intentions of hiding any of my work.

Aou said:
I haven't actually build a ROM yet, but this might be a good time to try!
iknorite? Perhaps a more experienced Dev could shed some light on what's going on with this. If a solution is found, I would love to incorporate it into this project.
Also, an update: I added instructions in post #2 on how you can obtain and neuter your own OTA update file. I have no intentions of hiding any of my work.
Click to expand...
Click to collapse
You've tried different kernels and such
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

Aou said:
I haven't actually build a ROM yet, but this might be a good time to try.
If you want or need help in this. Just ask.
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse

I already sort of updated to the latest version I337UCUAMF3. Is there any hope left for me? Can I roll back to the previous versions and get my root back or should I just sit and wait and hope someone releases a root for the newer version?

Mrkqql143 said:
I already sort of updated to the latest version I337UCUAMF3. Is there any hope left for me? Can I roll back to the previous versions and get my root back or should I just sit and wait and hope someone releases a root for the newer version?
Click to expand...
Click to collapse
You can probably do the Samsung update utility through kies
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

jetlitheone said:
You can probably do the Samsung update utility through kies
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
I am saying I already updated. Is there a way for me to go back using the utility?

Mrkqql143 said:
I am saying I already updated. Is there a way for me to go back using the utility?
Click to expand...
Click to collapse
Yes it'll update you backwards since the new update isn't up on their site haha do an emergency firmware update or whatever
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

Mrkqql143 said:
I am saying I already updated. Is there a way for me to go back using the utility?
Click to expand...
Click to collapse
Last I read odin was a no go if you take the update so you're stuck until someone figures out how to get around it.
EDIT: Let me know if the above works if you try.

If I am rooted with supersu 1.41 (custom status removed) and cwm recovery - can I just flash the neutered ota.zip and get the modem update that came with the ota zip?
Thanks for the clarification.

Noobla_Khan said:
Last I read odin was a no go if you take the update so you're stuck until someone figures out how to get around it.
EDIT: Let me know if the above works if you try.
Click to expand...
Click to collapse
Nope. Odin is a NO go!

Mrkqql143 said:
Nope. Odin is a NO go!
Click to expand...
Click to collapse
Yup knew odin was a no go, I was wondering if you could emergency back with Kies due to them not having the update on the web yet as stated above.