Database Users

[Q] loop device

Sorry for the totally newbie question (for both android and linux).
I've rom images from legend ruu: android-info.txt, boot.img, hboot_legend_7227_1.01.0000_101108.nb0, radio.img, rcdata.img, recovery.img, splash1.nb0, system.img, userdata.img.
Is there any way to mount them (especially boot.img, recovery.img and system.img) on a linux box using a loop device?
The files boot.img and recovery.img are starting with magic word "ANDROID!°¨#", while I cannot recognize any string in system.img. What kind of file systems are these?
Thank you in advance,
TiceRex

system.img should just be a yaffs image and can be mounted loopback if you have the yaffs drivers installed. boot.img and recovery.img are ramdisk images which consist of a kernel and a cpio archive (containing the files for the root filesystem) bundled together in a package. HBOOT loads the kernel first, then unzips the cpio archive into a newly created ramdisk. Once all is loaded, execution is passed off to the kernel which has a nice ramdisk full of the init files needed for the remainder of the boot process. system and data images are then mounted to mountpoints in the ramdisk.
To extract and manipulate boot.img and recovery.img, see this thread:
http://forum.xda-developers.com/showthread.php?t=551711

Thank you very much.
Seeing into dsixda's rom kitchen scripts I was able to extract the boot.img and recovery.img files (and found the kernel and initrd).
I will look for the yaffs drivers.
Regards, TiceRex

[Q] How do I package a zip file from the boot.img produced from kernel compile?

Hi,
I have compiled a note 3 kernel and packaged up a boot.img. I would like to flash via CWM Recovery with a zip file. How do I take the boot.img that was generated and place it within a zip for flashing? Is there some signing that needs to take place? I've noticed a META-INF directory in some kernel binaries that I've downloaded and checked.
Thanks for any help!

solved
xrebecca_kelly1993x said:
Hi,
I have compiled a note 3 kernel and packaged up a boot.img. I would like to flash via CWM Recovery with a zip file. How do I take the boot.img that was generated and place it within a zip for flashing? Is there some signing that needs to take place? I've noticed a META-INF directory in some kernel binaries that I've downloaded and checked.
Thanks for any help!
Click to expand...
Click to collapse
I'm not quite sure yet on how to zip the newly packaged boot.img into a zip for flashing with CWM, but I did figure out how to flash regardless. CWM simply does this too.
adb push boot_repacked.img /sdcard/
adb shell su -c "dd if=/sdcard/boot_repacked.img of=/dev/block/platform/dw_mmc.0/by-name/BOOT"

Convert a twrp backup to flashable zip!

Might be quite helpful for many I think as myself was looking for this.
What worked for me on Win 10 Pro x64 using CYGWIN:
1)First unpack the TWRP backup archive.
2)Then grab the two files named:
system.ext4.win000
system.ext4.win001
3)Next rename these files to:
system.ext4.win000.tar
system.ext4.win001.tar
4)Download and Install CYGWIN
5)Go to:
C:\cygwin64\home\YOURUSERNAMEHERE
6)Create a folder named "untar"
7)Now type these command in CYGWIN Terminal
Code:
[COLOR="Red"]cd c:/[/COLOR]
Code:
[COLOR="Red"]cd C:/cygwin64/home/YOURUSERNAMEHERE/untar[/COLOR]
Code:
[COLOR="Red"]tar -xvf system.ext4.win000.tar
tar -xvf system.ext4.win001.tar[/COLOR]
8)That's it! The /system folder was just unpacked to the /untar dir we just created before. Now you can
We need a couple of more things yet:
9)Collect the 'boot.emmc.win' file from the unpacked TWRP archive and rename it to boot.img.
9.1)Optional. Collect the 'logo.emmc.win' file from the unpacked TWRP archive and rename it to logo.img.
10)Now collect a META-INF folder from any custom rom which is made for K3 Note (yes there are many! :laugh: )
We have all the files! Now we need just to create a zip file!
11)Select the META-INF,system and boot.img and create an archive using WinRAR, 7zip or similar.
Optional: Add also the logo.img in the zip if it's present in the TWRP backup.
12)Done.
Credits: @carl1961

911-Future_Maker said:
Might be quite helpful for many I think as myself was looking for this.
What worked for me on Win 10 Pro x64 using CYGWIN:
1)First unpack the TWRP backup archive.
2)Then grab the two files named:
system.ext4.win000
system.ext4.win001
3)Next rename these files to:
system.ext4.win000.tar
system.ext4.win001.tar
4)Download and Install CYGWIN
5)Go to:
C:\cygwin64\home\YOURUSERNAMEHERE
6)Create a folder named "untar"
7)Now type these command in CYGWIN Terminal
Code:
[COLOR="Red"]cd c:/[/COLOR]
Code:
[COLOR="Red"]cd C:/cygwin64/home/YOURUSERNAMEHERE/untar[/COLOR]
Code:
[COLOR="Red"]tar -xvf system.ext4.win000.tar
tar -xvf system.ext4.win001.tar[/COLOR]
8)That's it! The /system folder was just unpacked to the /untar dir we just created before. Now you can
We need a couple of more things yet:
9)Collect the 'boot.emmc.win' file from the unpacked TWRP archive and rename it to boot.img.
9.1)Optional. Collect the 'logo.emmc.win' file from the unpacked TWRP archive and rename it to logo.img.
10)Now collect a META-INF folder from any custom rom which is made for K3 Note (yes there are many! :laugh: )
We have all the files! Now we need just to create a zip file!
11)Select the META-INF,system and boot.img and create an archive using WinRAR, 7zip or similar.
Optional: Add also the logo.img in the zip if it's present in the TWRP backup.
12)Done.
Credits: @carl1961
Click to expand...
Click to collapse
How would I go about making a flashable Odin file from my TWRP backup? I want to flash it with Odin.

