Database Info

OB10 to custom roms

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

Going from 11.0.15.0 to Poco X2 11.0.7.0

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.

Android 11 Red Magic Rom [FLASHGUIDE]

Hello again!
I saw a post where leipnacht provides a link to the public beta of Android R. (I let you here a drive link to download it faster).
I flashed it and it's working properly on my device. There is some bugs, but the most part of the things works without problems (Personally, I didn't face any bug itself (only a low noise with the vibration by the moment), but there are some comments in the page of bbs nubia about some problems with other things.
The previous conditions from where I update to Android R Red Magic Rom were using a GSI in the Android 10 chinese version of the rom. So, the steps I followed are:
1. In the recovery, wipe data, cache and dalvik. Also, format data.
2. Flash in the Android 10 TWRP the Android R rom.
3. Flash this NikGapps Package , Magisk Debug and DFE (Encrypt disabler in order to be able decrypt data in the recovery). I also flashed Permissive_5 but I think there is no need to do it.
4. Boot and enjoy.
I will attach all the files and some screenshots for those who want to take a see to the rom. Personally, I feel no changes in this version, but, as always, the performance is great and it runs really smooth. It's a beta version, so I hope more changes in the future.
P.D. In order to get safetynet passing, I used HideProps Config magisk module. There is no big issues with it, and everything is fixable
P.d.2. This rom has antiroll-back active, so if you want to go back to previous version, you will have to use the unbrick tool

