How can a BOOT.IMG be extracted from an Android Phone if there is no Stock Firmware ROM available?

Search This thread

defcondoc

Senior Member
May 1, 2019
92
13
Hi! Are there any pro’s out there that can help out with some issues, we are having with 3 phones.
It would be greatly appreciated. I believe we are not the only ones.



How can a BOOT.IMG be extracted from an Android Phone if there is no Stock Firmware ROM available?

All 3 phones manufactured in 2022.

The Bootloader is unlocked for all 3. USB Debugging is turned on.

- Moxee m2160 MH-T6000 only boots to Fastboot & Recovery. I have tried to restore but it will not restore.

- Vortex V22 has a GSI Pixel Experience Plus 13 ROM installed and is unable to go back to factory ROM image.

- ANS ACK2326 is on a stock Android 12 ROM and hasn’t been modified but has a build number kirk2_v1 2.0_BTM-ST.


Is it possible to get a Generic BOOT.IMG to modify for root?

Are there other ROMS like GSI’s with a BOOT.IMG that could work to try to get root?

Are there other ways to get root without a BOOT.IMG?

Is there a way to parse the entire phone to compile a BOOT.IMG?

The manufacturers were contacted. No system firmware ROM is available online that we could find after searching. We don’t have any experience searching china websites or know where to begin. If someone knows where we could find the stock ROM's on a China website that would be a great help!

Are we SOL? Are phones that don’t publish stock firmware that secure that if you need a BOOT.img from stock firmware to get to access the entire encrypted rom, you are out of luck?

Or, would we need a Jtag hardware reader?

Thank you in advance for your time and help which is greatly appreciated!
 

V0latyle

Forum Moderator
Staff member
The boot image contains the kernel for that specific device; there is no such thing as a "generic boot image", as the kernel has to have the basic drivers for that specific device's hardware.

It's possible to dump the boot image if you already have root, but I'm assuming that the whole reason you want the boot image is to patch it with Magisk to gain root.

The alternative, if TWRP is available, is to use ADB through TWRP to dump the boot partition.

If you can't use TWRP and aren't rooted, there is no way to dump the boot partition through fastboot.
 
  • Like
Reactions: alecxs

defcondoc

Senior Member
May 1, 2019
92
13
The boot image contains the kernel for that specific device; there is no such thing as a "generic boot image", as the kernel has to have the basic drivers for that specific device's hardware.

It's possible to dump the boot image if you already have root, but I'm assuming that the whole reason you want the boot image is to patch it with Magisk to gain root.

The alternative, if TWRP is available, is to use ADB through TWRP to dump the boot partition.

If you can't use TWRP and aren't rooted, there is no way to dump the boot partition through fastboot.
Thanks you for the reply! That is correct. Our ultimate goal is to gain root on these devices. Is Magisk the only root pathway or are there other rooting options?

Can you use ADB Shell, ADB root and dd to pull the boot partitions?

There is not a TWRP available for these devices. How would you go about making a TWRP for these phones? Do you need the stock firmware?
 

V0latyle

Forum Moderator
Staff member
Thanks you for the reply! That is correct. Our ultimate goal is to gain root on these devices. Is Magisk the only root pathway or are there other rooting options?
No, but it is the most popular and arguably the best
Can you use ADB Shell, ADB root and dd to pull the boot partitions?
No, because again you need root to run adbd as root. I could be wrong...
There is not a TWRP available for these devices. How would you go about making a TWRP for these phones? Do you need the stock firmware?
I am not a developer so I have no idea but I imagine you'd need the original kernel source, yes.
 

alecxs

Forum Moderator
Staff member
Feb 17, 2016
4,262
7
2,999
gitlab.com
another risky way is to flash rooted GSI. but in case it boot loops, you are screwed without stock ROM. the user @gregeerg ended up with a semi bricked phone, luckily he was able to pull boot.img from adb, so another member @Jet! with same device could finally root his phone and provide super.img for unbrick. So this method is only working if you have two identical phones.
 
Last edited:

defcondoc

Senior Member
May 1, 2019
92
13
If u have mtk there are many options
1:using mtk client
2: using mtk bypass and wwr2

Then if u have snapdragon u need the gfil software and the phone firehose programmer
I actually had or was going to ask this if there is a way to access firmware from the hardware level. Somehow the post never got posted or deleted.

Anyway, with MTK Client & QFIL, how complicated is it to extract the firmware from a device? Will it work with all devices, or will I run into issues with newer devices? I will do some researching on these and see what I can find. Thank you!
 

defcondoc

