Redmi 2/WT88047 OmniROM PIE 9.0
DOWNLOAD BUILD-28/12/2019 (ARM)
DOWNLOAD BUILD-05/01/2020 (ARM64)
RELEASES:
====================
18/08/19
====================
* Initial release
* Omni upstream as of 18/08
====================
25/08/19
====================
* Selinux enforcing
* Added Dirac support from MIUI
* ZRAM 4.18 backport from a6k kernel
* Fixed the janky flashlight toggle
====================
10/09/19
====================
* Initial ARM64 release
(Thanks to @Cecell3000 for his ARM64 works
and @karthik km for fixing RIL)
====================
28/12/19 - ARM | 05/01/2020 - ARM64
====================
* Fixed VoLTE
* Updated GPS HAL to A6020
* Omni upstream as of 28/12
(looks like the pie branch is no longer updated and is deprecated, maybe its time to discontinue omni pie)
REQUIREMENTS TO SUCCESSFULLY FLASH OMNIROM:
1. TWRP obviously (Use Cecell's ARM64 TWRP)
2. Latest device firmware (WT86047 | WT88047)
3. Repart /system to at least 1.5GB
(Go HERE to resize system partition)
INSTALLATION INSTRUCTIONS:
1. Reboot device to TWRP
2. Wipe everything except internal and external storage
3. Flash the ROM zip file
4. Flash the 3Expand-filesystem zip file (Available HERE)
5. (Optional) Flash a gapps package
6. Reboot device to system
CURRENT ISSUES:
* You tell me!?
SOURCES:
Device tree (ARM | ARM64)
Common tree (ARM | ARM64)
Kernel sauce (ARM | ARM64)
Vendor (ARM | ARM64)
BUG REPORTS:
REPORT BUGS ONLY IF
- AFTER A CLEAN INSTALL
- USING STOCK KERNEL
- NO MODS OF ANY SORT
OMNI GERRIT REVIEW:
https://gerrit.omnirom.org/
DISCLAIMER:
No one is responsible for any damage done to your device but YOU. You've been warned.
XDA:DevDB Information
OmniROM, ROM for the Xiaomi Redmi 2
Contributors
Rahif M
Source Code: http://github.com/omnirom
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x
Version Information
Status: Testing
Created 2019-08-18
Last Updated 2020-01-17
Thank you!
Nice...
Thanks, I'm gonna try this :good:
Very good.
Onfire again.
Any review please.
Which rom is comptible arm or arm 64 ???
Flash BUILD-10/09/2019 (ARM64) using twrp 3.2.3.0 - 64 bit, get error 255 "error installing zip file"
system partition: resized to 1.5GB
device: redmi 2 1 GB ram
Wow arm64... I wanna try it
I guess need move rom zip file to internal storage, then flash.
thonipublic said:
Flash BUILD-10/09/2019 (ARM64) using twrp 3.2.3.0 - 64 bit, get error 255 "error installing zip file"
system partition: resized to 1.5GB
device: redmi 2 1 GB ram
Click to expand...
Click to collapse
That's weird, can u provide recovery logs pls?
also did you follow the flash procedure correctly?
flash rom.zip+expandfs.zip and then gapps?
Rahif M said:
That's weird, can u provide recovery logs pls?
also did you follow the flash procedure correctly?
flash rom.zip+expandfs.zip and then gapps?
Click to expand...
Click to collapse
Yes, i had follow the flash procedure.
I will try it again tomorrow to get recovery log.
Currently on other rom.
Rahif M said:
That's weird, can u provide recovery logs pls?
also did you follow the flash procedure correctly?
flash rom.zip+expandfs.zip and then gapps?
Click to expand...
Click to collapse
Successfully flash the rom after resize /system partition to 1.75 gb.
Thanks, for this smooth rom :good:
I am not able to flash and boot into the ARM64 TWRP recovery. It'd just hang at the logo. Meanwhile, the normal TWRP (3.3.1.0) works fine. Am I missing something?
I have a 2014817 1GB variant. Could it be misdetecting as a 2GB instead?
Edit: Figured it out
thank you so much for the arm64 bro, i am going to install and test it.
Managed to get it working by flashing latest MM firmware and then the 64bit TWRP. However, it gets stuck at Google Verifying Account page during setup. I can't get past it even using my own accounts to log in. Anyone else has this issue or knows how to get past this?
Edit: Never mind figured out to boot up first time and then flash Open GApps
conspibro said:
Managed to get it working by flashing latest MM firmware and then the 64bit TWRP. However, it gets stuck at Google Verifying Account page during setup. I can't get past it even using my own accounts to log in. Anyone else has this issue or knows how to get past this?
Edit: Never mind figured out to boot up first time and then flash Open GApps
Click to expand...
Click to collapse
MM firmware? WTF!? ?
nadimhd said:
MM firmware? WTF!? ?
Click to expand...
Click to collapse
My phone was still on its stock Kit Kat firmware. The ARM64 TWRP only works with the latest firmware (MM) it seems.
Firmware for the modem, wifi etc, not the OS.
For you information, the instruction isn't that clear. It pretty much take me one day to make it work
here's how I do it
1. Reboot device to TWRP
2. Flash 1Resize-System-Redmi2 zip (can be found at 3rd requirement link)
3. Resize to 1.75 gb
4. Wipe everything except internal and external storage
5. Flash the ROM zip file
6. Flash the 3Expand-filesystem zip file
7. Flash MindTheGapps gapps package (Don't use opengapps it causes bootloop)
8. Reboot device to system
Hope it helps you!
Related
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?
/* *** Disclaimer
* I am 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/KERNEL
* before flashing it! YOU are choosing to make these modifications, and if
* you point your finger at me for messing up your device, I will laugh at you.
* BOOM! goes the dynamite
*/
Hi XDA community, we are proud to present our vision of LineageOS with features that we think are useful. Hope you enjoy our builds as much as we do.
The main goal of Nuclear Team is to provide a clean and fast ROM with nice and useful features.
# Features:
• Based on LOS 14.1
• Android 7.1.1
• Nuclear Settings
• Customizable status bar
• Gestures Anywhere
• Exclusive Nuclear Boot (thanks to zuk user Xals)
• Switch To Hide SuperSu from Status Bar
• Qualcomm Assertive Display
• Network traffic indicator
• Three finger swipe to screenshot
• Show cpu info
• Dt2s everywhere on lockscreen
• All LOS goodies
AND MORE
HOW TO BUG REPORT:
-If you have a major bug to report that has not been reported already, and is not a known issue with CM,
please take the following steps to report it to us. It will save you time, as well as us.
-Download the Catlog app from the Play Store.
There is also a donate version which you can purchase to show appreciation.
-After downloading the Catlog app, go to the app settings, and change the log level to Debug.
-Clear all previous logs and take the exact steps to produce the error you are receiving.
-As soon as you receive the error (probably a force close), go straight into Catlog and stop the log recording.
-Copy and paste the entire log either to Hastebin or Pastebin
-Save the log, and copy and paste the link into the forum with a brief description of the error.
-You can also open trouble tickets on our website for bugs.
× Make a nandroid backup (optional but always recommended)
× Download ROM: Here
× Download GApps: Here
× Wipe system,data,cache,dalvik
× Flash ROM
× Flash GApps
Optional: Flash SUPERSU (for root)
× Reboot
Updating:
× Flash ROM
× Reboot
Have fun....
Enjoy!
Special thanks to:
CyanogenMod
Lord Boeffla
Temasek
Ak
OrdenKrieger
ResurrectionRemix
XDA
HTCmania
Nuclear Team & testers
And a very special thanks to TugaPower
Anyone I might have forgotten (please let me know)
XDA:DevDB Information
NucleaROM, ROM for the OnePlus 2
Contributors
MZO
Source Code: https://github.com/OneRomOne-N
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: OOS 3
Based On: LineageOS
Version Information
Status: Testing
Created 2017-01-24
Last Updated 2017-01-24
Reserved
This ROM follows LineageOS trees
Reserved
Screenshots of some features
reserved
raining roms for oneplus2 <3
downloading...
good to see new rom for op2 but can we have some screenshots please
New ROM, great ?
Enviado desde mi ONE A2003 mediante Tapatalk
clean flash, rom+pico gapps, bootlooping. i'm on f2fs on /data /cache
chxei said:
clean flash, rom+pico gapps, bootlooping. i'm on f2fs on /data /cache
Click to expand...
Click to collapse
Sorry this is only supported with ext4. It's working fine - screenshots uploaded
MZO said:
Sorry this is only supported with ext4. It's working fine - screenshots uploaded
Click to expand...
Click to collapse
I'm on ext4 I'm bootloop too?
12 minutes waiting ,,
Try download again...
Let me make a new build.
Can anyone shoot me a logcat with *:E
Anyone who's trying to use this ROM please use this kernel for now: it's permissive
https://www.androidfilehost.com/?fid=673368273298926110 (with first build) or wait for second build
Can you use different passwords for encryption and lockscreen?
boot loops it's been 85mins and nothing
MZO said:
Anyone who's trying to use this ROM please use this kernel for now: it's permissive
https://www.androidfilehost.com/?fid=673368273298926110 (with first build) or wait for second build
Click to expand...
Click to collapse
still nothing, but flash my own kernel , rom booting fine
It's working, you might need to reboot again after a few minutes, 5 users on Plus including me have booted it with new kernel so it works
MZO said:
It's working, you might need to reboot again after a few minutes, 5 users on Plus including me have booted it with new kernel so it works
Click to expand...
Click to collapse
yes I think :good:
nice rom
btw no root option on dev mod only root adb
NeoVsk said:
Can you use different passwords for encryption and lockscreen?
Click to expand...
Click to collapse
Never used encryption. What about the lock screen?
MZO said:
Never used encryption. What about the lock screen?
Click to expand...
Click to collapse
Usually there is same password/PIN used to decrypt the phone on startup and to unlock the screen. But some ROMs have option to use different passwords for each.
Now the build works fine tested by a few guys including me
User report:
Vamshi Prasad:
New build, everything is working
It's stable
The only bug I'm having is that there's no fast charging
But the ROM sources doesn't have much of customisation.
But the battery backup and all is very much wow.
ROM rating
Battery-10/10
Features-8/10
Stability-9/10(9 because it still lags sometimes)
Overall 9/10(it charges slowly)
My LuisROM based on cdDroid V6.x for Oneplus 5T (dumpling)
Code:
*** Disclamer
/*
* 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 us for messing up your device, we will laugh at you.
*
*/
This is my personal custom rom. LuisROM based on the crDroid, LineageOS and other...
This is a ROM that works on Oneplus 5T (dumpling) snapdrgon only! This ROM comes with a highly-customized kernel, as well as some other very custom modifications.
I will NOT provide support if you install a custom kernel!
Changelogs: http://luis-builds.de/downloads/lineageos/cr/oneplus5t/changelog_dumpling.txt
Introduction
Hello Friends!
I had troubles to find current builds for my devices so I decided to make regular builds for my devices. When my friends told me about similar problems, I extended the builds to include their devices as well. So these builds were and are mainly for my friends and me, but I finally decided to provide them also for public download.
My ROMs
My LuisROM an awesome combination of performance, customization, power and the most new features, brought directly to your device. The LuisROM build server generates automaticly every 2nd days new builds directly from the sources.
Notice
Sometimes I get a lot of help or feature requests from users of my LuisROMs. My dog Luis and I try to fulfill most of the wishes, but that is not always possible. I do that as a little hobby and Luis does not always want to build ROMs . Please understand if I can not always answer directly.
ROM features:
Based on the latest cdDroid V6.x (Android 10), LineageOS and AOSP sources
Latest security patches and sources
OTA Updater
Compatible with EX Kernel Manager
Many other misc. performance and stability improvements under the hood
Kernel: Linux 4.4.x Kernel with many mods other devs and me (thanks for your incredible work!)
Removed lots of excessive bloat (improves security and performance)
Improved stability (several bugs not listed here have been fixed)
Boeffla Wakelock blocker driver V1.1.0
More I/O-Schedulers (fiops, sio, zen, maple)
Optimized for performance and battery life
Compatible with systemless root (recommend Magisk 20.x !!!)
Many other misc. improvements not listed here
Installation instructions:
Pre-installation:
TWRP Recovery of course (download here)
Tested with Oxygen OS 9.0.10 firmware. (download here)
Magisk 20.x and above (Link) can also be used just make sure you flash it after a first successful boot (after passed setup screen)
First time installation:
Unlock your bootloader
Install lates Oxygen firmware (tested 9.0.10)
Flash recovery zip (TWRP)
Flash my latest LuisROM (download here)
Optional: Flash Open GApps and Magisk 20.x and above
Reboot and enjoy
OTA App update installation (auto):
Go to crDroid > About cdDroid > Updates
Press reload button (right corner)
Select download on the new build list
After download select update/flash new build
Optional: Installed gapps and magisk will be moved into new system automaticaly !
TWRP update installation (manual):
Download latest LuisROM build (download here)
Boot into Recovery TWRP
Flash my updated LuisROM (download here)
Reboot and enjoy
Download
Latest builds: (http://luis-builds.de/downloads/lineageos/cr/oneplus5t/)
Latest Oxygen firmware: (download)
My other devices/ROMs: (http://luis-builds.de/downloads/lineageos/)
Download OpenGapps: (http://opengapps.org)
Flash latest TWRP Recovery: (download here)
Donate for my dog Luis, he is looking forward to an extra bone:
https://bw2.link/LuisDonation
Changelog
Developer: http://luis-builds.de/downloads/lineageos/cr/oneplus5t/changelog_dumpling.txt
Known Issus
..
Telegram group:
https://t.me/rr_luisrom
Thanks To/Credits
Special thanks to Teams:
LineageOS team: https://www.lineageos.org
crDroid Team: https://crdroid.net/
OMNI team https://omnirom.org/about/
SLIMROMS https://slimroms.org/#/about
topjohnwu (Magisk) https://forum.xda-developers.com/apps/magisk
Thanks to the best devs on earth:
LuK1337 (https://forum.xda-developers.com/member.php?u=5075128)
PeterCxy (https://forum.xda-developers.com/member.php?u=5351691)
francokernel (https://forum.xda-developers.com/member.php?u=3292224)
sultanxda (https://forum.xda-developers.com/member.php?u=4800121)
flar2 (https://forum.xda-developers.com/member.php?u=4684315)
nathanchance (https://forum.xda-developers.com/member.php?u=6842057)
zx2c4 for the wireguard vpn ROM Integration (https://forum.xda-developers.com/android/development/wireguard-rom-integration-t3711635)
phhusson for some blobs (https://github.com/phhusson)
and of course to all the supporters.
Thanks for the Sources/Blobs/Tweaks
crDroid (https://github.com/LineageOS)
Omnirom (https://github.com/omnirom)
TheMuppets (https://github.com/TheMuppets)
neobuddy89 (https://github.com/neobuddy89)
My Sources/Blobs/Tweaks
DEVICE (https://github.com/FraEgg/android_device_oneplus_dumpling)
KERNEL (https://github.com/FraEgg/android_kernel_oneplus_msm8998)
XDA:DevDB Information
[ROM][OP5T][10]LuisROM Android 10 based on crDroid V6.x [DUMPLING], ROM for the OnePlus 5T
Contributors
8224Freak
Source Code: Source Link: https://github.com/FraEgg
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: 9.0.11
Based On: LineageOS, crDroid, AOSP
Version Information
Status: Beta
Beta Release Date: 2020-03-24
Created 2020-01-26
Last Updated 2020-03-24
Reserved
Huge request to add TTL fixation support to the kernel
Thanks for the ROM!
But I have problem after flash your ROM. I'm stuck at setup wizard, my carrier not detected (Indonesia carrier network, already tried to remove then insert sim card again but still no luck). And at wifi setup it still searching and won't find any network (I have excellent wifi network here and detected with other ROM).
EDIT : after following flashing order by @sant03 now this rom running flawlessly on my 5t. very smooth and nearly haven't facing fps drop on gaming. thanks a lot @8224Freak !
wahing said:
Thanks for the ROM!
But I have problem after flash your ROM. I'm stuck at setup wizard, my carrier not detected (Indonesia carrier network, already tried to remove then insert sim card again but still no luck). And at wifi setup it still searching and won't find any network (I have excellent wifi network here and detected with other ROM).
Click to expand...
Click to collapse
Hi,
Pls check your firmware.
Cu Frank
8224Freak said:
Hi,
Pls check your firmware.
Cu Frank
Click to expand...
Click to collapse
i already flashed firmware 9.0.10 before flash the rom.
and the previous rom i used was OOS 9.0.10
wahing said:
i already flashed firmware 9.0.10 before flash the rom.
and the previous rom i used was OOS 9.0.10
Click to expand...
Click to collapse
I too came from OOS 9.0.10, NO issues here. Very smooth Rom.
hmm i think i know the problem, just notice the magisk point in pre install section.
so i assume the flashing order is :
1. flash rom
2. flash gapps
3. reboot
4. after successufully boot into OS and setup, then go back to recovery to install magisk
isn't it?
wahing said:
hmm i think i know the problem, just notice the magisk point in pre install section.
so i assume the flashing order is :
1. flash rom
2. flash gapps
3. reboot
4. after successufully boot into OS and setup, then go back to recovery to install magisk
isn't it?
Click to expand...
Click to collapse
That's what I did
[email protected] said:
Huge request to add TTL fixation support to the kernel
Click to expand...
Click to collapse
Done! Looking for the next builds...
Cu Frank
8224Freak said:
Done! Looking for the next builds...
Cu Frank
Click to expand...
Click to collapse
Type in the next kernel will already have support? And can I put me on the off version?
Does this ROM have the System Profiles like crDroid V5 does? That's a very useful feature I missed when I upgraded to other Android 10 ROMs, which is why I downgraded.
sant03 said:
That's what I did
Click to expand...
Click to collapse
alright, i'll try tomorrow. thank you so much!
Any plans for mirrors???......download speed very poor from given source, 2+ hours......:crying:
I can t find 9 .0.10 firmware in sourceforge,only 9.0.9.
Anybody can help with this or post another link?
broky said:
I can t find 9 .0.10 firmware in sourceforge,only 9.0.9.
Anybody can help with this or post another link?
Click to expand...
Click to collapse
here you go:
https://forum.xda-developers.com/showthread.php?t=3728665&p=81425595
Tnx for your hard.work
Thanks!!.. Great rom
I found a bug, when using the system profiles option the phone restarts
Enviado desde mi ONEPLUS A5010 mediante Tapatalk
Thanks for building to 5T. Are you skipping Resurrection Remix OS for Android 19 now? I've been a fan of those roms for several devices much because of the possibility to edit navbar behavior.
i found another issue, double tap to wake somtimes didnt work.
C A O S 11
< Your warranty is now void! >
We're 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
CAOS 11 (Custom AOSP OS) is a project which based on @phhusson's Treble GSI AOSP 11. I began it because original project have not only pros (stability, speed, support) but also some issues and limitations - pure AOSP code have some bugs / haven't much useful things and it's a hard way pulling it. So i did this fork. System can run with SELinux enforced state, as an original Phh AOSP GSI. Fully compatible with PHH-Treble patches. Has dynamic root which can be activated/deactivated without reboot - 'su' binary and SuperUser app (can works on all devices even with system read-only). Also has dynamic SafetyNet helper (but it compatible not with all devices), users have four ways to pass SafetyNet: a. just enable SafetyNet option (recommended) b. disable SafetyNet and enable "Spoof Pixel 5" then reboot c. enable both options and reboot d. mount system as RW and create empty file /system/phh/secure (legacy method), and in the Recovery do Wipe Data or Factory reset
UPDATE VERSION
latest build: 2022.03.21
treble patches: v316
SPL: 5 Mar 2022
FEATURES/CHANGES
see Project page changelog
DOWNLOAD (CL1CK HERE)
vanilla, gapps, go-gapps: all possible architectures
NAMING
Some information you should know about knowing what type of gsi it is
<ARCH>_xyZ
<ARCH> can either be arm, a64 (arm32_binder64) or arm64
x can either be a or b
y can either be v, o, g or f
Z can be N or S
b = a/b
a = a-only
g = gapps
o = gapps-go
v = vanilla (no gapps included)
f = floss (free & open source apps instead gapps)
N = no superuser
S = superuser included
Z = dynamic superuser included
-lite = for VNDK Lite vendors (also can help with broken camera even on normal VNDK vendors)
so in most common example "arm64_avZ" is ARM64 A-only vanilla with dynamic superuser
CONTACTS
> telegram group
> project page
KN0WN BUGS
• excluding fixes, the same as on AOSP Roar (in some cases doesn't work: broadcasting on TV, calls via BT; offline charging does not work normally etc etc)
NOTE: always test ROM first without Magisk (with clean boot ramdisk). and don't send me bug reports if you have:
a) Magisk installed
b) modified/custom vendor or kernel
c) dirty flashing rom without wiping data
d) modified props values (another device fingerprint and so on)
CREDITS
persons: @phhusson
projects: TrebleGSI • BlissROMs • crDroid • PixelExperience • ION • neon-OS • Havoc-OS • LineageOS • Evolution-X • LiquidRemix • ExtendedUI • GrapheneOS • ABC Rom • SyberiaOS • RevengeOS • ProtonAOSP
#include_one
#include_two
Great to this thread comes up... it been long time coming.
Can't wait to see when a CAOS is build on Android 12
eremitein said:
KN0WN BUGS• excluding fixes, the same as on AOSP Quack
Click to expand...
Click to collapse
Guess this should read "the same as on AOSP Roar"
Hi,
I flashed CAOS R 2021.04.19 in my HTC U12 life but DigitalWellbeing tools are not available. Is it only available for pixel devices ?
And I'm unable to transfer files using USB connection? Any suggestions or work around to get it working ?
Thank you.
nsbandara said:
Hi,
I flashed CAOS R 2021.04.19 in my HTC U12 life but DigitalWellbeing tools are not available. Is it only available for pixel devices ?
And I'm unable to transfer files using USB connection? Any suggestions or work around to get it working ?
Thank you.
Click to expand...
Click to collapse
are you flashed gappsed variant? i just added Wellbeing but can't test it now, my device have small system partition and i can't easy flash gappsed build
for MTP try enable file transfer in Developer settings
eremitein said:
are you flashed gappsed variant? i just added Wellbeing but can't test it now, my device have small system partition and i can't easy flash gappsed build
for MTP try enable file transfer in Developer settings
Click to expand...
Click to collapse
Yes, I flashed caos-v305-210419-arm64-agZ. I'm unable to find any settings/app entry for WellBeing.
@eremitein - thanks for your work. The ROM is great and fast.
I have it installed on Xiaomi Poco X3 Pro. There are some problems with sound and screen backlight but both of them can be resolved from Phh treble settings. I have posted solutions in X3 Pro thread.
I have one question - in case I would like to update CAOS in future. Is there any "official" way to do this ? Is it possible at all ? Or clean flash is required every time you post new version ?
nsbandara said:
Yes, I flashed caos-v305-210419-arm64-agZ. I'm unable to find any settings/app entry for WellBeing.
Click to expand...
Click to collapse
sad, but i guess you have same with AOSP
as400l said:
I have one question - in case I would like to update CAOS in future. Is there any "official" way to do this ? Is it possible at all ? Or clean flash is required every time you post new version ?
Click to expand...
Click to collapse
How to update GSI
< only same ROM variants >
• go to TWRP, make wipe Dalvik cache (optionally, but recommended)
• install new GSI img to system (or reboot to fastboot/fastbootd and flash GSI)
• boot to TWRP again, resize System
• reinstall same GApps if used before
note: dirty update is not supports by me, do not send bug reports - if you will have bugs first try clean install
CAOS v306 2021.04.24
download /// changelog
Big fan of this CF. I hope there is a option to update (with further versions) using fastboot/adb. (Without loosing data) My Oukitel WP6 just supports these 2 options .
Balsamderaersche said:
My Oukitel WP6 just supports these 2 options .
Click to expand...
Click to collapse
I have one too, and you can simply flash a new version on top of the old one in fastboot without wiping, works totally fine without loss of data.
BTW @eremitein , did you work some magic on VoLTE in the latest releases, or is it on @phhusson side? For me it just works out of the box suddenly, no more fiddling with IMS or APN settings, see screenshot. This is on your latest crDRom, really really nice, see screenshot:
GroovyG said:
I have one too, and you can simply flash a new version on top of the old one in fastboot without wiping, works totally fine without loss of data.
BTW @eremitein , did you work some magic on VoLTE in the latest releases, or is it on @phhusson side? For me it just works out of the box suddenly, no more fiddling with IMS or APN settings, see screenshot. This is on your latest crDRom, really really nice, see screenshot:
Click to expand...
Click to collapse
So basically just:
fastboot flash system xxx.img
?
Yeah!
And a
fastboot erase cache
never hurts, just to have no junk left in there.
GroovyG said:
BTW @eremitein , did you work some magic on VoLTE in the latest releases, or is it on @phhusson side? For me it just works out of the box suddenly, no more fiddling with IMS or APN settings, see screenshot. This is on your latest crDRom, really really nice, see screenshot:
Click to expand...
Click to collapse
is it 21.04.28 build?
No, that's on 21.04.25, didn't see you had a new one up already again, going to install later today
This is hands down the best ROM I have ever used, huge props to you!
Please help me and give me the download links for ( A705FN im arm64-ab )
I'm confused
/*** BEGIN DISCLAIMER ***/
* Your warranty is now void. All flashing is done at your own risk!
* I am not responsible for bricked devices, dead SD cards, 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
/*** END DISCLAIMER ***/
Here's my first effort at porting the custom ROM to the Galaxy Tab A 9.7 [SM-P555] on Android 11. It's likely to have bugs and is EXPERIMENTAL as it is a work in progress.
S-Pen is not supported on this ROM.
Always backup your current ROM (and/or keep stock firmware close by) before flashing.
Please read the full article before proceeding to flash this rom.
Installation Instructions
If you don't have a custom recovery:
- Download twrp_3.0.2-1_SM-P555_mm_15816.tar
- Reboot your tablet in download mode (power+vol-down+home) and connect it to your pc
- Using ODIN load the downloaded file to the AP slot and press start
- As soon the tablet start to reboot hold vol-up and home (don't let it reboot to system)
- Now you should see TWRP-3.0.2.0
If you have custom recovery:
- Copy rom to sdcard or micro sdcard
- Full Wipe (System, Data, Davik Cache, Cache)
- Flash Rom
- Reboot (time boot up to 10 minute)
ROM Download Links:
Android File Host
Google Apps - Select ARM and Android 11
https://opengapps.org/
Change History
20220414:
Initial Version
Working
1. WiFi
2. Bluetooth
3. Brightness
4. Audio via Speakers
5. Location/GPS
6. Camera
7. RIL
Not Working
FM Radio - Hardware doesn't support
ROM OS Version: Android 10
ROM Kernel: Linux 3.10.x
Based On: Lineage
Thanks/Credits
LineageOS Team for the rom sources
Thanks to @retiredtab @RandomAndroidTinkerer for their extensive work on SM-T550 & SM-T555 build. I have followed their sources and commits to fix the ROM issues.
Special mention to @kgvarunkanth for all the support and hours spent teaching me basics and clearing my doubts while building the Development PC and the ROM. I wouldn't have reached this point without his support.
Device Tree gt5note10lte
Kernel sources Github
psuryatej said:
Device Tree gt5note10lte
Click to expand...
Click to collapse
Congrats on getting this build up. Your device tree above only shows the 17.1 branch? Where is the 18.1 branch?
PS. If you haven't removed the FM Radio app from your build, you can do it with this commit
https://github.com/retiredtab/andro...mmit/fb0da5cba8f5223860c52f1be674609527a677da
retiredtab said:
Congrats on getting this build up. Your device tree above only shows the 17.1 branch? Where is the 18.1 branch?
PS. If you haven't removed the FM Radio app from your build, you can do it with this commit
https://github.com/retiredtab/andro...mmit/fb0da5cba8f5223860c52f1be674609527a677da
Click to expand...
Click to collapse
Check the sources now,
Will try this commit thanks.