[ROM][AOSP] S4 Google Edition [SafeStrap]

Hi all,

After discovering the terrible mistake I made buying an AT&T S4 with a non-unlockable bootloader, I looked for any way to run an AOSP/GPE rom on this phone with Safestrap. It looks like I've finally gotten it into a decent state for my personal use so I thought I'd share.

The ROM is based on [AOSP] Official 4.4.3 - S4 Google Edition - Final-R2.0 and nearly all of the credit goes to them for making a GPE rom that actually boots with our kernel. The only changes I've made are ripping out the kernel for safestrap, installing a wrapper script for the sdcard binary, and some post_boot init script additions to properly load the WiFi module. For wifi to work, you need your stock kernel's modules installed after the ROM, specifically dhd.ko, to /system/lib/modules.

If you'd like to enable Nexus-style software buttons and disable the hardware capacitive buttons, see this thread for instructions: http://xdaforums.com/showthread.php?t=2032117. You can disable the capacitive button lights with GravityBox.

Warning:
Do NOT take OTA updates with this rom. Doing so could break the rom, or in the worst case trip Knox, which would void your warranty. I'll do my best to update the rom to the latest version as soon as possible.

What works:
Internal/external storage
WiFi (may not come up every boot, a soft reboot usually fixes)
USB debugging
USB internet tethering
Paid apps from Play Store (see workaround below)
Chrome (see workaround below)
Google Earth (remove from /system/app and reinstall from Play store)
IPv6 APN (for compatible carriers such as T-Mobile)
Almost everything else

In progress:
WiFi Tethering (see: http://xdaforums.com/showpost.php?p=54878857&postcount=662)

What doesn't work:
USB MTP (due to kernel differences)

AT&T Install Instructions:
http://xdaforums.com/showthread.php?p=53758259

Verizon Install Instructions:
http://xdaforums.com/galaxy-s4-verizon/general/how-to-install-aosp-s4-google-edition-t2817708

Download:
4.4.3: https://drive.google.com/file/d/0ByCYkZozShp_bXFTdnpYSmxyZHM
4.4.3: https://www.dropbox.com/s/v59aak1j3fz1z35/gpe_443_safestrap.zip?dl=0 (Mirror)

Update:
4.4.4: https://drive.google.com/file/d/0ByCYkZozShp_bE02ZlJRQkgxTWM (requires 4.4.3)
4.4.4: https://www.dropbox.com/s/z57whcu44ypcx93/gpe_444_update.zip?dl=0 (Mirror)

Lollipop/5.0:
The 5.0.0 OTA for the real S4 GPE came out today, so I tried adapting it like the 4.4.4 update. Unfortunately and not surprisingly, it failed to boot. This probably means we need to wait for AT&T's 5.0 TW update to get a compatible kernel to make 5.0 GPE work

FAQ:
WiFi isn't working: Do a soft reset with the GravityBox Power Menu or the Xposed Installer.

USB Transfer not working: Use Airdroid, FTPServer, or adb push/pull.

Paid apps won't install: See workaround below.

Chrome force closes on new tab: See workaround below.

Paid Apps & Chrome Workaround:
Install SELinux Mode Changer and set SELinux to permissive.

JeeperDon said:

The 'multi-step to normal' boot process is probably ok. The thing that I prefer not to live with (too much pain) is not having USB file xfer. That's a deal breaker for me, and there is no talk of anyone trying to fix this since the rom came out 6 weeks ago.

Click to expand...

Click to collapse

You can get around the multi-boot process by turning off wifi or putting the phone into airplane mode before shutting down or rebooting.

AOSP/GPE roms (like this one) and TW roms use a completely different device exposed by the kernel for usb transfer. This would be a quick fix if we could replace the kernel, but we can't. My attempts at getting samsung binaries to be a shim or symlinking kernel devices hasn't panned out.

JeeperDon said:

So this is the end of the road then? No one interested in trying to fix any of the issues/bugs/broken things and make this a clean load? Everyone here seems content with the pain.

Click to expand...

Click to collapse

The remaining issues are not showstoppers for me personally. I've tried fixing them, but these last few issues are tricky to fix. Yes the issues are annoying, but it's better than using TW. There's only so much you can do with a locked kernel not designed for GPE.

JeeperDon said:

You're missing the point. In most other ROMS, there may be a 'Known Issues:' list on day-one, but the devs or others dig into the list over time to get the list to zero. Not happening here, no squeak (from any one other than me apparently), so no oil... everyone may be happy to just keep using the patches, I'm just saying it's unusual for an XDA rom.

Click to expand...

Click to collapse

This is not most other ROMs. This is using a rom on a kernel that it wasn't meant to be used with, it's mostly a hack job. If you want a quick fix, get a phone with an unlocked bootloader, or use a touchwiz rom that the kernel was designed for. You're also welcome to take a look at the rom yourself and see if you can fix the remaining issues.

Last night I made some progress on wifi tethering. I now know the commands to make it work, but I haven't figured out an easy way to implement the fix for everyone yet.

1. Toggle Wifi off.

2.
3. Toggle Wifi AP on; it should now be broadcasting properly.

4. When done, toggle Wifi AP off.

5.
6. Toggle Wifi on.

I don't know when the samsung gpe lollipop release will ship. As soon as the official gpe s4 build shows up from Samsung, then I'll look into making it work with safestrap.

jmsq said:

Last night I made some progress on wifi tethering. I now know the commands to make it work, but I haven't figured out an easy way to implement the fix for everyone yet.

1. Toggle Wifi off.

2.

Code:

# rmmod dhd; insmod /system/lib/modules/dhd.ko "firmware_path=/system/etc/wifi/bcmdhd_apsta.bin nvram_path=/system/etc/wifi/nvram_net.txt"

3. Toggle Wifi AP on; it should now be broadcasting properly.

4. When done, toggle Wifi AP off.

5.

Code:

# rmmod dhd; insmod /system/lib/modules/dhd.ko "firmware_path=/system/etc/wifi/bcmdhd_sta.bin nvram_path=/system/etc/wifi/nvram_net.txt"

6. Toggle Wifi on.

Click to expand...

Click to collapse

DeadlySin9 said:

Thanks, confirmed working on my phone and it will be useful. I created a one line file for each command and pushed them to /system/bin for ease, but I don't know how you'd get it to run when AP is toggled.

Click to expand...

Click to collapse

This is the same way I would toggle hotspot on and off when we had to downgrade to mk2 on vzw s4. An easy way to implement this for people would be to create a new toggle that calls that intent action. Or using/editing an apk to do this. Although deadlysin's method of having the files in system/bin shouldn't be tough for people to do.

Another idea is it to create a conditional if then statement based script to determine when to turn off/on WiFi AP etc. I just wrote a rough idea of this in the form of a script. You can probably expand on this to accomplish what you are wanting to do.

#!/system/bin/sh

if [ ! -z "$(cat /proc/modules | grep 'dhd*')" ]; then
echo "WiFi/AP already on"
else
insmod /system/lib/modules/dhd.ko
fi

Click to expand...

Click to collapse

Or I guess maybe in this particular case

#!/system/bin/sh

if [ ! -z "$(cat /proc/modules | grep 'dhd*')" ]; then
echo "WiFi/AP already on"
else
insmod /system/lib/modules/dhd.ko "firmware_path=/system/etc/wifi/bcmdhd_sta.bin nvram_path=/system/etc/wifi/nvram_net.txt"
fi

Click to expand...

Click to collapse