yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 General] MJHawaii:
Got it here's how.Go into SuperSU do a full unroot and reboot then after you reboot boot back into boot loader and relock boot loader "fastboot oem lock" then reboot. Then reboot into stock recovery and apply update.

PROFIT! just did mine

The downside you will have to re unlock (wipe data) and reroot if you want root
[Galaxy S 4 General] jetlitheone:
I'm gonna create a flashable zip I'm pretty positive I can do this but give me some time guys.
[Galaxy S 4 General] illogic6:
Thanks. Still seems impossible to install on mine.
[Galaxy S 4 General] jetlitheone:
It isn't possible I can see in the updater script its calling for ceraint parameters
[Galaxy S 4 General] illogic6:
Yeah, I was looking at that too. Looks like it's failing on checking my modem image. Wonder if there's a way to revert that to stock.

Betting I picked up a different version from one of the 4.3 leaks.
[Galaxy S 4 General] MJHawaii:
Guys just follow my post in #12 and you can update
[Galaxy S 4 General] jetlitheone:
Think you can remove the line that checks.
[Galaxy S 4 General] illogic6:
Still failing after those steps unfortunately.
[Galaxy S 4 General] MJHawaii:
Use my Odin to stock rooted .tar and redue my steps

http://xdaforums.com/showthread.php?t=2388504