Perseo99 said:
Hello again!
I saw a post where leipnacht provides a link to the public beta of Android R. (I let you here a drive link to download it faster).
I flashed it and it's working properly on my device. There is some bugs, but the most part of the things works without problems (Personally, I didn't face any bug itself (only a low noise with the vibration by the moment), but there are some comments in the page of bbs nubia about some problems with other things.
The previous conditions from where I update to Android R Red Magic Rom were using a GSI in the Android 10 chinese version of the rom. So, the steps I followed are:
1. In the recovery, wipe data, cache and dalvik. Also, format data.
2. Flash in the Android 10 TWRP the Android R rom.
3. Flash this NikGapps Package , Magisk Debug and DFE (Encrypt disabler in order to be able decrypt data in the recovery). I also flashed Permissive_5 but I think there is no need to do it.
4. Boot and enjoy.
I will attach all the files and some screenshots for those who want to take a see to the rom. Personally, I feel no changes in this version, but, as always, the performance is great and it runs really smooth. It's a beta version, so I hope more changes in the future.
P.D. In order to get safetynet passing, I used HideProps Config magisk module. There is no big issues with it, and everything is fixable
P.d.2. This rom has antiroll-back active, so if you want to go back to previous version, you will have to use the unbrick tool
Click to expand...
Click to collapse
Thanks for the update.
I have been planning to upgrade my Red Magic 3 to Android 10 (CN rom) for quite a while now. And its good to know A11 beta has arrived too.
Have you tried fps games on this device like pubg mobile, cod etc? Do they work properly ?
Also, I haven't even unlocked bootloader on my device. Can you proivde a better guide, to completely switch from global rom (stock) to A11 (beta) or A10 CN rom (stable).
Need links / guide for following items -
- Unlock bootloader
- Link of working twrp and steps to flash (should I change recovery after installing this beta?)
- Gapps and Magisk link (As I can't run this device without Google services).
It will be a huge help for me to get started.
Take your time with it (no rush).
Thanks in advance!!!

nalin_s3 said:
Thanks for the update.
I have been planning to upgrade my Red Magic 3 to Android 10 (CN rom) for quite a while now. And its good to know A11 beta has arrived too.
Have you tried fps games on this device like pubg mobile, cod etc? Do they work properly ?
Also, I haven't even unlocked bootloader on my device. Can you proivde a better guide, to completely switch from global rom (stock) to A11 (beta) or A10 CN rom (stable).
Need links / guide for following items -
- Unlock bootloader
- Link of working twrp and steps to flash (should I change recovery after installing this beta?)
- Gapps and Magisk link (As I can't run this device without Google services).
It will be a huge help for me to get started.
Take your time with it (no rush).
Thanks in advance!!!
Click to expand...
Click to collapse
Hey!
No problem at all. I let you here two guides to migrate to the cn rom and even a gsi
Be careful and aware about what you are going to do, It's not specially difficult but you have to get ready all the files and tools in case of brick or bootloops.
Enjoy the flashing!

Perseo99 said:
Hey!
No problem at all. I let you here two guides to migrate to the cn rom and even a gsi
Be careful and aware about what you are going to do, It's not specially difficult but you have to get ready all the files and tools in case of brick or bootloops.
Enjoy the flashing!
Click to expand...
Click to collapse
Thanks for the links. I am planning to update to stable A10 version for now.
I have few questions it be a huge help you could clear some of my doubts -
1. After unlocking bootloader I have to install TWRP (for gapps to run). So should I install TWRP after flashing CN rom ? or before ?
I am asking this because I read in some guides that only CN rom is custom recovery capable.
2. If you have run A10 stables before, does OTA updates require to be installed via TWRP only ?
Will I loose Gapps and Root access if I updated the ota directly from settings? And will every rom flash with TWRP clear my installed apps ?
Thanks in advance for helping!!. ??

nalin_s3 said:
Thanks for the links. I am planning to update to stable A10 version for now.
I have few questions it be a huge help you could clear some of my doubts -
1. After unlocking bootloader I have to install TWRP (for gapps to run). So should I install TWRP after flashing CN rom ? or before ?
I am asking this because I read in some guides that only CN rom is custom recovery capable.
2. If you have run A10 stables before, does OTA updates require to be installed via TWRP only ?
Will I loose Gapps and Root access if I updated the ota directly from settings? And will every rom flash with TWRP clear my installed apps ?
Thanks in advance for helping!!. ?
Click to expand...
Click to collapse
Well, I will go in order:
1. You have to flash first in the stock recovery the Android 10 CN rom and then flash the custom recovery. There is no twrp avaible for global rom. Once in the custom recovery, you can flash Gapps and Magisk (in android 10 there is no need of DFE file, the recovery is able to decrypt data properly.
2. You don't need to get worried about OTAs, there is no a constant software update work by nubia for this device, but in case of update, you would flash the rom from the offcial page, with magisk and gapps again and be sure you keep the custom recovery.

Perseo99 said:
Hello again!
I saw a post where leipnacht provides a link to the public beta of Android R. (I let you here a drive link to download it faster).
I flashed it and it's working properly on my device. There is some bugs, but the most part of the things works without problems (Personally, I didn't face any bug itself (only a low noise with the vibration by the moment), but there are some comments in the page of bbs nubia about some problems with other things.
The previous conditions from where I update to Android R Red Magic Rom were using a GSI in the Android 10 chinese version of the rom. So, the steps I followed are:
1. In the recovery, wipe data, cache and dalvik. Also, format data.
2. Flash in the Android 10 TWRP the Android R rom.
3. Flash this NikGapps Package , Magisk Debug and DFE (Encrypt disabler in order to be able decrypt data in the recovery). I also flashed Permissive_5 but I think there is no need to do it.
4. Boot and enjoy.
I will attach all the files and some screenshots for those who want to take a see to the rom. Personally, I feel no changes in this version, but, as always, the performance is great and it runs really smooth. It's a beta version, so I hope more changes in the future.
P.D. In order to get safetynet passing, I used HideProps Config magisk module. There is no big issues with it, and everything is fixable
P.d.2. This rom has antiroll-back active, so if you want to go back to previous version, you will have to use the unbrick tool
Click to expand...
Click to collapse
Can you check your pm??

There's no problem in flashing but take note there's no going back i mean you cant downgrade it anymore using unbric tool even if you flash rom using cmd it will not work my rm3s now is bricked theres no tool or method that can fix it right now. Unless someone make a new unbrick tool

jepoyxxv said:
There's no problem in flashing but take note there's no going back i mean you cant downgrade it anymore using unbric tool even if you flash rom using cmd it will not work my rm3s now is bricked theres no tool or method that can fix it right now. Unless someone make a new unbrick tool
Click to expand...
Click to collapse
I already went to 11 and flash to 3.11

But how did you flash android 10 3.11 in rm3s no matter what tool i use i cant fix my rm3s from being bricked by flashing android 11 beta can you tell me what did you do did you flash it manually in command prompt please help me

jepoyxxv said:
But how did you flash android 10 3.11 in rm3s no matter what tool i use i cant fix my rm3s from being bricked by flashing android 11 beta can you tell me what did you do did you flash it manually in command prompt please help me
Click to expand...
Click to collapse
If you are in 11 beta and want to downgrade..just simple flash global version and again flash 3.11 done

What did you use to flash global rom lastweek i successfully installed android 11 beta and use unbrick tool to go back to global but i got bricked. And i cant fix it anymore.

jepoyxxv said:
What did you use to flash global rom lastweek i successfully installed android 11 beta and use unbrick tool to go back to global but i got bricked. And i cant fix it anymore.
Click to expand...
Click to collapse
I just flash global from otg and tham again 3.11

walkwitmeinhel said:
I just flash global from otg and tham again 3.11
Click to expand...
Click to collapse
Could you please tell me where to download the 3.11 rom. I am not aware that this rom exists. Is this a CN or global rom? Thanks for your reply.

[email protected] said:
Could you please tell me where to download the 3.11 rom. I am not aware that this rom exists. Is this a CN or global rom? Thanks for your reply.
Click to expand...
Click to collapse
http://ui.nubia.cn/rom/detail/64

Oh! Didn't expect that. I just post this for Red Magic 3 device users. I don't know how RM3S actually works. Have you tried the unbrick tool from chinese version? Or just flashing the global rom from recovery is enough?

Wait is there a chinese unbrick tool cn. version for red magic can you provide me a link.. unbrick tool 3/3s.global by jerry is not working anymore if you got brick by android 11 beta rom...

jepoyxxv said:
Wait is there a chinese unbrick tool cn. version for red magic can you provide me a link.. unbrick tool 3/3s.global by jerry is not working anymore if you got brick by android 11 beta rom...
Click to expand...
Click to collapse
Let's see. Here is a link for Red Magic 3S unbrick tool. Download the non-eu ones.
If you have a Red Magic 3 with Red Magic 3s software, I will provide you the link to the other unbrick tool.
Also, you can try flashing the global rom from the stock recovery included in the package of the A11 rom that you have download.

Thanks for replying my bro.. my device is rm3s i already use rm3 and rm3s unbrick tool.. downloading fire hose programmer and image was successfully but.. my phone is still corrupted... And one thingg i dont have twrp install in my rm3s thats why its hard for me to fix it.. can you please guide or teach me how to flash stock recovery using global rom i know how to use cmd and adb

jepoyxxv said:
Wait is there a chinese unbrick tool cn. version for red magic can you provide me a link.. unbrick tool 3/3s.global by jerry is not working anymore if you got brick by android 11 beta rom...
Click to expand...
Click to collapse
So then, It's not a problem of the unbrick tool, that is actually working properly. The thing is that you didn't know how to do a correct process to migrate from cm rom to global...
The first thing you should do is reboot the phone into fastboot mode (power+vol. Down). Then, connect the phone to the PC and type the next commands in the cmd:
Code:
fastboot devices
in order to see if your device is being recognized
Code:
fastboot oem nubia_unlock NUBIA_NX629J
to unlock the bootloader
Code:
fastboot flashing unlock
in order to make your phone able to boot with a modified software. In the moment you will enter this command, you will see a screen advising you about your data (it'll be erased once you accept to unlock flashing).
After that, you can reboot your phone, that will show you an screen advising you that the bootloader is open. Accept and continue without problems.
Tell me if you have been able to make your phone boot.

Perseo99 said:
Well, I will go in order:
1. You have to flash first in the stock recovery the Android 10 CN rom and then flash the custom recovery. There is no twrp avaible for global rom. Once in the custom recovery, you can flash Gapps and Magisk (in android 10 there is no need of DFE file, the recovery is able to decrypt data properly.
2. You don't need to get worried about OTAs, there is no a constant software update work by nubia for this device, but in case of update, you would flash the rom from the offcial page, with magisk and gapps again and be sure you keep the custom recovery.
Click to expand...
Click to collapse
Required in CN A10 + twrp A10, or maybe from CN A9 + twrp A9 to be able to flash

Bootloop Problem?

I have an interesting problem. I was using a11 stable beta official. I wanted to go back to aosp rom. I know it's impossible. But before, I was installing the official A10 rom global then install a11 aosp rom. It was working. But now, When I try to install Official rom by fastboot or recovery or mi flash tool, it stucks on boot. But interesting, I can install Abhix Rog edition rom and A11 official stable beta rom. I can't figure out this problem. I'm using orange fox recovery, also tried with TWRP. Whatever I tried that didn't work. Is there any advice for solution? Thanks in advance.
NOTE : Before, in recovery there are two folders sdcard and scard1.But now even I do format data, I only see only sdcard folder, there's no sdcard1 folder.

I solved the problem. I re-partition sdcard then format data. Then install 12.0.8.0 fw. Install havoc os 4.3 then flash dm-verity disabled then flash permissiver_v5...Boom works

hucar13 said:
I solved the problem. I re-partition sdcard then format data. Then install 12.0.8.0 fw. Install havoc os 4.3 then flash dm-verity disabled then flash permissiver_v5...Boom works
Click to expand...
Click to collapse
Hello! i am having the same problem. can you please help me with the repartitioning?

First Download the below files
1. TWRP
2. MIUI Firmware( Region wise)
3. Download Recovery Rom.
3. Download Fastboot Rom.
4. Download Mi Global Flash Tool.
5. Boot into Fastboot.
6. Flash TWRP. Install MIUI Firmware( would be around 80MB -100 MB Only) zip file.
7. install the Recovery Rom zip file. Format Data.
8. Reboot in to Bootloader.
9. Now open the Mi global flash tool and select the extracted Fastboot rom and click flash..
Hope this will solve the Problem

Question Install official RUI updates from TWRP?

So, I rooted my phone, for which I needed to unlock the bootloader and install TWRP. Now, when I want to install an update on my phone, it downloads and when I want to install it, it jumps to TWRP recovery instead of the phone's recovery, so I can't update my phone. Does anyone know how can I install the updates from TWRP?
Else, reinstall the default recovery. (Only the recovery, not the entire OS since that would un-root my phone)
Thanks.
Edit: After it boots to TWRP, it apparently tries to install the update, since I can see it on the log, but when I reboot my phone it has not installed. It errors: "E3994: This package is for "2169B" devices; this is a "". Updater process ended with ERROR: 1. Error installing zip file '/data/ota_package/OTA/.otaPackage/my_manifest_RMX3370_11.F.04_3040_202302282047.44.36402b59_all.zip'
Edit 2: After failing to install it, it prompts me to re-download it and re-install it, but it jumped from ~500MB update to 4.76GB update.

( may loose data)
I read in telegram channels, this twrp: https://www.pling.com/p/1922292 support installation latest zip. but I haven't tried.
one more thing you can do is ( may loose data)
1. restore twrp backup for recovery partition ( if you don't have backup. search recovery.img in upgrade zip )
2. reboot to recovery to check stock recovery is installed
3. install update
4. then follow steps to install twrp and magisk ( root again )

SanOne+1 said:
( may loose data)
I read in telegram channels, this twrp: https://www.pling.com/p/1922292 support installation latest zip. but I haven't tried.
one more thing you can do is ( may loose data)
1. restore twrp backup for recovery partition ( if you don't have backup. search recovery.img in upgrade zip )
2. reboot to recovery to check stock recovery is installed
3. install update
4. then follow steps to install twrp and magisk ( root again )
Click to expand...
Click to collapse
Your guide is incorrect and will definitely put the device into bootloop.
** The twrp link that you shared doesn't allow system updates to install, it is just a A13 compatable twrp recovery.
1) What if that person has not created any twrp backup of all system partitions? According to his explanation, I'm pretty sure he has not created any backup of the partitions.
2) only flashing recovery image and installing the update will again put the device into bootloop because as confirmed by the OP that his device is rooted and due to root the boot image of the device gets modified so it will put the device into bootloop.
3) unless the OP has stock boot and recovery images at his disposal he should not attempt to install the update to avoid bootloop.
** Kindly avoid sharing incorrect information you aren't sure about the correct procedure.
procedure that I follow to flash updates :
1) in magisk - uninstall magisk - restore images
2) boot device into bootloader and flash stock boot and recovery.
3) boot device and install update.
4) put device again in bootloader and flash twrp and within twrp flash magisk and reboot.
I haven't found any easier way than this. If anyone has, kindly put it below.

