Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
What's the catch, we have Official LOS builds?:
These are home baked builds of LineageOS with full Substratum support. It supports the rootless operations of Substratum as well as all of its features. It will be Pure LineageOS and as such, bug reporting won't work for this one.
All the bugs that you face will either be of LineageOS or if any themeing one than it would be from Substratum. [Well there aren't any as of now]. Builds will be either weekly or daily or as new changes merge in OR depending upon my upload to the server was successful or not.
Frequently Asked Questions
1.1 Q: Can I dirty flash over from official LineageOS?
1.1 A: No, a clean flash is required as their builds are signed with private keys.
1.2 Q: Can you merge ABC feature from XYZ ROM?
1.2 A: No. This is stock Lineage with full OMS support, that is it.
1.3 Q: I have LMN bug, please fix!
1.3 A: Wait till either the Lineage Team or the Substratum team fixes it. Till then live your life dangerously....
1.4 Q: How do I see what is new every release?
1.4 A: https://www.cmxlog.com/14.1/shieldtablet/
1.4 B: https://github.com/LineageOMS
1.5 Q: What root should I flash?
1.5 A: It's up to you, as root is only required for boot animations. There are four options:
SuperSU
Magisk
phh's SuperUser
Lineage's SU
Downloads:
ROM: LineageOS on the G Drive
GAPPS: use OpenGapps or any of your preferred choice, 7.1 ARM; pico preferred.
ROOT: see above
Instructions :
Download the latest build and gapps
Reboot to recovery
Flash the latest build and gapps
Reboot. Profit.
Credits:
The Official LineageOS Team
The Substratum Repo Guys
TheMuppet Guys
Many Thanks to:
Steel01: For helping me figure out how to merge.
BitOBSessiOn: The guy who is always ready to help irrespective of time and number of questions.
XDA:DevDB Information
Lineage OS 14.1 with full OMS, ROM for the Nvidia Shield Tablet
Contributors
Mohammad Siddique
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: Lineage OS
Version Information
Status: Nightly
Created 2017-07-13
Last Updated 2017-07-13
Hi, recently purchased an already rooted shield tablet
running 7.0
software 5.0
TWRP 3.1.0
I would like to flash without PC (looks fine) is that doable?
I am also unsure if I need to flash a root method after flashing rom and gapps since I am already rooted?
What about any root ad-ons like referenced in the official version?
thanks in advance (thank you button will be hit!)
jlipps75 said:
Hi, recently purchased an already rooted shield tablet
running 7.0
software 5.0
TWRP 3.1.0
I would like to flash without PC (looks fine) is that doable?
I am also unsure if I need to flash a root method after flashing rom and gapps since I am already rooted?
What about any root ad-ons like referenced in the official version?
thanks in advance (thank you button will be hit!)
Click to expand...
Click to collapse
Since you already have TWRP, you can go ahead and flash any rom of your choice, no PC required of course, just download it in your device, and flash via TWRP, for root as mentioned you can flash any zip of your choice to achieve the root, and what root add-ons are you referring to ?
lineage-14.1-20170715-UNOFFICIAL-shieldtablet uploaded to the G Drive with latest OMS patches
Mohammad Siddique said:
Since you already have TWRP, you can go ahead and flash any rom of your choice, no PC required of course, just download it in your device, and flash via TWRP, for root as mentioned you can flash any zip of your choice to achieve the root, and what root add-ons are you referring to ?
Click to expand...
Click to collapse
So do I need to flash a root zip to re-gain root after flashing this rom? I am already rooted so I am confused about this process. And the root add-ons seem to be useful and/or necessary with LOS official roms, there is a download link to add-on zip on page one of Steel01 official LOS thread.
jlipps75 said:
So do I need to flash a root zip to re-gain root after flashing this rom? I am already rooted so I am confused about this process. And the root add-ons seem to be useful and/or necessary with LOS official roms, there is a download link to add-on zip on page one of Steel01 official LOS thread.
Click to expand...
Click to collapse
Yes, to regain root you'll need to flash, and that root addon from LOS page will enable the inbuilt root access which can be found in development settings. If using that then no other is required to flash
Hey man, how would you go about building and merging OMS-7 for your ROM? I've been building myself a nice build of LineageOS for my OnePlus 5 with some extra mods but I haven't found out (properly) how to implement OMS yet.
Any help would be appreciated, thanks.
Interceptor777 said:
Hey man, how would you go about building and merging OMS-7 for your ROM? I've been building myself a nice build of LineageOS for my OnePlus 5 with some extra mods but I haven't found out (properly) how to implement OMS yet.
Any help would be appreciated, thanks.
Click to expand...
Click to collapse
https://github.com/LineageOMS either merge or download,
if you scroll down and see there will be merge script, or the easiest
https://forum.xda-developers.com/apps/substratum/reference-lineageos-substratum-support-t3580276
follow this step, I successfully did that using the third step EasyPeasy
And Good Luck with your build )
Hi!
When I try flashing, it tells me that it needs bootloader version 4.0.0 ... but the only bootloader I can download on from webgeek1234 either give me bootloader version 3.1.1 or 4.0.1 ... so installation fails. Installing LineageOS 13.0 doesn't complain about bootloader...
Am I missing something?
ggravier said:
When I try flashing, it tells me that it needs bootloader version 4.0.0 ... but the only bootloader I can download on from webgeek1234 either give me bootloader version 3.1.1 or 4.0.1 ...
Click to expand...
Click to collapse
Bootloader version doesn't match the stock rom version number. The bootloader it wants is the N or stock 5.0 one. I should probably make that more clear in my post...
Steel01 said:
Bootloader version doesn't match the stock rom version number. The bootloader it wants is the N or stock 5.0 one. I should probably make that more clear in my post...
Click to expand...
Click to collapse
Hi!
OK. So... how can I get, and how do I install the N bootloader on my SHIELD? I didn't see it documented.
Thanks!
It's linked in the opening post to my Lineage thread.
Steel01 said:
It's linked in the opening post to my Lineage thread.
Click to expand...
Click to collapse
Hi!
Here? On th is thread? The only thing I see is :
ROM: LineageOS on the G Drive
GAPPS: use OpenGapps or any of your preferred choice, 7.1 ARM; pico preferred.
ROOT: see above
But nothing about bootloader. Another thread maybe?
Gilles.
ggravier said:
Hi!
Here? On th is thread? The only thing I see is :
ROM: LineageOS on the G Drive
GAPPS: use OpenGapps or any of your preferred choice, 7.1 ARM; pico preferred.
ROOT: see above
But nothing about bootloader. Another thread maybe?
Gilles.
Click to expand...
Click to collapse
https://forum.xda-developers.com/shield-tablet/development/rom-lineageos-shield-tablet-t3562839
He clearly mentioned his thread, here it is:
in the downloads section Firmware
doing a stock update to come to Nougat is safe. DL the file and flash via recovery then do a reboot recovery and then retry flashing.
Mohammad Siddique said:
https://forum.xda-developers.com/shield-tablet/development/rom-lineageos-shield-tablet-t3562839
He clearly mentioned his thread, here it is:
in the downloads section Firmware
doing a stock update to come to Nougat is safe. DL the file and flash via recovery then do a reboot recovery and then retry flashing.
Click to expand...
Click to collapse
So I posted on his thread... it doesn't work on my device.
ggravier said:
So I posted on his thread... it doesn't work on my device.
Click to expand...
Click to collapse
You tried flashing the zip? or just extract the blob file from the zip and fastboot flash it, profit.
Mohammad Siddique said:
You tried flashing the zip? or just extract the blob file from the zip and fastboot flash it, profit.
Click to expand...
Click to collapse
I did same procedure as for versions 311 and 420 from webgeek1234 : put the zip on the SD. Boot to TWRP. Use the "install" function to install the ZIP. It works for 311 and 420... but when I do it with version 50... the output of the installation just says "succeded" and after, when trying to install Lineage, it says version unknown.
ggravier said:
I did same procedure as for versions 311 and 420 from webgeek1234 : put the zip on the SD. Boot to TWRP. Use the "install" function to install the ZIP. It works for 311 and 420... but when I do it with version 50... the output of the installation just says "succeded" and after, when trying to install Lineage, it says version unknown.
Click to expand...
Click to collapse
That's why I'll recommend you to go on stock, update to whatever latest version stock is on, then re trying the above process, let us know your results...
Mohammad Siddique said:
That's why I'll recommend you to go on stock, update to whatever latest version stock is on, then re trying the above process, let us know your results...
Click to expand...
Click to collapse
Unfortunately, I can't go on stock. The device is a device that was recalled for the battery issue (but this one's batter never even blinks towards a thermometer when even operating at full speed). So when I got the new device, I had to flash it with a non stock OS.
So I'm running one of the latest builds of Cyanogen before they went ballistic.
And if I go to stock, the machine will be bricked.
ggravier said:
Unfortunately, I can't go on stock. The device is a device that was recalled for the battery issue (but this one's batter never even blinks towards a thermometer when even operating at full speed). So when I got the new device, I had to flash it with a non stock OS.
So I'm running one of the latest builds of Cyanogen before they went ballistic.
And if I go to stock, the machine will be bricked.
Click to expand...
Click to collapse
From the zip you have download extract the blob file, reboot your tablet to bootloader/ fastboot
and run this command
Code:
fastboot flash staging blob
this will update your bootloader to the latest N bootloader by Nvidia and hence the error will also be gone.
I didin't know about Commotio until I accidently came across it while searching for the latest Vanir ROM. For what I know, Commotio and Vanir share the same device tree and are much similar. Commotio however releases new functionality in it's ROM's that eventualy might endup in a Vanir ROM. (Anyone, correct me if I'm wrong).
So I got curious and tested Commotio's last build, B140 08202017 for the hiaeuhl. I must say, this is an excellent ROM if your bored with LinageOS. Stable, fast and comes with full OMS support for substratum. During the installation (flash by twrp) it installs the latest stable magisk version by default. I found out that the latest superSU+suhide is much more stable. So I removed magisk and rooted Commotio with SuperSU+suhide, SafetyNet doesn't stand a chance.
Links:
Commotio ROM's for the hiaeuhl here
Magisk removal tool (flashable zip) here
Latest SuperSU by Chainfire (flashable zip) here
Suhide 1.08 by Chainfire (flashable zip) here
Aroma SuperSUconfig 1.00 (flashable zip) here
OpenGApps here
Installation:
1. Clear data and dalvik/cache
2. Flash ROM
3. Flash GApps
4. Remove Magisk or keep it as it is and enjoy your ROM (remove Magisk Manager manually once booted into OS)
5. Flash SuperSUconfig. Choose to disable forced data encryption and install in systemless SBIN mode (important!)
6. Flash latest SuperSU
7. Flash latest suhide
8. Reboot
I want to remind you guys, you have to be on MM firmware with the latest TWRP recovery installed to get this to work.
Enjoy
Some screenshots can be found here
And oh, don't bother me with old threads about Commotio just to point out you remember what you've read two years ago. I'm just trying to keep the forum alive and maybe trigger custom developers to provide us with more ROM's.
My Device Us Unlocked. S-off Rooted. Firmware 2.18.617.30 Nougat 7.0 . How Can I install that Rom ?
Hi
Hi guys i need a help can someone take the nogut version twrp backup for htc one a9 or please make the sense based nogut rom plz.plz
Nuroxy said:
My Device Us Unlocked. S-off Rooted. Firmware 2.18.617.30 Nougat 7.0 . How Can I install that Rom ?
Click to expand...
Click to collapse
first you have to downgrade your firmware to 1.5x or wait for developers to publish a ROM capable of working with 2.X firmware. I have feeling this is gonna take some time. Once set to the right firmware, flash the ROM as you usually do.
eavandijk83 said:
I didin't know about Commotio until I accidently came across it while searching for the latest Vanir ROM. For what I know, Commotio and Vanir share the same device tree and are much similar. Commotio however releases new functionality in it's ROM's that eventualy might endup in a Vanir ROM. (Anyone, correct me if I'm wrong).
So I got curious and tested Commotio's last build, B140 08202017 for the hiaeuhl. I must say, this is an excellent ROM if your bored with LinageOS. Stable, fast and comes with full OMS support for substratum. During the installation (flash by twrp) it installs the latest stable magisk version by default. I found out that the latest superSU+suhide is much more stable. So I removed magisk and rooted Commotio with SuperSU+suhide, SafetyNet doesn't stand a chance.
Links:
Commotio ROM's for the hiaeuhl here
Magisk removal tool (flashable zip) here
Latest SuperSU by Chainfire (flashable zip) here
Suhide 1.08 by Chainfire (flashable zip) here
Aroma SuperSUconfig 1.00 (flashable zip) here
OpenGApps here
Installation:
1. Clear data and dalvik/cache
2. Flash ROM
3. Flash GApps
4. Remove Magisk or keep it as it is and enjoy your ROM (remove Magisk Manager manually once booted into OS)
5. Flash SuperSUconfig. Choose to disable forced data encryption and install in systemless SBIN mode (important!)
6. Flash latest SuperSU
7. Flash latest suhide
8. Reboot
I want to remind you guys, you have to be on MM firmware with the latest TWRP recovery installed to get this to work.
Enjoy
Click to expand...
Click to collapse
How about the camera working on Commotio ??????in lineage os camera is not working properly.and most of 3rd party camera app not working....
Camera is working fine
Tried latest build on 1.56.401 firmware Encryption unsuccesfull error all the time.
Someone know if in this rom with old firmware the hotspot working?
Hey I'm on the new firmware and I've been trying to follow your instructions here and am failing. I am able to follow you till flashing the magisk uninstaller. Then when I use the aroma installer to config su on the first page i select systemless bin mode(explicitly states for >=8.0) then i disable force encryption and click on next and complete config but when i flash the superuserSU.zip it installs the binary files in the /data/ directory and then the suhide fails to install. am I doing something wrong.?
Namaless said:
Someone know if in this rom with old firmware the hotspot working?
Click to expand...
Click to collapse
newest version woking fine .best rom ever :good:
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.
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.
Tired of miui, always been a stock android user till now. Needs guidance on installing PE+ since the twrp now supports encryption. Some people says that twrp gets replaced by stock recovery if i dont flash magisk and root it. Since the safetynet support comes prebuilt in PE+, i dont feel like rooting as what im searching for is a fluent stock android experience. Can i flash PE+ as soon as i flash twrp? Is there any recomended firmware need to be added before the rom file? Miui in my device is currently on 13.0.3. should i flash the same firmware again before adding the PE+ rom?
NanduForRom said:
Tired of miui, always been a stock android user till now. Needs guidance on installing PE+ since the twrp now supports encryption. Some people says that twrp gets replaced by stock recovery if i dont flash magisk and root it. Since the safetynet support comes prebuilt in PE+, i dont feel like rooting as what im searching for is a fluent stock android experience. Can i flash PE+ as soon as i flash twrp? Is there any recomended firmware need to be added before the rom file? Miui in my device is currently on 13.0.3. should i flash the same firmware again before adding the PE+ rom?
Click to expand...
Click to collapse
Whether the Twrp decrypts or not is irrelevant since for the first installation you will have to format the data (TWRP/wipe/format data type yes/reboot TWRP).
For the firmware use the one that corresponds with the date of the rom or more recent (global if not specify another).
Pixel experience provides a recovery:https://wiki.pixelexperience.org/devices/vayu/install/
Firmware:https://xiaomifirmwareupdater.com/firmware/vayu/
TWRP only one for A12:https://androidfilehost.com/?w=files&flid=322455
Rom:https://download.pixelexperience.org/vayu
If the requested firmware is not available, flash the recovery rom:https://xiaomifirmwareupdater.com/miui/vayu/
NOSS8 said:
Whether the Twrp decrypts or not is irrelevant since for the first installation you will have to format the data (TWRP/wipe/format data type yes/reboot TWRP).
For the firmware use the one that corresponds with the date of the rom or more recent (global if not specify another).
Pixel experience provides a recovery:https://wiki.pixelexperience.org/devices/vayu/install/
Firmware:https://xiaomifirmwareupdater.com/firmware/vayu/
TWRP only one for A12:https://androidfilehost.com/?w=files&flid=322455
Rom:https://download.pixelexperience.org/vayu
If the requested firmware is not available, flash the recovery rom:https://xiaomifirmwareupdater.com/miui/vayu/
Click to expand...
Click to collapse
So should i flash the latest firmware thats available for my device that is 13.0.3 for miui? Should the PE+ work efficiently with that firmware. What do you mean by the requested firmware not available? Can you elaborate on that specifically? Requested by PE+ you mean?
NanduForRom said:
So should i flash the latest firmware thats available for my device that is 13.0.3 for miui? Should the PE+ work efficiently with that firmware. What do you mean by the requested firmware not available? Can you elaborate on that specifically? Requested by PE+ you mean?
Click to expand...
Click to collapse
Nope,since you already have it.Global not EEA
I haven't seen any instructions for the firmware so it's assumed it's the latest.
Older firmware will not work, newer ones will.
For some AOSP the OP asks to flash a Chinese firmware for example.
Either way if it's not the right firmware the rom won't boot or work properly.
Ask on the thread of the rom you want to install.
As suggested by @NOSS8, Get the latest TWRP/OrangeFox (based on TWRP, a beautiful recovery) but be advised A12 encryption/decryption is still in beta (but is pretty stable IMO). Usually one flashes the latest Chinese firmware, no harm in flashing it even if you are switching over from MIUI.