I would also suggest re downloading the file make sure its on your ext SD card and do Not rename it
[Galaxy S 4 General] iB4STiD:
im thinking something is wrong with the ota .. thats odd in itself
[Galaxy S 4 General] SamuriHL:
And how the hell am I going to fix this? :(
[Galaxy S 4 General] qnet:
Thank you. I've been quietly following this thread as well as some others. I'm in the same boat as illogic6 and ThugEsquire . I flashed the leak with the MG8 modem and cannot go back to the MFD.
[Galaxy S 4 General] iB4STiD:
I would downgrade .. to 4.2.2 if u can ... i would be pretty angry paying that much for a phone and dealing with that.. theres an odin package around here 4.2.2
[Galaxy S 4 General] mrvirginia:
this is exactly what i did...

i created a 4.2.2 odexed GPE ROM and then commented out a build.prop and insecure check, as well as removed patching for modems/recovery or anything that was unrelated to /system. i then repacked the OTA zip and flashed...

however, after pulling a system dump this way and attempting to create a ROM, it booted but there was no sound so i had a permission issues somewhere. so, i'm back on my own OTA updater which is fully working with sound... sans the security issue. IF i fix the security issue, then i'll fix the sound issue because it's just a permission problem
[Galaxy S 4 General] wilbarger:
I have the OTA and have had no fc's at all. Uninstalled 2 apps with no problems at all.
[Galaxy S 4 General] SamuriHL:
I have an older nandroid of 4.2.2 and I could try downgrading to that. I just tried reapplying the update and it gave me an error 7 but rebooted before I could fully read it. I thought with a GPE we weren't supposed to have these kinds of problems.....
[Galaxy S 4 General] AJ Newkirk:
Can you open Settings->Security completely tho?
[Galaxy S 4 General] Sammy4Life:
What and Adventure.

Ok, I realize that I should be considered a noob here for being my first post, however, I've done quite a bit of this already. Here are my notes and thoughts on what I've done and where am and maybe someone can guide me down the right path.

First of all after the initial bootloader unlock, I did the chainfire CF-Autoroot. Then I proceeded to back up my stuff using dd.... especially the recovery.

dd if=/dev/block/mmcblk0p21 of=/sdcard/recovery_stock.img bs=4096 and also the system img, boot img following instructions in another thread. Then used goo manager to install custom recovery TWRP 2.6.0.0

Now, if you look at this file closely, the recovery_stock.img it is approximately 10MB.

I like may others did not get the OTA updates, so I decided to roll back step by step. Triangle Away, Chainfire Unroot, relock bootloader. This didn't do much of anything so I followed the instructions in http://xdaforums.com/showthread.php?t=2360346 however if you look closely, the recovery provided in that thread is a bit smaller 9.5MB... not sure why.

Also flashing back my original recovery did not work. Stuck in loading recovery boot loop. I'm able to get out of all of this now using Heimdall method provided in the other thread. Stock recovery cannot see partitions.

Not sure what to do at this point. Boot loader is unlocked, TWRP 2.6.0.0 rooted, using Heimdall. That is basically where I sit today, be glad to do some more testing and play along if someone would like for me flash another recovery or do some testing. I've been pretty fortunate to be able to resurrect this phone many many times already :)

As it stands now:

True GT-I9505G

Baseband: I9505GUEUAMFD

Build Number: JDQ39.I9505GUEUAMFD

Bootloader Unlocked, TWRP 2.6.0.0, Rooted only.

Beginning to not like the folks who have their phone listed as GT-I9505G, very deceiving who to believe.
[Galaxy S 4 General] iB4STiD:
interesting.. keep us updated

try that .. since ota didnt flashed baseband it should work
[Galaxy S 4 General] mrvirginia:
more info

http://xdaforums.com/showpost.php?p=44311297&postcount=842
[Galaxy S 4 General] SamuriHL:
I've restored my 4.2.2 nandroid. I'm just letting all my apps update and I'll redo some of the changes I had made since I took the nandroid. Going to update the nandroid, restore stock recovery, and allow the phone to take the OTA instead of sideloading it from the ext sdcard. We'll see if this makes any difference.
[Galaxy S 4 General] iB4STiD:
thanks man, and nice job!! :good:
[Galaxy S 4 General] wilbarger:
Yes, I just opened security and modified the device name. No issue at all.
[Galaxy S 4 General] SamuriHL:
Let's pray this works for me....ugh.
[Galaxy S 4 General] mrvirginia:
are you rooted? can you please pull SecSettingsProvider.apk and Settings.apk?

would greatly benefit the community
[Galaxy S 4 General] wilbarger:
No, I am not rooted yet. Still running the OTA as it came. I did try to install TWRP, but it did not take. Give me some instructions and I will be happy to pull wht you need.
[Galaxy S 4 General] mrvirginia:
if you're on a computer, this is by far the easiest method to get a custom recovery installed

http://xdaforums.com/showthread.php?t=2260031
[Galaxy S 4 General] wilbarger:
To pull the 2 .apk files, do I use adb? If so, what is the path to use?
[Galaxy S 4 General] mrvirginia:
adb pull /system/app/SecSettingsProvider.apk C:\

adb pull /system/app/Settings.apk C:\

type it just like that and both will be dumped on your C drive
[Galaxy S 4 General] iB4STiD:
adb pull /system/app/SecSettingsProvider.apk SecSettingsProvider.apk

adb pull /system/app/Settings.apk Settings.apk
[Galaxy S 4 General] mrvirginia:
[MENTION=4782861]wilbarger[/MENTION] we need the odex variants of both of those as well. so, type the same two lines except change .apk to .odex

adb pull /system/app/SecSettingsProvider.odex C:\

adb pull /system/app/Settings.odex C:\
[Galaxy S 4 General] SamuriHL:
Moment of truth....Android is upgrading....

Did it update the baseband this time? Let's find out, shall we?

Indeed it did. I'm now on MH1. Well that was fun.
[Galaxy S 4 General] mrvirginia:
if you use this method, they will be pulled to wherever you have adb installed...

something like drive:\android-sdk-windows\platform-tools
[Galaxy S 4 General] iB4STiD:
ya.. i have adb setup a little different.. i know that anything i pull goes to /android/tools .. and forgot about the odex files good call there :good:
[Galaxy S 4 General] MJHawaii:
I have a thread here in general on how to root this you have to update the binaries by installing the SuperSU zip with twrp

---------- Post added at 06:56 AM ---------- Previous post was at 06:53 AM ----------

Just an update on the MH1 Full Odin package I am having trouble getting the a.boot.mbn, sbl, and modems to flash I am working on it so if your waiting on a full restore Odin package this explains the delay. I can only get the system, recovery, and boot to flash so far???
[Galaxy S 4 General] SamuriHL:
I was able to root with CF Auto Root. And I've extracted a new recovery img now that I have a fixed 4.3 install. And it's different than the one I did last night and the one that was posted earlier. Beats me on that. But it seems to work. I'm about to flash TWRP and nandroid this thing. Good times.
[Galaxy S 4 General] DerekChas:
Here is a TWRP Nandroid of stock 4.3 of my I9505G that is running with no fc's.

https://mega.co.nz/#!UVFgCIyQ!o5h6mDAKpBEM1SecP-cuGeYHL0jVSPJt6dsHjnzcSWg

-Derek
[Galaxy S 4 General] iB4STiD:
thanks Derek ... brb :good:
[Galaxy S 4 General] mrvirginia:
yeah ditto lol
[Galaxy S 4 General] iB4STiD:
:p

edit

still fc... sigh
[Galaxy S 4 General] SamuriHL:
Ok, I can confirm 100% that the crashing/reboot issue is caused by the baseband. I made a nandroid before I reverted to 4.2.2 and updated again with the OTA. Now that the baseband was updated, I restored the nandroid that was crashing and am now able to uninstall apps with no problems. So the fix is going to have to be to get the baseband updated....however that has to happen. Has someone extracted the baseband from the new OTA and made an ODIN flashable package yet? Just curious if people can go forward from the leaked baseband that so many are on. I know going back seems to be a problem. But forward might be possible?
[Galaxy S 4 General] mrvirginia:
yep, not sure what the issue is. but i checked file size and then md5'd and they're the exact same

edit: maybe what [MENTION=2812087]SamuriHL[/MENTION] is saying is the problem... i can make an Odin baseband updater but i would need to be on Linux to do it and that's not possible for at least another 6 hours
[Galaxy S 4 General] faux123:
Hi,

I am subscribed to this thread... I have a fully working full custom kernel ready.. but still waiting for a solution to the security issues. I have a TMO variant, loaded the latest dumps from here, but just like many users here, having issues with security.

I've run keymaster_test under /system/bin and I get a segmentation fault...

Can those with 100% ROMs run the keymaster_test and post the outputs here?

use terminal:

su

cd /system/bin/

keymaster_test

Still waiting for a solution to this for non-real-GE folks like myself.
[Galaxy S 4 General] MaKTaiL:
So Samsung finally found a way to keep i9505 out of the custom GE roms.

F*ck you Sammy! :crying:
[Galaxy S 4 General] iB4STiD:
hmm.. does anyone have the baseband not in a patch format?
[Galaxy S 4 General] mrvirginia:
i was looking into the keymaster issue as well. would like to know if this is the problem...

yeah this is going to be tough to get...
[Galaxy S 4 General] SamuriHL:
Can it be done in cygwin? That's what I've been using to make my recovery ODIN flashable files. I just don't know what partitions to pull and what order they belong in the tar. If you give me instructions I can probably do it.

---------- Post added at 01:38 PM ---------- Previous post was at 01:34 PM ----------

No, and that's the problem. I suspect it can be extracted using DD. It's just that I don't know the right partitions we need and what order to add them to the tar. If I knew that, I could probably make one that some brave soul could try. I'm new to the Samsung world so I'm still getting my feet wet. As I said, I've successfully made ODIN flashable recovery packages, but, that's the extent of how far I've gone with it.
[Galaxy S 4 General] iB4STiD:
brb
[Galaxy S 4 General] mrvirginia:
probably but i'm on a work machine so i can't install things like that. we need to figure out the keymaster_test first before going through the trouble of getting modems

can someone please do what faux asked?
[Galaxy S 4 General] iB4STiD:
I believe these are the paths to baseband

lrwxrwxrwx root root 2013-06-28 18:24 modemst1 -> /dev/block/mmcblk0p11

lrwxrwxrwx root root 2013-06-28 18:24 modemst2 -> /dev/block/mmcblk0p12
[Galaxy S 4 General] illogic6:
Should we make a separate thread for tackling this baseband issue with the OTA? I've tried everything I can think of and, short of obtaining some kind of Samsung-signed Odin firmware package for either of the official firmwares/basebands, I'm totally out of ideas. :crying:

At this point, I have a half a mind to sell this phone while the gettin' is good and either get a regular I9505 or a HTC One.
[Galaxy S 4 General] iB4STiD:
sep thread sounds good

mount points

shell@android:/ $ ls -al /dev/block/platform/msm_sdcc.1/by-name
ls -al /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root root 2013-06-28 18:24 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2013-06-28 18:24 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-06-28 18:24 backup -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2013-06-28 18:24 boot -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2013-06-28 18:24 cache -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2013-06-28 18:24 carrier -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2013-06-28 18:24 efs -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2013-06-28 18:24 fota -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2013-06-28 18:24 fsg -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2013-06-28 18:24 hidden -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2013-06-28 18:24 m9kefs1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2013-06-28 18:24 m9kefs2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2013-06-28 18:24 m9kefs3 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2013-06-28 18:24 mdm -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-06-28 18:24 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2013-06-28 18:24 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2013-06-28 18:24 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2013-06-28 18:24 param -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2013-06-28 18:24 persdata -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2013-06-28 18:24 persist -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2013-06-28 18:24 recovery -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2013-06-28 18:24 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2013-06-28 18:24 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-06-28 18:24 sbl2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-06-28 18:24 sbl3 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-06-28 18:24 ssd -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2013-06-28 18:24 system -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2013-06-28 18:24 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2013-06-28 18:24 userdata -> /dev/block/mmcblk0p29

Number Start End Size File system Name Flags
1 4194kB 17.3MB 13.1MB apnhlos
2 17.3MB 71.3MB 54.0MB mdm
3 71.3MB 71.4MB 131kB sbl1
4 71.4MB 71.7MB 262kB sbl2
5 71.7MB 72.2MB 524kB sbl3
6 72.2MB 74.3MB 2097kB aboot
7 74.3MB 74.8MB 524kB rpm
8 74.8MB 75.4MB 524kB tz
9 75.4MB 92.7MB 17.3MB pad
10 92.7MB 107MB 14.3MB ext4 efs
11 107MB 110MB 3146kB modemst1
12 110MB 113MB 3146kB modemst2
13 113MB 114MB 799kB m9kefs1
14 114MB 115MB 799kB m9kefs2
15 115MB 116MB 799kB m9kefs3
16 116MB 3010MB 2894MB ext4 system
17 3010MB 3018MB 8389kB persist
18 3018MB 5189MB 2171MB ext4 cache
19 5189MB 5195MB 6291kB param
20 5195MB 5205MB 10.5MB boot
21 5205MB 5216MB 10.5MB recovery
22 5216MB 5226MB 10.5MB fota
23 5226MB 5233MB 6291kB backup
24 5233MB 5236MB 3146kB fsg
25 5236MB 5236MB 8192B ssd
26 5236MB 5245MB 9437kB ext4 persdata
27 5245MB 5770MB 524MB ext4 hidden
28 5770MB 5791MB 21.0MB carrier
29 5791MB 15.8GB 9961MB ext4 userdata
[Galaxy S 4 General] faux123:
Hi,

Thanks for the output.

Can you run the same test again, but instead this time grab me the dmesg log instead.

here's the sequence using terminal:

su

cd system/bin

keymaster_test

dmesg > /sdcard/dmesg.txt

then post the /sdcard/dmesg.txt either here or to pastebin.com

TIA!
[Galaxy S 4 General] AJ Newkirk:
2 other things that are not in all of these system dumps are:

assert(apply_patch_check("EMMC:/dev/block/platform/msm_sdcc.1/by-name/apnhlos:9018112:de2de0523a88ce0781eb125b563ac0bb176bcb7e:9181952:c15e52d975b0b46478798a436c3feca3d4b755d7", "c15e52d975b0b46478798a436c3feca3d4b755d7", "de2de0523a88ce0781eb125b563ac0bb176bcb7e"));

assert(apply_patch_check("EMMC:/dev/block/platform/msm_sdcc.1/by-name/mdm:51976960:14ce52dce17261030fa5807a4d6d02b2ad061370:51944192:a43358aa04912437a98f3348a63d9bc88f3d7af4", "a43358aa04912437a98f3348a63d9bc88f3d7af4", "14ce52dce17261030fa5807a4d6d02b2ad061370"));

Also, please note that SecSettingsProvider.apk & SecSettingsProvider.odex both get patched and are apparently verified as part of the patching process.

assert(apply_patch_check("/system/app/SecSettingsProvider.apk", "b1f70f1973ccbde8a0bbaff019a999fdd72551f1", "041972a8fb59488b32eee903c17ac965908ee206"));
set_progress(0.350722);
assert(apply_patch_check("/system/app/SecSettingsProvider.odex", "4134c507bb6e32856204a3d87e1637157b804fd5", "fd77dcd5b12a63cd03b3cd5d2aead60ab74ddb6a"));
set_progress(0.350949);
[Galaxy S 4 General] mrvirginia:
this is correct. which is why my spoofed patcher worked just like a typical OTA, except removing the flashing of recovery and other things that weren't needed/would be bad to flash on a non-official GPE phone

mdm and apnhlos are both modems...
[Galaxy S 4 General] SamuriHL:
I pm'd you the requested info. Hope it helps!!
[Galaxy S 4 General] faux123:
Thanks. Got it..
[Galaxy S 4 General] SamuriHL:
Man who would have thought that a GPE could cause so many issues! :) I'm just glad I am back up on 4.3 with the proper baseband. What a nightmare that was. I sincerely hope everyone is able to get their issues worked out and get up on this update. It's been so smooth so far.
[Galaxy S 4 General] illogic6:
Ask and you shall receive. http://xdaforums.com/showthread.php?p=44316456
[Galaxy S 4 General] MJHawaii:
I put this guide up awhile ago for Rooting MH1 4.3