You are the best
Thanx Very Much

can we unpack backups taken from twrp-3.0.2 ?? I can't unpack them

It would be interesting to do the opposite. Owning boot.img, recovery.img, system.img and create a TWRP flashable backup.

When I unpack my backup created with TWRP, there is no "boot.emmc.win". I have data.ext4.win000, data.ext4.win001, and system.ext4.000 and the md5 hashes. That's it. Where do I find these? thanks

pwntrik said:
When I unpack my backup created with TWRP, there is no "boot.emmc.win". I have data.ext4.win000, data.ext4.win001, and system.ext4.000 and the md5 hashes. That's it. Where do I find these? thanks
Click to expand...
Click to collapse
I believe this would happen if you did not check the box for the Boot partition when you created the backup. If you make another backup with that box checked, you should see this file in the result.

is this possible to make it as a bat file to automate the process?

superbeef150 said:
I believe this would happen if you did not check the box for the Boot partition when you created the backup. If you make another backup with that box checked, you should see this file in the result.
Click to expand...
Click to collapse
Since I posted that, I figured out why there's no boot or recovery: TWRP doesn't give you the option in rbox's latest build (Not sure why?) You could easily use dd to make a backup of the boot and recovery sectors if you run Advanced>Terminal in TWRP.

hi..
I did all the steps but unfortunately it didn't work
---------------------------------------------------------------
Dr [email protected] ~
$ cd c:/
bash: cd: command not found

How to make a System.img file from rom.zip file

I have lots of custom roms as well as miui stock rom i don't like flashing via TWRP i want to make all those zip file to system.img file is there a way how to make a system.img file from rom.zip file i am currently working in a Ubuntu machine so any terminal operation is highly appreciated

Follow this tutorial.

[Guide] Unpack Update.app in phone

So there's threads about how to unpack UPDATE.APP on windows/PC/OS X so i decided why not do it on android too, this apps requires some additional tools to be downloaded just as OS X/Windows and linux needs as well. but process is otherwise similar. this tutorial doesn't need root!
NOTE THIS TUTORIAL isn't fully working on OREO on Huawei devices, it has some issues and i haven't found a workaround for it yet!​
Needed apps
Termux https://play.google.com/store/apps/details?id=com.termux
Recommended apps
Hacker keyboard
Needed files
https://github.com/atarii/split_updata.pl/blob/master/splitupdate
@Atarii 's modification of splitupdate to manually enter the partitions you want to unpack
The desired FW you wan't to unpack
Unpack process:
Download Termux
Open termux and type
termux-setup-storage This will allow termux to access your /sdcard
pkg install perl (this will install perl which the update.app process is using) once asked press y and enter.
copy the downloaded files to root of your SDCARD *We keep this simple*
Once copied type: cd storage
perl splitupdate UPDATE.APP partitionyouwanttoextract if everything goes well you should be good to go and having the selected files in a folder called output where selected files should be stored.
The unpack tutorial is done. But wait! If you want to browse the files you need to do one more thing or two.
Download android image kitchen
https://play.google.com/store/apps/details?id=com.redlee90.imagekitchenforandroid
This will allow you to *unpack boot/recovery and convert system image (also vendor, product, cust and version)
*in order to unpack a boot or recovery file you'll need to remove all code using a hex edit file until you see ANDROID text. Else it won't unpack. You can unpack aosp images easily with this tool and modify what you want and repack to flash it on your device tested with twrp image for honor 8.
I would suggest to not unpack/repack boot using this tool since it'll cause problem.
There's a python script that works to unpack boot and recovery which can be found https://github.com/liudongmiao/bootimg/blob/master/bootimg.py
For this you'll need to install python.
pkg install python and hit y and enter
Now you just do as the splitupdate part where you extract the file.
Command to unpack
python bootimg.py --unpack-bootimg similar is for ramdisk but you replace bootimg with ramdisk.
To repack just simply python bootimg.py --repack-bootimg
Please note if you repack ramdisk the boot might not work (it's a while since I tested this) now this covers up how you unpack boot and extract update.app from phone.
Credits to @Atarii for telling how to unpack boot on phone and for his custom splipupdate script
Sent from my FRD-L09 using Tapatalk

Known Issues:
If you get Killed when trying to extract system.img this is most likely because the image size is too big, this isn't due to small space available i guess its due to all ram is being taken yet i can't tell.
i get permission issues. yeah this can happen sometimes try chmod +x or chmod 0777 with root, it might help.
when typing termux-setup-storage i get lots of errors and i'm on 8.0 EMUI
This is not your fault it's a bug caused by android i'd guess, or app isn't adopted completely for 8.0