I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
As we all know - the tablet does not support treble. And we do not have a separate partition, with enough space (about 450mb) to place the whole vendor there.
As a result, I created a solution and tried to make it as much easy as possible for daily use.
I created 2 files - system.img/vendor.img as ext4 images and put it in to the system partition. And then on early init I mounting real system partition as /system_src and then mount system.img as /system and vendor.img as /vendor.
Also I created twrp treble's version for easy use /system and /vendor. It's can wipe new system\vendor partitions, you can restore images to system/vendor in the same way, as we use for boot/recovery.
How to
Prepare - need only once
1. in the current twrp make full wipe (at least we need clean /system, because later we fill all /system by 2 files: system.img/vendor.img)
2. you need flash my twrp with treble support (sm-t825-twrp_3.2.3-0_treble.img): https://drive.google.com/file/d/1GJMrHI4wkePXh8JmF_jgxBSly38B5tu1/view?usp=sharing
3. flash zip with new system.img/vendor.img as ext4 images: https://drive.google.com/file/d/14lwrnM85CoxcpjTUiJ0yfbGHXLa7k0DB/view?usp=sharing
Installation
1. download treble zip from Links and flash it as usual zip. It will flash boot.img and /vendor partition (this is part, specific for our tablet only)
2. download any treble system (64bit System A-only) image from: https://forum.xda-developers.com/project-treble/trebleenabled-device-development, if it not a .img file - extract it, then copy to sdcard/extsd card and then flash image as system_image in twrp (Install - switch to Install Image and flash as System Image)
3. some images require vendor's modification, in oreo some firmware has a 90 rotate, some 270, in my treble zip 90, if you see - image rotated on 180 - flash zip from Additional Links
4. if you wanna back to original lineage\rr without treble - you need flash normal twrp version and make full wipe or just flash stock firmware via odin
Known Issues
sound 2 skeakers only for now
fingerprint
keys light dnw on some firmwares
Links
2. 20180911: fix rotate, back to stock sound (fix bt, quad speakers): https://drive.google.com/file/d/1e_mzosWYL7bv29n613OKZpvSZPXMh26k/view?usp=sharing
1. 20180802: initial treble: https://drive.google.com/file/d/14lwrnM85CoxcpjTUiJ0yfbGHXLa7k0DB/view?usp=sharing
Few notes about item 2: your tablet has wrong image orientation, panel horizontal, sensor - vertical, as result troubles with show right image in right orientation. In 7.0-8.1 this problem was fixed by adding ro.sf.hwrotation=270 in build.prop. For pie this way dnw. Google remove this option and update configstore with new ISurfaceFlingerConfigs. It was added new method: primaryDisplayOrientation. Problem was in adding new configstore sources in the 15.1 sources. Finally I had successfully builded configstore 1.0/1.1 from 16.0 in 15.1.
Additional Links - need only for some oreo images, if image rotated on 180
2. 20180911: https://drive.google.com/file/d/1S4mvXFcX-d2xoZEp9b9dG3ywUhybT6U2/view?usp=sharing
1. 20180802: initial fix rotate: https://drive.google.com/file/d/1JKGu7vudrU0bJPEdkGwBVFkyCJpsHLLs/view?usp=sharing
Magisk
For some reason original Magisk dnw with our treble. It's somehow connect to sepolicy and I'm almost sure about it connected to our treble way with loop0/loop1 mount.
Finally I made small update of the original latest Magisk and it's working. Only one thing was done by me: inside zip in the binary magiskinit file I remove seclabel (seclabel u:r:magisk:s0) for magisk services.
Fixed 17.1 Magisk beta: https://drive.google.com/file/d/1lMhM8ceaJoy5pHRHjCsxxG2C9e5sB5Ot/view?usp=sharing
17.1 Magisk beta manager (this apk also inside Magisk, but cann't be installed automatically during Magisk install), install it as normal apk after install Magisk: https://drive.google.com/file/d/1qCoVPUxvvxopCGfIpoHdAnKueNIxMXal/view?usp=sharing
GApps
https://opengapps.org
Almost all firmware say about wrong vendor version. This is normal, just press OK.
Checked firmwares
AospExtended (need rotate 270 patch): https://forum.xda-developers.com/pr...evelopment/rom-aospextended-rom-v5-5-t3797509
Cosmic-OS: https://forum.xda-developers.com/pr...ment/cosmic-ospulsar8-1-0201805243-2-t3794806
DroidOnTime: https://forum.xda-developers.com/pr...pment/official-droidontime-dotos-2-x-t3794338
Havoc-OS: https://forum.xda-developers.com/pr...-device-development/rom-havoc-os-8-1-t3819050
Lineage: https://forum.xda-developers.com/pr...evice-development/lineage-phh-treble-t3767690
OmniROM Treskmod (need rotate 270 patch): https://forum.xda-developers.com/pr...development/rom-8-1-omnirom-treskmod-t3818188
Pixel Experience (it's requere register custom firmware): https://forum.xda-developers.com/pr...e-development/8-1-0-pixel-experience-t3796011
Resurrection Remix: https://forum.xda-developers.com/pr...opment/resurrection-remix-phh-treble-t3767688
let's experiment together!
Wow! Man, you rock! My Favourite dev! Thanks for Your hard work!
Thanks for this. One question, do we use A/B or A images?
Peeps1513 said:
Thanks for this. One question, do we use A/B or A images?
Click to expand...
Click to collapse
Forgot: system a only
Valera1978 said:
Forgot: system a only
Click to expand...
Click to collapse
And what did You think about the bugs You have mentioned? (Fingerprint, deepsleep, speakers) Fixable or not?
deepsleep, speakers - this is the common tab s3 problems (same in the original lineage), a bit later will back to it.
fingerprint - need to check, in the treble mode shim libs dnw because of linker in the system, also service from vendor don't see libs in system - i.e. some limitations. For camera I made workaround: launch second cameraserver service with my shim lib in environment, but this way dnw for fingerprint. It should be something easy to fix, but I still don't see it.
Valera1978 said:
deepsleep, speakers - this is the common tab s3 problems (same in the original lineage), a bit later will back to it.
fingerprint - need to check, in the treble mode shim libs dnw because of linker in the system, also service from vendor don't see libs in system - i.e. some limitations. For camera I made workaround: launch second cameraserver service with my shim lib in environment, but this way dnw for fingerprint. It should be something easy to fix, but I still don't see it.
Click to expand...
Click to collapse
Really appreciate your work :highfive:
Nice project. Good stuff.
I finally settled on HAVOC after much playing around but am facing an issue trying to install magisk (16.7), no success yet . When I searched [ROM][TREBLE] Havoc-OS 8.1 it seems that magisk has been installed on other devices so could it be a vendor issue? Any help would be appreciated. phh supersu seems to be fine though.
Peeps1513 said:
I finally settled on HAVOC after much playing around but am facing an issue trying to install magisk (16.7), no success yet . When I searched [ROM][TREBLE] Havoc-OS 8.1 it seems that magisk has been installed on other devices so could it be a vendor issue? Any help would be appreciated. phh supersu seems to be fine though.
Click to expand...
Click to collapse
Yep. I've tested treble but no sucess atm for me. Better stay with non-treble lineage, as most of the things work just fine. Maybe in future if Valera fix some things on treble bulid (if ever). Hope Dev focus on oreo lineage than treble project (which is good stuff, but not good enough as daily driver)
I want to leave a feedback after almost a month with treble roms
I have to change my mind: treble is fantastic! Such a great thing, very helpfull for all of us. I was running Valera's lineage 15.1 as daily driver for about 2 months.
In regular non-treble bulid almost everything work. Bad thing were performance (slow animations) and not working deepsleep.
I was happy but not at al. That wasnt this what i was looking for. Then i found again this thread and again give a try (longer) :fingers-crossed:
I am running now treble omnirom for few weeks. Worst things i find is: magisk did not work (very sad, tried multiple versions with no luck, other users report magisk is working for them) and my bluetooth headphones arent working (probably our side bug too)
In plus: no random reboots, performance is very good, no slow downs, deepsleep problem almost gone (drain 6% overnight connected to wifi)
Didnt find any other bugs
I am really happy now. It would be exelent with magisk and bluetooth audio working
Great job, i stick with treble for now :laugh:
Thanks for your great work, Valera!
Have anyone tried this on SM-T820 (Wi-Fi only version)?
imder said:
Thanks for your great work, Valera!
Have anyone tried this on SM-T820 (Wi-Fi only version)?
Click to expand...
Click to collapse
Work only with T825
Any updates Master?
@Valera1978
Could you PLEASE make this for us left out t820 owners???
How does this rom with Lineage compare to your non-treble build? Any reason to switch if I want to stick with Lineage?
robsmith11 said:
How does this rom with Lineage compare to your non-treble build? Any reason to switch if I want to stick with Lineage?
Click to expand...
Click to collapse
You better wait for Pie relase. Valera is working on it.
suzook said:
@Valera1978
Could you PLEASE make this for us left out t820 owners???
Click to expand...
Click to collapse
Without device this is impossible. Look like somehow vendors is differ in 820/825, and I need device to understand, what is wrong, why vendor from 825 dnw on 820 (except ril, may be gps). It should be something simple. Because on my another samsung's tablet on exynos no diffs at all. Treble for wifi version I had made based on lte version in first attempt.
robsmith11 said:
How does this rom with Lineage compare to your non-treble build? Any reason to switch if I want to stick with Lineage?
Click to expand...
Click to collapse
I'll update non-treble build soon. And treble too. During working on treble I had fixed some stuff, like hexedit finger libs to remove shim lib. But I need fix audio in calls again first.
About pie - I dont see any reason to start work on it right now, it's too early, it still has a lot of problems. Better spend this time to make something cool - may be even make samsung port from note 9 or tab s4 with dex and some stuff.
But if you don't want use treble (I agree, it's may be too complicate with special twrp and additional partitions), I think I can prepare integrated pie system images with simple flash without any additional manipulations, like you flash lineage.
Valera1978 said:
Without device this is impossible. Look like somehow vendors is differ in 820/825, and I need device to understand, what is wrong, why vendor from 825 dnw on 820 (except ril, may be gps). It should be something simple. Because on my another samsung's tablet on exynos no diffs at all. Treble for wifi version I had made based on lte version in first attempt.
Click to expand...
Click to collapse
Man, if you would be somehow able to build a unified or a separate treble rom for 820, you would be the greatest man on xda! Cause we have no support for 820 anymore...
Related
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Note 1/19/18: I fixed OTG in 3.2.1-0. Since the LineageOS kernel for the VS995 is known to have broken OTG, I went back to my good old reliable 10b source. I stripped down the options as much as I could to reduce the file size. It seems to be working well. Unfortunatly the only way to tell them apart is the file size or md5.
Old: 24,637,440 bytes / MD5 - ca8bb67c07a81fe17f463eeaacd7c096
New: 24,653,824 bytes / MD5 - d2b25849241b9524b838a11bb0a39093
Here's the build info from the old builds for those looking for breadcrumbs, etc.
OK, this is the first time I've built TWRP so I'm sure there are some issues. Please use this at your own risk. I've done some very basic testing and it seems to work OK for my purposes. I do not plan to build for anything other than the VS995. For other devices I'll lay out my basic workflow in hopes that those still working on other devices can do the same.
Basically I followed the guide here: https://forum.xda-developers.com/showthread.php?t=1943625
Since I already have the LineageOS repositories (with proprietary files from here) installed on my machine, I started with the code from here: https://github.com/omnirom/android_bootable_recovery
I found out LineageOS doesn't have busybox so I added that to my LineageOS system/external folder from here: https://github.com/omnirom/android_external_busybox
Since it failed to build with encryption, I cherry-picked this commit: https://gerrit.omnirom.org/#/c/22096/
I added the recover.fstab from here to the device folder for the vs995: https://github.com/jcadduono/android_device_lge_vs995/tree/android-6.0/recovery/root
Here are the extra lines and flags I added to my default LineageOS BoardConfig.mk
Code:
RECOVERY_VARIANT := twrp
PRODUCT_COPY_FILES += device/lge/vs995/twrp.fstab:recovery/root/etc/twrp.fstab
TW_THEME := portrait_hdpi
RECOVERY_SDCARD_ON_DATA := true
TW_INCLUDE_CRYPTO := true
That's pretty much everything I've done.
Note to developers: This recovery is a true VS995 build. Please add vs995 to your zips asserts.
Know issues:
- ROMs, kernels, mods, etc. whose zips are built with 'elsa' and/or 'vs996' only asserts will not flash. This is not a bug. If your zip tells you it's for another device and not a vs995, please ask the developer to add this to their asserts.
Download: VS995 TWRP 3.2.1-0
Device tree/kernel source
Old Builds:
VS995 TWRP 3.2.0-0
TWRP 3.2.1-0 Changelog
Code:
What's new in 3.2.1-0:
* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
Thank you very much, even though I don't own a VS995 it's always good to see new development. Thanks again OP.
Link gives me "Access Denied"
wally86 said:
Link gives me "Access Denied"
Click to expand...
Click to collapse
I (think I) fixed it. Please try again.
BackCheck said:
I (think I) fixed it. Please try again.
Click to expand...
Click to collapse
Working now!
I just received my vs995. I'm gonna downgrade to 12A from 15A with uppercut, when use dirtysanta. Should I use twrp 3.0.2-1 like in the guide then then update to 3.2.0-0 or just use 3.2.0-0?
Thanks
wally86 said:
Working now!
I just received my vs995. I'm gonna downgrade to 12A from 15A with uppercut, when use dirtysanta. Should I use twrp 3.0.2-1 like in the guide then then update to 3.2.0-0 or just use 3.2.0-0?
Thanks
Click to expand...
Click to collapse
I would 100% use the 3.0.2-1 from the thread. It has been well tested. From there is you're looking to use a custom kernel or flash a custom rom, then you might test 3.2.0-0. Like I said in the OP, this is the first time I've ever messed with compiling TWRP.
BackCheck said:
I would 100% use the 3.0.2-1 from the thread. It has been well tested. From there is you're looking to use a custom kernel or flash a custom rom, then you might test 3.2.0-0. Like I said in the OP, this is the first time I've ever messed with compiling TWRP.
Click to expand...
Click to collapse
Alright sounds good. I'm gonna try resurrection remix & weta with this version and I'll report back in a few days with how it's working.
Awesome, thanks for keeping the development alive!
Awesome thanks so much. Downloading now. You're great!
Any idea if this is available on the H918 (T-mobile)?
jaysonic88 said:
Any idea if this is available on the H918 (T-mobile)?
Click to expand...
Click to collapse
To the best of my knowledge, there is no 3.2.0 TWRP for the H918, 3.1.1 is the most recent build for it.
This works perfectly with VS995. Thank you!
Any idea how to make this for H990DS ?
Zenns said:
Any idea how to make this for H990DS ?
Click to expand...
Click to collapse
Between the links I posted in the OP and this there are enough breadcrumbs for someone to start building it. That someone isn't me but I would gladly offer advice if needed.
BackCheck said:
Between the links I posted in the OP and this there are enough breadcrumbs for someone to start building it. That someone isn't me but I would gladly offer advice if needed.
Click to expand...
Click to collapse
So I followed your guide (thanks btw!) and successfully compiled twrp 3.2 for the h910 (att) variant. There are some issues for me though. First the terminal in twrp constantly says "child process exited" when I try to type anything in. Also when installing stuff there's a red warning saying "error mount -o bind data/media/0 error 2" or something similar. In the file manager I can access that partition and see files there. Backup and restore seems to work and I tested a couple of magisk zips and they all flashed successfully. Was wondering if you had seen anything like that.
toastyp said:
So I followed your guide (thanks btw!) and successfully compiled twrp 3.2 for the h910 (att) variant. There are some issues for me though. First the terminal in twrp constantly says "child process exited" when I try to type anything in. Also when installing stuff there's a red warning saying "error mount -o bind data/media/0 error 2" or something similar. In the file manager I can access that partition and see files there. Backup and restore seems to work and I tested a couple of magisk zips and they all flashed successfully. Was wondering if you had seen anything like that.
Click to expand...
Click to collapse
Good job. And no, my first build had completely different errors. If you want to PM me your fstab and board config I might be able to look over it sometime and see if I can see anything. Those 2 files look like good places to start.
So I've gone and gotten a sorta working us996 build. Definitely took a couple trys, and my first attempt wiped /data (thanks LG, but this is why I keep backups!) Since I didn't have TW_IGNORE_MISC_WIPE_DATA set. It doesn't have USB otg support like the old 3.0.2 build does (neither does Lineage, but the old build and stock does). I plan on looking at cleaning up my fstab or whatever so that the sdcard is labeled nicely (has internal storage and then storage0 - storage4 with the sdcard being one of those). Havnt tried backups/restoring yet, nor any sort of encryption, but flashing a new lineage build, gapps, and magisk worked. Slightly annoyed I can't build lineage and twrp at the same time (using brunch it pukes out an error about not being able to find some library twrp builds in it's applypatch directory, granted paraphrasing errors doesn't help much) but whatever I can toggle back and forth.
Phoenix591 said:
So I've gone and gotten a sorta working us996 build. Definitely took a couple trys, and my first attempt wiped /data (thanks LG, but this is why I keep backups!) Since I didn't have TW_IGNORE_MISC_WIPE_DATA set. It doesn't have USB otg support like the old 3.0.2 build does (neither does Lineage, but the old build and stock does). I plan on looking at cleaning up my fstab or whatever so that the sdcard is labeled nicely (has internal storage and then storage0 - storage4 with the sdcard being one of those). Havnt tried backups/restoring yet, nor any sort of encryption, but flashing a new lineage build, gapps, and magisk worked. Slightly annoyed I can't build lineage and twrp at the same time (using brunch it pukes out an error about not being able to find some library twrp builds in it's applypatch directory, granted paraphrasing errors doesn't help much) but whatever I can toggle back and forth.
Click to expand...
Click to collapse
I share your pain on the errors with brunch, I get that too. What are you using for fstab? If your using the fstab from jcadduono then OTG is in the file, then it's in there. I don't use OTG so I'm not sure it or encryption is working in mine either. I need testers.
BackCheck said:
I share your pain on the errors with brunch, I get that too. What are you using for fstab? If your using the fstab from jcadduono then OTG is in the file, then it's in there. I don't use OTG so I'm not sure it or encryption is working in mine either. I need testers.
Click to expand...
Click to collapse
No it isn't in jc's fstab, looks like USA-RedDragon has it in his, https://github.com/DesolationRom-Devices/device_lge_h910twrp?files=1 . Going to take a closer look in a day or so.
Well, I got USB otg working, just not the way I hoped. I grabbed the prebuilt kernel image from the repo in my last post and that did the trick when using his fstab as well. So it's probably a kernel problem, since it didn't work with his fstab alone. I tried enabling the more obviously named USB otg kernel config options without success.
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
As we all know - the tablet does not support treble. And we do not have a separate /vendor partition, i'm using /cache as /vendor.
Instructions
1. flash my twrp from link below
2. flash treble zip
3. download any system image from https://forum.xda-developers.com/project-treble/trebleenabled-device-development and flash it as system image
Known Issues
1. need fix gps on SM-T580
2. in aosp 9.0 phh image build-in camera app crashed, all other working fine
Notes
- This is treble build, based on latest lineage 16.0, latest 3.18.137 OC kernel (thanks @followmsi) (with mac fix and 4.0.10.205 wlan driver from codeaurora project) and latest device\configs.
- for /vendor partition I use /cache (it's about 209mb, it' enough for our vendor)
- for /cache partition I use /hidden (it's about 50-60mb, it' enough for cache)
Links
Treble images
SM-T585:
1. 20190401: https://drive.google.com/file/d/1BsmyMb7hI-xYZhIj1XqLNpkfNI9kjDxa/view?usp=sharing
SM-T580:
1. 20190401: https://drive.google.com/file/d/1nQciZhBq_2BnyxbHcP4JuDDA22wUfbzW/view?usp=sharing
Root
Use Magisk if need
Recovery
SM-t585:
1. my repack with add /vendor: https://drive.google.com/file/d/1kEQ-Wwee9MYrF5i69EII8p8R_lOwwf-O/view?usp=sharing
SM-T580:
1. my repack with add /vendor: https://drive.google.com/file/d/1wB665QMq6yesKaMteHQGrmdBAKvkHo0Y/view?usp=sharing
System images
A only and 64Bits
Checked firmwares: almost all pie roms from treble's thread should work. Checked aosp, pixelexperience, arrow, havoc.
Sources
Kernel: https://github.com/Valera1978/android_kernel_samsung_exynos7870/tree/lineage-16.0_treble
Device tree SM-T585: https://github.com/Valera1978/android_device_samsung_gtaxllte/tree/lineage-16.0_treble
Device tree SM-T580: https://github.com/Valera1978/android_device_samsung_gtaxlwifi/tree/lineage-16.0_treble
Vendor SM-T585: https://github.com/Valera1978/android_vendor_samsung_gtaxllte/tree/lineage-16.0_treble
Vendor SM-T580: https://github.com/Valera1978/android_vendor_samsung_gtaxlwifi/tree/lineage-16.0_treble
Hi just flashed the new blissrom gsi and everything seems to be good except that the headphone jack is not working. Haven't tried a different gsi yet to see if it happens on them also or if it is a problem with our tablets. By the way this on a sm-t580
twfs said:
Hi just flashed the new blissrom gsi and everything seems to be good except that the headphone jack is not working. Haven't tried a different gsi yet to see if it happens on them also or if it is a problem with our tablets. By the way this on a sm-t580
Click to expand...
Click to collapse
I just flashed Pixel dust on my sm-t580 and the headphone is ignored.
All sounds play thru the speaker just like you didn't install a headphone.
Also the sound settings are ignored, audio playing at full volume.
Even if I changed it to all soft or even off.
The same is with Viper Os.
There is also the problem that you can't install a bigger open gaps because of the partation isn't large enough.
Thanks for the first version for our tablet.
BT audio does not work in all treble firmware
So every time I boot I get a message that says:
There's an internal problem with your device. Contact your manufacturer for details.
Is this normal after flashing Pixel Experience GSI?
Also had this issue with Resurrection Remix as well
thenubknownasepic said:
So every time I boot I get a message that says:
There's an internal problem with your device. Contact your manufacturer for details.
Is this normal after flashing Pixel Experience GSI?
Also had this issue with Resurrection Remix as well
Click to expand...
Click to collapse
I'm guessing that it will happen when your custom ROM is on a different build number from the underlying official build.
Whatever it is, I think you can just ignore it - as long as both are up-to-date, you should encounter no actual errors.
The mismatch is probaly between the build fingerprint mentioned in the build.prop file in the system partition and the build.prop file in the vendor image, specifically the ro.vendor.build.fingerprint key.
RichyE said:
I just flashed Pixel dust on my sm-t580 and the headphone is ignored.
All sounds play thru the speaker just like you didn't install a headphone.
Also the sound settings are ignored, audio playing at full volume.
Even if I changed it to all soft or even off.
The same is with Viper Os.
There is also the problem that you can't install a bigger open gaps because of the partation isn't large enough.
Thanks for the first version for our tablet.
Click to expand...
Click to collapse
I dont know about the headphones, but i have the same problem with audio always at full volume rr gsi
hi how r u
is there any problem with havoc 2.9 please?
any bugs?
Thanks @Valera1978 for this Treble implementation. I am a huge fan of Treble, as it opens a wide range of ROMs to this tablet. Do you continue development on it? It seems come to a stop?
There is another Treble implementation for this Exynos, this is for Galaxy A3 2017 (A320FL). Maybe that can help.
Please could you make a version that supports AB system images?
@Valera1978
Does it support Android 10
this project supports android 10 can someone tell me please
@Chris_0147 the project is dead, you'd better to sell the device. i'll do that also. it's too old and no developer wants to develop anymore something for it. i tried any a10/a11 gsi rom, all are not supported.
I've been looking at previous comments ,OK , I understand it doesn't support 10 and 11 but has anyone tried installing Pie and then upgrading to 10 or 11.
Nope
You can try and tell us
Chris_0147 said:
You can try and tell us
Click to expand...
Click to collapse
Very helpful, I was hoping for something more constructive
Code:
/*
* Your warranty is now void.
*
* 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
* 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.
*
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (Pie), which is designed to increase performance and reliability over stock Android for your device.
About this project
This is not a regular ROM. Usually, ROMs are based on certain components provided by the vendor (e.g. the heavily modified kernel and certain proprietary components). In contrast, this ROM makes use of a largely unmodified mainline Linux kernel together with many open-source components. Only a tiny bit of firmware is taken from the stock ROM.
This has many advantages for security and maintainability, but also means that certain hardware features (e.g. Camera, GPS) are difficult to implement because they require significant effort and a lot of reverse engineering. Nevertheless, this ROM has reached a state where it is very much usable with the majority of functionality implemented.
(See "Development" in the GitHub README for a more technical introduction...)
New features
Android 9 (LineageOS 16.0) with latest security patches
Linux 4.19 kernel
Meltdown, Spectre, RIDL, Fallout, ... fixes
Vulkan graphics (experimental)
Less/no bloatware
Full backlight control (allows much lower brightness)
F2FS (with a compatible recovery)
Signature spoofing (allows using MicroG instead of proprietary Google Play Services)
WireGuard
Tested features
Display, Backlight control
Graphics (OpenGL etc)
Touchscreen
WiFi, Bluetooth
Audio: Speaker, Headphones, Microphone
Battery, Charging
Sensors: Accelerometer, Magnetometer
Internal Storage/External Storage (SD Card)
USB, USB-OTG
Hardware video accelerated codecs
Planned features (not working yet)
Suspend/Deep sleep states
Not planned
Camera
GPS
FAQ
How is the battery live? Screen-on time is probably similar if not longer, but there is a lot of battery drain in standby mode (even worse than on the ASUS system). I recommend that you turn off the tablet when you're not using it.
How do I obtain root access? There are various ways, but the recommended way for LineageOS is to flash addonsu. (Available below.) However, note that this will break SafetyNet. Use Magisk alternatively.
Can I use Netflix with this ROM? Yes, although you will need to build and flash the Widevine DRM addon manually (see below).
Installation
Preparation
Make sure you are running Android Lollipop (5.0).
You need an unlocked bootloader. LineageOS 16.0 requires me176c-bootstrap 0.3.0, included in me176c-boot 0.3.0. (The old "Intel" bootloader is no longer supported.)
Install TWRP
Make a full backup of the ASUS system. You may want to go back to it.
Do a full factory reset. Wipe data and cache partitions.
Install the main system using the flashable ZIP below.
If needed, install additional addons not included with the main system (see below).
Download
System image (install as ZIP in recovery): lineage-16.0-20191213-UNOFFICIAL-me176c-signed.zip
TWRP recovery image: Available in a separate thread.
Addons
There are various packages you can flash for additional functionality. Most of them are proprietary. All addons persist during LineageOS updates, so you do not need to flash them again after updating.
Google Apps (Google Play Services, Play Store, ...): Use Open GApps (x86, Android 9.0)
Fingerprint (used to pass SafetyNet/Google Play certification): Flash me176c-asus-fingerprint-signed.zip.
Magisk users: Alternatively, you can use MagiskHide Props Config with the fingerprint asus/WW_K013/K013:5.0/LRX21V/WW_K013-12.10.1.36-20151230:user/release-keys
Root: Flash addonsu-16.0-x86-me176c-signed.zip. Remove using addonsu-remove-16.0-x86-me176c-signed.zip
This will break SafetyNet. Alternatively, you can use Magisk.
Widevine DRM (used in certain streaming apps like Netflix): Flash widevine-x86-chromeos-12499.66.0_atlas.zip* [see below]
Houdini (used to run ARM apps on x86, may help if an app shows up as incompatible): Flash houdini-x86-chromeos-12499.66.0_atlas.zip* [see below]
Signature Spoofing (for use with microG): Flash me176c-signature-spoofing-signed.zip to enable signature spoofing. Grant permission with caution only.
*Houdini/Widevine: I do not provide pre-built ZIPs for those two addons. (See this post for more information.)
They can be built easily on any Linux distribution using android_vendor_google_chromeos-x86. Takes just a few minutes (depending on your download speed). No development experience or Android source code required.
If you are unable to build it, someone else may share a build with you. In that case, you can verify its integrity using the SHA-1 checksums available in the release notes.
XDA:DevDB Information
Unofficial LineageOS for ASUS MeMO Pad 7 (ME176C(X)), ROM for the Asus MeMO Pad 7
Contributors
lambdadroid
Source Code: https://github.com/me176c-dev
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: me176c-boot(strap) 0.3.0+
Based On: LineageOS
Version Information
Status: Beta
Created 2019-05-12
Last Updated 2019-12-13
Version History
LineageOS 16.0 (2019-12-13)
lambdadroid said:
Android security patch level: December 5, 2019
Updates: Linux (4.19.75 -> 4.19.89), Mesa (19.1.7 -> 19.3.0), MediaSDK (19.2.1 -> 19.3.1), …
Addons
Widevine/Houdini: Recommended version is now: 12499.66.0_atlas
Download: lineage-16.0-20191213-UNOFFICIAL-me176c-signed.zip
Click to expand...
Click to collapse
LineageOS 16.0 (2019-09-22)
lambdadroid said:
Android security patch level: September 5, 2019
Updates: Linux (4.19.68 -> 4.19.75), Mesa (19.1.4 -> 19.1.7)
Addons
Widevine/Houdini: Recommended version updated to 12239.92.0_nocturne
Download: lineage-16.0-20190922-UNOFFICIAL-me176c-signed.zip
Click to expand...
Click to collapse
LineageOS 16.0 (2019-08-19)
lambdadroid said:
Android security patch level: August 5, 2019
Use WiFi firmware from stock ROM
Add LineageOS power profiles
The default setting disables the turbo frequencies of the CPU to reduce heat (like on LineageOS 14.1).
The old behavior of LineageOS 16.0 (turbo on) can be restored by setting the power profile to "Quick".
Updates: Linux (4.19.57 -> 4.19.68), Mesa (19.1.1 -> 19.1.4), MediaSDK (2019 Q1 -> 19.2.1)
Download: lineage-16.0-20190819-UNOFFICIAL-me176c-signed.zip
Click to expand...
Click to collapse
LineageOS 16.0 (2019-07-07)
lambdadroid said:
Android security patch level: July 5, 2019
Updates: Linux (4.19.49 -> 4.19.57), Mesa (19.0.6 -> 19.1.1)
Download: lineage-16.0-20190707-UNOFFICIAL-me176c-signed.zip
Click to expand...
Click to collapse
LineageOS 16.0 (2019-06-09)
lambdadroid said:
Security Advisory
Android security patch level: June 5, 2019
Added mitigation and CPU microcode update for:
CVE-2018-12126, CVE-2018-12130, CVE-2018-12127, CVE-2019-11091
aka Zombieload, RIDL, Fallout, MDS, … so many names, sigh
Changelog
Enabled MPEG2 video codecs (including hardware acceleration)
Fixed warning: "There's an internal problem with your device. Contact your manufacturer for details."
Flashing "vfp-fix-lineage-16.0-me176c-signed.zip" is no longer necessary
Updates: Linux (4.19.42 -> 4.19.49), Mesa (19.0.4 -> 19.0.6)
Addons
CPU Microcode addon is now obsolete, since CPU microcode updates are included by default again.
Re-install me176c-boot if you have been using it.
Widevine/Houdini: Updated to 11895.118.0_nocturne
There are now simplified build instructions in BUILDING.md
Download
Installable ZIP: lineage-16.0-20190609-UNOFFICIAL-me176c-signed.zip
Click to expand...
Click to collapse
LineageOS 16.0 (2019-05-12)
lambdadroid said:
This build is a major update to LineageOS 16.0 (based on Android 9 Pie) and contains several weeks of work with significant cleanup and other major changes.
Major changes
Based on LineageOS 16.0 (Android 9 Pie)
Use Android Go build configuration to optimize for low RAM (More information)
Hardware accelerated video codecs are now open-source
The remaining proprietary components are no longer included by default and must be flashed manually if needed: (More information)
Widevine DRM (used in certain streaming apps like Netflix)
Houdini (used to run ARM apps on x86)
CPU microcode update
New installation instructions
LineageOS 16.0 requires me176c-bootstrap 0.3.0, included in me176c-boot 0.3.0.
The old ("Intel") bootloader is no longer supported.
There are many new "addons" that can be flashed for full functionality.
Please check the new installation instructions on the LineageOS 16.0 thread before installing this update.
Upgrading
Upgrading from LineageOS 14.1 may work but is untested (and largely unsupported)
Upgrading from LineageOS 16.0 test builds is not possible!
Do a factory reset before installing the new build.
Improvements
Use MAC address from stock ROM for both WiFi and Bluetooth
Put Bluetooth in low power mode while not actively in use (#37)
Fixes
Android security patch level: May 5, 2019
MTP (#33)
Green artifacts on video thumbnails in Gallery (#51)
Headset / headphones microphone detection (#19)
Other changes
Updates: Linux (4.14.72 -> 4.19.42), Mesa (18.2.1 -> 19.0.4), MediaSDK (2018 Q2.2 -> 2019 Q1), …
Download
Installable ZIP: lineage-16.0-20190512-UNOFFICIAL-me176c-signed.zip
Click to expand...
Click to collapse
Great news, I will try today at home! Thanks!!!
I have tested it today. Seems be work without any problems. Thank you.
Houdini/WidevineDRM
So far this ROM is working without any problem, The performance is usable, and the battery is OK due to hardware limitations.
I have a problem installing Houdini and Widevine DRM (I Don't have any development experience) yet i don't understand the instructions on how to make a ZIP and how and where i should put the MK files.
If you dont want to provide the flashable ZIP files that is alright, but could you atleast make a guide that we can follow?
Great Job and Thanks for making this unusable tablet usable again.
Bazgir said:
I have a problem installing Houdini and Widevine DRM (I Don't have any development experience) yet i don't understand the instructions on how to make a ZIP and how and where i should put the MK files.
If you dont want to provide the flashable ZIP files that is alright, but could you atleast make a guide that we can follow?
Click to expand...
Click to collapse
Making a step by step guide is quite difficult because it really depends on the system you are using. I'm guessing that most users will already run into trouble because it can be only built on Linux.
Creating a guide to set up a virtual machine etc., how to get into a terminal etc would require a lot of effort. This is time that I would rather spent in development. I realize this entire situation isn't ideal, but I haven't been able to come up with a better solution.
If you have a working Linux system, building should be pretty simple:
Download and unpack https://github.com/me176c-dev/android_vendor_google_chromeos-x86/archive/11647.154.0_nocturne.tar.gz
Open a terminal and run (in the extracted folder):
Code:
$ ./extract-files.sh
$ zip/build.sh
Find flashable ZIPs in zip/out.
No development experience needed.
This is also roughly what is already explained in https://github.com/me176c-dev/android_vendor_google_chromeos-x86 although the README has more background information because it is really intended for people that would like to use that project in own projects (e.g. in other ROMs).
Maybe someone else here would like to provide more detailed instructions?
Hey, Thanks for the Reply!
I have already setup the Virtual Machine and even tried "Sudo ./extract-files.sh" I'll get the messedge "https://imgur.com/a/Y1lKg5P"
It probebly fail because i don't have the OS for the chromeOS, But then again where should i put the extractions file so that the script can locate and extract the nessecary files?
Am i missing something? a file maybe? or should the script takeout the nessecery files from internet? (i have almost no clue what im talking about )
I have the ASUS K013 (ME176CX) (1GB RAM) (8GB ROM)
Thanks again!
Hello Again,
I managed to create the ZIP files, The only problem i had was that i needed the recovery files for Chromeos (Nocturne),
Ones i had the files i extracted the recovery and got the file named propretary, and build the ZIP.
The link for the "I cant provide it for you because i don't have 10 post"
For other builds: cros-update-service-appspot.com (Try to find the one called nocturne and then 73 (then eddit the url so that u get 154.0 insted of 104.1))
This was a crusial step to understand how to extract the files, u also need to put the zip in to the same directori as extract.build.sh,
I have not yet tried this, so im not sure if it will work. The SHA.1 Matches
Thanks!!
Bazgir said:
I have the ASUS K013 (ME176CX) (1GB RAM) (8GB ROM)
Click to expand...
Click to collapse
There is really a K013 with only 8 GB internal storage?
I've read this a few times, but haven't seen one before. Good to know that the ROM works fine on it.
Bazgir said:
I have already setup the Virtual Machine and even tried "Sudo ./extract-files.sh" I'll get the messedge "https://imgur.com/a/Y1lKg5P"
It probebly fail because i don't have the OS for the chromeOS, But then again where should i put the extractions file so that the script can locate and extract the nessecary files?
Am i missing something? a file maybe? or should the script takeout the nessecery files from internet? (i have almost no clue what im talking about )
Click to expand...
Click to collapse
Great! The script downloads everything for you, but it looks like you don't have "curl" installed. On Ubuntu, you can install it using "sudo apt install curl". Then it will probably download the same file you have already downloaded manually.
Bazgir said:
I managed to create the ZIP files, The only problem i had was that i needed the recovery files for Chromeos (Nocturne),
Ones i had the files i extracted the recovery and got the file named propretary, and build the ZIP.
The link for the "I cant provide it for you because i don't have 10 post"
For other builds: cros-update-service-appspot.com (Try to find the one called nocturne and then 73 (then eddit the url so that u get 154.0 insted of 104.1))
This was a crusial step to understand how to extract the files, u also need to put the zip in to the same directori as extract.build.sh,
Click to expand...
Click to collapse
You can skip this if you have "curl" installed.
Thanks for trying to build it and your feedback! I will try to make the README more clear, especially regarding additional dependencies (e.g. "curl") plus the commands to run.
I'm supprised on how the ROM turned out to be, being a x86 platform even tho it's not supported anymore, with Houdini and Widevine.
I was able to play games on the phone such as Old school runescape on the tablet (Not perfect but playable) watch videos on youtube with the sound bug :/
The battery is better but still horrible (it was like this before), Might download somekind of deepsleep app such as Greenify for that.
What magisk module i have downloaded för best possible preformance is NFS-INJECTOR in Magisk.
I don't have any major problem with the 8GB ROM even tho the emmc memory is very very bad (Read 40Mb/s and write 8-10Mb/s) Somehow when i installed old SD card which is R 20Mb/s and 10Mb/s the tablets performance increase even tho it has lover read and write speed.
Is there a way to optimize the performance for the tablet even more? The main problem is RAM and ROM, i feel like the emmc memory and the amount of ram is holding back the CPU/GPU
Thanks!
Bazgir said:
I was able to play games on the phone such as Old school runescape on the tablet (Not perfect but playable) watch videos on youtube with the sound bug :/
Click to expand...
Click to collapse
Sound bug?
Bazgir said:
I don't have any major problem with the 8GB ROM even tho the emmc memory is very very bad (Read 40Mb/s and write 8-10Mb/s) Somehow when i installed old SD card which is R 20Mb/s and 10Mb/s the tablets performance increase even tho it has lover read and write speed.
Is there a way to optimize the performance for the tablet even more? The main problem is RAM and ROM, i feel like the emmc memory and the amount of ram is holding back the CPU/GPU
Click to expand...
Click to collapse
Android and most apps raise their requirements each year as new devices are released with higher specs. Many devices come with 6GB+ RAM now.
Altogether, this tablet was already low-end when it was released. The CPU is pretty good compared to low-end ARM processors. But with ~800MB usable RAM this tablet can simply not keep up with apps that require more and more resources.
This tablet would do fine if Android and apps were continuously optimized to use less resources. However, the development actually goes into the opposite direction.
Sooner or later, this tablet will probably no longer manage to boot new Android versions at all, simply because all RAM is taken up by the system.
My point is: If you want to optimize this tablet, you need to go back in time. Not just with the OS (e.g. by downgrading to Android 4.4 KitKat), but with all apps you are using. If you go to ~2015 this tablet will likely do a much better job.
This ROM is definitely less "optimized" for this specific device, simply because it does not have most of the device-specific hacks they had for these Intel tablets back then. But this is the price for being able to keep it up to date with acceptable effort. And if you look back to ASUS's version of Lollipop, it usually didn't feel much better either even though it was technically more "optimized".
lambdadroid said:
Sound bug?
Android and most apps raise their requirements each year as new devices are released with higher specs. Many devices come with 6GB+ RAM now.
Altogether, this tablet was already low-end when it was released. The CPU is pretty good compared to low-end ARM processors. But with ~800MB usable RAM this tablet can simply not keep up with apps that require more and more resources.
This tablet would do fine if Android and apps were continuously optimized to use less resources. However, the development actually goes into the opposite direction.
Sooner or later, this tablet will probably no longer manage to boot new Android versions at all, simply because all RAM is taken up by the system.
My point is: If you want to optimize this tablet, you need to go back in time. Not just with the OS (e.g. by downgrading to Android 4.4 KitKat), but with all apps you are using. If you go to ~2015 this tablet will likely do a much better job.
This ROM is definitely less "optimized" for this specific device, simply because it does not have most of the device-specific hacks they had for these Intel tablets back then. But this is the price for being able to keep it up to date with acceptable effort. And if you look back to ASUS's version of Lollipop, it usually didn't feel much better either even though it was technically more "optimized".
Click to expand...
Click to collapse
Ignore the sound bug, I will just use headphones (small fix).
That's true, om overall pretty happy with the result nevertheless.
Thank you.
Bazgir said:
Ignore the sound bug, I will just use headphones (small fix).
Click to expand...
Click to collapse
I'm not aware of a "sound bug". If you would like to have it fixed, you will need to explain it a bit further.
Do not hesitate to report minor problems; some of them are really easy to fix and exist only because of an oversight. For all others I will decide if they are worth the effort.
lambdadroid said:
I'm not aware of a "sound bug". If you would like to have it fixed, you will need to explain it a bit further.
Do not hesitate to report minor problems; some of them are really easy to fix and exist only because of an oversight. For all others I will decide if they are worth the effort.
Click to expand...
Click to collapse
It's very hard to explain the sound it makes, but when ever i start a youtube video, it basicly has to encode the video and the sound, The sound syncs upp with the video and there for when the video is a bit choppy it creates those weird sounds.
This is what im talking about "https://vocaroo.com/i/s1s7rSAFCIv0"
Not sure if its a video encoding problem but looks like it.
Thanks
Bazgir said:
It's very hard to explain the sound it makes, but when ever i start a youtube video, it basicly has to encode the video and the sound, The sound syncs upp with the video and there for when the video is a bit choppy it creates those weird sounds.
This is what im talking about "https://vocaroo.com/i/s1s7rSAFCIv0"
Not sure if its a video encoding problem but looks like it.
Thanks
Click to expand...
Click to collapse
I had also encounter this problem in LineageOS 14.1 of this tablet... I have noticed that it always happen when multiple sounds are composed by the tablet itself instead of composed by one app. (When it plays notification sound when music (using music player) playing, it sounds laggy for a while, but when a game plays multiple sounds, it's fine.) Also, after not playing any sounds for a while, it will create a loud pop sound right when the first sound is played. (And it hurts my ear when I'm using earphones... :silly: ) I haven't managed to build the Widevine and Houdini pack, so I don't know if the problem still goes the same in 16.1, but it seems that the same problem still exists. Hope that these information helps to fix the bug.
Frisk Dreemurr said:
I had also encounter this problem in LineageOS 14.1 of this tablet... I have noticed that it always happen when multiple sounds are composed by the tablet itself instead of composed by one app. (When it plays notification sound when music (using music player) playing, it sounds laggy for a while, but when a game plays multiple sounds, it's fine.) Also, after not playing any sounds for a while, it will create a loud pop sound right when the first sound is played. (And it hurts my ear when I'm using earphones... :silly: ) I haven't managed to build the Widevine and Houdini pack, so I don't know if the problem still goes the same in 16.1, but it seems that the same problem still exists. Hope that these information helps to fix the bug.
Click to expand...
Click to collapse
Here is the link for Houdini: https://mega.nz/#!E9li3QBJ!uN_TVlPjWUu50F5j4FIk6CqapMt9_k7ix5r01GrdyVQ
Here is the link for Widevine: https://mega.nz/#!kxlWlI6Z!u5OqNzys3r1LyMq3U1UOejsxj87GR1-f6f5Bn6u12mI
Not sure if it will work for you, make sure you do a backup :good:
I´ve installed the ROM and it works great! Thanks a lot!
Bazgir said:
It's very hard to explain the sound it makes, but when ever i start a youtube video, it basicly has to encode the video and the sound, The sound syncs upp with the video and there for when the video is a bit choppy it creates those weird sounds.
This is what im talking about "https://vocaroo.com/i/s1s7rSAFCIv0"
Not sure if its a video encoding problem but looks like it.
Click to expand...
Click to collapse
Frisk Dreemurr said:
I had also encounter this problem in LineageOS 14.1 of this tablet... I have noticed that it always happen when multiple sounds are composed by the tablet itself instead of composed by one app. (When it plays notification sound when music (using music player) playing, it sounds laggy for a while, but when a game plays multiple sounds, it's fine.)
Click to expand...
Click to collapse
Weird, I've never seen (heard) this issue even though I test video playback quite often. I used to have problems with touch sounds that were usually played high pitched for some reason, but it magically went away with some later 14.1 release.
Frisk Dreemurr said:
Also, after not playing any sounds for a while, it will create a loud pop sound right when the first sound is played. (And it hurts my ear when I'm using earphones... :silly: )
Click to expand...
Click to collapse
I know about this one. Quite annoying. I suspect that it is due to some kind of energy saving. (The headphones get turned off after unused for a while.) Not sure how to avoid it...
Frisk Dreemurr said:
I haven't managed to build the Widevine and Houdini pack, so I don't know if the problem still goes the same in 16.1
Click to expand...
Click to collapse
FYI you don't need Widevine/Houdini for most apps. Listening to Music, watching normal YouTube videos works fine without it.
Widevine is mainly needed for paid video streaming (e.g. movies, ...), and Houdini for more uncommon apps and games that are not compiled for x86 (you can install it as soon as you see an app that is displayed as "incompatible" with your device).
Bazgir said:
Here is the link for Houdini: https://mega.nz/#!E9li3QBJ!uN_TVlPjWUu50F5j4FIk6CqapMt9_k7ix5r01GrdyVQ
Here is the link for Widevine: https://mega.nz/#!kxlWlI6Z!u5OqNzys3r1LyMq3U1UOejsxj87GR1-f6f5Bn6u12mI
Not sure if it will work for you, make sure you do a backup :good:
Click to expand...
Click to collapse
Thanks a lot for offering the files! :good: But it seems like it's not working on my tablet... :crying: (The SHA-1 of the files I downloaded matches the correct one.) Any ways to solve this problem?
Frisk Dreemurr said:
it seems like it's not working on my tablet... :crying: (The SHA-1 of the files I downloaded matches the correct one.) Any ways to solve this problem?
Click to expand...
Click to collapse
Weird error. Can you try flashing from internal storage/external SD card or using ADB sideload? Might be related to USB OTG.
crDroid 6.2 ROM 15-01-2020
There's no guarantee nothing, don't use it if you don't know what you're doing!
SAVE your DATA before!
Make sure you have a custom recovery installed (TWRP is the preferred recovery. [I'm not using Fox recovery, I'm not going to give you advice.])
Boot into recovery
Wipe data, cache partitions to clean install. Wipe dalvik, cache to update previous crDroid.
(If your /data partition secured, maybe need format /data if you want to use this ROM.)
Flash Rom in TWRP (sideload or copy any storage)
Flash OpenGapps (Optional) [I'm not using GAPPS, I'm not going to give you advice.]
Flash Magisk Root (Optional) [I'm not using Magisk, I'm not going to give you advice.]
Reboot (If TWRP warn that there is no system, it doesn't matter, go reboot.)
First boot may take up to 1 minute.
DOWNLOAD SF
DOWNLOAD AD
All ROMs here: LINK
Known issues: don't know
*
Screenshots: LINK
OS source: LINK Many thanks to adi153!
ROM OS Version: 10.x Q
ROM Kernel: Linux 3.18.140 (not my work)
ROM info: Q10 Lineage-17.1, system_root partition, Android quota removed (easier to go back to earlier 7.x-9.x ROMs).
If you have previously used Android 9.x or 10.x ROM which has a quota set on the data partition, you can remove the quota in TWRP, and not need format the data partition (this method tested, working was for me, but no guarantee for by all means)
commands:
Code:
tune2fs -O ^quota /dev/block/bootdevice/by-name/userdata
tune2fs -Q ^usrquota,^grpquota /dev/block/bootdevice/by-name/userdata
If you then use a ROM that configures quota (fstab.qcom), you can start over, if do not want quota. Or cleaning from fstab: "quota".
Created 24-12-2019 6.0 version
Last Updated 15-01-2020 6.2 (build3)
I am not aware that it contains malicious code in the ROM, I have never put it in. This is a ported ROM, all its elements come from the Internet.
You're welcome.
New build 15.01.2020, & many changes to the system. I'd like to get feedback on whether VOLTE is working? Thanks.
SYS update V1 out: 14-01-2020
Something wrong with the system updates, I moved it to the test directory.
Nice
Wow, a new rom... Thanks szanalmas, will give feedback after testing it
@szanalmas
Edit: Already tested your rom, so stable and smooth...
But found some small bug (doesn't really matter anyway but you may need know):
-At first boot/crdroid setup wizard, email exchange request permission but when i grant it permission manager crash (but back normal after that)
-When i change the hardware button function to screenshot... The Setting app will crash and back to main menu
Just that, still looking for other
Big thanks again for this nice rom
(Sorry for my bad english :v)
@szanalmas thanks ...for stable ROM.
---------- Post added at 04:18 AM ---------- Previous post was at 04:00 AM ----------
From long time i was waiting for stable ROM. Thanks for your hard work.
@szanalmas thanks for make stable ROM :good:
while there are no bugs,
if there are bugs
I'll tell you later
thanks man i like crdroid
rom stable smooth did not find any bug after 2 hours use
Fadly357 said:
But found some small bug (doesn't really matter anyway but you may need know):
-At first boot/crdroid setup wizard, email exchange request permission but when i grant it permission manager crash (but back normal after that)
-When i change the hardware button function to screenshot... The Setting app will crash and back to main menu
Click to expand...
Click to collapse
Thanks for the feedback!
I didn't know about the first bug, probably because I have always denied email permissions in the wizard. I have bad habits!
I knew about the second bug, some of the function settings on the buttons don't work.
Unfortunately, these bugs are in the official ROM, but I think they will be fixed over time.
And of course, the SD card camera and gallery permission bugs have remained, but the solution is to use internal storage for the time being.
szanalmas said:
Thanks for the feedback!
I didn't know about the first bug, probably because I have always denied email permissions in the wizard. I have bad habits!
I knew about the second bug, some of the function settings on the buttons don't work.
Unfortunately, these bugs are in the official ROM, but I think they will be fixed over time.
And of course, the SD card camera and gallery permission bugs have remained, but the solution is to use internal storage for the time being.
Click to expand...
Click to collapse
Okay, will tell you as soon as possible if i found other
could you teach me rom build? i wanna learn and help
@szanalmas
About your ported TWRP, can you install magisk? When i use your TWRP to install magisk, the magisk installation failed, says it can mount vendor which is same as cust, right?
viethoang18 said:
could you teach me rom build? i wanna learn and help
Click to expand...
Click to collapse
Sorry I can't give you guidance. I'm not building ROM, I'm just porting. If you really want to build ROM, I recommend the ViperOS developers, this was the only Official build for this phone (7.1.2). Building a ROM requires 3 things, the kernel, vendor, and AOSP. Since phone manufacturers largely do not make their source code public, their construction is tremendously laborious and time consuming.
If you want to port, it is highly recommended that you know Linux, which is quite a bit of time and energy. Actually, you need to learn the basics of linux for Android, but at least to the point where you can already interpret log error messages.
I don't know if you use linux, if you don't and you want to start with it, install linux, configure it well, and compile a linux kernel for ugglite, which starts with ROM 10. If you want to go hard, thoroughly, and deeper, do it all without installing a linux graphical interface. I don't really know how much time it takes to easily manage Linux. How to port Android 10 on windows I don't know, but I think it's not easy.
And on top of that, Android has some specific changes that are different from the Linux system, so you also have to get to know Android so.
And now we're just about to boot on Linux based Android, on the DalvikVM running applications is another world with lots of Java code.
For all this, there is no guide to doing this or that, you need to apply knowledge in a complex way.
I only do this on a hobby level.
Fadly357 said:
@szanalmas
About your ported TWRP, can you install magisk? When i use your TWRP to install magisk, the magisk installation failed, says it can mount vendor which is same as cust, right?
Click to expand...
Click to collapse
I once used the magisk in TWRP but not this ROM. It worked for some.
But I didn't write in my post on my TWRP either now.
(I don't use magisk now.)
Use Canary: LINK
Or whatever.
szanalmas said:
Sorry I can't give you guidance. I'm not building ROM, I'm just porting. If you really want to build ROM, I recommend the ViperOS developers, this was the only Official build for this phone (7.1.2). Building a ROM requires 3 things, the kernel, vendor, and AOSP. Since phone manufacturers largely do not make their source code public, their construction is tremendously laborious and time consuming.
If you want to port, it is highly recommended that you know Linux, which is quite a bit of time and energy. Actually, you need to learn the basics of linux for Android, but at least to the point where you can already interpret log error messages.
I don't know if you use linux, if you don't and you want to start with it, install linux, configure it well, and compile a linux kernel for ugglite, which starts with ROM 10. If you want to go hard, thoroughly, and deeper, do it all without installing a linux graphical interface. I don't really know how much time it takes to easily manage Linux. How to port Android 10 on windows I don't know, but I think it's not easy.
And on top of that, Android has some specific changes that are different from the Linux system, so you also have to get to know Android so.
And now we're just about to boot on Linux based Android, on the DalvikVM running applications is another world with lots of Java code.
For all this, there is no guide to doing this or that, you need to apply knowledge in a complex way.
I only do this on a hobby level.
Click to expand...
Click to collapse
can i use Unbutu wls on windows ?
@szanalmas I flashed this ROM.
ULTRA SMOOTH... NO SERIOUS BUG, SOMETIMES AUTO BRIGHTNESS RESPONSE SLOWLY. Suddenly high brightness automatically. Another issue with attached sd card asking for format.
"Issue with sandisk SD Card"
Its for daily use is ok.
bug, when enabling ambient display d2tw stopped not wroking after disable ambient dt2w work again
Thank you very much feedbacks and thanks to everyone! :good:
Call volume on speaker is very high by default
@szanalmas Call volume on speaker is very high by default. Please set lower level by default. I hope in new build it willbe resolve.
Thanks...
ahmedhelmy71 said:
bug, when enabling ambient display d2tw stopped not wroking after disable ambient dt2w work again
Click to expand...
Click to collapse
This is what LINK is all about, and I still hold that the double-tap feature cannot be used for two things at once. What's interesting is that I can't find the ambient display double-tap menu option, and there's a separate one in Havoc ambient settings.
This is also an Official bug unfortunately.
*
cpglbitm said:
@szanalmas I flashed this ROM.
ULTRA SMOOTH... NO SERIOUS BUG, SOMETIMES AUTO BRIGHTNESS RESPONSE SLOWLY. Suddenly high brightness automatically. Another issue with attached sd card asking for format.
"Issue with sandisk SD Card"
Its for daily use is ok.
Click to expand...
Click to collapse
The SD card problem is very-very interesting.
What filesystem is in sd card?
Could you send us a logcat digest right after the phone is started?
Code:
adb logcat | grep vold > sdcardproblem.txt
viethoang18 said:
can i use Unbutu wls on windows ?
Click to expand...
Click to collapse
I don't know. I haven't used Windows for years, sorry.
Important information:
This thread is for LineageOS 19.1 opensource builds for Wingtech WT88047, marketed as Redmi 2 by Xiaomi. The following will not be supported in this thread:
Custom Kernels
Mods
Modified system files
Xposed
Magisk
What's not working:
SELinux Permissive
Encryption
Connecting to some Bluetooth Classic devices
Installation:
If you are on the stock OS, you will first need a custom recovery. You can get the recommended Lineage recovery here.
If you are coming from stock or other ROMs, you need to do a factory reset, and resize your partitions with this tool. It is highly recommended to flash it using ADB sideload.
As always, make sure to backup before installing this ROM.
For more detailed instructions, please visit:
Install LineageOS on wt88047
Download link:
SourceForge
Recommended Google Apps package:
MindTheGapps
Recommended Firmware:
Google Drive
Bug reports:
How to submit a bug report
Gitlab Issues
Donate to support development:
Donate via PayPal to tipzrickycheung
Donate via PayPal to nicknitewolf
Donate via PayPal to LineageOS
Source Code:
Device tree
Kernel
LineageOS Github
Contributors
@tipzrickycheung, @althafvly, @nicknitewolf, Lineage Team
ROM OS Version: 12.x S
ROM Kernel: Linux 3.10.x
ROM Firmware Required: M8936FAAAANUZM-1.33887.1.41528.1
Based On: LineageOS
Reserved
New update!
20220218
- Fixed Bluetooth
- Baseband and IMEI now detected
Download
Perfect Android 12, basically everything works fine, thank you very much for your work.
However, there are also some problems: 1. The size of the "oem partition" is insufficient and needs to be expanded. The expansion zip provided by you cannot be used. 2. Some animations of the settings application are missing, such as the last two pictures. 3. The system time will return to the compile time after restarting.
I can not speak English
Are you in Coolapk?
pinksheer said:
Perfect Android 12, basically everything works fine, thank you very much for your work.
However, there are also some problems: 1. The size of the "oem partition" is insufficient and needs to be expanded. The expansion zip provided by you cannot be used. 2. Some animations of the settings application are missing, such as the last two pictures. 3. The system time will return to the compile time after restarting.
I can not speak English
Are you in Coolapk?
Click to expand...
Click to collapse
Yup, I am on Coolapk
pinksheer said:
Perfect Android 12, basically everything works fine, thank you very much for your work.
However, there are also some problems: 1. The size of the "oem partition" is insufficient and needs to be expanded. The expansion zip provided by you cannot be used. 2. Some animations of the settings application are missing, such as the last two pictures. 3. The system time will return to the compile time after restarting.
I can not speak English
Are you in Coolapk?
Click to expand...
Click to collapse
About the expansion zip, you need to have the stock partition layouts to start with.
New update!
20220219
- Fixed LiveDisplay
- Added SEPolicy Changes
- Added Binder and lmk kernel backports
Note:
Enforcing now boots but adb, camera, baseband, etc. no longer works with enforcing turned on. Builds are still shipped with permissive.
Download
I'm just popping in to say this looks very promising! Thanks for caring about this device. Please don't give up with this build
New update!
20220227
- Fixed Hotspot (Can be fixed for 18.1 too)
- Software navkeys now works properly
Note:
Enforcing now boots but adb, camera, baseband, etc. no longer works with enforcing turned on. Builds are still shipped with permissive.
Download
hi developer wt88047 @tipzrickycheung how fixed for twrp error E2001 : Failed to update vendor image? for flashing build lineageos unofficial 19
now iam dowgrade lineage os unofficiall 18.0 build from @nicknitewolf its work
BangJhon.id said:
hi developer wt88047 @tipzrickycheung how fixed for twrp error E2001 : Failed to update vendor image? for flashing build lineageos unofficial 19
now iam dowgrade lineage os unofficiall 18.0 build from @nicknitewolf its work
Click to expand...
Click to collapse
Use the partition expand package first
pinksheer said:
Perfect Android 12, basically everything works fine, thank you very much for your work.
However, there are also some problems: 1. The size of the "oem partition" is insufficient and needs to be expanded. The expansion zip provided by you cannot be used. 2. Some animations of the settings application are missing, such as the last two pictures. 3. The system time will return to the compile time after restarting.
I can not speak English
Are you in Coolapk?
Click to expand...
Click to collapse
I think I might have fixed bug 3, will push an update when appropriate.
one by one step i try, no fixed this message, from recovery all path, partisi, i not working instal lineage os based 19.0
New update!
20220228
- Fixed TimeKeep (?)
Note:
Enforcing now boots but adb, camera, baseband, etc. no longer works with enforcing turned on. Builds are still shipped with permissive.
Download
Thanks for the release! Today I tried to install this, but I got error 1 in TWRP saying "failed to update vendor image". Is it required to add a dedicated treble vendor partition with this tool? Just asking because this may have to do with the system partitioning otherwise.
RandomNewbie said:
Thanks for the release! Today I tried to install this, but I got error 1 in TWRP saying "failed to update vendor image". Is it required to add a dedicated treble vendor partition with this tool? Just asking because this may have to do with the system partitioning otherwise.
Click to expand...
Click to collapse
No, and we don't support using that tool.
tipzrickycheung said:
Use the partition expand package first
Click to expand...
Click to collapse
I am unable to install the partition expand package that you have provided (resize_wt88047x_v6.zip) on my device. TWRP gives me this error - "Can not extract update-script. Do you have it in package?". I have the 8gb variant. Any help is appreciated!
SaneComputing said:
I am unable to install the partition expand package that you have provided (resize_wt88047x_v6.zip) on my device. TWRP gives me this error - "Can not extract update-script. Do you have it in package?". I have the 8gb variant. Any help is appreciated!
Click to expand...
Click to collapse
Update your TWRP.
New update!
20220323
Android 12L!
Note:
Enforcing now boots but adb, camera, baseband, etc. no longer works with enforcing turned on. Builds are still shipped with permissive.
Download
Still using latest twrp but error show up everytime