Database Info

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

[Thread doubts] OnePlus 7 chinese version [GM1900]

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

is it possible to upgrade from pie hos to a10 oos using local update?

hello there.
sorry for making a new thread .. ive asked my question multiple times no one answered properly. so here's the situation:
just received the phone from china . i'm on android pie hos. and want to update to ob7 . having root and twrp is it the right way to do it? :
1. update to ob7 using local update and full zip file.
2. unlock the bootloader and flash twrp 70 (or 74 i'm not sure?) using adb
3. flash magisk and twrp installer in twrp recovery
4. done!
i heared its better to use twrp 70 and dont know the reason. whats wrong with the latest version?

Not sure if that will work, but locally upgrading from h2OS to OOS worked on my old op6 when I had it.
If it does not work;
Backup your files first then you need to unlock your bootloader.
Then boot twrp via command prompt. Once booted into twrp. Wipe data and do a factory reset there. Flash twrp installer then reboot into recovery.
Flash OB7, twrp installer and magisk then reboot to recovery again and flash ob7, twrp installer and magisk then reboot to system
I'm using .74
Not sure what the problem is/are.
Regards

Dark Fear said:
hello there.
sorry for making a new thread .. ive asked my question multiple times no one answered properly. so here's the situation:
just received the phone from china . i'm on android pie hos. and want to update to ob7 . having root and twrp is it the right way to do it? :
1. update to ob7 using local update and full zip file.
2. unlock the bootloader and flash twrp 70 (or 74 i'm not sure?) using adb
3. flash magisk and twrp installer in twrp recovery
4. done!
i heared its better to use twrp 70 and dont know the reason. whats wrong with the latest version?
Click to expand...
Click to collapse
It can be done but I wasn't happy with it there were loads of bugs.. Issues slowdowns etc.. I would suggest strictly against it..

theocdguy said:
It can be done but I wasn't happy with it there were loads of bugs.. Issues slowdowns etc.. I would suggest strictly against it..
Click to expand...
Click to collapse
so whats the right way to do it

Dark Fear said:
so whats the right way to do it
Click to expand...
Click to collapse
Which route you want to follow twrp or official? If its official i'd say try the msm tool.. That will put you on oldest pie and then you can do OTA..
Twrp is self explanatory..

theocdguy said:
Which route you want to follow twrp or official? If its official i'd say try the msm tool.. That will put you on oldest pie and then you can do OTA..
Twrp is self explanatory..
Click to expand...
Click to collapse
i'm already on oldest pie.. whats the difference of his method with the one i mentioned?

Workaround for CMI Mi 10 Pro 5G Global Custom ROM & Root eg MIU 12

There is a problem while rooting and installing TWRP recovery on the MI 10 Pro 5G (German-Version ROM Global). If you try to install TWRP you will not be able to get into the recovery. If you try (Vol up + Power) you`ll only able to start the MIU-Recovery.
Also I got some problems to get google pay to work, but this way works for me.
Before we start the disclaimer " I'm not responsible for any damage / bricking / ... If this way fails on your phone"
How to install MIU 12 EU CMI to get Dual-SIM, MIU Phone-App,...
You need:
- an unlocked boot loader
- a working ADB on Win / Mac / Linux
- TWRP I took this one HERE
- a custom ROM I took the weekly EU-ROM because I want Dual-Sim, the regular MI-Caller and the other cool stuff. You could find it HERE take the one for MI 10 Pro!! Alternativ MIU 12 ROM (tested)
MIU 12 EU stable Vers: 12-10 get it here
1 Step:
connect your phone to your computer and copy your "new" ROM to the device
2. Step:
Power off phone > hold Vol down + Power and reboot in Fastboot-Mode
3. Step start TWRP in a different way
fastboot boot "link to your TWRP Recovery"
EXAMPLE: fastboot boot C:\Users\neunzehn\Desktop\ADB\TWRP\recovery.img
now you boot TWRP from you computer without installing, so if anything goes wrong you are able to plug of and reboot in Fastboot.
4. Step flash ROM
DON`T UNPLUG YOUR PHONE!
choose your preferred language in TWRP and flash the ROM you put on the Phone before
5. Step
Reboot your Phone.. it will stuck /reboot (don't get nervous let it happen for e few times)
Press " Volume up + Power" you get the MIU Recovery choose " Wipe Data"
6.Step
Wait that your phone boot is complete , in my case it tooks 10 Min... after that you got your Custom-ROM
How to root without losing Bank-Apps, Safety-Net
You need:
- an unlocked boot loader
- a working ADB on Win / Mac / Linux
1. Step:
connect your phone to your computer and copy your Magisk v20.2 to your device IMPORTED only use Magisk 20.2 you can get it HERE
2. Step:
Power off phone > hold Vol down + Power and reboot in Fastboot-Mode
3. Step start TWRP in a diffrent way
fastboot boot "link to your TWRP Recovery"
EXAMPLE: fastboot boot C:\Users\neunzehn\Desktop\ADB\TWRP\recovery.img
4. Step flash root
DON`T UNPLUG YOUR PHONE!
choose your preferred language in TWRP and flash the Magisk.zip you put on the Phone before
5 Step reboot
Reboot your Phone. After Reboot start the Magisk-App and disable "automatic-update / search for update" and make the safety-net test.
Done...
PS: In 8 years of flashing I never have seen this behavior, don't ask me why this is actually the best way to get a stable CR on your phone. I tried this way on 3 MI 10 Pro 5G bought in Germany (Telekom, Media Markt, Ebay) with the awful Global ROM
CREDITS go to: XDA and MIU for ROM and TWRP
Article UPDATES:
06/25/20: Link to TWRP was broken > corrected
06/27/20 added workaround to root
07/02 added stable 12 MIU EU-ROM (all languages are supported)

Interesting, must then be specific to the German edition of the phone as I didn't get this with my (Global) Mi 10 Pro !
Following your description it seems as if flashing TWRP does not work, what are the commands you used ? It should be "fastboot flash recovery <twrp_file.img>"....
As an idea: what would happen if you boot TWRP as in your step 4, then copy the TWRP file to the phone and install TWRP from TWRP ?

Thanks, nice to know, i even got my phone from mediamarkt in germany.
Could you please tell me, is the phone encrypted after you've flashed Xiaomi.eu?
AND, is google pay working?
thx

s3axel said:
Interesting, must then be specific to the German edition of the phone as I didn't get this with my (Global) Mi 10 Pro !
As an idea: what would happen if you boot TWRP as in your step 4, then copy the TWRP file to the phone and install TWRP from TWRP ?
Click to expand...
Click to collapse
I also tired this, but it produced a boot loop an " Chinese-Letters"

Flash-User said:
Thanks, nice to know, i even got my phone from mediamarkt in germany.
Could you please tell me, is the phone encrypted after you've flashed Xiaomi.eu?
AND, is google pay working?
thx
Click to expand...
Click to collapse
You have to encrypt it at the first boot via your MI-Account , Yes Google Pay works for me and also Postbank, Moneese, and im able to "disable" the Exposure Notification Framework ( the discussion on SWR / WDR / NDR in Germany about GPRD / Security of the Covid-STuff)

neunzehn77 said:
If you try to install TWRP you will not be able to get into the recovery. If you try (Vol up + Power) you`ll only able to start the MIU-Recovery.
Click to expand...
Click to collapse
it's been like this for years now, just google "twrp replaced by stock recovery xiaomi reboot" you'll find lots of reddit posts of this happening.
i only do this once when buying a new device so sorry I don't remember exactly which one but there are two ways to reboot after installing the recovery and one of them prevents the device from overwrite the recovery, if I remember correctly
1- run "fastboot reboot" and hold volume up
2- hold power and vol up until the device reboots and boots to recovery
on another note, this section is for development not tutorials and general discussions

Won't happen if you follow my guide. My friend in Switzerland tried it with the Global Mi10Pro without issues
https://youtu.be/uM1dBptUBd8

Thank you neunhzehn77 !!! U saved my day
Now folks let me tell you something...
I´m not new to rooting phones anyway and i did try several ways to get the xiamomi.eu custom rom on my Mi 10 Pro.
I failed every single time.
Then asking neunzehn77 for specific help on my flashing situation in a private chat.
This guy explained to me some of the "super-partition-features-issues" and cleared his guide for me.
What can i say... i truly folled his guide step-by-step and i´m now on xiaomi.eu beta MIUI 12 rom in no time.
And again thank neunzehn77 for saving my MIUI-Rom-experience for good.:victory:

underlines said:
Won't happen if you follow my guide. My friend in Switzerland tried it with the Global Mi10Pro without issues
https://youtu.be/uM1dBptUBd8
Click to expand...
Click to collapse
If you follow your guide, you will lose essential-stuff like some Banking-Apps, Google-Pay,... and some more. I tried your way on a "German MI 10 Pro 5G" and get random boot-loops... maybe there is an unknown difference between CN ,EU, Global Versions. I don't know... for me your guide isn't working... but maybe that's a way for CN/US bought MI`s
In my case its better to leave the Super-Partition untouched, to get unwanted effects.
Thanx for sharing Mate...

neunzehn77 said:
If you follow your guide, you will lose essential-stuff like some Banking-Apps, Google-Pay,... and some more. I tried your way on a "German MI 10 Pro 5G" and get random boot-loops... maybe there is an unknown difference between CN ,EU, Global Versions. I don't know... for me your guide isn't working... but maybe that's a way for CN/US bought MI`s
In my case its better to leave the Super-Partition untouched, to get unwanted effects.
Thanx for sharing Mate...
Click to expand...
Click to collapse
Thanks for this valuable feedback. I have to put up a warning for EU users then.
Can you remember what exactly it was that lead to errors or problems? And which TWRP did you use? xiaomi.eu's modified one or LR.Team's?
Also, how exactly did you flash magisk?
On my CN CMI I also had all these problems, when touching the super partition. That's common as soon as you modify the super partition: https://xiaomi.eu/community/threads/twrp-and-system-problem.56103/
Do you remember what exactly you did differently from my guide in order for you to make it work? I could incorporate that into the AIO Guide on XDA.

underlines said:
Won't happen if you follow my guide. My friend in Switzerland tried it with the Global Mi10Pro without issues
https://youtu.be/uM1dBptUBd8
Click to expand...
Click to collapse
Hello, does your friend in Switzerland have 5G working ? I happen to be in Switzerland too (carrier : Sunrise), everything works smoothly but 5G... Thanks for your answer.

AFAIK all custom ROMs based on CN, so no 5g..

@neunzehn77 I have a question for you. I just unlocked the bootloader of my Mi 10 (yes not the pro, but the principle is the same). I bought it through Orange in Belgium and it is the Global version, I suppose it must be similar to yours. I see that you didn't format or wipe when flashing a new ROM and all other guides I find do format /data. Isn't this necessary when going from the official ROM to a Xiaomi.EU ROM? The problem with your workaround would then be that the ROM you put in your storage would be gone. I am used to flashing Oneplus devices, but this is something else... It really confuses me.

sithlord512589 said:
Now folks let me tell you something...
I´m not new to rooting phones anyway and i did try several ways to get the xiamomi.eu custom rom on my Mi 10 Pro.
I failed every single time.
Then asking neunzehn77 for specific help on my flashing situation in a private chat.
This guy explained to me some of the "super-partition-features-issues" and cleared his guide for me.
What can i say... i truly folled his guide step-by-step and i´m now on xiaomi.eu beta MIUI 12 rom in no time.
And again thank neunzehn77 for saving my MIUI-Rom-experience for good.:victory:
Click to expand...
Click to collapse
Hi, I'm on the verge of trying to flash xiaomi.eu ROM on my Mi 10 (Global - Belgium) and rooting it afterwards. The problem is that I'm a bit afraid of getting an error or a bootloop and not knowing how to recover from it. I'm not familiar with Xiaomi because I always had a Oneplus device before. How did you fix it? Did you format /data like other guides suggest? Or did you just "dirty flash" xiaomi.eu on top of the stock ROM like in this workaround guide?

Marcoziezo said:
Hi, I'm on the verge of trying to flash xiaomi.eu ROM on my Mi 10 (Global - Belgium) and rooting it afterwards. The problem is that I'm a bit afraid of getting an error or a bootloop and not knowing how to recover from it. I'm not familiar with Xiaomi because I always had a Oneplus device before. How did you fix it? Did you format /data like other guides suggest? Or did you just "dirty flash" xiaomi.eu on top of the stock ROM like in this workaround guide?
Click to expand...
Click to collapse
No no.. when you switch to custom you have to start all over. So wipe and format(make cloud backup ?)

marcel112 said:
No no.. when you switch to custom you have to start all over. So wipe and format(make cloud backup ?)
Click to expand...
Click to collapse
I used the latest LR team TWRP (3.4.2B wzsx150 from june 23) and it worked out fine with my global (European) version of the Mi 10. So this workaround is not needed anymore I guess.
1) I fastboot flashed this TWRP version
2) Booted to TWRP
3) Formatted /data
4) Rebooted to TWRP to be able to acces the internal storage
5) Transferred and flashed the Xiaomi.EU stable build of August 10th
6) Rebooted to system.
Everything is working fine, I am rooted using Magisk 20.4 with some modules and even swift installer is working great.
Cheers

Marcoziezo said:
I used the latest LR team TWRP (3.4.2B wzsx150 from june 23) and it worked out fine with my global (European) version of the Mi 10. So this workaround is not needed anymore I guess.
1) I fastboot flashed this TWRP version
2) Booted to TWRP
3) Formatted /data
4) Rebooted to TWRP to be able to acces the internal storage
5) Transferred and flashed the Xiaomi.EU stable build of August 10th
6) Rebooted to system.
Everything is working fine, I am rooted using Magisk 20.4 with some modules and even swift installer is working great.
Cheers
Click to expand...
Click to collapse
just remember, on android 11, you cant use normal magisk 20.4.
You need to use canary builds.
Also Android 11, twrp cant decrypt using pincode... you need to set up , gesture

Is imei repair and qcn file output for mi 10 pro?

badaas said:
AFAIK all custom ROMs based on CN, so no 5g..
Click to expand...
Click to collapse
Just saw this.
Maybe this is the reason that the EU rom does not have 5G working.

Development OP9-LEMONADE-A13-ROM-WATCHDOGS-JUNE 25, 2023

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.