Database Info

[HOW-TO] Flash A/B Treble GSI ROMs without TWRP

Android devices can have different designs, so there is no generic command or set of instructions for flashing a GSI to apply to all devices. Specially for Xperias am i writing this Guides for You. So please read carefully...
1. Ensure that You have the following before You start:
Latest Fastboot Version (Or the used fastboot commands may not work)
A Method for disabling Android Verified Boot (Part of the Guide)
An unlocked Bootloader State (Official Instructions HERE)
To Start:
Download the Basic Package from Google: https://developer.android.com/topic/generic-system-image/releases
Download the AOSP Vendor Package from Sony: https://developer.sony.com/develop/open-devices/downloads/software-binaries
Open up the Zip Files and place the 3 included Images on Your fastboot destination
Boot Your Device into Fastboot:
Code:
Turn off Your Device and hold VolumeUP while connecting via USB to a PC or use ADB to reboot to fastboot
Disable the verified booting (AVB) by flashing vbmeta.img:
Code:
fastboot --disable-verification flash vbmeta vbmeta.img
Flash the Vendor to the Primary A Slot OEM:
Code:
fastboot flash oem_a nameofthesonyoemimage.img
Repeat to flash to the B Slot OEM
Code:
fastboot flash oem_b nameofthesonyoemimage.img
Flash the GSI to the Primary A Slot System:
Code:
fastboot flash system_a system.img
Repeat to flash to the B Slot System
Code:
fastboot flash system_b system.img
Wipe the user data and clear the data from other necessary partitions (for example, user data and system partitions):
Code:
fastboot -w
Reboot:
Code:
fastboot reboot
Additional:
You can use any Android 9+ GSI out of the XDA Forum here: https://forum.xda-developers.com/project-treble/trebleenabled-device-development
To get Magisk/Root; just patch Your actual Kernel with the Magisk Manager App and flash the Boot Image together with the GSI (Example below)
Patched Boot Image for Xperia 5 Users: https://forum.xda-developers.com/xp...isk-v20-3-patched-boot-image-android-t4033547

How to force unlock bootloader?
On Sony XZ3 Unlocking Bootloader is not allowed.

How To Guide [CLOSED] Deleted

Here was a Guide. Someone said people don't care about Me or My Work so...​

there is no Xperia 5 III or even the Xperia 1 III at the Sony Website

I Think you can use xperia 5 II. For xperia 5 II was Xperia 5 the right option before Xperia 5 II was listed

Not one notice that this nulls your warranty........

riahc3 said:
Not one notice that this nulls your warranty........
Click to expand...
Click to collapse
You get this Info from SONY, and it just makes Sense... You don't have trouble if You can relock Your Device. So stop spreading random Infos like "nulls Your Warranty". No One here complains about that...
{
"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"
}

Flash Firmware with newflasher ends in bootloop and "your device is corrupt"....
How can i fix it?
Edit: I Fixed it with set_active:a

which file i need from there for A 11
Generic System Image releases | Platform | Android Developers
developer.android.com

DanielMode said:
which file i need from there for A 11
Generic System Image releases | Platform | Android Developers
developer.android.com
Click to expand...
Click to collapse
Basic knowledge for all Tech around the World before You continue with anything of this:
ARM = Mobile Chips
ARM64 = Mobile Chips with 64Bit Support
X86 = Desktop Chips like from AMD or Intel
X86_64 = You guessed it? Desktop 64Bit Chips...
GMS = Google Services or Google Apps
You want to use an Xperia Mobile Device with GMS?
ARM64 GMS... No GMS no Play Store...

i don't get it where i have to look for this sin file
3. Extract the File boot_********.sin with the Unsin Exe (Drag and drop the Image on the Exe)

DanielMode said:
i don't get it where i have to look for this sin file
3. Extract the File boot_********.sin with the Unsin Exe (Drag and drop the Image on the Exe)
Click to expand...
Click to collapse
Before Modding Your Device...
Download the Firmware for Your Model with Xperifirm. It will include everything that's needed. Including Your Way back to a working Device if You screw something...
I will edit the Threads soon with a hint for this. Sorry for the trouble!

already found it at patched too but was confusing buddy
to find at the main folder of downloaded FW from XperFirm

DanielMode said:
already found it at patched too but was confusing buddy
to find at the main folder of downloaded FW from XperFirm
Click to expand...
Click to collapse
To be honest with everyone, I don't have much time usually but I do my best to help out if I can! I have many Projects running and writing Guides isn't my Top Priority. But I will rework them ones more! Thank You for pointing out that part of the Guide!

so far so good, but now i'm getting nervis
after flashing patched boot.img i'm at this step now
PS C:\platform-tools> fastboot -w
erasing 'userdata'...
OKAY [ 39.720s]
formatting 'userdata' partition...
how long it takes to formating 'userdata' ??
i wait 30min already

