yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S 4 Original Android Develop] aburns7487:
v 3.3 I had bootloop...FreeGS4 v 2.0 MF9...I reflashed v. 3.0

USMC OIF Veteran

Semper Fidelis

Boston Strong!!!
[Sprint Samsung Galaxy S 4 Original Android Develop] Highway 55:
Might be a stupid question but...

For those of you having problems, did you upgrade firmware and modem to MF9 before installing this? The reason I ask is I have 1 person that tried to install my ROM (which comes with this kernel) but it won't boot. But says that stock MF9 with stock kernel boots fine. He hasn't replied back as to whether he did the full upgrade yet.
[Sprint Samsung Galaxy S 4 Original Android Develop] agat63:
Kernel should work fine with both MDL and MF9.

So those upgrades to new firmware should not matter.

I have tried the kernel on both. Full MDL and full MF9.
[Sprint Samsung Galaxy S 4 Original Android Develop] Highway 55:
Ok, just making sure. I am running it right now with zero issues, and 34 others have dowloaded it without issues. Might have to chalk this one up to a bad download or device issues. ..
[Sprint Samsung Galaxy S 4 Original Android Develop] aburns7487:
I had done just the modem/ Firmware update to mf9. Previous to adding v3.3
[Sprint Samsung Galaxy S 4 Original Android Develop] PiggySmalls:
Downloading now agat, I'm on Mf9 modem and MdL rom. Will let you know, but if this thing runs like 3.2 did, I'm about to be a happy dude.

Sent from my SPH-L720 using Xparent BlueTapatalk 2
[Sprint Samsung Galaxy S 4 Original Android Develop] shizkoff777:
That doesnt help nothing.Need more info like a logcat

Agat.batteries great on sacs v2 and3.3.No hiccups so fat
[Sprint Samsung Galaxy S 4 Original Android Develop] agat63:
Did full MDL restore from thread I posted previously.

Stock MDL kernel, recovery.

Flashed noobl's full MF9 restore over it.

Flashed TWRP recovery compiled by me.

Flashed my 0.3.1 kernel ( had it on sd card).

Boot to system.

Boot to recovery

Flashed crawj's deodexed MF9 rom (no data wipe).

Boot to system.

Boot to recovery and flashed v0.3.3 kernel.

Boot to system.

No reboots, no bootloops, no hick ups....

So I duplicated your steps and everything is good here.

Running crawj's MF9 deodexed rom with my v0.3.3 kernel.

Let me know if I can help you with anything else.
[Sprint Samsung Galaxy S 4 Original Android Develop] devoureddreams:
This kernel doesnt mix well with sacs v2 rom also had a issue with it constantly rebooting.
[Sprint Samsung Galaxy S 4 Original Android Develop] dschachm:
It's the ROM, not the kernel.
[Sprint Samsung Galaxy S 4 Original Android Develop] shizkoff777:
The hell it doesnt.No im playing.Its running perfect for me and thats what im using
[Sprint Samsung Galaxy S 4 Original Android Develop] devoureddreams:
Weird I couldn't get it to boot. May not like me tho.
[Sprint Samsung Galaxy S 4 Original Android Develop] shizkoff777:
Dont feel bad v .31 wouldnt boot for me on any rom
[Sprint Samsung Galaxy S 4 Original Android Develop] deltawye:
I couldn't get it to boot as well
[Sprint Samsung Galaxy S 4 Original Android Develop] liquid307:
Sup, 1st time user of this kernel, same results for me...fruitloops on v.0.3.3 running stock rooted mf9 no mods.

These kernels seem to work on mf9.

Ktoonsez 7/11 working but didn't like battery life, even undervolted & not overclocked, just noticed he posted new one 7/15 will have to test.

Faux123 working testing now and of course stock mf9 kernel.

Sent from The Twilight Zone
[Sprint Samsung Galaxy S 4 Original Android Develop] fgr:
I have a 64gb Sandisk, formatted exFat. Got the safe to remove message after flashing 0.3.3.

Re-downloaded and tried again, same thing.

