Develop Bugs

How to install recovery stock images

hey happy new year guys i searched alot but no luck , i downloaded recovery stock rom 10.0.17.0 from here
https://mirom.ezbox.idv.tw/en/phone/daisy/roms-global-stable/
but when i try to flash it from recovery i get an error what is proper way to install it (knowing that i'm on 10.0.3.0 ) please asap ??

If I'm not mistaken, I think that the link you provided is to a file that will contain a payload.bin, which would also need to be extracted. Maybe try from this link and extract the tgz & tar file to gain access to flash_all.bat/images.
I also had errors trying to flash the image as well but the path to the flash file was long (N:\Android\Xiaomi\Images\daisy_global_images_V10.0.17.0.PDLMIXM_9.0-2). When I simply moved the folder to the N drive it worked beautifully (N:\daisy_global_images_V10.0.17.0.PDLMIXM_9.0-2).
Hope that helps & good luck!

farrouk said:
hey happy new year guys i searched alot but no luck , i downloaded recovery stock rom 10.0.17.0 from here
https://mirom.ezbox.idv.tw/en/phone/daisy/roms-global-stable/
but when i try to flash it from recovery i get an error what is proper way to install it (knowing that i'm on 10.0.3.0 ) please asap ??
Click to expand...
Click to collapse
To install that, maybe TWRP can do it?
Else you will need to extract the images from payload.bin (use payload dumper) and flash each image using fastboot.
Probably flash them to the other slot and then change active slot. But you won't need to do that since you're flashing from fastboot.

a1291762 said:
To install that, maybe TWRP can do it?
Else you will need to extract the images from payload.bin (use payload dumper) and flash each image using fastboot.
Probably flash them to the other slot and then change active slot. But you won't need to do that since you're flashing from fastboot.
Click to expand...
Click to collapse
twrp doesnt do it and payload dumper seems alot of work it's okay i found fastboot rom of 10.0.17.0 , anyway my trouble now is what is the proper way to install magisk and twrp along side ? please

farrouk said:
twrp doesnt do it and payload dumper seems alot of work it's okay i found fastboot rom of 10.0.17.0 , anyway my trouble now is what is the proper way to install magisk and twrp along side ? please
Click to expand...
Click to collapse
I followed this using offain's TWRP. Rather than pushing the files with adb, I had them loaded on my sd card. Just follow the guide & you'll be good.
Link not working - remove spaces below:
https://www.the custom droid .com/install-twrp-recovery-root-xiaomi-mi-a2-a2-lite/

mn1968 said:
I followed this using offain's TWRP. Rather than pushing the files with adb, I had them loaded on my sd card. Just follow the guide & you'll be good.
Link not working - remove spaces below:
https://www.the custom droid .com/install-twrp-recovery-root-xiaomi-mi-a2-a2-lite/
Click to expand...
Click to collapse
thnx i'll give it a try and feedback

How do I extract a boot image from a GSI rom without TWRP.

I recently bought a Chinese phone from a relatively unknown manufacturer, so I was unable to find any TWRP images that match the device, I was wondering if it was possible to extract the boot image directly from a GSI ROM. My end goal is to install Magisk so if there is a better way to go about this please let me know.

can you tell model and brand

Hsnmastoor said:
can you tell model and brand
Click to expand...
Click to collapse
Thank you for replying,
The phone is the Cubot X20 pro, it is running the Unofficial Pixel Experience GSI ROM.

XDA-Developer30 said:
Thank you for replying,
The phone is the Cubot X20 pro, it is running the Unofficial Pixel Experience GSI ROM.
Click to expand...
Click to collapse
your welcome its mediatek download stock rom extract it and port twrp with hovatek twrp porter

Hsnmastoor said:
your welcome its mediatek download stock rom extract it and port twrp with hovatek twrp porter
Click to expand...
Click to collapse
Mediatek (MTK) Auto TWRP recovery porter by Team Hovatek
If you wish to root your Mediatek Android phone, we'd dropped a guide on rooting using Magisk and stock boot.img at https://www.hovatek.com/forum/thread-21427.html , no custom recovery is required. Se
forum.hovatek.com

Due to my understanding, GSI have no boot.img , it uses stock boot image ( along with all other needed partitions ). So if your purpose is to root using Magisk, just find the correct boot.img of the current stock firm on your device before GSI and patch it with Magisk!

LinhBT said:
Due to my understanding, GSI have no boot.img , it uses stock boot image ( along with all other needed partitions ). So if your purpose is to root using Magisk, just find the correct boot.img of the current stock firm on your device before GSI and patch it with Magisk!
Click to expand...
Click to collapse
Thank you for the reply, I forgot to mention that I used Hsnmastoor's method successfully.

LinhBT said:
Due to my understanding, GSI have no boot.img , it uses stock boot image ( along with all other needed partitions ). So if your purpose is to root using Magisk, just find the correct boot.img of the current stock firm on your device before GSI and patch it with Magisk!
Click to expand...
Click to collapse
I use the boot.img file from the stock rom of my device, I patch it with magisk but I always end up in bootloop
how can i root my device?

elmapq said:
I use the boot.img file from the stock rom of my device, I patch it with magisk but I always end up in bootloop
how can i root my device?
Click to expand...
Click to collapse
And your device is...???

LinhBT said:
And your device is...???
Click to expand...
Click to collapse
Tecno Spark 6 ke7

LinhBT said:
And your device is...???
Click to expand...
Click to collapse
I have a Vortex V22 MTM6761 There is no stock rom. It has unofficial GSI Pixel experience plus 13.0 running on it. I too would like to root. How can I retrieve the boot.img file from the GSI rom? Or how can I pull it from the phone via terminal and fastboot? All help is greatly appreciated! Happy Saint Patricks Day!

For devices which powered by MediaTek SOC, after flash the patched boot.img, you will need to flash patched blank vbmeta.img in order to bypass AVB with follow command :
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
in which vbmeta.img is a patched blank vbmeta of your device

LinhBT said:
For devices which powered by MediaTek SOC, after flash the patched boot.img, you will need to flash patched blank vbmeta.img in order to bypass AVB with follow command :
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
in which vbmeta.img is a patched blank vbmeta of your device
Click to expand...
Click to collapse
Thank you for the quick reply. I'm not sure I quite understand your message.
Flashing a vbmeta.img will give me a boot.img? I have a GSI PixelExperience 13.IMG file. The command fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img was flashed along with it. It was running a different rom prior to flashing the GSI PixelExp 13.IMG
All I want to do is Root the device. I've been told over and over I need the boot.img partition to modify for Root access, but I can't get unless i'm in Root or have access to the current ROM BOOT.IMG, Correct?
Why is the BOOT.IMG or Payload.BIN missing from GSI IMG ROMS? is there another way to convert or pull from a ROM like that?

defcondoc said:
Thank you for the quick reply. I'm not sure I quite understand your message.
Flashing a vbmeta.img will give me a boot.img? I have a GSI PixelExperience 13.IMG file. The command fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img was flashed along with it. It was running a different rom prior to flashing the GSI PixelExp 13.IMG
All I want to do is Root the device. I've been told over and over I need the boot.img partition to modify for Root access, but I can't get unless i'm in Root or have access to the current ROM BOOT.IMG, Correct?
Why is the BOOT.IMG or Payload.BIN missing from GSI IMG ROMS? is there another way to convert or pull from a ROM like that?
Click to expand...
Click to collapse
Yep, I think u misunderstanding me from my very first msg. What I meant back there was : GSI ROM is what called Generic System Image. Which means, it has ONLY system.img that you will need to flash into system partition of the device. Therefore, if you need the boot image in order to patch it with Magisk or else, you will need to extract the boot.img of the CURRENT ROM which is already running on your device ( and normally, it should be stock ROM ). Cuz to be in short, GSI ROM does not have any boot.img for you to seek for, my friend!

.

LinhBT said:
Yep, I think u misunderstanding me from my very first msg. What I meant back there was : GSI ROM is what called Generic System Image. Which means, it has ONLY system.img that you will need to flash into system partition of the device. Therefore, if you need the boot image in order to patch it with Magisk or else, you will need to extract the boot.img of the CURRENT ROM which is already running on your device ( and normally, it should be stock ROM ). Cuz to be in short, GSI ROM does not have any boot.img for you to seek for, my friend!
Click to expand...
Click to collapse
Thank you for the message my friend. I understand that part of it. There is no stock ROM, at least I don't think there is on it. It is a a/b system but I've tried to go back to factory reset but it does not work and goes into a boot loop. So I load the GSI pixel experience rom to get it working again.
So what you are saying is, if I do not have the stock ROM, I cannot get the BOOT.IMG, Correct? So I am pretty much out of luck to get a boot.img from a GSI? Is there another generic ROM I could use that would have a boot.IMG? Ive tried a dozen ROMS and the latest pixel experience 13 unofficial rom was the only one that worked. Maybe Im trying the wrong ROM's. I do know I need A/B versions of them, I think.
If anyone else might know a way to help get me out of this situation, I would greatly appreciate. Thank you my friends!

defcondoc said:
Thank you for the message my friend. I understand that part of it. There is no stock ROM, at least I don't think there is on it. It is a a/b system but I've tried to go back to factory reset but it does not work and goes into a boot loop. So I load the GSI pixel experience rom to get it working again.
So what you are saying is, if I do not have the stock ROM, I cannot get the BOOT.IMG, Correct? So I am pretty much out of luck to get a boot.img from a GSI? Is there another generic ROM I could use that would have a boot.IMG? Ive tried a dozen ROMS and the latest pixel experience 13 unofficial rom was the only one that worked. Maybe Im trying the wrong ROM's. I do know I need A/B versions of them, I think.
If anyone else might know a way to help get me out of this situation, I would greatly appreciate. Thank you my friends!
Click to expand...
Click to collapse
You need to understand the basic core point is : GSI is ALWAYS system image only my friend. Boot.img can be found only on FULL ROM, not GSI. And there's always stock ROM for ANY DEVICES, what you need to do is just Google with keywords : Your-Device-Full-name Stock ROM Download. Then choose the correct one which is currently running on your device and download it. Boot.img will be right there on the zip.

LinhBT said:
You need to understand the basic core point is : GSI is ALWAYS system image only my friend. Boot.img can be found only on FULL ROM, not GSI. And there's always stock ROM for ANY DEVICES, what you need to do is just Google with keywords : Your-Device-Full-name Stock ROM Download. Then choose the correct one which is currently running on your device and download it. Boot.img will be right there on the zip.
Click to expand...
Click to collapse
Thank you! I do realize the obvious. If I was able to find it, I wouldn't be asking for help. I have rooted close to a hundred phones with stock ROM's going back over a decade.
What I'm asking is, What if the stock rom cannot be found? There is no other alternative way? I challenge finding this particular stock ROM.
Vortex V22 Model 2ADLJ-V22 MT6761V/WBB.
I have searched over and over for months on various search engines and found nothing. Maybe the ROM is uploaded somewhere in a different language other than English. I would be absolutely stunned if the stock rom was found on the internet.
Can I extract boot.img from terminal via fastboot or other linux or win program?

I have 2 models I cannot find stock ROM's for:
Vortex V22 Model 2ADLJ-V22 MT6761V/WBB - manufacture date year 2022
Moxee M2160 Model MH-T6000 2APQU-MH-T6000 Q6006_V1.0 - manufacture date year 2022
Can anyone find anything? I have scoured the web for months!
I can't believe there is nothing available for these phones.
Please let me know if you can find a stock ROM. I would love to learn where and how you found them. As I've have found nothing for months and months.
Thank you!!!

defcondoc said:
Thank you! I do realize the obvious. If I was able to find it, I wouldn't be asking for help. I have rooted close to a hundred phones with stock ROM's going back over a decade.
What I'm asking is, What if the stock rom cannot be found? There is no other alternative way? I challenge finding this particular stock ROM.
Vortex V22 Model 2ADLJ-V22 MT6761V/WBB.
I have searched over and over for months on various search engines and found nothing. Maybe the ROM is uploaded somewhere in a different language other than English. I would be absolutely stunned if the stock rom was found on the internet.
Can I extract boot.img from terminal via fastboot or other linux or win program?
Click to expand...
Click to collapse
You CAN extract the boot.img via terminal ONLY IF you're on a ROOTED devices!

Question 1.2.5.5 AA Boot image request

Anyone have the boot image for OOS of 11.2.5.5 AA ?

11.2.5.5 isn't out for AA I don't think ...

avid_droid said:
Correct. It's not. Posted the link cause seems like he doesn't want to look and he can spam the link to when they post the boot.img there haha
Click to expand...
Click to collapse
No i I'm not trying to spam it just that most of time usually someone just posts the boot image within a thread that asks for the boot image of the certain one
I've already seen that thread you posted.

This is 11.2.5.5 AA boot image, I copy it from magisk backup, it's Untouched

xls654 said:
This is 11.2.5.5 AA boot image, I copy it from magisk backup, it's Untouched
Click to expand...
Click to collapse
That's a negative on the boot.img. Unsupported file, patched failed.

xls654 said:
This is 11.2.5.5 AA boot image, I copy it from magisk backup, it's Untouched
Click to expand...
Click to collapse
I'm guessing you have to zip the file before you post it here cause it'll mess with it

Is the 11.2.5.5 AA boot image posted on #7 valid?

see post #8

11.2.5.5AA boot.img, stock and magisk patched:
11.2.5.5AA-boot.zip - Shared with pCloud
Keep, share and access your files whenever you need from wherever you are. Create a free pCloud account and make your life easier.
u.pcloud.link

schmeggy929 said:
That's a negative on the boot.img. Unsupported file, patched failed.
Click to expand...
Click to collapse
gunzip it before magisk patch

[OP7T][Stock/Magisk] OxygenOS 11.0.5.1.HD65AA boot.img

OnePlus 7T OxygenOS 11.0.5.1.HD65AA Global boot.img
Stock: https://mega.nz/file/WQF3DQKK#DP82spRyHgWcng4E93bXBRwVjtfp9mbG_b9DJZMUZHE
Magisk v23.0 Patched: https://mega.nz/file/aYF1FIzD#owemDLp98DFfVjHfdaM5jAr8cyOiwosMIxUd4h3O7kc

Hi
I haven't updated my phone for awhile. Why should we use a patched Magisk? Can I just follow the usual steps to keep my Magisk application & root before update ? ('install in inactive space, ater OTA')
Thanks

morback said:
Hi
I haven't updated my phone for awhile. Why should we use a patched Magisk? Can I just follow the usual steps to keep my Magisk application & root before update ? ('install in inactive space, ater OTA')
Thanks
Click to expand...
Click to collapse
You shouldn't use patched Magisk if you've followed the usual steps to retain root after OTA. This is meant for those who did it otherwise.

thexile said:
You shouldn't use patched Magisk if you follow the usual steps to retain root after OTA. This is meant for those who did it otherwise.
Click to expand...
Click to collapse
Yes, in the meantime I went like I usually did to update and everything is fine. Thank you!

Thanks again!!! Thank you for all your assistance here. It's appreciated.

what can i do if my mobile stuck in a boot loop if this boot img did not work

this boot.img file size is 96 mb but i have extracted the real boot.img file from payload.bin of this update and its size is 101mb so you are faking us please dont provide wrong stuff like this you can make many mobile to stuck in a bootloop.

[email protected] said:
this boot.img file size is 96 mb but i have extracted the real boot.img file from payload.bin of this update and its size is 101mb so you are faking us please dont provide wrong stuff like this you can make many mobile to stuck in a bootloop.
Click to expand...
Click to collapse
Strong accusation without any proof. Anyway, whether you want to use my files is entirely up to you. If you think I have malicious intents, please GTFO.

thexile said:
Strong accusation without any proof. Anyway, whether you want to use my files is entirely up to you. If you think I have malicious intents, please GTFO.
Click to expand...
Click to collapse
Thanks daddy

Question how to extract boot image for OOS F.15 update?

Hi
Can anyone provide me the boot image for OOS F.15 update.
these updates are just problem sometimes. is there an easy method to find or extract the boot image as most of the roms are not not available online.
I have tried using oxygen updater and payload dumper and various other methods but to no avail. I am unable to extract boot.img.

Is there any other method for the same or can anyone provide me with the boot image.

Here it is

penguinus said:
Here is it
Click to expand...
Click to collapse
Thank you for the link. thank you for the help.
I hav tried to download it but keep getting an invalid SSL Certificate error(code 526) / androidfilehost.com Host Error .
Is there any alternative link for the file.

Oops, AFH is down today.
Try this one

penguinus said:
Oops, AFH is down today.
Try this one
Click to expand...
Click to collapse
Thank you once again.
may i ask how does one go about extracting the boot.img from bin file.

The easiest way is to use fastboot enhance tool for windows. It allows to extract any partititon from Full OTA update (it is usually about 4-6Gb). Note that it doesn't support incremental OTA.

Thank you i am looking forward to using fastboot enhance.
I have used the tool and it works great wonderful windows based simple app.