EDIT: included rough procedures for OEM unlocking, and updated link to recovery-verified.img (Sorry for uploading the wrong file ><)
Hi all bv9000 pro Users!
Recently I went on a journey to root this awesome rugged phone with one purspose: to remove that F*@(#&$ god awful loud annoying sound triggered by the OS when you use a camera app to take a picture + the boot startup sound (A bug blackview hasn't gotten around to fixing).
I successfully managed to port TWRP 3.1.1 from the Blackview bv8000 Pro and run it on the Blackview bv9000 Pro-f!
I've then managed to flash in Magisk to gain root access.
DISCLAIMER: I do not take responsibility for any bricked phones caused by the process, do so at your own risk (yadayadayada).
NOTE 1: Although I've got it running on the bv9000 Pro-F, this image should also work for the non-fullHD version, if someone can test this I'd be happy.
The link to the stock ROM (with the modified recovery img) can be found in the post below.
NOTE 2: No need to download anything other than what I've listed, Magisk is included in my custom recovery to circumvent the need to load the devices encrypted storage (or any other external storage) nothing stops you from mounting external usb storage.
What you'll need:
- USB Mouse (As there is no touchscreen input support, your device should have come with a usb-c otg cable so there's no problem here!)
- MediaTek SP Flash tools (I'd recommend the latest version) https://spflashtool.com/
- unlocked bootloader (You should be able to do this via the developer settings -> unlock OEM Bootloader)
EDIT: To unlock the boot loader, do the following:
1) Go to settings -> unlock OEM Bootloader (tick)
2) plug your device in (assuming you have ADB installed), use adb to access fastboot via. command prompt:
"adb reboot bootloader"
Then once the device is rebooted into fastboot mode
"fastboot oem unlock"
KEEP IN MIND THIS WILL REMOVE ANY FILES, so back them up
- I've done this with windows, but you should be able to repeat with linux no problems!
- A little patience
Pre-preparation:
First install any updates and back up your data (it's just easiest to use the google cloud backup as restoring becomes easy as pie, updating also fixes the setup wizard crashing on first setup). This is necessary because OTA updates cannot be performed with TWRP recovery, and flashing TWRP before doing OTA updates will flick the device into a recovery boot loop.
Install the SP Flash tools, and the MediaTek VCOM Drivers
(I won't link the specifics here, a quick google search should be able to help you, just note you might need to disable driver signature enforcement)
Two options for flashing:
1)
My Full Stock ROM already pre-prepared for flashing:
Patched ROM
No need for extra prep here! you should just be able to load the scatter
2)
My custom patched TWRP stock rom: recovery-verified.img
Blackiew's stock rom: stock rom
- Download the stock rom, backup the recovery-verified.img in the R06 folder, and then replace it with my custom patched TWRP stock rom (file name should be the same).
- Run "CheckSum_Gen.exe" once you replaced the file, it will generate the necessary checksum to allow SP flash tools to successfully flash recovery.
Once you've done with the pre-prep, switch off your device, take a deep breath and you're ready to go!
Steps!
1) Load up SP Flash Tools, select the android scatter file you've downloaded in the R06 folder
2) Select Download Only (I MEAN IT, FORMATTING WILL REMOVE YOUR IMEI AND RENDER THE PHONE USELESS)
3) Deselect everything but recovery (You only want to flash this)
4) Hit download
https://pasteboard.co/HkufwZZ.png
5) Hold volume up + power and plug in your phone, keep the volume up button held
6) very quickly the flash should be complete, and you should be greeted with a big ol' green tick to verify
https://pasteboard.co/HkuiTBB.png
7) Once you're done, remove your USB cable, plug in the OTG then we proceed to flash magisk
8) Hold power + volume up until you reach the bootloader, then use the menu to select recovery
9) You *should* be greeted with the TWRP recovery screen (Which is great success! )
DON'T PANIC IF YOU CANNOT USE THE TOUCH SCREEN, the kernel I've patched is missing this, seems the driver is different between touch screens, just plug in your OTG mouse to continue from here!
10) Use your mouse to first hit cancel, we don't need to decrypt the user data storage.
11) But oh no! it's all in Russian (no problem, Next step sorts that)
12) Use your mouse to navigate the menus as shown here to change to English! (or your preferred language) Change Language
13) Click install, then navigate up folder levels until you are in the root directory
14) scroll down and click on Magisk.zip, install it, allow it to install any apps as system apps (because this will then install to the system image, not the userdata)
15) reboot the phone (if it hasn't rebooted already)
16) You should be able to boot into your usual phones OS, if you don't see Magisk listed in your phone apps, just download it from here:
Magisk Manager
17) Congratulations! You should have complete root access :laugh::laugh::laugh:
Feel free to express your thanks, or list any problems you have, but keep in mind my studies take all my life, so I may not be able to help with all the problems you have
Congrats! Would it work on the BV9000 HD version?
Hi!
From what I've seen they both run the helio p25 chip
(Just a difference in RAM size) so it should.
You're more than welcome to try.
Just keep a backup of the original ROMs recovery. If something goes wrong during the boot to recovery you can easily re flash
hi i tried both optinos but they didn't work for me
I tried the first and the second options and it was showed me same error:
ERROR: STATUS INSUFFICIENT_BUFFER(0XC0010007)
I tried download only, format all and download, if i install original ROM its installing without problems!
In settings-> developer options -> OEM unlocking is enabled
can someone give me tips if I'm doing something wrong. thanks
My phone is Blackview BV9000PRO-F
Hello,
i have the blackview 9000 pro Hd (not full hd)
i first tried your prepared patched rom = not working (get erorrers in step 6)
then i chose step 2 and i was thinking to use the stock rom from the NOT full hd rom
now i get a green screen from the flashing: but after rebooting in recovery nothing happens, just normal reboot then
perhaps this is not so clair for me:
- Download the stock rom, backup the recovery-verified.img in the R06 folder, and then replace it with my custom patched TWRP stock rom (file name should be the same).
- Run "CheckSum_Gen.exe" once you replaced the file, it will generate the necessary checksum to allow SP flash tools to successfully flash recovery.
the file name you posted here " My custom patched TWRP stock rom: recovery-verified.img" is ramdisk-recovery.img
i replaced the ramdisk-recovery.img... it is not clair need to replace recovery-verified.img to?
>I tried the first and the second options and it was >showed me same error:
>ERROR: STATUS INSUFFICIENT_BUFFER(0XC0010007)
> tried download only, format all and download, if i install >original ROM its installing without problems!
>can someone give me tips if I'm doing something wrong. >thanks
>My phone is Blackview BV9000PRO-F
Hi, you need to unlock the OEM bootloader, if this is still locked it will prevent the flashing of custom ROMS.
I might've missed this step, will update post as necessary.
>
dingsje said:
Hello,
>i have the blackview 9000 pro Hd (not full hd)
>i first tried your prepared patched rom = not working >(get erorrers in step 6)
>then i chose step 2 and i was thinking to use the stock >rom from the NOT full hd rom
>now i get a green screen from the flashing: but after >rebooting in recovery nothing happens, just normal >reboot then
>perhaps this is not so clair for me:
>- Download the stock rom, backup the recovery->verified.img in the R06 folder, and then replace it with >my custom patched TWRP stock rom (file name should >be the same).
>- Run "CheckSum_Gen.exe" once you replaced the file, >it will generate the necessary checksum to allow SP >flash tools to successfully flash recovery.
>the file name you posted here " My custom patched >TWRP stock rom: recovery-verified.img" is ramdisk->recovery.img
>i replaced the ramdisk-recovery.img... it is not clair >need to replace recovery-verified.img to?
Click to expand...
Click to collapse
Hi,
I've uploaded the wrong file, the uploaded file should be recovery-verified.img.
I'm uploading a new file and will correct the link now,
Please accept my apologies ><
hyperlethalvector92 said:
>I tried the first and the second options and it was >showed me same error:
>ERROR: STATUS INSUFFICIENT_BUFFER(0XC0010007)
> tried download only, format all and download, if i install >original ROM its installing without problems!
>can someone give me tips if I'm doing something wrong. >thanks
>My phone is Blackview BV9000PRO-F
Hi, you need to unlock the OEM bootloader, if this is still locked it will prevent the flashing of custom ROMS.
I might've missed this step, will update post as necessary.
Click to expand...
Click to collapse
I already did this step:
Enable developer options-> OEM unlocking is enabled
Is that enough for this MTK phone to be unlocked the bootloader ?
And tried the both options but the results are same.
I have been unlocking bootloaders on many phones but first time MTK phones. If i try with adb commands it recognize when is in the android with command adb devices and show my device but if I try reboot bootloader and check in device manager in windows its show its connected and drives are correct but if i try to show the devices, it doesn't show any device connected
Hi,
You need to install fastboot drivers once it's in bootloader mode,
then use fastboot, not adb.
"fastboot oem unlock"
Then follow instructions.
simply doing settings -> oem unlock won't unlock the bootloader, it allows you to do so later via. fastboot
Check the original post, I've added the extra instructions sorry about the confusion!
Thanks a lot. I finally succeeded to unlock the bootloader and root my phone and install the magisk.. I did without use your rom just I unlocked the bootloader and install your twrp file and after in the recovery mode i format the data and istall magic and i still have the last updated android.
I hope this it ill help to other people. Cheers
zlatkomas said:
Thanks a lot. I finally succeeded to unlock the bootloader and root my phone and install the magisk.. I did without use your rom just I unlocked the bootloader and install your twrp file and after in the recovery mode i format the data and istall magic and i still have the last updated android.
I hope this it ill help to other people. Cheers
Click to expand...
Click to collapse
I'm glad ^______^
Enjoy your rooted phone
I used this video to root my bv9000 pro hd
much easier than this above, i think it works to on bv9000 pro fhd
https://www.youtube.com/watch?v=c48ISLPjn4Q
Congratulations .... I need a tip,.
And, brother, thank you very much. Worked perfectly.
But first I would like to get you a tip ..
One of the main reasons I have done all this complicated process was to be able to disable the crap of the loud music that plays when the device is started.
I want complete silence at startup.
How do I disable this ****?
Code for Huawei mobile Wi-Fi e5577s-321
Pls help unlock my Huawei mobile Wi-Fi e5577s-321
Imei
860782038163889
TWRP looping after OTA update
My dear, the procedure worked very well, until an OTA update was downloaded.
You are now looping on TWRP. How do I get out of this?
:crying:
help!
i missed to run wireless software update,so ROM clashed.
How can i re-install custom ROM?
mackie_ma said:
help!
i missed to run wireless software update,so ROM clashed.
How can i re-install custom ROM?
Click to expand...
Click to collapse
Hi guys, lemme apologize for disappearing, life and whatnot!
For those stuck in a TWRP boot loop, simply restoring the original recovery then restarting the phone will be enough to fix the problem.
(Actually you really don't need TWRP after the phone is rooted, maybe I should update the guide?)
Many Thanks
First off, thank you for your hard work. Loved the "**** it we have an OTG cable let's use it" haha. It works fine for me.
Second, do you happen to know if someone has ported Oreo on our bv9000 ? Or do you know of any ETA ?
Thanks again,
Cheers
Anyone tried on the BV9000 Pro? Don't think mine is 'F' OR 'Fhd'.... I must have first model brought out...
Ugh.. Windows and Drivers?!?!
I keep getting Driver not Recognized in Windows 7 Pro X86.
I installed the latest vcom/usb drivers, in legacy also. No Go.
I installed from several other sources the drivers, including the Automatic Mediatek driver install. No Go.
So if anyone has a tip for me, please let me know because once more Windows is proving itself ridiculous. I can't even get to the storage of my phone. Did something change with a Windows Update that it's not allowed anymore?
I put my BV9000 Pro in OEM Unlock and USB Debugging. I backupped everything. My phone is ready for it. It's as ready as Amy having coitus with Sheldon for the first time.
[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.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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.
"MCT ofp extract tool" is a virus
nirmago said:
"MCT ofp extract tool" is a virus
Click to expand...
Click to collapse
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.
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.
Code:
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
lapist said:
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.
Code:
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
Click to expand...
Click to collapse
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.
nirmago said:
"MCT ofp extract tool" is a virus
Click to expand...
Click to collapse
Thanks man. The file really have a virus.
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???????
p1w3xxx said:
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???????
Click to expand...
Click to collapse
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.
xxx8086 said:
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.
Click to expand...
Click to collapse
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??
p1w3xxx said:
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??
Click to expand...
Click to collapse
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
xxx8086 said:
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
Click to expand...
Click to collapse
Can u upload for me this file ? Maybe my computer has problem with this.. idk..
p1w3xxx said:
Can u upload for me this file ? Maybe my computer has problem with this.. idk..
Click to expand...
Click to collapse
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
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)
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.
But other recovery not working..
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
yes, tried a few recovery update for OrangeFox and nothing..
I can install a few .img, which files i need install from shapeshiftOS.zip to working my devices???
xxx8086 said:
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.
Click to expand...
Click to collapse
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
Thanks man it's really helpful for me.
Last night I do have a problem with the custom rom that I have installed, because of the battery problem keeps on dropping, so I decided to go back to the official stock rom which is for global however after flashing the fastboot rom via Miflash Tool, I have a welcome message that says Find Device storage corrupted. Your device is unsafe now. I thought that I just need to activate this to the device admin, after a reboot I tried to check it out if this message if this message will still pop up, and it keeps on popping up. I have flashed the rom again and it keeps on happening.
Things that I have Tried:
So I tried to check for other ways that I could get rid of this but this doesnt work on the terminal via TWRP. "
[GUIDE] How to fix "Find Device storage corrupted. Your device is unsafe now".
[GUIDE] How to fix "Find Device storage corrupted. Your device is unsafe now". How to fix "Find Device storage corrupted. Your device is unsafe now" ? (At your own risk... I'm not responsible for damage or brick) Required : - Be rooted and...
forum.xda-developers.com
".
The one that works:
Things that you needed:
1. Download Mi Flash Tool(https://www.xiaomiflash.com/)
2. Minimal ADB and Fastboot
3. 7zip or BreeZip
4. TWRP A12(
TWRP A12.rar
drive.google.com
) if you are using other MIUI and devices and want to check it this will work then just use your twrp that is recommended for your mui device.
5. Global Rom (https://xiaomifirmwareupdater.com/miui/alioth/stable/V12.5.6.0.RKHMIXM/)
warning: make sure that you are using the right rom for your device, my device that I am using is a global variant so I need to flash a global version, if you are using other MIUI device and want to check it out just download the miui that works for you must be on a later update of the rom if the latest current rom that you are working on right now didnt work.
Steps to follow.
1. Extract the Rom which you have downloaded using the 7zip or BreeZip, so for me I extracted the version 12.5.6.0 take note that this is not the latest rom but for this to work we need to be in a later update this rom is an android version 11.
2. after extracting the fastboot rom file type TGZ you will notice that the one that you extracted is on a TAR file type, and you need to extract the TAR file type for you to have the folder "alioth_global_images_V12.5.6.0.RKHMIXM_20220210.0000.00_11.0_global_62b4f5d6ca"
3. Using the Mi Flash Tool, just pick the clean all and start the flashing.
4. After flashing the rom set up the phone but do not update it.
5. On your extracted folder for the rom go to the folder that says images and look for 'persist" this is an img file. copy the persist img file and paste it on your Internal memory of your phone.
6. Turn off your phone and go to fastboot by pressing the volume down as well as the power button. You will notice that the fastboot logo is the older version since we are using an older rom.
7. Extract the TWRP A12 and you should have the disc recovery image of it, copy and paste it on your Minimal ADB and Fastboot folder and rename it "recovery".
8. While you are on the Minimal ADB Fastboot folder make sure that your phone is plug in to the usb port on your computer, click the cmd here on the Minimal ADB and Fastboot Folder and you should able to run the cmd.
9. run the following commands:
fastboot devices (then press the enter)
warning: make sure that the fastboot devices is able to see your device.
after seeing the device run this command:
fastboot boot recovery.img (then press enter)
the device should boot to the twrp if its on chinese look for settings and set it to english. we are not flashing the twrp we are just going to use it temporarily thats why we are only going to boot it to twrp recovery.
10. On your twrp, go to install, click the install image and look for your persist.img that we have copied earlier to your internal memory
you should find it on the sdcard folder. just flash and you will see that you have successfully flashed the persist image and then just reboot your phone.
After rebooting your phone you will notice that the "Find Device storage corrupted. Your device is unsafe now." will not prompt. Since I already have the current fastboot rom I have tried to flash the current fastboot rom and locked my device and fixed the problem permanently without any problem.
You wrote too much for something that could be written in a few sentences. And why would anyone downgrade an android or flash a clean fastboot ROM? (Android or MIUI version doesn't matter)
Summary guide:
1. Download the fastboot ROM from here and extract the "persist.img" image or dump the "persistbak" partition from your device and rename this file to "persist.img"
2. Put persist.img into your device's internal memory and go to TWRP
3. In TWRP, go to: Install> select install image> select file persist.img> select "Persist" partition
4. Restart the device, it should work fine
uvzen said:
You wrote too much for something that could be written in a few sentences. And why would anyone downgrade an android or flash a clean fastboot ROM? (Android or MIUI version doesn't matter)
Summary guide:
1. Download the fastboot ROM from here and extract the "persist.img" image or dump the "persistbak" partition from your device and rename this file to "persist.img"
2. Put persist.img into your device's internal memory and go to TWRP
3. In TWRP, go to: Install> select install image> select file persist.img> select "Persist" partition
4. Restart the device, it should work fine
Click to expand...
Click to collapse
Wrote it down for the newbies that doesnt know how to fix anyway thanks for the summary. I have to downgraded it because the latest current rom doesnt work give me "invalid sparse file format at header magic" error as I flash the persist.img file, via twrp.
mizuhored said:
Wrote it down for the newbies that doesnt know how to fix anyway thanks for the summary. I have to downgraded it because the latest current rom doesnt work give me "invalid sparse file format at header magic" error as I flash the persist.img file, via twrp.
Click to expand...
Click to collapse
If you are using TWRP from Nebrassy then use skkk TWRP or OrangeFox. Flashing persist should work fine on both recoveries (I did it myself recently).
uvzen said:
If you are using TWRP from Nebrassy then use skkk TWRP or OrangeFox. Flashing persist should work fine on both recoveries (I did it myself recently).
Click to expand...
Click to collapse
Thats great but this is the one that works for me anyways. At least we have found out the things that we needed in order for it to be fixed. Just sharing my ideas and how did I fixed the problem myself. Thanks for sharing of your ideas. Hoping that we could share our ideas to others as well. Been on a nightmare last night cant sleep because of this problem. Trying to figure out what to do since using the cmds via terminal on twrp doesnt work for me. Need to downgrade for me to fix it.
mizuhored said:
Thats great but this is the one that works for me anyways. At least we have found out the things that we needed in order for it to be fixed. Just sharing my ideas and how did I fixed the problem myself. Thanks for sharing of your ideas. Hoping that we could share our ideas to others as well. Been on a nightmare last night cant sleep because of this problem. Trying to figure out what to do since using the cmds via terminal on twrp doesnt work for me. Need to downgrade for me to fix it.
Click to expand...
Click to collapse
Could you please confirm if flashing persist.img doesn't mess up with sensor like fingerprint, l1, compass etc..? I have seen other forums talking about possibility of losing these in case perist is flashed from rom. I have this message for some time now, but all other sensors work fine, even l1 certification and saftynet. Thanks in advance.