How do I remove dual core scripts... Or whatever is enabling them... I tried a couple kernels and still activated. Running eternity 1.4.2
Sent from my PG86100 using xda premium
Check your init.d folder for a file called 98dualcore, delete that. If you don't see anything, then your going to have to flash an unmodified stock kernel. Freeza has an explanation for that in his thread.
ceyo14 said:
How do I remove dual core scripts... Or whatever is enabling them... I tried a couple kernels and still activated. Running eternity 1.4.2
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
DDiaz007 said:
Check your init.d folder for a file called 98dualcore, delete that. If you don't see anything, then your going to have to flash an unmodified stock kernel. Freeza has an explanation for that in his thread.
Click to expand...
Click to collapse
Example: Ziggy's dual core kernel flash .zip file modifies thre system binaries in addition to the init.d script it adds. Kernel .zip files, imo, should not modify system binaries. System binaries should only be modified by ROMs. Of course, there is no official standard and this is just my opinion based on experience.
One main reason would be, majority of other kernel .zip files do not modify those same system binaries. So the only way to "undo" the files changed by Ziggy's kernel flash, would be to reload a ROM which replaces the three system binaries Ziggy changes.
Essentially, if you want to undo the changes made by Ziggy's kernel flash, you'll need to replace all files modified by his kernel flash. Flashing another kernel will not replace those files, but loading another ROM *should*.
Hope that helps!
Related
I was playing around with some scripts from Caulkin on some other versions of Froyo to try and improve performance. I have read up on the init.rc script and use of the init.d folder. I have set all this up and have edited the init.rc script to run the init.d scripts, but it gets overridden by the base init.rc on reboot. I had read somewhere that you cannot directly edit the init.rc and that it will be overridden on boot from the boot.img. Can someone confirm that? I thought most roms now have the ability to use init.d out of the box, but it doesn't look like it on Brilliant Corners. Can someone confirm that? Do you know of any Froyo ROMS, other than Caulkins, that has init.d capability? Thanks
markmac said:
I have set all this up and have edited the init.rc script to run the init.d scripts, but it gets overridden by the base init.rc on reboot.
Click to expand...
Click to collapse
Are you using the run-parts program?
I had read somewhere that you cannot directly edit the init.rc and that it will be overridden on boot from the boot.img. Can someone confirm that?
Click to expand...
Click to collapse
That's correct.
Thanks for the response. I was editing the init.rc directly which obviously won't work. So i need to look into building my own boot.img or another option. I was using run-parts setup as a service. I would have thought most kernels/ROMs would support this now, but it does not appear that way.
markmac said:
So i need to look into building my own boot.img or another option.
Click to expand...
Click to collapse
You don't need to build your own new image; you can just modify the existing one by flashing. Take a look at the attachements in these 2 posts where I've done just that. Just make sure the script is idempotent if other people will use it.
Post 1
Post 2
Thanks will definitely check this out.
Looked at this. So to update the init.rc file I would have to edit and package into a boot.img file, then flash the img file with adb or nvflash correct?
markmac said:
So to update the init.rc file I would have to edit and package into a boot.img file, then flash the img file with adb or nvflash correct?
Click to expand...
Click to collapse
No. That's too much work for the user. My technique is meant to be like flashing a new kernel. No external utilities are needed. Just CWM (or, possibly, even standard recovery).
Hi,
I'm kinda new to flashing and upgrading my phone.
Therefore I got some questions:
Currently running on my Neo: AOSP 4.0.3 ICS BETA with kernel provided there
Baseband says: 56 as last two digits
I would like to upgrade my baseband to 62. (latest)?
As far as I understood I will have to flash 4.0.2.A.0.62 Baseband using flashtool.
Do I have to flash the kernel again after upgrading baseband or should I flash the 4.0.2.A.0.62 Kernel first and change it afterwards?
fastboot flash boot boot.img
Click to expand...
Click to collapse
Will changing the baseband or kernel delete anything?
When would be the right time to apply the RAISE your NEO userdata space patch? Before or after baseband, kernel flash?
Sometimes they say that a reboot is required after flashing a new ROM before flashing an update.zip in CWM. Do I have to reboot at other times?
Is there a tool or a possibility I missed which can flash anything like baseband, kernel, ROM and updates to it in one step?
If I want to edit a ROM like directly changing bootanimation and ringtones.
How should the zip file be packed? No compression, etc?
Is it a good idea to include updates which I would have flashed in CWM directly into the ROMs zip file?
Do I have to flash the kernel again after upgrading baseband or should I flash the 4.0.2.A.0.62 Kernel first and change it afterwards?
Click to expand...
Click to collapse
Kernel is not related to baseband. Simply flash baseband, no need to flash kernel after or before.
Will changing the baseband or kernel delete anything?
Click to expand...
Click to collapse
Flashing baseband won't delete anything, but flashing kernel might. I see that kernel in that thread have CWM inside, so if you flash stock kernel you will lose that.
When would be the right time to apply the RAISE your NEO userdata space patch? Before or after baseband, kernel flash?
Click to expand...
Click to collapse
Whenever you want. It's not related to kernel or baseband.
Sometimes they say that a reboot is required after flashing a new ROM before flashing an update.zip in CWM. Do I have to reboot at other times?
Click to expand...
Click to collapse
Yes, they say that so that ROM "settles down in it's place" then you can install fixes and stuff.
What other times?
Is there a tool or a possibility I missed which can flash anything like baseband, kernel, ROM and updates to it in one step?
Click to expand...
Click to collapse
There is flashtool, but only for stock rom's. Custom roms are installed as a .zip file via CWM recovery.
If I want to edit a ROM like directly changing bootanimation and ringtones.
Click to expand...
Click to collapse
You can do that with root explorer app(or any app which can access to system), create that bootanimation.zip on pc and upload it to sdcard, then move it to where it needs to be. For bootanimation.zip, yes, it's with no compression. How it's created, check other bootanimation.zip's over the net.
For other zip's which are flashed trough CWM, it's a bit more complicated to explain how to create them.
Is it a good idea to include updates which I would have flashed in CWM directly into the ROMs zip file?
Click to expand...
Click to collapse
Well depends. Most likely yes, but I would still ask creator/porter of each rom if that is advisable
Madfysh said:
seXneo said:
If I want to edit a ROM like directly changing bootanimation and ringtones.
How should the zip file be packed? No compression, etc?
Click to expand...
Click to collapse
You can do that with root explorer app(or any app which can access to system), create that bootanimation.zip on pc and upload it to sdcard, then move it to where it needs to be. For bootanimation.zip, yes, it's with no compression. How it's created, check other bootanimation.zip's over the net.
For other zip's which are flashed trough CWM, it's a bit more complicated to explain how to create them.
Click to expand...
Click to collapse
Thank you very much.
But in this point there was a misunderstanding.
I just wanted to know how the update.zip or rom.zip has to be packed and if it's save to replace bootanimation.zip inside rom.zip. Are there any checksums for apk or other files inside an CWM update.zip I need to change?
Most of the ICS based ROMs use MT15i_Neo_ICS_Kernel_V1.img. Where does it come from and where is it's original thread?
if it's save to replace bootanimation.zip inside rom.zip. Are there any checksums for apk or other files inside an CWM update.zip I need to change?
its safe to change bootanimations.zip and any other apk or file in side the provided update.zip file
but if u extract it n do changes then u will lose the signature of the developer n wont b able to install the update.zip properly
chintu1234 said:
its safe to change bootanimations.zip and any other apk or file in side the provided update.zip file
but if u extract it n do changes then u will lose the signature of the developer n wont b able to install the update.zip properly
Click to expand...
Click to collapse
Yes of course. If original zip file flashed and runs nice it will be my fault if it won't after my edits.
So no checksums in the update.zip directly. Thanks.
Signing of an altered apk file is required. Got it.
And I figured that there is no signing of the bootanimation possible.
Will post my question regarding the kernel in an extra thread.
hey guys so i installed cm7
and then used DJNoXD.
i was wondering how can i go back to the original kernel?
how can i extract the kernel from the rom?
or do you guys have any other suggestions for which kernel should be used?
please help
Ramis93 said:
hey guys so i installed cm7
and then used DJNoXD.
i was wondering how can i go back to the original kernel?
how can i extract the kernel from the rom?
or do you guys have any other suggestions for which kernel should be used?
please help
Click to expand...
Click to collapse
You can use Roq's latest Kernel from Here.
Ramis93 said:
hey guys so i installed cm7
and then used DJNoXD.
i was wondering how can i go back to the original kernel?
how can i extract the kernel from the rom?
or do you guys have any other suggestions for which kernel should be used?
please help
Click to expand...
Click to collapse
Just flash cm7 again (without wiping anything).
After that you will have the original kernel again.
DJNoXD said:
Just flash cm7 again (without wiping anything).
After that you will have the original kernel again.
Click to expand...
Click to collapse
but that would reset all all my settings.
isnt there a way to extract the kernel?
No, if you flash a new version (or the same version) of cm you won't loose all your settings. Important is that you only wipe dalivik cache and cache, nothing else.
Than the only thing you loose are changes you have done to "system"-folder. But less people do this.
The normal configurations like wlan, ... are not touched / lost.
If you are scared to loose your rom data, create a backup (clockwork recovery) before.
Only extracting is not easily possible.
If you got the kernel "zImage" file and the "wireless.ko" module, you have to create the signed zip file before you can flash it.
source cyanogenmod
Code:
Option 1: Koush's AnyKernel zip file Koush's AnyKernel repacks the kernel in the package with the ramdisk currently flashed to the device. Therefore, we need to change the boot.img --base address so the boot.img will boot on the 32A device. This change needs to be made in mkbootimg.sh in the package. Koush has a 32A branch of AnyKernel here: http://github.com/koush/AnyKernel Clone the AnyKernel repo
git clone git://github.com/koush/AnyKernel.git -b 32A
This will make a folder called AnyKernel in your working directory. Keep this and just copy it to your packaging directory.
Copy the AnyKernel folder to a working directory. In the AnyKernel folder you have three folders:
kernel
Put the zImage in this folder. Leave it named zImage
META-INF
system
Put the wlan.ko in system/lib/modules. Replace the placeholder wlan.ko file.
Now you can zip the 3 folders together and sign them
zip -r port.zip *
java -classpath <path to SDK/tools>testsign.jar testsign port.zip signed-port.zip
for example:
java -jar ../SignApp/signapk.jar ../SignApp/testkey.x509.pem ../SignApp/testkey.pk8 port.zip update_signed.zip
This creates a signed zip file called port.zip and can be flashed. :) You are done.
DJNoXD said:
No, if you flash a new version (or the same version) of cm you won't loose all your settings. Important is that you only wipe dalivik cache and cache, nothing else.
Than the only thing you loose are changes you have done to "system"-folder. But less people do this.
The normal configurations like wlan, ... are not touched / lost.
If you are scared to loose your rom data, create a backup (clockwork recovery) before.
Only extracting is not easily possible.
If you got the kernel "zImage" file and the "wireless.ko" module, you have to create the signed zip file before you can flash it.
Click to expand...
Click to collapse
oh ok then, thanks
p.s would you recommend Roq's kernel or the default cm7 one?
(i won't be gaming on my phone. just want performance and battery life)
I haven't tried roqs latest kernel.
Just try it. Only you will know what you are searching for.
All custom kernels are good. But not every kernel is good for everyone.
Edit: What kind of performance are you searching for?
ok then,
thanks for the help
Here you can get the stock kernel for CM7
http://forum.xda-developers.com/showthread.php?t=1564203
Sent from my LG-P500 using XDA
yuripg1 said:
Here you can get the stock kernel for CM7
http://forum.xda-developers.com/showthread.php?t=1564203
Sent from my LG-P500 using XDA
Click to expand...
Click to collapse
awesome thanks
yuripg1 said:
Here you can get the stock kernel for CM7
http://forum.xda-developers.com/showthread.php?t=1564203
Sent from my LG-P500 using XDA
Click to expand...
Click to collapse
Haven't seen that you have updated your kernel to latest sources.
> you can use kitchen to extract zimage.. and copy modules from system>lib>modules folder.. I dont know how to repack it as a zip? may be by the link given above for stock kernel with outdated source.. just replace zimage and modules content on the zip.
I get the zImage using a flashable ZIP that I made.
http://db.tt/0WKE2o8w
What I did was simply modify a kernel installer (by Koush) to make it extract the boot.img of the ROM currently installed to the SD card.
After flashing it, I copy and rename the zImage in /sdcard, copy the modules in /system/lib/modules and make the flashable ZIP as any other kernel.
Sent from my LG-P500 using XDA
I'm running the latest stock rooted rom with init.d support. If I modify an init.d script or add an additional script, as soon as I reboot the my changes are gone. What is causing this? Is /system/etc/init.d part of the boot.img?
fldash said:
I'm running the latest stock rooted rom with init.d support. If I modify an init.d script or add an additional script, as soon as I reboot the my changes are gone. What is causing this? Is /system/etc/init.d part of the boot.img?
Click to expand...
Click to collapse
I take you are still S-ON and that is the reason. the system does not allows permenent write. There are ROMS that fixed this issue for people with S-ON. Check in the development section and check out the ROMS that support init.d with permanent write to /system.
Its specifaclly the kernel. Use the elemental kernel to fix that, or flash meanbean
Sent from my EVO using xda app-developers app
Thanks guys.
Hi i just created this zip to install init.d on our phone (G530H)
For those who dont know what is the "init.d" its just a folder on the system where you can put some scripts and will run everytime you start the phone, its usefull to clean some cache, get better performance, zipalign etc. theres a lot of scripts on the web but i dont have time to test all of them so, heres a zip to install this folder, it includes the zipalign binary, tested and fully working, you can also google some scripts, test them and share the results with us
Flash it on cwm or twrp and enjoy
To run init.d scripts you need a custom kernel that support it or enable it on stock kernel. Without these changes , you will just have a new folder in your system...
Humberto.Ortega said:
To run init.d scripts you need a custom kernel that support it or enable it on stock kernel. Without these changes , you will just have a new folder in your system...
Click to expand...
Click to collapse
then... How do this worked?
Dam7lc said:
then... How do this worked?
Click to expand...
Click to collapse
I think this flashable zip has already enabled init.d support in stock kernel. I searched how to enable this support and I found we have to install the file "install-recovery.sh" in system/etc. I download your zip file and I saw that this file is present...
So this zip file doesn´t contains only script, but enable the init.d support for the stock kernel :highfive:
We can check this in /data/local/tmp...there should be a txt file there named "init.d_log_test.txt"
Sorry my mistake
I'll flash it and report later....
Thanks man!!
PLEASE MAKE ONE FOR G530P to enable gsm
To my speculations it seems the g530p is no different from the g530 variants p/h/t/t1 and the others as they all have the same qualcomm baseband but as the cdma feature is enable and the others are lock can you gather a team and make this possible to create a baseband or modem that edit these fields and enable gsm/umts or any other bands to work globally as well as the init.rd
thanks