looks like i messed it up
PS C:\platform-tools> fastboot -w
erasing 'userdata'...
OKAY [ 38.658s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type f2fs not supported.
OKAY [ 0.009s]
erasing 'cache'...
FAILED (remote: No such partition.)
finished. total time: 38.698s
PS C:\platform-tools>
how can i revive it now.??

k started all over again and now at this step again and waiting
formatting 'userdata' partition...
will see if its done when i get up tomorrow

6 hours later and still
formatting 'userdata' partition...

erasing and/or formating isn't finishing anymore
after flashing patched boot.img

finaly i could flash latest FW with newflasher
but root wasn't there so
i flashed patched boot.img with fastboot again and i got root acces
was a bit of'n struggel but now its rooted
now i was trying die relock the bootloader...u said wipe userdata again and i did and got stuck there now
PS C:\platform-tools> fastboot -w
erasing 'userdata'...
OKAY [ 41.602s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 107809730560
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 26320735
Block groups: 804
Reserved block group size: 1024
Created filesystem with 11/6586368 inodes and 461507/26320735 blocks
sending 'userdata' (144159 KB)...
writing 'userdata'...

Can i Lock the Bootloader with Root Access?

Hi @Miustone ,
At the GSI flashing stage, I am getting an error.
fastboot flash system_a system.img
Click to expand...
Click to collapse
returns FAILED (remote: 'No such partition.')
Click to expand...
Click to collapse
I tried dropping the _a but that didn't help.
My eventual goal is to replace the MBN files following :https://forums.oneplus.com/threads/...ell-volte-and-vowifi-calling-working.1284987/
When I try to access su from adb shell, I just get a cursor that doesn't seem to execute commands. But doesn't give the error from before rooting. So I'm semi rooted?

[TOOL] Oppo/Realme Flash .OFP File on Bootloader

{
"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"
}
A tool to flash .ofp files in bootloader mode without needing MSM Tool, an alternative to official realme tool.
THE DEVICE MUST HAVE THE BOOTLOADER UNLOCKED​Features​
soft unbrick
install stock firmware
switch device region
Credits​
italorecife
bkerler oppo_decrypt
All contributors
Installation​Install​Linux (in the example below I will use ubuntu)​Install adb & fastboot and simg2img​
Code:
sudo apt-get install android-tools-adb android-tools-fastboot simg2img
Install python >=3.8, git and other deps​
Code:
sudo apt install python3 git python3-pip
Grab files​
Code:
git clone https://github.com/italorecife/OppoRealme-OFP-Flash
cd OppoRealme-OFP-Flash
pip3 install -r requirements.txt
Windows​Install the adb & fastboot drivers.
Install python + git​
Install python 3.9 and git
WIN+R
Code:
cmd
Grab files and install​
Code:
git clone https://github.com/italorecife/OppoRealme-OFP-Flash
cd OppoRealme-OFP-Flash
pip3 install -r requirements.txt
Usage​Put the .ofp file in the same folder as the program, then put your device in mode fastboot to start flash.
Run:
Code:
python3 flash.py
if you have windows OS you can run normally by double clicking, and you have linux use terminal.
DOWNLOAD
Source Code​

Searching for .ofp files
File found: RMX2151export_11_C.16_2022021018190000.ofp
Traceback (most recent call last):
File "C:\Users\cumbr\OppoRealme-OFP-Flash\flash.py", line 515, in <module>
main()
File "C:\Users\cumbr\OppoRealme-OFP-Flash\flash.py", line 316, in main
pagesize,key,iv,data=generatekey(ofpfile)
File "C:\Users\cumbr\OppoRealme-OFP-Flash\flash.py", line 109, in generatekey
pagesize,data=extract_xml(filename,key,iv)
File "C:\Users\cumbr\OppoRealme-OFP-Flash\flash.py", line 127, in extract_xml
offset=unpack("<I",rf.read(4))[0]*pagesize
struct.error: unpack requires a buffer of 4 bytes
[proceso terminado con el código 1]
Trying to flash fastboot mode, stock ROM, Realme 7.

Dude are you sure this tool works on all devices, I mean In my Realme 6 pro it seems to be doesnt work. I can help you with testing if you willing it fix it, You can PM on Teleram @neel0210
and good work btw if this works for realme the way it shows then it will be very helpful to others

Trying to flash realme 5i. It doesn't work. It says it's done flashing as soon as you press the button.
Code:
[[email protected] OppoRealme-OFP-Flash]$ python3 flash.py
Oppo/Realme Flash .OFP File on Bootloader | 1.0 (c) 2022 | Italo Almeida (@SirCDA) - GPL-3.0 License
Usage: Put the .ofp file in the same folder as the program,
then put your device in mode fastboot to start flash.
Note: if your device was not recognized in fastboot
mode by the computer, try to install the adb drivers.
=======================
Searching for .ofp files
File found: RMX2030EX_11_C.65_210223_6a6318eb.ofp
OK: Ofp Compatible
>> Can keep some partitions without changing <<
0 - Start Flash
1 - USERDATA(app, settings, internal memory) | STATUS: NEW
2 - BOOT | STATUS: NEW
3 - RECOVERY | STATUS: NEW
Choose to toggle status or start flash: 0
=================DISCLAIMER=================
We are 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 included in this ROM
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at us for messing up your device, we will laugh at you.
=================DISCLAIMER=================
1 - I understand and wish to continue
0 - Exit
Choice: 1
>> Waiting for device in fastboot mode to start <<
OK: Device unlocked
Starting process....
Note: this may take a while, it will make some popcorn for now.
Done. ofp file flashed with success!
Press Enter to continue...

worked perfectly, however due to persist.img that ofp have, acceleronometer, proximity and gyro are dead and unuseable. but hey, it recovers my phone
Device: RMX1971 (Realme 5 Pro)
UI Version: F03 (based on Android 11)

SubwayChamp said:
Searching for .ofp files
File found: RMX2151export_11_C.16_2022021018190000.ofp
Traceback (most recent call last):
File "C:\Users\cumbr\OppoRealme-OFP-Flash\flash.py", line 515, in <module>
main()
File "C:\Users\cumbr\OppoRealme-OFP-Flash\flash.py", line 316, in main
pagesize,key,iv,data=generatekey(ofpfile)
File "C:\Users\cumbr\OppoRealme-OFP-Flash\flash.py", line 109, in generatekey
pagesize,data=extract_xml(filename,key,iv)
File "C:\Users\cumbr\OppoRealme-OFP-Flash\flash.py", line 127, in extract_xml
offset=unpack("<I",rf.read(4))[0]*pagesize
struct.error: unpack requires a buffer of 4 bytes
[proceso terminado con el código 1]
Trying to flash fastboot mode, stock ROM, Realme 7.
Click to expand...
Click to collapse
try again, i have this error earlier but its fixed now

gianonceu said:
try again, i have this error earlier but its fixed now
Click to expand...
Click to collapse
I didn't try it in Linux but in Windows still the same error, my folder looks like this, if I grab the files through git, the exe file is not present, but if I download the zip, running the exe file is the same.

SubwayChamp said:
I didn't try it in Linux but in Windows still the same error, my folder looks like this, if I grab the files through git, the exe file is not present, but if I download the zip, running the exe file is the same.
View attachment 5574235
Click to expand...
Click to collapse
i also use in windows, but it flashed after 2nd time

can anyone save my phone i went to flash ofp file using this tool for my realme gt 2 pro and after the flash is complete i try to restart my phone but it's in total black screen and no responses no matter what button i try to press (fastboot and recovery mode not working too). I've try to plug in to my PC to check if there's any Qualcomm driver detected in case it's hard bricked but it's not able to detect. I've installed the Qualcomm HS-USB QDLoader 9008 Driver on my PC too. now my phone just can't power up. Can any kind soul help me out thanks

kskan24 said:
can anyone save my phone i went to flash ofp file using this tool for my realme gt 2 pro and after the flash is complete i try to restart my phone but it's in total black screen and no responses no matter what button i try to press (fastboot and recovery mode not working too). I've try to plug in to my PC to check if there's any Qualcomm driver detected in case it's hard bricked but it's not able to detect. I've installed the Qualcomm HS-USB QDLoader 9008 Driver on my PC too. now my phone just can't power up. Can any kind soul help me out thanks
Click to expand...
Click to collapse
It could be a kernel panic, so firstly, you should try the commands (no matter screen is off) either, pretending the device is in ADB or fastboot mode.
If none of them is really available, and you have the bootloader unlocked, you should try to boot to EDL using a combination button, in some devices work pressing both volume buttons at the same time you connect to PC.
If still doesn't work, then you have to make your way opening the back cover and doing a test point, to flash it through some Qualcomm flasher tool.

SubwayChamp said:
Pesquisando arquivos .ofp
Arquivo encontrado: RMX2151export_11_C.16_2022021018190000.ofp
Traceback (última chamada mais recente):
Arquivo "C:\Users\cumbr\OppoRealme-OFP-Flash\flash.py", linha 515, em <module>
a Principal()
Arquivo "C:\Users\cumbr\OppoRealme-OFP-Flash\flash.py", linha 316, em main
pagesize,key,iv,data=generatekey(ofpfile)
Arquivo "C:\Users\cumbr\OppoRealme-OFP-Flash\flash.py", linha 109, em generatekey
pagesize,data=extract_xml(nome do arquivo,chave,iv)
Arquivo "C:\Users\cumbr\OppoRealme-OFP-Flash\flash.py", linha 127, em extract_xml
offset=unpack("<I",rf.read(4))[0]*pagesize
struct.error: unpack requer um buffer de 4 bytes
[processo finalizado com o código 1]
Tentando flashear o modo fastboot, ROM de estoque, Realme 7.
Click to expand...
Click to collapse
Need 64bits pc

SrCDA said:
Need 64bits pc
Click to expand...
Click to collapse
Thanks, I already have a 64 bits PC, tried both on my dual (triple) boot, Windows 11, Zorin and Ubuntu Budgie.

Not working on realme5i. Notifies success without even flashing.
>> Waiting for device in fastboot mode to start <<
OK: Device unlocked
Starting process....
Note: this may take a while, it will make some popcorn for now.
Done. ofp file flashed with success!
Press Enter to continue...

Today I have flashed downgraded version firmware to realme 7 pro, it completed successfully. Everything works well until I decide to upgrade latest version of realme UI. I flashed new ofp file with this tool, it said successfully completed. When I restart one, it never start again. Volume Up Down, Power, none of them works. I also connect phone to pc, nothing detects on com ports. Is there any way to solve problem on home? I can not find way to enter EDL mod.
My log:
Markdown (GitHub flavored):
Searching for .ofp files
File found: RMX2170export_11_C.22_2022030317200000.ofp
OK: Ofp Compatible
Region: BD
>> Can keep some partitions without changing <<
0 - Start Flash
1 - USERDATA(app, settings, internal memory) | STATUS: NEW
2 - BOOT | STATUS: NEW
3 - RECOVERY | STATUS: NEW
Choose to toggle status or start flash: 0
=================DISCLAIMER=================
We are 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 included in this ROM
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at us for messing up your device, we will laugh at you.
=================DISCLAIMER=================
1 - I understand and wish to continue
0 - Exit
Choice: 1
>> Waiting for device in fastboot mode to start <<
OK: Device unlocked
Starting process....
Note: this may take a while, it will make some popcorn for now.
EXTRACTING: persist
FLASHING: persist
FLASH SUCCESS!
EXTRACTING: cache
FLASHING: cache
FLASH FAILED!
EXTRACTING: recovery
FLASHING: recovery
FLASH SUCCESS!
EXTRACTING: vbmeta_system
FLASHING: vbmeta_system
FLASH SUCCESS!
EXTRACTING: vbmeta_vendor
FLASHING: vbmeta_vendor
FLASH SUCCESS!
EXTRACTING: metadata
FLASHING: metadata
FLASH SUCCESS!
EXTRACTING: userdata
FLASHING: userdata
FLASH SUCCESS!
EXTRACTING: xbl
FLASHING: xbl
FLASH FAIL: Changing this partition is not allowed for security reasons (Critical Partition)
EXTRACTING: xbl_config
FLASHING: xbl_config
FLASH FAIL: Changing this partition is not allowed for security reasons (Critical Partition)
EXTRACTING: tz
FLASHING: tz
FLASH FAIL: Changing this partition is not allowed for security reasons (Critical Partition)
EXTRACTING: hyp
FLASHING: hyp
FLASH FAIL: Changing this partition is not allowed for security reasons (Critical Partition)
EXTRACTING: bluetooth
FLASHING: bluetooth
FLASH SUCCESS!
EXTRACTING: abl
FLASHING: abl
FLASH FAIL: Changing this partition is not allowed for security reasons (Critical Partition)
EXTRACTING: dsp
FLASHING: dsp
FLASH SUCCESS!
EXTRACTING: keymaster
FLASHING: keymaster
FLASH FAIL: Changing this partition is not allowed for security reasons (Critical Partition)
EXTRACTING: boot
FLASHING: boot
FLASH FAILED!
EXTRACTING: devcfg
FLASHING: devcfg
FLASH FAIL: Changing this partition is not allowed for security reasons (Critical Partition)
EXTRACTING: qupfw
FLASHING: qupfw
FLASH FAIL: Changing this partition is not allowed for security reasons (Critical Partition)
EXTRACTING: vbmeta
FLASHING: vbmeta
FLASH SUCCESS!
EXTRACTING: dtbo
FLASHING: dtbo
FLASH SUCCESS!
EXTRACTING: imagefv
FLASHING: imagefv
FLASH FAIL: Changing this partition is not allowed for security reasons (Critical Partition)
EXTRACTING: uefisecapp
FLASHING: uefisecapp
FLASH FAIL: Changing this partition is not allowed for security reasons (Critical Partition)
EXTRACTING: featenabler
FLASHING: featenabler
FLASH SUCCESS!
EXTRACTING: apdp
FLASHING: apdp
FLASH SUCCESS!
EXTRACTING: splash
FLASHING: splash
FLASH SUCCESS!
EXTRACTING: logfs
FLASHING: logfs
FLASH SUCCESS!
EXTRACTING: storsec
FLASHING: storsec
FLASH SUCCESS!
EXTRACTING: secdata
FLASHING: secdata
FLASH FAIL: Changing this partition is not allowed for security reasons (Critical Partition)
EXTRACTING: oppo_sec
FLASHING: oppo_sec
FLASH SUCCESS!
EXTRACTING: opporeserve2
FLASHING: opporeserve2
FLASH FAILED!
EXTRACTING: DRIVER
FLASHING: DRIVER
FLASH SUCCESS!
EXTRACTING: super
FLASHING: super
FLASH FAILED!
Done. ofp file flashed with success!
Press Enter to continue...

nobat said:
Today I have flashed downgraded version firmware to realme 7 pro, it completed successfully. Everything works well until I decide to upgrade latest version of realme UI. I flashed new ofp file with this tool, it said successfully completed. When I restart one, it never start again. Volume Up Down, Power, none of them works. I also connect phone to pc, nothing detects on com ports. Is there any way to solve problem on home? I can not find way to enter EDL mod.
My log:
Markdown (GitHub flavored):
Searching for .ofp files
File found: RMX2170export_11_C.22_2022030317200000.ofp
OK: Ofp Compatible
Region: BD
>> Can keep some partitions without changing <<
0 - Start Flash
1 - USERDATA(app, settings, internal memory) | STATUS: NEW
2 - BOOT | STATUS: NEW
3 - RECOVERY | STATUS: NEW
Choose to toggle status or start flash: 0
=================DISCLAIMER=================
We are 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 included in this ROM
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at us for messing up your device, we will laugh at you.
=================DISCLAIMER=================
1 - I understand and wish to continue
0 - Exit
Choice: 1
>> Waiting for device in fastboot mode to start <<
OK: Device unlocked
Starting process....
Note: this may take a while, it will make some popcorn for now.
EXTRACTING: persist
FLASHING: persist
FLASH SUCCESS!
EXTRACTING: cache
FLASHING: cache
FLASH FAILED!
EXTRACTING: recovery
FLASHING: recovery
FLASH SUCCESS!
EXTRACTING: vbmeta_system
FLASHING: vbmeta_system
FLASH SUCCESS!
EXTRACTING: vbmeta_vendor
FLASHING: vbmeta_vendor
FLASH SUCCESS!
EXTRACTING: metadata
FLASHING: metadata
FLASH SUCCESS!
EXTRACTING: userdata
FLASHING: userdata
FLASH SUCCESS!
EXTRACTING: xbl
FLASHING: xbl
FLASH FAIL: Changing this partition is not allowed for security reasons (Critical Partition)
EXTRACTING: xbl_config
FLASHING: xbl_config
FLASH FAIL: Changing this partition is not allowed for security reasons (Critical Partition)
EXTRACTING: tz
FLASHING: tz
FLASH FAIL: Changing this partition is not allowed for security reasons (Critical Partition)
EXTRACTING: hyp
FLASHING: hyp
FLASH FAIL: Changing this partition is not allowed for security reasons (Critical Partition)
EXTRACTING: bluetooth
FLASHING: bluetooth
FLASH SUCCESS!
EXTRACTING: abl
FLASHING: abl
FLASH FAIL: Changing this partition is not allowed for security reasons (Critical Partition)
EXTRACTING: dsp
FLASHING: dsp
FLASH SUCCESS!
EXTRACTING: keymaster
FLASHING: keymaster
FLASH FAIL: Changing this partition is not allowed for security reasons (Critical Partition)
EXTRACTING: boot
FLASHING: boot
FLASH FAILED!
EXTRACTING: devcfg
FLASHING: devcfg
FLASH FAIL: Changing this partition is not allowed for security reasons (Critical Partition)
EXTRACTING: qupfw
FLASHING: qupfw
FLASH FAIL: Changing this partition is not allowed for security reasons (Critical Partition)
EXTRACTING: vbmeta
FLASHING: vbmeta
FLASH SUCCESS!
EXTRACTING: dtbo
FLASHING: dtbo
FLASH SUCCESS!
EXTRACTING: imagefv
FLASHING: imagefv
FLASH FAIL: Changing this partition is not allowed for security reasons (Critical Partition)
EXTRACTING: uefisecapp
FLASHING: uefisecapp
FLASH FAIL: Changing this partition is not allowed for security reasons (Critical Partition)
EXTRACTING: featenabler
FLASHING: featenabler
FLASH SUCCESS!
EXTRACTING: apdp
FLASHING: apdp
FLASH SUCCESS!
EXTRACTING: splash
FLASHING: splash
FLASH SUCCESS!
EXTRACTING: logfs
FLASHING: logfs
FLASH SUCCESS!
EXTRACTING: storsec
FLASHING: storsec
FLASH SUCCESS!
EXTRACTING: secdata
FLASHING: secdata
FLASH FAIL: Changing this partition is not allowed for security reasons (Critical Partition)
EXTRACTING: oppo_sec
FLASHING: oppo_sec
FLASH SUCCESS!
EXTRACTING: opporeserve2
FLASHING: opporeserve2
FLASH FAILED!
EXTRACTING: DRIVER
FLASHING: DRIVER
FLASH SUCCESS!
EXTRACTING: super
FLASHING: super
FLASH FAILED!
Done. ofp file flashed with success!
Press Enter to continue..
[/QUOTE]
brother you should push the volume buttons while the devices is turned off and then plug the cable in, phone will be in edl mode but nothing will appear on screen. If this doesn't work, get the mct mtk bypass tool and select your mtk chipset on right-top, then click bypass and psuh volume buttons and plug the cable in. maybe one of these works. If still not, then you can search for libusb on google. I'll be around here
Click to expand...
Click to collapse

Does it erase all the data in phone?

I send my phone to service and they replaced motherboard, so all data removed . But I always backup my data, no problem.

nobat said:
Today I have flashed downgraded version firmware to realme 7 pro, it completed successfully. Everything works well until I decide to upgrade latest version of realme UI. I flashed new ofp file with this tool, it said successfully completed. When I restart one, it never start again. Volume Up Down, Power, none of them works. I also connect phone to pc, nothing detects on com ports. Is there any way to solve problem on home? I can not find way to enter EDL mod.
My log:
Markdown (GitHub flavored):
Searching for .ofp files
File found: RMX2170export_11_C.22_2022030317200000.ofp
OK: Ofp Compatible
Region: BD
>> Can keep some partitions without changing <<
0 - Start Flash
1 - USERDATA(app, settings, internal memory) | STATUS: NEW
2 - BOOT | STATUS: NEW
3 - RECOVERY | STATUS: NEW
Choose to toggle status or start flash: 0
=================DISCLAIMER=================
We are 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 included in this ROM
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at us for messing up your device, we will laugh at you.
=================DISCLAIMER=================
1 - I understand and wish to continue
0 - Exit
Choice: 1
>> Waiting for device in fastboot mode to start <<
OK: Device unlocked
Starting process....
Note: this may take a while, it will make some popcorn for now.
EXTRACTING: persist
FLASHING: persist
FLASH SUCCESS!
EXTRACTING: cache
FLASHING: cache
FLASH FAILED!
EXTRACTING: recovery
FLASHING: recovery
FLASH SUCCESS!
EXTRACTING: vbmeta_system
FLASHING: vbmeta_system
FLASH SUCCESS!
EXTRACTING: vbmeta_vendor
FLASHING: vbmeta_vendor
FLASH SUCCESS!
EXTRACTING: metadata
FLASHING: metadata
FLASH SUCCESS!
EXTRACTING: userdata
FLASHING: userdata
FLASH SUCCESS!
EXTRACTING: xbl
FLASHING: xbl
FLASH FAIL: Changing this partition is not allowed for security reasons (Critical Partition)
EXTRACTING: xbl_config
FLASHING: xbl_config
FLASH FAIL: Changing this partition is not allowed for security reasons (Critical Partition)
EXTRACTING: tz
FLASHING: tz
FLASH FAIL: Changing this partition is not allowed for security reasons (Critical Partition)
EXTRACTING: hyp
FLASHING: hyp
FLASH FAIL: Changing this partition is not allowed for security reasons (Critical Partition)
EXTRACTING: bluetooth
FLASHING: bluetooth
FLASH SUCCESS!
EXTRACTING: abl
FLASHING: abl
FLASH FAIL: Changing this partition is not allowed for security reasons (Critical Partition)
EXTRACTING: dsp
FLASHING: dsp
FLASH SUCCESS!
EXTRACTING: keymaster
FLASHING: keymaster
FLASH FAIL: Changing this partition is not allowed for security reasons (Critical Partition)
EXTRACTING: boot
FLASHING: boot
FLASH FAILED!
EXTRACTING: devcfg
FLASHING: devcfg
FLASH FAIL: Changing this partition is not allowed for security reasons (Critical Partition)
EXTRACTING: qupfw
FLASHING: qupfw
FLASH FAIL: Changing this partition is not allowed for security reasons (Critical Partition)
EXTRACTING: vbmeta
FLASHING: vbmeta
FLASH SUCCESS!
EXTRACTING: dtbo
FLASHING: dtbo
FLASH SUCCESS!
EXTRACTING: imagefv
FLASHING: imagefv
FLASH FAIL: Changing this partition is not allowed for security reasons (Critical Partition)
EXTRACTING: uefisecapp
FLASHING: uefisecapp
FLASH FAIL: Changing this partition is not allowed for security reasons (Critical Partition)
EXTRACTING: featenabler
FLASHING: featenabler
FLASH SUCCESS!
EXTRACTING: apdp
FLASHING: apdp
FLASH SUCCESS!
EXTRACTING: splash
FLASHING: splash
FLASH SUCCESS!
EXTRACTING: logfs
FLASHING: logfs
FLASH SUCCESS!
EXTRACTING: storsec
FLASHING: storsec
FLASH SUCCESS!
EXTRACTING: secdata
FLASHING: secdata
FLASH FAIL: Changing this partition is not allowed for security reasons (Critical Partition)
EXTRACTING: oppo_sec
FLASHING: oppo_sec
FLASH SUCCESS!
EXTRACTING: opporeserve2
FLASHING: opporeserve2
FLASH FAILED!
EXTRACTING: DRIVER
FLASHING: DRIVER
FLASH SUCCESS!
EXTRACTING: super
FLASHING: super
FLASH FAILED!
Done. ofp file flashed with success!
Press Enter to continue...
Click to expand...
Click to collapse
Does anyone know why there's that "Changing this partition is not allowed for security reasons (Critical Partition)"?

maskalicz said:
Does anyone know why there's that "Changing this partition is not allowed for security reasons (Critical Partition)"?
Click to expand...
Click to collapse
This is in locked devices.

nobat said:
Today I have flashed downgraded version firmware to realme 7 pro, it completed successfully. Everything works well until I decide to upgrade latest version of realme UI. I flashed new ofp file with this tool, it said successfully completed. When I restart one, it never start again. Volume Up Down, Power, none of them works. I also connect phone to pc, nothing detects on com ports. Is there any way to solve problem on home? I can not find way to enter EDL mod.
My log:
Markdown (GitHub flavored):
Searching for .ofp files
File found: RMX2170export_11_C.22_2022030317200000.ofp
OK: Ofp Compatible
Region: BD
>> Can keep some partitions without changing <<
0 - Start Flash
1 - USERDATA(app, settings, internal memory) | STATUS: NEW
2 - BOOT | STATUS: NEW
3 - RECOVERY | STATUS: NEW
Choose to toggle status or start flash: 0
=================DISCLAIMER=================
We are 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 included in this ROM
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at us for messing up your device, we will laugh at you.
=================DISCLAIMER=================
1 - I understand and wish to continue
0 - Exit
Choice: 1
>> Waiting for device in fastboot mode to start <<
OK: Device unlocked
Starting process....
Note: this may take a while, it will make some popcorn for now.
EXTRACTING: persist
FLASHING: persist
FLASH SUCCESS!
EXTRACTING: cache
FLASHING: cache
FLASH FAILED!
EXTRACTING: recovery
FLASHING: recovery
FLASH SUCCESS!
EXTRACTING: vbmeta_system
FLASHING: vbmeta_system
FLASH SUCCESS!
EXTRACTING: vbmeta_vendor
FLASHING: vbmeta_vendor
FLASH SUCCESS!
EXTRACTING: metadata
FLASHING: metadata
FLASH SUCCESS!
EXTRACTING: userdata
FLASHING: userdata
FLASH SUCCESS!
EXTRACTING: xbl
FLASHING: xbl
FLASH FAIL: Changing this partition is not allowed for security reasons (Critical Partition)
EXTRACTING: xbl_config
FLASHING: xbl_config
FLASH FAIL: Changing this partition is not allowed for security reasons (Critical Partition)
EXTRACTING: tz
FLASHING: tz
FLASH FAIL: Changing this partition is not allowed for security reasons (Critical Partition)
EXTRACTING: hyp
FLASHING: hyp
FLASH FAIL: Changing this partition is not allowed for security reasons (Critical Partition)
EXTRACTING: bluetooth
FLASHING: bluetooth
FLASH SUCCESS!
EXTRACTING: abl
FLASHING: abl
FLASH FAIL: Changing this partition is not allowed for security reasons (Critical Partition)
EXTRACTING: dsp
FLASHING: dsp
FLASH SUCCESS!
EXTRACTING: keymaster
FLASHING: keymaster
FLASH FAIL: Changing this partition is not allowed for security reasons (Critical Partition)
EXTRACTING: boot
FLASHING: boot
FLASH FAILED!
EXTRACTING: devcfg
FLASHING: devcfg
FLASH FAIL: Changing this partition is not allowed for security reasons (Critical Partition)
EXTRACTING: qupfw
FLASHING: qupfw
FLASH FAIL: Changing this partition is not allowed for security reasons (Critical Partition)
EXTRACTING: vbmeta
FLASHING: vbmeta
FLASH SUCCESS!
EXTRACTING: dtbo
FLASHING: dtbo
FLASH SUCCESS!
EXTRACTING: imagefv
FLASHING: imagefv
FLASH FAIL: Changing this partition is not allowed for security reasons (Critical Partition)
EXTRACTING: uefisecapp
FLASHING: uefisecapp
FLASH FAIL: Changing this partition is not allowed for security reasons (Critical Partition)
EXTRACTING: featenabler
FLASHING: featenabler
FLASH SUCCESS!
EXTRACTING: apdp
FLASHING: apdp
FLASH SUCCESS!
EXTRACTING: splash
FLASHING: splash
FLASH SUCCESS!
EXTRACTING: logfs
FLASHING: logfs
FLASH SUCCESS!
EXTRACTING: storsec
FLASHING: storsec
FLASH SUCCESS!
EXTRACTING: secdata
FLASHING: secdata
FLASH FAIL: Changing this partition is not allowed for security reasons (Critical Partition)
EXTRACTING: oppo_sec
FLASHING: oppo_sec
FLASH SUCCESS!
EXTRACTING: opporeserve2
FLASHING: opporeserve2
FLASH FAILED!
EXTRACTING: DRIVER
FLASHING: DRIVER
FLASH SUCCESS!
EXTRACTING: super
FLASHING: super
FLASH FAILED!
Done. ofp file flashed with success!
Press Enter to continue...
Click to expand...
Click to collapse
Do you have latest Realme7Pro RUI3 fw?
if yes send me

Failed to mount '/vendor'(Invalid argument)

Failed to mount '/vendor'(Invalid argument)
Failed to mount '/prodcut'(Invalid argument)
Failed to mount '/odm'(Invalid argument)
I tried to flash EU ROM from EU rom 13.04 to 13.05, using TWRP 3.4.1b.
Firstly, the zip could not be seen in internal storage, someone in XDA thread suggested I changed file system from ext 2 to ext 4 and back to ext 2, but now it failed .
The zip file is now in usb drive and I use USB-OTG to flash the zip file but the above three error appeared.
1.How can I solve it ???
2.If not possible, can I use fastboot to flash back to 13.02 with all the data, apps and pictures, video etc remain in the phone ???????
Thank you !

but why you not try flash with fb mode

Mr Hassan said:
but why you not try flash with fb mode
Click to expand...
Click to collapse
There is no fastboot mode for 13.0.5.
By the way, if I fb mode for 13.0.2, will all the pics, videos, files, and apps be deleted ?

htcandroid said:
Failed to mount '/vendor'(Invalid argument)
Failed to mount '/prdocut'(Invalid argument)
Failed to mount '/odm'(Invalid argument)
I tried to flash EU ROM from EU rom 13.04 to 13.05, using TWRP 3.4.1b.
Firstly, the zip could not be seen in internal storage, someone in XDA thread suggested I changed file system from ext 2 to ext 4 and back to ext 2, but now it failed .
The zip file is now in usb drive and I use USB-OTG to flash the zip file but the above three error appeared.
1.How can I solve it ???
2.If not possible, can I use fastboot to flash back to 13.02 with all the data, apps and pictures, video etc remain in the phone ???????
Thank you !
Click to expand...
Click to collapse
remove all lock screen security
Use OTA

NOSS8 said:
remove all lock screen security
Use OTA
Click to expand...
Click to collapse
How to remove all lock screen security ? What is OTA ? and I would like to maintain all the data, pics, videos, apps etc, will using OTA erase all these ? Thank you !

htcandroid said:
How to remove all lock screen security ? What is OTA ? and I would like to maintain all the data, pics, videos, apps etc, will using OTA erase all these ? Thank you !
Click to expand...
Click to collapse
Removed security on the lock screen if you have any.
OTA
select update file and select the rom (you must have a twrp installed).
An update does not erase the data.
{
"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"
}

NOSS8 said:
Removed security on the lock screen if you have any.
OTA
select update file and select the rom (you must have a twrp installed).
An update does not erase the data.
View attachment 5740835​
Click to expand...
Click to collapse

NOSS8 said:
Removed security on the lock screen if you have any.
OTA
select update file and select the rom (you must have a twrp installed).
An update does not erase the data.
View attachment 5740835​
Click to expand...
Click to collapse
Thank you ! But how to install OTA in my phone ? I have TWRP already installed , TWRP didn't ask me to input the security on the lockscreen.

NOSS8 said:
Removed security on the lock screen if you have any.
OTA
select update file and select the rom (you must have a twrp installed).
An update does not erase the data.
View attachment 5740835​
Click to expand...
Click to collapse
I cann't boot into my ROM now, it only goes to the recovery of TWRP !

htcandroid said:
Thank you ! But how to install OTA in my phone ? I have TWRP already installed , TWRP didn't ask me to input the security on the lockscreen.
Click to expand...
Click to collapse
You must have an update icon otherwise go to settings/my phone tap on the image where there is the 13 then the 3 dots at the top right.
Use this TWRP https://dl.akr-developers.com/?dir=skkk/TWRP/A12/v6.0_A12
If that doesn't work.
TWRP
wipe/format data type yes(data lost)
reboot twrp
Put the rom in internal storage or use OTG
flash the rom
first start takes 8/10 minutes.

htcandroid said:
I cann't boot into my ROM now, it only goes to the recovery of TWRP !
Click to expand...
Click to collapse
The post came later.
Try with the TWRP above.

Mr Hassan said:
but why you not try flash with fb mode
Click to expand...
Click to collapse
If I flash with fb mode, will all the pics, videos, files and apps installed erased ?

htcandroid said:
If I flash with fb mode, will all the pics, videos, files and apps installed erased ?
Click to expand...
Click to collapse
Nope, provided you use the correct command.

htcandroid said:
If I flash with fb mode, will all the pics, videos, files and apps installed erased ?
Click to expand...
Click to collapse
Edit flash.bat and remove fastboot -w
And flash

Mr Hassan said:
Edit flash.bat and remove fastboot -w
And flash
Click to expand...
Click to collapse
All the pics and videos, files, apps installed still there ?

Mr Hassan said:
Edit flash.bat and remove fastboot -w
And flash
Click to expand...
Click to collapse
There is not this type of command on the Xiaomi eu rom but
%fastboot% %* erase metadata
%fastboot% %* erase userdata

htcandroid said:
All the pics and videos, files, apps installed still there ?
Click to expand...
Click to collapse
Here is the Xiaomi Eu rom update script for Poco F2 you will have to check that everything corresponds to the rom you want to install and maybe modify it.
Spoiler: Command BAT
@Echo off
cd %~dp0
set fastboot=bin\windows\fastboot.exe
if not exist %fastboot% echo %fastboot% not found. & exit /B 1
echo Waiting for device...
set device=unknown
for /f "tokens=2" %%D in ('%fastboot% %* getvar product 2^>^&1 ^| findstr /l /b /c:"product:"') do set device=%%D
if "%device%" neq "lmi" if "%device%" neq "lmipro" echo This package is for "lmi" and "lmipro" devices; this is a "%device%". & exit /B 1
echo ##################################################################
echo Please wait. The device will reboot when installation is finished.
echo ##################################################################
%fastboot% %* flash cmnlib64 images\cmnlib64.mbn
%fastboot% %* flash xbl_config_5 images\xbl_config_5.elf
%fastboot% %* flash modem images\NON-HLOS.bin
%fastboot% %* flash cmnlib images\cmnlib.mbn
%fastboot% %* flash bluetooth images\BTFM.bin
%fastboot% %* flash keymaster images\km4.mbn
%fastboot% %* flash xbl_5 images\xbl_5.elf
%fastboot% %* flash tz images\tz.mbn
%fastboot% %* flash aop images\aop.mbn
%fastboot% %* flash featenabler images\featenabler.mbn
%fastboot% %* flash xbl_config_4 images\xbl_config_4.elf
%fastboot% %* flash storsec images\storsec.mbn
%fastboot% %* flash uefisecapp images\uefi_sec.mbn
%fastboot% %* flash qupfw images\qupv3fw.elf
%fastboot% %* flash abl images\abl.elf
%fastboot% %* flash dsp images\dspso.bin
%fastboot% %* flash devcfg images\devcfg.mbn
%fastboot% %* flash xbl_4 images\xbl_4.elf
%fastboot% %* flash hyp images\hyp.mbn
%fastboot% %* flash cmnlib64bak images\cmnlib64.mbn
%fastboot% %* flash cmnlibbak images\cmnlib.mbn
%fastboot% %* flash tzbak images\tz.mbn
%fastboot% %* flash aopbak images\aop.mbn
%fastboot% %* flash qupfwbak images\qupv3fw.elf
%fastboot% %* flash ablbak images\abl.elf
%fastboot% %* flash devcfgbak images\devcfg.mbn
%fastboot% %* flash hypbak images\hyp.mbn
%fastboot% %* flash boot images\boot.img
%fastboot% %* flash logo images\logo.img
%fastboot% %* flash dtbo images\dtbo.img
%fastboot% %* flash vbmeta images\vbmeta.img
%fastboot% %* flash vbmeta_system images\vbmeta_system.img
%fastboot% %* flash cust images\cust.img
%fastboot% %* flash super images\super.img
%fastboot% %* reboot

[SOLVED] GSI on BV 4900 Pro: "Cannot load Android system. Your data may be corrupt. "

tl;dr: I followed the procedure to flash Android's Generic System Image (gsi_gms_arm64-exp-TP1A.220624.014-8819323-8a77fef1) on my Blackview BV 4900 Pro, but I am stuck in a bootloop that ends with "Cannot load Android system. Your data may be corrupt."
In details:
Prep​I made sure that my phone could support GSI​
$adb shell getprop ro.treble.enabled
true
$adb shell cat /system/etc/ld.config.29.txt | grep -A 20 "\[vendor\]"
…
namespace.default.isolated = true
…
$adb shell getprop ro.product.cpu.abi
arm64-v8a
Additional Checks​
Bootloader is unlocked.
Device was launched with Android 9 or higher (it was launched with Android 10)
Android 13 GSIs was downloaded (build Build: TP1A.220624.014) was downloaded from https://developer.android.com/topic/generic-system-image/releases and checksum for ARM64+GMS was confirmed to be 8a77fef1842da4a4cff68e36802f779d65e52ae0cfce024a33901d5dc48d47d0.
The phone has Android Verified Boot (AVB):
$adb shell getprop ro.boot.veritymode
enforcing
Flashing​
I followed the official tutorial for flashing GSIs but changed a couple of things (I may have the order wrong, but I essentially did, once I was in fastboot mode
fastboot flashing unlock # To unlock bootloader
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img # Disable secure boot
fastboot reboot fastboot # Restart in fastbootd
fastboot delete-logical-partition product # I didn't have enough space for Resizing 'system' (I had FAILED (remote: 'Not enough space to resize partition'))
fastboot erase system
fastboot format:ext4 system # because when I tried to flash system.img the first time, I had "Invalid sparse file format at header magic"
fastboot flash system system.img
fastboot format:ext4 userdata
fastboot erase userdata
fastboot format:ext4 metadata
fastboot erase metadata
fastboot erase cache
But when I restart, I am always prompted with
Android Recovery
Blackview /BV4900Pro_US/BV4900Pro10/…
user/release-keys
Use volume up/down and power
Can't load Android system. Your data
may be corrupt. If you continue to get
this message, you may need to perform a
factory data reset and erase all user
data stored on this device
-------------------------
Try again
Factory data reset
-------------------------
Supported API:3
I have tried to reset factory data and to reboot, but I always have the same message…
$ adb --version
Android Debug Bridge version 1.0.41
Version 33.0.3-8952118

I just realized / remembered that this phone uses super.img instead of system.img, maybe I need to repack the system.img into a super.img, following this procedure?

tl;dr: Yes, repacking the system.img into a super.img and then flashing it was key to success.
I have essentially followed what I have described here: https://forum.xda-developers.com/t/...n-blackview-bv-4900-pro.4453955/post-87029001
Except that the three images I used were the original vendor.img, the original product.img, and
aosp_arm64-exp-TP1A.220624.014-8819323-996da050/system.img (available at
Generic System Images (GSIs) | Platform | Android Developers
developer.android.com
)
I used the command
python3 lpmakesimple.py lpbinary/binary/lpmake ./super_20220510.img 4294967296 system=system.img,vendor=./vendor.img,product=./product.img
(4294967296 being picked semi-randomly: it's a multiple of the block size (65536), less than the size of the super partition but more than the size of the three images combined + some more).
That's it: I flashed that super_20220510.img using fastboot flash super super_20220510.img and it was all good!