nikkotsoi, on 20 April 2012 - 11:37 AM, said:
yes, to make it clear
new zimage + modules installed = not boot
new zimage + old modules =boot (no vibration/phone signal/camera)
old zimage + new modules installed =boot (no vibration/phone signal/camera)
tapptapp, on 20 April 2012 - 08:42 PM, said:
I have installed android in internal storage.
Here are my results with the new zImage:
old zImage + new modules installed = boot (no phone signal/no wlan)
new zImage + new modules installed = not boot
new zImage + old modules = not boot
erikcas, on 20 April 2012 - 08:49 PM, said:
Kernel a plus modules b and vice versa will never work.
Sorry for the late reply. I think I know what's the cause. It's the param.ko - the samsung legacy code that caused all those troubles. I stopped loading it in my first few days of hacking. The code doesn't do much but is ugly as hell.
To fix, comment out the insmod param.ko line in init.rc, or simply remove the ko file. It shouldn't have been built in the first place, but I just forgot to kill it in the config. Your line should look like:
And it should work no matter where you installed the system, sdcard or otherwise, so long as the modules reside in the /modules directory of the root filesystem (or more precisely, where your startup scripts can find them.)
@erikcas: I read somewhere you are running B7610, right? I only own an I8000, and likely you won't be able to use the binaries directly. But I believe you can roll your own and it should work since I haven't touched any modules32 code except for some obvious stuff.