Flashed back to stock MF9 kernel and all is well again...

I'm mostly stock MF9 rom, just some cosmetic mods of my own...

Anybody else have this problem?
[Sprint Samsung Galaxy S 4 Original Android Develop] shizkoff777:
I wonder if samsung didnt hide something in the code to make it not work in some different scenarios. Are all you guys on updated firmware
[Sprint Samsung Galaxy S 4 Original Android Develop] fgr:
Guess I should have mentioned that also.

Everything

is MF9 in my situation.
[Sprint Samsung Galaxy S 4 Original Android Develop] guitardoc64:
3.3 has been very good for me. I've flashed it twice so far. Once on my update to MF9 and today after having to redo everything because I dirty flashed. On Crawrj rooted stock odex and it's smooth as butter.
[Sprint Samsung Galaxy S 4 Original Android Develop] agat63:
I don't have 64GB card but I did run test on my 32GB card.

I moved everything to my pc and formatted card to ExFat.

Got safe to remove sd card message.

Reboot the phone and card was got mounted.

The problem with ExFat is that we don't have MS binaries and we using mount.exfat-fuse as workaround.

That means that card won't be automatically mounted ones inserted into slot like it happens with vfat formatted card.

Kernel includes a script that checks the card filesystem and if it's exfat it will run mount script.

But script runs only on boot.

So if you put exfat formatted card into slot wile phone is running you will have to restart the phone to mount sd card.

Hope this helps.
[Sprint Samsung Galaxy S 4 Original Android Develop] fgr:
I tried rebooting, and then complete power off after both downloads... Still a no go.

Before the MF9 update, I was running FreeGS rom with your kernel and the same card... No problems... Strange...

Anybody else with a 64gb exFat formatted card out there that can test?
[Sprint Samsung Galaxy S 4 Original Android Develop] agat63:
ExFat support is in the ramdisk and it's same in all kernels.

There are pretty much no changes and/or edits to it. So if it used to work it should work now.

I'm on MF9 as well and my 32 GB exfat formatted card worked just fine. :confused:
[Sprint Samsung Galaxy S 4 Original Android Develop] fgr:
I'm tired and have had a few drinks now :silly: (I installed the kernel earlier in the day, by the way... lol)

I did not format the card after installing the kernel. Tomorrow I'll move everything off of it and try reformatting and such to see if that makes any difference.
[Sprint Samsung Galaxy S 4 Original Android Develop] Grommish:
Agat, I've not been able to test 0.3.3 yet, but hopefully sometime today.
[Sprint Samsung Galaxy S 4 Original Android Develop] fgr:
Still a no-go on my 64gb exFat Sandisk card.

Today I pulled it from the phone, and formatted fat32 using my desktop.

Installed in phone and powered on. All good...

Using the phone, I formatted the card. Once formatted all I got was the safe to remove message.

Repeated the above using the desktop to format the card exFat. Put back in phone and powered on, still a no-go.

Restored stock MF9 kernel and it works fine.

Stock kernel isn't too bad, so I'll have to stick with it for now. No biggie.
[Sprint Samsung Galaxy S 4 Original Android Develop] optimummind:
On v0.3.3, my Samsung 64GB microSD exFat worked fine for me.
[Sprint Samsung Galaxy S 4 Original Android Develop] agat63:
Stock kernel is using proprietary MS exfat modules. We don't have source for them so we can't compile new ones for custom kernel.

But card size should not matter. Kernel either supports exfat or it doesn't and if it works for my 32 GB card it should work for 64 GB as well.

And I did format card using my phone too.

After formatting it got same message "SD card is safe to remove".

I just rebooted my phone and card was mounted.

Did copy few file to it just to make sure it works.

Did that process 3 times.

And you don't need to pull the card from your phone to format it.

If you use "Format SD card" option under menu->settings->storage your card will be formatted to vfat. That's default setting in the phone.

After that you can format it to exfat again by running mkfs or mkexfatfs to /dev/block/mmcblk1p1.

