yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 5] AptLogic:
Whoever finds one that works with X ROM please tell me so I can bake it into AptOS.
[AT&T Samsung Galaxy S 5] Goron_Elder_Chris:
I did not but what ROM are you on? I am on X ROM atm
[AT&T Samsung Galaxy S 5] pinheaD420:
Witch one there's 4 different ones no clue witch one to flash lol
[AT&T Samsung Galaxy S 5] xdanilva:
Here ya go [MENTION=7597286]AptLogic[/MENTION] [MENTION=3108410]pinheaD420[/MENTION] [MENTION=7087653]Goron_Elder_Chris[/MENTION]

https://xdaforums.com/xposed/unofficial-xposed-samsung-lollipop-5-0-x-t3455992
[AT&T Samsung Galaxy S 5] invert_nexus:
That's right. I forgot about dkcldark's framework. I found that after I'd already got arter97's working on my phone. And that was when Kingroot took a crap on us. Since then, I didn't want to mess with it fearing a bootloop. And since root has returned, I haven't had time to change anything yet.

dkcldark's framework is the newest one. It should work, I would think.

I'm on twi5ted lollipop presently. Been planning on trying out X at some point, just no time.
[AT&T Samsung Galaxy S 5] pinheaD420:
Witch one do I flash is what I was asking ...There's a arm a arm64 and x86 version ? Also says must be flashed in custom recovery I'm assuming FlashFire will still work ?
[AT&T Samsung Galaxy S 5] AptLogic:
Flash the arm version using FlashFire
[AT&T Samsung Galaxy S 5] pinheaD420:
Thx fella

---------- Post added at 07:51 PM ---------- Previous post was at 07:19 PM ----------

Sooooooo dumb question but I have flashed 2 versions now and hasn't done anything .... I'm confused I have flashed this before on other phones but yea I'm lost as to what's I'm doing wrong lol
[AT&T Samsung Galaxy S 5] xdanilva:
did you flash arter's version first then dklcdark's?
[AT&T Samsung Galaxy S 5] pinheaD420:
No I did it in opposite order I believe
[AT&T Samsung Galaxy S 5] invert_nexus:
Probably a dumb question, but just checking the obvious.

You do have the xposed installer set up, right?
[AT&T Samsung Galaxy S 5] xdanilva:
well arters xposed uninstaller doesn't work as it softbricks your device so first backup your data partition with flashfire and save it to a secure location then flash COI5 to your device with odin and follow the steps from there then make sure to never installer arters version install dkcldark's version
[AT&T Samsung Galaxy S 5] pinheaD420:
I got it working using files from above link .... All modules IV installed work great so far .
[AT&T Samsung Galaxy S 5] shadowofchaos:
So I take it, people are pretty much tinkering with stuff here to see if we can get root with Marshmallow?
[AT&T Samsung Galaxy S 5] xdanilva:
well there's still no root on marshmallow because of really high security on android marshmallow for at&t
[AT&T Samsung Galaxy S 5] AptLogic:
If we want to get root on Marshmallow (or permanent on 5.1.1 for that matter), we'd need to use a modified kernel that "relaxes" the SELinux and Knox security settings so that it will allow root. Its not as easy as inserting the su binaries and packaging, the kernel will detect it and bootloop the phone.
[AT&T Samsung Galaxy S 5] pinheaD420:
Anyone no of a aux volume booster for g900a on xrom 2.3.1 ? Preferably a decent one that doesn't jack the quality up to bad ....
[AT&T Samsung Galaxy S 5] xdanilva:
Divine Beats
[AT&T Samsung Galaxy S 5] AptLogic:
I second that. DivineBeats is really good, and it's gonna be going into AptOS too
[AT&T Samsung Galaxy S 5] pinheaD420:
Any info on a eta for aptos ? Been patiently waiting lol just got this xrom setup but can't wait to give apt a try ... But thank u I will look into this devinebeats ! Thx as always
[AT&T Samsung Galaxy S 5] AptLogic:
The ETA for the first public release will be a beta late this month or early March, with a release coming late March if things go right.
[AT&T Samsung Galaxy S 5] DejaVuAgain:
If you're rooted, it's dead easy to edit /etc/mixer_paths.xml for the individual device volume you want to boost.

Typical boost might be from 84 to 90 ... at 95 the distortion gets pretty bad.
[AT&T Samsung Galaxy S 5] taquanglam181:
I downgrade to 5.0 and root perfect. And now, I want to downgrade from 5.0 to 4.4. Can you help me?
[AT&T Samsung Galaxy S 5] lingo2012:
Ok so no on trying that again?
[AT&T Samsung Galaxy S 5] nnjhbb:
I understood.

