[Q] Mounting ext4 as data before boot + PA 2.00 - HD2 Android Q&A, Help & Troubleshooting and Genera

Hi everyone.
I'm trying to increase data partition storage by using ph03n!x walkthru on Paranoid Android 1.992 and 2.0. I'm stuck at extracting boot.img in Working folder. The rom.zip itself don't have boot.img or boot folder so after extracting PA rom in dsixda kitchen i copied boot.img from Nandroid backup on SD. But while im trying to extract that boot.img there's an error
Code:
Working folder found
Android 'magic' header not found at start of boot.img
Cheching if it exists elsewhere ...
Warning: Android header not found in boot.img (unsupported format)
Error: kernel offset (page size) is 0
Press Enter to continue
So i took recovery.img from nandroid backup, renamed it to boot.img and extracting went fine, but there was some problems: could not find init.htcleo.rc file and "on fs" lines in init.rc file
Any suggestions how to do it? I think that real init.rc is placet in boot.img (not recovery.img), but how to extract it?

Do you have a working folder setup? If you do, then forget about the boot.img, just place the 'boot' directory from the ROM's zip (under /kernel/). If you do not have a Working folder setup, then follow my instructions to create a temporary ROM zip with the required folders - meta-inf, system and boot.

ph03n!x said:
just place the 'boot' directory from the ROM's zip (under /kernel/)
Click to expand...
Click to collapse
Thanks a lot ph03n!x. It worked And also thanks for this great mod (Initrd.gz was great, now its time for this new method )

Related

