Develop Bugs

[GUIDE] How to flash " .IMG " files [HOW TO]

So,
I searched the forums for about an hour but i was not able to find a proper guide on how to flash .img files. Mostly, people have problems flashing recovery files.
This might be pretty easy but,...Still,it might help someone.
Here are some simple steps on how to flash .img files onto your Galaxy Nexus.
Let's Get Started
• First of all download this great toolkit by WugFresh from his website.
• Setup the toolkit by installing the Samsung drivers(you must have already installed them).
• Now enable USB debugging on your device by Setting>Developer Options>Android Debugging > [check enable].
• Download ClockworkMod Recovery from here.
• Now Click on Launch (Advance Utilities) at the bottom left corner on the toolkit.
{
"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"
}
___________________________________________________________
• Now check ' Flash (Permanent) ' .
___________________________________________________________
• Click 'Recovery'
___________________________________________________________
• Now, Select the .img recovery file you've downloaded or you can search the file path given below(in the image) for recovery.img files included in the toolkit.
___________________________________________________________
• Select OK and then your'e Done !.

looks good.. here are the steps for mskips toolkit if you wanna add them
download .img file
place the .img file in mskips toolkits "put img file here to flash here" folder
boot gnex to fastboot mode and connect to pc
open mskips toolkit
choose model number
choose option 11 "boot or flash .img file to device"

at first look i thinked you write the steps for flash a .img..but in fastboot..not in a toolkit.i think that flash in a toolkit is so easy also for a total-noob..because they are made for that!instead of do this type of installation,i'd preferred to see the standard fastboot mode,to encourage people to do it manually ( 30 sec)
sometimes **** happens and with the use of toolkit it's more difficult trace problems,anyways that for the guide!
EDIT at this point,i think this is not bad
to flash a .img files from fastboot,download and do an md5 of the file,copy it in the fastboot folder and in a command terminal from windows after going to the directory of fastboot where you downloaded the file digit: (yours phone has to be in fastboot-mode and with usb-debug ON)
FOR A RECOVERY .img
fastboot flash name_of_file.img
FOR A BOOTLOADER .img
fastboot flash bootloader name_of_file.img
FOR A BOOT .img (kernel+ramdisk)
fastboot flash boot name_of_the_file.img
1.some in the fastboot directory have the file inside nomined fastboot-windows..if it's the case,you have to write always fastboot-windows instead of fastboot in commands..or you can rename it that's more quick.
2.when you have to do with a recovery,if you want to only trying that,you can instead of -fastboot flash- do -fastboot boot-..in this case the phone boots with that recovery but after a reset it reloads the previous
EDIT 2
you can add in yours poll the voice "i don't use toolkit".i think in the end will have lots of vote!

Great, but learn how to do it via fastboot. Its safer and its impossible to brick your device if you know fastboot.
Sent from my Galaxy Nexus

thegtfusion said:
Great, but learn how to do it via fastboot. Its safer and its impossible to brick your device if you know fastboot.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
+1 fastboot is a lot safer and easier.

Nice. I had my recovery installed via cwm by the way.

thegtfusion said:
Great, but learn how to do it via fastboot. Its safer and its impossible to brick your device if you know fastboot.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
this.
if you are going to teach people how to flash .img files, do it right, not through a root toolkit. oh, and in no way does this belong in development.

Guides like this are best in General or Themes
Please read rule 15 for a better description of what should be posted where
Thank you for your cooperation
Thread moved
FNM

lawl.
fastboot flash recovery nameofrecovery.img is so hard.

Jesus! What thread have I stepped into!
Beamed from my Grouper.

Zepius said:
lawl.
fastboot flash recovery nameofrecovery.img is so hard.
Click to expand...
Click to collapse
We had someone in IRC when the Gnex first came out flash recovery to the boot kernel.
For those confused,
fastboot flash boot recovery.img
The user couldn't figure out why it only booted to recovery

adrynalyne said:
We had someone in IRC when the Gnex first came out flash recovery to the boot kernel.
For those confused,
fastboot flash boot recovery.img
The user couldn't figure out why it only booted to recovery
Click to expand...
Click to collapse
Lol!
Beamed from my Grouper.

MI 9 SE Brick After Locking the Bootloader (Global rom installed on Chinese phone)

