Original Stock BOOT.IMG for MERLIN
+ Magisk Patched BOOT.IMG for MERLIN
+ Original Stock VBMETA.IMG for MERLIN
+ Original Stock RECOVERY.IMG for MERLIN
Works with:
- Xiaomi Redmi 10X 4G
- Xiaomi Redmi Note 9
Firmware Versions:
- (Engineering) AL2522-Merlin-V039-Q-0513
- (Engineering) AL2522-Merlin-V044-Q-0920
- V12.0.5.0.QJOMIXM
- V12.0.4.0.QJOMIXM
Magisk Version:
Magisk version: v20.4 / v23.0
How to flash it?
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot magisk_patched.img
MD5 hashes for (Engineering) AL2522-Merlin-V039-Q-0513
(Engineering) (AL2522-Merlin-V039-Q-0513) Original Stock Rom BOOT.IMG: d6e19a30d85a27379d91072665ad43c9
(Engineering) (AL2522-Merlin-V039-Q-0513) Magisk Patched (v23.0) BOOT.IMG: 40799cd519a4d76fbf6f6bf48618cb4b
(Engineering) (AL2522-Merlin-V039-Q-0513) Original Stock Rom vbmeta.img: 31da88d4a00b99b36081f859f17f808a
(Engineering) (AL2522-Merlin-V039-Q-0513) Original Stock Rom RECOVERY.IMG: 6362f1beb617572680f3fc91640d3767
MD5 hashes for (Engineering) AL2522-Merlin-V044-Q-0920
(Engineering) (AL2522-Merlin-V044-Q-0920) Original Stock Rom BOOT.IMG: cf47a73562cfd84a7337b37637eb8cef
(Engineering) (AL2522-Merlin-V044-Q-0920) Magisk Patched (v23.0) BOOT.IMG: 5b059ea9665156a296320f1dec6f2149
(Engineering) (AL2522-Merlin-V044-Q-0920) Original Stock Rom vbmeta.img: 5003b40cb64cfcd77b9f85fc2cc8f478
(Engineering) (AL2522-Merlin-V044-Q-0920) Original Stock Rom RECOVERY.IMG: f3d00ee3de8ba4598318c3a80fdbad63
MD5 hashes for V12.0.5.0.QJOMIXM
(V12.0.5.0.QJOMIXM) Original Stock Rom BOOT.IMG: 2012df0c05a5a8cbda196587c87dcd6e
(V12.0.5.0.QJOMIXM) Magisk Patched (v20.4) BOOT.IMG: 61065cbcfec52e7e3544192c0b7eabb2
(V12.0.5.0.QJOMIXM) Original Stock Rom vbmeta.img: 0a2837ff13f46f9cb9d12bafa480cb5a
(V12.0.5.0.QJOMIXM) Original Stock Rom RECOVERY.IMG: d390181ce65fff4d90b9c81e37d8e4f0
MD5 hashes for V12.0.4.0.QJOMIXM
(V12.0.4.0.QJOMIXM) Original Stock Rom BOOT.IMG: e6a904938cf6ea3ed5d040ae69115131
(V12.0.4.0.QJOMIXM) Magisk Patched (v20.4) BOOT.IMG: 2915940d4097bfaf7739f10bed8d968d
(V12.0.4.0.QJOMIXM) Original Stock Rom vbmeta.img: 46815a4103db076986b1f877a3e01da1
(V12.0.4.0.QJOMIXM) Original Stock Rom RECOVERY.IMG: 49ad8c5cf3b9aaf39c15e10550711649
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
Original Stock BOOT.IMG for MERLIN
+ Magisk Patched BOOT.IMG for MERLIN
+ Original Stock VBMETA.IMG for MERLIN
+ Original Stock RECOVERY.IMG for MERLIN
Works with:
- Xiaomi Redmi 10X 4G
- Xiaomi Redmi Note 9
Firmware Versions:
- V11.0.5.0.QJOMIXM
- V11.0.4.0.QJOMIXM
Magisk Version:
Magisk version: v20.4
Magisk Manager used: v8.0.4
How to flash it?
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot magisk_patched.img
MD5 hashes for V11.0.5.0.QJOMIXM
(V11.0.5.0.QJOMIXM) Original Stock Rom: BOOT.IMG 0f30a2cbbe6aa49951a264910e164179
(V11.0.5.0.QJOMIXM) Magisk Patched BOOT.IMG: 20d87e38da9e636ceb9ad274554a3f78
(V11.0.5.0.QJOMIXM) Original Stock Rom vbmeta.img: 2862688acc3723019377e56163ee2672
(V11.0.5.0.QJOMIXM) Original Stock Rom RECOVERY.IMG: 480bddf2617553ee33e67d7eb9be0259
MD5 hashes for V11.0.4.0.QJOMIXM
(V11.0.4.0.QJOMIXM) Original Stock Rom: BOOT.IMG fa15e5f55369f2f3624f49e323bb3ecf
(V11.0.4.0.QJOMIXM) Magisk Patched BOOT.IMG: 17c1dc1940dd149dd58ce36464c9d40f
(V11.0.4.0.QJOMIXM) Original Stock Rom vbmeta.img: 110fae325e6659a0ba81cb3820d41c41
(V11.0.4.0.QJOMIXM) Original Stock Rom RECOVERY.IMG: a0b47332664a85c2ccc455281af92d77
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
Original Stock BOOT.IMG for MERLIN
+ Magisk Patched BOOT.IMG for MERLIN
+ Original Stock VBMETA.IMG for MERLIN
+ Original Stock RECOVERY.IMG for MERLIN
Works with:
- Xiaomi Redmi 10X 4G
- Xiaomi Redmi Note 9
Firmware Versions:
- (India) V12.0.4.0.QJOINXM
- V11.0.2.0.QJOMIXM
Magisk Version:
Magisk version: v20.4
Magisk Manager used: v8.0.4
How to flash it?
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot magisk_patched.img
MD5 hashes for V12.0.4.0.QJOINXM (India)
(India) (V12.0.4.0.QJOINXM) Original Stock Rom: BOOT.IMG 096d8d46ca1612f0ff13863fed7cf6e5
(India) (V12.0.4.0.QJOINXM) Magisk Patched BOOT.IMG: 2097a84a63eb5c3bfdd5888bbbb90254
(India) (V12.0.4.0.QJOINXM) Original Stock Rom vbmeta.img: a0a81348af3eb9a0734a71ffb4aa4c66
(India) (V12.0.4.0.QJOINXM) Original Stock Rom RECOVERY.IMG: cc002eba1ad975c141cd0134cd45d4f1
MD5 hashes for V11.0.2.0.QJOMIXM
(V11.0.2.0.QJOMIXM) Original Stock Rom: BOOT.IMG b0ff40a8a9258b57406dbce09bc48ac9
(V11.0.2.0.QJOMIXM) Original Stock Rom vbmeta.img: db1aa7448d2b1a414a480d6e239b88e5
(V11.0.2.0.QJOMIXM) Original Stock Rom RECOVERY.IMG: 53bec4fe327c314668282b2421180ee5
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
Original Stock BOOT.IMG for MERLIN
+ Magisk Patched BOOT.IMG for MERLIN
+ Original Stock VBMETA.IMG for MERLIN
+ Original Stock RECOVERY.IMG for MERLIN
Works with:
- Xiaomi Redmi 10X 4G
- Xiaomi Redmi Note 9
Firmware Versions:
- V12.0.7.0.QJOMIXM
- V12.0.6.0.QJOMIXM
Magisk Version:
- V12.0.7.0.QJOMIXM: v22.0 / v22.1
- V12.0.6.0.QJOMIXM: v20.4 / v21.2 / v21.3 / v21.4 / v22.0
How to flash it?
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot magisk_patched.img
MD5 hashes for V12.0.7.0.QJOMIXM
(V12.0.7.0.QJOMIXM) Original Stock Rom BOOT.IMG: 6778ea8ce479808077d181cc1ac03943
(V12.0.7.0.QJOMIXM) Magisk Patched (v23.0) BOOT.IMG: ec4dfce2d410d004b29d9c4f8c0e2906
(V12.0.7.0.QJOMIXM) Magisk Patched (v22.1) BOOT.IMG: b61f62a9aba550621387c3c2307c00b6
(V12.0.7.0.QJOMIXM) Magisk Patched (v22.0) BOOT.IMG: ad0d4840939a059a904aabc204aa3737
(V12.0.7.0.QJOMIXM) Original Stock Rom vbmeta.img: 31bd85d94d62ae722143b0d1119ee977
(V12.0.7.0.QJOMIXM) Original Stock Rom RECOVERY.IMG: 73bf431b875192477a3c50fd91d7a895
MD5 hashes for V12.0.6.0.QJOMIXM
(V12.0.6.0.QJOMIXM) Original Stock Rom BOOT.IMG: 27ca5be7acfedc624f07633715b2f3953
(V12.0.6.0.QJOMIXM) Magisk Patched (v22.0) BOOT.IMG: 0e4a571b819babf6382bbf4acdb93972
(V12.0.6.0.QJOMIXM) Magisk Patched (v21.4) BOOT.IMG: 262ac418af8042aa9f69b687e6583619
(V12.0.6.0.QJOMIXM) Magisk Patched (v21.3) BOOT.IMG: 0373a1525c56a2ff769b3a10d3329037
(V12.0.6.0.QJOMIXM) Magisk Patched (v21.2) BOOT.IMG: 678fec9f87db68c88ff62ef095953f838
(V12.0.6.0.QJOMIXM) Magisk Patched (v20.4) BOOT.IMG: 3e6e3c1d0ac628f2b096847acc1ccd97
(V12.0.6.0.QJOMIXM) Original Stock Rom vbmeta.img: b189ca5a9884fb2ae16ab0cb496adacb
(V12.0.6.0.QJOMIXM) Original Stock Rom RECOVERY.IMG: eba7cb5878c6ec9989526972e611bc77
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
VD may you give the procedure on how to upload these files into the phone please step by step i do not want to brick my phone i have seen there is version files exactly for my Redmi note 9 merlin
gruka said:
VD may you give the procedure on how to upload these files into the phone please step by step i do not want to brick my phone i have seen there is version files exactly for my Redmi note 9 merlin
Click to expand...
Click to collapse
First, you need unlocked bootloader !
If you want to flash safe and secure, go to fastboot.
(Keep pressed keys: Power + Vol.Down and wait for fastboot logo.)
You can find a hude amound of videos in youtube too, about how enter in fastboot and how flash using fastboot.
Certainly, it helps alot.
If you want to flash the original stock vbmeta, download and flash vbmeta.img.
If you want to flash the original stock recovery, download and flash recovery.img.
If you want to root, you need to download and flash the magisk_patched.img to the boot.
You can flash the image files according your MIUI version and it will works perfectly.
If you want TWRP, you need to go to: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4227759/
REMEMBER: if you want to flash a custom boot, like magisk patched, or a custom recovery, like TWRP, you need to disable verity and disable verification on vbmeta ! Otherwise, your device will be bricked.
Here, you can find PATCHED vbmeta (disabled verity and disabled verification): https://forum.xda-developers.com/t/...omi-redmi-10x-4g-xiaomi-redmi-note-9.4221075/
So, you need to flash all this for rooting and twrp:
Code:
fastboot flash boot MAGISK_PATCHED.IMG
fastboot flash recovery TWRP.IMG
fastboot flash vbmeta VBMETA_VD171.IMG
For reboot, you can type:
fastboot reboot
Good luck
I have a problem and got stuck in bootloop. I wanted to flash the latest recovery and flashed PRBP. It keeps showing Redmi and doesnt go into system or recovery. I am able to enter fastboot mode
My ROM version is 12.0.6. Please help me
balaji345 said:
I have a problem and got stuck in bootloop. I wanted to flash the latest recovery and flashed PRBP. It keeps showing Redmi and doesnt go into system or recovery. I am able to enter fastboot mode
My ROM version is 12.0.6. Please help me
Click to expand...
Click to collapse
If you can enter in fastboot mode, be careful for don't bricking it.
It can help to solve your problem.
Well, does your device keep rebooting forever?
Or does it stops on a frozen black screen?
VD171 said:
If you can enter in fastboot mode, be careful for don't bricking it.
It can help to solve your problem.
Well, does your device keep rebooting forever?
Or does it stops on a frozen black screen?
Click to expand...
Click to collapse
It keeps rebooting forever. If I press power button and down volume button, I am able to get into fastboot mode. I tried with XiaomiTool v2. It flashes stock rom but still doesnt work.
balaji345 said:
It keeps rebooting forever. If I press power button and down volume button, I am able to get into fastboot mode
Click to expand...
Click to collapse
So, you've flashed any file by mistake.
If you can see the word "Redmi" and you can't see the word "MIUI", probably the problem is with boot.
If you can see the word "MIUI", probably your problem is with the userdata.
What were your last steps before it got bootloop?
Can you enter in recovery mode too?
Did you flash vbmeta?
VD171 said:
So, you've flashed any file by mistake.
If you can see the word "Redmi" and you can't see the word "MIUI", probably the problem is with boot.
If you can see the word "MIUI", probably your problem is with the userdata.
What were your last steps before it got bootloop?
Can you enter in recovery mode too?
Did you flash vbmeta?
Click to expand...
Click to collapse
I can see Redmi and not MIUI.
Im not able to enter recovery mode. If I try.
VD171 said:
So, you've flashed any file by mistake.
If you can see the word "Redmi" and you can't see the word "MIUI", probably the problem is with boot.
If you can see the word "MIUI", probably your problem is with the userdata.
What were your last steps before it got bootloop?
Can you enter in recovery mode too?
Did you flash vbmeta?
Click to expand...
Click to collapse
I can see only the redmi name. And it keeps bootlooping.
I flashed the following file in fastboot mode.
PBRP-Note9-V11.0.4.0.QJOCNXM-20210114-wzsx15. I got this in the Lineageos 17 thread. Didnt realise it was the wrong version fo rmy Stock ROM which is 12.0.6
After this, when I rebooted, it keeps boot looping.
Have flashed vbmeta.
Not able to enter recovery mode.
balaji345 said:
I can see Redmi and not MIUI.
Im not able to enter recovery mode. If I try.
I can see only the redmi name. And it keeps bootlooping.
I flashed the following file in fastboot mode.
PBRP-Note9-V11.0.4.0.QJOCNXM-20210114-wzsx15. I got this in the Lineageos 17 thread. Didnt realise it was the wrong version fo rmy Stock ROM which is 12.0.6
After this, when I rebooted, it keeps boot looping.
Have flashed vbmeta.
Not able to enter recovery mode.
Click to expand...
Click to collapse
Normally, the recovery partition doesn't break the boot.
Unhappy, V11.0.4.0 recovery projects, works only with MIUI V12.0.4.0 or lower.
For V12.0.5.0 or higher, you need to flash the V12.0.6.0 recovery project.
I think the problem is with vbmeta, because it can break the boot.
Did you flash vbmeta with flags "--disable-verity --disable-verification" ?
VD171 said:
Normally, the recovery partition doesn't break the boot.
Unhappy, V11.0.4.0 recovery projects, works only with MIUI V12.0.4.0 or lower.
For V12.0.5.0 or higher, you need to flash the V12.0.6.0 reocvery projet.
I think the problem is with vbmeta, because it can break the boot.
Did you flash vbmeta with flags "--disable-verity --disable-verification" ?
Click to expand...
Click to collapse
I tried to flash vbmeta with flags. It says below error " unrecognised option -- disable verity
{
"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"
}
request if you can share the full command and the version of vbmeta?
I am able to get into stock recovery mode.
Sorry for bothering you and thanks for your prompt support. Much Appreciated!
The below is the error while flashing
balaji345 said:
I tried to flash vbmeta with flags. It says below error " unrecognised option -- disable verityView attachment 5220985 request if you can share the full command and the version of vbmeta?
I am able to get into stock recovery mode.
Sorry for bothering you and thanks for your prompt support. Much Appreciated!
Click to expand...
Click to collapse
You may try my already patched vbmeta: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218909/
You can flash it without using the flags, it is already patched on its content.
Good luck
VD171 said:
You may try my already patched vbmeta: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218909/
You can flash it without using the flags, it is already patched on its content.
Good luck
Click to expand...
Click to collapse
So I tried patching the vbmeta file. Now its stuck on the Redmi screen, not moving forward.
Can you guide how can I restore to stock MIUI rom? Is there a flashable stock version which can be flashed through fastboot?
Once again, sorry for the multiple queries. My issue is not getting resolved. Thanks for the support once again. Request guidance
balaji345 said:
So I tried patching the vbmeta file. Now its stuck on the Redmi screen, not moving forward.
Can you guide how can I restore to stock MIUI rom? Is there a flashable stock version which can be flashed through fastboot?
Once again, sorry for the multiple queries. My issue is not getting resolved. Thanks for the support once again. Request guidance
Click to expand...
Click to collapse
Any fastboot version, can be flashed through fastboot
Here, you can find original stock rom for Merlin: https://xiaomifirmwareupdater.com/miui/merlin/
If you flash the whole firmware, certainly it will unbrick your device.
If it keeps in bootloop after flashing the whole firmware, you just need to wipe data.
VD171 said:
Any fastboot version, can be flashed through fastboot
Here, you can find original stock rom for Merlin: https://xiaomifirmwareupdater.com/miui/merlin/
If you flash the whole firmware, certainly it will unbrick your device.
If it keeps in bootloop after flashing the whole firmware, you just need to wipe data.
Click to expand...
Click to collapse
Hmm I downloaded the fastboot version of the stock ROM, it is ending with .tgz.
Can you suggest how do I flash it and command to be used.
balaji345 said:
Hmm I downloaded the fastboot version of the stock ROM, it is ending with .tgz.
Can you suggest how do I flash it and command to be used.
Click to expand...
Click to collapse
You need to extract it, and then flash manually or using the flash_all_except_data.bat or flash_all.bat
KEEP AWAY of the flash_all_lock.bat this file will LOCK your bootloader again !!!
You can flash it using MiFlash too, see those:
VD171 said:
You need to extract it, and then flash manually or using the flash_all_except_data.bat or flash_all.bat
KEEP AWAY of the flash_all_lock.bat this file will LOCK your bootloader again !!!
You can flash it using MiFlash too, see those:
Click to expand...
Click to collapse
Tried the steps above. The MIflash tool initially gave error that the folder (extracted ROM) cannot be found.
I tried to manually run the .bat file, now it is a black screen. NO response, not switching on or off. When connected to the PC, it does make the connected sound in the PC. But nothing on the screen. I think I hard bricked.
Wasted half my day and yours too. I think ill take this to the Service centre. Cant see any other solution
balaji345 said:
Tried the steps above. The MIflash tool initially gave error that the folder (extracted ROM) cannot be found.
I tried to manually run the .bat file, now it is a black screen. NO response, not switching on or off. When connected to the PC, it does make the connected sound in the PC. But nothing on the screen. I think I hard bricked.
Wasted half my day and yours too. I think ill take this to the Service centre. Cant see any other solution
Click to expand...
Click to collapse
What was result of the .bat file?
Did it flash all partitions?
If you flashed the ROM and then bricked your device, apparentely this is not the properly rom for your device.
Are you sure you have a Redmi Note 9 or a Redmi 10X 4G ?
Go to black screen, plug usb cable and try "adb devices".
Does it show your device?
Code:
* Disclaimer
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed. Please do some research
* before flashing GSI! YOU are choosing to make these modifications, and if
* you blame me in any way for what happens to your device, I will laugh at you.
* BOOM! goes the dynamite
- make sure you have your stock rom by hand, and in case youre also using a new mediatek device make sure you also have mtk-bypass utility and sp flash tool by hand just in case or any other way of restoring your stock rom
you cant have magisk patched boot image installed unless you have also flashed a different product img
- under developer options enable oem unlocking
- adb reboot bootloader
- fastboot flashing unlock
- fastboot flashing unlock_critical
- fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
- fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
- fastboot reboot fastboot
- fastboot delete-logical-partition product (DONT DO THIS IF YOU WANT TO FLASH MAGISK. IF YOU DO THEN FOLLOW THIS GUIDE REGARDING MAGISK AND PRODUCT PARTITION https://forum.xda-developers.com/t/tutorial-magisk-on-gsi-on-devices-with-dynamic-partition.4311045/)
- fastboot flash system system.img (must be arm64 A/B)
- fastboot reboot recovery
- format in TWRP (https://forum.xda-developers.com/t/unofficial-twrp-3-5-2-for-infinix-zero-8-x687.4303243/)
enjoy your GSI experience
note that im not responsible for any bricked devices
do this at your own risk
tested on infinix zero 8 X687
Your device MUST have an unlockable bootloader.
Your device MUST be Project Treble compatible. That means your device meets one of the following criteria:
Your device LAUNCHED with Android 8.0 Oreo or a newer version (eg. Android 8.1 Oreo) AND is Google Play certified. (If you rooted your device/flashed another custom ROM and somehow ended up with your device being listed as uncertified in Google Play, then don’t worry. We’re only concerned about the status of the device as it was shipped.)
Your device UPGRADED to Android 8.0 Oreo or a newer version AND was made Project Treble compatible by the manufacturer. See this article for a list of such devices.
Your device does not meet either of the above criteria but DOES have access to an unofficial way to be made Treble compatible. Again, refer to this article for a list of such devices.
Your device is free of any heavy modifications such as the Xposed Framework, SuperSU, or Magisk. You can re-install these afterward, but please be sure you are using the stock boot/ramdisk before proceeding.
Sarticle said:
Your device MUST have an unlockable bootloader.
Your device MUST be Project Treble compatible. That means your device meets one of the following criteria:
Your device LAUNCHED with Android 8.0 Oreo or a newer version (eg. Android 8.1 Oreo) AND is Google Play certified. (If you rooted your device/flashed another custom ROM and somehow ended up with your device being listed as uncertified in Google Play, then don’t worry. We’re only concerned about the status of the device as it was shipped.)
Your device UPGRADED to Android 8.0 Oreo or a newer version AND was made Project Treble compatible by the manufacturer. See this article for a list of such devices.
Your device does not meet either of the above criteria but DOES have access to an unofficial way to be made Treble compatible. Again, refer to this article for a list of such devices.
Your device is free of any heavy modifications such as the Xposed Framework, SuperSU, or Magisk. You can re-install these afterward, but please be sure you are using the stock boot/ramdisk before proceeding.
Click to expand...
Click to collapse
thats complete bs
your device must be launched with android 10 or newer to be able to have dynamic partitions.
google play certification has nothing to do with it.
and if you flash product partition you might get away without reinstalling magisk or xposed
can anyone shed light on whether or the super partition is shared between the slots? in other words, if I flash a boot image to super partition in twrp, will it flash only to that slot's super (slot B in my case is messed up) or will it flash to both slots? I am only trying to flash to slot B super partition in hopes of restoring /system_ext, /product, and /odm. any help is greatly appreciated
thirtythr33 said:
can anyone shed light on whether or the super partition is shared between the slots? in other words, if I flash a boot image to super partition in twrp, will it flash only to that slot's super (slot B in my case is messed up) or will it flash to both slots? I am only trying to flash to slot B super partition in hopes of restoring /system_ext, /product, and /odm. any help is greatly appreciated
Click to expand...
Click to collapse
super partiton only has system, vendor and product a/b partitions
boot isnt on super partition
kusti420 said:
super partiton only has system, vendor and product a/b partitions
boot isnt on super partition
Click to expand...
Click to collapse
ok the reason I ask is I am given the option to flash my backup boot image to super in twrp flash image screen, that's why I asked, and since twrp is reporting that I'm missing system_ext, product, and odm, that flashing to super would fix that, a long shot but I'm desperate.
so to be clear is it shared between slots or does each slot have it's own super? (or the partitions found in it)
kusti420 said:
- make sure you have your stock rom by hand, and in case youre also using a new mediatek device make sure you also have mtk-bypass utility and sp flash tool by hand just in case or any other way of restoring your stock rom
also stock recovery must be installed
and you cant have magisk patched boot image installed
- under developer options enable oem unlocking
- fastboot flashing unlock and then fastboot flashing unlock_critical
- fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
- fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
- fastboot reboot fastboot
- fastboot delete-logical-partition product
- fastboot flash system system.img (must be arm64 A/B)
- fastboot reboot
- format in TWRP (https://forum.xda-developers.com/t/unofficial-twrp-3-5-2-for-infinix-zero-8-x687.4303243/)
or if you dont have a custom recovery then you can just factory reset in stock recovery
enjoy your GSI experience
note that im not responsible for any bricked devices
do this at your own risk
tested on infinix zero 8 X687
Click to expand...
Click to collapse
this is all done on pc right? is everything in order?
JordanPahlevi said:
this is all done on pc right? is everything in order?
Click to expand...
Click to collapse
yes its done on pc and everything is indeed in order
Flash gsi with twrp can't ?
Blacxx said:
Flash gsi with twrp can't ?
Click to expand...
Click to collapse
you can only do it in twrp if you rebuild the whole super partition with the gsi of your choice and flash that
Android prevents apps or pretty much anything from mounting the system.
Stephanie_Sy said:
Android prevents apps or pretty much anything from mounting the system.
Click to expand...
Click to collapse
mounting isnt the problem, it mounts just fine, but its read only, thats the problem
How did you port twrp for infinix zero 8? I need one for infinix note 10
My phone is Techno kd7.
My phone Dynamic Partition Android, I have installed TWRP Recovery but can't flash gsi img because the system is IMG partition 1700 MB and gsi img 1800 up. Please give me a solution sir
Parvej789 said:
My phone is Techno kd7.
My phone Dynamic Partition Android, I have installed TWRP Recovery but can't flash gsi img because the system is IMG partition 1700 MB and gsi img 1800 up. Please give me a solution sir
Click to expand...
Click to collapse
follow the tutorial and flash product partition
this may be of interest or help to Samsung users in particular.
getting fastboot via TWRP to work on windows 7 to 10. it worked for me on windows 10 pro and enabled me to flash GSIs successfully.
Latest ADB Fastboot and USB Drivers installer tool for windows
All praise and All Thanks to God ADB Fastboot and USB Driver installer tool for Windows, which will always install the latest version. To update the adb fastboot and usb drivers again, just rerun the tool. OS Requirements: Windows 7 and above Steps: 1. Connect the phone in USB Debugging mode...
eu.community.samsung.com
it's not just for Samsung users though, it'll install the latest ADB and Fastboot drivers and download Microsoft dependencies. but now us Samsung users can have Fastboot and do
Code:
fastboot flash system system.img
... so yay !!
kusti420 said:
super partiton only has system, vendor and product a/b partitions
boot isnt on super partition
Click to expand...
Click to collapse
i flashed using these commands on my v60 tmobile
--AB devices--
fastboot devices
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot reboot fastboot
fastboot getvar is-userspace
fastboot erase system
fastboot delete-logical-partition product_insertslothere
Example
fastboot delete-logical-partition product_a
fastboot delete-logical-partition productb
fastboot flash system system.img
fastboot reboot recovery
i flashed 3 gsi A10s, los 17.1 didnt boot, pixel experiance and RR Remix booted but never entered android. and when i tried to flash my kdz it flashes all parititons except for super.img it fails everytime on different modes of LG up. I flashed super.img via Qfil but phon wont boot.
i even tried using ChonDoe_Flasher via twrp in a folder it flashes but it still wont boot at all. at this point i cant use LGup because i get stuck in download mode. any help would be greatly appreciated
blaze2051 said:
Try :
Click to expand...
Click to collapse
Commands used to Install gsi Rom using Fastboot Mode
1. First Go into Fastboot mode by typing this command
adb reboot bootloader
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
2.Type these commands 1 by 1
fastboot reboot fastboot
fastboot delete-logical-partition product_a
fastboot delete-logical-partition system_ext_a
fastboot erase system
fastboot flash system system.img(dynamic gsi ROM flash)
fastbo -w
fastboot reboot
Note(stock recovery to try)
Parvej789 said:
Commands used to Install gsi Rom using Fastboot Mode
1. First Go into Fastboot mode by typing this command
adb reboot bootloader
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
2.Type these commands 1 by 1
fastboot reboot fastboot
fastboot delete-logical-partition product_a
fastboot delete-logical-partition system_ext_a
fastboot erase system
fastboot flash system system.img(dynamic gsi ROM flash)
fastbo -w
fastboot reboot
Note(stock recovery to try)
Click to expand...
Click to collapse
i finally got a working rom install since i cant go back to oem stock, it wasnt the commands it was the roms, they just dont boot at all. except one 1 rom did boot. all others LOS 16-18 RR Remix and Pixel experiamce all failed to boot except for E foundation rom
/http://doc.e.foundation/how-tos/understand-and-use-gsi 7
/http://doc.e.foundation/how-tos/install-GSI 7
New linksto download the latest official
dev /e/ G.S.I. android.10 Q
Once you know which system image you need
Arm A 2 (system-arm-a.img.xz)
Arm A/B 3 (system-arm-ab.img.xz)
Arm64 A 11 (system-arm64-a.img.xz)
Arm64 A/B 31 (system-arm64-ab.img.xz)
Binder 64 A 1 (system-a64-a.img.xz)
Binder 64 A/B 4 (system-a64-ab.img.xz)
I no know.
Dynamic
gsi ROM
GsI Rom Link : Tested rom
Tecno kd7 work
*Official Android 11 :
1. AOSP 11.0 v313_system-roar-arusson
Download link AOSP 11.0 v313
*Unofficial QAndroid 11 :
1. Pixel Experience Plus 11.0 v313
Thanks for ponces
Download link PixelExperience_Plus_arm64-ab-11.0-20211011-UNOFFICIAL.img.xz
*Unofficial Android 12 :
1.Pixel Experience 12.0 v400.e
Thanks for ponces
Full googel rom. my used 5 day . 1 bug : bootanimation not vew full size
Download link :PixelExperience_arm64-ab-12.0-20211226-UNOFFICIAL.img.xz