http://xdaforums.com/showthread.php?t=2391723
[Galaxy S 4 General] faux123:
Nasty kernel hack ;) but it works!

Not sure if I should reveal it.. Afraid of Samsuck patching this out in the future... Open for discussions...
[Galaxy S 4 General] yeahmann:
If faux is on the case, a fix isn't far off.
[Galaxy S 4 General] mrvirginia:
a pm would be appreciated. so the problem is kernel related?
[Galaxy S 4 General] AJ Newkirk:
So you have the choice to use it until the time comes if/when Samsung patches, or to not use it at all.
[Galaxy S 4 General] faux123:
no, the issue is in the TrustZone app itself.. (Keymaster app is an ARM TrustZone secure app). The app will return an unknown response when talking to a non-MH1 baseband. Then the error is propagated all the way back to the userspace (in this case the QSEECOM HAL). Once the HAL failed, then the application on using the HAL also failed (in this case, Settings app).

What I've done is to stop this propagation of error back to userspace from the kernel side so the userspace can continue without crashing ;)
[Galaxy S 4 General] iB4STiD:
^ the man is good :good:
[Galaxy S 4 General] mrvirginia:
they're getting tricky, dude. good job! and thank you for the explanation.
[Galaxy S 4 General] tublah:
I flashed your recovery - it would not boot into recovery - it just skipped it and booted up normally. I'd say this is a no-go.
[Galaxy S 4 General] :
you can share it with some of us in PM's ill sign a contract or something that i won't leak it :good:
[Galaxy S 4 General] faux123:
Here's a stock boot.img + hack for those of you who wants to try..