Hi everyone!
I bought a MI 9 SE for my dad, it was a Chinese version with an unlocked bootloader and global rom installed.
After trying to use Google Pay, I figured it needs a locked bootloader. So I locked it using "fastboot oem lock".
After that, the phone is bricked
I didn't have an account bound to it, so can't use the official unlock.
Can access fastboot and recovery.
Tried flashing using recovery, sideloading.
It refuses to install a chinese rom, only a global one can be installed.
Obviously, I get the "This MIUI version can't be installed on this device".
I know there's the EDL path, but that requires an authorized account
Is there any other way around this?
Is there a way to force install a chinese rom over the global rom?
I would really appreciate any help or advice. I've spent a few days reading the forums, tried a lot of utilities but with zero luck.

Did you try the original chinese ROM, the first release? The same with global?

elpaablo said:
Did you try the original chinese ROM, the first release? The same with global?
Click to expand...
Click to collapse
I have tried the last few MIUI versions, but didn't try the original release versions. That's a good point! Will try today, and get back with the results :good:

If you locked the bootloader on a non-official ROM, you could have messed the AVB (Android Verified Boot) partition.
Disabling vbmeta could be helpful.
Download vbmeta.img from https://drive.google.com/open?id=1-Np8xHPfVlJwUJLURntIklmkCyVqU5jH and place it in the same folder of your fastboot tools.
Open a cmd window (don't use Windows Power Shell) and type command
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
If you get the command executed properly, then type
fastboot reboot
and pray if device will restart on old ROM, set a MiAccount and unlock bootloader again using MiFlash, then flash any Official ROM and relock bootloader, if needed.
You can also get GPay working on unlocked bootloader, using Magisk, in case.

Flounderist said:
If you locked the bootloader on a non-official ROM, you could have messed the AVB (Android Verified Boot) partition.
Disabling vbmeta could be helpful.
Download vbmeta.img from and place it in the same folder of your fastboot tools.
Open a cmd window (don't use Windows Power Shell) and type command
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
If you get the command executed properly, then type
fastboot reboot
and pray if device will restart on old ROM, set a MiAccount and unlock bootloader again using MiFlash, then flash any Official ROM and relock bootloader, if needed.
You can also get GPay working on unlocked bootloader, using Magisk, in case.
Click to expand...
Click to collapse
{
"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"
}
It didn't work, says 'Flashing is not allowed in Lock State'

elpaablo said:
Did you try the original chinese ROM, the first release? The same with global?
Click to expand...
Click to collapse
The same error both times, seems it refuses to install older versions of MIUI

savandriy said:
The same error both times, seems it refuses to install older versions of MIUI
Click to expand...
Click to collapse
Oh, you don't use miflash tools?

savandriy said:
It didn't work, says 'Flashing is not allowed in Lock State'
Click to expand...
Click to collapse
Try with
fastboot format userdata
and
fastboot reboot
If you use telegram, join the conversation here @GrusFamily

Reboot in fastboot ans use Flashtool
Flash any ron in fastboot format from here https://mirom.ezbox.idv.tw/en/phone/grus/
With flashtool, all partition will be format and phone is like out of the box

Flounderist said:
If you use telegram, join the conversation here @GrusFamily
Click to expand...
Click to collapse
What the hell, I have a family? What's this about?

Grus said:
What the hell, I have a family? What's this about?
Click to expand...
Click to collapse
Hahaha sorry mate. It's the link of a telegram group and it matched with your nickname.
Grus is the device name for Mi 9 SE :laugh:

That's so incredibly strange. Guess I'll have to check that phone out.

Flounderist said:
Try with
fastboot format userdata
and
fastboot reboot
If you use telegram, join the conversation here @GrusFamily
Click to expand...
Click to collapse
Sadly, it just hangs forever on the "Sending 'userdata' (4400 KB)" part ...

pikouchou said:
Reboot in fastboot ans use Flashtool
Flash any ron in fastboot format from here https://mirom.ezbox.idv.tw/en/phone/grus/
With flashtool, all partition will be format and phone is like out of the box
Click to expand...
Click to collapse
Can you please link to the Flashtool or a tutorial? Do you mean XiaomiADB?

savandriy said:
Can you please link to the Flashtool or a tutorial? Do you mean XiaomiADB?
Click to expand...
Click to collapse
Here is the link:
https://www.xiaomiflash.com/download/
You need to download a fastboot ROM and to unzip it TWICE to get the flashable files.
Then launch flashtool while device is connected in fastboot mode.
Locate files using flashtool interface and try to flash it.
If you won't succeed, EDL flash is your last resort.

https://mirom.ezbox.idv.tw/en/phone/grus/roms-cn-stable/
Try the first chinese version (10.2.3).

Flounderist said:
Here is the link:
https://www.xiaomiflash.com/download/
You need to download a fastboot ROM and to unzip it TWICE to get the flashable files.
Then launch flashtool while device is connected in fastboot mode.
Locate files using flashtool interface and try to flash it.
If you won't succeed, EDL flash is your last resort.
Click to expand...
Click to collapse
It says there's a device mismatch, but this is the Chinese MIUI 10.2.3 for MI 9 SE
I guess EDL it is then

Try global too. I would try all Chinese and global versions, just to be sure. Because, you know, edl isn't free.

savandriy said:
It says there's a device mismatch, but this is the Chinese MIUI 10.2.3 for MI 9 SE
I guess EDL it is then
Click to expand...
Click to collapse
If you get device mismatch error you should:
- check if your device is actually a Mi9 SE
- check if you downloaded a fastboot ROM for Mi 9SE
- check if you are using the latest MIUI driver and MiFlash.
Probably your device had a fake-MIUI ROM installed with some messed device fingerprint, hence MiFlash does not recognize it as Grus.
If you are 100% sure your device is a Mi 9SE, and you downloaded the correct ROM (I would recommend latest China Stable), you can try editing the flash-all.bat file.
Here is a tutorial (you probably will need to translate it): https://www.miui.it/forum/index.php...lazione-delle-rom-fastboot-con-miflash.15301/
Good luck!

You can flash him only with testpoint and auth account

Open Beta 1 for OnePlus 8 Pro ROOT

Here is the patched boot img for OB1. I now have root again.
https://drive.google.com/file/d/1WBJ_0TLp_TFAMoN2ONmvWU4iMeeaHiY8/view?usp=sharing
Try this at your own risk. Worked great for me but I make no warranties if you blow up you phone.
Copy the above to you ADB folder
Type ABD reboot bootloader
Type fastboot boot OB1_patched.img
If the phone boots properly, go back into fastboot and type
Fastboot flash boot_a OB1_patched.img
Fastboot flash boot_b OB1_patched.img
Fastboot reboot.
You should be rooted on OB1
{
"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"
}

Deleted

@Mike02z My magisk is not installed properly with your patched boot img.
I came from oos 10 stable not rooted and followed all the steps you wrote, but when i launch magisk manager i see N/A on the status (See screenshot)
can sombody help me?
Thanks

I know this may sound silly but your bootloader is unlocked, correct? Bootloader must be unlocked.
I extracted the boot.img using payload dumper and Python. I then copied the boot.img to my device. I then ran Magisk and chose patch boot.img. selected it from my Download folder, patched it then copied it to my ADB/Fastboot directory. I booted the new patched image and it worked fine and showed I was rooted. I then flashed both slots, rebooted again and now I have permanent root.
Not sure why it's not working for you if you're unlocked.

Hiya!
Same thing here, bootloader unlocked, followed your instructions to the T and still no root. I downloaded the official canary_manager from github, could it be that? That the manager is the wrong one?
I also see your model is IN2025 but mine is IN2023 could that be it?

Mike02z said:
I know this may sound silly but your bootloader is unlocked, correct? Bootloader must be unlocked.
I extracted the boot.img using payload dumper and Python. I then copied the boot.img to my device. I then ran Magisk and chose patch boot.img. selected it from my Download folder, patched it then copied it to my ADB/Fastboot directory. I booted the new patched image and it worked fine and showed I was rooted. I then flashed both slots, rebooted again and now I have permanent root.
Not sure why it's not working for you if you're unlocked.
Click to expand...
Click to collapse
I had the same issue can you let me know what where you got your version of magisk manager are you using?
thanks

Ok I managed to get root with a bit of a workaround:
1. Download the patched boot.img from here to your phone
2. Open Magisk Manager Canary
3. Go to install - Patch image file - select the OB1_patched.img you downloaded
4. Redo step 3 only this time select the output file magisk_patched.img (the reason was that the magisk_patched.img file had a size of 0b, redoing the step with the new patched img solved it and it was back to 43MB)
5. Copy the magisk_patched.img to your adb folder on your PC or Mac
6. ADB reboot bootloader
7. Fastboot boot magisk_patched.img (do not skip this step so you know your phone will boot and you can check if you have root)
8. Fastboot flash boot_a magisk_patched.img
9. Fastboot flash boot_b magisk_patched.img
10. Fastboot reboot
This did it for me and I know have root on my phone so hope it helps

Shredz98 said:
Ok I managed to get root with a bit of a workaround:
1. Download the patched boot.img from here to your phone
2. Open Magisk Manager Canary
3. Go to install - Patch image file - select the OB1_patched.img you downloaded
4. Redo step 3 only this time select the output file magisk_patched.img (the reason was that the magisk_patched.img file had a size of 0b, redoing the step with the new patched img solved it and it was back to 43MB)
5. Copy the magisk_patched.img to your adb folder on your PC or Mac
6. ADB reboot bootloader
7. Fastboot boot magisk_patched.img (do not skip this step so you know your phone will boot and you can check if you have root)
8. Fastboot flash boot_a magisk_patched.img
9. Fastboot flash boot_b magisk_patched.img
10. Fastboot reboot
This did it for me and I know have root on my phone so hope it helps
Click to expand...
Click to collapse
that makes complete sense now, but what version of magisk manager are you using please?
thanks

bigAL99 said:
that makes complete sense now, but what version of magisk manager are you using please?
thanks
Click to expand...
Click to collapse
It worked flawlessly for me now, so hopefully you'll have the same luck!
The latest one off of his github canary release: fbaf2bde (297).

Shredz98 said:
It worked flawlessly for me now, so hopefully you'll have the same luck!
The latest one off of his github canary release: fbaf2bde (297).
Click to expand...
Click to collapse
i amy be completely stupid but I can't find this channel or this release :crying:

bigAL99 said:
i amy be completely stupid but I can't find this channel or this release :crying:
Click to expand...
Click to collapse
As I'm not fully clear on posting links here I've sent you the link to the official release via PM, hope it helps

Any idea how to keep root comming from 10.5.13?

RicardoDimm said:
Any idea how to keep root comming from 10.5.13?
Click to expand...
Click to collapse
I believe you'll have to do the steps, as the firmware and boot.img would've changed since you're upgrading to Android 11. I could be wrong though

bigAL99 said:
i amy be completely stupid but I can't find this channel or this release :crying:
Click to expand...
Click to collapse
You may download it here.
https://github.com/topjohnwu/magisk_files/blob/canary/app-debug.apk

thnx, for me it worked flawlessly :good:

works flaweless the way you explained it !
I now have root on OB1 , thanks m8

I never got it to boot after doing the inactive slot flash. Since then I have tried this - including the a and b flash, but still stuck on the OnePlus boot animation. Besides MSM, is there any way to get this to boot. I have same AA global device.

Is anyone able to patch boot.img and fastboot the patched image on IN2021. I downloaded the OB1 OTA and extracted boot.img. I am able to fastboot the extracted boot.img. Installed magisk canary and patched the boot.img and got the magisk_patched.img. For some reason when I boot the patched img file it goes to boot loop.

Hi all, can someone clarify if the steps highlighted are to be done before/after using local upgrade on the OB1 zip?

[email protected] said:
Is anyone able to patch boot.img and fastboot the patched image on IN2021. I downloaded the OB1 OTA and extracted boot.img. I am able to fastboot the extracted boot.img. Installed magisk canary and patched the boot.img and got the magisk_patched.img. For some reason when I boot the patched img file it goes to boot loop.
Click to expand...
Click to collapse
I don't think you need to patched the boot img as it is already patched as per OP post.

How To Guide Flash/Install TWRP on Realme GT Master Edition RMX3360 (Indian variant)

TWRP flashing guide for Realme GT Master edition RMX3360​
Flash at your own risk. You might LOSE all data on your phone.
( I will be not responsible for any damage to your device )​
Prerequisites :
Your Bootloader Should be Unlocked. Click Here For Instructions.
First Back up all of your data and files present on the phone because the phone might be erased from the process.
Install Minimal ADB and Fastboot tool from here: LINK
Get the A.09 vbmeta.img files for the Stock firmware. If you are using A.09 firmware then vbmeta.img is needed from A.09 firmware file. LINK
Get the TWRP image file and rename it to twrp.img . Unofficial TWRP Link
The process to disable verity/Verification (Important for Flashing TWRP Recovery):
Reboot the phone to fastboot (Vol Down + Power ).
Connect the phone to the computer using an USB data cable. Preferred to use the stock USB cable.
Search for Minimal adb and fastboot icon in the 'Windows search' and right-click for 'Locate file location' option.
Copy and Place that vbmeta.img in the Minimal adb and fastboot folder.
Hold Shift and Right-click in that directory and click on the options 'open cmd terminal there'.
Type fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img in the cmd terminal.
Reboot the phone again to fastboot mode.
Follow the further process.
The process to install TWRP :
Reboot the phone to fastboot (Vol Down + Power ).
Connect the phone to the computer using an USB data cable. Preferred to use the stock USB cable.
Search for Minimal adb and fastboot icon in the 'Windows search' and right-click for 'Locate file location' option.
Copy and Place that twrp.img in the Minimal adb and fastboot folder.
Hold Shift and Right-click in that directory and click on the options 'open cmd terminal there'.
Type fastboot boot twrp.img in the cmd terminal.
The phone will boot in TWRP recovery and after that go to Advanced > Flash Current TWRP.
Done you have installed TWRP in your device.
TWRP flashed now Enjoy Flashing Custom files and ZIPS.​

pkm774 said:
TWRP flashing guide for Realme GT Master edition RMX3360​
Flash at your own risk. You might LOSE all data on your phone.
( I will be not responsible for any damage to your device )​
Prerequisites :
Your Bootloader Should be Unlocked. Click Here For Instructions.
First Back up all of your data and files present on the phone because the phone might be erased from the process.
Install Minimal ADB and Fastboot tool from here: LINK
Get the A.09 vbmeta.img files for the Stock firmware. If you are using A.09 firmware then vbmeta.img is needed from A.09 firmware file. LINK
Get the TWRP image file and rename it to twrp.img . Unofficial TWRP Link
The process to disable verity/Verification (Important for Flashing TWRP Recovery):
Reboot the phone to fastboot (Vol Down + Power ).
Connect the phone to the computer using an USB data cable. Preferred to use the stock USB cable.
Search for Minimal adb and fastboot icon in the 'Windows search' and right-click for 'Locate file location' option.
Copy and Place that vbmeta.img in the Minimal adb and fastboot folder.
Hold Shift and Right-click in that directory and click on the options 'open cmd terminal there'.
Type fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img in the cmd terminal.
Reboot the phone again to fastboot mode.
Follow the further process.
The process to install TWRP :
Reboot the phone to fastboot (Vol Down + Power ).
Connect the phone to the computer using an USB data cable. Preferred to use the stock USB cable.
Search for Minimal adb and fastboot icon in the 'Windows search' and right-click for 'Locate file location' option.
Copy and Place that twrp.img in the Minimal adb and fastboot folder.
Hold Shift and Right-click in that directory and click on the options 'open cmd terminal there'.
Type fastboot boot twrp.img in the cmd terminal.
The phone will boot in TWRP recovery and after that go to Advanced > Flash Current TWRP.
Done you have installed TWRP in your device.
TWRP flashed now Enjoy Flashing Custom files and ZIPS.​
Click to expand...
Click to collapse
I am getting an error in the last step (Flash current TWRP): "failed to create ramdisk to flash". Any idea?

aprilfoo said:
I am getting an error in the last step (Flash current TWRP): "failed to create ramdisk to flash". Any idea?
Click to expand...
Click to collapse
Maybe more help for the issue i just mentioned above: in the temporary TWRP, the file ramdisk-files.txt contains a line for "mnt/vendor/persist", which does not exist, and thus the cpio command fails.

aprilfoo said:
Maybe more help for the issue i just mentioned above: in the temporary TWRP, the file ramdisk-files.txt contains a line for "mnt/vendor/persist", which does not exist, and thus the cpio command fails.
Click to expand...
Click to collapse
Screenshot can help better, try taking and sending it here.

{
"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"
}

hello sir is it compatible with rmx3363 ?

Okay Stupid question: Has Realme officially released bootloader unlock tool? I know they have released kernel and drivers.

xeltos said:
Okay Stupid question: Has Realme officially released bootloader unlock tool? I know they have released kernel and drivers.
Click to expand...
Click to collapse
well yes for some phones but deeptest somehow works for others if your lucky test them all and see ^^

pkm774 said:
TWRP flashing guide for Realme GT Master edition RMX3360​
Flash at your own risk. You might LOSE all data on your phone.
( I will be not responsible for any damage to your device )​
Prerequisites :
Your Bootloader Should be Unlocked. Click Here For Instructions.
First Back up all of your data and files present on the phone because the phone might be erased from the process.
Install Minimal ADB and Fastboot tool from here: LINK
Get the A.09 vbmeta.img files for the Stock firmware. If you are using A.09 firmware then vbmeta.img is needed from A.09 firmware file. LINK
Get the TWRP image file and rename it to twrp.img . Unofficial TWRP Link
The process to disable verity/Verification (Important for Flashing TWRP Recovery):
Reboot the phone to fastboot (Vol Down + Power ).
Connect the phone to the computer using an USB data cable. Preferred to use the stock USB cable.
Search for Minimal adb and fastboot icon in the 'Windows search' and right-click for 'Locate file location' option.
Copy and Place that vbmeta.img in the Minimal adb and fastboot folder.
Hold Shift and Right-click in that directory and click on the options 'open cmd terminal there'.
Type fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img in the cmd terminal.
Reboot the phone again to fastboot mode.
Follow the further process.
The process to install TWRP :
Reboot the phone to fastboot (Vol Down + Power ).
Connect the phone to the computer using an USB data cable. Preferred to use the stock USB cable.
Search for Minimal adb and fastboot icon in the 'Windows search' and right-click for 'Locate file location' option.
Copy and Place that twrp.img in the Minimal adb and fastboot folder.
Hold Shift and Right-click in that directory and click on the options 'open cmd terminal there'.
Type fastboot boot twrp.img in the cmd terminal.
The phone will boot in TWRP recovery and after that go to Advanced > Flash Current TWRP.
Done you have installed TWRP in your device.
TWRP flashed now Enjoy Flashing Custom files and ZIPS.​
Click to expand...
Click to collapse
hello sir is it compatible with rmx3363 ?

is this method work for latest Android 12 for installing twrp ?

pankaj9pankaj9334 said:
is this method work for latest Android 12 for installing twrp ?
Click to expand...
Click to collapse
Currently, A12 Twrp is under development by twrp team. So you have to wait.

ites working with rmx3363 finally i got twrp to work ^^ thanks

NextB said:
ites working with rmx3363 finally i got twrp to work ^^ thanks
Click to expand...
Click to collapse
Allright, you are the best.
Without any modification of twrp.img ?
On Android 11 Firmware ?

guizzzmo said:
Allright, you are the best.
Without any modification of twrp.img ?
On Android 11 Firmware ?
Click to expand...
Click to collapse
without any

NextB said:
without any
Click to expand...
Click to collapse
I can boot this twrp with fastboot boot twrp.img
but if i try to do Advanced > Flash Current TWRP
i have the same error than as @aprilfoo above

guizzzmo said:
I can boot this twrp with fastboot boot twrp.img
but if i try to do Advanced > Flash Current TWRP
i have the same error than as @aprilfoo above
Click to expand...
Click to collapse
Actually i found a workaround but i prefer not even to share it because of a bigger issue: the OP forgot to mention that: 'Installing Magisk is must if you are planning to press "Flash Current TWRP" when flashing alongside stock ROM'. I did not install Magisk and ended up with a completely dysfunctional phone and had to flash again the stock OS.
So i suggest to wait a bit more (some ROMs are in release candidate in the Telegram group)

aprilfoo said:
Actually i found a workaround but i prefer not even to share it because of a bigger issue: the OP forgot to mention that: 'Installing Magisk is must if you are planning to press "Flash Current TWRP" when flashing alongside stock ROM'. I did not install Magisk and ended up with a completely dysfunctional phone and had to flash again the stock OS.
So i suggest to wait a bit more (some ROMs are in release candidate in the Telegram group)
Click to expand...
Click to collapse
ok thanks for the reply. wich telegram group?

guizzzmo said:
ok thanks for the reply. wich telegram group?
Click to expand...
Click to collapse
@realmegtmasterupdates - telegram channel publications statistics Realme GT Master | UPDATES
telegram channel publications statistics of Realme GT Master | UPDATES telegram channel. All about Realme GT Master - RMX3366 ROMs, Kernels, Guides, Mods, NEWS, everything. Stay up-to-date with us! Official Group: @RealmeGTMaster Photography : @RMGTMasterPhotography Gaming : @RMGTMasterGaming...
telemetr.io

Use This
https://www.getdroidtips.com/twrp-recovery-realme-gt-master-edition/

Oh i see the problem, it's because the new partition slot A/B.
Ok i have magisk installed on stock rom but i think i will waiting. I stay on UI 2.0 with full root, magisk, lsposed, safetynet, and no bugs

Question My phone has became brick(cannot enter the recovery mode), after installed boot.img

After 168 hours bought. I've unlocked my Xiaomi 11 lite 5G NE.
I follow the offical guide to install the latest Lineageos. https://wiki.lineageos.org/devices/lisa/install
here is my operations:
Enable devleoper mode and USB debugging on my device.
adb devices shows OK, it can list my device.
enter the fastboot mode, type `fastboot devices` shows ok, it can list my device.
I've download all files from this page: https://download.lineageos.org/devices/lisa/builds
lineage-19.1-20230325-nightly-lisa-signed.zip
boot.img
dtbo.img
super_empty.img
vbmeta.img
vendor_boot.img
then I enter the fastboot mode in my phone and connected to my computer(adb, fastboot, usb drivers was installed).
I follow the Lineageos instructions and type the following command.
fastboot flash dtbo <dtbo>.img //dtbo.img listed above
fastboot flash vendor_boot <vendor_boot>.img //vendor_boot.img listed above
fastboot flash boot <recovery_filename>.img //boot.img listed above
then the guide let me enter the recovery mode(hold power + volumn up), my phone shows this image:
{
"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"
}
It can not enter the recovery mode like the guide says.

Hello,
don't know if it could be a reason, but was official miui 13 or 14 (Android 12 or 13) ?

newbie_or_not_newbie said:
Hello,
don't know if it could be a reason, but was official miui 13 or 14 (Android 12 or 13) ?
Click to expand...
Click to collapse
I don't know which version of miui installed in my phone. I didn't check my phone's default miui version. I've just brought this phone a week.

In lineage OS flash instructions, it says this :
WARNING: Before following these instructions please ensure that the device is currently using Android 12 firmware.
Don't know if it can softbrick your phone if it's android 13.

newbie_or_not_newbie said:
In lineage OS flash instructions, it says this :
WARNING: Before following these instructions please ensure that the device is currently using Android 12 firmware.
Don't know if it can softbrick your phone if it's android 13.
Click to expand...
Click to collapse
I think that's the really problem. I will recovery the offical miui and try again.

it cold possibile a problem with usb driver or cable problems
i think you only flash dtbo.img , boot and vendor_boot did not get on the device
start you lisa device with fastboot (power + Vol down)
fastboot flash boot_ab .\path to boot.img all files in the same folder
Code:
PS C:\lisa\lineageos19\> .\fastboot.exe flash boot boot.img
press enter,
than connect the cable after its finish unplug the cable
an do it with dtbo and vender_boot the same way

Trismo said:
it cold possibile a problem with usb driver or cable problems
i think you only flash dtbo.img , boot and vendor_boot did not get on the device
start you lisa device with fastboot (power + Vol down)
fastboot flash boot_ab .\path to boot.img all files in the same folder
Code:
PS C:\lisa\lineageos19\> .\fastboot.exe flash boot boot.img
press enter,
than connect the cable after its finish unplug the cable
an do it with dtbo and vender_boot the same way
Click to expand...
Click to collapse
It doesn't work. I've tried.
newbie_or_not_newbie said:
In lineage OS flash instructions, it says this :
WARNING: Before following these instructions please ensure that the device is currently using Android 12 firmware.
Don't know if it can softbrick your phone if it's android 13.
Click to expand...
Click to collapse
No, I've tried to recovery Miui. And ensuring my Miui to equal android 12. It is still not work.

treelu said:
It doesn't work. I've tried.
No, I've tried to recovery Miui. And ensuring my Miui to equal android 12. It is still not work.
Click to expand...
Click to collapse
And Miui Start ?

Hi
Bro no worry
Flash the the latest xiaomi.eu rom for lisa
Via fastboot and it will boot normaly
Ps all data will be erased

Nillesse said:
Hi
Bro no worry
Flash the the latest xiaomi.eu rom for lisa
Via fastboot and it will boot normaly
Ps all data will be erased
Click to expand...
Click to collapse
Thanks. I am not worry. My phone can still work with Miui.