yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 General] brilliantdonkey:
I have a couple of pristine / just unboxed I9505Gs, and I want to upgrade one to 4.3, and extract all the partitions from both so we can get full system dumps for 4.2.2 and 4.3.

It sounds like I would fastboot twrp, root, and dd out the partitions, but wouldn't rooting modify the system partition? If someone can tell me how to get full system dumps off these phones, I'd be happy to post them somewhere to help figure out this issue (I have another I9505G that is running the same 4.3 leak that is causing problems for all of us in this thread)
[Galaxy S 4 General] mastergrillo:
well I hva the files and symlinked them to /etc still no go anyone else have luck
[Galaxy S 4 General] jamal2367:
not working for me .... i have symlinkin and to /ect and the kernel from faux not working :/
[Galaxy S 4 General] mrvirginia:
yes but you have to root in order to pull a full dump from a dev block. you can't shell su if there's no su...

it's okay if it's only modified with root. we know how to remove that if need be.

adb shell
su
dd if=/dev/block/mmcblk0p16 of=/sdcard/0/system.img.ext4
exit
exit
adb pull /sdcard/0/system.img.ext4 C:\

do this for each respective block that you want to pull...

---------- Post added at 05:00 PM ---------- Previous post was at 04:59 PM ----------

same here, guys. did it a while ago and still no dice
[Galaxy S 4 General] jamal2367:
i have not keymaster file in vendor/firmware ...... lol ... i have the another 6 files copy to /ect with symlinking
[Galaxy S 4 General] SamuriHL:
For the record, you can do neat things like this:

adb shell "su -c 'dd if=/dev/block/mmcblk0p16 of=/sdcard/0/system.img.ext4'"
...

I've used that to script commands that require a su prompt. :)

(EDIT: You can do whole bunches of commands in one line by separating them by a ;....for example: adb shell "su -c 'cd /sdcard/0; dd if=/dev/block/mmcblk0p16 of=system.img.ext4'")
[Galaxy S 4 General] brilliantdonkey:
Okay, I'll do that. By the way, why can't I just dd from within the root shell in TWRP? Just curious :)
[Galaxy S 4 General] mrvirginia:
maybe you can, i don't know. i don't use TWRP nor have i ever tried to use shell while in recovery. i was just giving clear cut instructions on what i know will work for pulling a dev block
[Galaxy S 4 General] jamal2367:
[MENTION=2651267]mrvirginia[/MENTION] have you the keymaster files ? the 5 files ??
[Galaxy S 4 General] faux123:
here's my keymaster files in a tar.gz
[Galaxy S 4 General] jamal2367:
thanks faux ..:) in system/vendor/ect comes the files ???
[Galaxy S 4 General] :
where do i put them? can someone tell me how to symlink them and everything to get "security" working? i really need to install some apps outside of the market and cant
[Galaxy S 4 General] InstigatorX:
Thanks, man. Was downloading every dump in this thread looking for them.
[Galaxy S 4 General] Cozmo85:
So is that what a proper GE rom zip should have? And not the 6 that we all seem to have?
[Galaxy S 4 General] mrvirginia:
would love to know where you grabbed these from. they were not included with the OTA... and i knew what you were referring to because i saw this in a Nexus 4 ROM and also because a fix for Security FC pointed to a keymaster folder...
[Galaxy S 4 General] iB4STiD:
he grabbed them from system dump :good:
[Galaxy S 4 General] jamal2367:
can someone test if its working the keymaster files ???
[Galaxy S 4 General] :
ill test if you can tell me what i need to do with them
[Galaxy S 4 General] mastergrillo:
Man i wish i was at home to test it gotta work

Sent from my GT-I9505G
[Galaxy S 4 General] mrvirginia:
i'm working on it mate

---------- Post added at 05:33 PM ---------- Previous post was at 05:32 PM ----------

can you point me to it please?
[Galaxy S 4 General] jamal2367:
thanks .... i have copy the 5 files in the system/vendor/ect

or system/vendor/firmware or system/vendor/firmware/keymaster ???
[Galaxy S 4 General] InstigatorX:
I put into /system/etc/firmware and not get...

E/QSEECOMAPI: ( 4688): Error::Load image request failed ret = -1, errno = 14

E/QSEECOMAPI: ( 4688): Error::Loading image failed with ret = -1

