Hi there
I've got a quick question: Right now I'm using Franco's Kernel with the stock 4.4.2 ROM. I also want to test experimentalX (i heard it's a tad snappier). Is it correct that instead of flashing from Franco directly to experimentalX, I install the stock kernel again with TWRP. After that i can flash to experimentalX.
I also use Xposed with a few modules. Is that going to be a problem?
Cheers!
2mnyshp said:
Hi there
I've got a quick question: Right now I'm using Franco's Kernel with the stock 4.4.2 ROM. I also want to test experimentalX (i heard it's a tad snappier). Is it correct that instead of flashing from Franco directly to experimentalX, I install the stock kernel again with TWRP. After that i can flash to experimentalX.
I also use Xposed with a few modules. Is that going to be a problem?
Cheers!
Click to expand...
Click to collapse
Yes You can directly flash experimental X from FRANCO kernel ...
Try yourself and tell us whether it gives a problem or not ?!!! :sly:
Sent from my Nexus 5 using Tapatalk
ok thanks! I'll try it this evening
rahil3108 said:
Yes You can directly flash experimental X from FRANCO kernel ...
Try yourself and tell us whether it gives a problem or not ?!!! :sly:
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
2mnyshp said:
Hi there
I've got a quick question: Right now I'm using Franco's Kernel with the stock 4.4.2 ROM. I also want to test experimentalX (i heard it's a tad snappier). Is it correct that instead of flashing from Franco directly to experimentalX, I install the stock kernel again with TWRP. After that i can flash to experimentalX.
I also use Xposed with a few modules. Is that going to be a problem?
Cheers!
Click to expand...
Click to collapse
You can be sure about flashing the stock boot.img first simply looking at the zip of your already installed kernel.. If the zip includes boot.img file you should flash the stock boot.img first, then your new custom kernel.
if the zip just includes kernel.img then you can flash your custom kernel over it safely.
Xposed isn't related to the kernel flashing, it won't cause any issue
Inviato dal mio Nexus 5 utilizzando Tapatalk
Hi,
Have you read the OP of ElementalX kernel?
NOTE: If you have been using a different custom kernel, please reflash your ROM without wiping data prior to installing this kernel. This will ensure you have all the necessary system files and that customizations from other kernels do not interfere.
Click to expand...
Click to collapse
With Francisco's kernel some system files are modified so better is to dirty flash your rom or at least the stock kernel before...
Just in case for the stock kernel: http://forum.xda-developers.com/showthread.php?t=2518816.
EDIT: too late...
OK, that's the way I would've done it; I put the stock kernal zip on my phone, flash that with TWRP and after that flash ElementalX. I'm not sure about the dirty stock rom flash: Can i just extract the system.img from the official android hammerhead download, put the img on my phone and flash that over my current rom?
Sorry for these trivial questions but the answers to such topics in other threads are sometimes a bit unclear.
Re,
If you have already flashed the stock kernel (so the boot.img) it should be enough... But Francisco's kernel rename some system files like /system/lib/hw/power.msm8974.so or /system/bin/thermal-engine-hh so with a dirty flash of your current rom all the files are replaced (and you won't loose anything, just wipe Dalvik cache and cache partition, just in case then reflash your rom).
Check if the files I mentioned don't have a .bak extension (with a file explorer follow the path above), if not all is fine. If yes, and if you are convenient, delete the .bak extension by yourself.
If you are not convenient with this (I mean delete some extension in system files), dirty flash your rom, reboot (as always just in case, to be sure, etc...), flash your new kernel... And you're good to go!
viking37 said:
Re,
If you have already flashed the stock kernel (so the boot.img) it should be enough... But Francisco's kernel rename some system files like /system/lib/hw/power.msm8974.so or /system/bin/thermal-engine-hh so with a dirty flash of your current rom all the files are replaced (and you won't loose anything, just wipe Dalvik cache and cache partition, just in case then reflash your rom).
Check if the files I mentioned don't have a .bak extension (with a file explorer follow the path above), if not all is fine. If yes, and if you are convenient, delete the .bak extension by yourself.
If you are not convenient with this (I mean delete some extension in system files), dirty flash your rom, reboot (as always just in case, to be sure, etc...), flash your new kernel... And you're good to go!
Click to expand...
Click to collapse
Thanks! And for the dirty flash i can use the System.img which i extracted with TWRP after i cleaned the dalvic cache, right?
2mnyshp said:
Thanks! And for the dirty flash i can use the System.img which i extracted with TWRP after i cleaned the dalvic cache, right?
Click to expand...
Click to collapse
Re
I don't understand what you mean here, you are on full stock rom? You have not flashed a rom from a zip file?
viking37 said:
Re,
If you have already flashed the stock kernel (so the boot.img) it should be enough... But Francisco's kernel rename some system files like /system/lib/hw/power.msm8974.so or /system/bin/thermal-engine-hh so with a dirty flash of your current rom all the files are replaced (and you won't loose anything, just wipe Dalvik cache and cache partition, just in case then reflash your rom).
Check if the files I mentioned don't have a .bak extension (with a file explorer follow the path above), if not all is fine. If yes, and if you are convenient, delete the .bak extension by yourself.
If you are not convenient with this (I mean delete some extension in system files), dirty flash your rom, reboot (as always just in case, to be sure, etc...), flash your new kernel... And you're good to go!
Click to expand...
Click to collapse
viking37 said:
Re
I don't understand what you mean, you are on full stock rom? You have not flashed a rom from a zip file?
Click to expand...
Click to collapse
yes, stock 4.4.2 only with a custom kernel (franco's as of now)
Yes, or at least just take a look at the files I mentioned following the path with a file explorer to see is there is still not the .bak extension. And after flashed ElemantalX kernel, obviously.
As far as I know it should be the only modified system files, I mean renamed since in Francisco's kernel they are not used, that "could" caused issues...
Related
How difficult would it be to "rip" a kernel from a ROM, to use in a different ROM? Is it a matter of pulling certain files from the zip and creating and signing a new zip, or is it much more involved?
Try it and find out. It's pretty easy to find. Not all ROMs include a kernel, so try out the Andromeda one for example, which does include a kernel.
ragnarokx said:
How difficult would it be to "rip" a kernel from a ROM, to use in a different ROM? Is it a matter of pulling certain files from the zip and creating and signing a new zip, or is it much more involved?
Click to expand...
Click to collapse
ragnarokx said:
How difficult would it be to "rip" a kernel from a ROM, to use in a different ROM? Is it a matter of pulling certain files from the zip and creating and signing a new zip, or is it much more involved?
Click to expand...
Click to collapse
If the rom you want to put it in has a kernel then it is just a matter of replacing the zImage in one with the other. Then resign.
For a rom that doesnt have one it could get a little uglier but still easy. (I just use one that has a kernel in it.)
smeyerhuky said:
If the rom you want to put it in has a kernel then it is just a matter of replacing the zImage in one with the other. Then resign.
For a rom that doesnt have one it could get a little uglier but still easy. (I just use one that has a kernel in it.)
Click to expand...
Click to collapse
So all I need is the "zImage"? I don't need the "redbend_ua" or files in any other folder?
And I did want to transplant this kernel to a ROM that doesn't come with a kernel, but you're saying that's not easy to do. So what if instead of putting the kernel directly in the ROM, I take a stand-alone kernel zip, put my zImage in there, resign, and install the kernel after I install the ROM. Would that work?
[QOUTE]So all I need is the "zImage"? I don't need the "redbend_ua" or files in any other folder? [/QOUTE]
as long as the rom your using had redbend_ua then there is no need to copy it over, but its the same redbend_ua for both probably.
ragnarokx said:
So what if instead of putting the kernel directly in the ROM, I take a stand-alone kernel zip, put my zImage in there, resign, and install the kernel after I install the ROM. Would that work?
Click to expand...
Click to collapse
That is what I always do., ps I include my keyboard hack as well. Don't forget to resign...
Sent from my SPH-D700 using XDA App
just installed oc kernel by cocafe on maclow studio 11 rom with art enabled and magic begins my GT-I9070 beats galaxy s 2 and asus transformer in benchmark score wwwwwwooooooooooowwwww........ my sgs advance was is lightning faaaaaaaast
installation :
ukf kernel flasher not support kk version si i gone this way
>delete boot. img from maclow studio rom (use windows pc to open zip archive)
> paste oc kernel boot. img in maclow studio rom
oc kernel http://d-h.st/vrW
>now flash this modified zip in recovery no need to perform wipe
bugs
wifi will not work anymore shhhhhiiiit........ waiting for albertoes or maclows overclocked rom
Please tell me your settings:victory:
And to make wifi work , copy all files from system/lib/modules of the aosp rom to your cm11
DaRkRhiNe said:
Please tell me your settings:victory:
And to make wifi work , copy all files from system/lib/modules of the aosp rom to your cm11
Click to expand...
Click to collapse
performance settings
>ondemand+deadline
>art enabled
>all cm tweaks kernel sampage+16 bit transperancy+purging of assets
>enabled 2d drawing in development settings
i don't have aosp rom and don't want to download whole rom plz can u give me all system lib files at u r Dropbox to enable wifi
Any ideas on why I can't install the modified zip? I replaced the original boot.img with the OC version and put the modified zip on the sdcard. I get Installation Aborted without any reason.
.venice. said:
Any ideas on why I can't install the modified zip? I replaced the original boot.img with the OC version and put the modified zip on the sdcard. I get Installation Aborted without any reason.
Click to expand...
Click to collapse
which rom u modified maclow or carbon or else
u have to open original zip in window on pc (just by clicking on it)
> then delete original boot.img
>then just paste oc kernel bootimage, do not touch anywhere
>do not extract zip and repack it (because it is signed zip if u extract it its signature verification got failed)
.venice. said:
Any ideas on why I can't install the modified zip? I replaced the original boot.img with the OC version and put the modified zip on the sdcard. I get Installation Aborted without any reason.
Click to expand...
Click to collapse
If you edit the zip you will break Samsung signature.Install CWM recovery and before install disable signature check.
DaRkRhiNe said:
Please tell me your settings:victory:
And to make wifi work , copy all files from system/lib/modules of the aosp rom to your cm11
Click to expand...
Click to collapse
Did you try that? and WiFi is working? or is just theory.
This oc kernel just get me LOTS of reboots everywhere!! Even on IDLE
rodaven said:
Did you try that? and WiFi is working? or is just theory.
Click to expand...
Click to collapse
its not theory its truth
Hi everyone! First of all, sorry for my english.
My question is very simple. I am going to flash Aero Kernel into my Moto G xt1034.
In case something goes wrong or i want to go back to stock kernel, does reflash the rom via fastboot replaces the kernel? I mean, Aero Kernel is ereased and replaced by the stock kernel?
Thank you very much in advance!
Yep, boot.img is your kernel, so you need to flash that at least. But, I think aero is replacing your kernel modules too (eg the WiFi driver), so you need to flash the system image too. Or backup the original modules from the /system/lib/modules directory.
Rhyn said:
Yep, boot.img is your kernel, so you need to flash that at least. But, I think aero is replacing your kernel modules too (eg the WiFi driver), so you need to flash the system image too. Or backup the original modules from the /system/lib/modules directory.
Click to expand...
Click to collapse
Thank you. Does flashing stock Rom replaces those modules ?
neucoas said:
Thank you. Does flashing stock Rom replaces those modules ?
Click to expand...
Click to collapse
If you mean by flashing is fastboot flash etc, then yes. The system.sparesechunk.0-3 files contains your full system partition including the kernel modules. But if you do a cwm backup from your stock system partition before flashing aero and flash that back, that will work too.
Edit: if you just do a backup from /system/lib/modules directory, you should include /system/lib/hw/power.msm8226.so too, hence aero installer also deletes that too.
Usually if you uncertain what a flashable zip do, you can always examine the META-INF/com/google/android/updater-script file. Thats the installer, you can open it with a simple text editor. Usually not too hard to understand, its quite a simple language.
Rhyn said:
If you mean by flashing is fastboot flash etc, then yes. The system.sparesechunk.0-3 files contains your full system partition including the kernel modules. But if you do a cwm backup from your stock system partition before flashing aero and flash that back, that will work too.
Edit: if you just do a backup from /system/lib/modules directory, you should include /system/lib/hw/power.msm8226.so too, hence aero installer also deletes that too.
Usually if you uncertain what a flashable zip do, you can always examine the META-INF/com/google/android/updater-script file. Thats the installer, you can open it with a simple text editor. Usually not too hard to understand, its quite a simple language.
Click to expand...
Click to collapse
Thank you very much! :victory:
Hi guys, I was able to extract system.new.dat from a rom (purity lollipop) and now I have the old good system with folders, so I can change whatever I want. But I tried to flash the zip and only the boot.img gets installed, the rest seems to be ignored.. What should I change in the zip on order to get it to install correctly?
carlese said:
Hi guys, I was able to extract system.new.dat from a rom (purity lollipop) and now I have the old good system with folders, so I can change whatever I want. But I tried to flash the zip and only the boot.img gets installed, the rest seems to be ignored.. What should I change in the zip on order to get it to install correctly?
Click to expand...
Click to collapse
Look at the updater-script
Lethargy said:
Look at the updater-script
Click to expand...
Click to collapse
Can I use the updater from the same rom but kitkat version? The things I install are the same I think..
This zip is a pure stock firmware with no extra stuff added! Only the boot.img is bumped and the modem is hybrid(v30 + v20 to make bump compatible).
Features:
Added from the stock v30 base:
system.img
modem.img - hybrid one(contains v30 + v20 stuff)
boot.img - bumped
rpm.img
tz.img
cust.img
selinux is permissive
How to install:
Wipe system, data, cache, dalvik cache for a clean install.
Flash D850_V30_Bumped.zip
For root:
SuperSU - flash BETA-SuperSU-v2.52.zip.(No SafetyNet pass).
MagiskSU - get it from the official magisk thread.(Passes SafetyNet).
Reboot
Downloads:
v30A [2017-02-09] - Click here to download (MD5: 95ff1dd2e38439e2dea3c46f4a49c3ee)
BETA-SuperSU-v2.52.zip - Click here to download
SharpeningMOD fix - Click here for thread
Mirrors are welcome because this is most probably the first and the last firmware that will come to the D850. It will be good if someone share a picture of about-phone that shows the software info
Modems:
v30A + v20A - Click here to download
v20A - Click here to download
Q&A:
What's different in the hybrid modem?
Check this post - click here
How is this different to other MM stock rom's out there?
This not an extracted system.img rom like others. It contains extracted .kdz files and just flashes them. Permissive selinux is included, alongsite 3 build.prop changes to make for better compatibility(this is an D850PR kdz). Nothing else, no tweaks, no other stuff added.
What does [2017-02-09] mean?
That's build date of the kdz(can be checked in build.prop, kernel build date...)
These are the build.prop changes:
Code:
ro.build.target_country=[B]COM[/B]/ro.build.target_country=[B]US[/B]
telephony.lteOnCdmaDevice=[B]0[/B]/telephony.lteOnCdmaDevice=[B]1[/B]
ro.product.locale=en-[B]GB[/B]/ro.product.locale=en-[B]US[/B]
Thanks man! Great work!
Noob Question: I am on Stock KitKat ROM with KitKat Modem. To upgrade into this, do I also need to flash the hybrid modems as well, then flash this ROM? Or the MM ROM already has the modem on it, and do I just need to flash the ROM?
souler456 said:
Noob Question: I am on Stock KitKat ROM with KitKat Modem. To upgrade into this, do I also need to flash the hybrid modems as well, then flash this ROM? Or the MM ROM already has the modem on it, and do I just need to flash the ROM?
Click to expand...
Click to collapse
The modem is already included in the full zip. I don't think you will have any problem. Most partitions from kdz are already included, so it should work fine. If not you must update to LP but that's only if this doesn't work.
Dear OP,
Please add Theme engine support to Stock Launcher, rest is awesome.
hemal_4404 said:
Dear OP,
Please add Theme engine support to Stock Launcher, rest is awesome.
Click to expand...
Click to collapse
Hello. It's strange because it's there but I guess just disabled. LGHome is the same like other variants. Do you use xposed? With xposed there may be an easy fix but without it need to investigate little more.
I am not using Xposed, and kept rom completely stock.
But Theme engine is not available.
hemal_4404 said:
I am not using Xposed, and kept rom completely stock.
But Theme engine is not available.
Click to expand...
Click to collapse
Hello. Download apk from attachments and replace it in - system/vendor/overlay/com.lge.launcher2 with rw-r-r permissions. Do a backup of the original file just in case. Tell me if this works or not.
MESA said:
Hello. Download apk from attachments and replace it in - system/vendor/overlay/com.lge.launcher2 with rw-r-r permissions. Do a backup of the original file just in case. Tell me if this works or not.
Click to expand...
Click to collapse
I think something is wrong with attached file as it's size is only 160 KB.
hemal_4404 said:
I think something is wrong with attached file as it's size is only 160 KB.
Click to expand...
Click to collapse
No it's not. Try it.
MESA said:
No it's not. Try it.
Click to expand...
Click to collapse
Tried but makes no difference.
MESA said:
Hello. Download apk from attachments and replace it in - system/vendor/overlay/com.lge.launcher2 with rw-r-r permissions. Do a backup of the original file just in case. Tell me if this works or not.
Click to expand...
Click to collapse
You must make changes in etc/permissions...
Ducatuca said:
You must make changes in etc/permissions...
Click to expand...
Click to collapse
Done but no changes.
hemal_4404 said:
Done but no changes.
Click to expand...
Click to collapse
What do you mean? What did you change in etc/permissions?
MESA said:
Hello. Download apk from attachments and replace it in - system/vendor/overlay/com.lge.launcher2 with rw-r-r permissions. Do a backup of the original file just in case. Tell me if this works or not.
Click to expand...
Click to collapse
I followed exactly same as mentioned.
hemal_4404 said:
I followed exactly same as mentioned.
Click to expand...
Click to collapse
Yes, but I wrote to @MESA to make changes in file which is in etc/permissions...
Ducatuca said:
Yes, but I wrote to @MESA to make changes in file which is in etc/permissions...
Click to expand...
Click to collapse
What file are you talking about? If you have any idea about the fix share it here.
[/COLOR]
MESA said:
What file are you talking about? If you have any idea about the fix share it here.
Click to expand...
Click to collapse
Try to download my rom which is the same for d850. And check the permissions folder. U will find the difference in size. I can't remember which exact file is for theme (it can be com.lge.permissions.xml but i'm not 100% sure)...
Ducatuca said:
You must make changes in etc/permissions...
Click to expand...
Click to collapse
Waiting for fix.
Ducatuca said:
[/COLOR]
Try to download my rom which is the same for d850. And check the permissions folder. U will find the difference in size. I can't remember which exact file is for theme (it can be com.lge.permissions.xml but i'm not 100% sure)...
Click to expand...
Click to collapse
All files from that folder are the same.
Do you use d850 system from kdz? Because all apk files are different.