how to unlock bootloader realme 7 pro with realme ui 3.0 and flash the custom recovery and cuatom rom

how to unlock bootloader realme 7 pro with realme ui 3.0 and flash the custom recovery and cuatom rom - Realme 7 Pro Questions & Answers

hi guys i'm trying to unlock the bootloader and install a custom recovery and custom rom i've never done it if anyone can help me and all the necessary files thanks a lot

Well first downgrade to rui 2.0 and then using deep testing apk unlock the bootlorder and then flash custom recovery (ofox better) . Install your custom rom of your choice then ur good to go

Pranav060 said:
Bene, prima eseguire il downgrade a rui 2.0 e quindi utilizzare l'apk di deep testing per sbloccare il bootlorder e quindi eseguire il flashing del ripristino personalizzato (ofox migliore). Installa la tua rom personalizzata di tua scelta, quindi sei a posto
Click to expand...
Click to collapse
unfortunately I can't find the realme ui 2.0 downgrade file when I install what is written in the guides it tells me verification failed and I can't downgrade

andrea34334343 said:
unfortunately I can't find the realme ui 2.0 downgrade file when I install what is written in the guides it tells me verification failed and I can't downgrade
Click to expand...
Click to collapse
I have this version of realme ui 3

Hi, maybe my experience will be useful to you. I have Realme 7 pro with android 12 rmx2170_11_f.24. I was doing root to my device. What I was doing? First I downloaded deeptest rui3.apk. When I get confirmation from manufacturer I start deep test in app. Then I use ADB to send command for unlock bootloader. I completed this task. Then I downloaded and flash TWRP 3.6.2_12 (because it's can work with android 12. I tried 3.5.2_10 it's not worked). Also you need vbmeta file from rmx2170_11_f.24 to don't make your phone brick. First flash vbmeta then recovery. After recovery you need to install Magisk from TWRP to keep TWRP working after reboot. But, when I tryed install Magisk I was getting TWRP error 1: cannot write /system. How I fix it? I reboot device and install Magisk 25.2 via Android. Then you need patch boot.img from rmx2170_11_f.24 via Magisk and you get Magisk patched boot.img. Then you need flash TWRP again and reboot to recovery. In TWRP you need chose flash img button and flash Magisk patched boot.img to boot partition. Doing this you keep TWRP working and then you can flash custom ROM's to your phone.
Mod edit: 4pda link removed.
here you can get f24 ROM ( you need vbmeta and boot.img from this ROM). ROM is ~2 Gb size. Maybe you need registration on website to download. Also get TWRP 3.6.2. I'll pin deep test rui3.apk and Magisk 25.2 for you here. You can rename Magisk.zip to Magisk.apk and install via Android. I gaved you roadmap how to make this. Hope you can do it. By the way, hello from Ukraine)

s_svyrydenko said:
Hi, maybe my experience will be useful to you. I have Realme 7 pro with android 12 rmx2170_11_f.24. I was doing root to my device. What I was doing? First I downloaded deeptest rui3.apk. When I get confirmation from manufacturer I start deep test in app. Then I use ADB to send command for unlock bootloader. I completed this task. Then I downloaded and flash TWRP 3.6.2_12 (because it's can work with android 12. I tried 3.5.2_10 it's not worked). Also you need vbmeta file from rmx2170_11_f.24 to don't make your phone brick. First flash vbmeta then recovery. After recovery you need to install Magisk from TWRP to keep TWRP working after reboot. But, when I tryed install Magisk I was getting TWRP error 1: cannot write /system. How I fix it? I reboot device and install Magisk 25.2 via Android. Then you need patch boot.img from rmx2170_11_f.24 via Magisk and you get Magisk patched boot.img. Then you need flash TWRP again and reboot to recovery. In TWRP you need chose flash img button and flash Magisk patched boot.img to boot partition. Doing this you keep TWRP working and then you can flash custom ROM's to your phone.
Mod edit: 4pda link removed.
here you can get f24 ROM ( you need vbmeta and boot.img from this ROM). ROM is ~2 Gb size. Maybe you need registration on website to download. Also get TWRP 3.6.2. I'll pin deep test rui3.apk and Magisk 25.2 for you here. You can rename Magisk.zip to Magisk.apk and install via Android. I gaved you roadmap how to make this. Hope you can do it. By the way, hello from Ukraine)
View attachment 5867277 View attachment 5867279
Click to expand...
Click to collapse
Thanks for helping me out and passing me the necessary files