E/QCOMKeyMaster( 4688): Loading keymaster app failied

E/keystore( 4688): could not open keymaster device in keystore (Operation not permitted)

E/keystore( 4688): keystore keymaster could not be initialized; exiting

whereas before I was getting the file not found error. Thoughts?
[Galaxy S 4 General] jamal2367:
copy the files in vendor/ect ´?
[Galaxy S 4 General] iB4STiD:
and it works !!!!!!!!!!
[Galaxy S 4 General] mrvirginia:
they're like that on Nexus 4...

also, still no dice....
[Galaxy S 4 General] jamal2367:
where you have added the 5 files?
[Galaxy S 4 General] Cozmo85:
More details?
[Galaxy S 4 General] jamal2367:
+1

where you have added the 5 files?
[Galaxy S 4 General] :
can you tell us how you did it
[Galaxy S 4 General] faux123:
Follow my original instructions... :p

copy keymaster files to /system/vendor/firmware, create symlinks from /system/vendor/firmware to /etc/firmware

flash my stock boot + hack kernel

done :)
[Galaxy S 4 General] jamal2367:
thanks for information

how do I add the symlink?
[Galaxy S 4 General] InstigatorX:
Bingo! That did it for me...Security and Uninstalling work!

cd /etc/firmware

ln -s /system/vendor/firmware/keymaster.b00 keymaster.b00

ln -s /system/vendor/firmware/keymaster.b01 keymaster.b01

ln -s /system/vendor/firmware/keymaster.b02 keymaster.b02

ln -s /system/vendor/firmware/keymaster.b03 keymaster.b03

ln -s /system/vendor/firmware/keymaster.mdt keymaster.mdt
[Galaxy S 4 General] brilliantdonkey:
I tried it only through TWRP, it seems to have worked. Here are the system partitions for 4.2.2 and 4.3:

4.2.2: https://mega.co.nz/#!LEEEBYhZ!duzTTS9TeGmgUeSfF4n9UkHrKT023X3blCKak0nH9rc

4.3: https://mega.co.nz/#!HZsU2DYB!PHEzDjhaFZ0S0QRrIQy8ujDicINAoSdmUlD422Y0M14

By the way, here's a diff on the partitions in case anyone is interested, however, the two dumps came from two different phones, so differences in phone-specific files don't necessarily mean it changed through the OTA:

Binary files i9505G 4.2.2 dump/aboot and i9505G 4.3 dump/aboot differ

Binary files i9505G 4.2.2 dump/apnhlos and i9505G 4.3 dump/apnhlos differ

Binary files i9505G 4.2.2 dump/boot and i9505G 4.3 dump/boot differ

Binary files i9505G 4.2.2 dump/efs and i9505G 4.3 dump/efs differ

Binary files i9505G 4.2.2 dump/fota and i9505G 4.3 dump/fota differ

Binary files i9505G 4.2.2 dump/m9kefs1 and i9505G 4.3 dump/m9kefs1 differ

Binary files i9505G 4.2.2 dump/m9kefs2 and i9505G 4.3 dump/m9kefs2 differ

Binary files i9505G 4.2.2 dump/m9kefs3 and i9505G 4.3 dump/m9kefs3 differ

Binary files i9505G 4.2.2 dump/mdm and i9505G 4.3 dump/mdm differ

Binary files i9505G 4.2.2 dump/recovery and i9505G 4.3 dump/recovery differ

Binary files i9505G 4.2.2 dump/rpm and i9505G 4.3 dump/rpm differ

Binary files i9505G 4.2.2 dump/sbl2 and i9505G 4.3 dump/sbl2 differ

Binary files i9505G 4.2.2 dump/sbl3 and i9505G 4.3 dump/sbl3 differ

Binary files i9505G 4.2.2 dump/system and i9505G 4.3 dump/system differ
[Galaxy S 4 General] boterkaaseneieren:
I hope you get it fixed, v10 :) :) :)
[Galaxy S 4 General] InstigatorX:
Btw, I'm running on AT&T SGH-I337.
[Galaxy S 4 General] jamal2367:
works vpn ???
[Galaxy S 4 General] InstigatorX:
Going into VPN screen doesn't FC, set PIN, and get to Edit VPN profile. Don't have a vpn to try.
[Galaxy S 4 General] jamal2367:
what i must changed in updater-script ???? to symlink??? for my rom in xda??
[Galaxy S 4 General] Sammy4Life:
Ok, I was able to finally update to 4.3, at the moment I'm trying to temporarily boot TWRP to root, I am not ready to fully commit to install TWRP at the moment. The issue is that when I perform the following commands:

adb reboot bootloader

fastboot boot openrecovery-twrp-2.6.0.0-jgedlte.img, I get to recovery, however I have no touch capabilities to install SuperSU zip file. I was able to temporarily boot Philz Touch Recovery, however it cannot mount any partitions.

I'm curious if I drop the SuperSu.zip file in the /cache partition can I "apply update" from cache and choose the zip file? I also tried adb sideload to no avail. Anyway to root w/o committing to a fully recovery swap out? I would like to take backups w/o any modifications.

Thanks.
[Galaxy S 4 General] jamal2367:
i flashed my new rom with the 5 files and this :

symlink("keymaster.b00", "/system/vendor/etc/keymaster.b00");

symlink("keymaster.b01", "/system/vendor/etc/keymaster.b01");

symlink("keymaster.b02", "/system/vendor/etc/keymaster.b02");

symlink("keymaster.b03", "/system/vendor/etc/keymaster.b03");

symlink("keymaster.mdt", "/system/vendor/etc/keymaster.mdt");

set_perm_recursive(0, 2000, 0755, 0644, "/system/vendor");

set_perm_recursive(0, 2000, 0755, 0644, "/system/vendor/etc");

set_perm_recursive(0, 0, 0755, 0644, "/system/vendor/firmware");

set_perm(0, 2000, 0755, "/system/vendor/firmware");

set_perm(0, 2000, 0755, "/system/vendor/lib");

not work can user help me ???

---------- Post added at 12:43 AM ---------- Previous post was at 12:29 AM ----------

??

---------- Post added at 12:43 AM ---------- Previous post was at 12:43 AM ----------

????
[Galaxy S 4 General] electronicrice:
Yes because adding more question marks will get you an answer quicker. Knock it off.

You're a "ROM Developer" right? Figure it out or wait patiently.
[Galaxy S 4 General] arip:
I had this same problem. Here's what I did to get root: http://xdaforums.com/showthread.php?p=44290125#post44290125

But at this point my (second attempt) stock recovery image should be able to get you back even if you decide to flash TWRP for reals.
[Galaxy S 4 General] MaKTaiL:
The zip is not opening here. Downloaded multiple times and nothing.

Do you happen to have a mirror? :)
[Galaxy S 4 General] faux123:
try on a PC.. my file host sometimes derps on mobile.
[Galaxy S 4 General] MaKTaiL:
That's what I was doing. :silly:

EDIT

Nevermind, downloaded the 7th time and it worked. lol

Don't know what was happening. Thanks anyway, I'll try it in my ROM soon. :)
[Galaxy S 4 General] SamuriHL:
Well slap me on the butt and call me susan....er, well, not really. LOL! I was indeed able to hand roll a recovery.img file from the 4.3 OTA update zip that matches the sha1 that the recovery img is SUPPOSED to have. I'm about to make this thing an ODIN flashable file and try it. Wish me luck!!

EDIT: Bingo. Recovery for stock 4.3 built by hand from the update....CHECK!

---------- Post added at 08:48 PM ---------- Previous post was at 07:52 PM ----------

Does anyone have the following files from 4.2.2?

modem.bin sha1: a43358aa04912437a98f3348a63d9bc88f3d7af4

NON-HLOS.bin sha1: c15e52d975b0b46478798a436c3feca3d4b755d7

I need them with those exact sha1 hashes. The ones from the full dump zip that was posted don't match this. If anyone has files that do match, please let me know. Thanks!
[Galaxy S 4 General] tublah:
1) Mind sharing the ODIN flashable stock recovery image?

2) Here are my post-4.3 patch SHA1 hashes:

NON-HLOS.bin = 19612bcecf45f83af3818ded291500972111d095

modem.bin = 14ed599a7ef94bee686da4b0dd0970ef3c600a40

3) Here are 4.2.2 SHA1 hashes of modem and non-hlos:

modem.bin = 16621e0712b216729ddc1a0a2cf6f34b0fb5f71b