So your card doesn't have to be pulled from the phone at all.
[Sprint Samsung Galaxy S 4 Original Android Develop] agat63:
Is it exfat formatted?

You can pull post-init.log from phone and take a look.

Post-init.log is located at /data/.agat folder.

If you have adb you can do following:

1. Connect your phone to PC.

2. adb shell

3. su

4. cp /data/.agat/post-init.log /sdcard/post-init.log

5. exit

6. exit

7. adb pull /sdcard/post-init.log

The post-init.log file will be in the same folder where you opened your terminal or cmd.

You can open it with any text editor and see the log.
[Sprint Samsung Galaxy S 4 Original Android Develop] fgr:
Took a look at my log, looks to me like it's finding the card :confused:

Fri Mar 20 22:27:03 UTC 1970

Superuser already exists

Running Post-Init Script

Setting Min/Max freq to core 0

CPU 1 already online, setting Min/Max Freq

CPU 2 already online, setting Min/Max Freq

CPU 3 already online, setting Min/Max Freq

ExFat-Debug: SD-Card is type: UUID=10EF-3A03

FRANDOM: found frandom Kernelmodule, loading...

Post-init finished ...

Does this look right?
[Sprint Samsung Galaxy S 4 Original Android Develop] agat63:
everything looks right except ExFat-Debug pert.

If you card is formatted ExFat it should say

SD-Card is type ExFat and than should mount it.

Edit: Yesterday I did order a 64GB card. I'll run more tests ones I get it. I don't think the size should/will matter but I bought the card just to make/be sure.
[Sprint Samsung Galaxy S 4 Original Android Develop] daniel4653:
Agat your 3.3 kernel is working great on GE 4.2.2 ROM port :)
[Sprint Samsung Galaxy S 4 Original Android Develop] fgr:
I always reboot twice just to make sure. I'll wait to see what happens with your 64gig when you get it.

I play with my phone ALOT, who knows what seemingly simple mod somewhere else could effect this. Not important enough for me to do a clean install at this point. That will probably happen when Clark44 releases his rom. Will your kernel be incorporated (I hope).
[Sprint Samsung Galaxy S 4 Original Android Develop] agat63:
So far Clark44 asked me to make a kernel specific to his rom and I made one for him (twice).

I used to run his rom on my GS3 a lot and I like his work so I'll support him when ever I can.

Thus far he didn't ask me to make one for new release but he might ask later.

We will see.
[Sprint Samsung Galaxy S 4 Original Android Develop] fgr:
Sounds good, please let me know what happens with you 64gig.
[Sprint Samsung Galaxy S 4 Original Android Develop] optimummind:
Yes, it is. Here is a copy and paste from that log file:

Superuser already exists

Running Post-Init Script

Setting Min/Max freq to core 0

CPU 1 already online, setting Min/Max Freq

CPU 2 already online, setting Min/Max Freq

CPU 3 already online, setting Min/Max Freq

ExFat-Debug: SD-Card is type ExFAT

ExFat-Debug: trying to mount via fuse

FUSE exfat 1.0.1

WARN: volume was not unmounted cleanly.

FRANDOM: found frandom Kernelmodule, loading...

Post-init finished ...
[Sprint Samsung Galaxy S 4 Original Android Develop] agat63:
That how it suppose to be.

Script has checked sd card filesystem.

Recognized ExFat.

and mounted it.

I'm not sure why you have the warning but your SD card should work.
[Sprint Samsung Galaxy S 4 Original Android Develop] fgr:
He's got the same card, and it's working, so it must be on my end.

Can you think of anything that might prevent it from mounting? We know it's not the card itself, works fine with stock kernel.

I had "USB Mass Storage" installed. Uninstalled it and tried everything again, no difference. I did have this installed before the MF9 upgrade and everything was fine.

That's the only thing I can think of that would cause a problem.

[MENTION=4693652]optimummind[/MENTION], are you fully MF9 upgraded?
[Sprint Samsung Galaxy S 4 Original Android Develop] agat63:
Unfortunately I can't help you with anything else until I get my 64GB card.