{Mod edit: Quoted post has been deleted. Oswald Boelcke, Senior Moderator}
You wrote in the wrong trend write in a new post

UNOFFICIAL TWRP RMX2170 TRIAL FOR ANDROID 12

give me
boot img .vbmeta and .persist img

Related

Root without custom recovery?

Hello,
i'm trying to root a Sharp B10 (SH-A01) with Magisk.
It would be nice if i could do this without unlocking because i want to keep the stock rom anyway.
First problem is that i can't find a custom recovery (TWRP, CWM) for this device from where i could install Magisk.
Then i found out that Magisk gives the possibility to root a device through the Magisk Manager App by patching the boot.img.
But the second problem is that i can't find the boot.img either. I spotted the boot partition on the device and tried to pull with adb but i would need an already rooted device to give the needed permissions.
Is there anything else I could do to get this thing rooted besides compiling my own TWRP for the device?
thanks a lot,
paul

Hello, i search the same.

paulquappe said:
Hello,
i'm trying to root a Sharp B10 (SH-A01) with Magisk.
It would be nice if i could do this without unlocking because i want to keep the stock rom anyway.
First problem is that i can't find a custom recovery (TWRP, CWM) for this device from where i could install Magisk.
Then i found out that Magisk gives the possibility to root a device through the Magisk Manager App by patching the boot.img.
But the second problem is that i can't find the boot.img either. I spotted the boot partition on the device and tried to pull with adb but i would need an already rooted device to give the needed permissions.
Is there anything else I could do to get this thing rooted besides compiling my own TWRP for the device?
thanks a lot,
paul
Click to expand...
Click to collapse
Neither Magisk nor TWRP is needed to root Android: Chainfire's SuperSu does the job. You flash its ZIP via stock recovery "adb sideload"

jwoegerbauer said:
Neither Magisk nor TWRP is needed to root Android: Chainfire's SuperSu does the job. You flash its ZIP via stock recovery "adb sideload"
Click to expand...
Click to collapse
Hi,
thanks for your answer.
I already managed to root this device. I got the boot.img with Wwr_MTK & SP flash tool (windows tools...), patched it with the magisk app and than flashed the patched boot.img

1. Unlock your bootloader enter in download mode Vol+ + Vol- + USB conected to pc (Keep in mind that by doing this you will lose your files, it is advisable to make a backup of your photos, music, etc.)
2. Once you start your cell phone install magisk manager, Choosing the boot.img file of your rom into the app (Tip: Only!!! If your model is SM-A015M Android 11 I leave you my own modified boot.img to flash:
File on MEGA
mega.nz
Otherwise, you can download the firmware (3.79 gb) and extract the boot.img from the firmware of your model SM-A015 M / F ... Android 10, Android 11... etc. And No need for pc
https://samfrew.com/model/SM-A015M/
3. The image will begin to flash
4. When it restarts you will have Root on the cell phone!
------------------------------------------------------------------------------------------------------------------------------------------------
Extra: If you need the custom recovery I give you the link with my TWRP which is installed through the Odin program on a PC (this step does not delete your files)
File on MEGA
mega.nz
Keep in mind that to install TWRP you must deactivate the DM-VERITY & FORCEENCRYPT DISABLER I leave it in a link:
Zackptg5 - Android
zackptg5.com
This is a module that can be installed via magisk, which is necessary to decrypt the system ... so once TWRP is installed, it is advisable to uninstall it via Magisk to avoid R / W errors

root Android Q on s9+

Hello, I updated to Q and can't get it rooted.
It bootlooped.
How can I root Android Q?

visit: h t t p s : / / twrp.me/site/update/2019/10/23/twrp-and-android-10.html
As, if now you cannot. For Android Q, it's still in research.
------------------------------------------------------------------------
Never tried but: ClockworkMod Recovery – a past alternative to TWRP custom recovery.
h t t p s : / / en.wikipedia.org/wiki/ClockworkMod#ClockworkMod_Recovery
Research over it & let me know if anything worked for you-!

I successfully roote Q with this ?
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389

I just flash TWRP, format and flash custom rom. Rooted.

First of all. What device do you have and what exactly have you tried? Include references.
Remember first step is to search before asking.

Guys need to re root my device on android 10 cuz i had it root under android 9 and cannot use s health
Need to root to chanfe the build prop command to use s health
Also missing the heart monitor pressure
Please help me
G965f

StonebridgeGr said:
Guys need to re root my device on android 10 cuz i had it root under android 9 and cannot use s health
Need to root to chanfe the build prop command to use s health
Also missing the heart monitor pressure
Please help me
G965f
Click to expand...
Click to collapse
I would recommend you flashing custom firmware, like the one in my signature. Everything is working, including Security Folder.

Rooting S9 +
sarjarim said:
I just flash TWRP, format and flash custom rom. Rooted.
Click to expand...
Click to collapse
Which TWRP version you used and how did you install TWRP on a non-rooted phone? Do you not have to use Magisk to root the phone first?

xectis said:
Which TWRP version you used and how did you install TWRP on a non-rooted phone? Do you not have to use Magisk to root the phone first?
Click to expand...
Click to collapse
I just used the 3.3.1.1 from the TWRP site.
Flash TWRP is to root, so I did it b4 root.
1. OEM unlock
2. Flash TWRP with odin then boot to TWRP, samsung will restore if u normal boot.
3. Backup EFS
4. Format data wipe all
5. Dm verity, search newest from dr ketan
6. Flash custom ROM.
Magisk usually comes with the custom ROM.

sarjarim said:
I just used the 3.3.1.1 from the TWRP site.
Flash TWRP is to root, so I did it b4 root.
1. OEM unlock
2. Flash TWRP with odin then boot to TWRP, samsung will restore if u normal boot.
3. Backup EFS
4. Format data wipe all
5. Dm verity, search newest from dr ketan
6. Flash custom ROM.
Magisk usually comes with the custom ROM.
Click to expand...
Click to collapse
Magic! Thanks bro.

For Android 10 U9 bootloader, is not more possible flash custom binaries... even twrp!
G965FXXU9ETF5

hi im new to this but what do you mean by Q??
i have sprint s9+ sm-g965u1, can i root my phone now ?

Devilix said:
For Android 10 U9 bootloader, is not more possible flash custom binaries... even twrp!
G965FXXU9ETF5
Click to expand...
Click to collapse
This isn't true I flashed Twrp 3.5.091 via Odin, S9+ exynos android 10, then flashed Magisk 21.4.
When I got phone it was android 10 June 2020 security update. It then updated again to 21/02/2021 ota.. I was able to flash recovery twrp and root/debloat. Only problem I did find is that I cannot flash lineage 18.1 or any custom roms.
Regards

JeyKul said:
Hello, I updated to Q and can't get it rooted.
It bootlooped.
How can I root Android Q? No root method root android Q.
Click to expand...
Click to collapse

hey ,
1.install magisk manager on your phone
2.download the firmware from samfirmware for your model of phone to pc
3.download 7zip with lz4
4. use 7zip lz4 to extract boot img from AP(firmware)
5. send the xtracted boot.img to phone sdcard and use magisk manager to patch said image .
6. send the patched img to pc and use 7zip to create archive as boot.tar file
7. one you install the firmware as normal via odin (disable auto reboot ) go back and disconnect/reconnect usb from phone so it appears as added in odin once more.
8. add the boot.tar file to AP in odin and flash the phone , reboot system and install magisk manager again , go into magisk and it will reboot again to fix the root.
there is a video somwhere on youtube showing you better than ive tried to here.
this is by far he best way as you can still take ota updates because stock recovery is still present .
regards

When will TWRP get support to Android 10?

I have flashed latest android 10 to my A3 and mistakenly uninstalled TWRP. Now i want to install twrp recovery. But everytime I flash it in partition b, it get stuck on fastboot screen.
If twrp doesn't support Android 10 then how come it supports other Android 10 based custom rom like Pixel Experience?

Because those custom ROMs use android 9 vendor, boot etc

Thanks for your helpful response
Sapper Morton said:
TWRP itself is compatible with Android 10, but not the pre-built image; the non-bootable state could be explained by the Pie Kernel inside twrp.img from official TeamWin website. Nonetheless, you can use Magisk to patch the Q boot image, or just download and flash the attached file, it's a v11.0.8.0 QFQMIXM boot image patched with the latest TWRP:
•https://app.blackhole.run/#5ae9e6c2301FpEtcnUSvhBisE7AD1JV98DHmKGDtK3WP
Click to expand...
Click to collapse
Thank you for your helpful response. If i want to flash twrp permanently, which zip file i need to flash after booting it temporarily with your attached twrp.img?

Sapper Morton said:
You must always use TWRP Installer (there's no need in specific custom ROMs, since they provide built-in custom recovery), the image I attached can only be used to install temporarily in Android 10 firmware (other than 11.0.8.0 QFQMIXM). And remember, all of this could be avoided if Xiaomi had implemented the boot command into Mi A3 bootloader:
Code:
fastboot boot image_example.img
Click to expand...
Click to collapse
so i am guessing there is no way to add the boot command to fastboot

build v11.0.11.0
Sapper Morton said:
TWRP itself is compatible with Android 10, but not the pre-built image; the non-bootable state could be explained by the Pie Kernel inside twrp.img from official TeamWin website. Nonetheless, you can use Magisk to patch the Q boot image, or just download and flash the attached file, it's a v11.0.8.0 QFQMIXM boot image patched with the latest TWRP:
•https://app.blackhole.run/#5ae9e6c2301FpEtcnUSvhBisE7AD1JV98DHmKGDtK3WP
Click to expand...
Click to collapse
Hi!
Thanks a lot, where I can find the file for the v11.0.11.0, or at least can you specify how I do this using stock boot?
Thanks! Hope to hear you back.

I booted with patched boot and finally was able to enter into TWRP recovery, but then I erased system/data/dalvik and tried to flash Pixel Experience but I am always getting error 1 when doing it. What can I do? It is something about the Android Q base? I'm now on build 11.0.11

Sapper Morton said:
You must always use TWRP Installer (there's no need in specific custom ROMs, since they provide built-in custom recovery), the image I attached can only be used to install temporarily in Android 10 firmware (other than 11.0.8.0 QFQMIXM). And remember, all of this could be avoided if Xiaomi had implemented the boot command into Mi A3 bootloader:
Code:
fastboot boot image_example.img
Click to expand...
Click to collapse
means that with this twrp it is used only to open the twrp periodically, once the custom rom is installed I install the twrp normally

Sapper Morton said:
TWRP itself is compatible with Android 10, but not the pre-built image; the non-bootable state could be explained by the Pie Kernel inside twrp.img from official TeamWin website. Nonetheless, you can use Magisk to patch the Q boot image, or just download and flash the attached file, it's a v11.0.8.0 QFQMIXM boot image patched with the latest TWRP:
•https://app.blackhole.run/#5ae9e6c2301FpEtcnUSvhBisE7AD1JV98DHmKGDtK3WP
Click to expand...
Click to collapse
What do you mean "patch the q boot image". What is that?

Sapper Morton said:
TWRP itself is compatible with Android 10, but not the pre-built image; the non-bootable state could be explained by the Pie Kernel inside twrp.img from official TeamWin website. Nonetheless, you can use Magisk to patch the Q boot image, or just download and flash the attached file, it's a v11.0.8.0 QFQMIXM boot image patched with the latest TWRP:
•https://app.blackhole.run/#5ae9e6c2301FpEtcnUSvhBisE7AD1JV98DHmKGDtK3WP
Click to expand...
Click to collapse
Thanks you saved me. I could boot into recovery with your boot.img but the encryption failed. Nevertheless I could sideload the recovery.zip to the device and install on both slots.

Redmi 8a Global a only 11.0.2.0 QCPMIXM GSI/Custom ROM still flashable?

Hi all, my first post here.
I recently bought this phone thinking it was customizable. Every tutorial I have tried has failed and required a re-flash to stock ROM using MIFlash.
I have tried custom ROMs, GSI ROMs, 64 bit, 32 bit, etc. I tried using Magisk 21.0 to root, it appears to work, but I believe the boot.img patching isn't currently working on this particular phone.
Most tutorials I have tried are very simple and use TWRP to flash the OS img file, then reboot and enjoy. Some suggest flashing vbmeta.img to prevent boot loop, but, boot loop happens anyway. I have TWRP installed and working, so far, that is all I have had success with.
Can this phone still be customized at all?
Update: I achieved root on the stock ROM. If anyone is interested I'll post the exact instructions.

stvmnn said:
Hi all, my first post here.
I recently bought this phone thinking it was customizable. Every tutorial I have tried has failed and required a re-flash to stock ROM using MIFlash.
I have tried custom ROMs, GSI ROMs, 64 bit, 32 bit, etc. I tried using Magisk 21.0 to root, it appears to work, but I believe the boot.img patching isn't currently working on this particular phone.
Most tutorials I have tried are very simple and use TWRP to flash the OS img file, then reboot and enjoy. Some suggest flashing vbmeta.img to prevent boot loop, but, boot loop happens anyway. I have TWRP installed and working, so far, that is all I have had success with.
Can this phone still be customized at all?
Update: I achieved root on the stock ROM. If anyone is interested I'll post the exact instructions.
Click to expand...
Click to collapse
Hi.
I´m interested. I´m not able to root the MI 8A MIUI 11 global 11.0.2.0 QCPMIXM. I achieved install TWRP . But I can´t install MAGISK . It don´t show me any error, but it isn´t installed. I ´ve tried many versions 20.0, 20.1, 20.2, 20.3 20.4 21.0 and 21.1. neither of them are successfull with TWRP.
Neither with magisk manager apk 7.5.1 and above. These are installed but then I download magisk 20.4 version, but this isn´t installed.
how did you it? please.

Yajirobai said:
Hi.
I´m interested. I´m not able to root the MI 8A MIUI 11 global 11.0.2.0 QCPMIXM. I achieved install TWRP . But I can´t install MAGISK . It don´t show me any error, but it isn´t installed. I ´ve tried many versions 20.0, 20.1, 20.2, 20.3 20.4 21.0 and 21.1. neither of them are successfull with TWRP.
Neither with magisk manager apk 7.5.1 and above. These are installed but then I download magisk 20.4 version, but this isn´t installed.
how did you it? please.
Click to expand...
Click to collapse
Your bootloader needs to be unlocked and USB debugging enabled first of course. TWRP Recovery should be installed.
To do this, you need the adb and fastboot binaries installed on a PC/Laptop. I use Ubuntu and installing these is trivial via apt package manager:
Debian based:
Code:
sudo apt install adb fastboot
RedHat based:
Code:
yum install adb fastboot
If you use Windows, the install and use of these binaries is a little different. I don't use Windows so you'll have to do a quick search to find out how to install and use these binaries. The commands listed below will work no matter what OS you use.
Connect your phone to your PC/Laptop via it's USB cable and reboot it to TWRP Recovery:
Power off the phone, then power on while holding the volume up button until you see the TWRP logo. Log into TWRP to decrypt.
Next, you need to pull the current boot.img from your ROM to patch it for root access:
Code:
adb shell dd if=/dev/block/by-name/boot of=/sdcard/boot.img
There should be a boot.img on your phone's internal storage, copy it to your PC/Laptop. From TWRP, reboot your phone to fastboot.
Now, we'll use this most excellent, free resource to patch the boot.img file which will give root access:
https://patcher.yaalex.xyz/
Check the 'Include Magisk' checkbox on the website before submitting image.
Important: After you upload your boot.img file to the website, be patient. This could take 10 minutes or more to complete, just wait until you get a prompt to download the patched image. You will be provided a patched_boot.img file from the website once it is finished.
Finally, all you need to do is flash the patched_boot.img to your phone:
Code:
fastboot flash boot patched_boot.img
Boot your phone to the ROM:
Code:
fastboot reboot
Install Magisk Manager if you haven't already, and enable Magisk Hide in the settings. Magisk Manager should report root access is available and SafetyNet test should pass.
I typed all this up from memory so if you run into trouble or are confused by any step, let me know and I will gladly clarify/fix the steps.
I hope this helps others achieve root on this phone. Let me know how it goes and happy de-bloating!
Rollback instructions:
If your phone fails to boot don't panic. You can restore your original boot.img if needed to regain access. Reboot your phone to fastboot:
Boot phone while holding the down volume button until you see the fastboot logo.
Next, flash the original boot.img to the boot partition:
Code:
fastboot flash boot boot.img
Now just reboot to ROM and all should be restored:
Code:
fastboot reboot

stvmnn said:
Hi all, my first post here.
I recently bought this phone thinking it was customizable. Every tutorial I have tried has failed and required a re-flash to stock ROM using MIFlash.
I have tried custom ROMs, GSI ROMs, 64 bit, 32 bit, etc. I tried using Magisk 21.0 to root, it appears to work, but I believe the boot.img patching isn't currently working on this particular phone.
Most tutorials I have tried are very simple and use TWRP to flash the OS img file, then reboot and enjoy. Some suggest flashing vbmeta.img to prevent boot loop, but, boot loop happens anyway. I have TWRP installed and working, so far, that is all I have had success with.
Can this phone still be customized at all?
Update: I achieved root on the stock ROM. If anyone is interested I'll post the exact instructions.
Click to expand...
Click to collapse
Iirc redmi 8a is an ab device, and yes this device is as customisable as any other Qualcomm. What gsi image are you flashing?

Actually he is not way off ..... i am NOT able to find a Custom Non MIUI ROM with full VoLTE support. VoLTE fix for GSI's ( if at all it worked ! ) does not work for Havoc. twrp root is all good. I want a NON MIUI ROM that can regional variants ( Europe and Asia ) and supports VoLTE

How to root realme 7 a.89

How to root realme 7 a.89....i have a.87 vbmeta img file.but my device is a.89.is this vbmeta file work on my a.89. please help

I think you can flash a.87 vbmeta in a.89 because if any version of vbmeta is in a10 or you are in a10 then you can flash it there no problem because i tested it tell me if you have problems with

hello guys, i'm having a problem here, I just installed a pixel plus ui and then installed the magisk app, then I renamed it to a zip file as mentioned in the website and went to flash it on my phone (Realme 7) after flashing successfully completed I pressed the reboot to system option, now it's stuck on the realme logo and doesn't budge anymore... I'm really worried please help me.

qeb said:
How to root realme 7 a.89....i have a.87 vbmeta img file.but my device is a.89.is this vbmeta file work on my a.89. please help
Click to expand...
Click to collapse
That vbmeta ( if it's patched ) can be used for all A10 builds. Which means u can use it with not only A87, A89. but all others RUI 1 available builds ( A83, A75....etc)

nabarun12 said:
hello guys, i'm having a problem here, I just installed a pixel plus ui and then installed the magisk app, then I renamed it to a zip file as mentioned in the website and went to flash it on my phone (Realme 7) after flashing successfully completed I pressed the reboot to system option, now it's stuck on the realme logo and doesn't budge anymore... I'm really worried please help me.
Click to expand...
Click to collapse
You can only do that with Permissive ROM builds, for Enforcing, you will need to patch boot.img manually with Magisk, then flash it into boot partition using fastboot command or custom recovery.

Better Mobile App

welcome