it's completely unsupported.

http://faux.androidro.ms/irc/beta/jfltetmo-stock-GE-JB43-patched.zip

Have fun.
[Galaxy S 4 General] mastergrillo:
So does it fix the uninstall issue also?

and thank you for time and knowledge

Sent from my GT-I9505G
[Galaxy S 4 General] Cozmo85:
Do we flash this in custom recovery over a GE 4.3 with the uninstall/systemfc issue?
[Galaxy S 4 General] :
i flashed it over the 4.3 rom without wiping anything and still cant get into security settings or uninstall apps
[Galaxy S 4 General] mrvirginia:
ditto. wiped cache/dalvik. no go here either
[Galaxy S 4 General] iB4STiD:
yup same here
[Galaxy S 4 General] faux123:
many of the dumps are broken..

you will need to fix the symlink as well...

make sure you link all 5 keymaster.xxx files from /system/vendor/firmware to /etc

If you don't have those 5 keymaster files, there's a dump here that has them.. extract and put in /system/vendor/firmware and then symlink them to /etc
[Galaxy S 4 General] jamal2367:
in my rom i have this in vendor/firmware ....

see this
[Galaxy S 4 General] iB4STiD:
i have 6 .. one of those days :eek:
[Galaxy S 4 General] Sammy4Life:
Ok, so I'm on TWRP 2.6.0.0, Rooted, unlocked bootloader and the system update just came in ready to be installed. Any recommendations?

