Related
Hey guys, I am in the process of rooting my evo 4g using this method http://htcevohacks.com/htc-evo-hacks/how-to-root-htc-evo-4g-on-hboot-2-18-with-s-off/ since I have 2.18 hboot version. I have unzipped all the files from RootEvo4GNew, and the file recovery-RA-supersonic-v2.3.img does not have the .img extension on it when I unzip it to the correct folder, and when I try to flash that in the cmd prompt it says
unknown partition 'recovery-RA-supersonic-v2.3.img'
error: cannot determine image filename for 'recovery-RA-supersonic-v2.3.img
I am assuming it can't find the file because it doesn't have the extendion .img on it once extracted. Any ideas? The icon next to the file looks like a zip file and can't be opened by 7zip
See it looks like a winzip file instead of a image file
Ok so I uninstalled winzip and now just have 7zip and it now shows the file as an .img file but I am still getting the same error message when in the command prompt. What am I doing wrong? Here's another image to show you what I mean
furrycnorm said:
Ok so I uninstalled winzip and now just have 7zip and it now shows the file as an .img file but I am still getting the same error message when in the command prompt. What am I doing wrong? Here's another image to show you what I mean
Click to expand...
Click to collapse
Download one of these,it has install instructions and a few different custom recoveries to choose from,creds to Smelkus of course..... http://forum.xda-developers.com/showthread.php?t=2171460
Diablo67 said:
Download one of these,it has install instructions and a few different custom recoveries to choose from,creds to Smelkus of course..... http://forum.xda-developers.com/showthread.php?t=2171460
Click to expand...
Click to collapse
I downloaded and followed instructions, isn't working for me. It looks like the phone doesn't see the file when in bootloader, not sure if I renamed it right.
furrycnorm said:
I downloaded and followed instructions, isn't working for me. It looks like the phone doesn't see the file when in bootloader, not sure if I renamed it right.
Click to expand...
Click to collapse
Follow this http://windows.microsoft.com/en-US/windows-vista/show-or-hide-file-name-extensions to make sure the file extensions show correctly, and make sure you didn't dupe the extension.
sent from a jb ROM..... cause I'm likely testing.
Wambo_Bomb said:
Follow this http://windows.microsoft.com/en-US/windows-vista/show-or-hide-file-name-extensions to make sure the file extensions show correctly, and make sure you didn't dupe the extension.
sent from a jb ROM..... cause I'm likely testing.
Click to expand...
Click to collapse
Thanks for the advice, I think this may work as I did have one extension duped. Problem is when I run the recovery it says it's an older version than what I already have installed and asks if I want to restart the device. I also still can't get the phone to flashboot recovery recovery-RA-supersonic-v2.3.img and it still says unrecognized partition in the command prompt. Is there a way to flash this from the sc card or anything else you can think of to try?
furrycnorm said:
Thanks for the advice, I think this may work as I did have one extension duped. Problem is when I run the recovery it says it's an older version than what I already have installed and asks if I want to restart the device. I also still can't get the phone to flashboot recovery recovery-RA-supersonic-v2.3.img and it still says unrecognized partition in the command prompt. Is there a way to flash this from the sc card or anything else you can think of to try?
Click to expand...
Click to collapse
Are you trying to fastboot flash the recovery .img file to your phone? If so you need to use the command "fastboot flash recovery *insert file name here*" (without quotation marks or asterisks). The recovery img file has to be in your ADB tools folder, alstherwise, put the recovery PC36IMG.zip file in the root folder of your SD card, make sure it's named PC36IMG.zip with no extra .zip extension, and reboot your bootloader. Follow the on-screen prompts to update your recovery.
Sent from my EVO using xda premium
FinZ28 said:
Are you trying to fastboot flash the recovery .img file to your phone? If so you need to use the command "fastboot flash recovery *insert file name here*" (without quotation marks or asterisks). The recovery img file has to be in your ADB tools folder, alstherwise, put the recovery PC36IMG.zip file in the root folder of your SD card, make sure it's named PC36IMG.zip with no extra .zip extension, and reboot your bootloader. Follow the on-screen prompts to update your recovery.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
wow I am retarded, my problem the whole time was that I was typing this:
fastboot flash recovery-RA-supersonic-v2.3.img
when I should have typed this:
fastboot flash recovery recovery-RA-supersonic-v2.3.img
Thank you so much for the help, on to the next step and hopefully this works!
Ok, successfully rooted with s-off! I have read through all the guides, and am still a bit confused because most of them are from 2010 and 2011. I need to flash a rom that will work with metro-pcs. Can you guys help me with which steps I need to take? I tried to download metrodroid v4 but the download link isn't working. Will aall of the roms in this thread work with metro pcs or do I need a specific one? http://forum.xda-developers.com/showthread.php?t=2318070
Also, once I have a rom flashed, do I have to go in to a metro pcs store to get it activated (I do not currently have a metro pcs account or other metro phone) or can I get the esn activated online or by calling there 800 number?
Extracting ROM files from HTC RUU
Official HTC ROM updates are released as RUU (ROM Update Utility), which you run on your (Windows) PC to get the target device updated automatically.
Some of the big brains in the Android community release RUUs re-packaged into signed update files,
which in turn allow for whatever ROM customization you can imagine.
In this how to I will explain how to extract ROM files from a RUU image,
which you can then customize and use to flash your device without the fear of a new bootloader possibly making your device unrootable.
Requirements :
Windows PC,
Microsoft Process Monitor,
File Archiver capable of extracting ZIP files(eg, 7ZIP),
Official HTC RUU for your Android device.
The process of extracting ROM files from a RUU is really straightforward.
The idea behind it is that the self-contained update utility first needs to unpack the update payload into a temporary folder before pushing it onto the device.
This is when we grab the ROM file...
1. download the official RUU
2. start Process Monitor.
3. press CTRL+L
4. change "Architecture" to "Process Name"
5. leave the "is" field as it is
6. in the empty field copy and paste the name of your
RUU file (eg, RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_Radio_12.65.60.29_26.14.04.28_M_release_225512_signed.exe)
7. click "Add"
8. change "Process Name" to "Path"
9. change "is" to "Contains"
10. in the blank field type "rom.zip" (without quotes)
11. click add
Click "OK" to set the filter and then run the RUU file.
Once the utility starts switch back to Process Monitor and look for an entry in the "Path" column that ends with "\rom.zip".
Right click on that line and select "Jump to..."
this will open a Windows Explorer window in the folder which contains the zipped ROM files
Copy the "rom.zip" file to some other folder, outside of the temp RUU folder tree (eg, desktop)
Once copied, close Process Monitor and the RUU utility.
The copied "rom.zip" file contains the following files:
android-info.txt - list of CIDs this RUU will flash to,
boot.img - root file system image,
hboot (followed by a version string) - boot-loader update,
radio.img - radio driver update,
recovery.img - recovery partition image,
splash1_Hero_320x480.nb0 - boot loader splash image,
system_rel.img - system partition image,
userdata.img - data partition image.
You can now, among many other things, root the ROM
and then flash the updated boot.img and all the other image files on to your device using Recovery
it doesnt work... the process monitor colum is all blank after running RUU... there are no processes listed
munnibhai said:
it doesnt work... the process monitor colum is all blank after running RUU... there are no processes listed
Click to expand...
Click to collapse
you mst be doing something wrong i double checked the method and it still works fine for me..
make sure your environment is set up correctly and run everything as administrator or disadle uac in windows..
thanks for the reply, let me check it again...
i will post back to u
rom.zip corrupted
I followed the directions and like another post in here procmon shows a blank screen. I went to task manager and opened processes and saw when it ran then clicked open file location and found it. I did this twice and both zips are corrupt. (used winzip)
error [D:\android apps\EVO root\EVO\rom.zip]: start of central directory not found; Zip file corrupt.
Possible cause: file transfer error
when I close the RUU all the files in that folder disappear so you have to leave the RUU running while you copy the zip file or it's gone.
At least that's what I saw.
update to last post
I found a zip repair tool and was able to repair and extract the 1.10.653.2 RUU rom capture. I will have to try to run it later. If anyone gets corrupted zip error, Zip Repair pro will repair it.
To get the rom zip without any errors just run the ruu.exe file, when the box with a picture of a phone pops up, click start on pc, type in "run" and click on run then in that box that pops up, type in %temp% and click ok. Another window pops up then just scroll down to the most recent folder and rom.zip will be in there, if not it will be in the next folder.
Hi,
when I try to open the rom.zip I get an error message, it just said it cannot open with 7zip and with windows it says its invalid.
I tried downloading the RUU multiple times but still the same error. I rune the RUU as administrator.
Tried copying it over to different locations and then open it.
RUU_ENRC2B_U_JB_45_O2_UK_1.14.206.13_Radio_3.1204.167.31_release_289474_signed
HTC ONE X+
Thank you
Update:
I used Zip Repair Pro.. however there is no boot.img inside the repaired zip -_-
For those which have problem with making Process Monitor detect RUU temp folder, make sure You add whole file name of RUU including .exe at the end.
Jmcclue's steps, work perfectly, Thank you post #7
htc RUU Rom
Inside 4ndroid said:
Extracting ROM files from HTC RUU
Official HTC ROM updates are released as RUU (ROM Update Utility), which you run on your (Windows) PC to get the target device updated automatically.
Some of the big brains in the Android community release RUUs re-packaged into signed update files,
which in turn allow for whatever ROM customization you can imagine.
In this how to I will explain how to extract ROM files from a RUU image,
which you can then customize and use to flash your device without the fear of a new bootloader possibly making your device unrootable.
Requirements :
Windows PC,
Microsoft Process Monitor,
File Archiver capable of extracting ZIP files(eg, 7ZIP),
Official HTC RUU for your Android device.
The process of extracting ROM files from a RUU is really straightforward.
The idea behind it is that the self-contained update utility first needs to unpack the update payload into a temporary folder before pushing it onto the device.
This is when we grab the ROM file...
1. download the official RUU
2. start Process Monitor.
3. press CTRL+L
4. change "Architecture" to "Process Name"
5. leave the "is" field as it is
6. in the empty field copy and paste the name of your
RUU file (eg, RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_Radio_12.65.60.29_26.14.04.28_M_release_225512_signed.exe)
7. click "Add"
8. change "Process Name" to "Path"
9. change "is" to "Contains"
10. in the blank field type "rom.zip" (without quotes)
11. click add
Click "OK" to set the filter and then run the RUU file.
Once the utility starts switch back to Process Monitor and look for an entry in the "Path" column that ends with "\rom.zip".
Right click on that line and select "Jump to..."
this will open a Windows Explorer window in the folder which contains the zipped ROM files
Copy the "rom.zip" file to some other folder, outside of the temp RUU folder tree (eg, desktop)
Once copied, close Process Monitor and the RUU utility.
The copied "rom.zip" file contains the following files:
android-info.txt - list of CIDs this RUU will flash to,
boot.img - root file system image,
hboot (followed by a version string) - boot-loader update,
radio.img - radio driver update,
recovery.img - recovery partition image,
splash1_Hero_320x480.nb0 - boot loader splash image,
system_rel.img - system partition image,
userdata.img - data partition image.
You can now, among many other things, root the ROM
and then flash the updated boot.img and all the other image files on to your device using Recovery
Click to expand...
Click to collapse
this is good working 100% thank you :good:
i_4_u89 said:
this is good working 100% thank you :good:
Click to expand...
Click to collapse
no problem and please instead of saying thanks please remember to hit the thanks button on threads first post..
works great, to bad you cant open the zip file
jpwhre said:
works great, to bad you cant open the zip file
Click to expand...
Click to collapse
You can open the zip. Go back a page n try the way i said.
jmcclue said:
You can open the zip. Go back a page n try the way i said.
Click to expand...
Click to collapse
note path is desktop (last post showed from temp folder) and i still get same results. did some searching and aperantly htc now signs their zip files and they can't be opened anymore. having usb issues that causes fastboot force close errors and need to be able to flash boot.img thru flashify app to return it to stock. ran the htcguru reset rom that uses aroma installer to return to stock that lets me take ota's but i get qualcom location force close and other custom roms give me issues forcing me to reset phone to stock every few days with guru installer. flashing recovery in fastboot is a chore as well. I have s-off and can keep it, but doing fastboot oem lock wont relock the bootloader, even though it shows success in cmd line. i can cid and super cid with fastboot.
it leaves me at a point where i really need to pull everything out of the rom.zip file and it wont open.
pic 1, 7zip wont open archive on desktop
pic 2, how i get recovery to flash
pic 3, results from running RUU
i have to reboot device, set comand to reboot bootloader, set command to flash recovery all faster than phone will do all commands to get it to flash, and RUU doesnt work that fast. i know im on sprint with htc one m7, but google search "extract htc zip" "extract rom.zip" both lead to this thread as top result. no other searches will tell me how to open the archive, except one that resulted in "htc signed zips can no longer be opened"
you're more than welcome to give it a go
http://forum.xda-developers.com/showthread.php?t=2795856 Sprint_HTC_One_m7wls_5.05.651.2_RUU.exe
Did HTC change the way they create the exe? I don't find it, the biggest file is data1.cab file that I can't extract.
I'm trying to extract the stock rom for an ATT HTC One Mini (m4) because RUU keeps crashing on me and won't install. I am also rooted with S-off.
If anybody can help me get the stock m4 rom so I can go back to stock, I would really appreciate it.
SyPete said:
Did HTC change the way they create the exe? I don't find it, the biggest file is data1.cab file that I can't extract.
I'm trying to extract the stock rom for an ATT HTC One Mini (m4) because RUU keeps crashing on me and won't install. I am also rooted with S-off.
If anybody can help me get the stock m4 rom so I can go back to stock, I would really appreciate it.
Click to expand...
Click to collapse
No they didn't change it. Some ruu's use a different format requiring the use of a tool called unruu instead of trying to capture the zip file when using the exe (I just learned this today). I've gone ahead and used unruu and the resulting zips have been put in a single tar file. you can download it from here for about 30 days after which ill have to delete the file. also i dont know which zip has what in it.
hi
master how to open Zip firmware !!?
i want to open zip firmware (PM60IMG.zip Desire 400)with 7zip ! but shows below error :
"can not open file PM60IMG.zip az archive "
how to pass this encryption ?
gandolf007 said:
hi
master how to open Zip firmware !!?
i want to open zip firmware (PM60IMG.zip Desire 400)with 7zip ! but shows below error :
"can not open file PM60IMG.zip az archive "
how to pass this encryption ?
Click to expand...
Click to collapse
https://github.com/kmdm/ruuveal/tree/f4936338f19841c75edafbe7e622242105cb39aa
Hello Community,
I tried to install custom recovery using this manual "wiki.cyanogenmod.org/w/Install_CM_for_serranoltexx" (<- cannot use the link function, because it's my first post). I followed every step. At point 9 I have to make commands using the cmd. Unfortunately the result is an Error:
Failed to access device. libusb error: -12
I had two insecurities while following the manual:
At point 4 I had to rename the recovery image but I'm not sure what the recovery image is. What I downloaded was a .tar.md5 file within a .zip. Do I have to rename the .zip or the .tar.md5? The renaming causes a change of the file type and I cannot really understand, why they didn't put the right file in that .zip at the beginnig...this step is a bit confusing
To point 5: I deinstalled Kies and the device driver in the Windows operating system. Since I've done this, there are appearing two devices in the zadig.exe when I connect my S4. I installed the zadig driver for both of them.
Im using Windows 7 x64
I hope someone can help me, for this moment I don't know what to do further...
greets
Dr. Bob! said:
At point 4 I had to rename the recovery image but I'm not sure what the recovery image is. What I downloaded was a .tar.md5 file within a .zip. Do I have to rename the .zip or the .tar.md5? The renaming causes a change of the file type and I cannot really understand, why they didn't put the right file in that .zip at the beginnig...this step is a bit confusing
Click to expand...
Click to collapse
I don't know about the libUSB error, and I haven't modded a Galaxy S4 mini, but I have installed CM on Galaxy Player. The tar.md5 has to be extracted from the zip; it is in fact a tar.gz file (tar archive compressed with gzip), but you don't have to rename it.
I flashed the Galaxy Player with Odin 3 v. 3.04, after having installed Kies to have the drivers installed. The Player showed in Odin with something like "ID:0 COM"; I then clicked on the "PDA" button, then pointed to the tar.md5, and clicked flashed, and it worked.
Here are my 2 cents :^)
Is your phone rooted? If rooted already it easy! For the most noob method, install ROM Manager from https://play.google.com/store/apps/details?id=com.koushikdutta.rommanager and ROM manager will install the CWM for you. From there, its pretty simple.
If it not rooted, that the first thing you'll have to do.
fdelente said:
[...] The tar.md5 has to be extracted from the zip; it is in fact a tar.gz file (tar archive compressed with gzip), but you don't have to rename it.
Click to expand...
Click to collapse
I found out, the .tar.md5 is also a compressed file. If I extract it, I get a file called "recovery.img". At this point it's not very clear what to do. Because there is nothing to rename. And even if you are right, the tutorial would be also wrong.
TNCS said:
If it not rooted, that the first thing you'll have to do.
Click to expand...
Click to collapse
This is for installing the custom recovery, that's is the root, isn't it? I had the problem that Heimdall doesn't gets access to the device (lubusb error: -12). It's probably a driver problem.
However, I solved the problem by doing another method using odin. The root was succesfull. Afterwards I will flash the custom rom.
Dr. Bob! said:
I found out, the .tar.md5 is also a compressed file. If I extract it, I get a file called "recovery.img". At this point it's not very clear what to do. Because there is nothing to rename. And even if you are right, the tutorial would be also wrong.
This is for installing the custom recovery, that's is the root, isn't it? I had the problem that Heimdall doesn't gets access to the device (lubusb error: -12). It's probably a driver problem.
However, I solved the problem by doing another method using odin. The root was succesfull. Afterwards I will flash the custom rom.
Click to expand...
Click to collapse
No, custom recovery is not rooting. Not my favourite method but it easy enough, try this: http://www.kingoapp.com/
It a universal root for JB and it will prompt you to install CWM afterwards.
After installing the CWM I rooted the device. I succesfully installed Canogenmod 10.2.1. The Tutorial says explicit, that it only helps for 10.2.x but I want to install the Nightly version which is running at CM version 11. If I could, I would ask this questions in the threat but I'm not allowed yet to post in the developers section. "forum.xda-developers.com/showthread.php?t=2474054"
Can I use this tutorial for flashing CM version 11?
I know most of you already know this, but it may help others because this is very usefull for installing kitkat.
It's a pain to copy an 1,2 GB ROM to internal storage, so sideloading (installing from PC) it's lot easier and faster.
So here's the trick.
Copy the zip you want to install in "adb" folder (archiev attached)
Reboot phone in recovery mode
Optional - do your wipes
If you have CMW
Go to install zip -> install zip from sideload
If you have TWRP
Go to advanced -> ADB sideload
connect the USB cable and run START.cmd
type "adb devices" to check if your phone is recognized and connected (skip if you know everything it's ok)
type "adb sideload kitkat.zip" (replace kitkat with zip's name)
Notes:
Ofc you need USB drivers
Ive tried that a couple times but always i get a "cannot read kitkat.zip" thing, any idea why?
Sent from my LG-E975 using XDA Premium 4 mobile app
mastor10 said:
Ive tried that a couple times but always i get a "cannot read kitkat.zip" thing, any idea why?
Click to expand...
Click to collapse
Umm... Did you replace "kitkat.zip" with the actual name of your zip file (or rename your zip to "kitkat.zip")? I know it might be a very stupid question, but I can only read your post, not your mind...
kt-Froggy said:
Umm... Did you replace "kitkat.zip" with the actual name of your zip file (or rename your zip to "kitkat.zip")? I know it might be a very stupid question, but I can only read your post, not your mind...
Click to expand...
Click to collapse
Of course man, all of the roms ive flashed was through sideload
mastor10 said:
Of course man, all of the roms ive flashed was through sideload
Click to expand...
Click to collapse
Make a screenshot of what you're doing and error you get, this way will be easier for both.
roscatel said:
Make a screenshot of what you're doing and error you get, this way will be easier for both.
Click to expand...
Click to collapse
there you go
i changed the name to zip but norhing happens
mastor10 said:
there you go
i changed the name to zip but norhing happens
Click to expand...
Click to collapse
First, there is no way for a rom to use ".rar" extension. After, error means that the file couldn't be read (missing or corrupted). Also you may try my method which doesn't need android SDK, so there is no complications with wrong paths or such.
roscatel said:
First, there is no way for a rom to use ".rar" extension. After, error means that the file couldn't be read (missing or corrupted). Also you may try my method which doesn't need android SDK, so there is no complications with wrong paths or such.
Click to expand...
Click to collapse
yes i know, but in there the rom is in rar http://forum.xda-developers.com/showthread.php?t=2762171
so i changed the rar to zip, also i downloaded the file 3 times and the same happens, ill try with your adb and see
also the others zips i flash through sideload from sdk works just fine, only in this rom i get the error
edit, nope the same happens
mastor10 said:
yes i know, but in there the rom is in rar http://forum.xda-developers.com/showthread.php?t=2762171
so i changed the rar to zip, also i downloaded the file 3 times and the same happens, ill try with your adb and see
also the others zips i flash through sideload from sdk works just fine, only in this rom i get the error
edit, nope the same happens
Click to expand...
Click to collapse
Look at the screen I've attached. Are you sure your zip it's not the same have you checked it? I've highlighted the rom itself.
roscatel said:
Look at the screen I've attached. Are you sure your zip it's not the same have you checked it? I've highlighted the rom itself.
Click to expand...
Click to collapse
this is what i download
https://drive.google.com/uc?id=0BxtwB2oE42pDNFJsaGJ3ODNkWGM&export=download
from the topic i mention above, its the same, i rename it to a smaller name though
mastor10 said:
this is what i download
https://drive.google.com/uc?id=0BxtwB2oE42pDNFJsaGJ3ODNkWGM&export=download
from the topic i mention above, its the same, i rename it to a smaller name though
Click to expand...
Click to collapse
Ok then simply extract "VDT-V20..." from that archieve. That's the zip you have to install via sideload!
roscatel said:
Ok then simply extract "VDT-V20..." from that archieve. That's the zip you have to install via sideload!
Click to expand...
Click to collapse
this is whats inside the zip i download
mastor10 said:
this is whats inside the zip i download
Click to expand...
Click to collapse
It looks to me that your screenshot is showing contents of a ZIP inside a RAR. What @roscatel means, you should extract the ZIP from the RAR that you downloaded -- it's actually an archive packed inside another archive. After that, flash the ZIP you just extracted using any method (sideload, or from recovery as usual). Do NOT rename RAR to ZIP -- it doesn't make sense, and will most definitely NOT work.
kt-Froggy said:
It looks to me that your screenshot is showing contents of a ZIP inside a RAR. What @roscatel means, you should extract the ZIP from the RAR that you downloaded -- it's actually an archive packed inside another archive. After that, flash the ZIP you just extracted using any method (sideload, or from recovery as usual). Do NOT rename RAR to ZIP -- it doesn't make sense, and will most definitely NOT work.
Click to expand...
Click to collapse
hi my pc known my device but when i write adb sideload ...zip foul (stand) 0% and i watting 15 minuts for process but nothing happening . plz help me . my device is xperia tx.. plzzzzzzzzzzzzz
install the last TWRP (flash it via bootloader), same process by opening commande window in the folder (shift+right click: then open command) and tiping command: fastboot flash recovery (name of the file).img (like that: exemple: fastboot flash recovery lastTWRP.img)
it autorize MTP transfer, so you cas access your internal storage and copy the zip file
or retrieve backups from your phone
I'm using and side load on my lge
LM-x210MA an I keep getting these different errors do I need to flash more than a twrp.imf what about sys.img root.img root-boot.img this is all a lot to take in as a first timer go easy I'm not trolling just trying to learn
Lets not talk about blah blah blah and start the guide....
Things You Will Need
Stock Recovery
Recovery which you want to port (CWM,TWRP,MIUI,LEWA,,,etc) NOTE :- This Recovery Image Will Be For That Device Which is a clone Device of yours Eg. Devices with Same Processors and No. of Cores etc...
Android Kitchen installed with Cygwin Link(if you did'nt installed) :- http://forum.xda-developers.com/showthread.php?t=1801690
Finally A Working Brain
1 Line Explains Everything
We just Have to Copy the 'zimage' file inside the stock recovery and replace the 'zimage' in the recovery you are porting
Procedure
Open Cygwin and type
cd kitchen
Click to expand...
Click to collapse
Hit Enter
Then type
./menu
Click to expand...
Click to collapse
Make a Working Folder In Kitchen
Place your stock recovery.img in working folder
In Cygwin Select Advanced options and then select Tools for boot/recovery images
Select Extract
After Extracting go to your kitchen directory and you will find a newly created folder named as Bootxxxx
Copy 'zimage' file anywhere to your computer
Now delete the Bootxxxx Folder and also delete stock recovery.img from working folder
Place the recovery.img you want to port in the working folder
Now do the same steps to extract this recovery
A new folder named Bootxxxx is once again created in the Kitchen Directory
Now Replace the 'zimage' in the Bootxxxx with the one you copied before
Now select to repack your newly created recovery
Flash It Using Fastboot/Bootloader mode and jump if it works
Hope I Helped You Creating Your Own Recoveries
Good Luck :good: