I'm trying to install LineageOS and I am pretty much stuck on one part. I'm on stock currently and do not have two but my device is unlocked. Now my question is if I need to flash twrp that is given in the LineageOS thread and then reboot into recovery and flash the ROM+ GApps or if I need to flash twrp compatible with EMUI5 then flash LineageOS+ GApps and finally flash the twrp that is compatible with LineageOS giving in that thread... Before anyone says that if I'm confused I shouldn't be flashing Roms I'd like to say I have tons of experience doing so but this is troubling me and I just rather ask a question if anyone has an answer to it before I pull the trigger and just do it.
Related
Hello,
Can we update CM Firmware without reinstalling OS?
I have recently install Nitrogen OS with the given firmware. But I have noticed there is a new firmware released with some bug fixes
Can I install the latest firmware without reinstalling the OS??
Jseven123 said:
Hello,
Can we update CM Firmware without reinstalling OS?
I have recently install Nitrogen OS with the given firmware. But I have noticed there is a new firmware released with some bug fixes
Can I install the latest firmware without reinstalling the OS??
Click to expand...
Click to collapse
If you want to switch to a completely different ROM, you will have to do the wipes in recovery then flash the new ROM. If you want to flash an update of the same ROM you have then you don't need the wipes, you can just flash the update without wiping, this is called "dirty flashing". Dirty flash usually only works when flashing an update of the same ROM that you have.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Hello ,
I am talking about the cm14.1 latest firmware and not about the custom room updates. Is it possible to install without any issues
Thanks in advance
Jseven123 said:
Hello ,
I am talking about the cm14.1 latest firmware and not about the custom room updates. Is it possible to install without any issues
Thanks in advance
Click to expand...
Click to collapse
What do you mean the latest CM14.1 update?
NitrogenOS and CM 14.1 ARE BOTH custom ROMs, they are NOT firmwares. Some devices were manufactured and sold with CyanogenMod as the stock firmware but CM is still predominately a custom android operating system.
And, as I said, if the update is an update to the exact same ROM as what is already installed, then all you have to do is flash it without doing any kind of wipes(this can even be done when updating stock via OTA, it's actually recommended to not do the wipes when updating stock via OTA). For example, if you have CM13 and want to update to CM14, or if you have CM14 and want to update to CM14.1 or if you have CM14.1 but want to flash a newer CM14.1 update, understand yet?
BUT!!!!
If you have some other ROM(something other than a version CM) currently installed but want to update to CM instead of what you have then you would have to factory reset, wipe cache and dalvik cache before flashing.
Let's make this simple since you can't seem to make sense of what I'm telling you. Tell me what you currently have installed and what you want to update to.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Hello,
I am currently using Nitrogen OS for Redmi note 3. I have flashed the firmware and installed the OS according to the procedures. I run nougat(7.1.2) on my Mob
Check this link : https://forum.xda-developers.com/redmi-note-3/how-to/cm14-14-1-aosp-n-firmware-kenzo-kate-t3507789
Jseven123 said:
Hello,
I am currently using Nitrogen OS for Redmi note 3. I have flashed the firmware and installed the OS according to the procedures. I run nougat(7.1.2) on my Mob
Check this link : https://forum.xda-developers.com/redmi-note-3/how-to/cm14-14-1-aosp-n-firmware-kenzo-kate-t3507789
Click to expand...
Click to collapse
You have nitrogen OS installed on your android and if you want to install update of nitrogen OS then no need of wiping.
If you want to change to different rom ( nitrogenOS to CM) then you need to first wiping/factory resetting or clearing dalvik and cache.
So, you are changing your rom then wipe/factory reset first and then flash CM. That what @Droidriven trying to say you.
Again you are confused. ROMs like Nitrogen runs on CM firmware ( or you can call it architecture). It's not the OS again, It regarding firmware. please someone help me on this I dont want my phone to get bootlooped or any other sort of issue. FYI : I don't want CM ROM/OS. I want Nitrogen itself but want to upgrade to the latest firmware. Please check the link i had provide before replying
Jseven123 said:
Again you are confused. ROMs like Nitrogen runs on CM firmware ( or you can call it architecture). It's not the OS again, It regarding firmware. please someone help me on this I dont want my phone to get bootlooped or any other sort of issue. FYI : I don't want CM ROM/OS. I want Nitrogen itself but want to upgrade to the latest firmware. Please check the link i had provide before replying
Click to expand...
Click to collapse
This is making sense now. You see, you are the one confused. You aren't asking the right question because you don't understand the difference.
You aren't looking for the "CM firmware", this does not even exist. This implies that the firmware was created by CM. It wasn't made by CM, it does not contain CM in it so it can't be called "CM FIRMWARE", it's a STOCK FIRMWARE that is COMPATIBLE with USING CM and other custom ROMs.
What you are looking for is the "stock firmware" that needs to be on your device BEFORE using CM13/14/14.1/AOSP Nougat ROMs.
The thread that you linked basically explains that if you want to use any kind of custom 7.0/7.1/7.1.1 Nougat ROMS then you need to flash this updated STOCK FIRMWARE in order for the device to be able to use those custom ROMs. It is not "CM FIRMWARE"
You're looking for the STOCK FIRMWARE that is compatible with CM and other nougat ROMs.
The thread that you linked explains what you need to know and how to do it, it says that you flash the updated firmware via TWRP and factory reset, wipe cache and dalvik when you flash it.
If you are looking for a newer update than the one in that thread then you'll have to find it in a TWRP flashable .zip. If there is not a TWRP flashable zip to apply the new update then the only way to flash the new update is to flash it via PC then root the device again, install TWRP again and then flash your NitrogenOS ROM again.
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
thank for the prompt response! so can i flash the latest firmware with the OS installed?
Jseven123 said:
thank for the prompt response! so can i flash the latest firmware with the OS installed?
Click to expand...
Click to collapse
I just explained what you needed to do, did you read it? It is simple, are you even reading the thread that you linked? What you are asking is irrelevant, just do what it says to do in the steps below.
1) Boot to TWRP
2) Flash the updated firmware via TWRP
3) Factory reset, wipe cache and dalvik
4) Flash NitrogenOS
5)reboot, enjoy.
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Some background: I'm coming from an OP3 which did not have this Slot A/B thing and you could easily just flash firmware going forward. I'm currently confused as to how custom roms will update firmware and such going forward.
I noticed there's 'systemless' roms now (like NoLimits), I don't really understand what the advantages/disadvantages vs something like Havoc OS are.
If I go with a custom rom, will I need to flash to OOS to update firmware then reflash back to the custom rom in the future?
I apologize if these are really newb questions, trying to find specific details with some of these keywords makes it really hard to find relevant information (and I've tried).
https://forum.xda-developers.com/oneplus-6/how-to/guide-noobs-guide-to-b-partitions-op6-t3816123
Link above is some info on A/B partitioning.
The benefit of systemless ROMs are that they are just Magisk Modules so installing and uninstalling is very easy. You don't need to boot into recovery or wipe anything.
Havoc is a full ROM and based on AOSP so wiping is needed, especially when security patches are different. Some people are decrypting their phones with the no verity zip but I won't say too much about that to keep things as simple as possible.
You don't need to flash any OOS firmware when on Havoc, and I think it's because custom ROMs have their own vendor image. More advanced users feel free to correct me if I'm wrong about this.
Flashing isn't really too different and I personally don't even think about A/B slots. You just need to remember to flash the TWRP zip file after a ROM flash to keep TWRP. And you also need to reboot back into recovery to install Google apps, rather than just after the ROM flash.
Custom kernels are now flashed last (after TWRP and Magisk).
This is how I've done it and have been issue-free.
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.
I am still trying to fully wrap my head around Android moving to Slot partitions. I am reading as much as I can and feel I have a better understanding of it but have tried to flash lineageOS with microg but ended up with a bricked device maybe due to not doing the proper steps to switch to the active slot? My question is if I have TWRP installed and currently on OOS 11, can I just flash the zip file for lineage OS or so I need to do something additional? The TWRP script states you have to boot into Recovery to switch active slots and flash additional items. I know if I flash lineage I will end up with their Recovery as well which I obviously dont want. Can I flash the TWRP installer after flashing lineageOS zip or no? Please help confirm or deny what needs to be done given my current setup.
Thank you all in advance for any help/experiences you can share about this.
Hi guys,
How do i update the pixel experience rom from android 12 to 13? is it just flash it through recovery and adb sideload, or is there any necessary step i should do before flashing it? like updating the recovery maybe? Im using pixel experience custom recovery and my device is unroot, only bootloader is unlocked
Any answers would be appreciated, thanks!
Maybe ask in an appropriate thread, but you could try dirty flash, stock is flashed the same way.
Odeya said:
Hi guys,
How do i update the pixel experience rom from android 12 to 13? is it just flash it through recovery and adb sideload, or is there any necessary step i should do before flashing it? like updating the recovery maybe? Im using pixel experience custom recovery and my device is unroot, only bootloader is unlocked
Any answers would be appreciated, thanks!
Click to expand...
Click to collapse
Backup all data and dirty flash. If you get errors, clean flash is helpful
Since it's a jump from one Android version to another, it's better to clean flash. Although, a dirty flash should still be possible once you wipe OS.
There should be a new, updated recovery file to flash as well. Tbh, the jump from A12 to 13 is not as big as the previous upgrades, with not much gains.