[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 to change the initrd.gz boot image?

Hi guys,
Can anyone explain me how to change the boot image contained in initrd.gz?
Thank you vary much...
erestor6 said:
Hi guys,
Can anyone explain me how to change the boot image contained in initrd.gz?
Thank you vary much...
Click to expand...
Click to collapse
+1 for this, I'm trying to do the exact same thing! Check out this post to create the image in the correct format:
http://forum.xda-developers.com/showthread.php?t=537515
I created a logo.rle image from a 480x800 image (both attached) but don't know how to overwrite the one inside my initrd.gz file. I tried using 7zip but it seems that it is write-protected. If anyone knows how to do this, it would be much appreciated. I've changed all of the other boot screens but just want to change the green HTC logo if I can.
Thanks in advance
gargon01 said:
+1 for this, I'm trying to do the exact same thing! Check out this post to create the image in the correct format:
http://forum.xda-developers.com/showthread.php?t=537515
I created a logo.rle image from a 480x800 image (both attached) but don't know how to overwrite the one inside my initrd.gz file. I tried using 7zip but it seems that it is write-protected. If anyone knows how to do this, it would be much appreciated. I've changed all of the other boot screens but just want to change the green HTC logo if I can.
Thanks in advance
Click to expand...
Click to collapse
thank you very much..but I was arrived at that poit.
In second of me the normal procedure is wrong, there wil be some steps that will be immediate and that we don't know.
help please...
Yeah - now it's working on my HD2!
This method is applicable for firmware, which include the file initrd.gz in zip archive. Many firmwares are distributed as img files, and I have not tried to extract initrd.gz from there, though perhaps it is possible.
The file logo.rle is not the usual rle and programs for creating or convert rle can not create it, also You can not view logo.rle by any usual rle-viewer. I took logo.rle from another firmware, because I could not do it (it can be reached by 7zip from initrd.gz; or copied from root directory after boot by root explorer, if firmware is already installed).
For this process Linux on a PC required - terminal emulator on phone doesn't work correctly! I used Chaox Live CD because I use Windows on my PC.
I put the file initrd.gz (from my firmware) in a folder and the new logo.rle file near this folder. In a Linux terminal I entered to that folder (by command cd) and ran the commands:
gunzip initrd.gz
cpio -i < initrd
cp -f ../logo.rle
rm initrd
find . | cpio -o -H newc | gzip > ../initrd.gz
Than I change the original initrd.gz in the firmware to the one I created.
ps: Not necessarily replace the entire firmware to replace the file initrd.gz. You can replace only a boot partition. To do this, take the original files boot/zImage & META-INF/com/google/android/updater-script from the firmware and add Your own boot/initrd.gz & META-INF/com/google/android/updater-script. Now You can zip it and place the archive to the root of the sdcard. Than enter to MAGLDR-ADrecovery-install zip from sdcard
Archive must contain this 4 files with pathnames:
boot/initrd.gz
boot/zImage
META-INF/com/google/android/update-binary
META-INF/com/google/android/updater-script
file updater-script must containe this commands:
mount("MTD", "boot", "/boot");
package_extract_dir("boot", "/boot");
unmount("/boot");
In my case I use this firmware and logo.rle file from this firmware.
Hope it's will be helpfull!
I'm sorry - english is not my language.
Awesome work, vovchok!
However after reading your sequence of 'nix commands multiple times I have determined that the little white guy doesn't look bad at all.
My momma's boy ain't touching that.
I found this Thread . After reading, I landed here. Now this is where I just got stuck.
I'm using Hyperdroid and there is no initrd.gz. There's just a "boot.img" with ~3mb.
I still would like to change my second boot screen to fit in the boot sequence.
(I already mastered to create my own 1st bootscreen, flashed it, and changed my boot animation, but as said, I got stuck here finding a guide how to change the second boot screen.)
Any ideas?
smeee_again said:
I found this Thread . After reading, I landed here. Now this is where I just got stuck.
I'm using Hyperdroid and there is no initrd.gz. There's just a "boot.img" with ~3mb.
I still would like to change my second boot screen to fit in the boot sequence.
(I already mastered to create my own 1st bootscreen, flashed it, and changed my boot animation, but as said, I got stuck here finding a guide how to change the second boot screen.)
Any ideas?
Click to expand...
Click to collapse
Yeah - it's a lot more complicated to extract the initrd.gz file from a boot.img than it is from a ROM with a boot partition. I spent many hours trying to do it, and failed.
Currently just building a ROM with an edited initrd.gz file inside it. I know that the logo.rle file in the initrd.gz file is the correct image that I want (the stock white HTC screen) but I just don't know if I'm building the ROM with the correct options (using the Android Kitchen).
I'll report back with results, because I tried to do this a couple of months ago and failed, since the ROM required me to flash a separate kernel zip after the main ROM, which replaced initrd.gz, and I couldn't edit the initrd.gz file using the Android Kitchen because it was in a boot.img.
EDIT: Okay, just spent about 2 hours trying to change the damn image, having replaced initrd.gz with what was definitely the right one, and I boot it up and see the black HTC logo.
Alright, I've actually successfully modified the logo.rle file from inside a boot.img, rebuilt the ROM with it, and reflashed it - the image is now in place, and the ROM works great.
So, the steps:
Use dsixda's Android Kitchen to unpack the ROM into a working folder.
Locate the boot.img and copy it to a separate folder.
Follow this tutorial to unpack the boot.img file, then locate the logo.rle inside there (there's no initrd.gz).
Use the tools found here to convert the image that you want to use to an RLE file, and then overwrite the existing RLE file in your working directory where you unpacked the boot.img.
Continuing the tutorial found in the link from step 3, repack your boot.img with the edited logo.rle now inside it.
Head back to your working folder in the Android Kitchen, where the ROM that you want to modify has been unpacked. Replace the boot.img there with the one that you just modified.
Choose option 99 in the kitchen to build a ROM from the working folder, and follow the steps.
Now flash your ROM in CWM! I flashed straight over an existing installation instead of wiping etc., although it did still get rid of all my settings
Hopefully this is helpful to someone. I might post it in a new thread - since I spent so long trying to find this, and finally figured out how to do it for myself.
This helped a lot. Thanks.
ryan1990 said:
This helped a lot. Thanks.
Click to expand...
Click to collapse
No worries. If anyone ever gets stuck or doesn't know what I did for some bit, let me know and I'll see if I can help, because it sucked when I was trying to figure this out for ages and nobody else seemed to know how to do it either.
vovchok said:
Yeah - now it's working on my HD2!
gunzip initrd.gz
cpio -i < initrd
cp -f ../logo.rle
rm initrd
find . | cpio -o -H newc | gzip > ../initrd.gz
Hope it's will be helpfull!
I'm sorry - english is not my language.
Click to expand...
Click to collapse
search for long time, now work fine.
THX bro.
vovchok said:
Yeah - now it's working on my HD2!
This method is applicable for firmware, which include the file initrd.gz in zip archive. Many firmwares are distributed as img files, and I have not tried to extract initrd.gz from there, though perhaps it is possible.
The file logo.rle is not the usual rle and programs for creating or convert rle can not create it, also You can not view logo.rle by any usual rle-viewer. I took logo.rle from another firmware, because I could not do it (it can be reached by 7zip from initrd.gz; or copied from root directory after boot by root explorer, if firmware is already installed).
For this process Linux on a PC required - terminal emulator on phone doesn't work correctly! I used Chaox Live CD because I use Windows on my PC.
I put the file initrd.gz (from my firmware) in a folder and the new logo.rle file near this folder. In a Linux terminal I entered to that folder (by command cd) and ran the commands:
gunzip initrd.gz
cpio -i < initrd
cp -f ../logo.rle
rm initrd
find . | cpio -o -H newc | gzip > ../initrd.gz
Than I change the original initrd.gz in the firmware to the one I created.
ps: Not necessarily replace the entire firmware to replace the file initrd.gz. You can replace only a boot partition. To do this, take the original files boot/zImage & META-INF/com/google/android/updater-script from the firmware and add Your own boot/initrd.gz & META-INF/com/google/android/updater-script. Now You can zip it and place the archive to the root of the sdcard. Than enter to MAGLDR-ADrecovery-install zip from sdcard
Archive must contain this 4 files with pathnames:
boot/initrd.gz
boot/zImage
META-INF/com/google/android/update-binary
META-INF/com/google/android/updater-script
file updater-script must containe this commands:
mount("MTD", "boot", "/boot");
package_extract_dir("boot", "/boot");
unmount("/boot");
In my case I use this firmware and logo.rle file from this firmware.
Hope it's will be helpfull!
I'm sorry - english is not my language.
Click to expand...
Click to collapse
Thz for your help^^
The rom i am using hvn't boot.img.
but i can find initrd.gz and i hv change the logo.rle.
the probllem is how to edit the updater-script only update the initrd.gz?
and is it possible to random boot a few of .rle files ?
Please, make initrd.gz for CM9ight
Oops, not the right thread.

[Q] How to make a system folder into a system.img

Hello XDA, I'm kind of new to ROMs etc. and would appreciate some help. I am trying to install mikegapinski's 2.3.7 ROM (v5) through fastboot and whereas in the past I have seen a boot.img and a system.img, there is a boot.img and a system folder. Is there a way to make the folder into a system.img file that I could flash onto my GT540?
In short, how do you make a system.img file out of a folder with system files in them?
hey there !
(system.img + boot.img) is for fastboot
fastboot flash boot boot.img
fastboot flash system system.img
and the (system folder + boot.img) is for recovery
use any recovery
select zip from sdcard
select the zip
i dont think you can convert the folder to a .img(or the other way around) . and if the rom you are talking about mike's aosp v5 then i wont recommend it as for now there are problems with the ram and so it becomes very laggy. i would recommend mur4iks swiftdroid asis but the choice is yours
I know you can 'extract' images using 'unyaffs' but I never made an image from a folder (except when dumping partitions). I think there is a way though.
If you have Linux on your PC, then you can use the 'yaffs' tool. Search it on Google.
This is how even AOSP compiles system folder into system.img
Sent from my LG GT540 Swift using XDA App
I list found this. Should work!
http://db.tt/ROQSWTW6
Sent from my LG GT540 Swift using Tapatalk
can someone please help me to make system.img from system extraxted folder.
my phone its dead and i can find right rom for it
allway hang on boot logo
Please
link for download
https://www.dropbox.com/s/c99ashouw0fb4hp/system.rar
PS
will if neeed no problem
I got it. If you use Linux, you can create an iso file of the system folder, and then convert it to .img. Just follow it:
In a terminal(CTRL+ALT+T):
Code:
mkisofs -o /path/to/the/system/folder ~/system.iso
dd if=~/system.iso of=~/system.img
rm ~/system.iso
Your system.img will be on your home directory.
and it work's too ? (when you flash it from fastboot)
y2yu said:
can someone please help me to make system.img from system extraxted folder.
my phone its dead and i can find right rom for it
allway hang on boot logo
Please
link for download
https://www.dropbox.com/s/c99ashouw0fb4hp/system.rar
PS
will if neeed no problem
Click to expand...
Click to collapse
pls if you find a solutuon please pm me. And do you think flashing the system.img will solve booting probz?
suggestion
take a look at this url, and examine the zip file contained.
you could boot into cwm and install the zip (not suggesting, its what i did)
if u make a zip file in the same layout you could install your zip and it will update the system partition.
as you have a desire, heres whats required
on phone: place phone into fastboot mode
on computer: unzip to a folder , place the img file in such folder,
open a command prompt, (navigate to folder using the cd command)
and type: fastboot boot bravo-cwm.img
mount sd card, toggle usb storage, place your zip in root of sdcard.
then untoggle, go back, select option to install zip from sdcard.
choose select zip file.
find your zip.
tap on the file, and it will install...
you SHOULD by this point have an updated phone as you desired (lol)
if it does not work as you expected, have a look for a standard system.img for your phone, and put that into a zip
name the zip (i put it in caps, weather needed i dont know) PM99IMG.zip
place it into root of sdcard, and put phone into the first screen of recovery menu, the white screen.
it will analyze your zip and ask you to install, press up to flash and then the required option to reboot when its done to revert your phone back to normal.
hope this helps there buddy,
ill most likley forget to check back, so if u need any help pm me and ill see what i can do,
Is this working
Edu_Renesto said:
I got it. If you use Linux, you can create an iso file of the system folder, and then convert it to .img. Just follow it:
In a terminal(CTRL+ALT+T):
Code:
mkisofs -o /path/to/the/system/folder ~/system.iso
dd if=~/system.iso of=~/system.img
rm ~/system.iso
Your system.img will be on your home directory.
Click to expand...
Click to collapse
HI Bro,
Is the output file system.img after flash into the rom?
phone stuck in usb logo... i have zenfone 4
Yaffey for Windows Might Help
tejasjadhav said:
If you have Linux on your PC, then you can use the 'yaffs' tool. Search it on Google.
This is how even AOSP compiles system folder into system.img
Sent from my LG GT540 Swift using XDA App
Click to expand...
Click to collapse
And if you have Windows on your PC, try Yaffey! http://www.xda-developers.com/yaffey-for-all-your-yaffs2-needs/

[Tutorial] Add TWRP to AOSP LP 5.0 boot.img

I've updated the boot.img for paxb build 504 with TWRP to replace CWM. Some were asking how to do this.
Always keep a backup of a file known as working. If your device doesn't boot after flashing a modified file, just reflash that backup.
To perform this mod on your own follow these steps:
1. Download and unpack the Android Image Kitchen
2. Extract the boot.img from the downloaded ROM to the kitchen directory
3. Unpack the image:
Code:
unpackimg.bat boot_cwm_pabx_504.img
Output:
Code:
Android Image Kitchen - UnpackImg Script by osm0sis @ xda-developers
Supplied image: boot_cwm_pabx_504.img
Removing old work folders and files . . .
Setting up work folders . . .
Splitting image to "/split_img/" . . .
BOARD_KERNEL_CMDLINE androidboot.hardware=sony user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 vmalloc=400M
BOARD_KERNEL_BASE 80200000
BOARD_NAME
BOARD_PAGE_SIZE 2048
BOARD_KERNEL_OFFSET 00008000
BOARD_RAMDISK_OFFSET 02000000
BOARD_TAGS_OFFSET 00000100
Unpacking ramdisk to "/ramdisk/" . . .
Compression used: gzip
9694 blocks
Done!
This process will overwrite previously extracted contents!!!
4. Create a directory for the original image content, e.g. "boot_cwm_pabx_504" and COPY the created directories "ramdisk" and "split_img" into it. This ensures you can recreate it if necessary or access its original contents
5. Repeat step 4 for a downloaded TWRP (or any other recovery) image, e.g. "openrecovery-twrp-2.8.0.1-yuga.img".
6. Locate the "*-ramdisk.cpio.gz" file in the dirs from step 5, most likely in "split_img".
7. Ensure the "ramdisk" and "split_img" directories in the kitchen root dir are those from the image you want to modify (i.e. copy back from the folder created in step 4. Then remove the "*.cpio" from the "ramdisk\recovery" directory
8. Extract the TWRP "*.cpio" file from the "*-ramdisk.cpio.gz" in step 6 to "ramdisk\recovery" and rename it to "ramdisk-recovery.cpio"
9. rebuilt the image with the updated content:
Code:
repackimg.bat
Output:
Code:
Android Image Kitchen - RepackImg Script
by osm0sis @ xda-developers
Packing ramdisk . . .
Using compression: gzip
Getting build information . . .
kernel = boot_cwm_pabx_504.img-zImage
cmdline = androidboot.hardware=sony user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 vmalloc=400M
board =
base = 80200000
pagesize = 2048
kernel_offset = 00008000
ramdisk_offset = 02000000
tags_offset = 00000100
Building image . . .
10. Step 9 creates a file called "image-new.img". Rename it to something more self-explanatory, i.e. "boot_twrp_2.8.0.1_pabx_504.img"
11. To flash the file flash it like any other file using the new name:
Code:
adb reboot bootloader
fastboot flash boot boot_twrp_2.8.0.1_pabx_504.img
fastboot reboot
That's it, enjoy your new recovery.
Note: I had issues getting TWRP 2.8.1.0 working, so I'm still using the predecessor 2.8.0.1.
The latest pabx "boot.img" modified with TWRP is attached.
Known issues
after restoring a Nandroid backup access to the internal storage isn't allowed anymore
Open a terminal or run through a adb shell:
Code:
restorecon -FR /data/media/0
Thank works dobře.TWRP I like long ....
cant understand what you mean in step 7 and 8..... i just unpacked boot.img (the img that i want to put a recovery on it) and then i created a folder and i copied split_img and ramdisk into it.....then i unpacked twrp.img and it replaced the previous split_img and ramdisk folders with the twrp ones..... i still have the folder i created with the original split_img and ramdisk folders from boot.img but i can understand what to do next....
well, sorry for that,...i think i got it now that i read it about 20 times..... one question though :
i copy ramdisk.cpio.gz from the twrp and i move it to the recovery folder of the boot img without extracting? just renaming it from ramdisk.cpio.gz to ramdisk-recovery.cpio ???
arismelachrinos said:
cant understand what you mean in step 7 and 8..... i just unpacked boot.img (the img that i want to put a recovery on it) and then i created a folder and i copied split_img and ramdisk into it.....then i unpacked twrp.img and it replaced the previous split_img and ramdisk folders with the twrp ones..... i still have the folder i created with the original split_img and ramdisk folders from boot.img but i can understand what to do next....
well, sorry for that,...i think i got it now that i read it about 20 times..... one question though :
i copy ramdisk.cpio.gz from the twrp and i move it to the recovery folder of the boot img without extracting? just renaming it from ramdisk.cpio.gz to ramdisk-recovery.cpio ???
Click to expand...
Click to collapse
Yeah I didn't fully understand that either, but i just tried it.
You delete ramdisk-recovery.cpio from /ramdisk.
You extract ramdisk.cpio.gz to the /ramdisk folder.
You rename it to ramdisk-recovery.cpio.
Repack image.
(note that when the kernel you use is already a dualrecovery kernel -lightning for example, cwm philz+twrp- and u want it to be multirom twrp, u need to edit init.sh also found in /ramdisk folder somewhere)
BTW thanks for this guide! I was messing with this a few days ago and I couldn't get it to work, thanks to you I now understand why!:thumbup:
I tried to put latest twrp into latest boot.IMG of Thomas lollipop 23/11/14 build and I thought it worked but I press volume up and down to enter the recovery and it does nothing....it doesn't boot,it just freezes with the led lighting.... please help I really want twrp to work with lollipop
arismelachrinos said:
I tried to put latest twrp into latest boot.IMG of Thomas lollipop 23/11/14 build and I thought it worked but I press volume up and down to enter the recovery and it does nothing....it doesn't boot,it just freezes with the led lighting.... please help I really want twrp to work with lollipop
Click to expand...
Click to collapse
Reread what I wrote.
You probably didn't extract ramdisk.cpio.gz, or you putted it into /split_img I think. Cuz I had that too, but if you follow the exact steps it will work!
no I did exactly what you said... I fully understood the instructions,I extracted it , I named it right and I moved it right... well, I will try again tomorrow but I don't think it will boot into it... Thomas boot.img has a cwm recovery ,does this have smthg to do with it?
arismelachrinos said:
no I did exactly what you said... I fully understood the instructions,I extracted it , I named it right and I moved it right... well, I will try again tomorrow but I don't think it will boot into it... Thomas boot.img has a cwm recovery ,does this have smthg to do with it?
Click to expand...
Click to collapse
What version of TWRP did you use? 2.8.1.0 will likely not work, use an older one instead.
arismelachrinos said:
cant understand what you mean in step 7 and 8..... i just unpacked boot.img (the img that i want to put a recovery on it) and then i created a folder and i copied split_img and ramdisk into it.....then i unpacked twrp.img and it replaced the previous split_img and ramdisk folders with the twrp ones..... i still have the folder i created with the original split_img and ramdisk folders from boot.img but i can understand what to do next....
well, sorry for that,...i think i got it now that i read it about 20 times..... one question though :
i copy ramdisk.cpio.gz from the twrp and i move it to the recovery folder of the boot img without extracting? just renaming it from ramdisk.cpio.gz to ramdisk-recovery.cpio ???
Click to expand...
Click to collapse
Adjusted the description of step 8, should be more clear now what to do.
I've also added a note to point out explicitly that each run of "unpackimg.bat" will overwrite existing data.
Thank you so much for the guide! Really appreciate it =D
mcfisch said:
What version of TWRP did you use? 2.8.1.0 will likely not work, use an older one instead.
Click to expand...
Click to collapse
I used the latest twrp...maybe that's why....I will try again and I will post here
thank you sooooo much.... i did it with the second try...the only thing i changed was that i downoaded a previous version of twrp because it wont work with the latest one...thanks a lot.... what about cwm? is it the same proccess?
CWM is included already. But you could split the latest cm boot.img and grab ramdisk-recovery.cpio from ramdisk/sbin to get the most up to date version
is this mean can add TWRP into .FTF files ?
that will be awesome
Can anyone share their twrp included boot.img for the latest thomas release?
i tried to do this on the cm12 expirimental build and the boot.img of that zip doesnt have a recovery folder inside ramdisk folder... i did create one just to see if it works and it didnt
arismelachrinos said:
i tried to do this on the cm12 expirimental build and the boot.img of that zip doesnt have a recovery folder inside ramdisk folder... i did create one just to see if it works and it didnt
Click to expand...
Click to collapse
Look for a *.cpio or *.cpio.gz file and replace that accordingly. The place doesn't really matter for you, the ROM knows where to find it. CM might expect it respectively at another place. Will take a look later if I can find something...
mcfisch said:
Look for a *.cpio or *.cpio.gz file and replace that accordingly. The place doesn't really matter for you, the ROM knows where to find it. CM might expect it respectively at another place. Will take a look later if I can find something...
Click to expand...
Click to collapse
can you please take look at this?because i did search all the ramdisk folder and i found nothing.... i uploaded the boot.img so that you dont have to download the rom zip
https://www.mediafire.com/?5d6swrdegr53iel
mcfisch said:
Look for a *.cpio or *.cpio.gz file and replace that accordingly. The place doesn't really matter for you, the ROM knows where to find it. CM might expect it respectively at another place. Will take a look later if I can find something...
Click to expand...
Click to collapse
Won't work like that. Needs a script to be inserted into the ramdisk, @pabx style, plus the recovery folder with ramdisk-recovery.cpio inside.
was thinking why the latest TWRP was not working, then realized that the TWRP is written to be loaded into the FotaKernal.
then it worked with TWRP flashed into FotaKernal.
have pabx_aosp_yuga-509 installed
1. Followed your steps exactly to create a new boot_pabx_aosp_yuga-509.img (with the latest TWRP image "recovery-twrp-2.8.4.1-yuga.img").
2. Flashed recovery-twrp-2.8.4.1-yuga.img into the FotaKernal.
3. Flashed the new boot_pabx_aosp_yuga-509.img
it works
Edit: On my Xperia Z c6002 (yuga)

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

Categories

Resources