Device: jgedlte

Baseband: I9505GUEUAMFD

Build Number: JDQ39.I9505GUEUAMFD

Bootloader Unlocked, TWRP 2.6.0.0, Rooted only.
[Galaxy S 4 General] :
i have the same 6 files in my rom
[Galaxy S 4 General] iB4STiD:
pray? :p
[Galaxy S 4 General] :
Segmentation fault? Isn't that usually hardware related

---------- Post added at 03:44 PM ---------- Previous post was at 03:43 PM ----------

Getting in on this guy's I'll help out in a moment
[Galaxy S 4 General] tublah:
YES! Put the stock 4.2.2 recovery back on, then after you update and re-root by fastboot boot twrp.img and rooting by flashing SuperSU 5.12.zip PLEASE grab a copy of the stock recovery. PM me if you need any help with any of this.
[Galaxy S 4 General] Sammy4Life:
Will do shortly, on a conference call at the moment.... So you and I are on the same page, I will be using Heimdall method from http://xdaforums.com/showthread.php?t=2360346 thread, I will be using the that recovery (which has not worked for me in the past in regards to updating via just the zip.) so if you have any other method you think I should get back to "normal" then let me know.

My drivers are setup as "Android Composite ADB Device"
[Galaxy S 4 General] tublah:
Sounds perfect. Heimdall the stock recovery for 4.2.2 -- The key here is once you're at the updated 4.3 recovery to only temp boot recovery/twrp using this method:

