Related
Hey, I'm trying to install TWRP Custom Recovery on my OPO, which is 5.0.2 with stock CM12s.
Now if I recall correctly, the .zip file of my CM11s installation had 'Bacon' on it ( The nickname of 11s version perhaps? ), and the TWRP download is also called 'Bacon', so I just want to make sure this is also supposed to work on my CM12s.
In other words, is the TWRP download link given at their website compatible with my device ( 5.0.2 & Stock CM12s ).
sorry for my dumbness, I'm just not too good with those things.
Lidor167 said:
Hey, I'm trying to install TWRP Custom Recovery on my OPO, which is 5.0.2 with stock CM12s.
Now if I recall correctly, the .zip file of my CM11s installation had 'Bacon' on it ( The nickname of 11s version perhaps? ), and the TWRP download is also called 'Bacon', so I just want to make sure this is also supposed to work on my CM12s.
In other words, is the TWRP download link given at their website compatible with my device ( 5.0.2 & Stock CM12s ).
sorry for my dumbness, I'm just not too good with those things.
Click to expand...
Click to collapse
Bacon is the codename for this device, so yes you have the right one. You need to approach the install a little differently than usually on CM12S though, see the last question in the FAQ thread:
http://forum.xda-developers.com/oneplus-one/help/faq-oneplus-one-frequently-questions-t2895136
Transmitted via Bacon
Hello,
I have a OnePlus One running on CM 13.0
I have MultiRom installed and I have this error showing on the front page of the app - "doesn't have hexec-hardpoot patch!". I tried to install Kernal 6.0.x (my primary ROM is CM 13.0) through the app, but I couldn't. When I try to install the Kernal I get an error during the instillation saying "needs recovery".
I don't really know a lot about this stuff so excuse my ignorance, but how do I install the needed recovery so that I will be able to install the Kernal.
I have TWRP installed in my phone. I swap my primary ROM with a secondary one few days ago. I am not sure if this was caused the issue.
ali282h said:
Hello,
I have a OnePlus One running on CM 13.0
I have MultiRom installed and I have this error showing on the front page of the app - "doesn't have hexec-hardpoot patch!". I tried to install Kernal 6.0.x (my primary ROM is CM 13.0) through the app, but I couldn't. When I try to install the Kernal I get an error during the instillation saying "needs recovery".
I don't really know a lot about this stuff so excuse my ignorance, but how do I install the needed recovery so that I will be able to install the Kernal.
I have TWRP installed in my phone. I swap my primary ROM with a secondary one few days ago. I am not sure if this was caused the issue.
Click to expand...
Click to collapse
Hello ali282h,
I don't know about the needs recovery error during the installation, but if it's saying doesn't have kexec-hardboot patch then you have to find an kernel that fits ur cm-13.0 rom with kexec-hardboot patch included. I assume that when you've switched ur external rom with ur primary that the external rom that you were using didn't had an kexec-hardboot patch included so try another kernel with kexec-hardboot patch included.
Hope this would help you with ur problem:good:
Thank you. I will give it a try.
ali282h said:
Thank you. I will give it a try.
Click to expand...
Click to collapse
if you want you existing primary, i can propose 2 kernels. 1 is Boeffla kernel and the other lightening CM13 kernel.
Instructions in their thread. However, if you plan to use multirom for a while, the latest update has kexec workaround. (multirom settings from TWRP- check multirom page last 2-3 pages). or i would entirely recommend you to keep a kexec patced rom as primary to negate any issues which may arise.
Thank you for the suggestions. I am actually using the 'workaround' feature in TWRP.
I have a question in regard to Boeffla. In the official website.. (http://boeffla.de/index.php/downloads/current-kernel-versions) It says 5.2 next the Oneplus One CM 13.0 Stable. I am confused as to what 5.2 really means. Is this the Android version? CM 13 is based on Android 6.0! I just don't want to flash the wrong one and end up with a boot loop. Do you think the kernel I mentioned is compatible with my phone (OnePlus One - CM 13.0 - Android 6.0.1)
Thank you!
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
For example, I can't install this ROM. https://androidfilehost.com/?fid=529141701856461698
When I install this ROM, the system doesn't boot
But I can install this ROM. https://androidfilehost.com/?fid=95916177934523996
So what's the problem?
dogukans3131 said:
For example, I can't install this ROM. https://androidfilehost.com/?fid=529141701856461698
When I install this ROM, the system doesn't boot
But I can install this ROM. https://androidfilehost.com/?fid=95916177934523996
So what's the problem?
Click to expand...
Click to collapse
which version of twrp are you running?
smart-t78 said:
which version of twrp are you running?
Click to expand...
Click to collapse
I don't use twrp.I'm using PhilZ Touch Recovery 6.59.2
dogukans3131 said:
I don't use twrp.I'm using PhilZ Touch Recovery 6.59.2
Click to expand...
Click to collapse
and thats the cause of your problem. philz touch recovery is out of date and cant handle unified espressowifi builds. if you want to use the latest roms, update to the latest common twrp by android-andi
smart-t78 said:
and thats the cause of your problem. philz touch recovery is out of date and cant handle unified espressowifi builds. if you want to use the latest roms, update to the latest common twrp by android-andi
Click to expand...
Click to collapse
the same problem was repeated for recovery.When I flash this recovery,it doesn't boot https://androidfilehost.com/?fid=673368273298980762
( I flash it using TWRP 3.0.0-0)
But when ı flash TWRP 3.0.0-0 for P5110( https://androidfilehost.com/?fid=24407100847293583 )It works perfectly
dogukans3131 said:
the same problem was repeated for recovery.When I flash this recovery,it doesn't boot https://androidfilehost.com/?fid=673368273298980762
( I flash it using TWRP 3.0.0-0)
But when ı flash TWRP 3.0.0-0 for P5110( https://androidfilehost.com/?fid=24407100847293583 )It works perfectly
Click to expand...
Click to collapse
which rom do you want to install?
when you run a unified common twrp, you cant install older device specific roms. if you run an older device specific twrp, you cant install newer unified roms.
smart-t78 said:
which rom do you want to install?
when you run a unified common twrp, you cant install older device specific roms. if you run an older device specific twrp, you cant install newer unified roms.
Click to expand...
Click to collapse
I want to install newer unified ROMs, but I can't install anything for Unified , I can only install device specific ROM and TWRP
If I install anything for "Unified espresso" (ROM, TWRP, Kernel etc.), the system will not boot, but if I install anything for device specific, the system will boot successfully
dogukans3131 said:
I want to install newer unified ROMs, but I can't install anything for Unified , I can only install device specific ROM and TWRP
If I install anything for "Unified espresso" (ROM, TWRP, Kernel etc.), the system will not boot, but if I install anything for device specific, the system will boot successfully
Click to expand...
Click to collapse
so what was the last installed samsung stock rom? 4.2.2 or 4.0.4?
smart-t78 said:
so what was the last installed samsung stock rom? 4.2.2 or 4.0.4?
Click to expand...
Click to collapse
4.2.2
dogukans3131 said:
4.2.2
Click to expand...
Click to collapse
ok.
next case is there replaced hardware in your tab (e.g mainboard, display)? you need a special kernel then. look here https://forum.xda-developers.com/ga...nified/kernel-anykernel-t3484739/post74352635
smart-t78 said:
ok.
next case is there replaced hardware in your tab (e.g mainboard, display)? you need a special kernel then. look here https://forum.xda-developers.com/ga...nified/kernel-anykernel-t3484739/post74352635
Click to expand...
Click to collapse
No
dogukans3131 said:
No
Click to expand...
Click to collapse
are you sure. maybe its a refurbished tab. try it out. install common twrp + unified rom + special kernel for your device
smart-t78 said:
are you sure. maybe its a refurbished tab. try it out. install common twrp + rom + special kernel for your device
Click to expand...
Click to collapse
Is this the kernel I need to install?
anykernel-2017-11-04-17-13-p5110-only.zip
And is this kernel compatible with Kitkat?(I'm using cm11)
dogukans3131 said:
Is this the kernel I need to install?
anykernel-2017-11-04-17-13-p5110-only.zip
And is this kernel compatible with Kitkat?(I'm using cm11)
Click to expand...
Click to collapse
backup your current system. after that try a marshmallow rom (e.g lineage 13). only to be sure
dogukans3131 said:
Is this the kernel I need to install?
anykernel-2017-11-04-17-13-p5110-only.zip
And is this kernel compatible with Kitkat?(I'm using cm11)
Click to expand...
Click to collapse
no, this kernel isnt compatible with kitkat.
smart-t78 said:
no, this kernel isnt compatible with kitkat.
Click to expand...
Click to collapse
I just downloaded Cyanogenmod 13 (device specific). Does this kernel work with device-specific ROMs? If it works, I'll try to flash the latest Unified TWRP first. If it works, I'll install the Unified ROMs.
The second question is, can I install cm 13 without factory reset(on CM 11)
dogukans3131 said:
I just downloaded Cyanogenmod 13 (device specific). Does this kernel work with device-specific ROMs? If it works, I'll try to flash the latest Unified TWRP first. If it works, I'll install the Unified ROMs.
The second question is, can I install cm 13 without factory reset(on CM 11)
Click to expand...
Click to collapse
1. i think there is no need for the special kernel on device specific roms. keep in mind that device specific builds wont be supported and wont get updates amymore.
2. no, you cant upgrade from cm11 to cm13 without factory reset. clean install is needed
smart-t78 said:
1. i think there is no need for the special kernel on device specific roms. keep in mind that device specific builds wont be supported and wont get updates amymore.
2. no, you cant upgrade from cm11 to cm13 without factory reset. clean install is needed
Click to expand...
Click to collapse
No, I want to install this kernel because I want to install Unified TWRP. If it works, then install Unified ROM
dogukans3131 said:
No, I want to install this kernel because I want to install Unified TWRP. If it works, then install Unified ROM
Click to expand...
Click to collapse
You can install unified twrp (or any other version of twrp) without installing the kernel. The rom and the kernel you have installed are completely independent of the twrp recovery. If you want to install a unified rom with a custom kernel you must first install unified twrp, then clean flash the rom and after that flash the kernel.
john99ap said:
You can install unified twrp (or any other version of twrp) without installing the kernel. The rom and the kernel you have installed are completely independent of the twrp recovery. If you want to install a unified rom with a custom kernel you must first install unified twrp, then clean flash the rom and after that flash the kernel.
Click to expand...
Click to collapse
Unfortunately, I can't enter the recovery mode when I flash Unified TWRP (after the Samsung Galaxy Tab 2 logo, the screen goes black and remains until I restart the system). I can only enter the recovery mode when I flash device specific TWRP
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.