[ROM][4.3.1][December 3] Slim Bean jfltetmo [stable 2.2]

[blk_jack]

Disclaimer: We are not responsible for any damages on your device.

Original Slim Features:

1. The Real Dark Slim
2. Notification drawer & lockscreen Shortcuts
3. SlimPIE
4. Customizable NavBar
5. QuickSettings custom Shortcuts
6. Full hardware key rebinding!
7. SlimCenter
8. ..and much more!

Need to find a feature? Want to see screenshots? Check out SlimBean's features!

Changelog
Find our latest Changelog go here

Chat with the slim team and other slim users

• IRC: #slimusers @ freenode
• New to IRC? Don't have a native app? Try the Freenode web client [link] or the Firefox extension Chatzilla [link]
• Google+ [link]
• Twitter [link]
• Facebook [Link]

Installation instructions
For Most Users
Please keep in mind if a special instruction is needed it will be noted in the Changelog

• Download the latest build from [here]
• Gapps ( if you don't have it already) from [here]
• !Recommended! Full wipe, and manual format /system
• Flash ROM and the gapps you want, reboot

FAQ
Check out out FAQ before posting! Keeps more common questions answered in one place!

To get root working go to Settings/Developer options/
Then change the option "root access" to "apps and adb".


Help us out!
If you want to help us by translating slim to your language check out Crowdin.net and submite your translations.
Or consider a donation.

Thanks!
You can find the full list of credits here

Source
Please visit here for the rom source code.
Kernel source can be found here

XDA:DevDB Information
Slim Bean jfltetmo [stable 2.2], a ROM for the T-Mobile Samsung Galaxy S 4

Contributors
blk_jack
ROM OS Version: 4.3.x Jellybean
ROM Kernel: Linux 3.4.x
Based On: AOSP

Version Information
Status: Stable
Current Stable Version: 2.2
Stable Release Date: 2013-12-03

Created 2013-08-18
Last Updated 2013-12-08

 

[blk_jack]

SlimBean 4.3 stable 2.2

Stable 2.2 is live! Please read the Changelog for more details including proper upgrade/installation methods, as well as notes on activating root and restoring with Titanium Backup.

Changes, Features & Fixes:

Changelog for stable 2.2

• SuperUser security fixes
• Several BT fixes
• Selinux security ehancements
• LID control fix
• some translation upstrem
• nearly all device got device and kernel updates

 

[blk_jack]

Please note these builds are under heavy development!

Known issues

• Headset in-call mic uses phone
• HDR Camera mode may need improvements, but should at least work

4.3 mini-FAQ

• Q) I'm stuck at the boot logo and/or a boot loop!
• A) Make sure you use TWRP 2.5.0.2. TWRP 2.6 and other recoveries can cause boot loops & hangups

• Q) Root doesn't work!
• A) From a clean build you need to enable root access for Superuser itself. This is different from 4.2.2 in which Superuser by default had root access on a new install. To do this, go to Settings -> Developer options -> Root access. If an app attempts to request root access before Superuser itself has access, it may cause problems with that app in the future where root requests are silently denied.

• Q) Titanium Backup isn't restoring apps!
• A) Change the backups folder to storage/emulated/legacy.

If you use Philz recovery 5.10.0 you must upgrade to 5.11.0 or you will lose radio!

Since the SGS4 is so new, development is happening very rapidly. This should be taken into consideration when flashing any 4.3 AOSP-based builds on the device. Known issues will be listed here.

 

[quickquest88]

I can't seem to get past the bootloop. rebooting repeatedly doesn't seem to do anything. if I go back to recovery, it won't even let me wipe. can't mount data. I have to go back and factory reset, then reboot into recovery to get wiping to work again. then I can get back to the o.s.

 

[blk_jack]

I can't seem to get past the bootloop. rebooting repeatedly doesn't seem to do anything. if I go back to recovery, it won't even let me wipe. can't mount data. I have to go back and factory reset, then reboot into recovery to get wiping to work again. then I can get back to the o.s.