Senior Member
May 1, 2019
92
13
another risky way is to flash rooted GSI. but in case it boot loops, you are screwed without stock ROM. the user @gregeerg ended up with a semi bricked phone, luckily he was able to pull boot.img from adb, so another member @Jet! with same device could finally root his phone and provide super.img for unbrick. So this method is only working if you have two identical phones.
Interesting. Where can I get a rooted GSI? I tried to searching but couldn't find anything. Is there a special way to search for one. I would be willing to try this. I had a boot loop on one and a unofficial unrooted PixelExp13 GSi fixed it.
 

defcondoc

Senior Member
May 1, 2019
92
13
Thank you! I'm assuming these are all GSI builds from LOS 16-20? Am I also correct in saying the difference in the bgN, bvN, bvS, files? b = a/b system, g = gapps installed, v = vanilla - no gapps installed. N = No Root? S = Root?

To get a GSI that is already rooted, I must install the file with S in the filename?
 
  • Like
Reactions: alecxs

defcondoc

Senior Member
May 1, 2019
92
13
OMG Thank you alecxs! Bravo! This is exactly what I was looking for! One install with no stock ROM rooted successfully!, two more to go. And especially thanks to andyyan for making this GSI image possible!
 

omb714.1980

Member
Feb 3, 2023
13
4
Project Treble
OMG Thank you alecxs! Bravo! This is exactly what I was looking for! One install with no stock ROM rooted successfully!, two more to go. And especially thanks to andyyan for making this GSI image possible!
May I ask you which of your devices listed above did you get it to work on the reason I ask is I have 2 of those phones am I'm trying to do the same thing. Thanks
 

defcondoc

Senior Member
May 1, 2019
92
13
May I ask you which of your devices listed above did you get it to work on the reason I ask is I have 2 of those phones am I'm trying to do the same thing. Thanks
The Vortex V22 I got to work successfully with a GSI root. I was able to get root with the Moxee but I have yet to get a custom rom or working GSI rom. I'll post when I get a working rom with the Moxee. The ANS has been a bit of trouble because I cannot get the BL unlocked even though it has OEM unlocking turned on.
 
  • Like
Reactions: omb714.1980

omb714.1980

Member
Feb 3, 2023
13
4
Project Treble
The Vortex V22 I got to work successfully with a GSI root. I was able to get root with the Moxee but I have yet to get a custom rom or working GSI rom. I'll post when I get a working rom with the Moxee. The ANS has been a bit of trouble because I cannot get the BL unlocked even though it has OEM unlocking turned on.
I'm having the same issue with the ANS your not alone.
 
  • Like
Reactions: defcondoc

defcondoc

Senior Member
May 1, 2019
92
13
Did anyone ever figure out how to unlock the bootloader yet?
I do know it is available somewhere and most likely password protected but to my knowledge it hasn't been made publicly yet. I'm still waiting as well. I've be able to do some workarounds with the stock rom but I would really like to get access to the firmware or boot image.
 
  • Like
Reactions: ronnieshane1
I do know it is available somewhere and most likely password protected but to my knowledge it hasn't been made publicly yet. I'm still waiting as well. I've be able to do some workarounds with the stock rom but I would really like to get access to the firmware or boot image.
I know right! I cant find hardly anything on the ACK2326 at all! I wish they would go ahead and make it public already.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Did anyone ever figure out how to unlock the bootloader yet?
    I do know it is available somewhere and most likely password protected but to my knowledge it hasn't been made publicly yet. I'm still waiting as well. I've be able to do some workarounds with the stock rom but I would really like to get access to the firmware or boot image.
  • 2
    I'm having the same issue with the ANS your not alone.
    I appreciate you letting me know. Good to know I'm not the only one.
    1
    The boot image contains the kernel for that specific device; there is no such thing as a "generic boot image", as the kernel has to have the basic drivers for that specific device's hardware.

    It's possible to dump the boot image if you already have root, but I'm assuming that the whole reason you want the boot image is to patch it with Magisk to gain root.

    The alternative, if TWRP is available, is to use ADB through TWRP to dump the boot partition.

    If you can't use TWRP and aren't rooted, there is no way to dump the boot partition through fastboot.
    1
    If u have mtk there are many options
    1:using mtk client
    2: using mtk bypass and wwr2

    Then if u have snapdragon u need the gfil software and the phone firehose programmer
    1
    1
    Did anyone ever figure out how to unlock the bootloader yet?
    I do know it is available somewhere and most likely password protected but to my knowledge it hasn't been made publicly yet. I'm still waiting as well. I've be able to do some workarounds with the stock rom but I would really like to get access to the firmware or boot image.