adb reboot bootloader

fastboot boot twrp-image-here.img

then root (using the zip here: http://download.chainfire.eu/supersu) rather than flashing twrp using heimdall. That way you've still got stock recovery and are able to dd it for us folks who herped when we should've derped. :)

Should be able to do (with USB debugging enabled)

adb shell

su

dd if=/dev/block/mmcblk0p22 of=/sdcard/recovery_4.3_stock.img bs=4096

Thanks again :)
[Galaxy S 4 General] arip:
Any other ideas for dumping the recovery image? I still haven't overwritten stock.
[Galaxy S 4 General] tublah:
Yep - I think I gave you the wrong partition # - try this:

dd if=/dev/block/mmcblk0p22 of=/sdcard/recovery_4.3_stock.img bs=4096
[Galaxy S 4 General] Sammy4Life:
BTW, this is exactly what I did on on stock recovery 4.2.2 but when I flashed it back it got stuck in a loop booting into recovery loop. Still on my call, maybe a bit later I can follow through some of your instructions.
[Galaxy S 4 General] arip:
Ah yeah, I wonder why it was the right size before, though.

Here is the new dump: http://www.speedyshare.com/ZkNuc/i9505g-recovery-4.3-stock-try2.img

The SHA1 of the image is 0c39403d21381f16998608eda7a2903847c6849f.
[Galaxy S 4 General] SamuriHL:
I really need to try to make a script that can create a recovery img from the recovery.img.p. Matt Groff showed us how to do that with boot.img files and in theory the same process should work for recovery. I'll mess around with it tonight. The House of Bionic code has the ability to do it for the boot.img so I'll see if I can modify it for recovery.img. Would be rather handy to be able to create a recovery.img for the update we're on.

---------- Post added at 04:43 PM ---------- Previous post was at 04:41 PM ----------

The sha1 of the one I pulled from mine today after successfully completing the upgrade was:

d6a4f837e3a04c60abe7cea01afe964589de8a24

I don't get how all these different images can be so different.
[Galaxy S 4 General] tublah:
w00t! This restored and booted up for me! Thank you a billion times! :)