NON-HLOS.bin = d342c5ddff7d1dd78e06072f90346978055aa9fb
[Galaxy S 4 General] tublah:
Also I am way curious how you hand rolled. I presume combining a 4.2.2 dump of recovery + the patch file?
[Galaxy S 4 General] SamuriHL:
Those won't help me. They MUST be the 4.2.2 files with the hashes I posted else what I want to do won't work.

As for the process, no, it patches the boot.img file that's in the update zip. Which is what the update script does. Basically you extract the recovery-from-boot.p and the boot.img from the update zip and you run an applypatch on it. You can do it on any rooted device. Doesn't even have to be done on the S4. Once the applypatch is done, you end up with a recovery.img file that matches the sha1 that's in the update. (Look at the install-recovery.sh file in the update zip). I copied the files to /sdcard on the phone and created an adb shell and cd /sdcard. Then ran this command:

applypatch boot.img recovery.img 6a1bef2e13ea3b9a4284565d560f7a2c0a17bf5d 9775360 07f4bc5b3cb20428a40d74dd0cff8a147d7155ef:recovery-from-boot.p

Here's my 4.3 ODIN flashable recovery.img file:

http://www.mediafire.com/download/vjc66wl5gb4k2cf/recovery.tar.md5

It was created using the process I mentioned above.
[Galaxy S 4 General] MeFryRice:
I've read through all 3x+ pages and honestly, I'm a bit lost in all the lingo although I have tried to research some of the technical terms you guys speak of.

I hate to be THAT guy but do you guys plan on updating the OP with "how to for dummies" instructions? I'm currently using an AT&T GS4 running the second leak 4.3GE Rom (broadband MDL) and would love to update to the official GE Rom.
[Galaxy S 4 General] SamuriHL:
The problems aren't all worked out yet. Once everything is working, I'm sure someone will either post a new thread or update this one with a how to. But for now, there are issues to overcome still.
[Galaxy S 4 General] bleez99:
I was able to go to the MH1 baseband from the latest leak. Unable to go backwards as we already know. Yes, I have a REAL GE S4.
[Galaxy S 4 General] ismaelmaia:
Bug in copy sd card in version final. Not copy in sdcard. Check error.
[Galaxy S 4 General] SamuriHL:
Nice. Well, I just cooked up something for the baseband. I have NO IDEA if it'll work.
[Galaxy S 4 General] bleez99:
Here's what I did. I dd'd NON-HLOS.bin then modem.bin from the other thread using the by-name devices. I don't know how important the order is, but I was briefly running the latest leak with the MH1 baseband. Why others have had failures, I really don't know. I just gave it a go knowing I could ODIN back to MG8 (just did that).

I tried going back to 4.2.2 keeping the MH1 baseband then applying the OTA with the asserts commented out. I had signing failures even though I re-signed the zip.
[Galaxy S 4 General] SamuriHL:
I was wondering if dd'ing them would work. I was hoping the odin flash I made would do it but someone said "it didn't work". Of course I have no idea what didn't work. Did it not flash? Did it fail to update the baseband? Who knows. But the bin files are exactly what the ota update creates... Sha1 hashes and all.
[Galaxy S 4 General] qnet:
You won't see this until later but it worked, thanks.
[Galaxy S 4 General] ismaelmaia:
Problem in rom jamal aosp 4.3 final edition. Bug in copy in delete external storage sd card 64gb classe 10 sandisk. No copy e no delete.:silly:
[Galaxy S 4 General] Sammy4Life:
Stock 4.3 Recovery Linked

Probably already out there now, but here is one more.....https://mega.co.nz/#F!0NBhBLDR!VOjptSyeRZJ4cXdIHFsb1g

I used the following method: dd if=/dev/block/mmcblk0p22 of=/sdcard/recovery_4.3_stock_Sammy4Life.img bs=4096
[Galaxy S 4 General] ismaelmaia:
Bug sd card

