Related
I'm currently on a custom 5.1 ROM with the new bootloader and radio. I read about issues when flashing the CM12 ROM with this setup. Is this still a problem? Do I have to go back to the 5.0 stock android (with full wipe) before flashing CM12?
Would like to know something similar of the sort, also have the 5.1 boot loader and radio and am on resurrection remix 5.1. Would like to go to CM12 if possible.
Solution found:
http://forum.xda-developers.com/showthread.php?t=2958222
I already installed CM12 after flashing the 5.0 bootloader and radio from the thread without any problems.
daniel.1983 said:
Solution found:
http://forum.xda-developers.com/showthread.php?t=2958222
I already installed CM12 after flashing the 5.0 bootloader and radio from the thread without any problems.
Click to expand...
Click to collapse
So what was the process you wnet through? Flash the 5.1 radio and bootloader, then CM12, then gapps? I thought downgrading the bootloader would result in a hard brick? Also did you flash the latest CM12 nightly?
KentuckyGuy447 said:
So what was the process you wnet through? Flash the 5.1 radio and bootloader, then CM12, then gapps? I thought downgrading the bootloader would result in a hard brick? Also did you flash the latest CM12 nightly?
Click to expand...
Click to collapse
I flashed the zip file from post one with the 5.0 bootloader (https://www.androidfilehost.com/?fid=95916177934545628). Afterwards I flashed the latest CM12 nightly and the Gapps on top. I'm not sure about which action/configuration could brick the device. I have seen much positive feedback in the other thread, so I tried this too.
KentuckyGuy447 said:
I thought downgrading the bootloader would result in a hard brick?
Click to expand...
Click to collapse
Think. Why would Google still make available older factory images, if downgrading (which would include the bootloader) bricked a updated device?
beekay201 said:
Think. Why would Google still make available older factory images, if downgrading (which would include the bootloader) bricked a updated device?
Click to expand...
Click to collapse
It is more of a concern you know. My knowledge is very limited as all this is new to me. I don't have money to throw around for a new device but thanks! I'm taking this as its safe to. Just hard bricking would permenatly destroy a device so don't wanna do that you know...
EDIT: Tested and Confirmed Woking! Big thanks to Daniel!
Has anyone around here flashed OOS 2.1.4 using the recommended method and then flashed a different rom, Im tired of using OOS but i cant seem to find a way to flash CM13 again.
Just flash cm13 in a version of twrp with working firmware flashing. The firmware is included in official cm13 builds.
install TWRP again, and download and flash cm13?
Yes, as long as it's an offical build and you have a version of twrp that supports firmware flashing, like 2.8.6.0 or 3.0.0-1, it will flash everything it needs. If you flash something like sultans bulids flash offical cyanogenmod first then flash the modded build.
Hello!
First of all I'm sorry I'm late to the party ?.
I bought my OPO yesterday and I'm a newbie with all the flashing and so on. It happens to run Oxygen OS 2.1.4 as well and I was wondering if anyone could give me (a link to?) a tutorial to flash a new recovery and everything? I'd really appreciate it.
Thanks in advance
skinnyflirter said:
Hello!
First of all I'm sorry I'm late to the party .
I bought my OPO yesterday and I'm a newbie with all the flashing and so on. It happens to run Oxygen OS 2.1.4 as well and I was wondering if anyone could give me (a link to?) a tutorial to flash a new recovery and everything? I'd really appreciate it.
Thanks in advance
Click to expand...
Click to collapse
https://forums.oneplus.net/threads/...oader-install-custom-recovery-and-root.64487/
After this,you should be considering this one as OOs 2.1.4 is pretty outdated: https://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541#login
lineageos has a good tutorial on flashing
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
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 NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE!!!
YOU HAVE BEEN WARNED!!!
Watch dogs is a ROM I created and it started with the OnePlus 9 Pro back in December. I have decided to bring it to the OnePlus 9, it's based on LineageOS & crDroid source & dependencies and I thank them for its use. SafetyNet and CTS passes whether your rooted or not. Modules not required. Most features are the same as crDroid but I have made some adjustments to bluetooth quality and some fonts that are not available there, plus Gapps are included.
Before you begin, if you don't have the latest platform tools installed on your windows machine. Download it here:
DO NOT FLASH GAPPS!!!! THEY ARE INCLUDED IN BUILD!!!!!
Flashing Instructions
First time installation (clean flash):
This update requires OOS 13.1 - 13.1.0.500(EX01) firmware
Backup your data
Download the ROM, and firmware flasher listed further down on this post and place all in your platform tools folder,
Extract all the contents in platform tools, Firmware flasher in folder.
You must flash firmware in bootloader.
Boot to recovery and factory reset then adb sideload
adb sideload WatchDogs-13.0-20230625-lemonade.zip
Reboot to system
reboot to recovery if you want root
adb sideload magisk.apk or adb sideload magisk.zip
Reboot to system
Update installation:
Updates can be sideloaded with custom recovery. Updates do not appear in system updater.
Sources:
ROM
Kernel
Downloads:
ROM
FIRMWARE FLASHER
Bugs?
Let me know.
Initial builds
WatchDogs-WITHGAPPS-13.0-20230312-lemonade.zip
WatchDogs-NOGAPPS-13.0-20230312-lemonade.zip
If you require Google apps, flash the first one only!
If you do not want Google apps, flash the second one only!
You can't cross dirty flash a update which should be common sense. Example, you can't dirty flash the with gapps build then next update, dirty flash the no gapps one.
I tried CRdroid recovery and the one I was on and both said name mismatch. Got any suggestions for me to try? Thank you for the new development too!
Telegram group please
lorilucille9 said:
I tried CRdroid recovery and the one I was on and both said name mismatch. Got any suggestions for me to try? Thank you for the new development too!
Click to expand...
Click to collapse
That's weird. Did you try sideloading the firmware flasher first before the ROM? If you still have difficulties, I will post the dtbo, boot and vendor_boot files for you to flash to make it compatible. I don't have this phone. I have the OnePlus9 Pro so I can't test it. I'm sure it works or there would be other users saying the same thing.
I flashed the firmware successfully and tried it again but still got the same error. It wouldn't hurt to post the kit files and recovery for others too. If you do then I'll try again before I have to head into work in a couple hours.
UPDATE:
I used the CrDroid boot-20230106 file and then sideloaded fw_Oneplus9_IN_OOS13_F20 on both slots and was able to flash the rom on both slots successfully. Will let you know what I find in time and thanks again for another version rom to pplay with
lorilucille9 said:
I flashed the firmware successfully and tried it again but still got the same error. It wouldn't hurt to post the kit files and recovery for others too. If you do then I'll try again before I have to head into work in a couple hours.
UPDATE:
I used the CrDroid boot-20230106 file and then sideloaded fw_Oneplus9_IN_OOS13_F20 on both slots and was able to flash the rom on both slots successfully. Will let you know what I find in time and thanks again for another version rom to pplay with
Click to expand...
Click to collapse
Good deal, and no problem. Since I use crDroid sources, I figured that should work. I will still post the files necessary to flash recovery when I get a chance. Let me know if there are any bugs or issues with the ROM itself so I can work on it. Thank you!
I installed it on my first try without any problems. but I couldn't understand how it differs from crdroid.
incesu571 said:
I installed it on my first try without any problems. but I couldn't understand how it differs from crdroid.
Click to expand...
Click to collapse
Bootanimation, fonts, bluetooth, sound audio and other tweaks.
TheSayaMan said:
Bootanimation, fonts, bluetooth, sound audio and other tweaks.
Click to expand...
Click to collapse
thx bro
TheSayaMan said:
Bootanimation, fonts, bluetooth, sound audio and other tweaks.
Click to expand...
Click to collapse
Not to mention Gapps included if you choose it so OTAs with no issues... otherwise you'd have to sideload Gapps again after at least for me that's what was happening.
lorilucille9 said:
Not to mention Gapps included if you choose it so OTAs with no issues... otherwise you'd have to sideload Gapps again after at least for me that's what was happening.
Click to expand...
Click to collapse
correct, sorry, forgot to mention that as well. Thank you!! crDroid doesn't offer a with gapps build. You can use the no gapps build to flash your own gapps but I won't support force close issues with the ROM. Example, pixel setup wizard can't be used because it interfers with the default launcher. And yes, on updates, just sideload the with gapps build and your done, unless you want root, then you will have to reboot and sideload magisk because root will be gone on a update.
incesu571 said:
Telegram group please
Click to expand...
Click to collapse
There is one in my 9 pro thread. I will update when I can.
I have op 9 t-mobile version le 2117, can you please guide me which firmware should i use IN, EU or NA?
Sady94 said:
I have op 9 t-mobile version le 2117, can you please guide me which firmware should i use IN, EU or NA?
Click to expand...
Click to collapse
Convert your T-Mobile to EU as listed on another thread, then you can use the EU firmware. I will be posting a update soon with the boot, vendor_boot and dtbo. If you don't want to do that, I will post them later to flash recovery on your phone. Keep in mind that different variants act different, so you may have bugs on T-Mobile, it wasn't tested.
screenshots?
pubmastervnt said:
screenshots?
Click to expand...
Click to collapse
Not by me, maybe someone else who is running it
MARCH UPDATES: 03/24:
WatchDogs-WITHGAPPS-13.0-20230324-lemonade.zip
WatchDogs-NOGAPPS-13.0-20230324-lemonade.zip
Sady94 said:
I have op 9 t-mobile version le 2117, can you please guide me which firmware should i use IN, EU or NA?
Click to expand...
Click to collapse
You can use my custom recovery, files added in OP. You still need latest stock A13.
fastboot flash --slot all boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vendor_boot vendor_boot.img
You cant install this (or any rom but base 11) on tmobile 2117 without BL unlock key. Pretty sure its not possible.
You can only convert to base global 11\OOS11 on 2117 for root, then in ui updater doesnt work OTA or manually. You can get to 13 stock only, because you need to be stock to ota, where you need a key to unlock bootloader again (conversion would bring you back to 11).
*The rooting situation with this phone sucks. I think Jaguar is the only one that will work because it is base 11.