Thank you for your dedication and willingness to help. :good:
[AT&T Samsung Galaxy S 5] NavSad:
That's great
[AT&T Samsung Galaxy S 5] AptLogic:
[MENTION=4911082]lingo2012[/MENTION] the experiment is ready.

https://www.androidfilehost.com/?fid=673368273298916337

This is a modified version of Resurrection Remix MM, I've slipped an ATT kernel (v3.4) into the package so it should work but at this point we just have to wait.

Flash like you would any other custom ROM with FlashFire. Remember to queue "Wipe" before "Flash ZIP/OTA" and keep Everroot disabled. OF3 is recommended but you can probably use any rooted version that supports FlashFire.

Also be aware that this does not come with GApps as it is an experimental release (due to the Kernel change). You're welcome to sideload GApps but I wanted to make the package as small as possible.
[AT&T Samsung Galaxy S 5] lingo2012:
Ok as soon as I find out ill let you know
[AT&T Samsung Galaxy S 5] lingo2012:
Here we go fingers crossed
[AT&T Samsung Galaxy S 5] AptLogic:
Yeah let's hope this works.. I don't see why it wouldn't.
[AT&T Samsung Galaxy S 5] lingo2012:
so much for hoping I got the same error, kernel related. flashing back OI5 again.
[AT&T Samsung Galaxy S 5] AptLogic:
Augh... how though? I copied over the boot.img from the PH4 release...

Update: Got another thing in store... working on it right now but I'm probably not gonna stop trying until I get a MM ROM working!
[AT&T Samsung Galaxy S 5] lingo2012:
idk i flashed everything right as soon as it starts i get the error.
[AT&T Samsung Galaxy S 5] AptLogic:
Alright... AT&T never makes things easy lol... working on another thing. [MENTION=4911082]lingo2012[/MENTION] try rooting on OI5, and then use FlashFire to upgrade to PH3 and use EverRoot to keep the root access.
[AT&T Samsung Galaxy S 5] NavSad:
I've heard SS will work as long as you have a KK kernel.
[AT&T Samsung Galaxy S 5] AptLogic:
We could try using SS... try using it with the NCE flasher and flash the same modified MM ROM and let's see what happens... (I've been focusing more on FlashFire than SS)

Potential New Development: Someone try flashing this: http://www.emccann.net/nuclearmistake/VanirAOSPNightlies/klteatt/vanir_klte_6.0.120516.zip using FlashFire and the instructions on the first page.
[AT&T Samsung Galaxy S 5] lingo2012:
Ill try the PH3 first
[AT&T Samsung Galaxy S 5] AptLogic:
Alrighty good luck
[AT&T Samsung Galaxy S 5] SmokeyDog:
Started with G900AUCS4CPA6 and after several soft bricks and reboots, i finally rooted my phone and downgraded back to 5.0.

Phone would root everytime but loose it after reboot.

This worked for me-

After soft bricking the phone flashed the phone with ol5 using odin.

Followed post 1 and rooted with king root 4.81

Updated SU binary

went to playstore installed SU and updated.

followed part 1 going back to good ol' 5.0

Never rebooted phone.

After phone rebooted have android 5.0 already rooted.

Thanks for all the hard work. Use this site a lot. First time posting.
[AT&T Samsung Galaxy S 5] AptLogic:
Always good to hear a success. This is a group effort, all input is appreciated
[AT&T Samsung Galaxy S 5] nnjhbb:
How to use this? With OI5 or EF3? With FlashFire?
[AT&T Samsung Galaxy S 5] AptLogic:
Refer to the instructions on page 1 post 3 "flashing ROMs"
[AT&T Samsung Galaxy S 5] siddharthrv:
cyanogen

can i install cm rom in s5 at&t
[AT&T Samsung Galaxy S 5] AptLogic:
I don't think there are any 4.4 Roms that lollipop users can safely install at this point.
[AT&T Samsung Galaxy S 5] AptLogic:
New Root method available!!

Thanks [MENTION=7533813]NavSad[/MENTION] for your help, without which this wouldn't be possible!

