yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 5] AptLogic:
I tried the same patches that were introduced in the latest build in APTOS and it bootlooped me, so I think there may be an issue with the framework-res.apk that was in the tethermod. At this point I'll be removing the updated build later tonight until I can get things sorted out.
[AT&T Samsung Galaxy S 5] invert_nexus:
Yeah. That's what i was thinking. Spent a little time trying to find exactly what it was that muniz_ri did to the framework-res, but didn't come across it yet.
[AT&T Samsung Galaxy S 5] AptLogic:
Well whatever it is cut the file size of the framework-res.apk in half
[AT&T Samsung Galaxy S 5] Vesnyx:
So I just thought of an easy way to verify that this is working. I'm going to upload a cubed version of the stock recovery.img.

This is the stock OF3 recovery.img in a tarball. It should go through Odin fine. This should match the version present in the OP.

http://www.mediafire.com/file/xmdb3gx8zwbjj41/recovery.tar.md5

This is the cubed signed version of the same image.

http://www.mediafire.com/file/9niqpfqcpk9sc76/recovery.tar.md5

Try both and tell me which works and which doesn't.
[AT&T Samsung Galaxy S 5] NavSad:
Looks like it.
[AT&T Samsung Galaxy S 5] pinheaD420:
Yea 2.3.1 worked fine .... Lol glad im not crazy was thinking I didn't do something right !
[AT&T Samsung Galaxy S 5] pinheaD420:
Ugh FML he trued to flash Xposed and bootlooped her gos flash 4 lol I can def confirm new root method works like a charm every time lol and is way easier ....
[AT&T Samsung Galaxy S 5] AptLogic:
And Safestrap works natively on it too (not like that helps tho). I might make a 4.4 rom at some point
[AT&T Samsung Galaxy S 5] NavSad:
[MENTION=7597286]AptLogic[/MENTION] I installed KitKat on my phone using the experimental BL.
[AT&T Samsung Galaxy S 5] pinheaD420:
Rooted?
[AT&T Samsung Galaxy S 5] NavSad:
You can install rooted but I choose stock.
[AT&T Samsung Galaxy S 5] lordmorphous:
Can anyone say whether or not this new method will work on the 870A?
[AT&T Samsung Galaxy S 5] AptLogic:
Well for it to work on the 870a we'd need an engineering firmware for it
[AT&T Samsung Galaxy S 5] AptLogic:
That feeling when you're testing an experimental ROM and you forget to replace the framework-res.apk that was causing bootloops.

gg brain
[AT&T Samsung Galaxy S 5] xdanilva:
the cubed one says is invalid

and the the stock one in a tar ball says fail
[AT&T Samsung Galaxy S 5] Vesnyx:
Hmmm... Okay then, seems like the cubed image might not be signed properly.

Before I rule out that the original tar is entirely incorrect, could you let me know which version of Odin you're using. Apparently there's a difference in the file structures between 3.10.7 and 3. I used 3.10.7 to make it. Also, you're putting it in the AP slot correct?

Here's the cubed image with the 00's at the end removed. I don't feel like this'll work, but you never know until you try right?

http://www.mediafire.com/file/fn57268br9qsbos/recovery.tar.md5
[AT&T Samsung Galaxy S 5] NavSad:
Fails with Secure check fail:recovery.
[AT&T Samsung Galaxy S 5] xdanilva:
I'm using odin 3.11

---------- Post added at 12:11 AM ---------- Previous post was at 12:07 AM ----------

im also putting it in the ap slot also which slot is the ap slot on odin 3.07

---------- Post added at 12:19 AM ---------- Previous post was at 12:11 AM ----------

none of them work not even the cubed 00 version works all of them say SECURE CHECK FAIL : recovery and on odin 3.07 side it says md5 hash is invalid and file.tar.md5 is invalid
[AT&T Samsung Galaxy S 5] Vesnyx:
Can you go to Settings -> Security -> Reactivation Lock? It should be turned off. If that isn't it, then it might just be that cuber isn't signing the images properly.

