Database Info

Procedure for custom rom to stock or custom rom to custom rom

guys, i have a little confusion:
What's the correct procedure for reinstall the stock OOS from a custom rom and the procedure for change custom rom to another one?
i ask this because every time i try i brick the phone. (so msmntool and lose internal storage)
my latest experiment:
i was on Havoc, rooted and blue_twrp
full wiped (cache's, data and system)
installed Full 9.0 OTA+ twrp on slot A
rebooted to twrp
installed again Full 9.0 OTA+ twrp on slot B
installed magisk
rebooted to system...
keep boot on recovery and also i canno't decrypt sdcard because twrp doesn't ask me the pin....
someone suggested to me to format data, but i don't want to lose my internal storage anytime...
help?

The best thing to do to avoid all of thi bs is to follow this guide:
https://forum.xda-developers.com/oneplus-6/how-to/tutorial-decrypt-flash-rom-pie-oreo-roms-t3838643

vivmar said:
guys, i have a little confusion:
What's the correct procedure for reinstall the stock OOS from a custom rom and the procedure for change custom rom to another one?
i ask this because every time i try i brick the phone. (so msmntool and lose internal storage)
my latest experiment:
i was on Havoc, rooted and blue_twrp
full wiped (cache's, data and system)
installed Full 9.0 OTA+ twrp on slot A
rebooted to twrp
installed again Full 9.0 OTA+ twrp on slot B
installed magisk
rebooted to system...
keep boot on recovery and also i canno't decrypt sdcard because twrp doesn't ask me the pin....
someone suggested to me to format data, but i don't want to lose my internal storage anytime...
help?
Click to expand...
Click to collapse
You dont have to flash the rom to both the slots. Just make a clean flash without format data.
First of all, Stay Encrypted :laugh:
Now from custom rom to Oxygen OS make a clean flash so follow the below:
Must Use Bluspark TWRP
1. Wipe Dalvik, System, Data & Cache
2. Flash the Full OxygenOS Rom Full Zip (Links available on my threads Beta or Stable Pie)
3. Flash the TWRP installer Zip
4. Reboot to RECOVERY to make sure TWRP stays and continue to root.
5. Flash Magisk Stable to maintain root (Avoid Beta)
6. Reboot System and Enjoy the latest firmware without any data loss
Make sure you follow above and also make sure:
1. Use Bluspark TWRP
2. Move from Pie To Pie / Pie to Oreo or Oreo to Pie might require a format.
Similarly follow the same if you want to move from Oxygen OS to Custom Rom, check the rom thread if the developer needs you to flash anything extra or firmware files.
Hope the above helps :good:

Funk Wizard said:
You dont have to flash the rom to both the slots. Just make a clean flash without format data.
First of all, Stay Encrypted :laugh:
Now from custom rom to Oxygen OS make a clean flash so follow the below:
Must Use Bluspark TWRP
1. Wipe Dalvik, System, Data & Cache
2. Flash the Full OxygenOS Rom Full Zip (Links available on my threads Beta or Stable Pie)
3. Flash the TWRP installer Zip
4. Reboot to RECOVERY to make sure TWRP stays and continue to root.
5. Flash Magisk Stable to maintain root (Avoid Beta)
6. Reboot System and Enjoy the latest firmware without any data loss
Make sure you follow above and also make sure:
1. Use Bluspark TWRP
2. Move from Pie To Pie / Pie to Oreo or Oreo to Pie might require a format.
Similarly follow the same if you want to move from Oxygen OS to Custom Rom, check the rom thread if the developer needs you to flash anything extra or firmware files.
Hope the above helps :good:
Click to expand...
Click to collapse
Thanks so much!

VENDOR.IMG

I've come from miui 10.0.2.0 (oreo) to Pixel Experience gsi
Unlocked bl, installed twrp, wiped all and flashed PE
It wasn't an easy process, but I finally got rid of miui.
Now I can't install any other gsi/non-gsi rom! That's ridiculous! I'm stuck on that gsi
The thing does not boot. When I flash something else
My installation algorithm -> advanced wipe, install gsi to system -> gapps (if needed) -> get a bootloop.
The thing that is not getting changed, I thought, is my vendor. So I guessed, that I need to install vendor 10.0.4, wich is Pie.
Maybe that Is the case.
All evening I've been looking for that vendor image, and there ain't singe one!
Does anyone have a Magik link to the thread, where are all the images?
If no,
What should I do next?
I guess install miui again?
Via what? Fastboot? Is there a twrp method?
Am I really the only one, that is facing this problem on this device?
A wonderful day for the reader!

I just unzipped the fastboot rom, and there is vendor.img inside.
It wouldn't be a stupid idea to consider this as the image I am looking for? I mean I can flash that image, and it should be fine?

You should download the latest fastboot global dev rom http://bigota.d.miui.com/8.11.15/po...15_20181115.0000.00_9.0_global_3dc5c2bb71.tgz and flash it with miflash.Then flash latest twrp wipe systemmdata and then flash rom,gapps and have fun

Havoc Pie downgrade to Havoc Oreo doesnt work

Hey guys. Iam trying 1 week to get Havoc Oreo.
I used this https://forums.oneplus.com/threads/oxygenos-9-0-ota-for-the-oneplus-6.909533/ to get base Oreo Rom on my OP6. This works.
But when i want to flash Havoc Oreo (Havoc-OS-20180904-enchilada-Official.zip) via TWRP (twrp-installer-enchilada-3.2.2-0.zip only this Version works for me) i get a loop in fastboot.
Can someone help me pls?
My instruction:
1. Flash downgrade
2. Go fastboot, boot TWRP
3. Flash TWRP via ADB SIDELOAD
4. Restart to recovery
5. Flash Havoc Oreo via ADB SIDELOAD
6. Restart
7. Bootloop Fastboot mode
thanks for any help.

RockstarLover said:
Hey guys. Iam trying 1 week to get Havoc Oreo.
I used this https://forums.oneplus.com/threads/oxygenos-9-0-ota-for-the-oneplus-6.909533/ to get base Oreo Rom on my OP6. This works.
But when i want to flash Havoc Oreo (Havoc-OS-20180904-enchilada-Official.zip) via TWRP (twrp-installer-enchilada-3.2.2-0.zip only this Version works for me) i get a loop in fastboot.
Can someone help me pls?
My instruction:
1. Flash downgrade
2. Go fastboot, boot TWRP
3. Flash TWRP via ADB SIDELOAD
4. Restart to recovery
5. Flash Havoc Oreo via ADB SIDELOAD
6. Restart
7. Bootloop Fastboot mode
thanks for any help.
Click to expand...
Click to collapse
OK, so I am not sure what exists in the OnePlus forums but lets start with:
1. You are aware there are two sets of partitions on this device correct? If not, please read here: https://forum.xda-developers.com/oneplus-6/how-to/guide-noobs-guide-to-b-partitions-op6-t3816123
2. What are you running now?
3. You need to update your TWRP to blu_spark but I am not sure if the latest (v9.91) works with Oreo... I know that v9.86 works with Oreo for sure. Read and download from here: https://forum.xda-developers.com/oneplus-6/development/kernel-t3800965
4. Get the appropriate OOS zip file from this thread: https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244
Specifically OOS 5.1.11: https://www.androidfilehost.com/?fid=1322778262903980680
The basic steps should be like this (all assumes you have and unlocked bootloader):
1. If you are running OOS 5.1.11, reboot to fastboot
2. Boot blu_spark TWRP.img - fastboot boot twrp.xxx.img
3. Flash OOS 5.1.11
4. Flash blu_spark TWRP.zip to get it on both slots
5. Reboot to RECOVERY
6. Flash OOS 5.1.11
7. Flash blu_spark TWRP.zip
8. Factory reset in TWRP
9. Flash Havoc Oreo zip
10. Flash blu_spark TWRP.zip
11. Reboot to RECOVERY
12. Flash GApps
13. Flash Magisk (optional if you want root)
14. Flash no-verity if you plan to run unencrypted. (optional)
My advice is to READ READ READ before going forward with anything. The A/B partition layout is far from the traditional days of a single partition layout with a recovery partition. Educate yourself or risk bricking your device and opening up a whole different set of problems.

i do this by step by step but now iam bricked. after all it want restart but it glows only the blue led

RockstarLover said:
i do this by step by step but now iam bricked. after all it want restart but it glows only the blue led
Click to expand...
Click to collapse
It does sound like you READ READ READ before proceeding... My steps were not intended as a step-by-step guide, which is why I said the steps "should look like this". You didn't answer any of my questions, so I have no idea where you started from or where things went wrong to get you into this state...
Can you get into fastboot mode?
If so, try this thread first: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
The fastboot restore method will ONLY work if you know which OOS you were running before you got bricked...
If you can't restore from fastboot images, try this thread: https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
I cannot stress enough, you MUST read all the steps and understand what you are doing before doing anything. If you have any questions, ASK before proceeding... Good luck.

thank u for ur help. i used the second method because the first didnt worked and now iam unbricked.
1. You are aware there are two sets of partitions on this device correct?
Click to expand...
Click to collapse
I know it
2. What are you running now?
Click to expand...
Click to collapse
Now iam running Oxygen OS 5.1.5 Android 8.1.0 and Device State is locked
Is this normal that in fastboot shows this bootloader and baseband empty ?
productname - xxx
variant -sdm ufs
bootloader version -
baseband version -
serialnumber - xxxxxxx
secure boot - yes
I want to try again to get havoc oreo. i will w8 for ur response.

RockstarLover said:
thank u for ur help. i used the second method because the first didnt worked and now iam unbricked.
I know it
Now iam running Oxygen OS 5.1.5 Android 8.1.0 and Device State is locked
Is this normal that in fastboot shows this bootloader and baseband empty ?
productname - xxx
variant -sdm ufs
bootloader version -
baseband version -
serialnumber - xxxxxxx
secure boot - yes
I want to try again to get havoc oreo. i will w8 for ur response.
Click to expand...
Click to collapse
You are back up and running, good work! Congrats!
When you say the device is 'locked', you mean the bootloader is locked again? It shows 'Locked' in fastboot? Obviously you need to unlock the bootloader again before proceeding if this is the case...
And 'Yes', it is normal for 'bootloader version' and 'baseband' to be blank. It shows the same on my device anyway, and I can flash custom ROMs with no issues, and everything works.
At this point, you should be able to follow the steps in my post, making sure you first unlock the bootloader (which will wipe all of your data). You might want to format data (not just wipe as well) to start fresh. I would also confirm that there are no issues running Havoc Oreo with encryption (I'd recommend asking the question in the Havoc OnePlus telegram channel, https://t.me/havoconeplus). After people ask to "Why are you running Oreo?!?!", you just might get an answer... I dumped being encrypted after about a week of having this device because it made moving between ROMs more difficult.
In step 14, I mention the no-verity file to remove force encryption. I have attached it to this post. Again, you may want to have /data encrypted (necessity, personal preference etc.) so this isn't mandatory but I found it made flashing different ROM's much easier (personal preference really).

do u know where u find the havoc oreo rom now ? they changed their download directory. and the overview is confusing me.

RockstarLover said:
do u know where u find the havoc oreo rom now ? they changed their download directory. and the overview is confusing me.
Click to expand...
Click to collapse
Looks like they removed Oreo builds, you might be out of luck. Check out XenonHD 8.1 thread if your set on running Oreo, was updated to Dec. Security patch.

hey brother. i have good news. i just want download again havoc oreo cause i deleted the old zip. i had thought maybe the oreo havoc zip was faulty. now i restored it with a restore tool. i tried again and now it works.
IAM ON HAVOC OREO . It starts but now i got a message.
"Android System
A vendor image mismatch has been detected. Typically this means your vendor image is out of date.Please ensure your vendor image matches OPM1.171019.011."
what is this now

RockstarLover said:
hey brother. i have good news. i just want download again havoc oreo cause i deleted the old zip. i had thought maybe the oreo havoc zip was faulty. now i restored it with a restore tool. i tried again and now it works.
IAM ON HAVOC OREO . It starts but now i got a message.
"Android System
A vendor image mismatch has been detected. Typically this means your vendor image is out of date.Please ensure your vendor image matches OPM1.171019.011."
what is this now
Click to expand...
Click to collapse
Did you flash OOS 5.1.11 on both slots? I know you said you were on OOS 5.1.5 when you did the MSM tool restore.
Unsure if the Havoc build you are running requires a certain FW. Usually the devs update the blobs on customer ROMs based on the latest releases of OOS. In this case, 5.1.11 was the last version of OOS Oreo.

i was on 5.1.5 and flashed 5.1.11 on both slots and then i flashed havoc rom

RockstarLover said:
i was on 5.1.5 and flashed 5.1.11 on both slots and then i flashed havoc rom
Click to expand...
Click to collapse
I'd recommend just going to Pie. I haven't run Havoc in over a month but the latest AEX is solid and battery life is excellent. The Pie ROMs have stabilized significantly in the last month.

i just flashed the latest havoc rom now. Really really thanks brother. ur a good boy.
have a good year

[Q] do we need to flash base ROM if another custom ROM needs the exact same base ROM?

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

Is there a latest stock ROM I can flash instead of the custom ROM I'm using now?

I'm TWRP'd and Magisk'd running a custom ROM (Havoc}, but it's a little buggy. I'm looking to flash a stock ROM with the latest OxygenOS, and then maybe use a Magisk module over that.
Can I? And if so, can you point me to the correct custom ROM thread? I see a couple, but not sure which one is flashable, and which one is for restoring the phone to completely stock (removing TWRP, etc.).

I suggest using this: https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
-BoneZ- said:
I see a couple, but not sure which one is flashable, and which one is for restoring the phone to completely stock (removing TWRP, etc.).
Click to expand...
Click to collapse
I don't think you can flash a stock ROM, and keep TWRP without flashing TWRP again. TWRP will always be removed when flashing a stock ROM, since recovery doesn't reside on it's own partition for this device, but rather is on boot.img, which by definition needs to be flashed with the ROM (contains the kernel).
AFAIK, you will need to flash the stock ROM then flash TWRP and Magisk again. To do that, fastboot flash the above linked stock ROM, then fastboot boot TWRP.img, then in TWRP flash TWRP installer zip and flash Magisk. Wouldn't take long to do, just have the TWRP zip and Magisk zip on the phone ready to go, before you flash the stock ROM.

redpoint73 said:
I suggest using this: https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
I don't think you can flash a stock ROM, and keep TWRP without flashing TWRP again. TWRP will always be removed when flashing a stock ROM, since recovery doesn't reside on it's own partition for this device, but rather is on boot.img, which by definition needs to be flashed with the ROM (contains the kernel).
AFAIK, you will need to flash the stock ROM then flash TWRP and Magisk again. To do that, fastboot flash the above linked stock ROM, then fastboot boot TWRP.img, then in TWRP flash TWRP installer zip and flash Magisk. Wouldn't take long to do, just have the TWRP zip and Magisk zip on the phone ready to go, before you flash the stock ROM.
Click to expand...
Click to collapse
I want to flash havoc OS and want to know if I can go back to OOS if I download the full OTA zip and flash it like you normally would (twrp and magisk)

D.Va said:
I want to flash havoc OS and want to know if I can go back to OOS if I download the full OTA zip and flash it like you normally would (twrp and magisk)
Click to expand...
Click to collapse
I have the same question. I'm on Havoc now and unencrypted and would like to back up Havoc and go back to OOS for now due to WiFi calling not working. With out having to reflash Twrp etc

The_Keeper86 said:
I have the same question. I'm on Havoc now and unencrypted and would like to back up Havoc and go back to OOS for now due to WiFi calling not working. With out having to reflash Twrp etc
Click to expand...
Click to collapse
Anyone?