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
So I was trying to get into rom development and got the stock rom from scottsrom, who also made cleanrom, with the following details.
This is the AT&T Stock Rooted MDL Base!
Stock
Rooted
De-Odex
Busybox
Zip Aligned
init.d Support
Knox Agent removed
NOT LOKI'ED! Must have recovery with Auto Loki!
MD5: 8DD8C6CD8FD17362512442FFE16513A0
Click to expand...
Click to collapse
All I did was make a working folder with this base and then built a rom from the working folder. I did not edit anything, not even the updater-script. When I flashed the newly built rom, I got the status 6 error. Am I doing something wrong?
And yes, the base rom was functional when I flashed it. Only the newly built rom had the status 6 error.
I try several methods to activate init.d support on leaked 4.4.2 with stock kernel ,but no one was successful.
Can someone help me ?
you placed the service in the init.rc of the kernel right?
No,when I try this and flash kernel , phone's goes to bootlop.
I try with several scripts , but they don't work.
mom4ence said:
No,when I try this and flash kernel , phone's goes to bootlop.
I try with several scripts , but they don't work.
Click to expand...
Click to collapse
Do it manually. The scripts are probably getting the repacking incorrect.
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
Hi, i have been trying to find a compatible updater-script for my phone to be able to flash a modified stock rom using android kitchen. The way android kitchen modify the update-script to updater-script is not working with my philz touch recovery latest version installed, even if i checkmark the option to use the old update-script method the installation goes thru inside the recovery but i am unable to start the system, it loops on the samsung logo.
any ideas where i can find a compatible updater-script and updater-binary ? i dont know what else i can provide as information to be more clear on the issue. I know a lot of ppl if not all who try to create custom roms are having, searching google did not help and searching the forums either because the results are not for my device specific SGH-M919V and i sure dont want to brick the phone. So far i was able to remove knox, bloatware i personnaly dont want to have in my rom. I am not a coder but i can understand the logics of some scripts.