Hi everyone,
I been trying to edit, unpack and repack vendor.img and vbmeta.img (or make a new one) but having trouble making the changes. After some hours of Googling, I was able to mount vendor.img in Ubuntu but it was mount in a read only state and as not being the owner I was unable to make changes.
I am attempting to enable my phone to work in China. The files exist on the phone but are not being pointed to by vendor/.../mbn_sw.txt
There doesn't seem to be any good guides for packing and unpacking these image files. I don't mind what OS I must use to do so just would like to figure this out.
Thanks in advance!
jkoch3 said:
Hi everyone,
I been trying to edit, unpack and repack vendor.img and vbmeta.img (or make a new one) but having trouble making the changes. After some hours of Googling, I was able to mount vendor.img in Ubuntu but it was mount in a read only state and as not being the owner I was unable to make changes.
I am attempting to enable my phone to work in China. The files exist on the phone but are not being pointed to by vendor/.../mbn_sw.txt
There doesn't seem to be any good guides for packing and unpacking these image files. I don't mind what OS I must use to do so just would like to figure this out.
Thanks in advance!
Click to expand...
Click to collapse
Got solution?
Related
Does anyone know how to go about modifying the recovery partition? I've been unable to even extract the files. I can't mount /dev/block/mtdblock2 (in recovery or out of it), and I can't mount a loop back device off any of the recovery.img's..
Any help would be appreciated. Thanks!
*bump* Someone out there knows an answer to this. I can feel it ;-)
I've figured it out more or less. For those of you who stumbled onto this post by searching and are wondering the answer, it appears boot.img and recovery.img are raw images containing a concatenated kernel and ramdisk. The good news is there's a perl script that can extract them, found here under alternative method.
phazen18 said:
I've figured it out more or less. For those of you who stumbled onto this post by searching and are wondering the answer, it appears boot.img and recovery.img are raw images containing a concatenated kernel and ramdisk. The good news is there's a perl script that can extract them, found here under alternative method.
Click to expand...
Click to collapse
Thank you! I've been searching for 2 days on how to access mtdblocks0-3!
I cannot find a method in Linux or Windows that will allow me to access the files in the system.img partition image from:
RUU_ENDEAVOR_U_ICS_40_hTC_Asia_SEA_WWE_1.29.728.12_Radio_1.1204.105.14_release_261350_signed.exe
I have never had a problem "unpacking" system.img files from other HTC phones using unyaffs or even in Windows with WinImage for EXT2/3/4 partitions.
Obviously many Devs have had success with the HOX system.img! Could someone please tell me what file system the system partition uses AND/OR reveal the correct approach to accessing the files within the img?
I presume the partition formats are identical in:
RUU_ENDEAVOR_U_ICS_40_hTC_Asia_SEA_WWE_1.28.728.9_Radio_1.1204.103.14_release_256493_signed.exe
...so I suppose there's no point in making an attempt with its system.img either!
Any help will be greatly appreciated!!
Thanks in advance.
BTW: I'm not one who asks for assistance as his 1st move.
I have been searching for resolution to this problem for @least a week!
Using appropriate keywords the best I have come up with is either others in this same predicament or suggested remedies which are not effective.
The overall picture I have got is that those with the solution seem reluctant to share the knowledge, which I find strange in development communities.
if you want just access to files inside the img, in windows use this jar attached to convert it to ext4 and then mount with DiskInternals Linux Reader.
or in linux use this tool to unpack.
http://forum.xda-developers.com/showthread.php?p=28837507#post28837507
don't even try to repack it will not work.
if you know how it posible to repack files to this img format please let me know.
Thanks heaps avicohh!
I solved the problem only a few hours before your post came in.
I used a slightly different approach through linux but basically same process & result.
If you follow this:
http://forum.xda-developers.com/showthread.php?t=1081239
you'll be able to unpack AND repack but it's done in linux.
I used Ubuntu 12.04 LTS (64bit) to compile & use the ext4_utils in the thread above.
Since you were so kind to answer my query please feel free to PM me if i can help you!! My use of the forum is sometimes sporadic though, unfortunately.
EDIT: Sorry, just realised we both had the same thread! So it doesn't work for repacking?? I'll see if I can find something that works.
Obviously something does but there's not as much free sharing of really useful stuff as I would have expected with this kind of thing.
Yap.. is the same thread.
probably the odin (samsung) img and the stock htc img they not exactly the same format.
i seraching after sulution to this thing because i'm trying to make custom rom to be able to flash on device with stock rom/locked bootloader from the stock recovery like the ruu firmwares.
Good day all,
I am hoping someone can help me out and explain what I am not doing correct or point me in the right direction.
I have been reading the forums for quiet some time and have learned alot and want to thank everyone for their posts.
My question is I have taken apart the combination file and have been able re create the tar ball and successfully push it back onto the phone. ( I know some of these eng boot and combination files are digitally signed and I have not figured out how to confirm this). The issue is when I push this file with odin it wipes the user data which is the issue.
I then began digging deeper into the img files and located within the cache.img/recovery/command:
--carry_out=csc_factory
--wipe_data
Which will wipe the data. I have tried removing this along with changing the csc_home which would not wipe the user data if I understand this correctly. Once I modify the file I change the permissions back to read only and convert the cache.img to an android sparse file and create the tar-ball. I am now going through the system.img and boot.img to see if I can possibly modify these to bypass mounting the cache.img.
I am not sure if any of this will work and not sure why its not working so any advice would be very helpful.
Thanks,
San
I downloaded a samsung galaxy s22 Odin firmware and unpacked the zip and the AP tar file and then I un lz4'd the super.img, unsparsed it and then I ran lpunpack on the unsparsed image to get unreadable images
Have you used one of the following?
Extract system.img,vendor.img and product.img from super.img
After lots of search i found a way to extract those img file from super.img What is need? 1.Computer with linux os. extract zip file from this post and place your super.img in same location where you extract.. then run below cmd... simg2img...
forum.xda-developers.com
super_img_lpmake_lpunpack.zip | by MrWaehere for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
ze7zez said:
Have you used one of the following?
Extract system.img,vendor.img and product.img from super.img
After lots of search i found a way to extract those img file from super.img What is need? 1.Computer with linux os. extract zip file from this post and place your super.img in same location where you extract.. then run below cmd... simg2img...
forum.xda-developers.com
super_img_lpmake_lpunpack.zip | by MrWaehere for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Click to expand...
Click to collapse
I have. I can get system.img out but I can't open it. I think it's a f2fs partition but I haven't found any tools that can extract files from it
It seems on newer firmware this method of unpacking and extracting system.img out of super.img no longer works. It seems now that when you extract system.img from super.img.raw it gives you a file that reads just as data and does not have the ext4 filesystem magic header bytes.
Have uploaded two screenshots to show how super.img.raw looks and how system.img looks after extraction from super.img. Any thoughts on this?
This firmware is being pulled from latest tar files for SM-S901U
Update, am working on a way and almost got it now. Will probably create a post on this once done and link from here. If you dont hear back from me, i failed. :'(
UPDATE: had some luck following this guys tutorial although a little different was able to extract files. Still cant mount but much closer. Device is f2fs file system. The reason it's not working is most methods on xda are for ext4
How to Extract F2FS Image from Android Device Flash - Baremetallics
How to Extract F2FS Image from Android Device Flash
baremetallics.com
kalexander7 said:
Update, am working on a way and almost got it now. Will probably create a post on this once done and link from here. If you dont hear back from me, i failed. :'(
UPDATE: had some luck following this guys tutorial although a little different was able to extract files. Still cant mount but much closer. Device is f2fs file system. The reason it's not working is most methods on xda are for ext4
How to Extract F2FS Image from Android Device Flash - Baremetallics
How to Extract F2FS Image from Android Device Flash
baremetallics.com
Click to expand...
Click to collapse
Is this also work for other's like erofs?
Mr Hassan said:
Is this also work for other's like erofs?
Click to expand...
Click to collapse
I doubt it although it may be alike using same linux tools like fsck. Erm I'm still stuck on trying to get this f2fs image too mount. It seems corrupt and although I was able to extract libs and apks they're coming out corrupted. Anyone in the community have any knowledge in this area?
kalexander7 said:
I doubt it although it may be alike using same linux tools like fsck. Erm I'm still stuck on trying to get this f2fs image too mount. It seems corrupt and although I was able to extract libs and apks they're coming out corrupted. Anyone in the community have any knowledge in this area?
Click to expand...
Click to collapse
Bro samsung have many dev's to mount fsf2 and already many dude done
The erofs not possible
Mr Hassan said:
Bro samsung have many dev's to mount fsf2 and already many dude done
The **** is erofs
Click to expand...
Click to collapse
what?
Hello
I want to know when we extract payload
Then its have img files like this
System
System_ext
Vendor
Product
So my question is it this possible to unpack modify and repack and flash back?
Is there any window or linux tool?
Or easy way to done my jon?
Thanks
Not possible?
Google search "repack payload.bin" to start with....
TheGhost1951 said:
Google search "repack payload.bin" to start with....
Click to expand...
Click to collapse
Ahh i think i never explain it very well but let me tell
I dont need to repack as payload.bin
I need to unpack vendor and system to modify and repack
Then Google "unpack repack .img file"....
Maybe something like this?
Editing system.img inside super.img and flashing our modifications
I'm trying to modify my system.img (/system/build.prop) to include support for multi users. After struggling a lot, I've succeeded following your guide (that's an awesome work btw) to unpack, mount, modify, umount and repack super.img. Then...
forum.xda-developers.com
from oxygen 12 oneplus uses the EROFS
[GUIDE] Universal guide for making your partitions inside super read-writable again.
Disclaimer: I'm not responsible for any result of these operations. Please be careful and well prepared. Always have your important data backed up safely on other place. Hello everyone! As far as 2022 and Xiaomi gets their new phones updated...
forum.xda-developers.com
ChrisFeiveel84 said:
from oxygen 12 oneplus uses the EROFS
[GUIDE] Universal guide for making your partitions inside super read-writable again.
Disclaimer: I'm not responsible for any result of these operations. Please be careful and well prepared. Always have your important data backed up safely on other place. Hello everyone! As far as 2022 and Xiaomi gets their new phones updated...
forum.xda-developers.com
Click to expand...
Click to collapse
getting error already tired this
Mr Hassan said:
getting error already tired this
Click to expand...
Click to collapse
You have used the super Partition or the images from the payload.bin ?
ChrisFeiveel84 said:
You have used the super Partition or the images from the payload.bin ?
Click to expand...
Click to collapse
Ofcourse backup super part
But in payload its not super
Its all one by one like system
System_ext vendor odm
So backup make its whole super.img
I already make details thread about this
But not get any help
Mr Hassan said:
Ofcourse backup super part
But in payload its not super
Its all one by one like system
System_ext vendor odm
So backup make its whole super.img
I already make details thread about this
But not get any help
Click to expand...
Click to collapse
From oos 11 or oos 12 ?
ChrisFeiveel84 said:
From oos 11 or oos 12 ?
Click to expand...
Click to collapse
Bro os12
even not able to convert in raw
simg2img.exe super.img super.raw
Invalid sparse file format at header magic
Failed to read sparse file