the system has been destroyed - Redmi Note 8 Questions & Answers

Plz help me what can i do? i dont flash properly my system has been destroyed. i did evething for solved this problem . now i have no option to solve this problem . now what can i do? any one Help me?
i am attached some photos
my image file : ginkgo_in_global_images_V11.0.3.0.PCOINXM
{
"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"
}
_20200214.0000.00_9.0_in_8e42c719e

Flash vbmeta file or try to move files to root directory.

shovan.cc said:
Plz help me what can i do? i dont flash properly my system has been destroyed. i did evething for solved this problem . now i have no option to solve this problem . now what can i do? any one Help me?
i am attached some photos
my image file : ginkgo_in_global_images_V11.0.3.0.PCOINXM
_20200214.0000.00_9.0_in_8e42c719e
Click to expand...
Click to collapse
in fastboot rom there must be a file vbmeta.img....
download latest platform tools first.
extract the plaform tools zip...copy vbmeta.img in this folder,open cmd in this folder path and flash vbmeta with phone in fastboot mode by this command
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
after this flash recovery.

if you solve the problem, here the vbmeta: https://mega.nz/#!bUwliDDS!PNCWo68avE9GsyK4JeJgV1zoVIiejh0-gIs1X6MCEPk

Mi Flash should be able to restore your phone to 100% stock, including boot and vbmeta - it could be that the directory is too long. Try placing the fastboot file in your root folder (C:/) and direct Mi Flash Tool towards that.
System has been destroyed should only really show up when you try flashing a ROM without a dummy vbmeta.img

Thx.
CommieColin said:
Mi Flash should be able to restore your phone to 100% stock, including boot and vbmeta - it could be that the directory is too long. Try placing the fastboot file in your root folder (C:/) and direct Mi Flash Tool towards that.
System has been destroyed should only really show up when you try flashing a ROM without a dummy vbmeta.img
Click to expand...
Click to collapse
Thanks For Your Suggestion.. & i Am done This flash Properly.

thank you
the_weird_aquarian said:
in fastboot rom there must be a file vbmeta.img....
download latest platform tools first.
extract the plaform tools zip...copy vbmeta.img in this folder,open cmd in this folder path and flash vbmeta with phone in fastboot mode by this command
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
after this flash recovery.
Click to expand...
Click to collapse
thank you you saved me

the_weird_aquarian said:
in fastboot rom there must be a file vbmeta.img....
download latest platform tools first.
extract the plaform tools zip...copy vbmeta.img in this folder,open cmd in this folder path and flash vbmeta with phone in fastboot mode by this command
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
after this flash recovery.
Click to expand...
Click to collapse
I am trying my best to perform this action and i cant

Janelas said:
I am trying my best to perform this action and i cant
Click to expand...
Click to collapse
All commands worked but stil stuck on fastboot

Janelas said:
All commands worked but stil stuck on fastboot
Click to expand...
Click to collapse
sorry for the late reply...after vbmeta is successful, did you flash recovery.img?? if after flashing recovery it doesn't enter recovery mode, press vol up + power button then check.

Related

[Q] Bricked my nexus - Fastboot still almost working

