This is what I did.
I had xXx rom installed on my OnePlus 7 not pro version before I bought my OnePlus 7 pro. I am not responsible for any rats that wake from the dead as Zombie Rats and eat your phone.
1)Download the stock Oxygen OS rom to the sd card on your phone from the Oxygen OS website, or from the Oxygen Updater app, or from XDA. Just make sure it is the Stock Rom though. (If you Do Not have a Custom Rom, Skip to Step 3.)
2) Go into TWRP and flash your Custom Rom's Uninstaller, if there was one, that the developer made with the custom rom. (do not reboot!!!!)
3) In TWRP, flash the Magisk uninstaller. (do not reboot!!!!!)
4) In TWRP, flash the Oxygen OS Stock Rom.
4) Reboot.
5) Buy the OnePlus 7 Pro like you know you should have in the first place.
The Custom Rom, Magisk, and TWRP will No Longer be on your phone.
If you want to Relock the bootloader, follow the guide in the link below. I needed to relock my bootloader in order to return my OnePlus 7 Not pro and this is the guide that helped me to do it. It says OnePlus 7 Pro in the guide, but it also worked for me on my OnePlus 7 not pro.
Mod edit: Link removed!
I did just that and it worked perfectly. At the end I locked the bootloader again.
I used the following command in Fastboot Mode
fastboot oem lock
Could anybody share how can I move from MiUI EU ROM for K30 11.0.15.0 to Poco X2 official build 11.0.7.0?
I installed EU ROM as I found flashing ROM with TWRP was easier than using Mi Flash tool, in case we want to switch between ROM's. But, after I installed 11.0.15.0 I figured lot of the custom ROM's do not boot after flashing them and phone boots into fastboot mode (except couple of ROM's). So, I have been looking at how switch back EU MiUI ROM from 11.0.15.0 to Poco X2 11.0.7.0. The issue am facing while flashing using Mi Flash tool is that it gives error of ARB (Anti rollback error: 2, also I checked the same by issuing fastboot getvar anti, it says 2), and I am not sure how to get past this.
Could someone please help me with this?
I think your device is triggered with anti-rollback. So you cannot install any rom with build less than 11.0.15.0 that is poco x2 11.0.7.0 cant be flashed. So, you have to wait until new poco build greater than 11.0.15.0 and then flash it. Until then, flash your existing rom or some custom rom. Do it carefully and dont ever flash older roms from now, if something goes wrong, your device will hardbrick and you will have to go to service center where they have authorized EDL access to your device to flash things. Best of Luck.
You can use full recovery rom zip 11.0.7 and flash it via twrp. In 11.0.7 zip make sure you change the devicename in script from phoenixin to phoenix as twrp is pheonix.
After flashing you will be on stock 11.0.7 and stock recovery.
If you want to try custom roms , you can just flash the stock vedor zip of 11.0.07 and then flash any aosp custom rom.(you can find this zip in telegram channel/github)
eagle06 said:
You can use full recovery rom zip 11.0.7 and flash it via twrp. In 11.0.7 zip make sure you change the devicename in script from phoenixin to phoenix as twrp is pheonix.
After flashing you will be on stock 11.0.7 and stock recovery.
If you want to try custom roms , you can just flash the stock vedor zip of 11.0.07 and then flash any aosp custom rom.(you can find this zip in telegram channel/github)
Click to expand...
Click to collapse
Bro, but what about anti-rollback hardbrick?.. new miui wont allow downgrade right? he has very newer build than 11.0.7.
eagle06 said:
You can use full recovery rom zip 11.0.7 and flash it via twrp. In 11.0.7 zip make sure you change the devicename in script from phoenixin to phoenix as twrp is pheonix.
After flashing you will be on stock 11.0.7 and stock recovery.
If you want to try custom roms , you can just flash the stock vedor zip of 11.0.07 and then flash any aosp custom rom.(you can find this zip in telegram channel/github)
Click to expand...
Click to collapse
vivek12341 said:
Bro, but what about anti-rollback hardbrick?.. new miui wont allow downgrade right? he has very newer build than 11.0.7.
Click to expand...
Click to collapse
@eagle06 am worried about 11.0.15.0 > 11.0.7.0 which will trigger ARB as @vivek12341 has pointed out and it will hard brick the device, from what I have read around, hence this post if anybody knows a way out. There seemed to be workarounds initially when Xiaomi introduced ARB, I have not seen anybody mentioning such things in recent times especially for MiUI 11.
The reason why I moved to 11.0.15.0 is was, as it has no bloatware etc, and I did NOT know about ARB, now that I have 11.0.15.0 most of the custom ROMs are based on Poco X2 11.0.7.0 and I am facing issues flashing ROMs based on 11.0.7.0, as the format data from TWRP does not wipe properly + I see 98% of the time device goes to fastboot mode even if I flash Poco stock recovery and clear the data, seems like 11.0.15.0 is also an issue
May be I will have to wait till Poco releases updates > 11.0.15.0 or for MiUI 12. Actually I still dont know, not many know much on this subject.
crDroid works without any issues (which is what my current daily driver, its a very stable ROM), flashing on 11.0.15.0 after clearing data, also any ROM whose dev releases fastboot ROM's those also I can flash and boot without issues, rest all ROM's dont and end up back in fastboot mode
coolcorner said:
Could anybody share how can I move from MiUI EU ROM for K30 11.0.15.0 to Poco X2 official build 11.0.7.0?
I installed EU ROM as I found flashing ROM with TWRP was easier than using Mi Flash tool, in case we want to switch between ROM's. But, after I installed 11.0.15.0 I figured lot of the custom ROM's do not boot after flashing them and phone boots into fastboot mode (except couple of ROM's). So, I have been looking at how switch back EU MiUI ROM from 11.0.15.0 to Poco X2 11.0.7.0. The issue am facing while flashing using Mi Flash tool is that it gives error of ARB (Anti rollback error: 2, also I checked the same by issuing fastboot getvar anti, it says 2), and I am not sure how to get past this.
Could someone please help me with this?
Click to expand...
Click to collapse
You should flash back to China rom (V11.0.15.0.QGHCNXM) using miflash and install TWRP-3.4.1B-0322 using fastboot. After that you can flash all custom roms as normal. I have tried almost all the custom roms and they all work without any problem.
Lol.. Bro i am on miui 12 beta and went back to 11.0.0.7 via twrp flash...
Just download this http://bigota.d.miui.com/V11.0.7.0....NGlobal_V11.0.7.0.QGHINXM_9c232b802a_10.0.zip
Open that in pc, modify the script and rename device name to phoenix from phoenixin.
On twrp format data.. Then reboot to twrp again, tranfer that zip file and just flash. You will be back on stock global 11.0.0.7
Also crdroid as you mentioned has custom vendor which is different from china eu or global one.
If you want to use fastboot zip then you need to use https://www.xiaomitool.com/V2/ to overcome antirollback error.
eagle06 said:
Lol.. Bro i am on miui 12 beta and went back to 11.0.0.7 via twrp flash...
Just download this http://bigota.d.miui.com/V11.0.7.0....NGlobal_V11.0.7.0.QGHINXM_9c232b802a_10.0.zip
Open that in pc, modify the script and rename device name to phoenix from phonenixin.
On twrp format data.. Then reboot to twrp again, tranfer that zip file and just flash. You will be back on stock global 11.0.0.7
Also crdroid as you mentioned has custom vendor which is different from china eu or global one. e
If you want to use fastboot zip then you need to use https://www.xiaomitool.com/V2/ to overcome antirollback error.
Click to expand...
Click to collapse
1. Which script are you talking about? I could not find any script. check attached snapshot.
2. And to do this step from TWRP to flash 11.0.7.0, do I need to be on MIUI EU ROM or I can flash from any custom ROM too?
3. You were on MIUI 12 beta (official global) and changed devicename from phoenixin to phoenix and flashed using TWRP after formatting data, without hitting ARB issue? Wow!
4. You mentioned https://forum.xda-developers.com/showpost.php?p=82502389&postcount=3 Telegram/Github where we can get official vendor zip which we can flash from TWRP, any links to that?
5. Is there a Redmi K30 global ROM which I can use instead of Poco X2, they should be same right?
eagle06 said:
You can use full recovery rom zip 11.0.7 and flash it via twrp. In 11.0.7 zip make sure you change the devicename in script from phoenixin to phoenix as twrp is pheonix.
After flashing you will be on stock 11.0.7 and stock recovery.
If you want to try custom roms , you can just flash the stock vedor zip of 11.0.07 and then flash any aosp custom rom.(you can find this zip in telegram channel/github)
Click to expand...
Click to collapse
Please share telegram or github link for vendor.zip which I can flash using TWRP. As crDroid has custom vendor may be that is why it works for me on EU ROM and I see other custom ROMs do not have vendor installed while flashing using TWRP.
jngiag said:
You should flash back to China rom (V11.0.15.0.QGHCNXM) using miflash and install TWRP-3.4.1B-0322 using fastboot. After that you can flash all custom roms as normal. I have tried almost all the custom roms and they all work without any problem.
Click to expand...
Click to collapse
As a final resort will go to China ROM V11.0.15.0.QGHCNXM (this will be chinese right?) or this itself is global K30 ROM? Any links to global official MIUI K30 ROM, all I get is K30 chinese ROM
Sorry, I am asking too many questions, I do not want to brick phone in these times and go stand in queue at Mi service center during these times, when the servicing engineer will touch my phone all over
coolcorner said:
1. Which script are you talking about? I could not find any script. check attached snapshot.
Its in META-INF/com/google/android/ file name updater-script. Change getprop("ro.product.device") == "phoenixin" || this to getprop("ro.product.device") == "phoenix" || . Why we are doing this? because we are using k30 twrp.. there is no special twrp for poco x2. phoenix = k30, phoenixin=poco x2
2. And to do this step from TWRP to flash 11.0.7.0, do I need to be on MIUI EU ROM or I can flash from any custom ROM too? Any rom
3. You were on MIUI 12 beta (official global) and changed devicename from phoenixin to phoenix and flashed using TWRP after formatting data, without hitting ARB issue? Wow! Yes with twrp. When you flashed twrp recovery , your device is now treated as K30 in twrp space
4. You mentioned https://forum.xda-developers.com/showpost.php?p=82502389&postcount=3 Telegram/Github where we can get official vendor zip which we can flash from TWRP, any links to that?check Pm , cant post telegram links here
5. Is there a Redmi K30 global ROM which I can use instead of Poco X2, they should be same right?Theres no K30 global.., poco x2 rom is global, k30 roms is china and there is eu custom rom based on chinese roms
Please share telegram or github link for vendor.zip which I can flash using TWRP. As crDroid has custom vendor may be that is why it works for me on EU ROM and I see other custom ROMs do not have vendor installed while flashing using TWRP.
Whenever you want to use custom rom without vendor , you need to flash either 11.0.0.7 zip or 11.0.0.7 vendor zip before flashing that custom rom
As a final resort will go to China ROM V11.0.15.0.QGHCNXM (this will be chinese right?) or this itself is global K30 ROM? Any links to global official MIUI K30 ROM, all I get is K30 chinese ROM
Sorry, I am asking too many questions, I do not want to brick phone in these times and go stand in queue at Mi service center during these times, when the servicing engineer will touch my phone all over
Click to expand...
Click to collapse
Check my replies in blue
coolcorner said:
As a final resort will go to China ROM V11.0.15.0.QGHCNXM (this will be chinese right?) or this itself is global K30 ROM? Any links to global official MIUI K30 ROM, all I get is K30 chinese ROM
Sorry, I am asking too many questions, I do not want to brick phone in these times and go stand in queue at Mi service center during these times, when the servicing engineer will touch my phone all over
Click to expand...
Click to collapse
It is a chinese rom. You can select english as your default language. It really doesn't matter as you are going to wipe it anyway if your purpose is to use it for flashing custom roms.
[Deleted]
coolcorner said:
Just now I tried flashing V11.0.15.0.QGHCNXM using Mi Flash tool, and I hit Anti Roll back error again. Not sure what I am missing here I am on same version 11.0.15.0 EU ROM which has same Anti 2, not sure why the error this time?
Click to expand...
Click to collapse
Bro If you want to use fastboot zip then you need to use https://www.xiaomitool.com/V2/ to overcome antirollback error. Connect device and enable usb debugging and proceed.
Mi flash tool doesnt work for poco.....you always get that rollback error.
For fastboot zips use above tool.
For recovery zips use twrp.
Both methods flash the same thing and twrp will be replaced with stock recovery.
---------- Post added at 08:36 AM ---------- Previous post was at 08:20 AM ----------
Vendor only zip.
[ fw_vendor_phoenixin_miui_PHOENIXININGlobal_V11_0_7_0_QGHINXM_9c232b802a.zip
Size : 1.12 GiB
Download : fw_vendor_phoenixin_miui_PHOENIXININGlobal_V11_0_7_0_QGHINXM_9c232b802a.zip
https://drive.google.com/uc?id=1-mIvf3EhtZwLl_rg1cFgZIp5Zz4QlQZu&export=download
Flash via twrp. If you get error 7/wrong device check updater script and change name
eagle06 said:
Bro If you want to use fastboot zip then you need to use https://www.xiaomitool.com/V2/ to overcome antirollback error. Connect device and enable usb debugging and proceed.
Mi flash tool doesnt work for poco.....you always get that rollback error.
For fastboot zips use above tool.
For recovery zips use twrp.
Both methods flash the same thing and twrp will be replaced with stock recovery.
Click to expand...
Click to collapse
Thanks, really appreciate your quick revert. I am trying out with xiaomitool now. I know TWRP method is simple, just edit/change the devicename. But, I am **** scared after seeing ARB error so many times. So using xiaomitool as you mentioned use it to overcome ARB error. I will update how it goes.
I thought Xiaomi is dev/custom dev friendly, seeing all these errors, no wonder why people resent MiUI so much, of course the hardware + price is good. From my search even Google on their devices is not this harsh about ARB blocking after unlocking bootloader.
eagle06 said:
Bro If you want to use fastboot zip then you need to use https://www.xiaomitool.com/V2/ to overcome antirollback error. Connect device and enable usb debugging and proceed.
Mi flash tool doesnt work for poco.....you always get that rollback error.
For fastboot zips use above tool.
For recovery zips use twrp.
Both methods flash the same thing and twrp will be replaced with stock recovery.
---------- Post added at 08:36 AM ---------- Previous post was at 08:20 AM ----------
Vendor only zip.
[ fw_vendor_phoenixin_miui_PHOENIXININGlobal_V11_0_7_0_QGHINXM_9c232b802a.zip
Size : 1.12 GiB
Download : fw_vendor_phoenixin_miui_PHOENIXININGlobal_V11_0_7_0_QGHINXM_9c232b802a.zip
https://drive.google.com/uc?id=1-mIvf3EhtZwLl_rg1cFgZIp5Zz4QlQZu&export=download
Flash via twrp. If you get error 7/wrong device check updater script and change name
Click to expand...
Click to collapse
Thanks for the vendor image link.
Oh! yeah I am back in Poco 11.0.7.0 image, xiaomitool worked without issues. Thanks to you!!
@eagle06 do you know in this entire image (attached file) list (from tgz file) which is fastboot file? The reason I ask is, in Poco X2 in fastboot mode I see a single deadpixel, whereas when I was in EU MIUI I never saw that dead pixel. I plan to replace that file with EU MIUI fastboot image file, so when am in fastboot, it is clean without any dead pixels.
That small white pixel in fastboot is normal. All users have it including me.
Pic
eagle06 said:
Pic
Click to expand...
Click to collapse
Yep right that is the one. When I was on EU Miui, that one did not have, hence asked which is the image file for fastboot, thought I would flash that or replace next time I flash Poco stock when I am installing new custom ROM.
Yes, its a trivial thing can be ignored, does not really bother or harm.
BTW, so now that I am back in Poco X2 stock (On top of that I have installed BlissROM), next time I have to flash I can use either TWRP or Xiaomitool/V2.
1. For TWRP, I need to rename devicename to phoenix from phoenixin in updater-script and flash it using TWRP after clearing data
OR
2. I can use Xiaomitool/V2 with ADB debugging on (same step as last time)
Just check fastboot getvar anti for my phone, it also says 2. There is no problem for me flashing china rom with miflash. I have successfully flashed it 4 times before.
Good to have another way of flashing - will try the xiaomitool next time. :good:
jngiag said:
Just check fastboot getvar anti for my phone, it also says 2. There is no problem for me flashing china rom with miflash. I have successfully flashed it 4 times before.
Good to have another way of flashing - will try the xiaomitool next time. :good:
Click to expand...
Click to collapse
Woah! Miflash tool kept throwing errors at me and you are saying it worked for you? Phew!!
If I had flashed using TWRP, I might have been holding a 200gm brick in my hands LOL. Got lucky by using Xiaomitool/v2 then Thanks to you. I will stick to Xiaomitool for flashing stock ROMs hence forth.
Hi, How do I downgrade from stock unrooted 10.3.4 to 10.3.3? Can I simply install the full OTA file via local upgrade? The reason is that I'd like to install Resurrection Rom which is needs 10.3.3 as base. Of course, I'll root the phone once it's on 10.3.3.
Also, the ROM page says I need to install OOS on both slots on TWRP. How do I do this? I'd assume that if the device on stock OOS from the start, that would mean that OOS is on both the slots. Isn't this so? Pls help
Back up your data, download the full version on oxygen updater, delete all in twrp so that 0000, connect to pc to add the 2.3gb OOS, go back to flash. It will flash OOS official both slots and you will go back to stock, you can root and twrp with tool all in one after back on stock. If that for someone reason doesn't work try the fast boot rom in tool all in one, recovery firmware, delete all option. I have done this option before to lock bootloader back
djhulk2 said:
Back up your data, download the full version on oxygen updater, delete all in twrp so that 0000, connect to pc to add the 2.3gb OOS, go back to flash. It will flash OOS official both slots and you will go back to stock, you can root and twrp with tool all in one after back on stock. If that for someone reason doesn't work try the fast boot rom in tool all in one, recovery firmware, delete all option. I have done this option before to lock bootloader back
Click to expand...
Click to collapse
Thanks comrade
Hi all so I am planning to install a Havoc OS on my phone with TWRP and Magisk
So my question is in the event that the install doesnt work out for me or that I dont like the rom (no rearson why I shouldnt) how do I get back to the original A10 rom?
I have downloaded the OxygenOS 10.0.6 [EU] OnePlus 7 Pro 5G.zip file from here already. Would I be able to go ahead boot into TWRP and flash this ifneeded?
TIA Bart
bartjunited said:
Hi all so I am planning to install a Havoc OS on my phone with TWRP and Magisk
So my question is in the event that the install doesnt work out for me or that I dont like the rom (no rearson why I shouldnt) how do I get back to the original A10 rom?
I have downloaded the OxygenOS 10.0.6 [EU] OnePlus 7 Pro 5G.zip file from here already. Would I be able to go ahead boot into TWRP and flash this ifneeded?
TIA Bart
Click to expand...
Click to collapse
Hi Bart,
Make sure you keep TWRP recovery after flashing custom Rom.
Then if you want to go back, flash official Rom zip on both slots after formatting data otherwise it won't boot.
Thanks for that.
Only thing I'm not sure is what you mean by flashing to both slots?
If for example you get a boot loop can you still get into TWRP?
I assume this is a yes as this is before it boots into the phones OS?
bartjunited said:
Thanks for that.
Only thing I'm not sure is what you mean by flashing to both slots?
If for example you get a boot loop can you still get into TWRP?
I assume this is a yes as this is before it boots into the phones OS?
Click to expand...
Click to collapse
When returning to stock,
format data
Flash stock zip
Flash TWRP
Reboot into recovery which is TWRP
Follow the same steps again and reboot...
If you end up in boot loop, don't stress. You can always flash TWRP recovery again via fastboot.
Sorry, I couldn't find the answer. I installed lineage 20 on my one plus 9. I also installed the custom recovery required by lineage. I want to try out the pixel rom but what do I do about the custom lineage recovery? Do i use msm tools to restore it first? or can i install the unofficial twrp i saw on this forum instead or is there a stock recovery I can easily find to change it back? Thanks for any help.
gisted said:
Sorry, I couldn't find the answer. I installed lineage 20 on my one plus 9. I also installed the custom recovery required by lineage. I want to try out the pixel rom but what do I do about the custom lineage recovery? Do i use msm tools to restore it first? or can i install the unofficial twrp i saw on this forum instead or is there a stock recovery I can easily find to change it back? Thanks for any help.
Click to expand...
Click to collapse
I just made this same switch now back on stock waiting for 13.1 Download dtbo,vendor_boot,boot from pixel extended. Flash all 3 In fastboot. Reboot recovery wipe data sideload Pe
Thanks for the help!
gisted said:
Sorry, I couldn't find the answer. I installed lineage 20 on my one plus 9. I also installed the custom recovery required by lineage. I want to try out the pixel rom but what do I do about the custom lineage recovery? Do i use msm tools to restore it first? or can i install the unofficial twrp i saw on this forum instead or is there a stock recovery I can easily find to change it back? Thanks for any help.
Click to expand...
Click to collapse
OnePlus 9 does not have a dedicated recovery partition anymore (most modern phones don't have anymore). Instead, recovery now resides inside boot, meaning they share the same kernel. That's the reason every ROM instruction says to flash the provided boot, vendor_boot and dtbo images. Note that these 3 images are the same found in that particular ROM zip. Anyway, the point is that when you flash boot, the recovery is flashed too.
So, in your case, even if you are on LineageOS 20, and you can access LineageOS recovery, you can just go ahead and do a factory reset and flash the Pixel ROM through adb sideload. After that, boot, vendor_boot and dtbo will be automatically flashed/updated to Pixel's. But the recommended way is still to make sure you first flash those given 3 images before going to recovery and proceeding with factory reset and flashing.