Ones I have I can try different scenarios and may be after that will be able offer some advice.

Sorry.
[Sprint Samsung Galaxy S 4 Original Android Develop] optimummind:
Yes, despite that warning, my card works well and there are no problems transferring files.

[MENTION=863124]fgr[/MENTION]. Yes, I'm fully MF9. I got there by Odin'ing to stock MDC using tar, then flashing the MF9 update zip from within stock recovery.

After that, I began to mod my phone from there. First was TWRP, then SuperSU, then the kernels (I've tried both agat's and the ktoonsez). I'm currently on ktoonsez but I was on agat's yesterday.
[Sprint Samsung Galaxy S 4 Original Android Develop] youngpro83:
I can't even get this kernel to boot. It keeps boot looping the Samsung logo.

Stock rooted. Deodexed. No tweaks. Except hotspot mod, 4 in 1 reboot, and custom boot animation. I thoight it was the custom boot animation but I tried flashing without it and still no go.
[Sprint Samsung Galaxy S 4 Original Android Develop] agat63:
4 in 1 reboot menu has edits to framework and services.jar.

That's the only thing I can think of that might create problem.

Try clean stock rom, flash kernel see if it helps.
[Sprint Samsung Galaxy S 4 Original Android Develop] pdoroba:
Been running great here. MF9 stock odexed, hotspot, 4 in 1, call recorder, agat's latest kernel, with my sandisk 64gb formatted exfat.
[Sprint Samsung Galaxy S 4 Original Android Develop] xchampx13:
I just tried flashing the 3.3 update but it gave me a boot loop. On stock MF9 no mods installed

Sent from my SPH-L720
[Sprint Samsung Galaxy S 4 Original Android Develop] agat63:
Would you please describe how did you flash/install MF9 and how did you flash kernel.

I can't understand why the kernel works for some and doesn't work for others.
[Sprint Samsung Galaxy S 4 Original Android Develop] devoureddreams:
Im on stock deodexed mf9. I did the tar mf9 upgrade through odin and flashed the deodexed rom in twrp and kernel will not boot
[Sprint Samsung Galaxy S 4 Original Android Develop] xchampx13:
I used noobnl's modem update guide to get to MF9, I flashed the kernel using twrp.
[Sprint Samsung Galaxy S 4 Original Android Develop] fgr:
Quick update on my 64gb exFat sdcard issues.

After flashing back to stock MF9 kernel last night, I discovered my wifi not working, and sdcard fine. Very weird for stock kernel.

Flashed your kernel again. Wifi works, sdcard doesn't !!! WTF?????

Note when I say flashed, I mean several tries with reboots/power offs/clearing cache and dalvik in between.

Ok then. I'm doing lots of mods to the launcher and other things, so I've pulled/edited/pushed/flashed my SystemUI/framework-res/SecLauncher3/SecSettings and a few others many, many times. Problems are starting, time for a clean install.

Used noobnl's tar to reflash all the firmware. Wiped

everything

a few times with twrp. Installed stock MF9 rom/kernel from crawrj's thread. Everything works.

