Hi,
i'm trying to build Q for this Clark, anyone want to test?
If yes, pm me on Telegram (@DarkDroidDev)
EDIT: Join telegram group @clarkdev for beta testing or see development
Hi, i'm in!
DarkDroidDev said:
Hi,
i'm trying to build Q for this Clark, anyone want to test?
If yes, pm me on Telegram (@DarkDroidDev)
Click to expand...
Click to collapse
Link?
i 'm in too..
Link?
@DarkDroidDev already sent the DM from telegram
Выложите пожалуйста √17
Development resumed, who want to see progress or help with testing, feel free to join telegram group
@clarkdev
Any chance you could provide links without telegram?
Not looking to add another messenger that I'll forget I have in 6 months lol
Maybe you are also interested in my efforts to bring clark to 17.1
Kernel: https://github.com/chrmhoffmann/android_kernel_motorola_msm8992/tree/staging/lineage-17.1
Device: https://github.com/chrmhoffmann/android_device_motorola_clark/tree/staging/lineage-17.1
Vendor: https://github.com/chrmhoffmann/proprietary_vendor_motorola/tree/staging/lineage-17.1
Additional patches: https://gist.github.com/chrmhoffmann/dd232f142dcde4c590a659e85944f7a4
The above trees are not supposed to remain stable, I do force pushs until clean and uploadable to lineage (if ever).
Very early testbuild: https://www.androidfilehost.com/?fid=4349826312261826984
Credits go mainly to the lineage community and their commits on gerrit, and of course: hashbang, randomblame and highwaystar - esp for the camera headers .
I'd also be interested but don't use Telegram
ac2323 said:
I'd also be interested but don't use Telegram
Click to expand...
Click to collapse
has anyone tried chrmhoffmann's rom yet (post #10)? I'm interested to see if it boots and how stable it is. Also he's openly sharing his source code.
Nice.
Wheels564 said:
has anyone tried chrmhoffmann's rom yet (post #10)? I'm interested to see if it boots and how stable it is. Also he's openly sharing his source code.
Click to expand...
Click to collapse
Yes, working nice.
@DarkDroidDev Hey, how did you extract the proprietary blobs? The instruction says that one needs to have an installable zip of LineageOS for clark, or already have the device runnning the LOS. I tried to extract it just from my stock Moto X Style with the script and it did something, but I'm not sure if it's going to work.
Edit: I'm also interested in testing the 17.1 build, since the one I'm trying to build following the instruction is 14.1 and actually it fails because of lack of some vendor files :/ But I'm also not interested in joining Telegram
Edit: Oh, I missed the @chrmhoffmann post!
hi, chrmhoffmann. thank you for your work.
chrmhoffmann said:
Maybe you are also interested in my efforts to bring clark to 17.1
Kernel: https://github.com/chrmhoffmann/android_kernel_motorola_msm8992/tree/staging/lineage-17.1
Device: https://github.com/chrmhoffmann/android_device_motorola_clark/tree/staging/lineage-17.1
Vendor: https://github.com/chrmhoffmann/proprietary_vendor_motorola/tree/staging/lineage-17.1
Additional patches: https://gist.github.com/chrmhoffmann/dd232f142dcde4c590a659e85944f7a4
The above trees are not supposed to remain stable, I do force pushs until clean and uploadable to lineage (if ever).
Very early testbuild: https://www.androidfilehost.com/?fid=4349826312261826984
Credits go mainly to the lineage community and their commits on gerrit, and of course: hashbang, randomblame and highwaystar - esp for the camera headers .
Click to expand...
Click to collapse
Hi, chrmhoffmann. Thank you for your work. I previously tested your 20200718 upgrade. I have installed the same date recovery and the latest magisk20.4. Unfortunately the system will not start. I also tried wipe system wipe cache wipe data and reinstalled it again, but it still didn't work.
I cannot find any kind of forum for @DarkDroidDev . I also can't find a forum for @chrmhoffmann but I found the andoridfilehost link for him with his builds.
https://androidfilehost.com/?a=show&w=files&flid=313335
I did a lot of trial and error and I notice that he is posting his own Lineage recovery which through Googling I find is apparently most use for updating a ROM. I am using the latest Clark TWRP 3.4.0-0 and once you install your first LOS17 you can no longer flash an updated build because TWRP seems to be unable to wipe an android 10 build.
@chrmhoffman has LOS Recovery builds that do allow you to update his LOS17 to a new build. His latest LOS recovery is named recovery.img from 8/19/20. LOS Recovery is not very functional and likewise does not even have the option to wipe. The only way I have been able to wipe these LOS builds is to flash back to stock Android 7 Moto ROM and start over fresh. I am using NPHS25.200-23 which is the last Moto ROM for Clark. I have found flashing back to stock is a good practice when moving to a new ROM and I am getting much better with practice so it is not so onerous.
So here's what I do to flash the initial working version of LOS 17 on my Clark. I have found you can use any of his builds. Thus you can start with his latest build 20200715.
Flash stock Android 7 using fastboot
Flash TWRP using fastboot
Flash 20200715 build and latest Android 10.0 Open Gapps with TWRP
This is pretty much the standard old way that we always do. Now if you want to update 20200715 with either a clean or a dirty flash when he drops a new build you cannot use TWRP to do this because you can't wipe. If you want to clean flash a new build you will have to start over with stock. If you want to update with a dirty flash then you will need LOS Recovery. Easiest way is to flash the LOS Recovery image with TWRP but you can also fastboot flash it.
Flash LOS Recovery
Update ROM from LOS Recovery.
I have been able to flash Magisk from Stock and it seems to work fine but I have not tried yet to see how LOS Recovery handles Magisk. I am looking for help from anyone with more experience than I have to explain this better and most importantly find out where discussion is happening. The ROM works beautifully and so far much better than @randomblame ROM. No boot problems, WiFi tether works great, camera is better. So far it is great. So give it a try.
kb8no said:
I cannot find any kind of forum for @DarkDroidDev . I also can't find a forum for @chrmhoffmann but I found the andoridfilehost link for him with his builds.
https://androidfilehost.com/?a=show&w=files&flid=313335
I did a lot of trial and error and I notice that he is posting his own Lineage recovery which through Googling I find is apparently most use for updating a ROM. I am using the latest Clark TWRP 3.4.0-0 and once you install your first LOS17 you can no longer flash an updated build because TWRP seems to be unable to wipe an android 10 build.
@chrmhoffman has LOS Recovery builds that do allow you to update his LOS17 to a new build. His latest LOS recovery is named recovery.img from 8/19/20. LOS Recovery is not very functional and likewise does not even have the option to wipe. The only way I have been able to wipe these LOS builds is to flash back to stock Android 7 Moto ROM and start over fresh. I am using NPHS25.200-23 which is the last Moto ROM for Clark. I have found flashing back to stock is a good practice when moving to a new ROM and I am getting much better with practice so it is not so onerous.
So here's what I do to flash the initial working version of LOS 17 on my Clark. I have found you can use any of his builds. Thus you can start with his latest build 20200715.
Flash stock Android 7 using fastboot
Flash TWRP using fastboot
Flash 20200715 build and latest Android 10.0 Open Gapps with TWRP
This is pretty much the standard old way that we always do. Now if you want to update 20200715 with either a clean or a dirty flash when he drops a new build you cannot use TWRP to do this because you can't wipe. If you want to clean flash a new build you will have to start over with stock. If you want to update with a dirty flash then you will need LOS Recovery. Easiest way is to flash the LOS Recovery image with TWRP but you can also fastboot flash it.
Flash LOS Recovery
Update ROM from LOS Recovery.
I have been able to flash Magisk from Stock and it seems to work fine but I have not tried yet to see how LOS Recovery handles Magisk. I am looking for help from anyone with more experience than I have to explain this better and most importantly find out where discussion is happening. The ROM works beautifully and so far much better than @randomblame ROM. No boot problems, WiFi tether works great, camera is better. So far it is great. So give it a try.
Click to expand...
Click to collapse
From what I've seed Darkdroiddev removed Clark from his Github so I assume he is no longer working on this phone and this thread is probably dead. Randomblame hasn't posted since February. chrmhoffmann's thread https://forum.xda-developers.com/mo...opment/unofficial-lineage-17-1-clark-t4123077 actually has a link to official Lineage gerrit which means we are well on our way to becoming official Lineage again. Meanwhile I'll keep posting LOS 14.1 for MMBL until we get there.
Related
I have a rooted phone with a rom that isn't being supported anymore but it actually works great. I just want to update to oreo so is there a rom I can flash from twrp that is already rooted and ready to go? I saw a video of a how to install oreo 8.1 but it's just music playing with someone showing the menu option and no installation instructions.
The OpenKirin ROMs don't work with TWRP. Moreover, TWRP is risky -- it is much easier to recover a phone using the stock EMUI recovery than with TWRP. It is probably better to eliminate TWRP (which will not eliminate your rooting) by flashing the stock ramdisk), then use Magisk if you want to take advantage of root for installation of unapproved apps. I'm not an expert -- this is what I get from reading threads. Now that I'm running OpenKirin (Carbon), I haven't bothered to install Magisk again as I don't need it, but I appreciate that there are things you can do with it.
prestonmcafee said:
The OpenKirin ROMs don't work with TWRP. Moreover, TWRP is risky -- it is much easier to recover a phone using the stock EMUI recovery than with TWRP. It is probably better to eliminate TWRP (which will not eliminate your rooting) by flashing the stock ramdisk), then use Magisk if you want to take advantage of root for installation of unapproved apps. I'm not an expert -- this is what I get from reading threads. Now that I'm running OpenKirin (Carbon), I haven't bothered to install Magisk again as I don't need it, but I appreciate that there are things you can do with it.
Click to expand...
Click to collapse
Last night I installed Oreo from a custom nougat rom. My wifi tether was working before now it isn't so I'll have to figure that out and maybe re root etc.. Is OpenKirin Oreo?
Yes, OpenKirin is Oreo 8.1.0, with security patches in Carbon 3.1 of July 2018. (The OpenKirin site currently has Carbon 2, which has the June patch, but you can get 3.1 from the telegram support group, which is what I'm running. It will show up on the OpenKirin site sooner or later.)
Can I go from stock 8.0 to OpenKirin? Since it doesn't use twrp I'll have to read how to do it.
Edit: Where do I find OpenKirin Carbon? I didn't see it in the rom section here.
jeffrimerman said:
Can I go from stock 8.0 to OpenKirin? Since it doesn't use twrp I'll have to read how to do it.
Edit: Where do I find OpenKirin Carbon? I didn't see it in the rom section here.
Click to expand...
Click to collapse
https://openkirin.net/download/
There are instructions at the site as well as downloads. The current version of Carbon, 3.1, can currently only be reached by going to the telegram group, but I found no bugs in v2.
They made a wiki on Beryllium (https://wiki.lineageos.org/devices/beryllium) and some other links to the official build (https://download.lineageos.org/beryllium) but they removed it.
I don't know what was the reason.
They rolling out the Lineage 16 PIE on couple devices like Oneplus 5/5T, Huawei P20 Pro, Xiaomi Mi Note 3, etc. (https://www.androidpolice.com/2019/...1-oneplus-phones-galaxy-s5-and-other-devices/)
wasn't released it failed but it is expected to succeed soon.
bower1994 said:
wasn't released it failed but it is expected to succeed soon.
Click to expand...
Click to collapse
Thank you for the response, out of curiosity, what was failed in the latest official build?
https://gitlab.com/LineageOS/builder/android/pipelines/49950700/builds
Yesterday all builds failed on that user/server
#### build completed successfully (01:34:25 (hh:mm:ss)) #### Guess we can expect a build in a few hours?
The nightly is available now
The inital nightly build seems to be broken, at least for me. Can't boot into system.
Same here, installed via adb sideload. system displays the boot animation for a while, then I end up in recovery every time.
tiantnait said:
Same here, installed via adb sideload. system displays the boot animation for a while, then I end up in recovery every time.
Click to expand...
Click to collapse
I tried again, this time flashing the 9.2.25 vendor firmware instead of 9.3.1, LOS flash also via sideload. It's working now!
no problems here.. clean flash, flashed firmware 9.2.25, los official nightly, pico gapps and magisk 18.2, wipe cache/dalvik and reboot. it runs awesome
Strel0ka said:
I tried again, this time flashing the 9.2.25 vendor firmware instead of 9.3.1, LOS flash also via sideload. It's working now!
Click to expand...
Click to collapse
No luck here. I also tried flashing 9.2.25 first (had 9.2.21 before). Still same boot loop. Must be something else.
(magisk, no google services, encrypted fs, not a clean install [update from UNOFFICAL 20190220])
going back to UNOFFICAL build works fine for now...
tiantnait said:
No luck here. I also tried flashing 9.2.25 first (had 9.2.21 before). Still same boot loop. Must be something else.
(magisk, no google services, encrypted fs, not a clean install [update from UNOFFICAL 20190220])
going back to UNOFFICAL build works fine for now...
Click to expand...
Click to collapse
So you performed a dirty flash of official LOS over unofficial LOS? That's like dirty flashing NOS over LOS. If you want to switch over to the official branch, I highly recommend starting from scratch.
My current setup is official LOS with microg + magisk and Encryption, no issues so far.
Yep.. Official build is on!
Recently I decided to play around with my retired xiaomi 4c which I bought in 2016/2017.
Firstly, I unlocked my phone and installed TWRP recovery. (the version I installed is twrp-3.1.1-0-libra), the link I used is here: https://dl.twrp.me/libra, the reason why I did not install version 3.1.1-1 is that It won't load in recovery mode.
Secondly, I tried to install lineage 14.1, 15.1,16.1, 17.1 (none of them worked), It gave me this error
E3004 the packge is for device 4c,libra, this device is .
After searching on google, I deleted the first line (the assert statement) in META-INF\com\google\android\updater-script.
I guess it managed to be installed (no error pop out).
the log displayed while it is installing:
detected filesystem ext4 for /dev/block/bootdevice/by-name/system
packing system image unconditionally
However, when I click boot to system, it stuck on the mi logo.
I need some suggestions on how to make this work.
Thanks in advance!
Flash the latest available official miui (currently V10.1.1.0), via mi flash tools
Flash twrp or orangefox, via ADB. twrp official site has an old version, androidfilehost has a newer version TWRP-20190528-3.3.1.0-libra. orangefox official site has taken down libra files but sourceforge has OrangeFox -R10.0-1-Stable-libra.
Then try again
I experienced "this device is ." problem before.
From I read somewhere in XDA, sometimes a ROM may require certain recovery images to flash. So if the image is published with some recovery, you may want to try them together.
The last time I flashed my mi4c successfully, the LineageOS build and TWRP are both from this post: https://forum.xda-developers.com/t/rom-android-8-9-10-unofficial-lineageos-for-mi-4c-mi-4s.4008625/ .
Good luck
Gourcuff14 said:
Flash the latest available official miui (currently V10.1.1.0), via mi flash tools
Flash twrp or orangefox, via ADB. twrp official site has an old version, androidfilehost has a newer version TWRP-20190528-3.3.1.0-libra. orangefox official site has taken down libra files but sourceforge has OrangeFox -R10.0-1-Stable-libra.
Then try again
Click to expand...
Click to collapse
Thank you! I finally managed to install lineage 14.1, but not 15.1, 16.1 or 17.1, weird
momocraft said:
I experienced "this device is ." problem before.
From I read somewhere in XDA, sometimes a ROM may require certain recovery images to flash. So if the image is published with some recovery, you may want to try them together.
The last time I flashed my mi4c successfully, the LineageOS build and TWRP are both from this post: https://forum.xda-developers.com/t/rom-android-8-9-10-unofficial-lineageos-for-mi-4c-mi-4s.4008625/ .
Good luck
Click to expand...
Click to collapse
Thank you, I finally managed to install lineage 14.1, but not 15.1, 16.1 or 17.1, weird.
Haha but now I failed to bypass the ssl pinning through sslunpinning and frida ><, frida says Bad access due to invalid address
Any idea how to fix this?
Try the boot image included in this build package and post your findings in that thread for assistance.
[ROM][8.1/9/10/11][Unofficial][EOL] LineageOS for Mi-4c/Mi-4s
DESCRIPTION Unofficial LineageOS ROMs for Mi-4c (libra) and Mi-4s (aqua), with base-layer enhancements and performance optimizations. Version 15.1/16.0/17.1/18.1 are available for download. FEATURE The following items may not be available for...
forum.xda-developers.com
you need orangefox for mi4c
yanzifan021 said:
Thank you! I finally managed to install lineage 14.1, but not 15.1, 16.1 or 17.1, weird
Click to expand...
Click to collapse
Hi friend, could you share the download link 14.1, thanks
timsg said:
Hi friend, could you share the download link 14.1, thanks
Click to expand...
Click to collapse
Here there are some builds https://androidfilehost.com/?w=search&s=libra&type=files&page=19
hi;
well i tried 19 again didn't back up gapps version and tried 11/arm/pico versions i get error 20 when sideloading gapps and even when using twrp 3 and using install.
any help would be great this error happens in win 11 and linux with latestr adb and fast boot installed.
Try installing it via the latest twrp from the official website:
Download TWRP for lux
Download TWRP Open Recovery for lux
eu.dl.twrp.me
If that doesn't work, try installing it with the oldest twrp available from here:
[TWRP][lux] TWRP for Moto X Play
This is my version of TWRP built for the 2015 Moto X Play. It should work fine, but using it is a try at your own risk procedure. Your bootloader must be unlocked to use this recovery. Fastboot mode is used to flash or boot this recovery. To...
forum.xda-developers.com
Also, maybe try some other gapps package, it's possible that opengapps isnt compatible with that lineage version. See if any gapps are recommended on the lineage forum page and use that. Some good alternatives are NikGapps and LiteGapps.
Make sure to try different roms as well, prefferably stable ones such as lineage 17.1 from here:
[ROM][EOL][OFFICIAL] LineageOS 17.1 weeklies [lux]
LineageOS is a free, community built, aftermarket firmware distribution of Android 10 (Q), which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project...
forum.xda-developers.com
Try lineage 17.1 again from the above link, but make sure to follow the instructions and read the page carefully, it says that you need a nougat base, and if you are coming from nougat stock, then you need to wipe /data.
PhotonIce said:
Try installing it via the latest twrp from the official website:
Download TWRP for lux
Download TWRP Open Recovery for lux
eu.dl.twrp.me
If that doesn't work, try installing it with the oldest twrp available from here:
[TWRP][lux] TWRP for Moto X Play
This is my version of TWRP built for the 2015 Moto X Play. It should work fine, but using it is a try at your own risk procedure. Your bootloader must be unlocked to use this recovery. Fastboot mode is used to flash or boot this recovery. To...
forum.xda-developers.com
Also, maybe try some other gapps package, it's possible that opengapps isnt compatible with that lineage version. See if any gapps are recommended on the lineage forum page and use that. Some good alternatives are NikGapps and LiteGapps.
Make sure to try different roms as well, prefferably stable ones such as lineage 17.1 from here:
[ROM][EOL][OFFICIAL] LineageOS 17.1 weeklies [lux]
LineageOS is a free, community built, aftermarket firmware distribution of Android 10 (Q), which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project...
forum.xda-developers.com
Try lineage 17.1 again from the above link, but make sure to follow the instructions and read the page carefully, it says that you need a nougat base, and if you are coming from nougat stock, then you need to wipe /data.
Click to expand...
Click to collapse
that is the version i re flashed after trying 19 again . ty and will look
still no luck yet still trying stuff.
hi;
close this thread plz as i went to E/os on my xplay while built on lineageos working well and now my daily driver.
gmail access,playstore etc . i'm happy.
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 - please make backup. Better to store all partitions.
What works
audio
bluetooth
brightness
call/LTE (mondrianlte)
camera
DRM
OTA
video
wifi
wifi display
What doesn't work
Back camera preview : wrong rotation on preview in default app Fixed build 20221204
SELinux Fixed build 20221130
Instructions:
0. Patched TWRP for FOTA : mondrianwifi / mondrianlte
1. Factory reset if coming from another ROM.
2. Install ROM
3. Install GApps (optionally) [Recommended BiTGApps ARM 13]
4. Install Magisk 25.2 (optionally)
Sources & Changes:
Device tree mondrianwifi
Device tree mondrianlte
Kernel tree
Vendor tree mondrianwifi
Vendor tree mondrianlte
TWRP tree mondrianwifi
TWRP tree mondrianlte
Download:
Downloads: mondrianwifi / mondrianlte
Note to users: I'm not responsible if you brick your tablet. See the disclaimer above.
Contributors
LineageOS team for source code.
@retiredtab for helping make mondrianwifi to work on Android12
@khalvat for its work on porting msm8974 to Android12 (https://github.com/LineageOS-UL)
@pocketrule, @bierma32, @Yxo 6o6uka for willing to test WIFI builds and leaving feedback
@bmwdroid for willing to test LTE builds and leaving feedback
ROM OS Version: 13.0
Version Information
Status: Nightlies
Created 2022-11-27
Last Updated 2023-01-05
THX @phoval for the New LOS 20 Version.
Installed this as update over the Version 20221010 without issue's.
FOTA update notification works .
New build: SeLinux is enforcing
Perfect !!!
Amazing !!
Thank you @phoval !!!
Hello, good job.
Thank you @phoval
Installed and runs smooth. Sound, video & wifi works. Excelled work.
Amazing, the previous versions made my tablet very slow, but this one seems to run well. Great job! Thanks to the developers
@phoval since I've installed the zram_ boot.IMG runs the ROM with out lags and crash's.
Thanks again for your work.
I will update today to the last Version 20221204
cwokel said:
Amazing, the previous versions made my tablet very slow, but this one seems to run well. Great job! Thanks to the developers
Click to expand...
Click to collapse
bierma32 said:
@phoval since I've installed the zram_ boot.IMG runs the ROM with out lags and crash's.
Thanks again for your work.
I will update today to the last Version 20221204
Click to expand...
Click to collapse
my tabelt is still slow, even with this built. i did a factory reset. even my battery is draining extremely.
@bierma32 what is zram_ boot.IMG. can you provide me that file? can i flash it in twrp?
greetz
@chkdsk90
Charge your battery to 100% and try another clean install, format also system and data .
chkdsk90 said:
my tabelt is still slow, even with this built. i did a factory reset. even my battery is draining extremely.
@bierma32 what is zram_ boot.IMG. can you provide me that file? can i flash it in twrp?
greetz
Click to expand...
Click to collapse
Provide logcat.
zram boot img was alpha kernel for test.
The changes are includes since 2nd december build.
how can i flash the patched TWRP? Odin doesn't recognize the twrp file because its a .img file and not .tar
chkdsk90 said:
how can i flash the patched TWRP? Odin doesn't recognize the twrp file because its a .img file and not .tar
Click to expand...
Click to collapse
You can download an official tar file, flash it in odin, reboot to recovery and from there you can update twrp.
pocketrule said:
You can download an official tar file, flash it in odin, reboot to recovery and from there you can update twrp.
Click to expand...
Click to collapse
And why is the link to a patched twrp? What exactly is patched? What is fota?
Sorry for the questions. I only know the Normal twrp. tar file
chkdsk90 said:
And why is the link to a patched twrp? What exactly is patched? What is fota?
Sorry for the questions. I only know the Normal twrp. tar file
Click to expand...
Click to collapse
It's patched for FOTA. A simple internet search reveals, that fota stands for "Firmware Over-the-Air" 😉️ I.e. you can download and update the rom directly from the rom itself. If you (always) download and flash the rom manually / separately, you don't need the patched rom.
One detail: the taskbar at the bottom does not disappear when I open an app, neither the three virtual bottons. Tried all configuration without result. Any hints?
If I get a app not responding message and I hit wait it will repeatedly pop up despite the app responding again (dirty flash). Otherwise first impressions of this rom are good.
Just asking, any plans or chances for mondrianlte to get an A13 build? I've got that device running an unofficial LOS A11 build (the latest OS available for it), and it still has official TWRP support as of today
cwokel said:
One detail: the taskbar at the bottom does not disappear when I open an app, neither the three virtual bottons. Tried all configuration without result. Any hints?
Click to expand...
Click to collapse
Just disable it in system > buttons. It's customization during first setup.
You can enable gesture navigation too.
jacomail95 said:
Just asking, any plans or chances for mondrianlte to get an A13 build? I've got that device running an unofficial LOS A11 build (the latest OS available for it), and it still has official TWRP support as of today
Click to expand...
Click to collapse
If someone can find me one to buy?