Honestly, I'm kind of confused. The stock recovery should be able to flash through Odin perfectly fine. I didn't sign it with Cuber but it's still throwing an error for some reason. I'm not super experienced with Odin, so if anyone is willing to chime in and help here that would be great.
[AT&T Samsung Galaxy S 5] pinheaD420:
I have best luck with 3.0.9.
[AT&T Samsung Galaxy S 5] AptLogic:
Give your firmware a check, there's always the chance it's corrupted.
[AT&T Samsung Galaxy S 5] xdanilva:
reactivation lock is also off [MENTION=5674700]Vesnyx[/MENTION]
[AT&T Samsung Galaxy S 5] xdanilva:
[MENTION=5674700]Vesnyx[/MENTION] your firmware was corrupted or you did something else improperly

Attached the proper stock recovery tar below
[AT&T Samsung Galaxy S 5] AptLogic:
Ya spelled his name wrong rip
[AT&T Samsung Galaxy S 5] xdanilva:
[MENTION=5674700]Vesnyx[/MENTION] [MENTION=7597286]AptLogic[/MENTION] fixed it also I have the cubed version both pass in odin after doing the following commands in ubuntu or cygwin

Attached Cubed Version Below

tar -H ustar -c recovery.img > recovery.tar
md5sum -t recovery.tar >> recovery.tar
mv recovery.tar recovery.tar.md5
[AT&T Samsung Galaxy S 5] AptLogic:
Yeah the cubed recovery works... now all we have to do is get a cubed twrp to work.
[AT&T Samsung Galaxy S 5] Vesnyx:
WithHmmm, okay maybe my tar file's are messed up. I'll provide the cleaned and cubed TWRP recovery.img, but you'll have to tar it. This will probably trip your Knox counter, so if you're comfortable with that try flashing it.

God I'm so hyped if this works. Only thing to be worried about now is that the phone won't boot into TWRP properly because the phone doesn't accept it.
[AT&T Samsung Galaxy S 5] AptLogic:
I'm fine with tripping the Knox counter, my warranty ran out a couple month ago anyway
[AT&T Samsung Galaxy S 5] Vesnyx:
[MENTION=7597286]AptLogic[/MENTION] [MENTION=7820902]xdanilva[/MENTION]

So I looked into the "cubedrecovery.tar" and it's actually just the stock OF3 recovery in a tarball. I'm not sure what the recovery.tar was but I compared with the cubed version I made and they don't seem to be the same. Either way I've provided links to test these again. Each of the folders contains 3 files: one is the default image with no cubed, the second is purely an image gone through cuber, and the third is a cubed boot image with the zeros at the end removed.

This folder contains the stock OF3 recoveries:

https://www.mediafire.com/folder/61g1aar6p0eqa/Attempt_1_with_OF3_Stock_Recovery

This folder contains the TWRP images:

https://www.mediafire.com/folder/17vit36pd9ajn/Attempt_2_with_TWRP_Images

The first one in the TWRP shouldn't even flash since it's not signed.
[AT&T Samsung Galaxy S 5] xdanilva:
oops
[AT&T Samsung Galaxy S 5] samccfl99:
So excuse me if I am a bit dense. After Odining the Experimental firmware, the BL will be a KK BL? And then does the BL stay KK after flashing the Special OF3 rom or what? I would certainly like to get rid of this OI5 BL and not have to worry that I cannot run SafeStrap anymore, if needed...LOL

I hate to ask, but next time someone does this, can they provide a screenshot from the Samsung Phone Info app (or equivalent) after odining AND after flashing OF3? I would just like to see (see attached current SS).

THANKS
[AT&T Samsung Galaxy S 5] sixxkilur:
while on Stock Prerooted OF3 from https://www.androidfilehost.com/?fid=24052804347788226 I tried via Odinv3.11 twrpcubed.img and twrpcubedremovedpad.img both gave same fail error Unsupport dev_type.

tar made via [MENTION=8011874]

Echo off[/MENTION]
tar --group=1 -H ustar -c twrpcubedremovedpad.img > twrpcubedremovedpad.tar
md5sum -t twrpcubedremovedpad.tar >> twrpcubedremovedpad.tar.md5
echo Done! boot.tar file ready in this folder.
pause>nul
[AT&T Samsung Galaxy S 5] AptLogic:
After flashing the experimental firmware, you should be on an OF1 BL, which is KitKat.

However, after using the special OF3, you will be going to an OF3 bootloader because the special OF3 works by flashing over EVERYTHING, as can be seen in the attached screenshot.

Did you try the stock recoveries as well? Because if you don't we have no idea if it's a problem with cuber or not.
[AT&T Samsung Galaxy S 5] AlanMaciiasz:
any way to downgrade to kitkat?
[AT&T Samsung Galaxy S 5] sixxkilur:
All 3 stock images failed with Unsupport dev_type
[AT&T Samsung Galaxy S 5] sixxkilur:
OK figured i would try other methods for tar'n my method uses