https://xdaforums.com/showpost.php?p=70011917&postcount=1
[AT&T Samsung Galaxy S 5] NavSad:
Good news everybody it looks like this engineering firmware bootloader is vulnerable to CVE-2014-0973. Which would allow us to unlock out bootloader.
[AT&T Samsung Galaxy S 5] AptLogic:
Please expand on the process that would involve while I research the exploit okay I have the info I need now. Could we use the Cuber program developed for the Kindle Fire HDX on our phones then?
[AT&T Samsung Galaxy S 5] Vesnyx:
I feel like I missed something. Could you link me to the engineering firmware?

Is it this link?

https://androidfilehost.com/?fid=745425885120704448

or is this newer one?

https://www.androidfilehost.com/?fid=673368273298933039

And how did you manage to get an engineering firmware?
[AT&T Samsung Galaxy S 5] AptLogic:
No idea where the engineering firmware came from, seems to have just popped up last December.

The engineering one is the first link. The second link is just the pre rooted OF3 with added things so the bl doesn't throw a fit.
[AT&T Samsung Galaxy S 5] Vesnyx:
How do we know it's an engineering firmware? And what is the difference from a stock OF1 firmware? I'm assuming it's the s-boot or the aboot that's different.

Seems I also found an OI2 firmware by the same releaser. Anyone want?

I think OI2 is 5.1.1, but no 100% sure about that.
[AT&T Samsung Galaxy S 5] NavSad:
I got the firmware from z3x box.

---------- Post added at 09:36 PM ---------- Previous post was at 09:35 PM ----------

Maybe I made a TWRP image using that tool but I haven't flashed it yet.

---------- Post added at 09:38 PM ---------- Previous post was at 09:36 PM ----------

OI2 is also engineering firmware, and I think all engineering firmwares are based on 4.4.2 . But I think it would be nice to have it.
[AT&T Samsung Galaxy S 5] Vesnyx:
Here's OI2:

https://mega.nz/#!3QQAgQIT!k4k-8cF8HW82iJKilQuxrZ_3VmcEXvYZR95ngXzWg_4

Credits go to gsmhosting/z3x

Isn't OF1 similar to OF3 (5.0)? That's why I think that OI2 is probably similar to OI5. Anyway, if the TWRP flash works, then we should be set to flash a new kernel and get some new development here.
[AT&T Samsung Galaxy S 5] Goron_Elder_Chris:
Towelroot just says "Please ensure you are connected to the internet."
[AT&T Samsung Galaxy S 5] Vesnyx:
Try Towelroot v2. Supposedly, it should work.
[AT&T Samsung Galaxy S 5] Goron_Elder_Chris:
upload? can't find a download for v2

Edit: found https://www.androidfilehost.com/?fid=529152257862703076
[AT&T Samsung Galaxy S 5] NavSad:
No OF1 is completly different, it has a 4.4.2 base whereas OF2 has a 5.0 base.
[AT&T Samsung Galaxy S 5] AptLogic:
Did you remember to install chrome? If you don't install chrome and connect to wifi it won't work.
[AT&T Samsung Galaxy S 5] Goron_Elder_Chris:
I think I might've not but using v2 worked like a charm
[AT&T Samsung Galaxy S 5] AptLogic:
Alrighty. Glad ya got it working!
[AT&T Samsung Galaxy S 5] Vesnyx:
How did the TWRP flash go?
[AT&T Samsung Galaxy S 5] AlanMaciiasz:
amazing work ,any way to downgrade to kitkat? thanks
[AT&T Samsung Galaxy S 5] NavSad:
Haven't tried it out yet. Will try it when I get back home.
[AT&T Samsung Galaxy S 5] Vesnyx:
For anyone willing to try (and by try I mean that this may brick your device)

YOU HAVE BEEN WARNED, I hold no responsibility for your decision in flashing this file.

PLEASE NOTE, THIS MAY VOID YOUR WARRANTY BY TRIGGERING KNOX.

Here's a signed version of klte twrp image. Use WinRAR or 7-Zip to extract the image and I believe you should be able to flash this through Odin. It goes in the AP slot. If Odin won't let you flash this, try FlashFire.

Make sure you follow the directions in the OP before proceeding with this flash.

If this works we should be able to get AOSP on our device at last. :)
[AT&T Samsung Galaxy S 5] NavSad:
I tries it before and it said unsupport dev_type. I think we have to use dd or Flashfire.
[AT&T Samsung Galaxy S 5] Vesnyx:
Apparently, it might be an issue with the bootloader having a different device type than what the TWRP image is intended for. Can you flash the original OF3 bootloader, starting with the experimental bootloader in Odin? Or does it give the same error?
[AT&T Samsung Galaxy S 5] AptLogic:
Flashing the OF3 bootloader in ODIN from a noship build like OF1 does work without a problem.