I Think my device is lost. It´s locked in boot of my Gummynex rom.
I´m not allowed to flash anything else, it´s like my filesystem is broken.
I have attached som screenshots of the error´s i get in galaxy nexus toolkit 5.6
{
"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"
}
I Have also tryed with Odin, but i cant seem to get odin to connect with the phone in fastboot.
If i try to go into recoverymode i get the android man lying on his back with and Red triangle inside.
Hope someone have any idea of what i should try next.
on the phone itself, can you get to bootloader?
Tomcat27 said:
I Think my device is lost. It´s locked in boot of my Gummynex rom.
I´m not allowed to flash anything else, it´s like my filesystem is broken.
I have attached som screenshots of the error´s i get in galaxy nexus toolkit 5.6
I Have also tryed with Odin, but i cant seem to get odin to connect with the phone in fastboot.
If i try to go into recoverymode i get the android man lying on his back with and Red triangle inside.
Hope someone have any idea of what i should try next.
Click to expand...
Click to collapse
Try using fastboot commands to flash the stock img files instead of the toolkit.
jhernand1102 said:
Try using fastboot commands to flash the stock img files instead of the toolkit.
Click to expand...
Click to collapse
But when i download the files from Google´s homepage there is only 1 file.
Shouldn´t it be enough ?
It´s the yakju-imm76d-factory-c6e807a1.tar file for my phone.
Tomcat27 said:
But when i download the files from Google´s homepage there is only 1 file.
Shouldn´t it be enough ?
It´s the yakju-imm76d-factory-c6e807a1.tar file for my phone.
Click to expand...
Click to collapse
extract the files.
But when i extract the files with winrar, i still only get 1 file ?
Tomcat27 said:
But when i extract the files with winrar, i still only get 1 file ?
Click to expand...
Click to collapse
Extract it again.
Sent from my Galaxy Nexus using xda premium
I´ve extracted the files again. now i have 6 img files.
boot
bootloader
radio
recovery
system
userdata
Flashed all the files to the phone, each time i get an error like before, but i can see in the fast boot screen that baseband versions ect. changes.
But unfortunatly the phone still won´t boot.
I have locked it again, and will take it to the store for repair if someone don´t have some good ideas
Thank you in advance
unlock the bootloader ( fastboot oem unlock )
5) Open up Command Prompt or Terminal, navigate to the folder you've extracted it all too and enter the following commands waiting for each to finish
Windows
fastboot-windows flash bootloader bootloader-maguro-primekk15.img
fastboot-windows reboot-bootloader
fastboot-windows flash radio radio-maguro-i9250xxkk6.img
fastboot-windows reboot-bootloader
fastboot-windows -w update image-yakju-icl53f.zip
Linux
./fastboot-linux flash bootloader bootloader-maguro-primekk15.img
./fastboot-linux reboot-bootloader
./fastboot-linux flash radio radio-maguro-i9250xxkk6.img
./fastboot-linux reboot-bootloader
./fastboot-linux -w update image-yakju-icl53f.zip
OSX
./fastboot-mac flash bootloader bootloader-maguro-primekk15.img
./fastboot-mac reboot-bootloader
./fastboot-mac flash radio radio-maguro-i9250xxkk6.img
./fastboot-mac reboot-bootloader
./fastboot-mac -w update image-yakju-icl53f.zip
6) The last step is to lock the bootloader. Restart the phone into the bootloader
7) Open CMD in the location of Superboot and type:
fastboot-windows oem lock
Help Needed
Guys,
I need any help possible although I fear I may be beyond recovery. Basically my Galaxy Nexus is bricked, I had been running 4.0.4 (IMM76D) on it. The phone is rooted and unlocked.
When switching the phone on, all I get is Google and the unlocked keypad. Will not progress further. I can boot into fastboot mode, and sometimes into recovery however although I have files showing on the SD, when I choose them I get a message declaring the path empty.
My main issue is that the handset is not recognised by my computer (running windows 7 and also since yesterday a dual boot of Ubuntu). This results in my Nexus toolkit and the AdamOutler tool being of no use as they do not recognize the device.
Any help/advice will be greatly appreciated as I'm at my wits end

back to stock sense

