After doing many repacks with zImage Injector and as I want to repack without being online I wrote the following Tool for Widnows to repack a kernel into another boot.img. I hope there wasn't already such a tool for Windows...
This Tool works on Windows and needs .NET 4.0 on your PC.
Usage:
Choose the boot.img with the kernel you want to use in the Source field.
Choose the boot.img with the ramdisk you need to use in the Destination field. (This is usually the boot.img from your ROM)
Click Repack and save the new file.
Flash it like any other boot.img.
Info:
This was successfully tested on HTC One X with CM10 and ncx kernel.
It should work with every other device too, as boot.img format is android-specific.
Just 2 exceptions:
Images with a second loader may or may not be supported. I can't test this!
Also I don't know if Images with a 4096 byte pagesize work properly. Can't test this too...
But afaik there's only one rare device with a second loader. Also 2048 byte pagesize seems standard and is fully supported!
Download:
http://dl.dropbox.com/u/12141394/kernel_repacker_v1.zip (Direct Link)
Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Changelog:
v1: Initial release
Bugs:
No serious bugs known. If you find one report it and I'll try my best to fix it.
hi this sounds interesting
any protocol or caveats... actually i don't develop (build rom or kernel)
but i do port some roms to my device.
will using your tool require same principles like stock to stock or will it be possible to use kernel of ICS and ramdisk of GB?
So sorry for this noob questions.
This tool does just the repacking. It doesn't check what's in the images.
You can repack every kernel into every boot.img. You have to check for yourself which images you use, as I have no clue about porting.
I developed this mainly for repacking kernels when you use custom kernels with roms.
langer hans said:
This tool does just the repacking. It doesn't check what's in the images.
You can repack every kernel into every boot.img. You have to check for yourself which images you use, as I have no clue about porting.
I developed this mainly for repacking kernels when you use custom kernels with roms.
Click to expand...
Click to collapse
thanks for your reply. will report back what happens when i give it a try. thanks for sharing.
Hey... thanks for this.. but my phone goes into a boot loop..
Did a repack of eternity project kernel by kohlk and cm10 ROM by tbalden..
It just goes into boot loop.. help..
BTW I am new to this.. my first time repacking..
Can you send me the 3 imgs you used? Then I can debug it.
Gesendet von meinem Akustikkoppler via BTX.
langer hans said:
Can you send me the 3 imgs you used? Then I can debug it.
Gesendet von meinem Akustikkoppler via BTX.
Click to expand...
Click to collapse
okay..
I want to use Eternity Project's kernel with CM10 by Tbalden.
The created boot.img by me is turning my phone into boot loops.. (tried everything. wiping cache and full wipe..)
Attached are the three boot imgs....
So If I am not wrong..
Source : Eternity Project's kernel
Dest. Image : Img from the ROM that I am using (Tbalden's CM10)
and I made the boot using those two and that boot is simply getting stuck in a boot loop..
The Link to the three Boot Imgs.. : https://www.dropbox.com/sh/1rucra60q07j766/hcT1BdK9SO
Hope this helps buddy..
EDIT : I extracted only the file eprjboot.img from the zip file that's given by eternity project.
here is the link to the actual and full file actually given by eternity project : http://dlhg.eternityproject.eu/HTC/endeavor/eprj/EPRJKRN_ENDEAVORU3.4_STO_v0.62.zip
Eternity Project Kernel thread link :
XDA Devs : http://forum.xda-developers.com/showthread.php?t=1640532
Eternity Project : http://www.eternityproject.eu/topic/48-eternityproject-kernel-34-for-htc-one-x-endeavoru/
ROM: CM10 link : http://forum.xda-developers.com/showthread.php?t=1786696
IllUMINATUz:
This is not a problem with my tool. It generates exactly the same image as zImage injector.
Did you also flash the modules fpr eternity project kernel? These are also needed, but nocht covered by my tool. Check their post for the modules and flash them. this should fix your problem
langer hans said:
IllUMINATUz:
This is not a problem with my tool. It generates exactly the same image as zImage injector.
Did you also flash the modules fpr eternity project kernel? These are also needed, but nocht covered by my tool. Check their post for the modules and flash them. this should fix your problem
Click to expand...
Click to collapse
ok.. I'll check up with that one.. there's another tool that does flash the modules as well.. i'll check it up.. thanks anyways.. cheers..
Yeah.. there is a separate set of modules in eternity project website... thanks for the tip bro..
Sent from my HTC One X using xda app-developers app
thanks to you to give easy made for easiest way build kernel from source. im gonna give a try. and are u sure this will work for any device?
Sorry, but it is not a Tool for building a kernel from source. Just to repack boot.img files.
Gesendet von meinem HTC One X mit Tapatalk 2
Thanks for this! Working perfectly for CM 10.1/Nexus 4 and faux123 Kernel.
Hope this working on gtab p1000...
Sorry, how can I put the repacked boot.img back to the ROM? Is it just unzipping the ROM, replace boot.img and then zip it up? I got a duplicated files error...
namartlu said:
[...] Is it just unzipping the ROM, replace boot.img and then zip it up? I got a duplicated files error...
Click to expand...
Click to collapse
It should be enough to just replace the file in WinRAR, or WinZIP, or whatever you are using. But that also depends on the device. I guess your device can flash a kernel included in a ROM package directly? If so, than replacing the file would be enough...
langer hans said:
It should be enough to just replace the file in WinRAR, or WinZIP, or whatever you are using. But that also depends on the device. I guess your device can flash a kernel included in a ROM package directly? If so, than replacing the file would be enough...
Click to expand...
Click to collapse
It's for Nexus 4, trying to run Matrix kernel with CM 10.1 nightly builds.
So, are you saying I could just flash the repacked boot.img? Or I still have to bundle it into the original ROM (a zip file)...
Thanks!
If you already have installed the ROM you don't need to pack the repacked.img in the zip. Just flash it via the usual
Code:
fastboot flash boot repacked.img
langer hans said:
If you already have installed the ROM you don't need to pack the repacked.img in the zip. Just flash it via the usual
Code:
fastboot flash boot repacked.img
Click to expand...
Click to collapse
Is it possible to flash with clockwork recovery?
Sent from my Nexus 4 using xda app-developers app
I'm sorry, I don't know this. I have a HTC One X. All I found wath the fastboot method. CWM needs a zip file to flash...
Also, on flashing instructions, check the various Kernel Threads on the Nexus 4 Forum, that would be a better place to ask this
Related
Just wondering if anyone has his kernel in a flashable zip? I've tried to extract it and make my own, but having problems.. Thanks.
boredmug said:
Just wondering if anyone has his kernel in a flashable zip? I've tried to extract it and make my own, but having problems.. Thanks.
Click to expand...
Click to collapse
i was told to just use the boot.img from fresh toast. insert it into the rom of ur choice and flash it. it worked for me.
you can't just insert it into the zip though right? Do you know of a tutorial that will tell me how to do it?
boredmug said:
you can't just insert it into the zip though right? Do you know of a tutorial that will tell me how to do it?
Click to expand...
Click to collapse
i put the boot.img right into the zip then resigned and flashed. worked fine for me
This is a signed zip of the boot.img. Kernel 2.6.29-GoDmOdE-OC-BFS [email protected] #89 Should work. I am using this one in a custom cooked rom, signed the update myself.
http://www.4shared.com/file/m8rEPxk2/update_signed.html
smstutler said:
This is a signed zip of the boot.img. Kernel 2.6.29-GoDmOdE-OC-BFS [email protected] #89 Should work. I am using this one in a custom cooked rom, signed the update myself.
is this flashable over the current rom we are using or does it have to be inserted in a rom zip folder..... in other words how is this applied
Click to expand...
Click to collapse
grr.. i tried to flash this update to sushi rom and it gave error can't find update script
boredmug said:
grr.. i tried to flash this update to sushi rom and it gave error can't find update script
Click to expand...
Click to collapse
yep same here
smstutler said:
This is a signed zip of the boot.img. Kernel 2.6.29-GoDmOdE-OC-BFS [email protected] #89 Should work. I am using this one in a custom cooked rom, signed the update myself.
http://www.4shared.com/file/m8rEPxk2/update_signed.html
Click to expand...
Click to collapse
you didnt include an update script you just signed it.
here is an update.zip with # 89 kernel. idk what it will and wont work on.
im not responsible for loss of rom. nandroid, apply, see what happens. i recommend using set cpu and min-245 max-729
this allows for the best stepping.
tried it on damage 2.07.2.3333 with jit enabled... wouldnt go past the htc screen
same on Icerom and Sushi. Sticks at the HTC screen
Avalaunchmods said:
you didnt include an update script you just signed it.
here is an update.zip with # 89 kernel. idk what it will and wont work on.
im not responsible for loss of rom. nandroid, apply, see what happens. i recommend using set cpu and min-245 max-729
this allows for the best stepping.
Click to expand...
Click to collapse
Thanks. Wasn't sure. Now I know a lil more than I did yesterday.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Aloysius 2.0.9 sticks at the HTC screen also.
ill throw a new update later. i know why this one isnt working ill have to make some changes in the ramdisk.
I am also very very interested in a flashable zip aswell!
Avalaunchmods said:
ill throw a new update later. i know why this one isnt working ill have to make some changes in the ramdisk.
Click to expand...
Click to collapse
Will you be posting it here?
Its not going to work when flashing to a damage control rom or one thats based off of damage like most roms here are. Also it will not work on darchdroid.
The only rom the kernel will work on is fresh or fresh toast or one based on it.
You have to pull the boot.img apart and put ramdisk from your current rom and the kernel from fresh toast. And then add the necessary lines to init.rc and etc so you can have bfs and compache and all working. You might even need the config file from your current rom to put into the kernel, which you would have to compile your own kernel using toasts github source.
Who wants to be a quick test dummy thats running damage control.
Here is quick boot.img i put together so theres a chance it might not work, its a flashable update.zip so you can do it in recovery. I used avalauches .zip he posted earlier just changed the boot.img. Make a nandroid before flashing.
This is fresh toast kernel
flashing now
let me know if there is anything specific I can tell you.
I would know what if anything to look for in a logcat, I'm just gonna dl setcpu and check it out
*edit-
SetCpu is showing 768MHz max, I'm watching it fluctuate between 19 and 768...
No fc's, normal boot time
So far so good
nebenezer said:
flashing now
let me know if there is anything specific I can tell you.
I would know what if anything to look for in a logcat, I'm just gonna dl setcpu and check it out
SetCpu is showing 768MHz max, I'm watching it fluctuate between 19 and 768...
No fc's, normal boot time
So far so good
Click to expand...
Click to collapse
The boot.img i just posted worked on damage control?
Can anyone help me finding stock Kernel w/ kexec-hardboot patch for Android 4.4 for multirom?
Im not able to get the version of my primary ROM is based on
(or)
Can i use third-party kernel?
...
Im on 4.4 (KRT16O) Manually flashed factory image (developers.google. com/android/nexus/images#occamkrt16o).
Unfortunately i tried installing other kernel and encountered boot-loop and I had to flash factory image again..
(I used multirom before [before flashing stock 4.4] and used stock 4.3 JWRXXX kexec-hardboot patch kernel. That worked fine.)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Instead of flashing the whole factory image again, what you do is something called a backup in your custom recovery. Select to backup "boot" partition, which is the kernel, so if the kernel doesn't work, you can restore just the boot partition. Or you can just use fastboot to restore the stock kernel. Some kernels package flash other files to your system though, so you can do a full restore.
You can give NEO kernel a try, wifi will not work (due to 4.3 kernels lacking the new PRIMA driver) (it'lll work with KitKat), but you can flash the dePRIMAtor package to fix it: http://www.androidfilehost.com/?a=show&w=files&flid=9271
You can try and use the faux kernel from this AOKPK rom as well: http://goo.im/devs/kecinzer/aokpk/mako
eksasol said:
Instead of flashing the whole factory image again, what you do is something called a backup in your custom recovery. Select to backup "boot" partition, which is the kernel, so if the kernel doesn't work, you can restore just the boot partition. Or you can just use fastboot to restore the stock kernel. Some kernels package flash other files to your system though, so you can do a full restore.
You can give NEO kernel a try, wifi will not work (due to 4.3 kernels lacking the new PRIMA driver) (it'lll work with KitKat), but you can flash the dePRIMAtor package to fix it: http://www.androidfilehost.com/?a=show&w=files&flid=9271
You can try and use the faux kernel from this AOKPK rom as well: http://goo.im/devs/kecinzer/aokpk/mako
Click to expand...
Click to collapse
Thanks a looot for kernel backup information it worked flawlessly..
But the above mentioned kernels didn't work either i encountered boot-loop again and restored it by the method u suggested.
I need any 4.4 kernel with kexec-hardboot patch (http://forum.xda-developers.com/showthread.php?t=2472316)..
Sidnexus4 said:
Thanks a looot for kernel backup information it worked flawlessly..
But the above mentioned kernels didn't work either i encountered boot-loop again and restored it by the method u suggested.
I need any 4.4 kernel with kexec-hardboot patch (http://forum.xda-developers.com/showthread.php?t=2472316)..
Click to expand...
Click to collapse
there arent any. considering that the code has to be built into the kernel, and 4.4 kernel source hasnt been releaded yet.
simms22 said:
there arent any. considering that the code has to be built into the kernel, and 4.4 kernel source hasn't been releaded yet.
Click to expand...
Click to collapse
Thanks for the information..
Planning to install rom : http://forum.xda-developers.com/showthread.php?t=2472316
and flash Linaro 4.8.2 kernel : http://forum.xda-developers.com/showthread.php?t=2414064 for multirom hope it works.
i will post the result by an hr.
Sidnexus4 said:
Thanks for the information..
Planning to install rom : http://forum.xda-developers.com/showthread.php?t=2472316
and flash Linaro 4.8.2 kernel : http://forum.xda-developers.com/showthread.php?t=2414064 for multirom hope it works.
i will post the result by an hr.
Click to expand...
Click to collapse
you can try trinity kernel as well, it has the multirom stuff included, and runs on 4.4 roms. heres the latest trinity, tf18b http://goo.gl/RvKALI
Lianro kernel Neo17 worked great for multirom on NEXUS 5 PORT 4.4 KRT16O : http://forum.xda-developers.com/showthread.php?t=2507021 (Rom is far better than the original stock image. It includes all the missing features on stock)
Thanks everyone for the support :victory:
I am using Neo kernel with my stock kitkat and multirom boot into other android roms just fine. No need for ports.
eksasol said:
I am using Neo kernel with my stock kitkat and multirom boot into other android roms just fine. No need for ports.
Click to expand...
Click to collapse
Yeah i realized that later thanks i flashed older Neo version which doesn't have kitkat black screen fix..
In port rom i got "transparent navigation bar" , left swipe "googlenow" which are missing in stock and "ok google" on home-screen worked better then the stock one.
Sidnexus4 said:
Yeah i realized that later thanks i flashed older Neo version which doesn't have kitkat black screen fix..
In port rom i got "transparent navigation bar" , left swipe "googlenow" which are missing in stock and "ok google" on home-screen worked better then the stock one.
Click to expand...
Click to collapse
Have you got knex hardboot then because I need that for Ubuntu touch you don't need knex hardboot for android roms
JJMACCA said:
Have you got knex hardboot then because I need that for Ubuntu touch you don't need knex hardboot for android roms
Click to expand...
Click to collapse
I think its needed for android roms too. when ever i need to boot into another rom after flashing it says knex hardboot needed and it doesn't start up..
As i posted earlier neo kernel worked fine on 4.4(internal rom) with dePRIMAtor file (www.androidfilehost. com/?a=show&w=files&flid=9271).
Hopefully Tasssadar is patching the stock 4.4 kernel with kexec-hardboot.
To be able to get 4.4 running as "internal" Multirom.
mar_sch said:
Hopefully Tasssadar is patching the stock 4.4 kernel with kexec-hardboot.
To be able to get 4.4 running as "internal" Multirom.
Click to expand...
Click to collapse
Great!
Can you give us the link here??
activexda said:
Great!
Can you give us the link here??
Click to expand...
Click to collapse
here z the page... check for the link in second post..
http://forum.xda-developers.com/showthread.php?t=2472295
Edit : All issue is solved now check this post
Hi
This post is only intended for GPE converted 1033 users. i've seen many guys complaining in Dev section.
im a GPE converted 1033 user since the day i unlocked the bootloader.
in recent past had a issue with all the CM12 based roms like
1. Encryption Error due to EXT4 partition
2. WiFi wont work (CM integrated wifi modules into kernel)
3. Roms recognize my device as Dual SIM after converting to GPE
4. Continuous System UI force closes
earlier, all this problem solved by flashing Donkey Kang Kernel. Recently dev of DKK stopped support for our device
Solution
as a workaround till our devs fix the issue with GPE converted 1033 devices. i took DKK3.8 kernel and CM12 Based Boot.img (exactly RR rom) made a new boot.img which works for me without above mentioned problems. i'm just sharing my experience here. if you feel this workaround is useful please confirm
summary
RAMDISK form DKK3.8
Zimage from CM12 based Kernel(Integrated WiFi Modules)
How to install.
the provided file is boot.img directly (not a flashable zip. )
Latest TWRP supports flashing img files directly. please make use of it else you can also use apps like rashr which is available in playstore.
please make sure you know what you are doing before messing with your device.
PS : i'm not a developer
Edit : i tested with Resurrection Rom and i can confirm everything works as a single sim device on GPE converted 1033
Edit1 : tested with validus build 17-01 works prefectly
Edit2 : all credits to the developers
tell me the changes needed i'll rebuild my base around it..
bharat_goku said:
tell me the changes needed i'll rebuild my base around it..
Click to expand...
Click to collapse
Actually the problem started when cm integrated WiFi modules into the kernel.
Also when i compare ram disk. gpe check has changed in the recent kernels. Earlier separated fstab available for gpe device Now its merged
In my op the boot.IMG consists of ramdisk from DKK 3.8 and zimage from latest cm source
reversegear said:
Actually the problem started when cm integrated WiFi modules into the kernel.
Also when i compare ram disk. gpe check has changed in the recent kernels. Earlier separated fstab available for gpe device Now its merged
In my op the boot.IMG consists of ramdisk from DKK 3.8 and zimage from latest cm source
Click to expand...
Click to collapse
Can these changes be merged in official cm?? @bharat_goku can u pls tell me??
Sent from my Moto G using XDA Free mobile app
Differences between stock kernel and modified kernels
Stock kernel device recognised as dual sim in terminal
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Modified kernel device recognised as gpe in terminal
Flashhhh said:
Can these changes be merged in official cm?? @bharat_goku can u pls tell me??
Sent from my Moto G using XDA Free mobile app
Click to expand...
Click to collapse
Does this work for u
reversegear said:
Does this work for u
Click to expand...
Click to collapse
I haven't tested yet but it should work
Sent from my Moto G using XDA Free mobile app
can i flash this boot.img on donkey kang kernel or should reflash rom and then flash boot.img?
edit:just flashed it using rashr app on candy rom above donkey kernel and everything is fine...thanks for this fix
Will try now..
worked for me
This worked for me. I couldn't receive SMS after flashing any ROM. Now I can receive. Also my phone is being detected as gpe single sim now. But I have a query. Would multitasking be affected by changing this boot.img ? Or it is only just for setting up boot correctly. Please if u can elaborate. Sorry for being noob.
prasoon27 said:
This worked for me. I couldn't receive SMS after flashing any ROM. Now I can receive. Also my phone is being detected as gpe single sim now. But I have a query. Would multitasking be affected by changing this boot.img ? Or it is only just for setting up boot correctly. Please if u can elaborate. Sorry for being noob.
Click to expand...
Click to collapse
as far as multitasking is concerned it is as good as CM12 roms.
this link might be useful if you are concerned about multitasking http://forum.xda-developers.com/moto-g/general/fix-lmk-fixer-adj-t3007589
reversegear said:
as far as multitasking is concerned it is as good as CM12 roms.
this link might be useful if you are concerned about multitasking http://forum.xda-developers.com/moto-g/general/fix-lmk-fixer-adj-t3007589
Click to expand...
Click to collapse
Thanks for the response. You are right, there are no multitasking issues.
Working perfectly for me... flickering issue also stopped... Super smooth now... using Crdroid..
padhu1989 said:
Working perfectly for me... flickering issue also stopped... Super smooth now... using Crdroid..
Click to expand...
Click to collapse
what is that Flickering issue..
bcoz i never came across Flickering issue with my device.
reversegear said:
what is that Flickering issue..
bcoz i never came across Flickering issue with my device.
Click to expand...
Click to collapse
i think it happen to people who updated to stock lollipop or something like that...i never enconter it too bcz i never gone back to stock
I found the cause of this "bug" gpe converted. In cm11 when has the file persist.radio.multisim.config empty into /data/property is recognized as single sim (the file is created automacally on reboot, even if manually delete). Donkey lp too don't create this file automatically in cm12 (what hack he used i don't know), but if create manually or made a dirty flash from cm11 all kernels recognized as single sim (due file created on cm11), if delete or made a factory reset cm12 back to be recognized as dual.
I hope that info help devs to fix in official roms :fingers-crossed:
Update on the way
In the mean time : anyone using this modified kernel pls confirm whether compass tile works in cm12 based ROMs
For me it is struck in initializing
reversegear said:
Update on the way
In the mean time : anyone using this modified kernel pls confirm whether compass tile works in cm12 based ROMs
For me it is struck in initializing
Click to expand...
Click to collapse
Yeah it not working on rr it getting stuck on initializing
reversegear said:
Solution
as a workaround till our devs fix the issue with GPE converted 1033 devices. i took DKK3.8 kernel and CM12 Based Boot.img (exactly RR rom) made a new boot.img which works for me without above mentioned problems. i'm just sharing my experience here. if you feel this workaround is useful please confirm
Click to expand...
Click to collapse
Based on your solution I've been looking at the RAMDISK of the Donkey Kernel and found that the only file that is required to start system as GPE is his "init" binary within the ramdisk. I've tried with 3 differents kernels from AOSP based roms and worked.
ren2r said:
Based on your solution I've been looking at the RAMDISK of the Donkey Kernel and found that the only file that is required to start system as GPE is his "init" binary within the ramdisk. I've tried with 3 differents kernels from AOSP based roms and worked.
Click to expand...
Click to collapse
Glad to here that..
You can share ur boot.img here with the permission of the actual kernel/rom developers. by giving them credits
Does compass tile work in ur modified kernel
Edit:
I never knew still so many GPE converted 1033 users on XDA :happy:
Android Recovery Emulator
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The android recovery emulator is a utility that allows you to emulate the android recovery.
Most options are supported and you can flash zips and roms with this, wipe data/factory reset, clear cache etc, this is basically a virtual device.
Download here
REVIEW:
Like, Share and subscribe for more programming tutorials!
Supported syntax -
(#) comments
(ui_print) printing
(package_extract_file) extracting files
(package_extract_directory) extracting directories
(block_image_update) updating blocks
(run_program) execution
(delete) deleting
(delete_recurive) recursive deleting
(abort) aborting installation
(format) formatting
(mount) mounting
(set_perm) setting permissions
(set_perm_recursive) setting permissions recursively
(set_metadata) setting metadata
(set_metadata_recursive) setting metadata recursively
(symlink) symlinking
(show_progress) showing progress
Supported error output -
Checks for non existing files
Checks for non existing directories
Outputs possible errors for files or directories not embedded in zip
etc.
Remember to say thanks.
XDA:DevDB Information
Android Recovery Emulator, Tool/Utility for all devices (see above for details)
Contributors
Ricky Divjakovski
Version Information
Status: Stable
Current Stable Version: V1.0.0.0
Stable Release Date: 2017-04-16
Created 2017-04-16
Last Updated 2017-04-18
Okay... I could use something like this but, just 2 questions.
1) Will the results from the Emulator also reflect those results from a TWRP Recovery?
2) For the CWM that this Emulator is based upon, are the results based upon for the last known release version or for all release versions?
Thanks!
Ibuprophen said:
Okay... I could use something like this but, just 2 questions.
1) Will the results from the Emulator also reflect those results from a TWRP Recovery?
2) For the CWM that this Emulator is based upon, are the results based upon for the last known release version or for all release versions?
Thanks!
Click to expand...
Click to collapse
The GUI is merely a theme, based on latest recoveries
So could this be used to flash ROMs onto an unrootable device? Not "unrootable", but USB debugging doesn't work on it so I can't root it but there are ROMs for it
Beasty244 said:
So could this be used to flash ROMs onto an unrootable device? Not "unrootable", but USB debugging doesn't work on it so I can't root it but there are ROMs for it
Click to expand...
Click to collapse
No this is just an emulator, it doesn't do anything to a real device
Where was that Years ago? I'm alomst 24 and My whole Life was wasted on testing ZIPs... Could You please give Me back My Time? lol
Thanks a lot for that! You're a true Hero for Me dear OP. Keep it Up! :angel:
Great work as alawys.
I have idea on my mind several months ago!
Can you make twrp theme emulator so we can test themes on the run.
Or you can make this open source so I can make it my self.
Very nice. If the ability to emulate aroma installers could be added it would be really cool.
@Ricky Divjakovski , does this support the legacy environment? Like using update-binary? Shell?
BTW: works starts in Ubuntu 16.04 with mono.
But if these created subdirs with backslashes will really work? IDK
Hello there, just noob question, I used it with a stock ROM with supersu and dualrecovery ( I have stock z1 compact ) and this is what I get, why that errors ?
http://imgur.com/a/BmSNw
VERY GOOD , but it doesn't ''like'' magisk
could this be fixed or bypassed somehow, so be able to continue flashing and reach to the end ?
mohammad.afaneh said:
Great work as alawys.
I have idea on my mind several months ago!
Can you make twrp theme emulator so we can test themes on the run.
Or you can make this open source so I can make it my self.
Click to expand...
Click to collapse
Im going to add TWRP option in next version
jrkruse said:
Very nice. If the ability to emulate aroma installers could be added it would be really cool.
Click to expand...
Click to collapse
im already on it
will take about a week to properly implement
veez21 said:
@Ricky Divjakovski , does this support the legacy environment? Like using update-binary? Shell?
Click to expand...
Click to collapse
at the moment it only checks if the script exists via "run_program" and parsing the first arguement to the program that then checks if the file exists, if it doesnt it throws a possible error, shell support will eventually be added, but for now the basics
ranf said:
BTW: works starts in Ubuntu 16.04 with mono.
But if these created subdirs with backslashes will really work? IDK
Click to expand...
Click to collapse
i will be compiling this for linux aswell when i get some free time
JIJOK said:
Hello there, just noob question, I used it with a stock ROM with supersu and dualrecovery ( I have stock z1 compact ) and this is what I get, why that errors ?
http://imgur.com/a/BmSNw
Click to expand...
Click to collapse
thats because theres a second zip file inside your zip, thats not supported yes
logosA said:
VERY GOOD , but it doesn't ''like'' magisk
could this be fixed or bypassed somehow, so be able to continue flashing and reach to the end ?
Click to expand...
Click to collapse
seperate zip file? i will add the functionallity for that next build
Ricky Divjakovski said:
thats because theres a second zip file inside your zip, thats not supported yes
Click to expand...
Click to collapse
yes, saw that happened , flashed rom successfully but second zip (magisk) inside the rom made that error appears.
---------- Post added at 10:48 AM ---------- Previous post was at 10:45 AM ----------
Ricky Divjakovski said:
seperate zip file? i will add the functionallity for that next build
Click to expand...
Click to collapse
almost all the latest roms in Samsung galaxy Note 2 these days, include magisk as default root method.
This is a second zip inside the rom zip, which as I understood creates that error
logosA said:
yes, saw that happened , flashed rom successfully but second zip (magisk) inside the rom made that error appears.
---------- Post added at 10:48 AM ---------- Previous post was at 10:45 AM ----------
almost all the latest roms in Samsung galaxy Note 2 these days, include magisk as default root method.
This is a second zip inside the rom zip, which as I understood creates that error
Click to expand...
Click to collapse
im working on a fix for that now so maybe tonight or tommorow when i get free time i will release
That really will be a tremendous help for us, who flash roms all day long and got stuck in bootloops and errors.
This way , we will be able to test before actually try.
Thank you very much OP.
Excellent, original work !
@Ricky Divjakovski this so needed emulate zip installer... I wish i could have found this years back. Great work.
A video review has been published.
Remember to follow me on youtube for programming tutorials, guides and reviews!
oppo ozip2zip tool:
Used in ubuntu 64 bit:
Support devices:
r9s、r11、a77
command:
HTML:
./OppoDecrypt *.ozip -device_name
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
oppo r9s device_name is:r9s
oppo r11 device_name is:r11
oppo a77 device_name is:a77
Download:https://www.androidfilehost.com/?fid=817550096634792751
if u feel that this work has helped u OR u think that the work i put into making this is worthy of donations, then click on the following link for buying me some coffee/beer/etc:fingers-crossed:
PAYPAL DONATION LINK
Contributors
cofface
Version Information
Status: Stable
Created 2017-08-08
Last Updated 2017-08-14
Can you explain more about thia tool?
This is a wonderful share, thank you very much! :good:
---------- Post added at 08:00 PM ---------- Previous post was at 07:55 PM ----------
sagargjasani264 said:
Can you explain more about thia tool?
Click to expand...
Click to collapse
I just became aware of this tool so I have yet to utilize it, but I am very familiar with current, official firmware as provided by Oppo.
Oppo's .ozip format is merely an encrypted archive that I have never penetrated. The content of the OP suggests that a Linux solution for extracting official Oppo firmware is finally available. :good:
didn't work! I get error message --- buffer overflow detected: ./OppoDecrypt terminated.
I typed ./OppoDecrypt CPH1707EX_11_OTA_0070.ozip -r11 on Ubuntu terminal.
Oppo R11
I downloaded the R11 ozip file here
http://www.oppo.com/au/downloads/
hello i actually followed what said in the guide and worked fine, now i have an oppo r9s plus chinese version , and i opened the rom thanks to oppodecrypt and than i made the rom unpack , actually i would like to use the rom pubblished in singapore website wich should be coloros 3.0i international , but to do this i need to find where the modem files are in the chinese rom and copy and replace the one in the singapore rom .
I am not an expert in that anyone can tell me :
1 where i will find the files
2 if i repack the rom and with a tool i add the signature can i hope to re encrypt the rom and flash without twrp?
3 in case i need to use twrp how to repack correctly the rom to be flashed?
4 did i forgot to change other vaulues in the rom to make it work?
thanks to everyone for the precious help, i love xda is source of good information.
I also managed to decrypt ozip for r9s and A77 but it didn;t work on R11.
Actually have you tried to unpack the zip file? if you have, you will realize the essential file system.new.dat couldn't get extracted - you will get an error message.
Regarding your questions below.
(1) Chinese forum. But you won;t be able to replace the modem.
(2)even if you can repack, it will fail the signature verification and can't proceed with installtion if you flash thru' official recovery/
(3) can't repack that way, you've to use msmdownload tool
(4)don't mess around without knowing what you are doing, otherwise you will brick your oppo.
StevenHood said:
hello i actually followed what said in the guide and worked fine, now i have an oppo r9s plus chinese version , and i opened the rom thanks to oppodecrypt and than i made the rom unpack , actually i would like to use the rom pubblished in singapore website wich should be coloros 3.0i international , but to do this i need to find where the modem files are in the chinese rom and copy and replace the one in the singapore rom .
I am not an expert in that anyone can tell me :
1 where i will find the files
2 if i repack the rom and with a tool i add the signature can i hope to re encrypt the rom and flash without twrp?
3 in case i need to use twrp how to repack correctly the rom to be flashed?
4 did i forgot to change other vaulues in the rom to make it work?
thanks to everyone for the precious help, i love xda is source of good information.
Click to expand...
Click to collapse
Well I was able to extract everything, and actually I see all the packages of the apps etc just I need to know in what folder the modem files are located... If I will manage to know how to put a picture.... I will show u what I mean..
The tool works
Look at mine and you will know where I'm coming from....
StevenHood said:
The tool works
Click to expand...
Click to collapse
This doesn't look like a complete set. all essential files are missing
StevenHood said:
The tool works
Click to expand...
Click to collapse
I was there before , u should open using a Linux 64 bit pc
carlochiefsg said:
This doesn't look like a complete set. all essential files are missing
Click to expand...
Click to collapse
cool finally i got somebody that look is understand what we are talking about?? well i will link now the result of using the cofface converter ... actually after that i used a system dat extractor found here in xda in another topic.... just to give all the details about what i did.
anyway here is link to my result https://drive.google.com/open?id=0B0YNufbboWNPY3h4WV8wWUlqaGc
let me know if you can help with my project
will it work for oppo f3 cph1609 .ozip format ?
carlochiefsg said:
didn't work! I get error message --- buffer overflow detected: ./OppoDecrypt terminated.
I typed ./OppoDecrypt CPH1707EX_11_OTA_0070.ozip -r11 on Ubuntu terminal.
Oppo R11
Click to expand...
Click to collapse
i have same problem ubuntu 17.10 64 bit ...
can you solve this ?
DO NOT USE THIS TOOL! It has a bug that losing some data at the end of the result file.
dont work R11 Plus :S
I've tried this one - abpprook/ozip2zip from github (sorry, I cannot post links yet)
Works perfect on Windows and Ubuntu
It does not works with R11 global rom CPH1707EX
are you able to fix ?
cofface said:
oppo ozip2zip tool:
Used in ubuntu 64 bit:
Support devices:
r9s、r11、a77
command:
HTML:
./OppoDecrypt *.ozip -device_name
oppo r9s device_name is:r9s
oppo r11 device_name is:r11
oppo a77 device_name is:a77
Download:https://www.androidfilehost.com/?fid=817550096634792751
if u feel that this work has helped u OR u think that the work i put into making this is worthy of donations, then click on the following link for buying me some coffee/beer/etc:fingers-crossed:
PAYPAL DONATION LINK
Contributors
cofface
Version Information
Status: Stable
Created 2017-08-08
Last Updated 2017-08-14
Click to expand...
Click to collapse
I have to agree on the R9S Plus, it actually decrypts, but when you try to extract the zip file, the system.new.dat file is corrupted.