I have been trying to unpack the atrix system.img file from the stock gingerbread 4.5.91 build, but I can't seem to get it to work. I keep getting an error about a segmentation fault. I have tried it on linux (ubuntu), OSX and windows. Linux and OSX give me a segmentation fault using unyaffs. Windows just gives me a stack file. If anyone knows how to unpack and repack the atrix .img files in either three of the operating systems I would appreciate the help.
Read the forum rules, questions do not belong in this section of the forum - thats what the Q&A section is for. Mr. Clown, please move or delete this thread..
Related
I have been trying to unpack the atrix system.img file from the stock gingerbread 4.5.91 build, but I can't seem to get it to work. I keep getting an error about a segmentation fault. I have tried it on linux (ubuntu), OSX and windows. Linux and OSX give me a segmentation fault using unyaffs. Windows just gives me a stack file. If anyone knows how to unpack and repack the atrix .img files in either three of the operating systems I would appreciate the help.
ok so im trying to port for the first time to a i5800.
Now i have Ubuntu and the disxda's kitchen in it.
I've got the boot.img , system.img, data.img, zImage and factoryfs.rfs of my phone with me.
Now my questions are:
1. would a Froyo init.rc work for the ICS?
2. When i try to mount the factoryfs.rfs of my phone, the aplications i tried to use always gave an error stating its not a valid CD image or somethingsimimlar(ive used UltraISO and MagicISO)
3. When i try to extract boot.img using disxda's kitchen, it says Android header not found in boot.img or anywhere in the boot.img and the kernel pagesize is 0.
4. i dont want an Update.zip instead i want it like a flashable rom(are they the same?)
Any help would greatly be appreciated.
Hello,
I searched a lot for a tutorial showing how to repack or create a boot.img with a newly compiled zImage BUT didn't find a valid one for S3.
I'm using kubuntu 13.04 and the kernel compilation (update10) succeeded as I (painly) managed to arrange the build environment.
I then tried to use abootimg to unpack another boot.img but both the command of update or create boot.img are failing because of size mismatch ...
Can anybody help me ? It's the last step keeping me away from entering the S3 kernel development world
Try XDA Development hacking Android Chef Central etc .
jje
Hey guys,
I'm currently in the middle of developing my own ROM for an S802 based TV box (M8). I am close to releasing but I have a few issues, one very much in particular. I am trying to find a script that will extract a .tar file to the /sdcard/ directory on first boot of the ROM but I'm having a hell of a time. I am a reseller of these boxes and I'm trying to get my Kodi userdata to extract into the proper directory, /sdcard/Android/data/, on first boot but nothing I do seems to be working. Currently I'm using a script called installApk.sh. From what I've gathered it works fine for extracting .tar files to non-sdcard directories but when I attempt to point the extract path of the tar to the /sdcard/ directory it fails. I've also tried decompiling the kodi apk, injecting all of my userdata directly into the apk and re-signing but that causes all of the addons to fail. I'm wondering if any of you have run into a similar issue or know a solution to my problem. Any help is appreciated. Thanks.
Mag
th3magpi3 said:
Hey guys,
I'm currently in the middle of developing my own ROM for an S802 based TV box (M8). I am close to releasing but I have a few issues, one very much in particular. I am trying to find a script that will extract a .tar file to the /sdcard/ directory on first boot of the ROM but I'm having a hell of a time. I am a reseller of these boxes and I'm trying to get my Kodi userdata to extract into the proper directory, /sdcard/Android/data/, on first boot but nothing I do seems to be working. Currently I'm using a script called installApk.sh. From what I've gathered it works fine for extracting .tar files to non-sdcard directories but when I attempt to point the extract path of the tar to the /sdcard/ directory it fails. I've also tried decompiling the kodi apk, injecting all of my userdata directly into the apk and re-signing but that causes all of the addons to fail. I'm wondering if any of you have run into a similar issue or know a solution to my problem. Any help is appreciated. Thanks.
Mag
Click to expand...
Click to collapse
see Introduction : How to build an Android ROM - XDA-University
[GUIDE] [how to] CREATE OWN ROM [FOR ANY ANDROID DEVICE] [FOR N00B] [EASIEST METHODS] by lokeshsaini94
This thread will be moved to Android Q&A, Help & Troubleshooting
Hi everyone, I hope you're doing great
So, I'm currently trying to debloat some XOS ROMs which is Infinix's official firmware.
I have a problem repacking product.img since it doesn't have file_contexts which is required by the tools that repack .img files
IJoseph23 said:
Hi everyone, I hope you're doing great
So, I'm currently trying to debloat some XOS ROMs which is Infinix's official firmware.
I have a problem repacking product.img since it doesn't have file_contexts which is required by the tools that repack .img files
Click to expand...
Click to collapse
Hello and good afternoon, @IJoseph23
Welcome to XDA! I hope you'll always get the support you require.
However, prior to your next posting please read the guidances that are stuck on top of every forum like
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com
and the others. I've moved your thread to Android Q&A.
Thanks for your cooperation!
Regards
Oswald Boelcke
Senior Moderator
these kind of img files are partition images of linux file systems, sometimes sparsed with simg2img to reduce file size.
usually, partition images can mounted in linux only, same as partitions. windows is not capable of mounting linux file systems natively.
"extracting" linux images on windows is just some nasty hack and not intended for "repacking", because windows file system (NTFS) cannot handle linux file names and its metadata (like permissions, uid/gid, secontext)
the proper way is to mount (EXT4) partition image on linux, delete files, and unmount it.
additionally it might need img2simg/simg2img (not for dynamic partitions on super partition)