Related
New version Slimkat 8.10 compiled today . New kernel with Tomoyo security enabled (as opposed to Apparmor). Enjoy.
See Download section
________________________________________________________________________________________
Here is the famous Slimkat 4-4-4 rom built from sources a few hours ago. Changes made to kernel only and they are the following:
Hardened Kernel with the following features:
a. Selinux disabled (don't trust them) and APPARMOR enabled as main security
b. All crypto core features enabled
c. All authenticated encryption modes enabled - CCM, GCM and SEQIV
d. All blocks enabled - CBC, CTR, CTS, ESB, LRW, PCBC and XTS
e. All hash modes enabled including SHA512 and others
f. All ciphers enabled including CAMELIA, TWOFISH, ANUBIS, SALSA20 and others
g. Compression - DEFLATE, ZLIB and LZO
h. Random number generation all options enabled to result in a better generation without CPU wakeups
Credit: Slimroms Team
WARNINGS:
I am not responsible for your device becoming a paperweight. I am also not responsible for death and destruction caused by your flashing this rom on your device. You are at your own perill. Complain to Putin - he will surely help.
INSTRUCTIONS
1. Unlocked Bootloader
2. If you have CWM, go to mounts and storage and wipe System/Cache/Data
3. If you have TWRP, go to advanced wipe and wipe System/Cache/Data
4. Flash the rom and reboot.
5. I recommend that you delete Cyanogenmod original boot animation as it slows down the boot significantly: without it your boot should take about 25 seconds. Once you remove bootanimation.zip in /system/media, you will have a nice vanilla android bootanimation.
6. Enjoy the rom and hit Thank You or perhaps Donate?
P.S. Rom is in Download Section above
XDA:DevDB Information
[ROM] [Kitkat 4.4.4] Slim-Honami-4.4.4.build 8.10-UNOFFICIAL, ROM for the Sony Xperia Z1
Contributors
optimumpro
Source Code: https://github.com/SlimRoms/platform_manifest
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader
Based On: Slimroms
Version Information
Status: Beta
Stable Release Date: 2014-11-11
Beta Release Date: 2014-10-21
Created 2014-10-21
Last Updated 2014-11-11
Thanks Man.. Please keep up the good work
OP, it must be terrible to be asked over and over again but I'd be very glad if you could tell what those changes in the kernel that you have introduced mean for the end user. So to speak, what can we expect after installing this? is this more security oriented or would the random number generation is related to entropy stuff and is supposed to speed up the system?
I saw your other thread too, wanted to give it a try but couldn't understand what these changes to the kernel actually mean for a layman.
Thanks man for your work!
srqrox said:
OP, it must be terrible to be asked over and over again but I'd be very glad if you could tell what those changes in the kernel that you have introduced mean for the end user. So to speak, what can we expect after installing this? is this more security oriented or would the random number generation is related to entropy stuff and is supposed to speed up the system?
I saw your other thread too, wanted to give it a try but couldn't understand what these changes to the kernel actually mean for a layman.
Thanks man for your work!
Click to expand...
Click to collapse
It is actually both security oriented and system speed based on better random number generation.
First of all, I don't trust Selinux, especially in light of the recent Snowden's revelations. So, selinux is out of this kernel. Instead, you have trusted Apparmor, which has been used in Linux for years. In addition, many newer ciphers, which are in this kernel, were disabled by default -- again think of several 3-letter-agencies that are known for deliberately weakening kernels and operating systems to make it easiers for themselves to break. So, I have enabled those ciphers. Hashes, especially SHA512, which is the strongest, were disabled by default. I have enabled them all. Random number generation: the same.
So, as result, you have a more secure system that is faster, because of better and more random seeding.. If you remember, there is an app on XDA, which the author says, provides better random number generation, but it drains battery, because CPU constantly checks if the pool (of random numbers) is large enough. Here, it is different, because the changes (better and more random seeding ) are on the kernel level. So, CPU does not have to constantly wake up and check...
optimumpro said:
It is actually both security oriented and system speed based on better random number generation.
First of all, I don't trust Selinux, especially in light of the recent Snowden's revelations. So, selinux is out of this kernel. Instead, you have trusted Apparmor, which has been used in Linux for years. In addition, many newer ciphers, which are in this kernel, were disabled by default -- again think of several 3-letter-agencoes that are known for deliberately weakening kernels and operating systems to make it easiers for themselves to break. So, I have enabled those ciphers. Hashes, especially SHA512, which is the strongest, were disabled by default. I have enabled them all. Random number generation: the same.
So, as result, you have a more secure system that is faster, because better and more random seeding.. If you remember, there is an app on XDA, which the author says, provides better random number generation, but it drains battery, because CPU constantly checks if the pool (of random numbers) is large enough. Here, it is different, because the changes (better and more random seeding ) are on the kernel level. So, CPU does not have to constantly wake up and check...
Click to expand...
Click to collapse
Got it, thanks for the great explanation bro.
I totally get it now, would be trying Aragon one today would definitely come and report how that works!
Great work buddy,
Can you share your kernel sources?
I might include some of your changes in official slimkat
also out of curiosity, if the change is only on the kernel, wouldn't it be easier to share the kernel only!
Regards,
Omar.
OmarEinea said:
Great work buddy,
Can you share your kernel sources?
I might include some of your changes in official slimkat
also out of curiosity, if the change is only on the kernel, wouldn't it be easier to share the kernel only!
Regards,
Omar.
Click to expand...
Click to collapse
Of course it is easier to do the kernel only, but I haven't found the way to do that outside of building the whole rom. Plus, in CM roms, I know where to put those changes: row rhine honam_def.conf and if you look at my sources for Black Argon rom, you will find the changes there.. But Slimroms guys use some other file, so I put my .config file in during the build. Plus, for the new kernel to work, you need modules from the rom you will be using it in and roms differ from one to another. So, for now, it is easier for me to build the whole rom.
very good
each person who comes to their work
it is a hope to be in a rom kk
if this rom has the same problem that all
3g signal loss that is very unpleasant truth
You could solve this drawback
It's good to see you here. A couple of months ago in the ion forums you were patient and answered a lot of questions I had when I switched from HTC to Sony. Armed with a little knowledge, I was able to find a good used Z1 with an unlockable bootloader.
Thanks again.
New Version Slimkat 8.10 posted: see Download section
New version posted. See Download...
auto rotate not working
Auto rotate not working anywhere
Yes. For some reason autorotate does not work. I even recompiled the 8.12 version and it still does not work. The Slim original 8.12 is fine. It is also not my kernel, because I am using my kernel with Slimkat original weekly without any problem. I am puzzled as to why it is happening...
The only change in build.prop I made was to add 3 entries regarding rild. You can try to open build.prop and delete those three entries (search for "rild" and delete them). But I don't think rild has anything to do with the sensors.
thanks !
optimumpro said:
New version Slimkat 8.10 compiled today . New kernel with Tomoyo security enabled (as opposed to Apparmor). Enjoy.
See Download section
________________________________________________________________________________________
Here is the famous Slimkat 4-4-4 rom built from sources a few hours ago. Changes made to kernel only and they are the following:
Hardened Kernel with the following features:
a. Selinux disabled (don't trust them) and APPARMOR enabled as main security
b. All crypto core features enabled
c. All authenticated encryption modes enabled - CCM, GCM and SEQIV
d. All blocks enabled - CBC, CTR, CTS, ESB, LRW, PCBC and XTS
e. All hash modes enabled including SHA512 and others
f. All ciphers enabled including CAMELIA, TWOFISH, ANUBIS, SALSA20 and others
g. Compression - DEFLATE, ZLIB and LZO
h. Random number generation all options enabled to result in a better generation without CPU wakeups
Credit: Slimroms Team
WARNINGS:
I am not responsible for your device becoming a paperweight. I am also not responsible for death and destruction caused by your flashing this rom on your device. You are at your own perill. Complain to Putin - he will surely help.
INSTRUCTIONS
1. Unlocked Bootloader
2. If you have CWM, go to mounts and storage and wipe System/Cache/Data
3. If you have TWRP, go to advanced wipe and wipe System/Cache/Data
4. Flash the rom and reboot.
5. I recommend that you delete Cyanogenmod original boot animation as it slows down the boot significantly: without it your boot should take about 25 seconds. Once you remove bootanimation.zip in /system/media, you will have a nice vanilla android bootanimation.
6. Enjoy the rom and hit Thank You or perhaps Donate?
P.S. Rom is in Download Section above
XDA:DevDB Information
[ROM] [Kitkat 4.4.4] Slim-Honami-4.4.4.build 8.10-UNOFFICIAL, ROM for the Sony Xperia Z1
Contributors
optimumpro
Source Code: https://github.com/SlimRoms/platform_manifest
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader
Based On: Slimroms
Version Information
Status: Beta
Stable Release Date: 2014-11-11
Beta Release Date: 2014-10-21
Created 2014-10-21
Last Updated 2014-11-11
Click to expand...
Click to collapse
Installed this 4.4.4 version and it works gr8.. but my recovery is gone
Tried : Z1-lockeddualrecovery2.8.15-RELEASE.installer and Fota.. both states that it works but my recovery never "boots" just stands there with a another light on the phone..
Suggestions anyone ?
Now i have a working 4.4.4 Rom but no working recovery (light changes but recovery never boots, when i press volume)
hakd said:
Installed this 4.4.4 version and it works gr8.. but my recovery is gone
Tried : Z1-lockeddualrecovery2.8.15-RELEASE.installer and Fota.. both states that it works but my recovery never "boots" just stands there with a another light on the phone..
Suggestions anyone ?
Now i have a working 4.4.4 Rom but no working recovery (light changes but recovery never boots, when i press volume)
Click to expand...
Click to collapse
Kitkat custom roms have in boot.img recovery, which collide with fota recovery. You need to get rid of one or you will have no recovery at all. The easiest way is to erase fota recovery:
Boot to fastboot and do this: fastboot erase recovery; then fastboot reboot. That's it.
optimumpro said:
Kitkat custom roms have in boot.img recovery, which collide with fota recovery. You need to get rid of one or you will have no recovery at all. The easiest way is to erase fota recovery:
Boot to fastboot and do this: fastboot erase recovery; then fastboot reboot. That's it.
Click to expand...
Click to collapse
LOG:
C:\Megasync\Android\ADB + Recovery>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.019s]
finished. total time: 0.020s
C:\Megasync\Android\ADB + Recovery>fastboot reboot
rebooting...
finished. total time: 0.002s
Thanks alot for taking the time to help me, now i got an awesome 4.4.4 With a custom recovery when i change my mind (5.x.x was not stable enough)
optimumpro said:
Kitkat custom roms have in boot.img recovery, which collide with fota recovery. You need to get rid of one or you will have no recovery at all. The easiest way is to erase fota recovery:
Boot to fastboot and do this: fastboot erase recovery; then fastboot reboot. That's it.
Click to expand...
Click to collapse
this helped me a lot
Here is infamous Tesla rom LP 5.1.1 built from source just a few hours ago. Latest features
My features:
1. Hardened kernel, overclocked, voltage, kcal, sound
2. Removed garbage IPs throughout sources
3. Removed NSA from kernel and replaced it with Tomoyo
4. Low camcoder sound fixed
5. Thermal manager values tweaked to prevent screen flickering and overheating
6. Data encryption set to 256 bit 7000 iteration
7. WIFI background scanning disabled for privacy and battery sake
8. Volte (Voice over LTE) enabled
9. Network selection handled by System, as opposed to Simcard/Modem to prevent carrier default
10. GPS supl change to Sony server
11. TWRP 2.8.0 incorporated in boot image
Maybe more...
Instructions:
1. Unlocked bootloader, TWRP
2. Enter recovery and wipe the following: System/Data/Cache/Internal SD
3. Factory reset: important since TWRP is known for not reliable formatting
5. Flash the rom and reboot
6. Enjoy and hit thank you, donate or both
Credit: Tesla Team, CM, Slimroms, AOKP
XDA:DevDB Information
Tesla LP5.1.1 Unofficial, ROM for the Sony Xperia Z1
Contributors
optimumpro
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader
Based On: CM
Version Information
Status: Testing
Created 2015-06-22
Last Updated 2015-06-22
Screenshots
Screenshots added with a black theme...
Use this rom since 2 days, (sorry, got it from your androidfilehost account).
Beside the bugs it works rly great! First LP Rom i want to use as daily
Bugs i found:
- theres no powermenu, the phone goes imidiatly off. (fixed it with apm+)
- no CM-Themer (pls put in )
- your recovery doesn't work, only get a destroyd picture and phone freeze (fixed it with fota twrp)
Aaskereija said:
Use this rom since 2 days, (sorry, got it from your androidfilehost account).
Beside the bugs it works rly great! First LP Rom i want to use as daily
Bugs i found:
- theres no powermenu, the phone goes imidiatly off. (fixed it with apm+)
- no CM-Themer (pls put in )
- your recovery doesn't work, only get a destroyd picture and phone freeze (fixed it with fota twrp)
Click to expand...
Click to collapse
You are confusing this rom, which is an unofficial build with the official one posted a few days ago. My build was posted just an hour ago. None of those bugs are present in my build: There is CM themer, there is power menu including advanced boot and there is a working TWRP in boot image.
Sorry, it is from another team. My fault
See post #2 for screen shots...
optimumpro said:
Here is infamous Tesla rom LP 5.1.1 built from source just a few hours ago. Latest features
My features:
1. Hardened kernel, overclocked, voltage, kcal, sound
2. Removed garbage IPs throughout sources
3. Removed NSA from kernel and replaced it with Tomoyo
4. Low camcoder sound fixed
5. Thermal manager values tweaked to prevent screen flickering and overheating
6. Data encryption set to 256 bit 7000 iteration
7. WIFI background scanning disabled for privacy and battery sake
8. Volte (Voice over LTE) enabled
9. Network selection handled by System, as opposed to Simcard/Modem to prevent carrier default
10. GPS supl change to Sony server
11. TWRP 2.8.0 incorporated in boot image
Maybe more...
Instructions:
1. Unlocked bootloader, TWRP
2. Enter recovery and wipe the following: System/Data/Cache/Internal SD
3. Factory reset: important since TWRP is known for not reliable formatting
5. Flash the rom and reboot
6. Enjoy and hit thank you, donate or both
Credit: Tesla Team, CM, Slimroms, AOKP
XDA:DevDB Information
Tesla LP5.1.1 Unofficial, ROM for the Sony Xperia Z1
Contributors
optimumpro
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader
Based On: CM
Version Information
Status: Testing
Created 2015-06-22
Last Updated 2015-06-22
Click to expand...
Click to collapse
Replacing resurrection remixed? What's the difference between 2? If this is superset of RR I'll switch over
wis3m0nkey said:
Replacing resurrection remixed? What's the difference between 2? If this is superset of RR I'll switch over
Click to expand...
Click to collapse
Not replacing anything. RR is well supported. Tesla is a different rom. It has support for Slimrom's layers as well as many other features. I like it more than RR, but for you the only way to find out is to try it...
optimumpro said:
Not replacing anything. RR is well supported. Tesla is a different rom. It has support for Slimrom's layers as well as many other features. I like it more than RR, but for you the only way to find out is to try it...
Click to expand...
Click to collapse
OK so I'll go to Tesla and use encryption similar to RR.
Is that correct?
wis3m0nkey said:
OK so I'll go to Tesla and use encryption similar to RR.
Is that correct?
Click to expand...
Click to collapse
Yes. All hardened features are there...
@optimumpro
Using this rom for 3-4 days no force closes no memory leak issues just damn perfect thank you... ?
TeslaOS is ROM by a well known banned member.
Any work or derived works are not welcome on XDA.
-karandpr
XDA Staff
Directions to setup wifi/data without captiveportal and with Afwall:
http://forum.xda-developers.com/showpost.php?p=62560397&postcount=3
March 3. New release.
1. LP 5.1.1 r.34
2. Up to day google/cm changes
3. Improved WIFI handling to cellular
4. M5 kernel with fixed sound
Download: http://forum.xda-developers.com/devdb/project/dl/?id=17183
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
February 15. Updated kernel to fix headphone sound.
Download: forum.xda-developers.com/attachment.php?attachmentid=3647315&d=1455549561
Unzip and flash in fastboot
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
]anuary 24: Rom updated to release 33
Warning: All my roms now include a custom script that executes on boot, not at init.d level, which comes much later, but at init.rc. This script disables internet access to prevent data leaking from android system during boot before init.d or your firewalls come in. After the phone is booted and Afwall starts, it resets iptable rules and you then have the internet. Afwall is a must if you care about your privacy and battery life. If you, however, are not going to use Afwall, then delete the following file: /system/etc/crashdod.sh and reboot.
1. Release 33
2. January security patches
3. Wakelock blocker added
4. Updated M5 kernel to include latest CM/Sony changes
Kernel Source: https://github.com/AOSP-Argon/android_kernel_sony_msm8974
Download: http://forum.xda-developers.com/devdb/project/dl/?id=16401
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
November 25. Updated M5 Kernel built with the latest Ubertc 5.2.1 Nov 21 edition. Also, Sony bootlogo image themed in a teal color, the Tesla way.
Download: http://forum.xda-developers.com/devdb/project/dl/?id=15345
Unzip and flash. Or you can flash the image with Kernel Adiutor.
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
November 22: New build. This is release 29 with Anti-Piracy features removed. Probably the final build. Enjoy.
Download: http://forum.xda-developers.com/devdb/project/dl/?id=15314
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
November 1. New kernel. [/COLOR]
1. Enabled hardware based encryption mixed with software (you need to re-encrypt to have the feature),
2. Enabled hardware random number generation also mixed with software
3. Your WIFI will work regardless of whether you have old wifi binaries or new
4. I have not incorporated some CM/M5 commits, as they cause random reboots.
5. Some security improvements in init files: now adb won't really work if usb debugging is set to off. Before that even if debugging was off, kernel would still get adb root rights during boot, which is insecure
Dowonload: forum.xda-developers.com/attachment.php?attachmentid=3527276&stc=1&d=1446392027
Sources for kernel: https://github.com/HonamiZ1/android_kernel_sony_msm8974
Instructions:
1. This boot.img does not have TWRP, so use Fota recovery image from my thread here http://forum.xda-developers.com/xperia-z1/orig-development/twrp-2-8-7-fota-partition-brightness-t3237229
2. Unzip boot.img and flash in fastboot: fastboot flash boot boot.img
3. To install TWRP 2.8.7 in Fota or Recovery (depending on whether you have upgraded your bootloader or not) do this also in fastboot: fastboot flash recovery recovery.img
4. Reboot. Now, you will have TWRP independent from kernel
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
This is Tesla-Redux resurrected by me. As you know, the latest official build does not recognize simcard, virtually turning your phone in a wifi device. Moreover, rhine devices are no longer officially supported and the honami thread itself is closed. Well, I fixed the simcard issue and built the rom from the latest sources.
Features include: SlimPie, RRO Layers, Customizable QS Tiles, SlimRecents, Slim's Power Menu, Slim's Nav bar, Hardware keys configuration, Animation Control, App Circle Sidebar, Lockscreen Weather, Screenrecorder settings, Kernel Aduitor built in plus more. My usual hardened features include hardened kernel (modified M5) plus removed nefarious IPs pooped by Google all over the source; full network choice in Cell menu; background wifi scanning is disabled for privacy and battery sake; cell network is handled by Android, as opposed to the modem; Volte provisioned; TWRP 2.8.7 in boot image, and much more...
This rom does NOT include the latest CM power scheme change, which causes random reboots and other issues. It is neither in this rom nor in my DU or Jaguar rom. The original power scheme was fine, no bugs, nothing to fix. So, why fix it, especially, that CM and Sony folks are incorporating 5-10 year old changes just now. I am not blaming Sony kernel developers, as they are not given the latest Sony blobs that are used in stock. So, as a result, they are working like kittens in the dark trying to bridge kernel with android and hardware. The same applies to the latest kernel commits including wifi. Prima driver worked fine in my latest Jaguar/DU builds, there were no WIFI issues. Moreover, the latest M5 changes cause multiple errors during build, so, kernel in this rom is stable as of October 8 or 9. This is the best you can get, as I doubt anyone will be paying any attention to lollipop any longer. .
Usual XDA warning: if your device dies or kills everybody in the vicinity, blame Putin, but I don't recommend it, since Russians mean business nowadays.
Instructions:
1. Unlocked bootloader, root and TWRP recovery
2. Wipe everything including internal SD card
3. Flash the rom, reboot and enjoy
Credit: Tesla Team, Slimroms and CM
Download: http://forum.xda-developers.com/devdb/project/dl/?id=14909
Kernel Sources: https://github.com/AOSP-Jaguar/android_kernel_sony_msm8974
XDA:DevDB Information
TESLA-REDUX-RESURRECTED, ROM for the Sony Xperia Z1
Contributors
optimumpro
Source Code: https://github.com/tesla-redux
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader
Based On: AOSP,Slimroms,CM
Version Information
Status: Stable
Stable Release Date: 2015-10-26
Created 2015-10-26
Last Updated 2016-03-03
Reserved
Mine
optimumpro said:
This is Tesla-Redux resurrected by me. As you know, the latest official build does not recognize simcard, virtually turning your phone in a wifi device. Moreover, rhine devices are no longer officially supported and the honami thread itself is closed. Well, I fixed the simcard issue and built the rom from the latest sources.
Features include: SlimPie, RRO Layers, Custimizable QS Tiles, SlimRecents, Slim's Power Menu, Slim's Nav bar, Hardware keys configuration, Animation Control, App Circle Sidebar, Lockscreen Weather, Screenrecorder settings, Kernel Aduitor built in plus more. My usual hardened features include hardened kernel (modified M5) plus removing nefarious IPs pooped by Google all over the source; full network choice in Cell menu; background wifi scanning is disabled for privacy and battery sake; cell network is handled by Android, as opposed to the modem; Volte provisioned; TWRP 2.8.7 in boot image, and much more...
Usual XDA warning: if your device dies or kills everybody in the vicinity, blame Putin, but I don't recommend it, since Russians mean business nowadays.
Instructions:
1. Unlocked bootloader, root and TWRP recovery
2. Wipe everything including internal SD card
3. Flash the rom, reboot and enjoy
Credit: Tesla Team, Slimroms and CM
Download: http://forum.xda-developers.com/devdb/project/dl/?id=14909
Kernel Sources: https://github.com/AOSP-Jaguar/android_kernel_sony_msm8974
XDA:DevDB Information
TESLA-REDUX-RESURRECTED, ROM for the Sony Xperia Z1
Contributors
optimumpro
Source Code: https://github.com/tesla-redux
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader
Based On: AOSP,Slimroms,CM
Version Information
Status: Stable
Stable Release Date: 2015-10-26
Created 2015-10-26
Last Updated 2015-10-26
Click to expand...
Click to collapse
Ready 2 test but will it work on C6902? Its Modem?
happy3777 said:
Ready 2 test but will it work on C6902? Its Modem?
Click to expand...
Click to collapse
Just flash C6902 modem on top: it is not a big deal...
You sir are a legend... Can't figure which one to use, Tesla or Jaguar Right now I'm on Tesla, testing stuff
Quick update, since GZR does not support our devices for some time now, they probably did not include the patch for headphones... would you mind to include it? I'm pretty sure that that bug is not present in Jaguar or DU
THANK TOU!
caki25 said:
You sir are a legend... Can't figure which one to use, Tesla or Jaguar Right now I'm on Tesla, testing stuff
Click to expand...
Click to collapse
Thank you. I am now on Tesla and it is hard to say which one is better. Jaguar is a little lighter, though. but Tesla guys have changed some animation timing, so, even if you turn off animation in developer section completely, it still feels a little different. I think Jaguar is lighter and a little faster, but Tesla feels smoother...
Does this and the jaguar ROM have the random reboot problems that Resurrection Remix is having?
Thanks.
YaqubYahya said:
Does this and the jaguar ROM have the random reboot problems that Resurrection Remix is having?
Thanks.
Click to expand...
Click to collapse
Not at all. Read the OP regarding random reboots on other roms...
optimumpro said:
Not at all. Read the OP regarding random reboots on other roms...
Click to expand...
Click to collapse
Oooooh, I'll most likely switch over tomorrow, which ROM do you recommend? Jaguar or Tesla?
Thanks for your great work!
optimumpro said:
Just flash C6902 modem on top: it is not a big deal...
Click to expand...
Click to collapse
Modem Zip never forked for me
Only cm12.1 is working for me without modem,
Either I always get a broken wifi on using modem
:crying:
happy3777 said:
Modem Zip never forked for me
Only cm12.1 is working for me without modem,
Either I always get a broken wifi on using modem
:crying:
Click to expand...
Click to collapse
You sure you used the correct one? http://forum.xda-developers.com/showthread.php?t=2614645
Works for others...
Hi, loving the rom! However is there any way of changing how curved the edges of everything is? I really don't like it, thanks.
YaqubYahya said:
Hi, loving the rom! However is there any way of changing how curved the edges of everything is? I really don't like it, thanks.
Click to expand...
Click to collapse
Have you changed screen resolution at all?
I don't know. I only start to see screen irregularities after 3-4 glasses of red wine.
optimumpro said:
You sure you used the correct one? http://forum.xda-developers.com/showthread.php?t=2614645
Works for others...
Click to expand...
Click to collapse
Ok I will try it today and report it 2 U
Thanx
How is the battery life on this ROM? That's my main prblm
optimumpro said:
Have you changed screen resolution at all?
I don't know. I only start to see screen irregularities after 3-4 glasses of red wine.
Click to expand...
Click to collapse
I think he's referring to the rounded corners of the notifications and the recent apps.
OT: I personally like it
What is the differentiating feature of this..
New kernel. See OP for description
optimumpro said:
New kernel. See OP for description
Click to expand...
Click to collapse
Can I flash this via twrp?
Ohhdayumm said:
Can I flash this via twrp?
Click to expand...
Click to collapse
No, it's a boot.img, so, you'll need a laptop...
The Sony Open Devices Project is always happy about volunteers (coding, testing, etc)
Also mainlining your favorite snapdragon powered xperia device into the mainline kernel is possible and we will be glad to help you!
Official site
Unofficial site
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
This is the LineageOS ROM for the Sony Xperia XZ2 (akari), XZ2C (apollo) and XZ3 (akatsuki)
This ROM build will always mainly based on Code from Sony AOSP & LineageOS and maybe include cherry-picks.
I plan to make monthly builds, after a new security patch level, if there is no need for a critical hotfix.
FAQ:
Switch the A/B slot for every monthly release to make sure you execute the same amount of write cycles on the entire flash storage. (Extends hardware lifetime)
fastboot & adb
https://developer.sony.com/develop/open-devices/get-started/flash-tool/useful-key-combinations/
https://wiki.lineageos.org/adb_fastboot_guide.html
https://developer.android.com/studio/releases/platform-tools
Stuck at SONY logo? Maybe you need to flash the OEM binary to oem_a and oem_b, while just oem is not enough.
For a complete security patch you have to install the newest stock firmware and boot it once.
https://github.com/sonyxperiadev/bug_tracker/issues/258#issuecomment-445816826
TL;DR Flash the latest stockfirmware, boot it once, to update your baseband/mobile network drivers and then flash this ROM.
(I prefer and support only newflasher from XDA and xperifirm to download the firmware.)
Maybe this helps windows users:
https://developer.sony.com/posts/flash-tool-updated-with-new-feature/
jerpelea said:
for a complete security patch you have to
1. flash the stock firmware using https://developer.sony.com/develop/open-devices/get-started/flash-tool/
2. build and flash the ROM
* The security patch may affect or not the proprietary parts depending on HW and implementation
* After official support ends you can still get security updates for kernel and Android but loader and firmware will be stuck to the latest official release
Click to expand...
Click to collapse
Bugtracker:
SODP Bugtracker -> If you think the problem is in SODP
LineageOS Bugtracker -> If you think the problem is in LineageOS
My Bugtracker -> If you think the problem is in my implementation
Bugreport:
A bugreport needs
Code:
logcat -b all
and a way to reproduce the issue.
A crash of the system requires the content of the /sys/fs/pstore folder as bug report
Be aware that a second reboot erases this folder
A crash to the recovery partition requires additionally the content of the /dev/block/by-name/misc partition
You get the content via `cat /dev/block/by-name/misc partition > /path/to/output/file.txt`
To rescue a not responding phone:
VOLUP+POWER for 3 Seconds -> RESTART with one Vibration.
VOLUP+POWER for 20 Seconds -> SHUTDOWN with 3 Vibrations.
VOLUP+POWER+CAMERA for 30 Seconds -> HARDWARE SHUTDOWN by discharging a capacitor.
Thank you very much for your help, code contribution & testing! (Random order):
@jerpelea, the sony employees and their volunteers (people like you and me) coding this wonderful piece of software
@dhacke for providing a download server
@Raphos for the initial installation manual without a recovery system, after I switched to OTA zips.
@kgvarunkanth for the jenkins build server
And many thanks to the few donators!
A telegram group for technical SODP stuff:
Sony [*Kim Jong*Un]official OD Chat
https://developer.sony.com/develop/open-devices OEM binaries: @SMDW_downloads Bug Tracker: https://github.com/sonyxperiadev/bug_tracker This group is only for dev stuff. For support: https://t.me/xdadevelopershub
t.me
XDA:DevDB Information
LineageOS, ROM for the Xperia XZ2
Contributors
MartinX3, SODP Team
Source Code: https://github.com/MartinX3-AndroidDevelopment-LineageOS/
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Latest Stock Firmware
Based On: LineageOS
Version Information
Status: No Longer Updated
Current Stable Version: 17.1
Created 2020-02-02
Last Updated 2020-10-23
Download & Installation
Download ROM:
Android File Host
FTP-Server from @dhacke
Download Drivers:
OEM (Tama) binaries
Please use the the OEM build which came before my last release, unless otherwise written.
GCAM Camera App:
Suggested GCams But GCAM's aren't usable at the moment until a camera hardware resource budget bug got fixed in the OEM binary blob.
Installation with a recovery:
fastboot flash oem_a oem_*.img
fastboot flash oem_b oem_*.img
Flash the ROM in a recovery
Reboot into recovery just to make sure you're on the new slot
Google Apps like Playstore
Dual Sim Patcher
(In case a modification prevents your device from booting) fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Flash the ROM without a recovery:
Extract the payload.bin from the .zip file
Extract the .img files with the Playload Dumper
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot -w (Wipes your internal storage and the userdata)
Continue with the normal installation
News
24.08.2020
since we have now an official lineageos based on stock, this rom would be double work.
So i stop the los port.
(sadly unless a dev owns a xz2p or xz3 these phones won't be supported in the official stock based lineageos)
the only difference between the stock and sodp editions are:
Sodp will get gcam support later and has camera2api level 3.
Stock will never support gcam apps and has the limited stock camera2api level.
Sodp uses a 4.14 kernel and probably get mainline support later.
Stock uses the stock 4.9 kernel and will probably be there forever.
Sodp targets to use as much open source as possible.
And livedisplay doesn't work in my sodp version.
Ps: After the september exams in the new semester i look for a rom replacement for the sake of diversity.
It's good to have a choice and with the available official supported sodp based pixel experiment, we have a rom which sadly forces you to use the full gapps (google apps package).
Click to expand...
Click to collapse
13.07.2020
july security patch level
oemv9c support
and any other sodp open source changes since my last build
Click to expand...
Click to collapse
18.06.2020
june security patch level
oemv8 support
and any other sodp open source changes since my last build
fixes for charger, battery, sleep (sideeffect working bluetooth audio) and more!
Click to expand...
Click to collapse
11.05.2020
may security patch level
oemv6 support
and any other sodp open source change since my last build
ps: Camera is work in progress.
Please flash gapps and the dual sim patcher again after applying an ota update.
It seems that the ota zip replaces every partition and deletes the modifications (like gapps).
Also it enforces avb heavily which prevents modifications like gapps from getting loaded.
So i deactivated avb now.
(but since the device bootloader can't be relocked the avb is not really useful anyway)
Click to expand...
Click to collapse
14.04.2020
now android 10.0.0_r33
april security patch level
oemv5 support
and any other sodp open source change since my last build
switched to:
zip files to flash
dual sim patcher instead of dual sim rom files
removed buildin gapps, since you can flash it now via twrp
installing this rom as an update won't remove the installed gapps.
ps: Camera is work in progress.
Click to expand...
Click to collapse
09.03.2020
march 2020 security update
oemv4 -> camera & other improvements
and any other lineageos / sodp open source changes since my last build
ps: Camera is work in progress.
Ps0:
Other than the aosp release, this lineageos got the new ril by qcom enabled for mobile network access.
Please test and report bugs. (dmesg & logcat, -> and pstore if the device crashes)
it will get activated in the next aosp release as well, if it makes no trouble.
Click to expand...
Click to collapse
01.03.2020
oemv4 is needed or device won't boot.
Oemv4 is not backward compatible with older releases.
oemv4 -> camera & other improvements
and any other lineageos / sodp open source changes since my last build
ps: Camera is work in progress.
Ps0:
Other than the aosp release, this lineageos got the new ril by qcom enabled for mobile network access.
Please test and report bugs. (dmesg & logcat, -> and pstore if the device crashes)
it will activated in the next aosp release as well, if it makes no trouble.
Click to expand...
Click to collapse
29.02.2020
added support for every sodp supported xperia https://github.com/martinx3-androiddevelopment-lineageos/
(except the loire and tone platform which no one requested.)
the oemv4 rom release will delay a bit.
Was in the need to delete my build cache for aosp and lineageos.
Click to expand...
Click to collapse
25.02.2020
need to take down the builds.
Oemv4 which comes tomorrow got some additional last minute changes today which needs a new rom compilation.
Click to expand...
Click to collapse
24.02.2020
oemv4 is needed or device won't boot.
Oemv4 is not backward compatible with older releases.
oemv4 -> camera & volte & other improvements
and an other lineageos / sodp open source changes since my last build
ps: Camera is work in progress.
Oemv4 maybe comes tomorrow.
Click to expand...
Click to collapse
15.02.2020
feburary security patch level
fixed bugs, now my sony aosp release and this lineageos port should contain the same amount of bugs (aside from the stuff on the lineageos part).
Switched from alpha to beta version.
The only instability i found on my own xz2 is a crash at night in flightmode without charger.
Anything else doesn't crash it here.
Might be various reasons.
If anyone has the same bug, please provide logs in my github issue tracker.
(and please look if your logs contain more informations than my logs).
Click to expand...
Click to collapse
02.02.2020
the first lineageos 17.1 build based on the sodp device trees.
My vanilla sodp release and lineageos should share the same bugs.
Plus bugs / missing features in lineageos and bugs introduced by myself porting sodp to lineageos :silly:
sadly i can't upload it at the moment to android file host.
Their new "stackpath" ddos blocking solution banned me, because i tried to upload the rom in 6 browser tabs. :silly:
fixed
have fun!
Ps: Camera is work in progress.
Twrp 10 is not ready, so i sadly can't start develop one for the xz2, xz2c, xz3.
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
that's the reason i include opengapps pico for now.
And to use magisk, simply patch the boot.img by yourself in the magik manager app and flash it via fastboot.
Maybe you need to deactivate vbmeta, which wasn't the case at my site.
Gcam doesn't work with oemv3.
There is a library missing.
Click to expand...
Click to collapse
02.02.2020
The first LineageOS 17.1 build based on the SODP device trees.
My vanilla SODP release and LineageOS should share the same bugs.
Plus bugs / missing features in LineageOS and bugs introduced by myself porting SODP to LineageOS :silly:
Sadly I can't upload it at the moment to Android File Host.
Their new "Stackpath" DDOS blocking solution banned me, because I tried to upload the ROM in 6 browser tabs. :silly:
Fixed
Have Fun!
PS: Camera is work in progress.
TWRP 10 is not ready, so I sadly can't start develop one for the XZ2, XZ2C, XZ3.
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
That's the reason I include OpenGapps Pico for now.
And to use Magisk, simply patch the boot.img by yourself in the magik manager app and flash it via fastboot.
Maybe you need to deactivate vbmeta, which wasn't the case at my site.
GCAM doesn't work with OEMv3.
There is a library missing.
Click to expand...
Click to collapse
Nice work Martin!!!
I had looked forward to be released this rom
And i have a question to you.
Does this rom support VoLTE?
Orihamburger said:
Nice work Martin!!!
I had looked forward to be released this rom
And i have a question to you.
Does this rom support VoLTE?
Click to expand...
Click to collapse
Thank you
Yes, at least I can use VoLTE in my country with my provider.
You need to test it by yourself. [emoji14]
I need some help from testers for logs and observed behavior.
It seems that the phone crashes while sleeping in combination with the installed firmware on my XZ2.
Does this crash only happen when someone upgraded his phone to stock 10.0 first or does it also happen with a previously installed stock 9.0 rom?
https://github.com/MartinX3-AndroidDevelopment-LineageOS/bug_tracker/issues/1
MartinX3 said:
I need some help from testers for logs and observed behavior.
It seems that the phone crashes while sleeping in combination with the installed firmware on my XZ2.
Click to expand...
Click to collapse
I had the same on PE.
PE rom flashed over latest stock firmware, then latest aosp oem binary.
And always when I Iock phone for some time, impossible to wake up it. Only restart helps using volup+power.
P.S. now i'm on stock.
zhka said:
I had the same on PE.
PE rom flashed over latest stock firmware, then latest aosp oem binary.
And always when I Iock phone for some time, impossible to wake up it. Only restart helps using volup+power.
P.S. now i'm on stock.
Click to expand...
Click to collapse
Thank you
I'm curious if it is the same issue.
hi martin, thanks a lot for your work, a question, in this version the general stability of this rom is the same of your sonyaosp project? i will try today or tomorrow
nikkdib said:
hi martin, thanks a lot for your work, a question, in this version the general stability of this rom is the same of your sonyaosp project? i will try today or tomorrow
Click to expand...
Click to collapse
Thank you, you're welcome
In theory it only contains bugs from SODP and LineageOS :silly:
MartinX3 said:
Thank you, you're welcome
In theory it only contains bugs from SODP and LineageOS :silly:
Click to expand...
Click to collapse
ok i try to flash. now i have stock bugged android 10 firmware
edit: ok i flashed this rom and for now my phone seems doesn't crashed or freeze. i try to install gcam but gcam crash
nikkdib said:
ok i try to flash. now i have stock bugged android 10 firmware
edit: ok i flashed this rom and for now my phone seems doesn't crashed or freeze. i try to install gcam but gcam crash
Click to expand...
Click to collapse
Gcam should work with OEMv4
There is a library missing to run this application.
The XZ3 Dual file is corrupted. It is only 50MB in size
nickholtus said:
The XZ3 Dual file is corrupted. It is only 50MB in size
Click to expand...
Click to collapse
Thank you, but the dual sim version only contains the files different from the single sim version.
MartinX3 said:
Thank you, but the dual sim version only contains the files different from the single sim version.
Click to expand...
Click to collapse
Ahhh damnn, sorry my fault! Stupid mistake
Very promising release=) However, I need your help, Bro, cause I'm officially stuck with the stock=))) Before I used your OMNI for 6 months and it was completely fine just the camera wasn't working at all regardless of any fixes I've tried! After that, I switched my H8266 xz2 Dual to your SODP to try Android 10, which I didn't like after playing with it for a while. And now - I flashed latest 52.0.A.8.131 or newer 52.1.A.0.532 for the US device - I COULDN'T find the correct twrp as well as I CAN'T install OMNIrom. I have a simple question ==> besides the stock, which rom is stable enough here to have a working camera and TWRP. From what I see, almost each rom has some issues. Instead of Lineage 17, could you fix the links for working 16th version? FIX me if I'm wrong=)))
Mazurik said:
Very promising release=) However, I need your help, Bro, cause I'm officially stuck with the stock=))) Before I used your OMNI for 6 months and it was completely fine just the camera wasn't working at all regardless of any fixes I've tried! After that, I switched my H8266 xz2 Dual to your SODP to try Android 10, which I didn't like after playing with it for a while. And now - I flashed latest 52.0.A.8.131 or newer 52.1.A.0.532 for the US device - I COULDN'T find the correct twrp as well as I CAN'T install OMNIrom. I have a simple question ==> besides the stock, which rom is stable enough here to have a working camera and TWRP. From what I see, almost each rom has some issues. Instead of Lineage 17, could you fix the links for working 16th version? FIX me if I'm wrong=)))
Click to expand...
Click to collapse
Thank you
At the moment the source code of TWRP 10.0 is not available/usable, but is needed to create a TWRP with the 10.0 code environment.
Why you can't install omnirom?
The TWRP only work for the 9.0 ROMs at the moment and will be fixed in the future.
The LineageOS 16.0 release wasn't made by me and I can't do anything (except creating my own LineageOS 16.0 but my time/ressources are sadly limited :silly
does anyone know how well gcam works compared to stock camera on locked device?
tb_ said:
does anyone know how well gcam works compared to stock camera on locked device?
Click to expand...
Click to collapse
The camera driver is work in progress
The gcam workarounded missing features on 9.0.
Now on 10.0 we need to wait for OEMv4 for a working gcam.
Resurrection Remix Oreo
If you're not familiar with Resurrection Remix (RR), it's a very customizable and feature rich ROM. It's packed with some many great features like a notification ticker (like in the good ol' Kitkat days), styling changes, custom gestures, and more! RR is based on LineageOS. This is a build originally developed on by (russel5), but abandoned in favor of AospEx and Pie projects of his. Personally, I'm not a fan of the direction taken in Pie and will be sticking with Oreo. I'll be developing the rom further with features, bug fixes and enhancements. Any suggestions or bugs should be opened as an issue on the Github.
Please report any issues you have on the Github. The issue tracker helps me keep organized and on top of stuff.
Downloads
GitHub
Installation
1. Download firmware zip
2. Download OpenGapps/MicroG/Whatever
3. Push to phone
4. Reboot to recovery (recommend TWRP) and do a full wipe
5. Flash RR then whatever else after (Gapps, ect)
6. Reboot
7. ???
8. Profit
General Info:
If you have issues with the camera being green, make sure you update your firmware to the most recent Oreo one via newflasher. I will update this with information regarding this. It's been months since I did it so I need to remember and hunt the files down I used (which is hard since my last computer died and I switched to Linux). I'd backup your Drm keys before doing anything if you do.
Exclude when flashing:
* fotakernel.sin
* kernel.sin
* simlock.ta (if you have it)
* system.sin
* userdata.sin
* vendor.sin
Forced encryption is disabled. If you want it make sure to flash the boot img attached. Many users have bootloops so use at your own caution. To flash use fastboot flash boot boot.img
Special thanks to:
@modpunk
@russel5
Anyone else I'm forgetting
Source:
Repo
XDA:DevDB Information
[G8441, XZ1c] [8.1] Resurrection Remix v6.2.1 (Oreo), ROM for the Sony Xperia XZ1 Compact
Contributors
hockeymikey
Source Code: https://github.com/hockeymikey/android_device_sony_lilac
ROM OS Version: 8.x Oreo
Based On: LOS
Version Information
Status: Stable
Current Stable Version: 6.2.1
Created 4/19/2020
Last Updated 5/13/2021
Additional info
Changelog:
May 13th, 2021 - 6.2.1-2020.10.11
* Signature spoofing, tweaked building fixing issues
September 4th, 2020 - 6.2.1-2020.09.04
* First build, updated libraries, security update
April 20th, 2020 - 6.2.1-2018.11.08
* Last release from russel5
Has anyone tried it yet?
DerSteppo said:
Has anyone tried it yet?
Click to expand...
Click to collapse
Yes, very good rom but i find out on androidfilehost about half year, so old.
USB tethering doesnt work.
Plenty of functions.
Stable, fast, no lags, pretty battery acceptable, more than 1 day of battery life.
Display options from stock, stock camera works very good.
I think, we need upgrade RR to 7 or 8.
I am using it now for about week and its very good as daily.
And at this moment its way better than Q roms.
jurko217 said:
Yes, very good rom but i find out on androidfilehost about half year, so old.
USB tethering doesnt work.
Plenty of functions.
Stable, fast, no lags, pretty battery acceptable, more than 1 day of battery life.
Display options from stock, stock camera works very good.
I think, we need upgrade RR to 7 or 8.
I am using it now for about week and its very good as daily.
And at this moment its way better than Q roms.
Click to expand...
Click to collapse
You can't find the most recent version of the rom on AFH, I had to hunt it down from some random forum and the most recent one before that was unstable so wanted to get it out there for people to have. I really like RR. I'll test tethering, I thought it was fine but haven't really used it. Maybe I'll mess with 7 or 8 someday after I have this one developed alittle. I personally don't have any interest in Pie+.
Edit: USB tethering works fine for me. Must be an issue with your computer. I'm using Kubuntu 18.04 and works perfectly.
hockeymikey said:
You can't find the most recent version of the rom on AFH, I had to hunt it down from some random forum and the most recent one before that was unstable so wanted to get it out there for people to have. I really like RR. I'll test tethering, I thought it was fine but haven't really used it. Maybe I'll mess with 7 or 8 someday after I have this one developed alittle. I personally don't have any interest in Pie+.
Edit: USB tethering works fine for me. Must be an issue with your computer. I'm using Kubuntu 18.04 and works perfectly.
Click to expand...
Click to collapse
I am using Windows 8.1, but in other roms like stock or PE 10 USB tethering works. I push that on and no reaction in computer - networking.
If will be Havoc OS 2.x or BaikalOS, ill start interest in pie, because i had these roms in Mi Mix 2 and they was best. Havoc in general, can be compared with most functions with RR, Baikal from russia brats in battery life, performance and simplicity.
Idk if they dont arrive to XZ1c, but pie i liked was stock, Oxygen, Miui (with some bugs, but with future).
Still, oreo and nougat roms are older, but better in most things except mentioned roms.
jurko217 said:
I am using Windows 8.1, but in other roms like stock or PE 10 USB tethering works. I push that on and no reaction in computer - networking.
If will be Havoc OS 2.x or BaikalOS, ill start interest in pie, because i had these roms in Mi Mix 2 and they was best. Havoc in general, can be compared with most functions with RR, Baikal from russia brats in battery life, performance and simplicity.
Idk if they dont arrive to XZ1c, but pie i liked was stock, Oxygen, Miui (with some bugs, but with future).
Still, oreo and nougat roms are older, but better in most things except mentioned roms.
Click to expand...
Click to collapse
No idea, it has to be your computer I'm guessing. Make sure you're running the most recent version since that other versions found on the other thread is very buggy. Noted on them.
> Forced encryption is disabled. If you want it make sure to flash the boot img attached. Many users have bootloops so use at your own caution. To flash use fastboot flash boot boot.img
Where's the boot.img?
asdf2345 said:
> Forced encryption is disabled. If you want it make sure to flash the boot img attached. Many users have bootloops so use at your own caution. To flash use fastboot flash boot boot.img
Where's the boot.img?
Click to expand...
Click to collapse
It's in the zip file.
Got a new update out https://github.com/hockeymikey/android_device_sony_lilac/releases/tag/6.2.1-2020.09.04
Check it out and let us know how it works. Seems stable on my end from testing.
How does Resurrection Remix compare to CrDroid?
asdf2345 said:
How does Resurrection Remix compare to CrDroid?
Click to expand...
Click to collapse
No idea, can't remember testing out the Pie CrDRoid on here. I'm not a fan of Pie+ so it didn't interest me. Should test and report in, looks like they are similar being LOS based with decent amount of customization. CrDroid has signature spoofing, but I'm making a build with that added in for RR as I type. But yeah, let me know and what other features that CrDroid has that looks cool.
hockeymikey said:
Resurrection Remix Oreo
If you're not familiar with Resurrection Remix (RR), it's a very customizable and feature rich ROM. It's packed with some many great features like a notification ticker (like in the good ol' Kitkat days), styling changes, custom gestures, and more! RR is based on LineageOS. This is a build originally developed on by (russel5), but abandoned in favor of AospEx and Pie projects of his. Personally, I'm not a fan of the direction taken in Pie and will be sticking with Oreo. I'll be developing the rom further with features, bug fixes and enhancements. Any suggestions should be opened as an issue on the Github.
Downloads
GitHub
Installation
1. Download firmware zip
2. Download OpenGapps/MicroG/Whatever
3. Push to phone
4. Reboot to recovery (recommend TWRP) and do a full wipe
5. Flash RR then whatever else after (Gapps, ect)
6. Reboot
7. ???
8. Profit
General Info:
If you have issues with the camera being green, make sure you update your fireware to the most recent Oreo one via newflasher. I will update this with information regarding this.. It's been months since I did it so I need to remember and hunt the files down I used (which is hard since my last computer died and I switched to Linux). I'd backup your Drm keys before doing anything if you do.
Exclude when flashing:
* fotakernel.sin
* kernel.sin
* simlock.ta (if you have it)
* system.sin
* userdata.sin
* vendor.sin
Forced encryption is disabled. If you want it make sure to flash the boot img attached. Many users have bootloops so use at your own caution. To flash use fastboot flash boot boot.img
Special thanks to:
@modpunk
@russel5
Anyone else I'm forgetting
Source:
Repo
XDA:DevDB Information
[G8441, XZ1c] [8.1] Resurrection Remix v6.2.1 (Oreo), ROM for the Sony Xperia XZ1 Compact
Contributors
hockeymikey
Source Code: https://github.com/hockeymikey/android_device_sony_lilac
ROM OS Version: 8.x Oreo
Based On: LOS
Version Information
Status: Stable
Current Stable Version: 6.2.1
Created 2020-04-19
Last Updated 2020-04-20
Click to expand...
Click to collapse
Hi, i have tested update of this rom and found out 2 system bugs.
First thing - bootloop. I flashed it like usually with newest BitGapps arm64 8.1.0 v15 and magisk. BitGapps caused bootloop. Clean install with only magisk booted, but magisk app not installed, so i had to install Magisk Manager manually, root installed.
Second boot into recovery and flash BitGapps caused no google store app, like before, so i flashed MindGapps and it works.
It is mine problem, i using alternative gapps but good to notice.
Sometimes not smooth, torn animations. More often than older build.
Red blinkings: Right after successful boot, after some clicks i see weird red blinkings on display. Something similar like in developer options turn on display blinkings after stress GPU/CPU but this happen in random time and is not turned on. Is little bit enyoying, its not happened in older 2018 build.
So my decide will be flash again .228 firmware and stay with Havoc OS, now i used version 3.8 for month and i can say, now is android 10 in lilac flawlessly done. I like more older Oreo UI but fix issue with blinking and i will be your satisfied user.
Thank you and best regards.
jurko217 said:
Hi, i have tested update of this rom and found out 2 system bugs.
First thing - bootloop. I flashed it like usually with newest BitGapps arm64 8.1.0 v15 and magisk. BitGapps caused bootloop. Clean install with only magisk booted, but magisk app not installed, so i had to install Magisk Manager manually, root installed.
Second boot into recovery and flash BitGapps caused no google store app, like before, so i flashed MindGapps and it works.
It is mine problem, i using alternative gapps but good to notice.
Sometimes not smooth, torn animations. More often than older build.
Red blinkings: Right after successful boot, after some clicks i see weird red blinkings on display. Something similar like in developer options turn on display blinkings after stress GPU/CPU but this happen in random time and is not turned on. Is little bit enyoying, its not happened in older 2018 build.
So my decide will be flash again .228 firmware and stay with Havoc OS, now i used version 3.8 for month and i can say, now is android 10 in lilac flawlessly done. I like more older Oreo UI but fix issue with blinking and i will be your satisfied user.
Thank you and best regards.
Click to expand...
Click to collapse
What's special about Bitgapps? That's really strange, can you grab a log on boot using adb? If not, go to https://github.com/hockeymikey/android_device_sony_lilac/issues and make an issue and help me track it and I'll get around to testing it. It'll help keep in touch with you and solve it especially if for some reason I can't recreate it for some reason. I got that red outline too and I thought it was just me. It went away for me so might be temporary on the initial install. If you could create an issue for that too on the previous link so I can keep you updated for that too.
jurko217 said:
Hi, i have tested update of this rom and found out 2 system bugs.
First thing - bootloop. I flashed it like usually with newest BitGapps arm64 8.1.0 v15 and magisk. BitGapps caused bootloop. Clean install with only magisk booted,......
Click to expand...
Click to collapse
So I did some testing. The red blinking is gone, that fix will be included in the next release (which includes signature spoofing and updates so a few system libraries like base, native and lineage-sdk). BitGapps doesn't cause a bootloop for me. It was kinda buggy, which is odd and crashes. I'll see what I can find for it. Magisk works fine for me. Make sure it's the most recent version but I was using old versions too as well as new so I don't know.
Hm, with usb-debugging enabled, it dont ask for permission and dont save the adb-key, so u arent able to adb into twrp. But ADB to the booted device works. Anybody else got this?
muebbel said:
Hm, with usb-debugging enabled, it dont ask for permission and dont save the adb-key, so u arent able to adb into twrp. But ADB to the booted device works. Anybody else got this?
Click to expand...
Click to collapse
That's a TWRP reason. Whoever built it disabled adb in it. I repackaged twrp to allow adb for myself, I can share it if you want.
This will be nice
And... i get this red-frame too if some higher cpu-usage happens. What did u do against it?
Encrypting the device ends in a infinity-loop at the "Encrypting... time remaining 00:00.."-Screen.
Maybe i missed something (tried with and without the boot.img for force-encryption)?
muebbel said:
This will be nice
And... i get this red-frame too if some higher cpu-usage happens. What did u do against it?
Encrypting the device ends in a infinity-loop at the "Encrypting... time remaining 00:00.."-Screen.
Maybe i missed something (tried with and without the boot.img for force-encryption)?
Click to expand...
Click to collapse
I think this is the correct one, let me know if not. Red frame is an issue I caused with how I built it, building it as a dev build not production. It's fixed on my device. I'll eventually get a new build out, I've been waiting to get OpenDelta done for OTA updates first to streamline the updating process. Maybe I should push one out sooner since the build on here I don't think is really that usable while my phone one I'm using daily. I haven't tested encryption honestly. I'll have to look into. If you could make an issue on github with every little detail to help me track and fix, that'd be cool.
Hmm, same problem -> adb devices -> unauthorized
And there is no dialog for accept/store the ADB-Key if u plugin the PC for the first time.
So.. i was using newflasher to flash the stock oreo rom and guess what... the stock rom does the same... so if u flash the stock rom (47.1.A.16.20) without remove any files from the stock-rom-directory and the adb_key still exists... where can it be?
BTW: i can access the stock-rom with adb add the first start at the "Welcome"-Screen... but twrp cant find/use the key which is stored $somewhere