I have android 10 f2 pro-global firmware 12.0.4
I wanted to ask if I root this phone and update comes, will it brick my phone?
I wanted to ask can I root it using flashing patched boot.img using the fast boot for magisk instead of twrp
I also wanted to ask people saying to flash Xiaomi.eu, first go to Chinese firmware then flash Xiaomi.eu rom or your device gets brick, is it true?
can I use other then twrp recovery to flash xiaomi.eu rom because twrp is not perfect this time and is bricking devices?
bilalrajput said:
I have android 10 f2 pro-global firmware 12.0.4
I wanted to ask if I root this phone and update comes, will it brick my phone?
I wanted to ask can I root it using flashing patched boot.img using the fast boot for magisk instead of twrp
I also wanted to ask people saying to flash Xiaomi.eu, first go to Chinese firmware then flash Xiaomi.eu rom or your device gets brick, is it true?
can I use other then twrp recovery to flash xiaomi.eu rom because twrp is not perfect this time and is bricking devices?
Click to expand...
Click to collapse
When I flash magisk I got bootloop how I fix this issue
chickentikka007 said:
When I flash magisk I got bootloop how I fix this issue
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-how-to-uninstall-magisk-module-t3940369 try this method
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
Hello,
I am having a very big problem:
Yesterday evening I unlocked the bootloader of my Poco F2 Pro and I wanted to install a custom rom (I was thinking of installing One Os).
I followed the step by step but the installation did not work and I only had access to recovery.
I managed to reset the original rom via Mi Flash but having retried the same Mi flash procedure now blocks.
Since then I find myself without a phone, the recovery seems to work but it stops there, impossible by flashing it to launch a ROM, I have the impression that the system partion does not work
To be precise, this is an 8-256GB
Thank you in advance to the person who can help me relaunch it.
Actarus0013 said:
Hello,
I am having a very big problem:
Yesterday evening I unlocked the bootloader of my Poco F2 Pro and I wanted to install a custom rom (I was thinking of installing One Os).
I followed the step by step but the installation did not work and I only had access to recovery.
I managed to reset the original rom via Mi Flash but having retried the same Mi flash procedure now blocks.
Since then I find myself without a phone, the recovery seems to work but it stops there, impossible by flashing it to launch a ROM, I have the impression that the system partion does not work
To be precise, this is an 8-256GB
Thank you in advance to the person who can help me relaunch it.
Click to expand...
Click to collapse
so u cant flash with miflash? what errors gives miflash on flashing?
Good evening,
Thanks for trying to help me.
I managed to finally flash my F2 Pro via MiFlash.
So what is the precise method to flash a rom, I would like to install MiuiMix but I do not have a view on the system partition in TWRP and I am afraid of bricking my phone.
Small precision, I do not know if that changes anything but it is an F2 Pro 8-256Go
thank you in advance
I just bought a new Redmi 9a with hopes to root this device. But after much time and effort in attempting to root it. I was just stuck with a boot loop. I did all the necessary requirement in order to root. Unlocked Bootloader (waited 7 days) Downloaded and Installed Updated Drivers..etc
I was successful in almost all steps of the rooting process until the one where im supposed to enter the twrp recovery mode. Is there a solution to this? or is because the twrp file is unofficial? Is there no chance to root this model of phone just yet?
magicayk said:
I just bought a new Redmi 9a with hopes to root this device. But after much time and effort in attempting to root it. I was just stuck with a boot loop. I did all the necessary requirement in order to root. Unlocked Bootloader (waited 7 days) Downloaded and Installed Updated Drivers..etc
I was successful in almost all steps of the rooting process until the one where im supposed to enter the twrp recovery mode. Is there a solution to this? or is because the twrp file is unofficial? Is there no chance to root this model of phone just yet?
Click to expand...
Click to collapse
There is actually no reason to install TWRP because nothing seems to be working after a flash, like Magisk.
I rooted mine by flashing boot.img from Tigrouzen, you can find his work in dev section. The only thing you have to do is to play with ADB commands, it should take 5 minutes at most.
Important point : I'm on MIUI 12. I really dont know if it work on the newest update.
To finish, like everytime, sorry for my scoolish English.
Today I tried to install twrp from this link
Install TWRP Recovery on OnePlus 9/9 Pro [Android 13]
In this comprehensive tutorial, we will show you the steps to install the TWRP Recovery on OnePlus 9 and OnePlus 9 Pro devices.
www.droidwin.com
I have the CN version (LE2110 ) with Oxygen 11.2.9.9.LE25AA. I was able to make it unlocked but on the step where I am in the temporary TWRP I can't now browser to any files I copied before. I have no access to the SDCARD, to flash TWRP permanent.
Is there another workaround to get TWRP running on the OP9 and root it after?
thanks
Andy
Great the twrp from op9 pro works perfecet. magisk and root as well. thanks very much for the great work.
Is there a way to disable the unlocked message which appears on the boot?
what happen if I lock it again? does TWRP and root work then?. Bit scary to try as yesterday I was hanging in a boot loop with trying twrp...)
thanks
I unlocked the bootloader with adb fastboot flashing unlock.
what do you mean by MSM?
right now I am on stock rom with all updates, TWRP with Magisk and root.
should I look the bootloader with ad fastboot flashing lock ? Do I still have TWRP and Magisk with root running after I lock the bootloader again?
thanks
Do not ever lock your bootloader with TWRP installed or root! It can and very likely will brick your device! You can only get rid of that message by going back to stock without root and without TWRP and then relock. You have been warned, do not even think about it
Hi,
ok thanks for the information, then I better leave this message,
thanks
Hi,
ok I will leave the message then.
thanks to all for quick support
It is/was "possible" to remove, but the difficulty and risk are not worth it.