tar --group=1 -H ustar -c stockrecovery.img > stockrecovery.tar
md5sum -t stockrecovery.tar >> stockrecovery.tar.md5
echo Done! boot.tar file ready in this folder.
pause>nul

some of you are using

tar -H ustar -c stockrecovery.img > stockrecovery.tar
md5sum -t stockrecovery.tar >> stockrecovery.tar
mv stockrecovery.tar stockrecovery.tar.md5

Retried stock img with your syntax and it passed. so going to do the same for other images and get back to you all.
[AT&T Samsung Galaxy S 5] xdanilva:
[MENTION=5674700]Vesnyx[/MENTION] For me everything failed except for the normal stock

Here's all the TWRP and stock recoveries in .IMG and .tar

https://drive.google.com/file/d/0ByaW5Jr3VVQWb0txOFpDNWN3dnM/view?usp=drivesdk

---------- Post added at 06:08 PM ---------- Previous post was at 06:06 PM ----------

@AptLogic how did you get a stock status bar drawer?
[AT&T Samsung Galaxy S 5] AptLogic:
AptOS uses a ported Nexus SystemUI to do that. Problem is fingerprints don't work on the lock screen but I'm working on it.
[AT&T Samsung Galaxy S 5] xdanilva:
[MENTION=7597286]AptLogic[/MENTION] Oh cool could you also put Xposed and gravity box in aptos?
[AT&T Samsung Galaxy S 5] AptLogic:
I could try to put in Xposed, but it probably won't get there until the second or third stable beta release. As for gravity box, I'm not going to be baking Xposed modules into the OS, I want the individual user to be able to decide what they want on it.
[AT&T Samsung Galaxy S 5] NavSad:
All fail except stock.
[AT&T Samsung Galaxy S 5] sixxkilur:
gravity box is for ASOP
[AT&T Samsung Galaxy S 5] xdanilva:
Some gravity box features work well with the TouchWiz UI and the capacitive buttons work with gravity box also there's heads up a battery bar and a custom circle battery icon that looks good
[AT&T Samsung Galaxy S 5] sixxkilur:
Alright here goes

All files from

https://www.mediafire.com/folder/61g1aar6p0eqa/Attempt_1_with_OF3_Stock_Recovery

https://www.mediafire.com/folder/17v...th_TWRP_Images

img converted to Tar

using

tar -H ustar -c stockrecovery.img > stockrecovery.tar
md5sum -t stockrecovery.tar >> stockrecovery.tar
mv stockrecovery.tar stockrecovery.tar.md5

Flashed via Odin v3.11

then booted device to recovery mode.

The original files 12Mb

MD5 check pass

stockrecovery.img pass

cubedrecovery.img pass

cubedrecoveryremovedpad.img pass

all files now 11kb

these output files appear to be blank.

if I use
tar --group=1 -H ustar -c stockrecovery.img > stockrecovery.tar
md5sum -t stockrecovery.tar >> stockrecovery.tar
mv stockrecovery.tar stockrecovery.tar.md5

output files are 12MB

MD5 check pass

Stock Flash failed.

summary: I believe using tar via windows with the --group=1 flag does archive the img to tar but corrupts the file.

not using the flag create an empty tar file with 11kb in size.
[AT&T Samsung Galaxy S 5] Vesnyx:
So from what I'm hearing is that only stockrecovery.img is flashing?

I guess there must be something else in the signature that cuber isn't generating.
[AT&T Samsung Galaxy S 5] sixxkilur:
files from https://drive.google.com/file/d/0ByaW5Jr3VVQWb0txOFpDNWN3dnM/view

Same for me only stock would pass or flash to device.

---------- Post added at 08:21 PM ---------- Previous post was at 08:19 PM ----------

Anyone know why my tar process would corrupt tar file if I use the --group1 flag and if I do not use that flag why would it create empty tar files?

I am using IMGtoTar for windows.
[AT&T Samsung Galaxy S 5] Vesnyx:
Yup, that means that cuber isn't generating valid signatures that we can flash. This is rather unfortunate. I'd have to examine the details more closely, but there's probably some magical extra thing that Samsung is adding to the signature.

