Related
Hi to all,now i'll present you one of my ROMs for GALAXY 5:it's the
ImPaCt ROM
Features :
1)Very fast and stable
2)Really great battery
3)No crashes
4)Based on CM7
5)Adw launcher
6)Kernel supports OC
7)Full tweaked
DOWNLOADs
1)ROM v2 :
2)ROM V1 :
3)GApps [ GB ] : HERE
CHANGELOGs
Code:
V1 : [B] INITIAL RELEASE [BUGS AND CRASHES OPENING DRAWER]
V2 : FIXED CRASHES AND LAGS,EDITED BUILD.PROP
V3 : STILL UPLOADING :crying:[/B]
INSTALLATION
1)Make sure that you're coming from a ROM which has CWM
2)Download the ROM and put it in the g5's SDCARD
3)Reboot in CWM
4)Make a Nandroid Backup [ OPTIONAL ]
5)Make 3 wipes (data/factory reset,cache,dalvik cache)
6)Install zip from sdcard>choose zip>"selectROM and install it
7)Do again 3 wipes
8)Install zip from sdcard>"select GApps and install them"
9)Reboot
10)Enjoy
somes shots?
Thread closed, please upload your kernel source code and because your ROM is based on CM7 also upload your ROM source code.
v30J updated 2016-05-29
[Marshmallow 6.0]
Added from the stock v30J base
system.img
modem.img (v21c)
boot.img
rpm.img
tz.img
cust.img
Download -> https://mega.nz/#!GRtHmILa!r_762ZiITXP1GflDGq7k_Wr-c2SrKbvEP7LGS7dGMSE
Old versions
v30F updated 2016-04-06
[Marshmallow 6.0]
Added from the stock v30F base
system.img
modem.img (v21c)
boot.img
rpm.img
tz.img
cust.img
Download -> https://mega.nz/#!LI1SEDyK!LclININemEv4ArXMS2OHq0jq60ZL4-P9U-86BE9tlHk
v30E updated 2016-04-02
[Marshmallow 6.0]
Added from the stock v30E base
system.img
modem.img
boot.img
rpm.img
tz.img
cust.img
Download -> https://mega.nz/#!WRVHwRSJ!pY0OltUe04dV_I6727DAyCrZqbV1Sbvr_NseWZUFDwg
v30C updated 2016-03-15
[Marshmallow 6.0]
Added from the stock v30C base
system.img
modem.img (21c)
boot.img
rpm.img
tz.img
cust.img
Download -> https://mega.nz/#!ic9lyIBI!9lnGmCgMnWz-M9by5YtGwqf__kNx9TWfdovsU-T4P6k
v30B updated 2015-12-18
[Marshmallow 6.0]
Added from the stock v30B base
system.img
modem.img (v2 is from 21c base)
boot.img
rpm.img
tz.img
cust.img
Download -> https://mega.nz/#!OINCkDxZ!AcGrjxytbMVAjFFAh9y8uUP6jFvLKqqQmmDJGZRTTa4
Download v2 (modem from v21c) -> https://mega.nz/#!OIlwGLKS!LlcNIImHKvrgubAUthDgV3cudMKMYEzSt_ikHlWj3yY
v21B updated 2015-12-18
[Lollipop 5.0]
Added from the stock v21C base
system.img
modem.img
boot.img
rpm.img
tz.img
cust.img
recommended install info:
Full wipe + format DATA
Flash rom
Reboot and let android upgrade
Enter twrp and flash supersu zip
Done
Download v21C -> https://mega.nz/#!SUVm1A4R!Pu6ePPfTIHcnldyrv4MiL6bRfFYjMySjU1XDlp5neKU
v21A updated 2015-11-04[/SIZE]
Added from the stock v21A base
system.img
modem.img
boot.img
rpm.img
tz.img
cust.img
recommended install info:
Full wipe + format DATA
Flash rom
Reboot and let android upgrade
Enter twrp and flash supersu zip
Done
Download v21A -> https://mega.nz/#!OBV0gDaa!APZeieS6t7z3dwt-3wRyaRMJkywNskmER97fEUVIGG8
Mirror -> https://www.androidfilehost.com/?fid=24269982086987955 thanks @GFXi0N
md5: e14a3c2eba4f4e44e73117c512d8dcd4
v20W updated 2015-09-19
Added from the stock v20W base
system.img
modem.img
boot.img
rpm.img
tz.img
cust.img
recommended install info:
Full wipe + format DATA
Flash rom
Reboot and let android upgrade
Enter twrp and flash supersu zip
Done
Download v20W -> https://mega.nz/#!DJ8QSBbA!5mjxJkY1zmPha3hGEF1-IOkB-37B_JeGtR1j9keeJwg
Mirror -> https://www.androidfilehost.com/?fid=24052804347819623 Thanks to @GFXi0N
md5: 08d550490ff64f8023e99e82e238f178
D85520W kernel with SELinux permissive and supporting init.d (no run-parts included, busybox etc is needed for init.d support) -> http://forum.xda-developers.com/showpost.php?p=62925475&postcount=1730 by @6ril1
NEW! v20U updated 2015-09-06
Added from the stock v20U base
system.img
modem.img
boot.img
rpm.img
tz.img
cust.img
recommended install info:
Full wipe + format DATA
Flash rom
Reboot and let android upgrade
Enter twrp and flash supersu zip
Done
Download v20U -> https://mega.nz/#!vFU1lDRC!qiOBNvVPmFcHWNKt-8QcIegWmvGA7ZFSBLRhdnqWQts
MD5: 43f5b759524ccf3c06b3355786eb84a5
Mirror -> https://www.androidfilehost.com/?fid=24052804347809860 thanks to @GFXi0N
If any of you guys like to have a kernel with init.d support and SELinux set to permissive (based on v20U) it can be found here -> http://forum.xda-developers.com/showpost.php?p=62692612&postcount=1479 made by @6ril1 :good:
v20T updated 2015-08-29
Added from the stock v20T base
system.img
modem.img
boot.img
rpm.img
tz.img
cust.img
recommended install info:
Full wipe + format DATA
Flash rom
Reboot and let android upgrade
Enter twrp and flash supersu zip
Done
Download v20T -> https://mega.nz/#!GV1WQZYT!ZRNZW3_hh77KFy5qGADE0ej5w1fhaPSYAsolZ7CM_NM
Mirror -> https://www.androidfilehost.com/?fid=24052804347806584 Big thanks to @GFXi0N fot this mirror.
md5: 67b2091f0ae06902cb4a1ea8f803817b
v20P updated 2015-05-15
Added from the stock v20P base
system.img
modem.img
boot.img
rpm.img
tz.img
cust.img
recommended install info:
Full wipe + format DATA
Flash rom
Reboot and let android upgrade
Enter twrp and flash supersu zip
Done
Download v20P ->https://mega.co.nz/#!DEg2yS4K!dNRH4jnSWtQQidx8OB2b6BEe4oB6CIpzc9uRpIuPw-4 (updated kernel)
Mirror -> http://forum.xda-developers.com/showpost.php?p=62364815&postcount=1396 thx to @thedoginthewok
HTML:
LG have patched the boot in v20p so i can not bump it, if anyone like to give it a shoot here it is.
http://www.fildirekt.se/dl/1431725525.rar
Kernel fixed by @6ril1 (v20p) :good:
Kernel only download -> http://www.filedropper.com/20pkernelbumpedby6ril1
v20i updated 2015-03-07
Added from the stock v20i base
system.img
modem.img
boot.img
rpm.img
tz.img
cust.img
recommended install info:
Full wipe + format DATA
Flash rom
Reboot and let android upgrade
Enter twrp and flash supersu 2.40
Done
Download v20i -> https://mega.nz/#!OU5HmaCS!Bf_txTpgz8YUjtc4HG_txr0maCnn4ASWyl92KFONyJY
v20H updated 2015-01-30
Added from the stock v20H base
system.img
modem.img
boot.img
rpm.img
tz.img
cust.img
Download v20H -> https://www.dropbox.com/s/yr71wikij6o9xk9/D85520H.zip?dl=0
Mirror -> https://mega.co.nz/#!qFRzhLjT!8IbwVURcfMjYeKI0KVdwG5StsiRJeu4Ek0E1b0WxowM
v20F updated 2014-12-31
Added from the stock v20F base
system.img
modem.img
boot.img
rpm.img
tz.img
cust.img
recommended install info:
Full wipe + format DATA
Flash rom
Reboot and let android upgrade
Enter twrp and flash supersu 2.40
Done
Download version 20F -> https://mega.co.nz/#!CA4R1bCA!ayzDwj9mDTs42HzPmKh0u5jKZqGrLpllrjelxVOUBFg
v20E updated 2014-12-16
Added from the stock v20E base
rpm.img
tz.img
cust.img
Kernel is now total stock (New SuperSu 2.40 should work fine with stock kernel now)
recommended install info:
Full wipe
Flash rom
Reboot and let android upgrade
Enter twrp and flash supersu 2.40
Done
Thanks for @Cloudyfa for the info
http://forum.xda-developers.com/showpost.php?p=57541255&postcount=428
Download rom--> https://mega.co.nz/#!uEggBLrR!tqFzm8PH_5FoFh7lKgfqLlOzGBPyCKDjhVRmmIPc2Gw
Download SuperSu -> http://download.chainfire.eu/641/SuperSU/UPDATE-SuperSU-v2.40.zip
LGD855 version D85520E_00 2014-12-16
Latest Lollipop version D85520E
System, kernel and modem.
The kernel is modded by @Skin1980
1: Make a full wipe
2: Flash the rom zip file from recovery.
3: Flash Supersu zip
4: Done
Download rom -> https://mega.co.nz/#!KVo1XRxY!FZS7SqXEg58G_A-HahKcJExTC4IYrA4fZwlXyTUuKAk
Download SuperSu -> http://download.chainfire.eu/641/SuperSU/UPDATE-SuperSU-v2.40.zip
Code:
[B]Big thanks to the number 1 guy [user=2174433]@Skin1980[/user], he is the one modding the kernel!![/B]
LGD855 (POLAND) version D85520D_00
I made a flash zip from the latest Lollipop version D85520D Poland.
System, kernel and modem.
The kernel is modded by @Skin1980 -> SElinux set to permissive; - init.d support - root support! :good:
1: Make a full wipe
2: Flash the rom zip file from recovery.
3: Flash Supersu zip
4: Done
Download rom -> https://mega.co.nz/#!WdhC1QzT!ZuJxc_dourI6EWHZ4AS4dksjNPtOLrG-dm8Xx26JyvY mirror -> http://www.filedropper.com/d85520d
Download SuperSu -> http://download.chainfire.eu/637/SuperSU/BETA-SuperSU-v2.38.zip
Thx to @RiCkS_ESP for the links
Thx to @Skin1980 for letting me use his new modded kernel
Thx to @Chainfire for SuperSu
Two bonus rom added - D85520S and D855K20V
D85520S.zip -> https://mega.nz/#!yNs0mSYA!IIujfNk9C0MUlpS45QaIRQUOxMrHR2-jLqTBcsroBuY
Mirror -> D855K20V: https://www.androidfilehost.com/?fid=24052804347811451 md5: b179f32bfd16198661b97b22ea4e3af2 (thanks to @GFXi0N)
D855K20V.zip -> https://mega.nz/#!PV1VkTqT!6toMOOKUAwT_HgZdgw63B_tfyI7hDpkHlB_EuBBbTS0
Mirror -> D85520S: https://www.androidfilehost.com/?fid=24052804347811452 md5: 8c4d856623744c34a7cf9ad265baa083 (thanks to @GFXi0N)
Stock boot.img doesn't need bumping.....
robalm said:
LGD855 (POLAND) version D85520D_00
I made a flash zip from the latest Lollipop version D85520D
System, kernel and modem.
Flash the zip file from recovery.
OBS the boot.img is not bumped, you can flash Rin Kernel 1.1, or wait for the stock boot.img to be bumped.
Download -> https://mega.co.nz/#!vYxSDTYa!q2nen4zciiBBLMSMYi8gur-UHm35vE-dnbJcUN-Idvs
thx to @RiCkS_ESP for the links
Click to expand...
Click to collapse
I have used 20C bumped kernel and it is working fine if you want to use a stock patched kernel.
L10nH34Rt said:
Stock boot.img doesn't need bumping.....
Click to expand...
Click to collapse
Yes if you want to mantain old bootloader and recovery! otherwise you can flash the whole kdz
Can anyone tell me what is the kernel version that either V20C or V20D use ?
Is it 3.4 or 3.10 ?
jodvova said:
Can anyone tell me what is the kernel version that either V20C or V20D use ?
Is it 3.4 or 3.10 ?
Click to expand...
Click to collapse
3.4, lg has not implemented 3.10
jodvova said:
Can anyone tell me what is the kernel version that either V20C or V20D use ?
Is it 3.4 or 3.10 ?
Click to expand...
Click to collapse
3.4.0
This rom flash from recovery ??rom rooted ??
Any differences in compare to 20C?
robalm said:
LGD855 (POLAND) version D85520D_00
I made a flash zip from the latest Lollipop version D85520D
System, kernel and modem.
Flash the zip file from recovery.
OBS the boot.img is not bumped, you can flash Rin Kernel 1.1, or wait for the stock boot.img to be bumped.
Download -> https://mega.co.nz/#!vYxSDTYa!q2nen4zciiBBLMSMYi8gur-UHm35vE-dnbJcUN-Idvs
thx to @RiCkS_ESP for the links
Click to expand...
Click to collapse
I have extract the kdz 20d with Pyton 2.7 in cmd and extract the dz. files with LG Firmware exanct and now have many bin Files...
What use you for Tool and change in img...?
Or gives other Method for extract kdz in img....?? Thx for your Help
---------- Post added at 04:22 PM ---------- Previous post was at 04:19 PM ----------
LukaszMPL said:
Any differences in compare to 20C?
Click to expand...
Click to collapse
20d have the Patch for Bug in Circle Case....included...
And the 20d is faster and run better like 20c and have in 20d no Problems with Trusted....and the Google Play Services 6.5.87 (434)..in 20c is 446 and many Trubble...
@sooti
Could you make a bumped version of it
?
drdoulittle said:
20d have the Patch for Bug in Circle Case....included...
And the 20d is faster and run better like 20c and have in 20d no Problems with Trusted....and the Google Play Services 6.5.87 (434)..in 20c is 446 and many Trubble...
Click to expand...
Click to collapse
20c also have quick circle fixed. Thanks, anyway I will not flash it until Android Now HD made from that version is released
@drdoulittle
[TOOL] KDZ and TOT Extractor http://forum.xda-developers.com/showthread.php?t=2600575
Select all system.bin and press "Merage System-bin"
If I flash this rom will my imei number go away? I have g3 with cloned imei.
Can anybody put it to the another File Hosting ? My download manager can't work with Mega.
I assume this isn't rooted.
lexman098 said:
I assume this isn't rooted.
Click to expand...
Click to collapse
You can (must) use any bumped kernel.
Idol400 said:
You can (must) use any bumped kernel.
Click to expand...
Click to collapse
So root is strictly a kernel-level thing?
lexman098 said:
So root is strictly a kernel-level thing?
Click to expand...
Click to collapse
no, with lollipop you should have a custom recovery and so the kernel should be bumped. then you can root!
In short: it's about the boot-image, not the kernel.
tobitege said:
In short: it's about the boot-image, not the kernel.
Click to expand...
Click to collapse
But don't we need a bumped and modified boot image for working root?
What it is
It is a self twrp build from the official 3.0.2-0 git sources on a omnirom tree with data decryption support. Also some flags are tuned to enable booting for newbootloaders (> 15.4)
This recovery is fully working for my sony xperia z3 (D6603) since september 2015. I give it 'as it is'.
Disclaimer
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* 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 me for messing up your device, I will laugh at you.
*
*/
Who can use it
it is only for z3 and unlocked bootloaders. It should work with
- phone where the sony TA update patch is appliedor
- all AOSP based rom which support FOTAKernel recoveries extraction (extract_elf_ramdisk), ask your rom maintainer.Since 2017-03-16 release this recovery use apps_logs partition as a workaround for N based roms, this will break stock roms!
LeonidasTurk said:
Sony Xperia devices don't have recovery partition. Instead of this in custom kernels is used recovery-in-boot conception with two-stage boot (ramdisk-recovery is packed inside main ramdisk). And there is partition called FOTAKernel that is used for installing official FOTA (firmware-over-the-air) updates. After unlocking your bootloader it partition becomes redundant, because you cannot use OTA function anymore. So it may be used for storing recovery ramdisk. And this very useful future was implemented by a xda member, he developed utility extract_elf_ramdisk https://github.com/Dees-Troy/extract_elf_ramdisk (it is merged to almost all kernels for Sony devices), it extracts recovery ramdisk from FOTA partition instead of using regular one from boot image. So even after updating or changing your kernel or ROM you don't lose your current recovery!
Click to expand...
Click to collapse
Actually it had been tested with CyanogenMod, and SlimRom as I know.
(tested only on D6603 version but should work on D6602,D6643,D6653) let me know if it work for you
The bootloader/reboot pain
From my experience there is 3 versions of the s1 bootloader for D66x3:
s1 D66x3 features:
LA3.0_L_15.4 : provide basic boot functionality, you can only boot in your boot partition.
LA3.0_L_37 : provide normal boot & recovery boot functonality (boot partition & FOTAKernel partition) but doesn't provide reboot to recovery functionality.
LA3.0_L_Hero_17 : (not yet tested): same as l_37 but correct the reboot in recovery bug.s1 D66x3 installation:
LA3.0_L_15.4 : is preinstalled. (.200 and above)
LA3.0_L_37 : is installed with M (.575)
LA3.0_L_Hero_17 : is installed with N preview (.?)Some roms flash other version of s1 that i never test (i only upgrade my bootloader with emma)
Check the s1 version:
Code:
getprop ro.boot.s1boot
What is working
Everything =)
backups
backups on encrypted partitions
restore
restore on encrypted partitions
all settings
change partitions type (f2fs/ext4)
flash zip
reboot
phone doesn't overheat and battery consumption is reasonable
/data decrypt
accessing recovery with new bootloader version (S1_Boot_MSM8974AC_LA3.0_L_37)
Brightness
usb otg
f2fs partition decryption
What is not working
wipe data buton (workaround by format, change type) --> should be ok since 2016-07-14 release.
reboot to recovery. I'm looking for documentation on new bootloader... --> workaround in progress --> should be ok for kernel with extract_elf_ramdisk
with old bootloader (< 15.4: check your cmdline) --> in progress --> should be ok for kernel with extract_elf_ramdisk. Let me know
What is not tested
f2fs partition decryption --> ok on 2016-07-16
what I forget, ask and I test asap
ToDo
create a zip to update this recovery --> re self signed zip since 2015-12-26 builds
change the 'power profile' in use when in recovery mode --> governor changed to 'ondemand' (2015-12-19)
create a VM for weekly builds --> done with jenkins (2016-02-17)
create a folder on webserver for weekly build --> Url will come soon (2016-02-17)
publish my files on a VCS --> https://github.com/nailyk-fr
update my blog to make a full (french) compiling guide -> ENOTIME. Ask here if you need.
make recovery functional for the 'full boot' process released by sony --> ok since 2016-01-09 builds
How to build
Follow the official twrp compiling guide (I start from omnirom tree),
If you are building from omni trees you do not need to change something as device have now official support.
breakfast z3
mka recoveryimage
wait a half hour and it's done
Reading CyanogenMod porting guide was very helpful.
2017-03-17: change manifest
2016-11-05: change manifest
2016-04-14: added the manifest repo url.
2016-03-07: update manifest.xml
2016-02-14: update manifest.xml
2016-02-07: switch to omnirom build tree (except kernel due to f2fs). Manifest is no more up-to-date
2016-01-15: change manifest to include z1&z1c
2016-01-13: add github fork links
2016-01-09: new twrp.fstab
2016-01-07: add patch link for the device/sony/shinano-common
2015-12-26: twrp.fstab & BoardConfigCommon.mk are no more up-to-date. I need to publish it on a public VCS but for now it's q&d. When job is done in a cleaner way a publish all the sources. If you need/want it before ask me and a provide a zip.
How to install
With a first rom installation with extract_elf_ramdisk support:
Ex: Coming from stock rom and installing CyanogenMod:
Follow the cm installation guide, and replace step 4 by:
download and check md5/sha1,
flash cyanogenmod kernel with:
Code:
fastboot flash boot boot.img
flash recovery by using command:
Code:
fastboot flash FOTAKernel <filename>
then reboot with
Code:
fastboot reboot
You can now continue the cm installation guide.
Via fastboot:
download and check md5/sha1,
reboot your phone in fastboot mode,
flash recovery by using command:
Code:
fastboot flash FOTAKernel <filename>
or
Code:
fastboot flash recovery <filename>
Via zip:
You need a custom recovery (like twrp/cwm) supporting flashing zip files,
Download zip to your internal/external sd,
Check md5/sha1,
Reboot to recovery,
flash zip.
Thanks to
@shoey63
@optimumpro
@_infected
@Micha_Btz
@frabe8378910
Team Win
Version Information
Created: 2015-12-18
Last Updated: 2018-03-28
Status: Work in progress --> stable (since 2016-07-16 build)
It's a self build version of twrp. I follow the official twrp compiling guide and add files for z3 (D6603 version in this case) and some 'compiling tricks' to add keymaster/keystore support in recovery to finally support encrypted /data partitions.
( From @LeonidasTurk's kernel thread, this build should work with other models but it not tested! Use it at your own risk, unlocked bootloaders only obviously)
official twrp compiling guide: http://forum.xda-developers.com/showthread.php?t=1943625
official CynogenMod z3 (D6603) thread: http://forum.xda-developers.com/z3/development/rom-cyanogenmod-12-nightlies-xperia-z3-t3010201
I'm not affiliated to TeamWin or CyanogenMod.
Report a problem link
Releases
Before flashing, read carefully the 'Who can use it' part and 'How to install'. If you are unsure, feel free to ask.
2018-03-28 single/unified:
FOTAKernel/recovery binary:
md5: 24cb9f0f64b2d62ef7798957932cc918
sha1: dd61d3f145f25a22b9f4eb9a6c0ec7a6eb92af0e
download mirror (fr)
Changelog
[*] Old boot process is broken. Will only works with new bootloader (See OP top)
Fix Oreo encryption. Need working /system!
[*] Warning this recovery cannot be used with stock roms as it use /misc for rom/recovery communication.
Old releases:
2017-10-02 Single:
FOTAKernel/recovery binary:
md5: 0b4ffccf31e201006937717a98bc8849
sha1: a755e659b4f96b2106b99c310042b8a29475266c
download[/INDENT]
Changelog
Codename fix
[*] Warning this recovery cannot be used with stock roms as it use /misc for rom/recovery communication.
2017-09-28 Single:
FOTAKernel/recovery binary:
md5: c8a004a1aa6a8abd8e85f010fce04f44
sha1: 375f3e48fbdf960970a795436e1b404d9d228fc2
download[/INDENT]
Changelog
Lots of improvement (twrp side)
Lots of changes on trees
adb backups are broken for now, don't use them!
Adjusted functionalities for our device
[*] Warning this recovery cannot be used with stock roms as it use /misc for rom/recovery communication.
2017-07-27 Single:
FOTAKernel/recovery binary:
md5: ad3279f0f4e761c193f2c1296789ac98
downloadflashable zip:
md5: 8acf3ea839ecd11f971032e292be7a8a
download
2017-07-27 Dual:
FOTAKernel/recovery binary:
md5: 7dea87dd9ab920931a769632dc054620
downloadflashable zip:
md5: e4aa892b4fbd2510eeb4e7f6dba8d7e5
download
Changelog
Don't remember
[*] Warning this recovery cannot be used with stock roms as it use /misc for rom/recovery communication.
2017-03-17:
FOTAKernel/recovery binary:
md5: 3f853b388621f60b57d6a56cbf91b8ed
sha1:
downloadflashable zip:
md5: f5984afeb6dc1f2b4bed570950b67445
sha1:
download
Switch back to 3.4 kernel (LineageOS 14.1)
Resolve some apps_logs partition problem
[*] Some functionality are not working (twrp related)
[*] Warning this recovery will break stock roms as it use /misc for rom/recovery communication.
2016-12-23:
FOTAKernel/recovery binary:
md5: b083f6c9594df72497fd647e5cef41c7
sha1: 0d83215e473d89f4586b9bd4ce408cafccf12782
downloadflashable zip:
md5: 7c20318900825eb6e7b814bc433d6c1c
sha1: 75d9e650811b4067b2d8beac26b6e11faca8d3ac
download
Switch to 3.10 1.3.3 (if you experienced problem use the 2016-10-17 version and report with log please)
Add app_log to fstab
2016-10-17:
FOTAKernel/recovery binary:
md5: 5926dcd958da084bb7d67e6f8279bc2c
sha1: x
downloadflashable zip:
md5: ba7abccc3a36dd2ad843b671c0935a44
sha1: faf863efd5a2e19c341e76d4e3bb8e26355a4c7a
download
Periodical build (some corrections bugs from twrp, init problem correction from cm)
still on 3.10 kernel, switch to 3.4 planned.
[*] Maybe a bug into twrp for android <= 5.1 flashing/restore into empty /system partition. Be careful!
2016-07-16:
FOTAKernel/recovery binary:
md5: 4d4316c266b1c9b737113e1a0166cbc4
sha1: 3ca7798021d4845ddc6814102abfc7c08a3bdee0
downloadflashable zip:
md5: abda5283b200eab0c115e8fd0a5e2196
sha1: e02bb10f69e71df10948a9f124c15ab0a627dad8
download
Correct fstab errors
[*] Apparently there is delay in partition opening due to the twrp implementation of adopted storage. I'm currently trying to fix it.
2016-07-14:
FOTAKernel/recovery binary:
md5: 1e76c989b36ff46657e59e3054ccb704
sha1: 9135cbd75ddb5b2611a24a31b372d841e9c6a69d
downloadflashable zip:
md5: 1da3efe239917ed8872638d4d07d7b9d
sha1: 23ff50355b70495dbf4a6b0ef72acadc324ee832
download
change fstab to make wipes easier
lots of improvements/corrections in twrp tree from TeamWin team
2016-04-14:
FOTAKernel/recovery binary:
md5: 70a22897f6b7cace772cd58e7846f224
sha1: ad11321805c1f91fe2500377baaee9b60b53340b
downloadflashable zip:
md5: f07e9d242b249d2c39388203e6a9eb70
sha1: 44f8a91b0c10b3c667246bd664e923d6d884dbdb
download
Change selinux policies (use xen0n repo)
Twrp flags to restore compatibility with old boot process
This build is a major' release which should restore compatibility with old bootloader.
please report feedback as I can know if I need to continue this way .
create a git repo to push local manifests files
for now my Jenkins is off --> added to the todo list
bootloop workaround kernel:
2016-03-07:
md5: b674a8aa843d9be6d801ada018006141
sha1: 22f7b9ecacb262dd6788fc22ac27e1a7c7265226
download
This is a cyanogenmod kernel where I remove the Dees_Troy 'extract_elf_ramdisk'. This way, if there is a soft reboot to recovery the phone restart cyanogenmod and doesn't go to bootloop. I don't try other rom with with kernel.
2016-03-07:
FOTAKernel/recovery binary:
md5: b5f878a70d7663c4a1d89c7b2668ec56
sha1: 87c278b5317b32c383ad0b2a97452843b37b9b3e
downloadflashable zip:
md5: 89de508f23adcede8967c5a61717e7e4
sha1: 6a59626204ef66614e9fa29635749953b7c6052d
download
resync with omnirom tree
change version number according to twrp.me
2016-02-14:
FOTAKernel/recovery binary:
md5: 69f3852c616472e49c5aaa1120a02a64
sha1: b62bc394849d6c0d918492b4472891a1a2128910
download alternativeflashable zip:
md5: 0aebbbc8e2f881ebef5dc5856060c668
sha1: a6979856c31f0efbf34a8470d7155d5c2a4fbcd5
download alternative
A few releases ago (2016-02-07) device was named leo instead of z3 so flashing zip could fail!
Improve display enabling hardware acceleration
tune some twrp flags
cleanup device tree
2016-02-08:
FOTAKernel/recovery binary:
md5: 6326926e5c46acc80fb925cb2838b05d
sha1: 3fb1a375121fef9b7690c6d556d5af934879ff66
download alternativeflashable zip:
md5: 0cdac0861f1a395706616ff75dbe00c7
sha1: e865ec398ed3c3b9a69735f4ccd51c4ea51fb3ba
download alternative
On precedent release (2016-02-07) device was named leo instead of z3 so flashing zip could fail!
Move device tree to correct the ro.product.device
! As twrp 3.0.0-0 is a new release for me I only test 'basic' things. Feel free to report your experience. (decryption and f2fs always working)
2016-02-07:
FOTAKernel/recovery binary:
md5: b69962aaea113f0e55aa9953d4a1f8c2
sha1: addb93e06824c576d893045e6cb2f65270c426df
downloadflashable zip:
md5: 816da3715c82c2f77b3ab5a6aca1612e
sha1: 26f09b99a65ad2100070f29edd8510d4da76a91e
download
Device name was 'leo' instead of 'z3'!
Switch to omnirom android-6.0 sources
twrp 3.0.0-0 release
kernel 3.10
! As twrp 3.0.0-0 is a new release for me I only test 'basic' things. Feel free to report your experience. (decryption and f2fs always working)
2016-01-14:
FOTAKernel/recovery binary:
md5: b2f6f7aee3e685b7b2a817dc2d9f9b45
sha1: 0b23e1e368ca57a14100eae069b3a0d7daedfbd4
downloadflashable zip:
md5: 52bfd146b0cb69bd0c29ce42b42cf995
sha1: 6f7e7b9ec51f662ef0ccb39a1e63567490485125
download
Custom governor to reduce heating
Revert board-name-change commit
2016-01-09:
FOTAKernel/recovery binary:
md5: a50f9b48d89db94bc5ffa5f791a7cd56
sha1: 2b9848d6f1b7cbdc04a6bb28590ae95265f5b2d0
download: http://s000.tinyupload.com/?file_id=47292896408680539327flashable zip:
md5: 2e8766e3a6be34c11470099f4638dd01
sha1: ca1ec7f53d308980e82c09c586882a6a464dbaf5
download: http://s000.tinyupload.com/?file_id=78086454241793216639
Minor changes (cmdline) to be bootable from new bootloader
2016-01-09:
FOTAKernel binary:
md5: 2aaf2d85bbaf40e0118fae9173b2fb69
sha1: c6ca54aafebde25a32a080d5d44172289a1c707e
download: http://s000.tinyupload.com/?file_id=08765682926169309050flashable zip:
md5: d56266b1df54d2731fd0f0a2e1b1eee6
sha1: 243e1f78c9409b638f68616a01c2f28d34cc4981
download: http://s000.tinyupload.com/?file_id=33880692705595869190
Updated build from sources
2015-12-26:
FOTAKernel binary:
md5: 0cf55faa541f861652e73fa62dbfb80a
sha1: 64a5672198b9a0031ecd663cc62cf2b05cd8a482
download: http://s000.tinyupload.com/?file_id=77779745124843827613flashable zip:
md5: 7bf41589eda189c4646ca979e93da047
sha1: 9a109fe526b1eb616acfed1f85f6438a8b0eb278
download: http://s000.tinyupload.com/?file_id=16394970444867985651
add keystore support in a cleaner way
add /system symlinks so mounting /system is no more needed to decrypt /data
make a 'updater-script' to automate flashing-zip generation
2015-12-24:
md5: 8993fdb30ce00e431a59068f9f014e41
sha1: 5a8dfe7b4cba0b79ba1beea70656e2318dbdc9a2
download: http://s000.tinyupload.com/?file_id=10791233217780154379
Add qcom msm8974 keymaster blobs
uncrypt data now working with workaround
2015-12-19:
md5: c6e3859eae39597f984852c41a183620
sha1: b42aa840637640c3934684b3cb1fa992ea5b383a
download: http://www.datafilehost.com/d/e46f08c4
Add qcom msm8974 hardware crypto support
Try to add uncrypt capabilities (failed)
add governor_scaling to 'ondemand'
2015-12-18:
md5: 13b1d5de4e69e4bb49621fbe87b8ae9b
sha1: 9ed93f895897c885d139d723180d50a33ec0a719
download: http://www.datafilehost.com/d/abe4ced7
Initial release
At home my computer are only on linux distros and today I post my release from work. Then I realize that datafilehost download malware on windows computer. I'm really sorry and hope no computer where infected.
For this 'working crypto' release tinyUpload was used but if anyone know a good solution I take-it. Thanks and sorry for inconvenience .
ext4/f2fs
New release.
Apparently this f2fs build is not compatible with ext4 over encryption (Seems only cyanogenmod use f2fs, you can check your encrypted filesystem with mount | grep "dm-0" )
If you need a decrypt for ext4 ask and I build it asap.
I am running CM12.1 on my Z3 with encryption and dm-0 is type ext4 mounted on /data. I did not changed things manualy. I checked the Z3 of my wife and it's ext4 too.
Gesendet von meinem Xperia Z3 mit Tapatalk
dm-0 ext4
frabe8378910 said:
I am running CM12.1 on my Z3 with encryption and dm-0 is type ext4 mounted on /data. [...] I checked the Z3 of my wife and it's ext4 too.
Click to expand...
Click to collapse
Thank you for this information! Is this build of twrp working for you with encryption? If not I rebuild it with the ext4 flag.
frabe8378910 said:
I did not changed things manualy.
Click to expand...
Click to collapse
I switch my /data & /data/media to f2fs before encrypting my CM12.1, maybe that is it
Thanks for your feedback.
nailyk said:
Thank you for this information! Is this build of twrp working for you with encryption? If not I rebuild it with the ext4 flag.
I switch my /data & /data/media to f2fs before encrypting my CM12.1, maybe that is it
Thanks for your feedback.
Click to expand...
Click to collapse
I did not tested it, because I thought it was build only for f2fs.
As our SDcard is also ext4 (I need files size up to 25GB) I had never played with f2fs.
And being honest: Both Z3 are "productive" Smartphones, so currently I'd install only "low risc" options.
Gesendet von meinem Xperia Z3 mit Tapatalk
frabe8378910 said:
I did not tested it, because I thought it was build only for f2fs.
As our SDcard is also ext4 (I need files size up to 25GB) I had never played with f2fs.
Click to expand...
Click to collapse
I switch to f2fs for performance but my last dmesg sounds like the dmcrypt is ext4. Anyway my computer is currently building with the ext4 flag for testing purpose.
frabe8378910 said:
And being honest: Both Z3 are "productive" Smartphones, so currently I'd install only "low risc" options.
Click to expand...
Click to collapse
Totally understand! My z3 is also everyday use and my only phone but it is mine. If i brake yours I go crazy :fingers-crossed:
I'm actually working with the twrp team to port my work, maybe you could try later
Have you find other recovery with working encryption?
nailyk said:
I switch to f2fs for performance but my last dmesg sounds like the dmcrypt is ext4. Anyway my computer is currently building with the ext4 flag for testing purpose.
Totally understand! My z3 is also everyday use and my only phone but it is mine. If i brake yours I go crazy :fingers-crossed:
I'm actually working with the twrp team to port my work, maybe you could try later
Have you find other recovery with working encryption?
Click to expand...
Click to collapse
No, I'm using twrp from LeonidasTurk on both Z3, which works fine except decryption of /data. So if your's would fix this issue, that would be perfect.
frabe8378910 said:
I did not tested it, because I thought it was build only for f2fs.
Click to expand...
Click to collapse
nailyk said:
my computer is currently building with the ext4 flag for testing purpose.
Click to expand...
Click to collapse
Confirmed, the
Code:
TW_CRYPTO_FS_TYPE
flag is deprecated.
(https://github.com/omnirom/android_bootable_recovery/blob/android-5.1/crypto/lollipop/cryptfs.c#L71)
and my dmcrypt is ext4
HTML:
/dev/block/dm-0 on /data type ext4 (rw,relatime,data=ordered)
/dev/block/dm-0 on /sdcard type ext4 (rw,relatime,data=ordered)
/dev/block/mmcblk1p1 on /external_sd type f2fs (rw,relatime,background_gc=on,user_xattr,acl,inline_data,extent_cache)
so the filesystem doesn't matters. I edit the post consequently. Thanks a lot @frabe8378910
frabe8378910 said:
No, I'm using twrp from LeonidasTurk on both Z3, which works fine except decryption of /data. So if your's would fix this issue, that would be perfect.
Click to expand...
Click to collapse
For me it is working fine for a couple of month now. And we have successfully ported twrp with encryption to z1, z1c & z3.
So if you are ok to try it please leave a comment to share the result of your tests (phone heat, encryption, speed, etc...)
Thank for your time!
nailyk said:
For me it is working fine for a couple of month now. And we have successfully ported twrp with encryption to z1, z1c & z3.
So if you are ok to try it please leave a comment to share the result of your tests (phone heat, encryption, speed, etc...)
Thank for your time!
Click to expand...
Click to collapse
I'll check it the coming weekend.
Thanks for your work.
Gesendet von meinem Xperia Z3 mit Tapatalk
frabe8378910 said:
I'll check it the coming weekend.
Thanks for your work.
Gesendet von meinem Xperia Z3 mit Tapatalk
Click to expand...
Click to collapse
I already did it and it works like a charm!
Perfect, now I can use internal sdcard from recovery too!!
Decryption just takes some seconds.
Tomorrow I'll update the Z3 of my wife too.
Thanks a lot for your work!
Gesendet von meinem Xperia Z3 mit Tapatalk
frabe8378910 said:
I already did it and it works like a charm!
Perfect, now I can use internal sdcard from recovery too!!
Decryption just takes some seconds.
Tomorrow I'll update the Z3 of my wife too.
Thanks a lot for your work!
Click to expand...
Click to collapse
Glad it work well for you too.
Thank for your time and your feedback!
nailyk said:
Glad it work well for you too.
Thank for your time and your feedback!
Click to expand...
Click to collapse
But so, you did the work and I just consumed that work...
Btw: I installed your recovery by flashing the zip from recovery.
Gesendet von meinem Xperia Z3 mit Tapatalk
z3 bootloader
frabe8378910 said:
Btw: I installed your recovery by flashing the zip from recovery.
Click to expand...
Click to collapse
Have you upgraded your bootloader or are you using the older?
The new one offer real recovery possibilities: if a rom upgrade fail recovery will still be accessible. That is not possible with the older bootloader. The point is, to upgrade, you need to reflash your entire phone to stock.... (all your datas will be lost) Dedicated xda-thread?
nailyk said:
Have you upgraded your bootloader or are you using the older?
The new one offer real recovery possibilities: if a rom upgrade fail recovery will still be accessible. That is not possible with the older bootloader. The point is, to upgrade, you need to reflash your entire phone to stock.... (all your datas will be lost) Dedicated xda-thread?
Click to expand...
Click to collapse
No, I did not change the bootloader, 'cause I don't like to reflash stock.
I've not read much about it, but doesn't mean reroot it afterwards? I'd just stay tuned that someone provide a better way...
Gesendet von meinem Xperia Z3 mit Tapatalk
frabe8378910 said:
No, I did not change the bootloader, 'cause I don't like to reflash stock.
I've not read much about it, but doesn't mean reroot it afterwards?
Click to expand...
Click to collapse
You are right, the way sony provide, reflash the entire phone (except recovery).
frabe8378910 said:
I'd just stay tuned that someone provide a better way...
Click to expand...
Click to collapse
I am a gambler(?) but with bootloader I take no risk.
Tell me if you find something working.
@nailyk
Welcome to XDA. By the way, you only need to encrypt your phone once. After that you can install any other rom while keeping the same encryption. You just do wiping in TWRP with rm -rf instead of formatting. I tested and was able to successfully install a different rom.
Also, it is important to encrypt your phone (once only) via adb, because otherwise, your data partition is encrypted with the following password: 'default_password', literally. That's no security at all. Adb allows you to have an unlimited length boot password and a separate short pin for screen lock.
Also, once you remove this commit https://gerrit.omnirom.org/#/c/14353/ , and you would want to remove encryption, you can do that by pressing 'cancel' when asked for password and then format system, then data and then /system/data/cache/...
AOSP encryption password
optimumpro said:
@nailyk
Welcome to XDA. By the way, you only need to encrypt your phone once. After that you can install any other rom while keeping the same encryption. You just do wiping in TWRP with rm -rf instead of formatting. I tested and was able to successfully install a different rom.
Click to expand...
Click to collapse
Thank you!
It is good new as I want to have ability to switch between CM and stock rom.
optimumpro said:
Also, it is important to encrypt your phone (once only) via adb, because otherwise, your data partition is encrypted with the following password: 'default_password', literally. That's no security at all. Adb allows you to have an unlimited length boot password and a separate short pin for screen lock.
Click to expand...
Click to collapse
I didn't change my bootpassword yet but it is planned
Also I have some questions:
What I have understood from official AOSP documentation and twrp source code is the dmcrypt password is 'default_password' even if encrypted with your adb way. I suppose 'vdc cryptfs changepw' if the command used by the GUI: if I change my boot password with 'foobar' with 'vdc cryptfs changepw 666f6f626172', then change my screen-unlock password with '0000', I suppose the bootpassword will be erased by '0000'. Is it true?
optimumpro said:
Also, once you remove this commit https://gerrit.omnirom.org/#/c/14353/ , and you would want to remove encryption, you can do that by pressing 'cancel' when asked for password and then format system, then data and then /system/data/cache/...
Click to expand...
Click to collapse
As I can remember and according to this part of code, wiping device by clicking the different 'format' buttons wipe encryption.
So did you say once the phone boot password is changed with your 'adb command' the only way to wipe encryption is to recompile a twrp without this commit? I also planned some tests: wiping encryption, restoring backups on encrypted partitions, etc...
P.S.: I update my build tree to include z1/z1c/z3 with a new recovery/Android.mk. Now mka recoveryimage should work.
@nailyk
Can't seem to reboot recovery from within TWRP on stock .264 (UB). It boots straight to system. Booting to recovery with power button plus volume down combo when device is off works. Any ideas?
## le_x2 -A-TEST-MIUI-10-OREO-BETA 8.9.13 xiaomi-miui.gr Ported 13.09.2018_le_x2 ##
All credits goes to Greek forum xiaomi-miui.gr. Rom is from there (sources)
Also credits go to @shivatejapeddi for his help and kernel..e.t.c.
*Changelog*
- Rom is Multilanguage and clean
- Several changes inside System tov work on our phone
- More Translations inside
- Gapps and all Google services included
- Including all latest framework patches
- Includes all latest changes and MIUI10 updates
- Includes latest Gcamera fixed modded (check at Aroma)
- Dolby Atmos
- IR included
- Security authenicator included
- Includes latest available Manager and themes.
- More....
Rom Link
https://drive.google.com/uc?id=13lzE...xport=download
!!IMPORTAND!!
Rom is pre -A- stage..bugs:br,cam,fp......
TWRP vendor compatible needed.
INSTALLATION
Make system,data,dalvik and cache wipe..reboot to recovery and flash rom.
Go through Aroma installer read carefully and choose custom installation... Choose betwin original Miui rom properties and LeMax2 custom inside Aroma..
Don't choose Magisk before 1st boot ..install it after..is faster and better..is inside rom zip at data>app>Magisk
With Aroma installer we can choose what we want and install according our need's...
NOTICE
Is a test rom!! Not ready for daily use..only test..
DO NOT ASK FOR UPDATE OR ETA. When is ready will be released...
I hope to have some help to fix all bugs and more stuff..
Compatible TWRP
https://drive.google.com/file/d/1_WK...ew?usp=sharing
Dark-Evil said:
## le_x2 -A-TEST-MIUI-10-OREO-BETA 8.9.13 xiaomi-miui.gr Ported 13.09.2018_le_x2 ##
All credits goes to Greek forum xiaomi-miui.gr. Rom is from there (sources)
Also credits go to @shivatejapeddi for his help and kernel..e.t.c.
*Changelog*
- Rom is Multilanguage and clean
- Several changes inside System tov work on our phone
- More Translations inside
- Gapps and all Google services included
- Including all latest framework patches
- Includes all latest changes and MIUI10 updates
- Includes latest Gcamera fixed modded (check at Aroma)
- Dolby Atmos
- IR included
- Security authenicator included
- Includes latest available Manager and themes.
- More....
Rom Link
https://drive.google.com/uc?id=13lzE...xport=download
!!IMPORTAND!!
Rom is pre -A- stage..bugs:br,cam,fp......
TWRP vendor compatible needed.
INSTALLATION
Make system,data,dalvik and cache wipe..reboot to recovery and flash rom.
Go through Aroma installer read carefully and choose custom installation... Choose betwin original Miui rom properties and LeMax2 custom inside Aroma..
Don't choose Magisk before 1st boot ..install it after..is faster and better..is inside rom zip at data>app>Magisk
With Aroma installer we can choose what we want and install according our need's...
NOTICE
Is a test rom!! Not ready for daily use..only test..
DO NOT ASK FOR UPDATE OR ETA. When is ready will be released...
I hope to have some help to fix all bugs and more stuff..
Compatible TWRP
https://drive.google.com/file/d/1_WK...ew?usp=sharing
Click to expand...
Click to collapse
very bad rom.. slowwwww
not.stable
test!!!
Download link not working..
Any correct link?
Link not working ....
I think this is the same ROM, link is from Crisbalgreece's page.
https://drive.google.com/uc?id=13lzEAQD5RMGGjhx7wAbenFd38PdG7loF&export=download
What a shame!!!!!!!!!!
It is Cris Work.
Great. Why have you deleted the download link?
Great rom. Expectinf new update soon with OTA?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
» Android Pie «
Code:
DISCLAIMER:
> Highly recommended to [B][COLOR="Red"]do a full backup in TWRP[/COLOR][/B] before taking any action incase things go wrong!
> You're not allowed to use anything from this ROM unless you've been given permission to do so!
> I don't take any responsibility and I'm not liable for any damage caused by using this ROM!
ROM BASE INFO
» Based on G95XFXXS9DTEA
» May security patch
» Supported G950 / 955F-FD-N
» Magisk root / no root
» Odexed system
» Zipaligned
» Multi CSC
» RMM state fix included
» Knox turned off
» Removed Samsung Pass and Secure Folder
AROMA OPTIONS
» Remove bloatware
» Emojis
» Fontpack
» Stock kernel / NX kernel
» Clean / dirty flash
» Netflix fix
» Remap Bixby button
» Magisk root
» TWRP recovery
» CSC Features
» Busybox
» Dual sim + sdcard mod
NOTES
» If magisk doesn't show up in the drawer after installing, take out the apk from ''magisk.zip'' in the rom, copy to phone and install as normal apk and reboot (first thing to do after installing rom)
» Flash the rom first and reboot and then flash BL/CP update.zip separately if you need to
» Flash correct rom.zip for your device!
» Remember that debloating may break some features/apps
» Default stock kernel needs root! For ''no root'' select NX kernel when installing!
ROM DOWNLOADS
» MEGA EclipseSTOCK_v16_G950F-FD-N_DTEA
» M.FIRE MIRROR
MD5: 2422956924CFFDE31F1439D99A497F4A
» MEGA EclipseSTOCK_v16_G955F-FD-N_DTEA
» M.FIRE MIRROR
MD5: 42BD9847F9023E8A686DCB6DCD7D2F9C
Bootloader / modem update DTEA
The bootloader and modem update is optional:
» G95XF-FD_BL-CP_Update-to-DTEA
CHANGELOG
Code:
[B]v1 - 04.03.2019[/B]
- Initial release
- Based on Official G95XFXXU4DSBA
- February security patch
- Busybox 1.29.3
- Magisk 18.2 root / no root in Aroma
- Odexed system
- Zipaligned
- Remove bloatware in Aroma
- Emoji choice in Aroma
- Fontpack choice in Aroma
- Clean / dirty flash option in Aroma
- Stock / NX kernel in Aroma
- Netflix fix in Aroma
- Remap bixby button in Aroma
- TWRP 3.2.3-2 recovery in Aroma
- RMM state fix included
- Knox turned off
- Removed Samsung Pass and Secure Folder
- Removed some Knox related useless apps
- Removed some other bloat apps
[B]v1.1 - 10.03.2019[/B]
- Added Applock (enable in csc features)
- Added Screenrecorder and Screencapture
- Added CSC Features in Aroma
- Enabled some extra toggles
[B]v2 - 18.03.2019[/B]
- Updated base to Official G95XFXXS4DSC2
- Stock kernel updated to DSC2
- March security patch
- Added Korean CSC's KTC/LUC/SKC
- Updated Magisk 18.2 Canary to latest
- Updated Busybox to 1.30.1
- Updated Bootloader/modem to DSC2
[B]v2.1 - 03.04.2019[/B]
- Updated base to Official G95XFXXU4DSCB
- S8 changelist [U]15668094[/U] / S8+ changelist [U]15668116[/U]
- Stock kernel updated to DSCB
- NX kernel updated to 23.5
- Magisk updated to 19.0 beta
- Bootloader/modem updated to DSCB
[B]v3 - 01.05.2019[/B]
- Updated base to Official G95XFXXU4DSDA
- April security patch
- S8 changelist [U]15838602[/U] / S8+ changelist [U]15838602[/U]
- Stock kernel updated to DSDA
- NX kernel updated to R25
- Magisk updated to latest Canary
- TWRP Recovery updated to 3.3.0-0
- Bootloader/modem updated to DSDA
[B]v4 - 18.05.2019[/B]
- Updated base to Official G95XFXXS4DSE1
- May security patch
- Stock kernel updated to DSE1
- Magisk updated to latest Canary
- Bootloader/modem updated to DSE1
[B]v4.1 - 24.05.2019[/B]
- Updated base to Official G95XFXXU4DSE4
- S8 changelist [U]16019454[/U] / S8+ changelist [U]16019454[/U]
- Added Busybox to Aroma options
- Updated CSC's KTC/LUC/SKC
- Stock kernel updated to DSE4
- Magisk updated to latest Canary
- TWRP Recovery updated to 3.3.1-0
- Bootloader/modem updated to DSE4
[B]v5 - 25.06.2019[/B]
- Updated base to Official G95XFXXS5DSF1
- June security patch
- Stock kernel updated to DSF1
- NX kernel updated to R27
- Added Dual sim + sdcard mod in Aroma
- Magisk updated to latest Canary
- Bootloader/modem updated to DSF1
[B]v6 - 03.07.2019[/B]
- Updated base to Official G95XFXXU5DSFB
- July security patch
- S8 changelist [U]16290088[/U] / S8+ changelist [U]16290088[/U]
- Stock kernel updated to DSFB
- Magisk updated to latest Canary
- Bootloader/modem updated to DSFB
[B]v7 - 21.08.2019[/B]
- Updated base to Official G95XFXXS5DSH5
- August security patch
- Stock kernel updated to DSH5
- NX kernel updated to R28
- Magisk updated to latest Canary
- Bootloader/modem updated to DSH5
[B]v7.1 - 07.09.2019[/B]
- Updated base to Official G95XFXXU5DSHC
- S8 changelist [U]16626841[/U] / S8+ changelist [U]16626841[/U]
- Stock kernel updated to DSHC
- Updated CSC's KTC/LUC/SKC
- Bootloader/modem updated to DSHC
[B]v8 - 19.09.2019[/B]
- Updated base to Official G95XFXXS5DSI1
- September security patch
- Stock kernel updated to DSI1
- Magisk updated to latest Canary
- Bootloader/modem updated to DSI1
[B]v9 - 21.10.2019[/B]
- Updated base to Official G95XFXXS5DSJ1
- October security patch
- Stock kernel updated to DSJ1
- Updated CSC's KTC/LUC/SKC
- Magisk updated to latest Canary
- TWRP Recovery updated to 3.3.1-1
- Bootloader/modem updated to DSJ1
[B]v9.1 - 09.11.2019[/B]
- Updated base to Official G95XFXXU5DSJC
- S8 changelist [U]17082260[/U] / S8+ changelist [U]17082260[/U]
- Stock kernel updated to DSJC
- NX kernel updated to R29
- Magisk updated to latest Canary
- Bootloader/modem updated to DSJC
[B]v10 - 06.12.2019[/B]
- Updated base to Official G95XFXXU6DSK9
- November security patch
- S8 changelist [U]17263988[/U] / S8+ changelist [U]17264019[/U]
- Stock kernel updated to DSK9
- Updated CSC's KTC/LUC/SKC
- Magisk updated to latest Canary
- Updated Busybox to 1.31.1
- Bootloader/modem updated to DSK9
[B]v11 - 19.12.2019[/B]
- Updated base to Official G95XFXXS6DSL2
- December security patch
- Stock kernel updated to DSL2
- Magisk updated to latest Canary
- Bootloader/modem updated to DSL2
[B]v12 - 20.01.2020[/B]
- Updated base to Official G95XFXXS6DTA1
- January security patch
- Stock kernel updated to DTA1
- Magisk updated to latest Canary
- Bootloader/modem updated to DTA1
[B]v13 - 18.02.2020[/B]
- Updated base to Official G95XFXXS7DTA6
- February security patch
- Stock kernel updated to DTA6
- Updated CSC's KTC/LUC/SKC
- Magisk updated to latest Canary
- Bootloader/modem updated to DTA6
[B]v14 - 17.03.2020[/B]
- Updated base to Official G95XFXXS8DTC1
- March security patch
- Stock kernel updated to DTC1
- Magisk updated to latest Canary
- Added Samsung Theme Park
- Bootloader/modem updated to DTC1
[B]v15 - 31.03.2020[/B]
- Updated base to Official G95XFXXS8DTC6
- April security patch
- Stock kernel updated to DTC6
- Magisk updated to latest Canary
- Bootloader/modem updated to DTC6
[B]v16 - 30.05.2020[/B]
- Updated base to Official G95XFXXS9DTEA
- May security patch
- Stock kernel updated to DTEA
- Updated CSC's KTC/LUC/SKC
- Samsung Theme Park updated to latest version
- Magisk updated to latest Canary
- TWRP Recovery updated to 3.3.1-2
- Bootloader/modem updated to DTEA
INSTALL INSTRUCTIONS
1) Make sure you got TWRP installed
2) Make sure OEM unlock is enabled in settings/dev. options if your coming from official stock
3) Copy rom.zip to internal/external SD (external recommended)
4) Boot into TWRP and wipe the following: cache, dalvik cache, data and system (also ''format data'' if coming from official stock)
5) Install ROM and follow Aroma installer
6) Reboot device
Installation and review video, thanks to @MobileTechPoint
CREDITS
Code:
Very much thanks to these amazing guys :)
* Samsung - for official firmware
* topjohnwu - for Magisk root
* Winb33 - for fontpack
* abhatia1435 - for Emojis
* corsicanu - for TWRP recovery, Screenrecorder and DS+SDcard
* ambasadii - for wipe script
* BlackMesa123 - for RMM state fix and DS+SDcard
* amarullz - for AROMA installer
* noxxxious - for NX kernel
* SoLdieR9312 - for the inspiration
* yash92duster - for update binary/installer and 50 fontpack
* osm0sis - for Android Image Kitchen and busybox
* _alexndr - for Applock
* Tkkg1994 - for CSC features
NX Kernel
Source Code: https://github.com/Noxxxious/Upgrade
XDA:DevDB Information
EclipseSTOCK, ROM for the Samsung Galaxy S8
Contributors
MaHo_66
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: TWRP Recovery
Version Information
Status: Stable
Stable Release Date: 2020-05-30
Created 2019-03-04
Last Updated 2020-08-28
Reserved
mods
» aliwaris mods
screenshots
Good to See some New stuff for the "old" S8 :fingers-crossed:
Does this rom include a fix for 2 sims + sd card mod?
Nice smooth rom if possible please include screen record and screen capture in pull down panel
iANiMeX said:
Does this rom include a fix for 2 sims + sd card mod?
Click to expand...
Click to collapse
Nope
Sorry deleted please
does the rom have csc tweaks in it?
Does DeX work ?
i dnt select microsoft apps bt they still come
i selected smart manager
bt theres no smart manager
its like stock bt i dnt want microsoft apps nd others also bt they keep coming
rom is smooth, fast
hope to see the fixes in the future
awerqw22 said:
does the rom have csc tweaks in it?
Click to expand...
Click to collapse
Nope
---------- Post added at 07:04 AM ---------- Previous post was at 07:03 AM ----------
saifulmenon said:
i dnt select microsoft apps bt they still come
i selected smart manager
bt theres no smart manager
its like stock bt i dnt want microsoft apps nd others also bt they keep coming
rom is smooth, fast
hope to see the fixes in the future
Click to expand...
Click to collapse
Use package disabler from play store
hi
this rom is nice
but how i can install viper4android ?
zip flashing works but no viper app in apps
flashing through magisk works with aroma installer , but no viper4android in apps (but stated as installed in magisk as installed module)
greetings from austria
Benji1983
Benji1983 said:
hi
this rom is nice
but how i can install viper4android ?
zip flashing works but no viper app in apps
flashing through magisk works with aroma installer , but no viper4android in apps (but stated as installed in magisk as installed module)
greetings from austria
Benji1983
Click to expand...
Click to collapse
It works just try magisk 18.1 not 2
Dual sim + sd card patch needed
Pls provide Dual sim + sd card patch if anybody have
Morning all. Quick update to v1.1 added few things for you guys, enjoy.
Changelog:
- Added Applock (enable in csc features)
- Added Screenrecorder and Screencapture
- Added CSC Features in Aroma
- Enabled some extra toggles
- Updated credits in OP
Please, add other mirrors because afh is ridiculous
erghetto said:
Please, add other mirrors because afh is ridiculous
Click to expand...
Click to collapse
hi
use download manager like jdownloader v2 or so and you can download in fullspeed
greetings
benji
custom binary error
Hi i flash Eclipsestick rom v1.1 after rom i flash pie firmware, my phone immediately reboot and stuck in custom binary lock, this time i flash only rom and boot with oreo firmware, everything goes smoothly ?
Great rom thanks
Very good Rom smooth as butter. Hope you Support S8 a Long time :fingers-crossed:
Good battery life
Jazz2000 said:
Very good Rom smooth as butter. Hope you Support S8 a Long time :fingers-crossed:
Good battery life
Click to expand...
Click to collapse
Plan is to support for long time hopefully if nothing happens to me or my phone
I was originally inspired by soldier's stock rom and felt kinda bad for many users when he announced EOL, so i made a similar rom and now sharing it with you guys