February 4: Rom updated to include February security patches.
Download: http://forum.xda-developers.com/devdb/project/dl/?id=16643
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
January 14. Rom updated to include Google's January 2016 security patches. Also, selinux not only disabled, but completely removed: the rom compiled without selinux sources/binaries.
Kernel does NOT include recovery, so use TWRP for Fota/Recovery partition.
Download: http://forum.xda-developers.com/devdb/project/dl/?id=16217
_________________________________________________________________________________
For those who prefer to stick to bugless kitkat: Rom updated to include all "shields up" features including cleaning creepy Ips and dns defaults. Compiled just a few days ago.
Download Link: http://forum.xda-developers.com/devdb/project/dl/?id=13001
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Here is Slimkat 10 unofficial built from sources on March 2. Built using JDK-7, which turned out to be beneficial for the rom. Slim, fast, smooth and stable. For those of you who have been using Lollipop for a while, you will see how much faster, smoother and more stable kitkat is. Everything works: no reboots, no freezing, no overheating, no screen light flickering, no video recording/play problems, great battery life and abundance of features. This taken together with improved security makes a pretty darn good rom. I tried it and got rid of Lollipop.
Changes:
1. New Iptables binaries which allow to stop kernel communicating (if used with Afwall) with Google home.
2. Changes in Vold to enable 256 bit AES encryption, as opposed to default 128 bit
3. Key length increased for multiple keys
3. Kernel with disabled Selinux and enabled Tomoyo together with all ciphers/hushes/digests/random number generation tools
4. Latest changes from Google code (I was surprised finding changes pushed for kitkat while synching Google source)
5. TWRP 2.8.x integrated in boot image
Install:
1. Be on Kitkat, rooted with recovery
2. Enter recovery and wipe Cache/System/Data
3. Flash the rom and reboot
4. Enjoy and say thank you or perhaps donate
Rom is in Download section above
Credit: Slimroms
Warning: I am not responsible for your device exploding and killing everybody around. You are on your own. :laugh:
Source: https://github.com/SlimRoms/platform_manifest/tree/kk4.4-caf
Source with changes: https://github.com/HonamiZ1
XDA:DevDB Information
Slimkat 10 Final Edition, ROM for the Sony Xperia Z1
Contributors
optimumpro
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader
Based On: Slimroms
Version Information
Status: Stable
Current Stable Version: 10
Stable Release Date: 2015-03-02
Created 2015-03-03
Last Updated 2016-02-04
Reserved
Believe me I have no interest in being in any of "your threads" {That's why I'm editing this post instead of posting a new one xD},
I'll leave this thread from any further discussion.... for now at least
Regards,
Omar.
OmarEinea said:
Cool, can you give us changelog of what's new between build 9.0 and build 10?
cuz latest kk build by Slim Team is 9.0 : https://github.com/SlimRoms/vendor_slim/blob/kk4.4/config/common.mk#L154
so you must have made some major changes to call it build 10, right?
Regards,
Omar.
Click to expand...
Click to collapse
Thanks. Reading the OP might help...
" you didn't get my point, did you!!"
Oh, I did get your point alright. :fingers-crossed:
Could you please do me a favor? Kindly stay away from my threads. If you feel that you need to continue to report me, that's your right, but again, stay away from my threads.
Best regards
Gonna give this a try as sounds like Kk on steroids well stable steroids.....LP still too buggy for me.
I tried it. But play store doesn't work. What is the problem...?
Rom Updated
See OP for description and download link...
thanks
the best option is in that forum for the Z1 now
First download
Thanks for all your awesome roms
I downgraded from CM12 because it feels like each LP-Rom needs more polishing.
The Rom installed successfully (did a system / data / cache Wipe) but now I am unable to get into recovery. It is stuck on the Sony Logo. Just starting the OS works fine though.
Edit:
I tried flashing TWRP 2.8.6.0 via Flashboot.
Flash was successfull, but I still get stuck on the Sony Logo when i try to get into recovery.
The Led also switches lights from purple to orange.
Xecu said:
I downgraded from CM12 because it feels like each LP-Rom needs more polishing.
The Rom installed successfully (did a system / data / cache Wipe) but now I am unable to get into recovery. It is stuck on the Sony Logo. Just starting the OS works fine though.
Edit:
I tried flashing TWRP 2.8.6.0 via Flashboot.
Flash was successfull, but I still get stuck on the Sony Logo when i try to get into recovery.
The Led also switches lights from purple to orange.
Click to expand...
Click to collapse
If you have recovery in Fota partition, it is known to collide with in boot image recovery resulting in no recovery at all. So, you need to get rid of Fota recovery to use internal one. For that do this in fastboot: fastboot erase recovery; then fastboot reboot...
optimumpro said:
If you have recovery in Fota partition, it is known to collide with in boot image recovery resulting in no recovery at all. So, you need to get rid of Fota recovery to use internal one. For that do this in fastboot: fastboot erase recovery; then fastboot reboot...
Click to expand...
Click to collapse
Thank you! That did it.
But I still dont quite understand what happened here.
So i had 2 partitions, fota and recovery, each having a recovery installed. 'fastboot erase' does delete the one in the recovery partition, leaving only the one in fota.
That sounds kind of wrong for me, because I do want to use the recovery I install via fastboot.
Xecu said:
Thank you! That did it.
But I still dont quite understand what happened here.
So i had 2 partitions, fota and recovery, each having a recovery installed. 'fastboot erase' does delete the one in the recovery partition, leaving only the one in fota.
That sounds kind of wrong for me, because I do want to use the recovery I install via fastboot.
Click to expand...
Click to collapse
Xperias don't have recovery partition. Fota is used by stock firmware only, so it is available in custom roms, hence recovery image could be installed there. However, the normal way for custom roms is to incorporate recovery into boot image, which is faster. This was until lollipop, when the not so smart folks at Cyanogen, gave up on CWM (which was always in boot image) and came up with their own recovery. CM recovery does not work, so TWRP guys figured out a way to install their recovery in Fota, instead of having users/developers decompiling boot image, replacing CM recovery with TWRP and recompiling the image again. That's what I do in CM based kernels, but Slimrom folks use TWRP in boot by default.
So, when you did fastboot erase recovery, you got rid of recovery in fota partition. Now, you have TWRP in boot image.
Running it for 2 days now and I am highly satisfied.
I downgraded from Lollipop (tried CM, crDroid, another CM-Based Rom and Custom Stock) because each Rom caused 2 main issues: Runtime decreased from 2 days to 1 day and the infamous touch screen issues.
Running this Rom, these issues are gone. I am again at 2 days runtime and I can finally write longer messages without beeing bothered by an unresponsive screen. The system feels reliable again.
Only issue i found so far, is that my headphones are sometimes not recognized. In these cases, I have to unplug and plug them in again until the system recognizes them. I had the same issue when I was on KitSlim_AMG, but not on stock. So this might be a bug in the SlimBean / CM Code-Base.
Xecu said:
Running it for 2 days now and I am highly satisfied.
I downgraded from Lollipop (tried CM, crDroid, another CM-Based Rom and Custom Stock) because each Rom caused 2 main issues: Runtime decreased from 2 days to 1 day and the infamous touch screen issues.
Click to expand...
Click to collapse
You are forgetting the heat issue, which requires RECALL. I am not a huge gamer, but CPU can easily get to 75-80 degrees after using Firefox/Fennec for about 10 minutes. Then flickering and other heat protection kick in. Note, that most users won't notice overheat, because glass is not a very good heat conduit. They just complain of backlight flickering. However, if you enable CPU stats in developer options, you can see the temperature on screen. This is a shame (overheating), especially that LP has been around for about 7 months to no avail. You can't blame the processor, since there is no heat issue on kitkat and jb.
Lollipop, in my view, is the worst ever android version: linux (which is great) + google poop (google does what it does best) = lollipop. Really, the name should be Lollipoop.
I got another question
Logcat seems to be disabled, because /dev/log/main is not created. Is there a way to activate it?
Xecu said:
I got another question
Logcat seems to be disabled, because /dev/log/main is not created. Is there a way to activate it?
Click to expand...
Click to collapse
Logging is disabled in kernel for security. You can get a few apps on f-droid for logcat...
New build
Rom updated to include January 2016 security patches. See OP for download and description.
optimumpro said:
Rom updated to include January 2016 security patches. See OP for download and description.
Click to expand...
Click to collapse
Thank you for continuing to support KitKat I'll try the new build tomorrow
So the boot image doesn't have a kernel? Do I have to fastboot flash recovery recovery.img if I don't have the bootloader update?
Google stops after going to any pages after a couple seconds... maybe the gapps that I installed is incompatible, I don't really know.
Have been using this rom for a few weeks now, and at first sight it seemed stable but I'm seeing more and more bugs.
For example, Netflix will work fine and start playing a video for about 5 seconds, and plays anything, then the screen goes black, and audio still going. Not sure exactly what are causing these issues, but any help would be greatly appreciated.
I could add screenshots but I think since this is my very first post here on the xda forums, I suppose but I'll just write the info listed in the About phone section
Model: LG-D850
Android Version: 5.0.1
Baseband version: MPSS.DI.2.0.1.c.1.13-00009-M8974AAAAANPZM-1
Kernel version: 3.4.0-LS
[email protected] #4
Mon Dec 8 06:20.41 PST 2014
Liquid version: LS-LP-v4.0-2014-12-08
Build date: Mon Dec 8 06:17:43 PST 2014
Liquid number: liquid_d850-userdebug 5.0.1 LRXC c1415a92bd test-keys
SELinux status: Permissive
I used TWRP to flash supersu 4.0 and gapps 5.0.1, and everything said it was successful during the flash.
Also: I've been considering just flashing the newer LS soon, but I wanted to see if there was a specific cause for these google errors first.
Thank you for your time and help.
Hrmmm
EDIT 4: Cool, so as long as my phone is in a nice unusable state, how long is it going to take for this community to reply? I am in safe mode...and my computer is not recognizing the phone
Getting kind of antsy lol. Any specific ROM recommendations for D850?
Edit1-- currently flashing newest Illusion ROM and gapps-lp-20150211 from
this post: http://forum.xda-developers.com/showthread.php?t=2772658
Edit2: Someone please let me know wtf I did wrong. I can't get into recovery mode...
Unfortunately, the prcoess com.candroid.phone has stopped
I'm in a boot cycle, I backed up using TWRP before I flashed the above, I cleared cache and dalvik cache but not data.
Now the above error pops up a number of time then the phone auto reboots, and I cannot get into recovery mode.
Please help let me know what I should do at this point
Edit3: I've gotten it to where the error keeps popping up, but it's not automatically rebooting, the playstore apps on the phone are greyed out and gapps aren't. IE, I can't open TWRP..
Resolved. Running fine now on the new illusion.. Just had to go to backup & reset in settings and it finally booted up properly... Had to update the gapps after going through the initial tutorial setup on phone. But running the prerooted lollipop illusion ROM. Sorry I'm such a noobie to all of this.. Last time I was doing this stuff in was jail breaking an iPhone in 2009...
Hello, I have a Nexus 7 2013 and I love it. One of the main reasons I got this tablet is because it is a flagship Google device and it could run custom ROMs well. I want to throw Kali Pwn pad on it. When I flashed Kali, it looked like it flash successfully, but when it started it would just hang on the Google screen. Since KitKat was the latest edition of KitKat when pwnpad was launched, I decided I should try to flash stock KitKat and see what happens, it appeared like it flashed right, but when my tablet started it would still hang on the Google logo. I also tried to flash CM 11, and still the same thing happened. Every ROM I flash that is based on 4.4 hangs on the Google logo. The farthest I am able to downgrade is Android 5.0.0. My tablet came with 5.0.1 out of the box. I am currently running CM 12.1-20150814 Nightly. Another note, the only recovery I can get working TWRP MultiRom, the other verisions of TWRP (along with CWM) cant mount anything. My goal here is to get either Pwnpad or Nethunter (Nethunter would just hang on the Nexus animation, but I don't think I had enough patience that evening to let it run) installed.
Thank you for your help
Ditto!
Bump!
my device is currently on 5.0.2. i'm unable to downgrade to any Factory Image below that. any info will be helpful.
Solved
OK here is what I found. Yes you can downgrade to KitKat, if you flash this bootloader (attached) after you install your KitKat based ROM. I was able to get Kitkat NetHunter running on a deodexed ASOP ROM. The only recovery I could get running with it is the Multi-rom TWRP recovery, don't get it from the Multi-rom app, just flash the attached recovery. The weird thing is that I bought this tablet directly from Amazon, not Groupon. All talbets coming from Groupon seem to be having the TWRP mounting and the downgrading issues. I notice also that my tablet has a leaking screen. I have taken this tablet to Haiti in mid July. That might be part of the problem, but I think it is a factory defect. I bought the tablet at the start of July.
Link to the bootloader: http://www.mediafire.com/download/2s6c91j26sk9vn6/boot.img
Link to the recovery: http://www.mediafire.com/download/6hfc7yfww372lq3/TWRP_multirom_flo_201503281.img
Greetings, Picked up a referb n900T (note3) with factory 5.0 android.
I believe I did the proper procedure for rooting and custom recovery.
I unlocked first.
Used ODIN 3.10 and chainfire cf auto root-hltmo smn900 file supplied to ROOT (ok)
I then used google play to install twrp for tmob note3. (twrp 3.0) (ok)
I boot into twrp.
I installed Resurrection Remix Rom (android 6)
Now on boot up I get "Kernel is not Seandroid enforcing". Not sure what the problem could be.
I did a search and found quite a bit of info but most all of them pertain to android 4.4 etc..
Im not sure if its the root or recovery causing the problem.
It does boot into android fine though... just on initial boot up I get the warning
I downgraded twrp to 2.8 thru img file but same message
any ideas ..thanks
I guess its normal to see this.. I Odin'd back to 5.0 android and did procedure over with 2 different root programs and 2 different roms (resurrection and cm12) . I still get the warning on boot up in the upper left corner... oh well
wogeboy said:
I guess its normal to see this.. I Odin'd back to 5.0 android and did procedure over with 2 different root programs and 2 different roms (resurrection and cm12) . I still get the warning on boot up in the upper left corner... oh well
Click to expand...
Click to collapse
Yes this is normal with almost all ROM's because they are using custom kernels. That's a good thing to get that message actually. It means security on the kernel isn't being enforced. The SE part means Security Enhanced. If that is active then there are major limitations on what the kernel can do.