Does anyone know a way of erasing the sdcard (external storage) on the Nexus S using fastboot commands? i ask because i'm creating a cmd file that will return my phone back to stock using factory images and then relock the bootloader, the only problem is that the sdcard doesn't get erased when relocking the bootloader, so is there a fastboot command to erase the sdcard?
You can lock and unlock bootloader again. Then relock.
So lock->unlock->relock
Sent from my Nexus S using Tapatalk
Thanks for the quick reply, i had thought of that but i would prefer to just erase the sdcard (also for future reference), or, perform a relock that gives the same results as the unlock, eg: wipe sdcard, which would be better, my cmd entries are below.
fastboot flash bootloader bootloader-crespo-i9020xxkl1.img
fastboot reboot-bootloader
timeout /t 5 > nul
fastboot flash radio radio-crespo-i9020xxki1.img
fastboot reboot-bootloader
timeout /t 5 > nul
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
fastboot reboot
The only thing missing is a command to erase the sdcard.
d.chatten said:
Thanks for the quick reply, i had thought of that but i would prefer to just erase the sdcard (also for future reference), or, perform a relock that gives the same results as the unlock, eg: wipe sdcard, which would be better, my cmd entries are below.
fastboot flash bootloader bootloader-crespo-i9020xxkl1.img
fastboot reboot-bootloader
timeout /t 5 > nul
fastboot flash radio radio-crespo-i9020xxki1.img
fastboot reboot-bootloader
timeout /t 5 > nul
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
fastboot reboot
The only thing missing is a command to erase the sdcard.
Click to expand...
Click to collapse
Try fastboot erase sdcard?
Sent from my ice cream powered Nexus S
DarkhShadow said:
Try fastboot erase sdcard?
Click to expand...
Click to collapse
Thanks for the suggestion, but i have tried this and it doesn't seem to work with the Nexus S.
Anyone...?
d.chatten said:
Thanks for the suggestion, but i have tried this and it doesn't seem to work with the Nexus S.
Click to expand...
Click to collapse
You could try fastboot erase /dev/block/vold/179:3
Or boot it up and delete it via android
If they don't work don't lame me I'm a noob xD
Sent from my ARCHOS 80G9 using XDA Premium HD app
I think i'll just use the lock>unlock>lock method till i find something a bit more concrete, thanks for the suggestions though, much appreciated.
where can i find all this files?
d.chatten said:
Thanks for the quick reply, i had thought of that but i would prefer to just erase the sdcard (also for future reference), or, perform a relock that gives the same results as the unlock, eg: wipe sdcard, which would be better, my cmd entries are below.
fastboot flash bootloader bootloader-crespo-i9020xxkl1.img
fastboot reboot-bootloader
timeout /t 5 > nul
fastboot flash radio radio-crespo-i9020xxki1.img
fastboot reboot-bootloader
timeout /t 5 > nul
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
fastboot reboot
The only thing missing is a command to erase the sdcard.
Click to expand...
Click to collapse
where can i find all this files?
You can download the factory images from here > https://developers.google.com/android/nexus/images, you'll need WinRAR, 7zip or similar installed to enable you to extract the files.
if i recall correctly, the command is "fastboot erase media"
TheMachoMidget said:
if i recall correctly, the command is "fastboot erase media"
Click to expand...
Click to collapse
Found this
Delete existing apps on Android SD
adb shell rm -r /system/sd/app
adb shell rm -r /system/sd/appprivate
Through Terminal Partition SD card
It will erase everything on your SD card
$ su
# cd /data
# wget http://64.105.21.209/bin/lib/droid/sdsplit4
# chmod 555 sdsplit
# /data/sdsplit -fs *size* (add -nc to the end for JFv1.5ADP)
Hello everyone,
I've been running into a strange issue since the october OTA update: the WiFi on my Mi A1 won't work anymore.
The toggle switch is set to "enabled", I can't switch it to "enabled" because it goes straight back to "disabled". What's weird is the phone seems
to search for available WiFi networks, at least according to the small progress bar at the top, even though it says WiFi is "disabled".
Anything I could try to fix this issue? I've tried reflashing the stock boot image, that doesn't change anything. WiFi seems to be broken
on both A and B partitions.
I'm attaching a screenshot, not sure if this helps.
Hey,
you need to reflash the modem and other partitions, had the same problem as you have.
Download newest image:
http://en.miui.com/download-333.html
Use this commands as a batch next to the fastboot.exe, change the image path to your folder with replacing. It won't wipe/delete anything!
fastboot flash modem_a C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\modem.img || @ECHO "Flash modem_a error" && exit /B 1
fastboot flash modem_b C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\modem.img || @ECHO "Flash modem_b error" && exit /B 1
fastboot flash sbl1 C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\sbl1.img || @ECHO "Flash sbl1 error" && exit /B 1
fastboot flash sbl1bak C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\sbl1.img || @ECHO "Flash sbl1bak error" && exit /B 1
fastboot flash rpm C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\rpm.img || @ECHO "Flash rpm error" && exit /B 1
fastboot flash rpmbak C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\rpm.img || @ECHO "Flash rpmbak error" && exit /B 1
fastboot flash tz C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\tz.img || @ECHO "Flash tz error" && exit /B 1
fastboot flash tzbak C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\tz.img || @ECHO "Flash tzbak error" && exit /B 1
fastboot flash devcfg C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\devcfg.img || @ECHO "Flash devcfg error" && exit /B 1
fastboot flash devcfgbak C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\devcfg.img || @ECHO "Flash devcfgbak error" && exit /B 1
fastboot flash dsp C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\adspso.bin || @ECHO "Flash dsp error" && exit /B 1
fastboot flash sec C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\sec.dat || @ECHO "Flash sec error" && exit /B 1
fastboot flash splash C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\splash.img || @ECHO "Flash splash error" && exit /B 1
fastboot flash misc C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\misc.img || @ECHO "Flash misc error" & exit /B 1
fastboot flash aboot C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\emmc_appsboot.mbn || @ECHO "Flash aboot error" && exit /B 1
fastboot flash abootbak C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\emmc_appsboot.mbn || @ECHO "Flash abootbak error" && exit /B 1
fastboot flash boot_a C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\boot.img || @ECHO "Flash boot_a error" && exit /B 1
fastboot flash boot_b C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\boot.img || @ECHO "Flash boot_b error" && exit /B 1
fastboot flash system_a C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\system.img || @ECHO "Flash system_a error" && exit /B 1
fastboot flash system_b C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\system.img || @ECHO "Flash system_a error" && exit /B 1
fastboot flash lksecapp C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\lksecapp.img || @ECHO "Flash lksecapp error" && exit /B 1
fastboot flash lksecappbak C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\lksecapp.img || @ECHO "Flash lksecappbak error" && exit /B 1
fastboot flash cmnlib C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\cmnlib.img || @ECHO "Flash cmnlib error" && exit /B 1
fastboot flash cmnlibbak C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\cmnlib.img || @ECHO "Flash cmnlibbak error" && exit /B 1
fastboot flash cmnlib64 C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\cmnlib64.img || @ECHO "Flash cmnlib64 error" && exit /B 1
fastboot flash cmnlib64bak C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\cmnlib64.img || @ECHO "Flash cmnlib64bak error" && exit /B 1
fastboot flash keymaster C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\keymaster.img || @ECHO "Flash keymaster error" && exit /B 1
fastboot flash keymasterbak C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\keymaster.img || @ECHO "Flash keymasterbak error" && exit /B 1
Aside from reflashing, have you tried a factory reset?
skroder said:
Aside from reflashing, have you tried a factory reset?
Click to expand...
Click to collapse
I really wanted to avoid a factory reset. Using t000x's method seems to have worked but I still have a weird issue with the phone: OTA updates on partition A seem to disappear (after a few reboots, partition A always goes back to august update.) I'll investigate further and will create another topic if needed.
Thanks agoin for your help. :good:
Cheers.
mrsmn said:
I really wanted to avoid a factory reset. Using t000x's method seems to have worked but I still have a weird issue with the phone: OTA updates on partition A seem to disappear (after a few reboots, partition A always goes back to august update.) I'll investigate further and will create another topic if needed.
Thanks agoin for your help. :good:
Cheers.
Click to expand...
Click to collapse
Glad I could help you! Maybe you need to set the active partition to B (or maybe A?).
Try set_active within fastboot.
i was having the same problem. but my wifi and hotspot could not be used after flashing twrp 3.1.1 and my phone is on bootloop cycle. i've try reflashing stock rom but still no luck
Lordzarilla said:
i was having the same problem. but my wifi and hotspot could not be used after flashing twrp 3.1.1 and my phone is on bootloop cycle. i've try reflashing stock rom but still no luck
Click to expand...
Click to collapse
Did you follow the instructions posted above?
yes i have
mrsmn said:
Did you follow the instructions posted above?
Click to expand...
Click to collapse
i've already tested to set active both a and b. still no luck. i've also tried to flash boot.img to both partition. still no luck. i don't know what went wrong. do i have to flash stock recovery? do someone has stock recovery for Mi A1?
mrsmn said:
Did you follow the instructions posted above?
Click to expand...
Click to collapse
my Mi A1 is still in bootloop after all these fastboot command. can't get past the android one logo and keep on restarting on and on. is this have to do with me unlocking my phone BL?
I was stock on same problem and I solved it
1. Flash lastest rom with mi flash tool
2. Copy persist.img at the lastest rom
3. Fastboot erase persist
4.. Fastboot flash persist persist.img
5. Reboot
I am not good at English Sorry
t000x said:
Hey,
you need to reflash the modem and other partitions, had the same problem as you have.
Download newest image:
http://en.miui.com/download-333.html
Use this commands as a batch next to the fastboot.exe, change the image path to your folder with replacing. It won't wipe/delete anything!
...
Click to expand...
Click to collapse
much thx.. it worked...
WiFI issues
vaibhav011286 said:
much thx.. it worked...
Click to expand...
Click to collapse
Hi
please can this solve wifi problem on Mi A1 with Oreo update 8.0.0
thank you
WIFI issues
t000x said:
Hey,
you need to reflash the modem and other partitions, had the same problem as you have.
Download newest image:
http://en.miui.com/download-333.html
Hi
please can this solve wifi problem on Mi A1 with Oreo update 8.0.0
thank you
Click to expand...
Click to collapse
Omarod said:
t000x said:
Hey,
you need to reflash the modem and other partitions, had the same problem as you have.
Download newest image:
http://en.miui.com/download-333.html
Hi
please can this solve wifi problem on Mi A1 with Oreo update 8.0.0
thank you
Click to expand...
Click to collapse
Hey, it should help. If after flashing it is not working, try a wipe.
Click to expand...
Click to collapse
wifi issues
t000x said:
Omarod said:
Hey, it should help. If after flashing it is not working, try a wipe.
Click to expand...
Click to collapse
i reflash everything but still same problem ??
Click to expand...
Click to collapse
Omarod said:
t000x said:
i reflash everything but still same problem ??
Click to expand...
Click to collapse
i still have the same problem :c
Click to expand...
Click to collapse
Nautilus99 said:
Omarod said:
i still have the same problem :c
Click to expand...
Click to collapse
Try to reflash firmware with the official tool. If that's not working, most likely your hardware is faulty.
Click to expand...
Click to collapse
t000x said:
Nautilus99 said:
Try to reflash firmware with the official tool. If that's not working, most likely your hardware is faulty.
Click to expand...
Click to collapse
Hello, i had custom rom Pixel experience, but after now i came back to stock, i cant use wifi.. it just says disabled, and cannot connect to any wifi networks. Is this solution what you described above with reflash?
Click to expand...
Click to collapse
saon371 said:
t000x said:
Hello, i had custom rom Pixel experience, but after now i came back to stock, i cant use wifi.. it just says disabled, and cannot connect to any wifi networks. Is this solution what you described above with reflash?
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a1/how-to/easiest-quickest-to-fix-wifi-custom-t3779040
Right like next to this thread. Nice research lol.
Click to expand...
Click to collapse
This worked for me, using the April 2018 update with Magisk, and my WiFi works now. Thank you so much for this.
So looks like I hard bricked the poco X3 NFC within thirty days of buying it (Xiaomi refused to repair, paid or otherwise).
Unlocked the bootloader using their official tool, no problems (except for the huge wait times).
Used the Xiaomi Unlock tool version 2.0 to install TWRP and then flashed Corvus 14.5 Mutate through it (I usually do it all manually but this app said it could handle the flash safely). Stuck in a bootloop. Looked up online what to do and someone said wipe the data partition (have a feeling this is what did it). Now the phone is completely dead. No LED blink when powering on or charging. My PC now reads it as a Qualcomm HS-USB QDLoader 9008.
It's a goner, isn't it?
Welcoming all advice/condolences.
condolences...
BjornBear said:
So looks like I hard bricked the poco X3 NFC within thirty days of buying it (Xiaomi refused to repair, paid or otherwise).
Unlocked the bootloader using their official tool, no problems (except for the huge wait times).
Used the Xiaomi Unlock tool version 2.0 to install TWRP and then flashed Corvus 14.5 Mutate through it (I usually do it all manually but this app said it could handle the flash safely). Stuck in a bootloop. Looked up online what to do and someone said wipe the data partition (have a feeling this is what did it). Now the phone is completely dead. No LED blink when powering on or charging. My PC now reads it as a Qualcomm HS-USB QDLoader 9008.
It's a goner, isn't it?
Welcoming all advice/condolences.
Click to expand...
Click to collapse
You need EDL Flash
It's all good. If it's already being recognised by your PC just flash the correct stock ROM using Mi Flash Tool ad you're golden. Just make sure it's the tight one fore your device and you've checked "clean all" option in Mi Flash Tool.
BTW if you end up in a boot loop after flashing a ROM again make sure you do "FORMAT DATA" not "wipe data". It is not the same thing!
I think if your pc can detect the device, you are still kinda safe. Download Mi flash tool and flash the official stock rom. Here is the link to both, hope it works for you.
https://c.mi.com/oc/miuidownload/detail?device=1900385
https://c.mi.com/oc/miuidownload/detail?guide=2
Best of luck.
there should be a speedrun for bricking your device
also how did you wipe your data partition? fastboot erase userdata ??
try restoring it via fastboot format:ext4 userdata
ramnoob said:
I think if your pc can detect the device, you are still kinda safe. Download Mi flash tool and flash the official stock rom. Here is the link to both, hope it works for you.
https://c.mi.com/oc/miuidownload/detail?device=1900385
https://c.mi.com/oc/miuidownload/detail?guide=2
Best of luck.
Click to expand...
Click to collapse
Thanks everyone for your help so far. I was considering paying for an EDL flash service (someone I know had theirs done successfully through an account on Telegram) Unfortunately the Mi Flash Tool doesn't seem to be working. I can't even get up to the bit where it would ask for an authorised Xiaomi EDL account. After clicking flash it just says 'timeout maybe the device was unplugged' or something like that and returns this string of code (taken from flash.bat)
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *karna" || fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *surya" || echo Missmatching image and device
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *karna" || fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *surya" || exit /B 1
set CURRENT_ANTI_VER=2
for /f "tokens=2 delims=: " %%i in ('fastboot %* getvar anti 2^>^&1 ^| findstr /r /c:"anti:"') do (set version=%%i)
if [%version%] EQU [] set version=0
if %version% GTR %CURRENT_ANTI_VER% (
echo current device antirollback version is greater than this package
exit /B 1
)
fastboot %* flash xbl %~dp0images\xbl.elf || @echo "Flash xbl error" && exit /B 1
fastboot %* flash xblbak %~dp0images\xbl.elf || @echo "Flash xblbak error" && exit /B 1
fastboot %* flash xbl_config %~dp0images\xbl_config.elf || @echo "Flash xbl_config error" && exit /B 1
fastboot %* flash xbl_configbak %~dp0images\xbl_config.elf || @echo "Flash xbl_config error" && exit /B 1
fastboot %* flash imagefv %~dp0images\imagefv.elf || @echo "Flash imagefv error" && exit /B 1
fastboot %* flash imagefvbak %~dp0images\imagefv.elf || @echo "Flash imagefvbak error" && exit /B 1
fastboot %* flash aop %~dp0images\aop.mbn || @echo "Flash aop error" && exit /B 1
fastboot %* flash aopbak %~dp0images\aop.mbn || @echo "Flash aopbak error" && exit /B 1
fastboot %* flash uefisecapp %~dp0images\uefi_sec.mbn || @echo "Flash uefisecapp error" && exit /B 1
fastboot %* flash uefisecappbak %~dp0images\uefi_sec.mbn || @echo "Flash uefisecappbak error" && exit /B 1
fastboot %* flash qupfw %~dp0images\qupv3fw.elf || @echo "Flash qupfw error" && exit /B 1
fastboot %* flash metadata %~dp0images\metadata.img || @echo "Flash xbl error" && exit /B 1
fastboot %* flash tz %~dp0images\tz.mbn || @echo "Flash tz error" && exit /B 1
fastboot %* flash tzbak %~dp0images\tz.mbn || @echo "Flash tzbak error" && exit /B 1
fastboot %* flash hyp %~dp0images\hyp.mbn || @echo "Flash hyp error" && exit /B 1
fastboot %* flash hypbak %~dp0images\hyp.mbn || @echo "Flash hypbak error" && exit /B 1
fastboot %* flash keymaster %~dp0images\km4.mbn || @echo "Flash keymaster error" && exit /B 1
fastboot %* flash keymasterbak %~dp0images\km4.mbn || @echo "Flash keymasterbak error" && exit /B 1
fastboot %* flash cmnlib %~dp0images\cmnlib.mbn || @echo "Flash cmnlib error" && exit /B 1
fastboot %* flash cmnlibbak %~dp0images\cmnlib.mbn || @echo "Flash cmnlib error" && exit /B 1
fastboot %* flash cmnlib64 %~dp0images\cmnlib64.mbn || @echo "Flash cmnlib64 error" && exit /B 1
fastboot %* flash cmnlib64bak %~dp0images\cmnlib64.mbn || @echo "Flash cmnlib64 error" && exit /B 1
fastboot %* flash modem %~dp0images\NON-HLOS.bin || @echo "Flash modem error" && exit /B 1
fastboot %* flash dsp %~dp0images\dspso.bin || @echo "Flash dsp error" && exit /B 1
fastboot %* flash bluetooth %~dp0images\BTFM.bin || @echo "Flash bluetooth error" && exit /B 1
fastboot %* flash storsec %~dp0images\storsec.mbn || @echo "Flash storsec error" && exit /B 1
fastboot %* flash devcfg %~dp0images\devcfg.mbn || @echo "Flash devcfg error" && exit /B 1
fastboot %* flash abl %~dp0images\abl.elf || @echo "Flash abl error" && exit /B 1
fastboot %* flash ablbak %~dp0images\abl.elf || @echo "Flash ablbak error" && exit /B 1
fastboot %* flash dtbo %~dp0images\dtbo.img || @echo "Flash dtbo error" && exit /B 1
fastboot %* flash vbmeta %~dp0images\vbmeta.img || @echo "Flash vbmeta error" && exit /B 1
fastboot %* flash boot %~dp0images\boot.img || @echo "Flash boot error" && exit /B 1
fastboot %* flash recovery %~dp0images\recovery.img || @echo "Flash recovery error" && exit /B 1
fastboot %* flash super %~dp0images\super.img || @echo "Flash super error" && exit /B 1
fastboot %* flash userdata %~dp0images\userdata.img || @echo "Flash userdata error" && exit /B 1
fastboot %* flash vbmeta_system %~dp0images\vbmeta_system.img || @echo "Flash vbmeta_system error" && exit /B 1
fastboot %* flash cust %~dp0images\cust.img || @echo "Flash cust error" && exit /B 1
fastboot %* flash ffu %~dp0images\ffu.img || @echo "Flash ffu error" && exit /B 1
fastboot %* flash cache %~dp0images\cache.img || @echo "Flash cache error" && exit /B 1
fastboot %* erase misc
fastboot %* erase apdp
fastboot %* erase multiimgoem
fastboot %* reboot
These parts worry me:
"product: *karna" || fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *surya" || echo Missmatching image and device"
and
"current device antirollback version is greater than this package"
Does anyone know what else I could try? I found this (https://romprovider.com/test-point-poco-x3-reboot-edl-mod/) but it's using software I'm unsure of. Is this my only option now do you think?
Try to move the MiFlash folder to the root directory (i.e. C:/MiFlash) and put the ROM inside the MiFlash folder and proceed this way. You never know ......
Can you get into fastboot or twrp ? Then it can easily be restored
Okay so I might get into trouble for this but SkaboXD was right, the only thing that would fix my phone was an EDL flash. I tried everything and this was the only thing that worked. I found a YouTuber by the name of Munchy (who basically spends his time telling people how to avoid tech scams) who endorsed a guy operating exclusively on Telegram on his video.
Seeing as so many people are being scammed for EDL accounts at the moment because real ones are like gold dust I think I'll take the risk of the banhammer to recommend (the guy the YouTuber endorsed) Angeluss69 on Telegram. I paid in Bitcoin because I wanted to stay anonymous but he accepts PayPal business and I don't know maybe he accepts more transfer types, didn't ask. I won't quote his prices just in case that isn't allowed but it's not so bad and he's running what seems like an honest business so I say it's worth it when compared to the expensive brick I had an hour ago. He's Spanish and his English isn't so good so he uses the Telegram in-built translator but it works well enough and he's quite friendly.
Sidenote: Apparently the reason why Xiaomi refused to fix my phone is because most staff don't have Authorised EDL accounts in their repair centers. This kind of makes sense. Gotta admit though, I'm curious as to how the heck he got that account. I'm putting up pictures as proof. Do your worst, Admins.
{
"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 UNLOCKEDFeatures
soft unbrick
install stock firmware
switch device region
Credits
italorecife
bkerler oppo_decrypt
All contributors
InstallationInstallLinux (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
WindowsInstall 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
UsagePut 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