Also [MENTION=7533813]NavSad[/MENTION] how did you load the img into IDA? I'd love to sift through the code but I cannot figure out what settings to use.
[AT&T Samsung Galaxy S 5] sixxkilur:
Yea earlier I found this https://xdaforums.com/showpost.php?p=60879993&postcount=34https://xdaforums.com/showpost.php?p=60879993&postcount=34
[AT&T Samsung Galaxy S 5] NavSad:
I used this:https://github.com/Surge1223/ida-mbn-sbl-loader.
[AT&T Samsung Galaxy S 5] AptLogic:
What if we try something new and try using Safestrap on the engineering firmware to use kexec

If we can get it to work, I bet we can find some dev to automate the process
[AT&T Samsung Galaxy S 5] AlanMaciiasz:
did aptOS suport themes?please includen them
[AT&T Samsung Galaxy S 5] AptLogic:
Themes are supported by both AptOS and X. However, themes will not be pre-installed in either one. This is to accelerate the release process and reduce my test load (if I put a ton of themes in, I'd have to test them all to make sure they work).

If you do, however, want themes, you can download the LAYERS theme app from the Play Store and use it on both X and AptOS.
[AT&T Samsung Galaxy S 5] xdanilva:
oops 2nd time
[AT&T Samsung Galaxy S 5] sixxkilur:
C:\ADroid\fw\experimental\IMGtoTAR\bin>tar -H ustar -c stockrecovery.img 1>stockrecovery.tar
tar: value 4294967295 out of gid_t range 0..2097151
tar: Exiting with failure status due to previous errors
[AT&T Samsung Galaxy S 5] xdanilva:
I just use ubuntu or you can also use cygwin on windows to do that IMGtoTAR is probably outdated

---------- Post added at 10:10 PM ---------- Previous post was at 09:59 PM ----------

@sixxkilur use ubuntu on a vm or dualboot it and use that command in the terminal after changing your active directory or use it in cygwin if you can't run a vm very fast
[AT&T Samsung Galaxy S 5] sixxkilur:
odd that error is present in all instances and diff version of the tools. seems to have created a bug in memory that is causing this error; because the other methods i used hours ago have same error results. brb rebooting.

---------- Post added at 11:12 PM ---------- Previous post was at 11:10 PM ----------

I have not booted up Ubuntu in VM Ware since i shut down and sold my miners.
[AT&T Samsung Galaxy S 5] xdanilva:
[MENTION=6100148]sixxkilur[/MENTION] well have you tried cygwin with the command?
[AT&T Samsung Galaxy S 5] samccfl99:
I lost track. Exactly what are you guys trying to do again??? :confused::D

I also got another question. It is about the BL. My understanding always was that if you went to a 5.0 BL, then you would not be able to Odin back to, say NCE. Then how come you can Odin from PH2 to OI5? And now we can Odin to OF1 from anything? I guess I thought I knew what the rules were. Just trying to understand this one part I never totally knew about. And UNlocking the BL allows a kernel and a real recovery (TWRP) to be flashed, correct?

THANKS
[AT&T Samsung Galaxy S 5] xdanilva:
@samccfl99 We are trying to unlock at&t's super secure bootloader; maybe find root methods for other firmware versions like PH4.

yes unlocking the bootloader allows twrp and a custom kernel to be flashed. I well actually don't know how the bootloader works for your first question.
[AT&T Samsung Galaxy S 5] AptLogic:
We can't go back to NCE because it would violate the qfuse. But we can go from something like PH4 to OI5 because they're both on the same qfuse version. OF1 is on the same qfuse as PH4 and OI5, so we can flash that too.
[AT&T Samsung Galaxy S 5] samccfl99:
Well thanks for that info. Of course there would be no need to go to NCE. I kept seeing that word QFUSE in the thread, but did not know what it was or paid much attention to it. So that is very strange that those 3 BL's have the same one and 5.0 and 5.1 do not have it. And what about OA1? So confusing.

I thought SafeStrap will only run on a KK BL (or actually a KK Kernel), so I would then ask, the OF3 BL allows changing the Kernel to OA1 using NCEFlasher to be able to boot back up on SS? Then we would have to flash the OF3 kernel before leaving SS or could we Flash the OA1 kernel?

Just asking. It is a bit confusing. Inquiring minds need to know...LOL

IT WOULD REALLY BE A MIRACLE IF YOU COULD ROOT MM, BUT THEN WHERE WOULD A CUSTOM ROM COME FROM? HOW MANY PEOPLE STILL HAVE THIS PHONE???

THANKS AND HAVE A NICE DAY AND GOOD LUCK!
[AT&T Samsung Galaxy S 5] AptLogic:
Basically anything that starts with G900AUCU4 or G900AUCS4 is safe to flash. So by this rule, OA1 is NOT safe to flash because it begins with G900AUCU2, so it violates the qfuse.

SafeStrap does run exclusively on a KitKat Kernel (I'm gonna see about porting it to 5.0 like they did on the Verizon S5). But fortunately the engineering firmware used to work is a KitKat kernel so SafeStrap works perfectly.

If you were to flash a 5.0 or above ROM using SafeStrap, then you would have to flash the OF3 kernel too but most ROM installers take care of that already.
[AT&T Samsung Galaxy S 5] xdanilva:
[MENTION=7597286]AptLogic[/MENTION] so any new dev news or screenshots of AptOS? (this thread doesn't have comments for hours at a time sometimes)
[AT&T Samsung Galaxy S 5] AptLogic:
Well I tested a patch for the fingerprint on the lockscreen, and it failed so we might not have a fingerprint lockscreen on AptOS. I'll keep looking into it.

I'm also trying to get the Google dialer to work, and that's a work in progress thing while I try to figure out what dependencies I need to make it stop crashing.

The incallui has also been replaced in an internal build and works fine except for the occasional system UI crash, again working on it.

Estimated beta release is March 5th
[AT&T Samsung Galaxy S 5] xdanilva:
ok
[AT&T Samsung Galaxy S 5] sixxkilur:
LOL! IKR It should be our choice what we do and put on devices that we have paid for; once contract is over and no balance is owed they should offer to unlock BL and network unlock the device. Offering this even for a $50 many users would gladly pay and they would even sale more services and device to the masses.

---------- Post added at 02:55 PM ---------- Previous post was at 02:53 PM ----------

No not yet attempted to copy my archived CYGWIN dir to main drive and the process seems to be borked been stuck at 54% since 3am.

Since 1am been more focused on retrieving data from POS data disk made in Win98SE-WinXP with Adaptec's Easy CD and Direct CD Drag & Drop with UDF unclosed disk sessions. should be a breeze since Nero bought out Adaptec and their technology years ago but still not a quick and easy process. I have recovered apps as old as ICQ99a NukeNabberv2.9 XICQ *****X Pirch98 MusicMatch JukeBox etc.
[AT&T Samsung Galaxy S 5] xdanilva:
[MENTION=6100148]sixxkilur[/MENTION] I also have a middle finger at&t logo
[AT&T Samsung Galaxy S 5] AptLogic:
XD
[AT&T Samsung Galaxy S 5] AptLogic:
Welp I found the root cause of the fingerprint bug in AptOS...

THE NEXUS 6 DID NOT HAVE A FINGERPRINT SCANNER

Now this may not seem like much at first, but the SystemUI AptOS uses was ported over from the Nexus 6, and if the device didn't have a fingerprint scanner, chances are the fingerprint scanner functionality wasn't present in the Nexus 6 SystemUI at all.

I'll see what I can do in this regard, I'll probably have to port from another device or merge the fingerprint functionality in somehow. If anyone wants to help me out I'd appreciate it lol :)
[AT&T Samsung Galaxy S 5] pinheaD420:
I wish I knew how to help fella sadly I'm not much use ....I can test anything you need but that's about the extent of my know how lol
[AT&T Samsung Galaxy S 5] Vesnyx:
Apt, I'm pretty sure that the System UI you're using is from FreedomROM correct? Please make sure to credit DROIDRAZ for his work on originally porting it if you do intend to use that UI. I also don't think that discussing a upcoming ROM really belongs in a thread that should mainly be about rooting the device. Perhaps making a separate thread to discuss your upcoming features would be better.

Anyway, since cuber doesn't appear to be working, I think we'll have to approach this from another angle. I've looked through a couple of threads and apparently there's a G900-AZ model. It's basically a rebranded G900-A, so we might be able to use that to do something.
[AT&T Samsung Galaxy S 5] xdanilva:
same
[AT&T Samsung Galaxy S 5] sixxkilur:
This post mentions of someone adding it to custom roms.

https://xdaforums.com/galaxy-s5/general/fingerprint-opensource-romcm-mokee-t3315196

After some digging the fingerprint scanner drivers are loaded via kernel level see url https://github.com/MoKee/android_kernel_samsung_klte/tree/mkl-mr1/drivers/fingerprint
[AT&T Samsung Galaxy S 5] sixxkilur:
Easy answer is Touchwiz based rom then yes you can get it to work. ASOP not so much according to his post MM and higher has fingerprint API. LL etc do not there are no drivers to add to LL- because Samsung did not release them opensource. So maybe. using his works. He mentions he is only able to add FP to CM13 or higher because of this.
[AT&T Samsung Galaxy S 5] AptLogic:
I already tried those files and it didn't make any difference. Again it seems to be more of a problem of the SystemUI itself doesn't support fingerprinting of any kind.
[AT&T Samsung Galaxy S 5] sixxkilur:
The scanner is loaded from the kernel

if SENSORS_FINGERPRINT
config SENSORS_FINGERPRINT_SYSFS
tristate "fingerprint sensor sysfs support"
default n
help
If you say yes here you get support for
fingerprint sensor FINGERPRINT_SYSFS
config SENSORS_VFS61XX

taken from his code on GitHub.
[AT&T Samsung Galaxy S 5] boyhonda5:
Do you think the "experimental" firmware for the G900A could work on the G870A to take it back and flash the pre-rooted Active ROM?
[AT&T Samsung Galaxy S 5] AptLogic:
I doubt it but you could try... My guess is ODIN would throw an auth error since it's a different device.

No harm in trying tho
[AT&T Samsung Galaxy S 5] AptLogic:
Updated the OP to reflect the fact that we don't actually need chrome after all.

:)
[AT&T Samsung Galaxy S 5] sixxkilur:
"Step 2: Our Old Friend"

Still mentions Chrome.
[AT&T Samsung Galaxy S 5] AptLogic:
Alrighty so it seems that AptOS is well on its way to an earlier beta release than expected! We've gotten the phone bug worked out so now it actually works, and I'm working on getting a different SystemUI ported.

So given the fact that things are pretty stable, I'm placing the BETA release date for AptOS on Friday, March 3rd. That way you all can play with it over the weekend.

:)
[AT&T Samsung Galaxy S 5] xdanilva:
Do you mean the fingerprint scanner by the phone bug? [MENTION=7597286]AptLogic[/MENTION]
[AT&T Samsung Galaxy S 5] AptLogic:
No the bug I was talking about was a bug where the SystemUI would crash several times when you make or receive a call. Not very catastrophic, but very annoying because it resets the wallpaper every time.
[AT&T Samsung Galaxy S 5] xdanilva:
Do you have any new features so far as of after divinebeats [MENTION=7597286]AptLogic[/MENTION]
[AT&T Samsung Galaxy S 5] AptLogic:
If anyone knows of any other Samsung devices that don't have root, feel free to reply to this thread with the device name and I'll take a look at it :)

Also if ANYONE has the firmware files for N910AUCU2COC6, I'd love it if you'd share ;)
[AT&T Samsung Galaxy S 5] boyhonda5:
I've tried rooting my G870A by the downgrade/kingoroot-king root methods as described for the G900A (with the proper G870A files of course) but it seems kingoroot and king root don't have any love for the Active?
[AT&T Samsung Galaxy S 5] AptLogic:
This is a long shot, but try flashing the noship file for the G900A and see if it works.
[AT&T Samsung Galaxy S 5] boyhonda5:
Should I downgrade to 5.0 first, or try it from the 6.0.1 that I'm on now?
[AT&T Samsung Galaxy S 5] AptLogic:
I think it'll be fine if you try from 6.0.1
[AT&T Samsung Galaxy S 5] boyhonda5:
I'll give it a go this evening!
[AT&T Samsung Galaxy S 5] AptLogic:
Alrighty cool :)
[AT&T Samsung Galaxy S 5] PopTartKing:
Can you try importing the AptOS rom to the Galaxy Alpha? If you can't, can you try bringing Phoenix Rom?
[AT&T Samsung Galaxy S 5] AptLogic:
I could try but I don't own a Galaxy Alpha so I can't test it.
[AT&T Samsung Galaxy S 5] AptLogic:
Oh also...

May all AT&T GALAXY NOTE 4 OWNERS PLEASE COME FORWARD and PM me, I've got a couple tests for anyone that's up for them (the good kind)