Attempting to flash the TWRP in ODIN using the OF1 Bootloader returns a SECURE CHECK FAIL: RECOVERY
[AT&T Samsung Galaxy S 5] Vesnyx:
Does the image work through FlashFire?
[AT&T Samsung Galaxy S 5] AptLogic:
working on it.. will update.

EDIT: That's a negative. Old recovery was still there after the flash.
[AT&T Samsung Galaxy S 5] zenrox:
Can't wait to flash a asop rom
[AT&T Samsung Galaxy S 5] NavSad:
Is this the one using the signing tool?
[AT&T Samsung Galaxy S 5] Vesnyx:
So as it turns out, there is a little segment in the TWRP that gets cut out when using cuber to sign the image. Figuring out how Samsung uses this might help: SEANDROIDENFORCE

53 45 41 4E 44 52 4F 49 44 45 4E 46 4F 52 43 45
[AT&T Samsung Galaxy S 5] AptLogic:
Yeah that's a result of Samsung's variant of lk. I found out about it last night doing research and forgot to tell you guys. We need a way to keep that segment while maintaining the signature or else the device will reject it.
[AT&T Samsung Galaxy S 5] Vesnyx:
Try this through ODIN, apparently flashfire can cause issues if you try to flash TWRP through it.
[AT&T Samsung Galaxy S 5] AptLogic:
I turned off my computers for the night :( I'll give it a go first thing tomorrow.
[AT&T Samsung Galaxy S 5] pinheaD420:
I'd be happy to test been waiting for this for a long time ... So odin "AP" slot ? That all I need to do ?

---------- Post added at 04:49 AM ---------- Previous post was at 04:48 AM ----------

Has anyone else flashed this yet ?Fail ? Success ? Anything before I dive in this ***** like a fat kid at a buffet ?
[AT&T Samsung Galaxy S 5] Vesnyx:
Yep that should be all. Don't know if anyone else has tested.

In all honesty, it probably won't pass the flash check, but who knows.
[AT&T Samsung Galaxy S 5] pinheaD420:
Most likely but never no till we try ....
[AT&T Samsung Galaxy S 5] Vesnyx:
:good: Let me know how it goes.
[AT&T Samsung Galaxy S 5] pinheaD420:
Didn't get very far lol haven't used my laptop since Xmas went to boot it up and now for some odd reason it won't boot .... Will reinstall winfail in the morning and will post results ...
[AT&T Samsung Galaxy S 5] samccfl99:
Hi. I hate to always ask this question. So again, does this new rooting method in Post #1 now work ALWAYS?

Can you be on any LP or MM version of Android to do this or must you start from OI5 (meaning still being stuck on the OI5 BL)?

After rooting, must we first use that Special pre-rooted OF3 and then restore whatever 5.0 FF backup we use?

Lastly, I never saw anymore mention about Unlocking the BL, so we can flash a kernel and use other roms???

I do thank you all for your work. I do not understand much when you get into the weeds...LOL, but I do know how to get around my phone. I would love for this to be permanent so I can play, because I have felt uneasy with this OI5 BL and not knowing if I could root again if some disaster happened (phone is over 2.5 years old now and still great, but you never know).

THANKS
[AT&T Samsung Galaxy S 5] xdanilva:
well first of all there's still a locked bootloader and there's aboot and some other bootloader files in the ap file so im guessing flashing the twrp recovery in odin won't work
[AT&T Samsung Galaxy S 5] AptLogic:
Yes, this new rooting method should ALWAYS work, because its based on an older engineering firmware that runs on KitKat and is vulnerable to towelroot.

You can start on ANY android build but you MUST ODIN down to the engineering firmware to root, after that you should use FlashFire to flash the special from-noship OF3 that is linked in the OP. If you don't use this special zip to upgrade, and instead use the old pre-rooted OF3, you will get an unauthorized software error upon bootup.

As for the bootloader unlock, we're working on it but as always don't hold your breath.
[AT&T Samsung Galaxy S 5] AptLogic:
Do yourself a favor and get a flash drive with Linux on it, saves ya from surprises when Winblows doesn't want to boot ;)
[AT&T Samsung Galaxy S 5] xdanilva:
have you tested it personally yet? [MENTION=7597286]AptLogic[/MENTION]
[AT&T Samsung Galaxy S 5] AptLogic:
The root method? Yes, many times now.

The patched recovery? Not quite yet, I needed my phone today so I'm not gonna be trying it for another couple hours.
[AT&T Samsung Galaxy S 5] pinheaD420:
I'm going to be attempting here in a few mins .... Everyone cross Thier fingers ...
[AT&T Samsung Galaxy S 5] AptLogic:
Fingers crossed! lol

Meanwhile, I found a way to root the G900V using engineering firmwares too!
[AT&T Samsung Galaxy S 5] pinheaD420:
OK so downloaded ur TWRP file when try to add to AP slot it will not allow me to select It ...Doesn't even show up .... I'm going to try every version of Odin this was just first effort on odin3 v3.10.7 ....
[AT&T Samsung Galaxy S 5] AptLogic:
Ya have to tar the file.
[AT&T Samsung Galaxy S 5] pinheaD420:
Lol I asked that fella if I had to do anything he said no ....Thx tho blonde moment ..

---------- Post added at 11:05 PM ---------- Previous post was at 10:23 PM ----------

Yea was a giant fail ....
[AT&T Samsung Galaxy S 5] AptLogic:
So it didn't work?
[AT&T Samsung Galaxy S 5] pinheaD420:
Nope ... Failed as soon as it started in all versions of Odin.
[AT&T Samsung Galaxy S 5] AptLogic:
I'm gonna go ahead and speculate that the image you tried to use didn't have the SEANDROIDENFORCE code in it.

In case you guys haven't put it in: YOU NEED THAT STRING FOR THE IMAGE TO HAVE A REMOTE CHANCE OF FLASHING. :)
[AT&T Samsung Galaxy S 5] pinheaD420:
Yea that's above my pay grade good sir lol but if someone can add it and post a link I'm down to give it a whirl
[AT&T Samsung Galaxy S 5] Vesnyx:
Lol yeah I forgot to mention that the image should be tarred. My bad. I manually edited the hex to add SEANDROIDENFORCE at the end, but I don't think that's the issue. I was looking at the recovery.img in the OF1 tar and it had its own unique signing which I believe is what we need to use with cuber. The TWRP image doesn't have a hash at the end.

However, the main issue is that this hash might be too large for cuber.

I'm thinking that maybe we might be able to use a different CID using beaups method but I think we need to decrypt the verification that differentiates the standard CID from one present on an engineering version. I believe that the emmc number is unique, and it shouldn't be present in the flashable tar. This means we need to reverse aboot. I believe there's a blog post mentioning how to load it into IDA, which we can then compare with LK.

Could you provide the error message that Odin gave?
[AT&T Samsung Galaxy S 5] pinheaD420:
So trued installing x on buddy's s5 it boot looped me was coming from alliance .... So started over got experimental firmware installed towlroot says connect to internet nothing else ....
[AT&T Samsung Galaxy S 5] zenrox:
Run chrome and you will find your issue
[AT&T Samsung Galaxy S 5] pinheaD420:
Lol thx figured that out .... He was telling at me thought I bricked him lol anyway Odin didn't give a error msg only said FAIL immediately after said start. ...

---------- Post added 23rd February 2017 at 12:03 AM ---------- Previous post was 22nd February 2017 at 11:51 PM ----------

OK so now I got the of3 installed it boots says process system isn't responding do you want to close it ? Wait and OK both restart phone ....Any ideas?

---------- Post added at 12:05 AM ---------- Previous post was at 12:03 AM ----------

Nvm after 25 reboots it figured it's self out lol
[AT&T Samsung Galaxy S 5] Vesnyx:
So as it turns out, I actually forgot to remove the padded zeros for the file to be recognized by Odin. ?

I'll be uploading another TWRP image soon. Hopefully, ODIN at least accepts this one.

EDIT: I broke the TWRP image by adding in that hex, the values I thought were padded zeros are reserved to be cubed ("decrypted") afaik.
[AT&T Samsung Galaxy S 5] pinheaD420:
So when I install xrom 2.3.2 I keep getting boot loops .... If I did new root method should I still select all wipe options except internal ? Just trying to figure out where I'm going wrong here ....Going to redownload n try again ....
[AT&T Samsung Galaxy S 5] NavSad:
Go to the date and time in Settings and fix it.
[AT&T Samsung Galaxy S 5] pinheaD420:
Yea figured that out already redownloading ROM now true twice and only get bootlooped
[AT&T Samsung Galaxy S 5] NavSad:
What's the password for OI2?
[AT&T Samsung Galaxy S 5] pinheaD420:
OK third flash of x 2.3.2 on a fresh download and still same result .... Sticks on Samsung logo ....
[AT&T Samsung Galaxy S 5] AptLogic:
I'll look into it... I don't think I changed enough for the device to boot loop like that.
[AT&T Samsung Galaxy S 5] pinheaD420:
You have link for 2.3.1 I no that works?
[AT&T Samsung Galaxy S 5] AptLogic:
Yeah hold on just a sec lemme grab it

Edit: here ya go https://www.androidfilehost.com/?fid=529152257862701103
[AT&T Samsung Galaxy S 5] pinheaD420:
Thx
[AT&T Samsung Galaxy S 5] Vesnyx:
It's in the rar file, but it' should be "www.gem-flash.com"

Back to the signing. It seems that the OF1 recovery.img has this as its signature.

AF D7 67 47 A1 DD 3C D5 FE 3B 27 59 F7 1F 51 C5 B6 60 18 5C 37 F7 FC 3B 7D 58 D8 34 CC 34 75 75 78 0A AE 43 09 11 21 03 CE 47 D5 AF 70 E3 37 62 75 A5 4A CC 17 62 2D 46 0A 38 F8 FE 05 D9 38 6C FC 11 00 8D 39 B4 02 DD F3 E5 73 FF 3F 26 9E 84 25 0E 24 8D 12 FA 1A 84 86 62 DC 86 27 5B 17 10 95 79 0B D0 26 79 4D A4 C7 C5 78 AE 78 03 29 65 4C 58 33 B8 79 54 42 3F C3 EA F9 E3 E4 15 87 10 11 23 10 86 F1 05 32 FF 6F B6 A3 42 C2 50 C0 C7 AD 9E 0B 0A EA 6E 99 41 79 F2 53 39 62 FD CF A8 F8 0F F6 48 EA 35 01 62 7E DD 6A 5A 1E 68 D6 1E 7F AC 5A 5B ED C4 42 BE 75 CF 40 8F E0 5F 9B 20 A3 CF 6D 28 FE 03 5C 0D F1 AC 47 00 4A 16 70 F0 07 00 4C 79 AB 24 11 18 2C AC E2 2F AA BA F2 90 B7 11 E5 CA 13 07 FA F7 75 84 28 21 38 2D 4F 5C 48 F5 85 08 F2 7B A8 4F 0A 0A 5E E6 FB FB AC C7

I'm taking a guess here, but I think that the SEANDROIDENFORCING is simply a flag set by the header to keep the kernel as enforcing rather than permissive. I don't think the TWRP image is hashed at all and we might not even need to include it in the Odin tarball.

Here's the signature for the twrp.img that was made through cuber:

32 CB FD 4A 7A DC 79 05 58 43 11 DF DF 53 DD 8B 94 1B A9 36 F5 38 1E D0 C8 B7 E6 31 4A 09 E2 C2 82 8D DD A1 7E F0 59 76 E2 33 77 BF 87 60 CB 0C 98 1A E0 C1 5B B1 2F 71 88 C8 9D 7C 72 E1 7B 17 CE 11 E7 7A FC 40 D4 8D 2B 9B DE 9D 62 43 7E 0D AD 36 1B 38 D0

The issue right now is that this signing doesn't appear to be validating properly through Odin. This means one of two things, a) my image is messed up (pretty likely) or b) the signature used by Samsung is different from the one presented in the vulnerability. [MENTION=7533813]NavSad[/MENTION] could you verify that the bootloader was indeed vulnerable?
[AT&T Samsung Galaxy S 5] AptLogic:
Maybe the issue isn't the vulnerability, but the way we are attempting to implement it.

Cuber was originally made just for the Kindle Fire HDX, and we are attempting to use it on a Samsung device. While these two may both be forked from lk, the signature length could have been doubled, which means that we should try modifying the program to work with signatures double the length.
[AT&T Samsung Galaxy S 5] invert_nexus:
[MENTION=7597286]AptLogic[/MENTION],

Have you tested x since adding the tether mod? I know that i couldn't flash the mod without bootlooping. I ended up freezing tetherautomation with titanium backup and installing x tether and keeping my fingers crossed that nothing's running home to tell ma bell.

I haven't tried your updated rom.

---------- Post added at 01:50 AM ---------- Previous post was at 01:49 AM ----------

As to the cuber thing, votorx himself discussed issues with samsung in his original thread. Figured you guys would have seen it yourselves.

By the way, i found another thread somewhere where somebody made a script or something to add the seandroid enforce thing to an image. Wasn't much activity in that thread, so not sure how effective it was or in what circumstances.