any way to fix the problem in read-only to the sd card? It does not erase nor write, becomes read only. Any idea how to fix this problem?
[Galaxy S 4 General] qnet:
You may be able to find a better answer in the thread of who created your Rom. This thread is about the OTA and how to apply it to stock Roms.
[Galaxy S 4 General] ismaelmaia:
Okay, thank you and sorry for the wrong post ahahahah
[Galaxy S 4 General] ack154:
Does anyone have anymore suggestions on getting the OTA to actually install? It looks like the discussion has shifted to the potential FCs in the Settings (which is fine, since it's obviously a problem) but I'm still not getting the OTA from my device, nor will it install in my recovery (error 7, as seen elsewhere in this thread). I posted some more details a couple pages back (stock recovery, rooted, etc) and also what I've tried, but I'm still stuck with no update. :(

Was hoping maybe I missed a "solution" somewhere in all these pages, but didn't think so.
[Galaxy S 4 General] SamuriHL:
Post a screen shot of your about phone, please.
[Galaxy S 4 General] Sammy4Life:
If you are rooted with stock recovery only (no other modifications) then try putting the update package in your /cache folder. That seems to be the only partition accessible to the stock recovery.
[Galaxy S 4 General] SamuriHL:
I have the apply from external option in stock recovery and the first time I updated I did exactly that. You can throw it on the ext sdcard and it should find it.
[Galaxy S 4 General] taney:
I was able to update from MH8 (MFP) radio to MH1. From there, I restored my system partition with the soft brick tool on another thread via Heimdall. I forced OTA update by killing Google Framework Services; installed the update fine and re-rooted with CF-AutoRoot and updating binaries via Play Store. Everything works properly and I have root without wipe.

After update to MH1:

After OTA update to JWR66V:

My only downside is my TitaniumBackup is unable to write to my SD card in JWR66V. Can anyone confirm that as well?
[Galaxy S 4 General] SamuriHL:
Yes, it's a known issue with this build of 4.3. It can see the ext sdcard but it's not writeable.
[Galaxy S 4 General] taney:
Thanks for all your help! :D:good:
[Galaxy S 4 General] Sammy4Life:
Maybe a per app issue? I was able to use ES File Explorer to copy files from my /system/app directory to external SD card just fine (exFat 64GB).
[Galaxy S 4 General] SamuriHL:
There was a list of specific apps that this particular build had problems with. TiBU was on the list. As is HBO Go and a few others I use. That's why the Nexus devices got a new build pushed to them so quickly. I'm HOPING maybe we get one too.
[Galaxy S 4 General] taney:
Nice! I can't wait for that.
[Galaxy S 4 General] ack154:
Here you go.

Also, I am able to read my external card from recovery (it seems to read the zip OK that I can tell) but have not yet tried from /cache.
[Galaxy S 4 General] SamuriHL:
Stick it in /cache and allow it to try to update it automatically. Everything on that screenshot looks correct. I wish I knew what the error 7 you're getting says. It might help come up with a fix. You're SURE you have the proper 4.2.2 stock recovery on there?
[Galaxy S 4 General] ack154:
Here's the second part. Will try /cache.
[Galaxy S 4 General] SamuriHL:
Won't help. Where did you get your recovery img from? Cause, um, yea.....

---------- Post added at 03:27 PM ---------- Previous post was at 03:23 PM ----------

http://www.mediafire.com/download/30hi8i0eeuccx5h/stock_422_recovery.tar.md5

Please flash that and try again.
[Galaxy S 4 General] ack154:
From here: http://xdaforums.com/showthread.php?t=2360346

Though interestingly, here's a look back when I was questioning if I was back to a stock recovery... and it looked like this:

http://xdaforums.com/showpost.php?p=43630012&postcount=17

So I'm now starting to think when I used the CF-autoroot it replaced my recovery. Maybe? I've seen the stock recovery floating around this thread, I'll try flashing that when I get home and see if works...
[Galaxy S 4 General] SamuriHL:
CF-autoroot replaces recovery with a version for the I9505 and that's exactly why it's failing. How do I know this? I did the same damn thing and had the same damn problem. LMAO. :) Flash the odin package I just linked to and you'll be good to go no matter how you decide to install the update. Yey!
[Galaxy S 4 General] ack154:
And that's exactly what I had just started thinking. Thank you for the help. I'll report back later tonight with the results!
[Galaxy S 4 General] SamuriHL:
Awesome. Let us know if you have any more issues.
[Galaxy S 4 General] taney:
LOL! I encountered the same thing and ended up doing the same thing. :P
[Galaxy S 4 General] SamuriHL:
We all suck! :D LMAO!!
[Galaxy S 4 General] ack154:
Flashed stock recovery and tried to apply zip from external. At least got a different error now.

The only other thing that would be different is I added a line to build.prop to enable on screen buttons and modified the generic KB layout to turn off capacitive button.

Going to try reverting those to backups now and try flashing again.

(edit: originals did not help)
[Galaxy S 4 General] SamuriHL:
It's failing on an assert for SystemUI.apk. I'd flash the 4.2.2 system img from the 4.2.2 FULL image zip that's floating around. Should fix you up.
[Galaxy S 4 General] taney:
Do you think the leaked recovery is the same? Would it work? Just curious.
[Galaxy S 4 General] SamuriHL:
I haven't seen the leak at all, so I can't answer that. Got a sha1 off of it?
[Galaxy S 4 General] ack154:
Didn't want to lose data, but had sort of prepared for it.

Just flashed the system image. Went into recovery, cleared data/cache, and immediately applied update from zip. Went right through. It's booting back up now.

Thank you again. What a PITA.
[Galaxy S 4 General] SamuriHL:
I wouldn't have wiped the data personally. But I'm glad you're updating now. Sorry for the PITA process you had to go through.
[Galaxy S 4 General] ChaoticUnreality:
I'm trying to follow this to relock my boot loader and it doesn't do anything

This is what it says when I run the command

...

OKAY [ 0.003s]

finished. total time: 0.003s

but nothing happens on my phone.

I know it is connected cause I can do fastboot oem unlock and it brings up the option to unlock but it shows it as already unlocked. I just want the OTA update for 4.3
[Galaxy S 4 General] tublah:
I was able to take the OTA and never relocked my bootloader.
[Galaxy S 4 General] warwolfx0:
FYI force update breaks stuff

This had issues

connect to your wifi

System setting / apps / all / Google Application Framework

click on all 3

Force stop / clear data / clear cache

system setting / about phone / system updates

click on

check now

found new update

you may need to repeat theses steps

I have TWRP and rooted, and unlocked bootloader

I rebooted after the update

Google play dose not allow me to install or update apps anymore and i am still on 4.2.2 (wipe fixes this)

UPDATE:

ok i flashed the stock recovery back from the dump that i made and the update worked

i had to reroot and i update my "[HOWTO] Root Stock i9505G (Google edition)" to make it work

FYI I NEVER INSTALLED THE LEAKED COPY
[Galaxy S 4 General] bleez99:
I have a fix. I did a little research and found that you can edit /etc/permissions/platform.xml and add a group to WRITE_EXTERNAL_STORAGE

Original:

<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >

<group gid="sdcard_rw" />

</permission>

Add the media_rw group:

<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >

<group gid="sdcard_rw" />

<group gid="media_rw" />

</permission>

Done. Doing a TiBU right now to my external card.

This _may_ fix other apps that have issues writing to the card, I personally didn't find any.

Suggest that you do an adb pull of the file for safekeeping before doing this.

If you pull the file, edit it, and push it back make sure the permissions are set to 644.

Thanks to everyone who made this "OTA" happen.

I was able to do a no wipe update to MH1 :)
[Galaxy S 4 General] taney:
THANK YOU!! That works wonders! =)

I'M LOVING JWR66V! Even the camera is better. My only wish/hope is for us to store pictures on external SD card. :D

---------- Post added at 10:54 PM ---------- Previous post was at 10:53 PM ----------

I can get one when I'm on my home mac.
[Galaxy S 4 General] mrvirginia:
[MENTION=3332811]faux123[/MENTION] when you get a chance, would it be possible for you to add exfat support back into the stock kernel as well?

i believe it needs to be added to init.rc

# ko files for exfat
insmod /system/lib/modules/exfat_core.ko
insmod /system/lib/modules/exfat_fs.ko

i haven't taken the kernel apart just yet so that was a stab in the dark. thank you!
[Galaxy S 4 General] ReivITA:
For Rom 4.3 Jamal?
[Galaxy S 4 General] faux123:
there are no source for exfat cores.. I can do a hack to get them back for stock... can you post the screenshoot of a 100% stock kernel's version strings. I will need to hack the compiled kernel to match the version strings of the real stock, then you can load the exfat BINARY ONLY modules!

Oh btw, I've unsubscribed from this thread, so use the [MENTION=3332811]faux123[/MENTION] to notify me.