i am tired to flash this rom
still show me error
i have s-off and unlocked bootloader
any help ?
{
"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"
}
nassimxmax said:
i am tired to flash this rom
still show me error
i have s-off and unlocked bootloader
any help ?
Click to expand...
Click to collapse
umm that doesnt really help, whats your fastboot getvar all, whats rom did you try to flash, your flash commands are all wrong but require the other info in order to see what your doing.
i am running GPe and want to back to stock
i trying to flash this rom https://www.androidfilehost.com/?fid=95916177934518148
but he give me error
i have s-off and unlocked bootloader
nassimxmax said:
i am running GPe and want to back to stock
i trying to flash this rom https://www.androidfilehost.com/?fid=95916177934518148
but he give me error
i have s-off and unlocked bootloader
Click to expand...
Click to collapse
ok when you have downloaded the file, put it in the same folder as ADB and fastboot files and rename it to RUU for ease
you will need to use the HTC_fastboot.exe to flash it, normal fastboot wont flash Lollipop RUU's, get the htc one from here and put in the same folder as your RUU.zip and other adb and fastboot files: https://www.androidfilehost.com/?fid=95916177934550031
then do htese commands:
fastboot oem rebootRUU (phone screen should go black with sliver HTC logo)
htc_fastboot flash zip RUU.zip (YOU MUST USE THE HTC_FASTBOOT to flash the zip, the normal fastboot wont work, now leave it alone to do its thing, takes about 10 mins, no need to issue this command twice as its automatic with the htc_fastboot)
now make sure when its finished and you have a command prompt and that it says successful at the end and OKAY
if so then type fastboot reboot-bootloader
now fastboot reboot
Seanie280672 said:
ok when you have downloaded the file, put it in the same folder as ADB and fastboot files and rename it to RUU for ease
you will need to use the HTC_fastboot.exe to flash it, normal fastboot wont flash Lollipop RUU's, get the htc one from here and put in the same folder as your RUU.zip and other adb and fastboot files: https://www.androidfilehost.com/?fid=95916177934550031
then do htese commands:
fastboot oem rebootRUU (phone screen should go black with sliver HTC logo)
htc_fastboot flash zip RUU.zip (YOU MUST USE THE HTC_FASTBOOT to flash the zip, the normal fastboot wont work, now leave it alone to do its thing, takes about 10 mins, no need to issue this command twice as its automatic with the htc_fastboot)
now make sure when its finished and you have a command prompt and that it says successful at the end and OKAY
if so then type fastboot reboot-bootloader
now fastboot reboot
Click to expand...
Click to collapse
thank you so much i trying to find that htc fastboot but i didin't find it
i understand now i will try
now it work fine
just waiting ^^

[Tutorial] Splash Image Maker

