Unbrick Realme 7 PRO UI 1.0 - Android10

[xxx8086]

[Unbrick Realme 7 PRO RMX2170 128GB with NFC - softbrick - bootloader unlocked UI 1.0 - Android10]

This tutorial works only in soft brick devices, for hardwre bricks only flashing with MSM Download and it I don't know how this works.

I don't know if this tutorial will works with other devices.

Try this if you don't have another way.


------------------------------------------------------------------------------------------------------------------------------------------
- I not responsable for your decision to try. -
- I'm not responsible for your device (hard brick or other things that might happen) -
------------------------------------------------------------------------------------------------------------------------------------------

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
- IMPORTANT NOTE -
- Unlocked Bootloader devices only (It's very important) Only Android 10 -
- If your device have locked bootloader only realme repair shop can help you, or flashing with MSM -
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Let's Start
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Flash the PBRP 3.0

[RECOVERY][UNOFFICIAL][RMX2170][v3.0.0] Pitch Black Recovery [10/12/20]

/* *Disclaimer * * Your warranty is now void. * * We're not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features...

forum.xda-developers.com

**** Don't change the name this image to recovery using anyway
PBRP-RMX2170-3.0.0-20210113-1340-UNOFFICIAL.img****

Download the ROM (of the official channel, I'm using RMX2170 A.41 PU) ozip format

Software Update - realme (India)

Update the latest software version on your realme phone.

www.realme.com

Download the rom OFP format
Search on google for your ROM, generally this type have 7GB

Put the rom ozip in device (external sdcard) the rom can be send to device for USB conection normally.

In PBRP goes in wipe menu and select Data (It's very important too) change partition Ext2 wait finish and select again to ext4 to remove any block on /Data partition.

Reboot menu and select reboot to recovery.

-----------------------------
Now proceed to PC

Download and opens the MCT ofp extract tool to extract the ofp to files img. (Only works on windows, in Linux use a VM)
The user nirmago alerted me over a virus in this file, thanks nirmago. Proced with caution with file. I used a new way to decrypt the ofp files

oppo_decrypt

Is free and developed in python, works very well in linux and I believe what this not have worms.

Is very simple to use
choose the OFP file
select a ouput folder to extract the files
and click on EXTRACT and wait finish.

*************
Important: After extract you will have 124 files in folder and this folder have 11.8GB.(See in baseboard of window). And the super file have 8GB. like picture below. See in pictures below, the first image to show how many files have in folder and the second picture the size of super file, see too what I have only one Super file.

Image 1 - 124 files extract and the folder with 11.8Gb. See in baseboard of window.

Image 2 - The Super file have 8Gb.

*************

Meanwhile remove the sd of your device (you don't need shutdown the device only remove)
Put the sdcard on pc and copy the folder of generate with MCT extract tool folder to root (Not move this folder to device for USB bcz some files not will be copied)

Put the ozip too (download the ozip that you had before RMX2170XX_11_A.XX)

Remove sdcard of your PC and put again on device. (Here I recommend security removal with using windows 10 or 11)

-------------------------------------
Proceed again on device
After you puted the sdcard on device goes to Mount menu in PBRP and select mount your external sd again.*
And the PBRP will reconect the sdcard.
* if you shutdown to remove the sdcard it's not necessary.

Open the folder that you copied (generated by MCT) on sdcard

Open flash menu and seek for img files above:

Boot.img
Super.img (This file is the key to recovery the system)
Recovery.img
Persist.img
Vbmeta.img
Vbmeta_system.img
Vbmeta_vendor.img

Touch on each one at a time, select the respective name on selection box and flash.

Now reboot to system, the system will crash on load, but not have bootloop, don't worry it's normal.

Reboot to bootloader again with procedure above.
*** vol+ + power at device reboot and fastly push vol- right after the device vibrate ***

In bootloader.
Now put de PBRP image again with the command above. Sometimes the device keeps restarting constantly
be quick to put the command.


fastboot flash recovery PBRP-RMX2170-3.0.0-20210113-1340-UNOFFICIAL.img


In PBRP
Wipe data, cache, dalvik
Install the ozip file that you downloaded before
and then the system will goes normal and the device is live again, [in my case the wifi not working after start system]

If you wanna the official recovery again, or have problems like wifi not works.
On PC open a terminal inside the folder created by MCT with the uncompressed OFP rom and use the commands above:

fastboot flash boot boot.img
fastboot flash recovery recovery.img

Press vol- at show up on screen reboot to recovery and will have the official recovery again

*If you have the wifi issue like me put the ozip (the same that you downloaded) on device for USB cable on download folder.
Reboot to official recovery (It not work on custom recovery)
Flash for file, search the ozip file and install normally.
It will solve the problem.

* You will not lose the IMEI

* The fingerprint sensor doesn't works. I will try to solve this issue now.

EDIT:
I used a new software to decrypt the ofp

GitHub - bkerler/oppo_decrypt: Oppo .ofp Firmware decrypter and oneplus .ops de-/encrypter

Oppo .ofp Firmware decrypter and oneplus .ops de-/encrypter - GitHub - bkerler/oppo_decrypt: Oppo .ofp Firmware decrypter and oneplus .ops de-/encrypter

github.com

Works very well in Linux, in Windows I don't know.

Open a terminal in directory os unzip the downloaded code

The command used was (in Linux):

./ofp_qc_decrypt.py <your file.ofp> <place to extract/decrypt>

And now I used OTG USB instead SdCard and works too.

OBS:
For fingerprint issue the only way yet is to restore the Persist partition backup generated by PBRP to but I haven't my persistent partition (original) to try, my realme was bricked before that I make it.


I study for a week to recovery my device, and I appreciate each one here what contribuited of a little tool or with your knowledge of the Android system.

I wish what this tutorial help you.
Good luck for all.

 

[nirmago]

"MCT ofp extract tool" is a virus

 

[xxx8086]

"MCT ofp extract tool" is a virus

You can search this tool of another site, or using another tool what extract OFP images, feel free to use since what the tool extract the files cited in tutorial. I used this tool and works fine for me.

I used the VM to extract all files bcz I use linux, but you can use VM too and after you can delete the VM.

 

[lapist]

Isn't it easier to flash those extracted IMG files directly from fastboot, rather than flashing PBRP and working with SD card? Wipe and flashing OZIP can be done thru stock recovery too.

fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash super super.img
fastboot flash boot boot.img
fastboot flash persist persist.img
fastboot flash recovery recovery.img

 

[xxx8086]

Isn't it easier to flash those extracted IMG files directly from fastboot, rather than flashing PBRP and working with SD card? Wipe and flashing OZIP can be done thru stock recovery too.

fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash super super.img
fastboot flash boot boot.img
fastboot flash persist persist.img
fastboot flash recovery recovery.img

Hello man!

Yep it is easier in theory, but doesn't works in practical.
In my case the device lose the stock recovery, I had /boot/recovery not found and the sotck recovery is dependent of super partition to works, if you flash only official recovery will have the error /boot/recovery not found. I did not have system, boot, vendor, nothing anymore in my device. When you have the total softbrick you have 2 things only the bootloader menu (if you unlocked it) and EDL, the EDL in Oppo/realme is complicated why they don't developer any tool to help us in flash for EDL, like Samsung (ODIN) Xioami (XiaomiFlashTool) or OnePlus. And to get worse the ozip and ofp only is used for Oppo/Realme any tool works.

Why not flash the partitions directally with fastboot?
The fastboot when transfering files with USB have some limitations when you work with bigger files 3GB or higher. And many limitations too with partitions, when I talk about open partitions of MB like recovery, boot, and vbmeta ok, the flash done with success, but the partition vendor and system in oppo/realme have the name Super, (\system+\vendor) and fastboot doesn't got write in this partition when your device is in softbrick, then unfortunately the last chance to flash this partition is PBRP this tool use the device like root permissions, I try with SHRP and Orange fox too, but give me errors like mount failed /system_root, and /vendor and SHRP don't flash img files.

The only way what I founded was PBRP flash the img direct to super partition, its solved my problems with don´t flah any zip file with PBRP, the super.img is the key to solve most problems.

I try flash with fastboot, and give me the error "Error: not is possible to format with RAW partitions, check the device terminal." It's happen bcz the fastboot could,t get write in partition system and vendor (or super) bcz the partitions for security are close to fastboot or adb. Was it is all what I discovered in some russian forums. And thanks to developers of PBRP and my efforts I got using my device again.

Why PBRP is good and why I used this tool?
PBRP transform ozip in zip, then he have the capacity of work with ozip very well
PBRP uncrypted my data files
Works with zip and img very easy
Your file explorer is great, better than TWRP, (and remember we don't have TWRP to Realme 7 pro).

Well is it.
I think I managed to explain everything.
Good luck!
I hope I've helped u man.

 

[xxx8086]

"MCT ofp extract tool" is a virus

Thanks man. The file really have a virus.

 

[p1w3xxx]

I did according to this guide.
But i have a few file super??
I do this .bat file (
"@Echo off
fastboot flash boot boot.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash persist persist.img
fastboot flash recovery recovery.img
fastboot flash vbmeta vbmeta.img
"
)
and working recovery and install .ozip
and now i have bootloap to fastboot.. i flash recovery and not working(stock and custom) all time restart to bootloader why???????

 

[xxx8086]

I did according to this guide.
But i have a few file super??
I do this .bat file (
"@Echo off
fastboot flash boot boot.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash persist persist.img
fastboot flash recovery recovery.img
fastboot flash vbmeta vbmeta.img
"
)
and working recovery and install .ozip
and now i have bootloap to fastboot.. i flash recovery and not working(stock and custom) all time restart to bootloader why???????

Hello man!

Something was wrong, bcz after extraction of rom you will have just one super file not all this in your image, how do you make the extraction of rom?
And after extract you have a lot files of 124 files in a folder.

Note that you have a divided super file image, with many sizes, the extraction should join all in only one, see the picture below to see, 124 files and 1 super.img file.

The problem is how you is making the extraction, if you dont use the correct tool you never extract the filer correctly, and in some point you have errors in partitions write. Try to use the tool that I used in tutorial, I search a lot and try many others ways to unbrick and only this tool solved my problem of extract.
This is your first problem.
The second problem is write the partitions, never write partitions with size up 1GB for abd or fastboot, this a limitation of reading and writing.
Ever ever EVER use the TWRP.



And you can use the MCT ofp extract tool, but this files and all that I download have a virus harder to get out the system, this works too. But is very dangerous , use this MCT ofp extract tool if you have another old machine with windows, or a pc that you can format after extraction process, bcz this virus attack the file manager of windows, if you don't have another old pc to try, I don't recommend the MCT ofp extract tool.

The files below was extract with oppo_decrypt using python 3.8 version. I use Linux system, it know what it works in windows too, but don't question me how, I don't know.

Can u see in image? 124 files, and only one super file!

Use the tool what I'd tested in this tutorial using with python. I think what you have a problem with extraction. See well you have two points very importants here:
1 The rom what you is using and the Android version what you system have before brick.
2 The super file, this file have up 8GB and have all system root separate by internal partitions. Why this? Simple, the android have a lot of partitions now, and the super rewrite then on your real locations, if you have a lot of super is wrong. I will post an image to illustrate what you see after extraction, and size of super file.

Please review your extraction. and don't use batch methods, make all changes in realme directly in TWRP, I recommend the PBRP to modify these files.

See the images what I posted now in tutorial. Remember after extract you will have 124 files in a folder with 11.8Gb of files. And a super file sizing 8Gb.


The fact that you have a loop is for your super.img the file was write incorrect or incomplete, and the system don't can charge to another partition. An analogy to you undertstanding it is:
"You try to turn on a car but the car doest have a battery doesnt matter how many times you try turn the key the car never will pass to turn on stats."

The first thing to do to fix the bootloop is write the first partition of android, the android have 2 essencial first partitions, vbmeta and recovery, and no they don't stays in same partitions, the vbmeta controls the part of turn on, and recovery controls recovery.
Then I think that your device stay in a infinite recovery/system bootloop, whats is this? if you enter in fastboot the smartphone restarts automacally, and the system is same.
Well when you writed the files you writed the wrong files this is the cause of boobtloop. Another analogy is:
"You try to turn on the car with a wrong key"

To solve it, first and very quick enter in fastboot, I don't remember if vol+ + power or vol- + power, and insert the correct vbmeta image, the device will reboot again, its normal, and after put the recovery, orangefox or PBRP to stop the fastboot bootloop, and after make the process again but now correctally, with the right files and step by step with calm, and attention. Make it quick bcz the smartphone is in infinite bootloop, then you have some seconds to do it.



Sorry for redundancy in reply but is very important to you understand all process for no have errors.

 

[p1w3xxx]

Hello man!

Something was wrong, bcz after extraction of rom you will have just one super file not all this in your image, how do you make the extraction of rom?
And after extract you have a lot files of 124 files in a folder.

Note that you have a divided super file image, with many sizes, the extraction should join all in only one, see the picture below to see, 124 files and 1 super.img file.

The problem is how you is making the extraction, if you dont use the correct tool you never extract the filer correctly, and in some point you have errors in partitions write. Try to use the tool that I used in tutorial, I search a lot and try many others ways to unbrick and only this tool solved my problem of extract.
This is your first problem.
The second problem is write the partitions, never write partitions with size up 1GB for abd or fastboot, this a limitation of reading and writing.
Ever ever EVER use the TWRP.



And you can use the MCT ofp extract tool, but this files and all that I download have a virus harder to get out the system, this works too. But is very dangerous , use this MCT ofp extract tool if you have another old machine with windows, or a pc that you can format after extraction process, bcz this virus attack the file manager of windows, if you don't have another old pc to try, I don't recommend the MCT ofp extract tool.

The files below was extract with oppo_decrypt using python 3.8 version. I use Linux system, it know what it works in windows too, but don't question me how, I don't know.

View attachment 5473915
Can u see in image? 124 files, and only one super file!

Use the tool what I'd tested in this tutorial using with python. I think what you have a problem with extraction. See well you have two points very importants here:
1 The rom what you is using and the Android version what you system have before brick.
2 The super file, this file have up 8GB and have all system root separate by internal partitions. Why this? Simple, the android have a lot of partitions now, and the super rewrite then on your real locations, if you have a lot of super is wrong. I will post an image to illustrate what you see after extraction, and size of super file.

Please review your extraction. and don't use batch methods, make all changes in realme directly in TWRP, I recommend the PBRP to modify these files.

See the images what I posted now in tutorial. Remember after extract you will have 124 files in a folder with 11.8Gb of files. And a super file sizing 8Gb.


The fact that you have a loop is for your super.img the file was write incorrect or incomplete, and the system don't can charge to another partition. An analogy to you undertstanding it is:
"You try to turn on a car but the car doest have a battery doesnt matter how many times you try turn the key the car never will pass to turn on stats."

The first thing to do to fix the bootloop is write the first partition of android, the android have 2 essencial first partitions, vbmeta and recovery, and no they don't stays in same partitions, the vbmeta controls the part of turn on, and recovery controls recovery.
Then I think that your device stay in a infinite recovery/system bootloop, whats is this? if you enter in fastboot the smartphone restarts automacally, and the system is same.
Well when you writed the files you writed the wrong files this is the cause of boobtloop. Another analogy is:
"You try to turn on the car with a wrong key"

To solve it, first and very quick enter in fastboot, I don't remember if vol+ + power or vol- + power, and insert the correct vbmeta image, the device will reboot again, its normal, and after put the recovery, orangefox or PBRP to stop the fastboot bootloop, and after make the process again but now correctally, with the right files and step by step with calm, and attention. Make it quick bcz the smartphone is in infinite bootloop, then you have some seconds to do it.



Sorry for redundancy in reply but is very important to you understand all process for no have errors.

Hello,
i do not understand.. i can't upload recovery.. in cmd everything is okey.. when i want open recovery, phone do restart bootloader.. now when i want open recovery, bad file flash or i don't know what, my phone "The current image(boot/recovery) have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it"
My question: how should i upload recovery and run it??

 

[xxx8086]

Hello,
i do not understand.. i can't upload recovery.. in cmd everything is okey.. when i want open recovery, phone do restart bootloader.. now when i want open recovery, bad file flash or i don't know what, my phone "The current image(boot/recovery) have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it"
My question: how should i upload recovery and run it??

Press vol- + power at the device turn on in fastboot after flash a good vbmeta.img, and a boot image, I recommend search it in the original rom, and after flash a recovery image (orangefox or PBRP).

But be quick before the device reboot.

fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img

 

[p1w3xxx]

Press vol- + power at the device turn on in fastboot after flash a good vbmeta.img, and a boot image, I recommend search it in the original rom, and after flash a recovery image (orangefox or PBRP).

But be quick before the device reboot.

fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img

Can u upload for me this file ? Maybe my computer has problem with this.. idk..

 

[xxx8086]

Can u upload for me this file ? Maybe my computer has problem with this.. idk..

Rename PBRP to recovery before to flash.


fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img




Link to download PBRP if necessary.

[RECOVERY][UNOFFICIAL][RMX2170][v3.0.0] Pitch Black Recovery [10/12/20]

/* *Disclaimer * * Your warranty is now void. * * We're not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features...

forum.xda-developers.com

Link to OrangeFox

Mayur - marshmello projects - Browse /RMX2170/OrangeFox at SourceForge.net

sourceforge.net

 

[p1w3xxx]

after use this command:
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot reboot recovery
my phone (attach file)
second attach file bootloader.

what i do wrong??

EDIT1:
install fox recovery and working recovery..
but when i want install custom .zip i see error(attach file 3)

 

[xxx8086]

You have an error of partitions!
Error 1 in zip describes a permission error and this error is bcz orangefox, try pbrp to try solve it. Some Orange recovery have an error about permissions in Android.

 

[p1w3xxx]

But other recovery not working..

 

[xxx8086]

Realme have a good hardware but bad softwares. All it is easilly solved if they had a tool like miflash or samaung Odin.

But...How they don't have... Let's go.

Are you tried write PBRP directally for Orangefox? Inside OrangeFox have a option to write files and partitions, but I don't remember where is it.

Note - You can't install any custom rom before you have a system working with all partitions defined and all running fine. Bcz the custom roms don't create a new partitions, only rewrite over the same system partitions. In your case you have't any system partitions.
And you

 

[p1w3xxx]

yes, tried a few recovery update for OrangeFox and nothing..

 

[p1w3xxx]

I can install a few .img, which files i need install from shapeshiftOS.zip to working my devices???

 

[p1w3xxx]

Hello man!

Something was wrong, bcz after extraction of rom you will have just one super file not all this in your image, how do you make the extraction of rom?
And after extract you have a lot files of 124 files in a folder.

Note that you have a divided super file image, with many sizes, the extraction should join all in only one, see the picture below to see, 124 files and 1 super.img file.

The problem is how you is making the extraction, if you dont use the correct tool you never extract the filer correctly, and in some point you have errors in partitions write. Try to use the tool that I used in tutorial, I search a lot and try many others ways to unbrick and only this tool solved my problem of extract.
This is your first problem.
The second problem is write the partitions, never write partitions with size up 1GB for abd or fastboot, this a limitation of reading and writing.
Ever ever EVER use the TWRP.



And you can use the MCT ofp extract tool, but this files and all that I download have a virus harder to get out the system, this works too. But is very dangerous , use this MCT ofp extract tool if you have another old machine with windows, or a pc that you can format after extraction process, bcz this virus attack the file manager of windows, if you don't have another old pc to try, I don't recommend the MCT ofp extract tool.

The files below was extract with oppo_decrypt using python 3.8 version. I use Linux system, it know what it works in windows too, but don't question me how, I don't know.

View attachment 5473915
Can u see in image? 124 files, and only one super file!

Use the tool what I'd tested in this tutorial using with python. I think what you have a problem with extraction. See well you have two points very importants here:
1 The rom what you is using and the Android version what you system have before brick.
2 The super file, this file have up 8GB and have all system root separate by internal partitions. Why this? Simple, the android have a lot of partitions now, and the super rewrite then on your real locations, if you have a lot of super is wrong. I will post an image to illustrate what you see after extraction, and size of super file.

Please review your extraction. and don't use batch methods, make all changes in realme directly in TWRP, I recommend the PBRP to modify these files.

See the images what I posted now in tutorial. Remember after extract you will have 124 files in a folder with 11.8Gb of files. And a super file sizing 8Gb.


The fact that you have a loop is for your super.img the file was write incorrect or incomplete, and the system don't can charge to another partition. An analogy to you undertstanding it is:
"You try to turn on a car but the car doest have a battery doesnt matter how many times you try turn the key the car never will pass to turn on stats."

The first thing to do to fix the bootloop is write the first partition of android, the android have 2 essencial first partitions, vbmeta and recovery, and no they don't stays in same partitions, the vbmeta controls the part of turn on, and recovery controls recovery.
Then I think that your device stay in a infinite recovery/system bootloop, whats is this? if you enter in fastboot the smartphone restarts automacally, and the system is same.
Well when you writed the files you writed the wrong files this is the cause of boobtloop. Another analogy is:
"You try to turn on the car with a wrong key"

To solve it, first and very quick enter in fastboot, I don't remember if vol+ + power or vol- + power, and insert the correct vbmeta image, the device will reboot again, its normal, and after put the recovery, orangefox or PBRP to stop the fastboot bootloop, and after make the process again but now correctally, with the right files and step by step with calm, and attention. Make it quick bcz the smartphone is in infinite bootloop, then you have some seconds to do it.



Sorry for redundancy in reply but is very important to you understand all process for no have errors.

hi, i repaired my device, but now i have other problem
don't working any bank application.. need latest version rom..
phone don't look new update.. i try change vpn (nord vpn) inida, deutchland NOTHING
i have this rom: RMX2170PU_11.A.41
i will try a few ofp file with android 11 but every have a few super.img... : attach 1
i have files: attach 2 and 3

only in rom ...A37... one files super.img but not working any bank application

 

[Sagun kumar]

Thanks man it's really helpful for me.