Install your kernel, no sdcard :( I'm still clueless since it worked when I was running FreeGS.

Note that I also note that I flashed KT's kernel and got the same results, so I'm pretty sure the problem is on my end. Either something has gotten "funky" with my phones hardware, or even possibly the sdcard. Stranger things have happened...
[Sprint Samsung Galaxy S 4 Original Android Develop] daniel4653:
8 hours on v3.3 on Sacs custom ROM v2 which is based on mf9 and it installed and booted without a hitch.
[Sprint Samsung Galaxy S 4 Original Android Develop] agat63:
I'm pretty much lost here.

I did install MF9 2 different ways and kernel worked for me both times.

1. Flash full stock MDL and apply update zip from stock recovery.

2. Flash full stock MDL and then flash noobl's update tar. After that installed custom recovery and flashed kernel from recovery. Tried with crawj's ODEXED and DEODEXED roms. No problems.

According to all reports both procedures work for some and don't work for others.

We still can't find a common denominator for all who have problems and bootloops.

Without figuring out what all users with problems have in common (mods, tweaks, scripts, hardware version etc.) I thing there is not too much I can do.

I'm out of ideas and open to any suggestion and/or tests we can run to try to narrow the problem and find fix for it.
[Sprint Samsung Galaxy S 4 Original Android Develop] devoureddreams:
Is there a way to read what's going on during the initial boot after flash to see what's being blocked from allowing boot.
[Sprint Samsung Galaxy S 4 Original Android Develop] Grommish:
So I loaded 0.3.3. Lasted an hour or so without issue. Then I disconnected Bluetooth and reconnected it. Hot reboot city :c (.. Back to 0.3.0.
[Sprint Samsung Galaxy S 4 Original Android Develop] daniel4653:
Don't stress yourself out too much Agat. Looks like its on the users side not your kernel.
[Sprint Samsung Galaxy S 4 Original Android Develop] devoureddreams:
Please explain to me how it can be user side when every other kernel boots just fine but not this one?
[Sprint Samsung Galaxy S 4 Original Android Develop] agat63:
I'll have to agree with the question.

I do understand that not every one has problems with boot but we can't dismiss the problem completely.

Even if we agree that couple of problems can be related to some tweaks or mods installed by user that they forgot about we can't

say with certainty that all of them have same mods present.

Thus kernel should be at least part of the problem.

I never uploaded a kernel that I didn't flash/run on my phone first and I never had problems with any of them.

But I don't have any bluetooth devices thus I never tested kernel for connectivity with it and/or any problems that might be present with bluetooth.

I guess I'll have to buy a bluetooth device as I bought (ordered) a 64 GB sd card to test it on my phone as well.

May be I'll be able to figure out something if I can replicate the problem myself.

As for another question asked before about some logs to see what happens.

If phone is bootlooping on splash screen that means kernel is not loading and without kernel there is no way to pull logcat or kmsg or dmsg or anything else.... :(
[Sprint Samsung Galaxy S 4 Original Android Develop] fgr:
I'm not to sure that it is mods any more either... Mine didn't work

completely

stock, fresh wipe and install (of MF9).

Restored one of my old nandroids while running FreeGS, and it worked fine, so I don't think its card or hardware related. Here are screenshots of working and not working setups if it is of any help.

Notice both are MF9 updated. The freeGS backup was on MDL at the time it was made, and I didn't want to try and downgrade firmware to test it. It's probably a good thing, it shows it probably not the MF9 firmware causing the problem.
[Sprint Samsung Galaxy S 4 Original Android Develop] agat63:
The only difference I can see (except kernel) is the rom.

FreeGS 2.0 is MDL based according to Clark44's changelog.

"FreeGS4 v2.0.0 Changelog:

-New exclusive Agat-FreeGS4 kernel is now included!

~Based on latest MDL source"

I'm not saying that's the reason why sd card works on his rom just making sure we are on same page here.
[Sprint Samsung Galaxy S 4 Original Android Develop] devoureddreams:
Thanks agat I've used your kernel before and never had a problem but .3.3 just will not boot I even started fresh. Its extremely wierd. I'm not complaining at all I just really like your kernel due to battery savings it does. :(
[Sprint Samsung Galaxy S 4 Original Android Develop] xchampx13:
I just can't get this 0.3.3 to install either. would definitely be willing to help test any other versions when you do updates. Thanks for all your work on this though! Been using your kernel for awhile.
[Sprint Samsung Galaxy S 4 Original Android Develop] agat63:
I just got an idea.

So far it looks like v0.3.0 is running for all and no one had problems with it.

I'll extract the ramdisk from it and make new kernel with source I have now but with that ramdisk.

If problems persist we will know that what ever problems we have are kernel source related.

If problems will be gone it will narrow down to ramdisk edits I made and we might be able to fix them.

I'll do it tonight when I get home from work.

Hopefully this will help.
[Sprint Samsung Galaxy S 4 Original Android Develop] guitardoc64:
That sounds like a good plan. I offer my services testing bluetooth if needed as I have one I use every day.
[Sprint Samsung Galaxy S 4 Original Android Develop] devoureddreams:
Defiantly here to test for any boot issues as if say if it fixes mine it should fix everyone else's as well.
[Sprint Samsung Galaxy S 4 Original Android Develop] agat63:
Ones I have kernel ready I'll pm you guys.

Thanks for offer and thanks for help.
[Sprint Samsung Galaxy S 4 Original Android Develop] fgr:
I think we're on the same page, my point being that something in the MF9 roms is playing nicely with your kernel for some reason (for only some of us).

I'm not to worried, whatever the problem is, it will get figured out :good:. The people who can't boot up should be your main concern...:p
[Sprint Samsung Galaxy S 4 Original Android Develop] DarkEye45:
I'm also getting boot loops with 0.3.3. I'm still running stock rooted ROM MDL. I've been running 0.3.0 with no problems for weeks now.

I also tried 0.3.1 and it boot looped.

I'm willing to try this new version you make tonight so PM me if you want me to test it agat.
[Sprint Samsung Galaxy S 4 Original Android Develop] PiggySmalls:
Agat, I haven't had boot issues, but I did have the blue tooth issue. I haven't had time to really mess with it this week, but this weekend, I'd be willing to flash to full stock mf9, add your kernel, and start adding mods and flashing roms one at a time to see if we can narrow this down more. Just let me know man, looking forward to being back on your kernel.

Sent from my SPH-L720 using Xparent BlueTapatalk 2
[Sprint Samsung Galaxy S 4 Original Android Develop] daniel4653:
[MENTION=1528277]agat[/MENTION] because you have tried to recreate two different ways of people not being able to install your kernel. I only once wasnt able to get 3.0 version of the kernel to boot and it was my fault. Ever since I havent ran into a single boot loop with your kernel.
[Sprint Samsung Galaxy S 4 Original Android Develop] fgr:
[MENTION=2953465]agat63[/MENTION], If you think this would have any effect on my sdcard issue, I'd be happy to test also.
[Sprint Samsung Galaxy S 4 Original Android Develop] Mahapederdon:
I had a bootloop with 3.3 running kuban with normal boot setting on kernel. Running mf9 bootloader and modem. It started bootloop while I was in the play store. It seemed like a quick reboot too. It went strait to the boot logo and then booted then rebooted again. It gave me like 10 seconds of run time before it rebooted again. Hope this helps. I don't have a log cat cause I just booted into recovery and installed a different kernel.
[Sprint Samsung Galaxy S 4 Original Android Develop] Grommish:
The hot reboot is what I get with Bluetooth under 0.3.1+. He'll figure it out but when it starts hot rebooting you can corrupt data and hose the entire thing.
[Sprint Samsung Galaxy S 4 Original Android Develop] DarkEye45:
I downloaded 0.3.4 (that agat PM'ed me the link) and then rebooted my SG4 into CWM recovery.

I then cleared caches and installed AGAT_GS4_v0.3.4.zip.

I then rebooted from recovery.

It booted to the Samsung logo and then went into a boot loop.

I went back into recovery (held down the volume up key to get there) and installed v0.3.0 again and phone boots fine and is working again.

I'm still on MDL stock ROM with rooted. I do have a 64GB SD Card installed.
[Sprint Samsung Galaxy S 4 Original Android Develop] Grommish:
Just as a quick note. 0.3.4 test has bt issue. I'm going to live log here in a bit
[Sprint Samsung Galaxy S 4 Original Android Develop] PiggySmalls:
Agat, 3.4 is running great so far. No bootloops, no bt issues. Running full stock mf9. I will let you know if anything goes wrong. Do you have any suggestions as to something to flash or do that you suspect might be causing the issues?

Sent from my SPH-L720 using Xparent BlueTapatalk 2
[Sprint Samsung Galaxy S 4 Original Android Develop] agat63:
Since I never had any of the problems I don't have any suggestions.

May one of the users that what problems/reboots/bootloops can tell what you should try....