Big thanks and credits to search0123 from 4pda.ru
(original post: MOD EDIT: link removed)
1. Download Mi_A2_Lite_Splash_Maker.zip and unzip the archive file
2. Put your 5 custom graphics files in the *png folder, but preserve their names (01.png, 02.png, 03.png etc...and keep their original resolutions)
Original splash.img includes those pictures:
{
"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"
}
3. Run the file CREATE_SPLASH.bat and after the script is done you will get splash.img in the Output folder.
4. Flash new splash.img via the fastboot command
Code:
fastboot flash splash splash.img
Chrono Leggionaire said:
Big thanks and credits to search0123 from 4pda.ru
(original post: MOD EDIT: link removed)
1. Download Mi_A2_Lite_Splash_Maker.zip and unzip the archive file
2. Put your 5 custom graphics files in the *png folder, but preserve their names (01.png, 02.png, 03.png etc...and keep their original resolutions)
Original splash.img includes those pictures:
3. Run the file CREATE_SPLASH.bat and after the script is done you will get splash.img in the Output folder.
4. Flash new splash.img via the fastboot command
Code:
fastboot flash splash splash.img
Click to expand...
Click to collapse
WORKS !! THANKS search0123 :fingers-crossed: :good:
anyone have cool splash img? do share ty
Dark images included work well with paranoid boot animation, thanks! No more blinding mornings...
Good to know... Custom splash does not affect OTA to 10.0.7.0.
mi logo
I don't have a Windows but python should be cross-platform...
Because I have a Mac, I had to run xcode-select --install to get zlib in place for Pillow.
I had to pip2.7 install Pillow to get the PIL library that the script wanted.
Then I could run python2.7 splash_gen.py and it produced a splash.img for me.
no more full screen unlocked bootloader warning. thanks
I conpreased the image file as a zip when I go to twrp which should I select boot or something else
rob420p said:
I conpreased the image file as a zip when I go to twrp which should I select boot or something else
Click to expand...
Click to collapse
This is a bootloader splash. Flash from fastboot.
fastboot flash splash splash.img
a1291762 said:
This is a bootloader splash. Flash from fastboot.
fastboot flash splash splash.img
Click to expand...
Click to collapse
I understand that but I can't for the life of me get this to work on fastboot idk what I'm doing wrong I know how to use fast boot so I'm loat
rob420p said:
I understand that but I can't for the life of me get this to work on fastboot idk what I'm doing wrong I know how to use fast boot so I'm loat
Click to expand...
Click to collapse
Do you have an unlocked bootloader?
What errors do you get from fastboot?
a1291762 said:
Do you have an unlocked bootloader?
What errors do you get from fastboot?
Click to expand...
Click to collapse
Unlocked custom rom when I type the commands its always saying no file
rob420p said:
Unlocked custom rom when I type the commands its always saying no file
Click to expand...
Click to collapse
So you don't have a splash.img then?
a1291762 said:
So you don't have a splash.img then?
Click to expand...
Click to collapse
I've downloaded them from this pafe
rob420p said:
I've downloaded them from this pafe
Click to expand...
Click to collapse
Is your phone in fastboot mode? Showing the rabbit with the blowtorch?
Do you have the fastboot program on your computer?
a1291762 said:
Is your phone in fastboot mode? Showing the rabbit with the blowtorch?
Do you have the fastboot program on your computer?
Click to expand...
Click to collapse
Yes I know all that.I got that
Ok, let's try something else. Here's what I see when I flash.
Code:
[Thirteen:~/Files/Mi A2 Lite/Splash/images] link$ adb reboot bootloader
[Thirteen:~/Files/Mi A2 Lite/Splash/images] link$ fastboot getvar current-slot
current-slot: a
Finished. Total time: 0.003s
[Thirteen:~/Files/Mi A2 Lite/Splash/images] link$ fastboot flash splash splash_stock_dark.img
Sending 'splash' (1460 KB) OKAY [ 0.080s]
Writing 'splash' OKAY [ 0.032s]
Finished. Total time: 0.159s
[Thirteen:~/Files/Mi A2 Lite/Splash/images] link$ fastboot reboot
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.001s
Can you please include what you see when you flash the splash image?
Chrono Leggionaire said:
Big thanks and credits to search0123 from 4pda.ru
(original post: MOD EDIT: link removed
1. Download Mi_A2_Lite_Splash_Maker.zip and unzip the archive file
2. Put your 5 custom graphics files in the *png folder, but preserve their names (01.png, 02.png, 03.png etc...and keep their original resolutions)
Original splash.img includes those pictures:
3. Run the file CREATE_SPLASH.bat and after the script is done you will get splash.img in the Output folder.
4. Flash new splash.img via the fastboot command
Click to expand...
Click to collapse
Hi great Dev can you explain me how to remove the " unlocked bootloader warn" whit your app? Sorry for my English thanks for your time and your work
rob420p said:
I've downloaded them from this pafe
Click to expand...
Click to collapse
taht is the correct comman as he said
fastboot flash splash splash.img

[UNOFFICIAL][RECOVERY] OrangeFox Recovery R11.1_5-A12 (Support Android 12+)

OrangeFox Recovery Project​
{
"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"
}
Downloads OrangeFox-R11.1_5-A12​
Installation
Code:
fastboot flash boot OrangeFox-R11.1_5_A12-Unofficial-avicii.img
fastboot reboot recovery
After booting into the recovery, flash OrangeFox-R11.1_5_A12-Unofficial-avicii.zip, it will reboot.
what is inside:
Support Android 12
Magisk-25.2
adb sideload
FDE decryption
or brick
Good luck.
Give feedback on the work or not work of this tool!
Version Information
Status: Beta
Current Beta Version: R11.1_5-A12
Release Date: 22-october-2022
Spoiler: for Donate:
BTC Wallet :
bc1qepm8lmd6228dhdpn9e0rjkplpq7yftdhkxywcp
Dkpost3 said:
OrangeFox Recovery Project​View attachment 5670603​Downloads OrangeFox-R12.1​
Installation
Code:
fastboot boot OrangeFox-R11.1_A12-vndk30-avicii.img
After booting into the recovery, flash OrangeFox-R11.1_3_A12-vndk30-avicii.zip, it will reboot.
what is inside:
Support Android 12
Magisk-25.2
adb sideload
FDE decryption
or brick
Good luck.
Version Information
Status: Beta
Current Beta Version: R11.1_A12
Release Date: 28-jule-2022
Spoiler: for Donate:
BTC Wallet :
bc1qepm8lmd6228dhdpn9e0rjkplpq7yftdhkxywcp
Click to expand...
Click to collapse
I flashed the recovery but the device is stuck in the bootloader
Anto426 said:
I flashed the recovery but the device is stuck in the bootloader
Click to expand...
Click to collapse
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot flash vbmeta_system --disable-verity --disable-verification vbmeta_system.img
What are the instructions simple fastboot or do we need to flash this vbmeta & vbmeta_system? Also
lordfinix said:
What are the instructions simple fastboot or do we need to flash this vbmeta & vbmeta_system? Also
Click to expand...
Click to collapse
if the first option doesn't work, add
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot flash vbmeta_system --disable-verity --disable-verification vbmeta_system.img
can i flash it on a12 custom rom?
lordfinix said:
can i flash it on a12 custom rom?
Click to expand...
Click to collapse
Yes
stuck at bootloader after normal flashing does, flashing vbmeta and vbmeta.system remove enc or wt does it do i dont want to format internal ?
lordfinix said:
stuck at bootloader after normal flashing does, flashing vbmeta and vbmeta.system remove enc or wt does it do i dont want to format internal ?
Click to expand...
Click to collapse
I don't have a work phone to check. before flashing the device, I recommend making a full backup
Dkpost3 said:
I don't have a work phone to check. before flashing the device, I recommend making a full backup
Click to expand...
Click to collapse
could anyone cnfirm if it boots up
lordfinix said:
could anyone cnfirm if it boots up
Click to expand...
Click to collapse
no, quite frankly it bricks the device, do not use.
Rchtect said:
no, quite frankly it bricks the device, do not use.
Click to expand...
Click to collapse
Can you be a little more specific, I'm not a telepath. Found bugs - write, attaching logs.
Dkpost3 said:
Can you be a little more specific, I'm not a telepath. Found bugs - write, attaching logs.
Click to expand...
Click to collapse
after flashing the vbmeta and vbmeta_system i get the error "FAILED (remote: 'Failed to load/authenticate boot image: Load Error')" when trying to boot the recovery img
edit: using the commands you gave us fixed the error but when booting the recovery img im stuck on "fastboot mode" logo
Rchtect said:
after flashing the vbmeta and vbmeta_system i get the error "FAILED (remote: 'Failed to load/authenticate boot image: Load Error')" when trying to boot the recovery img
edit: using the commands you gave us fixed the error but when booting the recovery img im stuck on "fastboot mode" logo
Click to expand...
Click to collapse
Most likely, you switched the slot, while you have 2 different firmware installed on A and B - and of course you will get a brick, you can’t do this.
1. fastboot set_active other - will return you to the working slot
2. send a log (in the recovery settings)
Recovery stuck on fox image
skia16 said:
Recovery stuck on fox imageView attachment 5676807
Click to expand...
Click to collapse
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot flash vbmeta_system --disable-verity --disable-verification vbmeta_system.img
Dkpost3 said:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot flash vbmeta_system --disable-verity --disable-verification vbmeta_system.img
Click to expand...
Click to collapse
not working. it is already stucking in fox image
Dkpost3 said:
OrangeFox Recovery Project​View attachment 5670603​Downloads OrangeFox-R12.1​
Installation
Code:
fastboot boot OrangeFox-R11.1_A12-vndk30-avicii.img
After booting into the recovery, flash OrangeFox-R11.1_3_A12-vndk30-avicii.zip, it will reboot.
Click to expand...
Click to collapse
Can you please state clearly in your thread's title and the OP that this is an UNOFFICIAL release? This is not clear at all, and thus makes it easy for people to assume that this is an official OrangeFox release.
Thanks.
@Dkpost3 The thread title has been updated to reflect that this is an unofficial build.
cc: @DarthJabba9
Regards,
shadowstep
Forum Moderator

How To Guide [ALL RMX] How to soft unbrick stock ROM with OTA update file (unlocked bootloader needed)

DO IT AT YOUR OWN RISK, I'M NOT RESPONSIBLE
I've just unbricked an RMX3474 (Realme 9 5G with unlocked bootloader) using this method. It was bricked (bootloader boot loop) following a bad downgrade by mistake from RUI4 to RUI3 (there's actually no RUI4 ROM available in .ofp format for the RMX3474GDPR).
QPST/QFIL is a powerful (and therefore dangerous) tool, which is why in my opinion it should be reserved for hard unbrick, i.e. for smartphones that only have access to EDL (Emergency DownLoad) mode. I think its current democratisation is not a good thing. This remains my humble opinion, of course. For a soft bricked smartphone, I'm still looking for a "fastboot" solution. LOL, that's just common sense
So (I call back : unlocked bootloader needed).
1. Download the lastest android-tools : here
2. Download the OTA update for the last stock ROM installed on the smartphone :
2a. realme-ota
2b. Type the command :
Code:
realme-ota -v4 -i IMEI1 IMEI2 --old-method RMX3363 RMX3363_11.firmware.XX_0000_000000000000 RUI_version region
2c. Where : - -i IMEI1 IMEI2 = for your smartphone (optional), firmware = letter of firmware, XX = number of firmware, RUI_version = 2, 3 or 4 and region = your smartphone region
2d. For example, for my smartphone, the last "F" firmware, RUI4 and EUEX region :
Code:
realme-ota -v4 -i IMEI1 IMEI2 --old-method RMX3363 RMX3363_11.F.00_0000_000000000000 4 01000100
2e. Result of the command is : "foreign_my_manifest_RMX3363_11.F.07_3070_202305171723.44.71d53b2c_1_cf16f9cb6b61168cd0959cff607e3b32"
2f. You'll find the download link for the OTA update in the result, just below this line
3. Extract .img files from payload.bin :
3a. payload-dumper-go
3b. Type the command :
Code:
payload-dumper-go /path/to/payload.bin
4. Put all files in the same directory (android-tools & extracted payload .img files)
4a. Example for RMX3363GDPR-F07 :
{
"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"
}
5. Boot your smartphone into bootloader and connect it to the PC USB port
6. You need to enter fastbootd mode (to be authorised to flash critical partitions), so open a terminal and type the following command :
Code:
fastboot reboot fastboot
7. Begin with slot a :
Code:
fastboot --set-active=a
8. Start the flash of the .img files (the number of .img files may vary depending on the smartphone model and the version of OTA update) :
Code:
fastboot flash file1 file1.img
fastboot flash file2 file2.img
fastboot flash file3 file3.img
(... etc)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
fastboot --disable-verity --disable-verification flash vbmeta_vendor vbmeta_vendor.img
9. Switch to slot b :
Code:
fastboot --set-active=b
10. Relaunch the flash of the .img files
11. Switch slot a back to active :
Code:
fastboot --set-active=a
12. Reboot the smartphone :
Code:
fastboot reboot
Note : I had 2 errors during the flashes (1 on slot a, 1 on slot b, not the same). On slot a, "Writing 'modem_a' FAILED (remote: 'Operation not permitted')". On slot b, I can't remember (a problem of insufficient space for a file). I tried several things but couldn't get round these errors. Nevertheless, the smartphone rebooted correctly with RUI4
After that, you can easily patch boot.img and vendor_boot.img (optional) files with Magisk, flash them again via fastboot and obtain root mode.
Have a nice day !

Categories

Resources