There's a way
Rui 4.0 Android 13 f.02
So, any verdict on this new update for the people that did update to it?
forum.xda-developers.com

Recetly I succesfully updated my Realme GT Neo 2 5G via TWRP recovery, the latest version support OTA.
Attention! After update TWPR and Magisk gone. Just reflash twrp and flash magisk normally. No need to reflash modules etc. (Just update from settings, no need to manually flash ota package from TWRP)

Hello mate can u help me with something real quick. Y are there no recent updates for gt neo 2 and if u r using a custom rom based gt neo 2 hows ur experience so far. Thanks in advance
Xemi_KryTeT.pl said:
Recetly I succesfully updated my Realme GT Neo 2 5G via TWRP recovery, the latest version support OTA.
Attention! After update TWPR and Magisk gone. Just reflash twrp and flash magisk normally. No need to reflash modules etc. (Just update from settings, no need to manually flash ota package from TWRP)
Click to expand...
Click to collapse
Which rom r u running and is it good?

Sabirsayed09 said:
Hello mate can u help me with something real quick. Y are there no recent updates for gt neo 2 and if u r using a custom rom based gt neo 2 hows ur experience so far. Thanks in advance
Which rom r u running and is it good?
Click to expand...
Click to collapse
Latest stock (4.0), I'm not going to flash custom roms for now