Hello,
I have a Lenovo K6 Power (K33a42) (Karate). I had installed this Custom ROM on 1st Jan. I liked it till February end but after noticing that it had some problems (not dev's problem, its just mine). I thought of switching to LineageOS 17. It says i require stock nougat firmware. I dont want to go to stock firmware just so that i can go to Lineage. So can i flash it normally? Just wipe system, data, cache, dalvik? (Is system necessary can i flash it without doing that too? Idm if i have to)
Thanks.
DamnBro304 said:
Hello,
I have a Lenovo K6 Power (K33a42) (Karate). I had installed this Custom ROM on 1st Jan. I liked it till February end but after noticing that it had some problems (not dev's problem, its just mine). I thought of switching to LineageOS 17. It says i require stock nougat firmware. I dont want to go to stock firmware just so that i can go to Lineage. So can i flash it normally? Just wipe system, data, cache, dalvik? (Is system necessary can i flash it without doing that too? Idm if i have to)
Thanks.
Click to expand...
Click to collapse
If it says to flash the nougat firmware, there is a reason it says to flash it? If it says that it is required, there is a reason it says that. If upubwant to use the LineageOS ROM then do what it says, flash the nougat firmware then flash LineageOS.
Yes, you can flash LineageOS without wiping system partition but it probably won't work correctly and you'll have to wipe system and flash the ROM again.
Just follow the instructions and do what it says to do. It does not matter that you do not want to.
Hey, thanks for that quick reply. Its not like i dont want to flash stock firmware (sorry if you felt like it in the first post). I cant find my firmware anywhere. I did find it here, its not the latest one but ig its fine? I Dont have enough trust on that website.
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
Hi there, can someone enlighten me how yo flash custom roms?my device already unlocked bootloader and i know how to flash cuz i play with xiaomi mi5, sams galaxy3 , sony x8.
For now i dont have a twrp. Im going twrp by fastboot before this.
Im really sure that i already go through all of the post. But seems from OB10 is really complicated.
1.ready fastboot twrp, bluspark twrp,roms, gapps and magisk( if necessary) and custom kernel
2.fastboot twrp by cmd or else
3.wipe what here? Or just factory reset and leave internal storage?
*Here i confused, do i need to wipe for both slot. Im still new to a/b partition. And do i need to do that for both slot to flash as steps 4-10 as below?
4.flash roms then bluspark twrp
5.reboot to recovery
6.flash gapps,magisk? Then twrp back?
7.reboot to twrp
8.flash custom kernel then twrp again?
9.reboot system
10. End right?
Please help me here. I cant find the real and proper steps. The only way i found is from OB7 to custom roms as they share same security patch.
Thanks for any help.
1. Flash any strock rom.zip partition A.
2. After that recovery.zip
3. Reboot back to recovery
4. Confirm you are in another slot B
5. Flash stock rom.zip. Which slot first is not important.
6. After that flash recovery.zip and then reboot.
After that you can install whatever you want.
That what I do if im switching roms and trying new stuff.
Working everytime.
Until OB7 and stable 9.0.2 I used fasboot roms, flashed via AIO tool, but new fastboot roms working different and I got laggy video and audio.
Okeh thats clear for both slot. But for OB10 to any customs rom is it needed to flash OB7?
What do you mean by stock rom?bete rom or stable rom?
slayerliar said:
Okeh thats clear for both slot. But for OB10 to any customs rom is it needed to flash OB7?
What do you mean by stock rom?bete rom or stable rom?
Click to expand...
Click to collapse
Stock any offical rom for OP6
9.0.2 or 9.0.3 or any OB3,4,5,6,7,8,9,10
If you want custom rom, look instructions, there is mentioned what is base rom. That you need flash.
If there is custom rom based OB7 then you need flash OB7(probably working lower builds also)
Thank brotha. I think they need to state which firmware do we need to start from. Otherwise it will be like me that confusing as they will patch up more and more security.
slayerliar said:
Thank brotha. I think they need to state which firmware do we need to start from. Otherwise it will be like me that confusing as they will patch up more and more security.
Click to expand...
Click to collapse
Pie ROM, pie firmware. (Except pre release betas)
Oreo ROM, Oreo firmware.
ROM - always flash latest firmware of the OS you want pie or Oreo (I always go for latest and don't have any issues . Tho I'm back to oos ,debloated now.)
Twrp - Always after ROMs, before roboot.
Gapps - after twrp and reboot, to make sure it installs to the right slot, that's why you install twrp and then reboot.. this will change your slot from A to B or from B to A. Manual switch is never necessary
Flashing gapps flashes to the slot you are in right now, so flashing before the first reboot (after twrp flash) Will get it to the wrong slot.
Magisk - if you want root. After all.
After all this you can, if you want, flash decrypt ..if you don't need your device to be encrypted,this Will give you more to think of tho.. let's just not go into this now.
i understand the process, but get confused at which file to specifically flash twice when they say
"latest firmware of the OS". So lets say the custom ROM i want to flash needs a PIE firmware 9.0.2 or higher,
what file am i supposed to flash?
9.0.2-PIE-OnePlus6Oxygen_22_OTA_027_all_1810260000_d46787d2c9-FASTBOOT.zip
or
OnePlus6Oxygen_22_OTA_027_all_1810260000_d46787d2c9.zip
Hey OP6 users
i thought of something. that might have been obvious for some people but maybe not for everyone.
when doing a clean flash for a custom ROM it is often needed that we flash a required base. Either OOS stable or a OOS beta version.. which ever is needed by the custom ROM.
we don't need to flash the base again when we're just updating the custom ROM (unless the custom ROM needs a newer version of the base
knowing that, is it still needed to flash the base when changing to a custom ROM that needs the exact same base?
correct me if I'm wrong, but it would save some time for us to not have to flash the same required base for another custom ROM which needs the same one we previously flashed.
it would save: two OOS + TWRP flashes every time and two TWRP reboots, which would be pretty nice?
it would also be nice to save that time if we just wanted to re flash the current ROM I/you/we were using for any reason.
then a clean flash of a current custom ROM in use or changing to another ROM with the requirement of the same base would just be as simple/fast as
Format Data !!!!(optiona)!!!!
Flash Custom ROM + TWRP.zip
Reboot TWRP
Flash Custom ROM + TWRP.zip
Reboot TWRP
Flash GApps.zip + Magisk
Reboot System
In general you don't have to flash the base ROM again to change your custom ROM. Even if one base is 9.0.3 and the other is 9.0.4 it is normally not necessary. The base Rom is foremost used for it's vendor (and other partitions) which are not touched by Custom Roms.
But you have to pay attention to your security patch level before you switch between ROMs.
And of course (strongly recommended) to wipe cache, data and system before switching to another ROM (a complete format is only needed uf you are rolling back to an earlier security patch level)
At least this is my experience and (little) knowledge about how android etc works.
Allthough, If you run into problems, rebasing your phone is always a good option. Helped me out a few times.
How much time do you think you are wasting out of your life when you have to flash a base file (give me seconds and % of HP)? ROFL...?
If I am flashing a new ROM, usually I clean flash, test the ROM... IF I LIKE --> clean flash again, and set it up proper.
Feels good coming fresh out of the box, knowing everything is working optimized.
Anways, with xXx.NoLimits and how smooth OOS is, personally I don't really see any point on flashing custom ROMs anyways anymore.
castrum_doloris said:
In general you don't have to flash the base ROM again to change your custom ROM. Even if one base is 9.0.3 and the other is 9.0.4 it is normally not necessary. The base Rom is foremost used for it's vendor (and other partitions) which are not touched by Custom Roms.
But you have to pay attention to your security patch level before you switch between ROMs.
And of course (strongly recommended) to wipe cache, data and system before switching to another ROM (a complete format is only needed uf you are rolling back to an earlier security patch level)
At least this is my experience and (little) knowledge about how android etc works.
Allthough, If you run into problems, rebasing your phone is always a good option. Helped me out a few times.
Click to expand...
Click to collapse
Aight yeah it thougt so. Ofc I wipe data before flashing a new rom. But thanks for your input/confirmation feels good to have other opinions and experiences then there's also the fact you also have to wait until your rom supports the new base, so u don't flash a new base then switch to your custom Rom and stuff won't work correctly hehe
@castrum_doloris
or anyone else here on the forum
now that our oneplus 6 got an official update i want to ask something. is this okey/safe to do
currently having omnirom installed in both slots and to update base could this work? or will it give problems
1 have custom rom installed with 9.0.4 base
2 flash oxygenos (9.0.5) x2
3 flash custom rom x2
4 reboot twrp
5 flash gapps + magisk
6 reboot system
if i flash oxygenos over omnirom just to update the base and never reboot system to oxygenos will this still give me problems with data? or is it a safe way to update the base ? or is the only way to go to do factory reset?
kewinhw said:
@castrum_doloris
or anyone else here on the forum
now that our oneplus 6 got an official update i want to ask something. is this okey/safe to do
currently having omnirom installed in both slots and to update base could this work? or will it give problems
1 have custom rom installed with 9.0.4 base
2 flash oxygenos (9.0.5) x2
3 flash custom rom x2
4 reboot twrp
5 flash gapps + magisk
6 reboot system
if i flash oxygenos over omnirom just to update the base and never reboot system to oxygenos will this still give me problems with data? or is it a safe way to update the base ? or is the only way to go to do factory reset?
Click to expand...
Click to collapse
Don't do it.
First, it is unneccessary (and useless) and second the security patch of 9.0.5 is too old compared to omni. Even if you don't boot into OOS System your whole storage won't get decrypted anymore (so you have to format your complete internal storage)
You have to get away a bit from this thought of the "Rom base". If you install a custom rom, you install a completely new system. The need of installing OOS "as a base" is mainly the vendor (and some other) partitions. And as long as these don't get updated/changed, your exact "base rom" is irrelevant.
9.0.5 doesn't have any significant changes. And these few changes are only relevant for the system itself (which would get deleted by installing a custom rom)
castrum_doloris said:
Don't do it.
First, it is unneccessary (and useless) and second the security patch of 9.0.5 is too old compared to omni. Even if you don't boot into OOS System your whole storage won't get decrypted anymore (so you have to format your complete internal storage)
You have to get away a bit from this thought of the "Rom base". If you install a custom rom, you install a completely new system. The need of installing OOS "as a base" is mainly the vendor (and some other) partitions. And as long as these don't get updated/changed, your exact "base rom" is irrelevant.
9.0.5 doesn't have any significant changes. And these few changes are only relevant for the system itself (which would get deleted by installing a custom rom)
Click to expand...
Click to collapse
okey I'm using the disable dm-verity, forceencrypt script btw. but okey i see now hehe. thanks for your answer
Hi guys, I open this thread to solve problems / doubts of this chinese version of One Plus 7 GM1900 because I guess many will be in my place.
I tell you my case:
My intention is to open bootloader to be able to put custom recovery TWRP and root it with Magisk.
Once I have it, I have doubts:
1. If I want to remove TWRP and Root, and I will leave all stock, what steps should I take?
2. If I am in OOS (for example 9.5.2) with TWRP and root and want to upgrade to a new version of OOS (for example 9.5.6), what steps do I have to follow?
3. I would like to know if this is true, and if so, what would be the solution: I have read that when a Wipe System is made from Twrp, the bootloader can be closed or that the phone does not start in fastboot mode causing a crash. Is this true?. I thought about when I wanted to install a cleaner ROM stock, make a Wipe System, data, cache and dalvik and then flash the rom, and according to that it might not be possible.
Thank you.
Hi, are these Treble GSI roms compatible with the OnePlus 7 (not pro) Chinese version GM 1900 ???
Roms Treble GSI:
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
hardware is the same, firmware also fits from EU/Indian devices. next time just use search.
tURkOsANsE said:
1. If I want to remove TWRP and Root, and I will leave all stock, what steps should I take?
Click to expand...
Click to collapse
Flash the stock ROM and reboot. You'll have a phone with stock recovery and ROM with no root access. It won't relock your bootloader though, so you'll have to do it with: fastboot oem lock
2. If I am in OOS (for example 9.5.2) with TWRP and root and want to upgrade to a new version of OOS (for example 9.5.6), what steps do I have to follow?
Click to expand...
Click to collapse
You always need to flash full ROM zips if you're rooted and want to update. However to keep the custom recovery (TWRP), you need to flash the TWRP installer along with the ROM. Then to not lose root access you'll have to reboot to TWRP and flash Magisk. Just follow these steps:
1. Boot to TWRP
2. Flash ROM
3. Flash TWRP installer
4. Reboot to TWRP
5. Flash Magisk
6. Reboot to system
3. I would like to know if this is true, and if so, what would be the solution: I have read that when a Wipe System is made from Twrp, the bootloader can be closed or that the phone does not start in fastboot mode causing a crash. Is this true?. I thought about when I wanted to install a cleaner ROM stock, make a Wipe System, data, cache and dalvik and then flash the rom, and according to that it might not be possible.
Click to expand...
Click to collapse
I haven't tried that yet. But since TWRP builds are official, I don't think there are bugs like that. Why don't you give it a try and let us all know?
@dewri21 Thank you very much for your answers, you have helped me a lot, thank you for your clear explanations, please like this, help those who are starting in this world.
dewri21 said:
I haven't tried that yet. But since TWRP builds are official, I don't think there are bugs like that. Why don't you give it a try and let us all know?
Click to expand...
Click to collapse
Hehehehe I dare not do it, I could run out of mobile phone and end up with a brick. At the moment if I want to put clean OOS I think I will use Fastboot mode. Let's see if a partner who knows how to get out of a brick does Wipe Sistem and confirms that.
FASTBOOT: https://forum.xda-developers.com/oneplus-7/how-to/rom-stock-fastboot-roms-oneplus-7-t3937478
Hi guys, I am writing to let you know that I have flashed the fastboot 9.5.6 BA ROM in my OnePlus 7 Chinese version GM 1900 and it worked perfectly. I was in TWRP, Root Margisk and Custom Kernel, and now I'm back in Stock. My device being a Chinese version came with ROM AA when removed from the box, and I confirm that the BA version can also be set up by Fastboot.
Add that as it is said, the first restart is slow, it stays a while in the warning screen of bootloader open, but it advances with the start. In my case I have not had to restore factory.
Very happy with this method to be able to return to Stock.
Hello, has anyone tried this on our OnePlus 7 to fix a brick? It seems that it is the MsMdonwloadsTools for our OnePlus 7. Someone who has a brick can try it and tell us if it works.
https://repairmymobile.in/flash/oneplus-7-flash-file/amp/
MsmDownloadTool For OnePLus 7: https://forum.xda-developers.com/oneplus-7/how-to/unbrick-tool-oneplus-7-msmtool-hydrogen-t3953240
Hi y'all. I recently got an X3 Pro and will be installing LineageOS on it. I'm just currently waiting out the 1 week period before the Mi Unlock app allows me to unlock the bootloader. I read through the official installation instructions a few times and one of the first things it says is to ensure the phone is already running its stock Android 12 ROM, which mine is. Further down where it says to factory reset in the custom recovery, it only mentions erasing the data and cache partitions. Does this mean I'm supposed to flash LOS over MIUI or is it safe to erase system first then clean install LOS? It would be much appreciated if anyone could shed some light on this. If it helps, I also intend to use OrangeFox recovery.
EDIT: I found out about Xiaomi firmware flashing while doing some more research for this. Please let me know if I've got this right. I think the reason the instructions say to be on the latest stock ROM and don't say to erase system is because MIUI has a set of closed-source low-level drivers that are available for download separately but cannot be included as part of a custom ROM. Dirty flashing LOS will keep these drivers intact while removing MIUI. If this is correct, then this should mean it's safe to erase system as long as I download the latest firmware file and flash it before the ROM so that the drivers are there when the ROM is installed. Am I right about all this?