Ok so maybe this sounds crazy but it's possible... at least on HTC devices...
Check this: http://forum.xda-developers.com/showthread.php?t=970543
So that is a kernel for CM7, flashable by Recovery... I removed the module in the archive then I tried: replacing the kernel with Arc one and flash; modifying the makebootimg.sh; adding also Ramdisk.
So can we make this work on our Arcs too? It would be amazing, because we will be able to alternate and change the ROMs whenever we want
Related
Hi,
I have downloaded kernel sources from HTC for wildfire and compiled zImage. using unpack and repack scripts I successfully installed the boot.img via update.zip. Now I see the device reboots fine, but I cannot unlock the screen, and none of the keys are functional.
I have no Idea what is still missing or have I done something wrong?? your help is need here.
Indeed I tried to compile jacobs kernel image from github but no luck.
Regards
bram
can anybody deliver the stock 2.3.4 kernel as an image to reflash via recovery if one wants to go back from a custom kernel?
would be easier, than using an old backup or reflash the whole ROM due to lost data, apps, sms, etc.
Second to that....maybe someone can help us.
Best Regards
Third to that! Want to try custom kernel, but don't want reflash whole image, if I'll not like it.
evlevl said:
Third to that! Want to try custom kernel, but don't want reflash whole image, if I'll not like it.
Click to expand...
Click to collapse
do a nandroid backup. it saves kernels
Flashing back stock kernel will not allways help , because some other alterations (e.g. in intit.d) will still remain .. But if you want the stock 2.3.4 kernel .. you can download the full rom posted by me or given in an other thread .. set a side the boot.img and flash it with fastboot ( fastboot flash boot boot.img)
If you do not want to download load an entire rom I attached the stcok 2.3.4 kernel .
Bandis710 said:
Flashing back stock kernel will not allways help , because some other alterations (e.g. in intit.d) will still remain .. But if you want the stock 2.3.4 kernel .. you can download the full rom posted by me or given in an other thread .. set a side the boot.img and flash it with fastboot ( fastboot flash boot boot.img)
If you do not want to download load an entire rom I attached the stcok 2.3.4 kernel .
Click to expand...
Click to collapse
excellent, thanx mate! i don't want to flash a whole rom just to get back on stock kernel, because all the backing up and restoring if not necessary is boring...
and does that really set back all changes, a custom kernel does on my phone? aren't there also always some folders in the zip-files of customs?
Well, now I see a reason why there is no "default kernel".
It's because all these custom kernels consist not only from "boot.img", but also from a number of "init.d scripts", "*.so modules", etc, which are obviously different from kernel to kernel. So because of that you cannot have an universal "stock" kernel, but rather a whole stock ROM.
Thanks a lot for all of you who comment that request, now the situation with kernels is more clear.
While all the above is sensible, it should be possible with a modicum of planning to go back and forth between a custom kernel and the stock one. I feel the question is more: is it worth the trouble versus flashing again? Probably not.
1 - Nandroid backup.
2 - Examine the scripts and files included in the custom kernel's zip.
3 - Back up what is replaced, patched or deleted outright from stock.
4 - Note what is added by the custom kernel.
When you want to revert to stock, reflash boot.img from stock, and either adb push the stock backup files back, or create your own update zip with a proper script to finish the job.
nfinitefx45 did this build by my request. but after flashing with his rom my kf stucked at kf boot logo. i solved this cause by replacing original boot.img by boot.img from stock rooted for dualboot. now my kf work perfectly. hope it`ll be useful for someone.
remember that this is only update. at first you need to install stock for dualboot. you can find it in android development thread in fff ex. bootloader section
this is link for download:
http://www.mediafire.com/?j5kh3y1tqj2gayw
I wanted to thank you for this ROM version. It works as advertised!
Thanks... plee3
updàte
Has anyone tested this rom? What's your feelings?
I only used it for a short time to make sure it was working correctly. But I am currently using Modaco Gr8 on my primary partitions and the stock ROM on the secondary partitions was too limiting (no play store and google apps).
So I tried to modify the Modaco Gr8 to run in the secondary partitions, but it would not boot correctly. Nor could I make any of the CM9/AOKP ROMs run on the secondary partitions. I followed all the listed steps to the init.omap4430.rc and updater-script files, but they would not boot up correctly.
In fact, the only other ROM that would boot correctly was the CM7 ROM that eldarerathis provided in his original thread.
Of course in performing these experiments wiped out the NFX ROM, so I no longer am running the NFX ROM on the secondary partitions.
I hope this helps... plee3
i know. we should make three different boot.img and updater-script files. if you want to covert your primary boot rom to alternate boot rom simply change these files. i expect boot.img and updater-script altboot for cm9
Thanks so much for this. Works great. Also using Modaco Gr8
DukeSilver79 said:
Thanks so much for this. Works great. Also using Modaco Gr8
Click to expand...
Click to collapse
Are you saying that you have Gr8 running in the secondary partitions?
If so, what additional changes did you make to change the Gr8 ROM?
Thanks... plee3
Change updater-script and replace by insecure boot.img from stock for altboot
I got Paranoid 3 as my internal rom, running franco kernel. However, gaming and file transfer with computer seem slow and laggy as a 2gigs movie took 15 mins to copy from pc to nexus 7, so I'd like to install stock rom and stock kernel as an alternative I can use when I want to transfer files. The problem is Multiboot only allow separate kernel for external roms as boot.img, and the kexec patched stock kernel (any many other kernels) is only released under .zip flashable. So does anyone have any solution to this? Please tell me
Um, what's the problem with flashing stock kernel over then stock ROM through Install menu in the recovery?
Fatal1ty_18_RUS said:
Um, what's the problem with flashing stock kernel over then stock ROM through Install menu in the recovery?
Click to expand...
Click to collapse
Well, there are too options to flash zip:
- flash zip thru install menu. This affects the internal ROM and Roms that share kernel with internal one
- flash zip thru multi boot -> manage roms -> choose a specific rom . The description already says that 'don't flash kernel with this option' and if I did, the ROM wouldn't boot.
So, way I see it, there's only one option to inject a boot.img that houses a kernel to the eexternal ROM, but the kernels I need are not released as a .img
Bump ? Anyone ?
Hi,
I have a small question. I own a Canadian Samsung 4 SGH-i337m, after reading the main guide for running other carrier rom on this address
http://forum.xda-developers.com/showthread.php?t=2295557
As the guide mention that I didn't need the loki kernel and I could use my carrier kernel.
I used to backup my kernel with SGS kernel flasher to do the job, but it's not working for s4.
I wanted to backup my stock kernel and apply it after the installation of a cursom rom and apply it through TWRP. As I understood it, kernel is the boot.img, and I read somewhere that the way to create this is to copy the boot.img + copy the /sytem/lib/modules files. If I look to the file prepared by iB4STiD in the file MDOB-I337M-VMK6-FIX-4.1 present here, it seems that it's the case.
There is still flashify as a solution but you can't use the file into recovery.
Does someone know how to do it, or point me out where to find a guide where I can do what I want.
thanks in advance,
youpiyo said:
Hi,
I have a small question. I own a Canadian Samsung 4 SGH-i337m, after reading the main guide for running other carrier rom on this address
http://forum.xda-developers.com/showthread.php?t=2295557
As the guide mention that I didn't need the loki kernel and I could use my carrier kernel.
I used to backup my kernel with SGS kernel flasher to do the job, but it's not working for s4.
I wanted to backup my stock kernel and apply it after the installation of a cursom rom and apply it through TWRP. As I understood it, kernel is the boot.img, and I read somewhere that the way to create this is to copy the boot.img + copy the /sytem/lib/modules files. If I look to the file prepared by iB4STiD in the file MDOB-I337M-VMK6-FIX-4.1 present here, it seems that it's the case.
There is still flashify as a solution but you can't use the file into recovery.
Does someone know how to do it, or point me out where to find a guide where I can do what I want.
thanks in advance,
Click to expand...
Click to collapse
What type of ROM are you using? You have to be using a compatible kernel. AOSP ROM's won't work with a stock kernel, and you can't cross Android version between system and kernel. Using any custom kernel developed for your phone with this guide will work okay however.
Thank you for your answer.
in order to answer your question I was trying to flash the hyperdrive to my phone with compatibility pack. But after reboot I go back directly to download mode. So I figured that it was the boot partition that wasn't adapted to my phone.
So yes, I understand that if you flash a rom based on code as cyanogenmod you will need a custom kernel. but for a rom that is based on stock as hyperdrive rom, unless I'm mistaken, I would imagine that the stock kernel should work.:cyclops:
Is there a way to back it up?
youpiyo said:
Thank you for your answer.
in order to answer your question I was trying to flash the hyperdrive to my phone with compatibility pack. But after reboot I go back directly to download mode. So I figured that it was the boot partition that wasn't adapted to my phone.
So yes, I understand that if you flash a rom based on code as cyanogenmod you will need a custom kernel. but for a rom that is based on stock as hyperdrive rom, unless I'm mistaken, I would imagine that the stock kernel should work.:cyclops:
Is there a way to back it up?
Click to expand...
Click to collapse
My best guess is find out which partition it is and use the dd command OR download the ODIN of your firmware version and extract the boot.img. However, it would be easier to just use a custom kernel designed for your phone as if you back it up like that you either have to make it into a flashable zip or use heimdall to restore it every time.
Sent from Black<3's I337 running Foxhound ROM
Thanks for your answer.
That's weird as a nandroid is doing the job,that is hard to find how to backup a kernel.
anyway, I guess my best chance is to download a custom kernel and apply it after installation of the cutom rom. At first boot re apply a backup kernel with an app as flashify.
thanks youpi