Something is definitely wrong on your end. You're gonna have to give me more info, like your recovery and what steps you did to install the ROM.

If it's stuck at the boot logo, try wiping dalvik cache.

Sent from my SGH-I337M using Tapatalk 4

 

[quickquest88]

I guess wasn't as clear as I thought. i can get the system to boot once, but trying a reboot, it will bootloop.

I'm using the latest twrp, wipe everything but extsd, format system, install 4.3 and 4.3 gapps. I can get it to boot and everything looks good from there. however, if I reboot, it gets stuck in the bootloop. pulling battery or long press power to turn off and boot again doesn't help. I can get to recovery, but if I try to wipe cache and dalvik, it says something about cant mount /data and says it failed. then I have to go back to format system. after I do that, the text on screen says I may have to reboot recovery to access /data. then I can get it to boot again. of course I have to reinstall all of my apps again.

if I do anything that requires a reboot, it will start to bootloop again, and I have to format system to get /data to mount.

 

[blk_jack]

I guess wasn't as clear as I thought. i can get the system to boot once, but trying a reboot, it will bootloop.

I'm using the latest twrp, wipe everything but extsd, format system, install 4.3 and 4.3 gapps. I can get it to boot and everything looks good from there. however, if I reboot, it gets stuck in the bootloop. pulling battery or long press power to turn off and boot again doesn't help. I can get to recovery, but if I try to wipe cache and dalvik, it says something about cant mount /data and says it failed. then I have to go back to format system. after I do that, the text on screen says I may have to reboot recovery to access /data. then I can get it to boot again. of course I have to reinstall all of my apps again.

if I do anything that requires a reboot, it will start to bootloop again, and I have to format system to get /data to mount.

The lack of /data in recovery worries me the most. That's definitely not good and I'm not sure how that would be happening.

Are you doing all this w/ your device plugged in? Can you try not plugging it in if that's the case?
EDIT: I've had an issue where sometimes on reboot w/ my device plugged in I need to wipe dalvik to continue booting. I'm not sure why this is at the moment but it's always fixed if I reboot to recovery and wipe dalvik cache.

 

[quickquest88]

i started not plugged in at 75% batt. I installed, activated, and installed all apps. ran titanium backup, and it said something about restoring android I'd. clicked yes, and at reboot it started to loop. tried wiping everything but system, didn't want to reinstall apps. tried to reflash zip, but failed because it couldnt mount /data.format system worked. reinstalled all apps. I thought maybe titanium backup hosed it somehow so i stayed away from it. wanted to change font with ifont. reboot looped again. wiping gave /data error again. format system worked without reflashing zip. got it running, oddly enough with the changed font.

the second format was plugged in, as at that point I was down to about 45% batt. As long as I don't reboot, everything seems good. hesitant to reboot again in case it loops.

 

[blk_jack]

i started not plugged in at 75% batt. I installed, activated, and installed all apps. ran titanium backup, and it said something about restoring android I'd. clicked yes, and at reboot it started to loop. tried wiping everything but system, didn't want to reinstall apps. tried to reflash zip, but failed because it couldnt mount /data.format system worked. reinstalled all apps. I thought maybe titanium backup hosed it somehow so i stayed away from it. wanted to change font with ifont. reboot looped again. wiping gave /data error again. format system worked without reflashing zip. got it running, oddly enough with the changed font.

the second format was plugged in, as at that point I was down to about 45% batt. As long as I don't reboot, everything seems good. hesitant to reboot again in case it loops.

From what I'm reading there are issues w/ TWRP 2.6. Downgrade to TWRP 2.5 and your issues should go away.

 

[quickquest88]

I couldn't find twerp 2.5, so I installed cwm 6. now i can't get past the bootloop no matter what. I'm not getting an error about /data, but nothing, not even a format system will get the damn thing to boot to o.s.
I went through and formatted everything in the mounts menu one by one. still nothing.

I spoke too soon. now I'm getting an error when trying to format system that says cwm can't mount /data or /android.secure and /sdcard

now I seem to be soft bricked. I can't get it to go past the Samsung galaxy s4 screen. can't format.

 

[blk_jack]

I couldn't find twerp 2.5, so I installed cwm 6. now i can't get past the bootloop no matter what. I'm not getting an error about /data, but nothing, not even a format system will get the damn thing to boot to o.s.
I went through and formatted everything in the mounts menu one by one. still nothing.

You sure you don't have a bad build?? None of my testers are having these issues. Grab it here & flash it w/ goomanager or odin/hemidall http://goo.im/devs/OpenRecovery/jfltetmo

 

[quickquest88]

thanks fro the link. twrp 2502 got me out of the softbrick. with cwm, nothing seemed to work to get it past the samsung screen.

twrp got me to the point that i can at least get it running again, however, not even 2502 fixes the original issue of being unable to reboot. this time after getting 4.3 installed, i rebooted at the screen asking what language. it didnt get past the samsung screen. went back into recovery and wipe/format data/yes and then reboot. that got me back into the o.s.

this is really strange, i wish i knew more about developing. as long as i dont reboot, im ok. good thing this isnt windows, or id be in trouble, hah!!

 

[yogi2010]

I had no problems installing with the latest regular version of CWM from ROM Manager. Got root working just by tinkering around in superuser in settings... Not sure what I did but root works. Overall very very nice for a beta release!

I have one inane question(hope I didn't miss it somewhere): is the setting for lock screen rotation removed? It seemed to me to be buggy on cm10.2 anyway. Also can't remember if the phone app rotated to landscape in 4.2.2 build, but I think it did. Again, meaningless issues really, just wondering.

Thanks for the hard and awesome work!

 

[LuigiBull23]

Loving the beta build! It's almost fully stable! All convenient features are working as should!

 

[Bowmanspeer]

I wants to say Great job! Got it all set up to find the camera won't work. Give error "Can't connect to camera". I thought OK, I'll try focal. Did the same thing initially then soft bricked the phone. Had to start from scratch.

I did notice as I scrolled through app list in TB that it didn't list a camera app at all.

 

[blk_jack]

I wants to say Great job! Got it all set up to find the camera won't work. Give error "Can't connect to camera". I thought OK, I'll try focal. Did the same thing initially then soft bricked the phone. Had to start from scratch.

I did notice as I scrolled through app list in TB that it didn't list a camera app at all.

It'll be under Gallery2

Sent from my SGH-I337M using Tapatalk 4

 

[Pinan]

Flashed 8/20/13 using TWRP 2.5.0.2. No problem, other than some freezing apps here and there. Cleared caches, fixed permissions, and all seem fine now.

Will now run it through my battery tests, etc.

Thank you blk_jack!

 

[quickquest88]

I'm not sure what happened to my phone. Apparently twrp 2.6 caused some weird issue that wasn't fixed by reflashing with another recovery.

I had to Odin back to stock (freaked me out cause first Odin attempt failed, second passed, then I had to go back and format system again), and upgrade from there. Now it works like it should, rebooting and everything with oudhs.

Sent from my SGH-M919 using xda app-developers app

 

[blk_jack]

I'm not sure what happened to my phone. Apparently twrp 2.6 caused some weird issue that wasn't fixed by reflashing with another recovery.

I had to Odin back to stock (freaked me out cause first Odin attempt failed, second passed, then I had to go back and format system again), and upgrade from there. Now it works like it should, rebooting and everything with oudhs.

Sent from my SGH-M919 using xda app-developers app

This is a notice for others on TWRP 2.6. Please read the OP (post 3 specifically). It has been updated to contain a mini-FAQ for 4.3 that should solve 99% of the issues I'm seeing on XDA.

 

[Persianhawkes]

Any way to get stock DPI?

Sent from my Nexus 7 using Tapatalk 4