This is a dev thread, and only for developers, please avoid of posting UNUSEFUL things. Thanks
Guys, there you go, this is zImage compiled with x10_x10mini_X10minipro_x8_eclair_2.1.A.0.435.tar.gz sources, built with semc_mimmi_defconfig. I would recommend to devs to go here, seems like it's more active that old threads.
Added splboot.ko compiled with X10 mini pro kernel sources (same config as zImage) , address 0x00200000
Also included a nice sh for insmodding, and dmesg modules.
SPLBOOT MODDED SOURCES ON MY APPORTS INDEX!
Original sources can be found on FreeXperia git, and ARMv6 by nAa at X8 bootloader bypass thread
Thanks to nobodyAtall for porting splboot to ARMv6. Thanks to aZuZu and doixanh for helping and side tips.
D4rKn3sSyS said:
This is a dev thread, and only for developers, please avoid of posting UNUSEFUL things. Thanks
Guys, there you go, this is zImage compiled with x10_x10mini_X10minipro_x8_eclair_2.1.A.0.435.tar.g z sources, built with semc_mimmi_defconfig. I would recommend to devs to go here, seems like it's more active that old threads.
Thanks to aZuZu and doixanh for helping me compiling.
Click to expand...
Click to collapse
it seems to be great news! but what is zImage for? how can it improve the Custom roms?
PTGamer said:
it seems to be great news! but what is zImage for? how can it improve the Custom roms?
Click to expand...
Click to collapse
Just read the wikipedia article on zImage. Here.
wikipedia said:
The filename of the bootable image is not important, but by convention it is called vmlinuz or zImage.
Click to expand...
Click to collapse
can you make bzImage? 2.3 Mb is to big for download... Thanks! Nice work!
Any progress on bootloader bypass?
PTGamer said:
it seems to be great news! but what is zImage for? how can it improve the Custom roms?
Click to expand...
Click to collapse
This is a dev thread, why it's supposed that this is related with custom roms?. zImage it's kernel executable (compressed btw).
Uploaded splboot.ko module, seems working well, if you are gonna try, be sure that you chmod to 777.
For development & testing you can use chmod 777 but never forget to set permissions correctly before releasing something!
Snoopo said:
For development & testing you can use chmod 777 but never forget to set permissions correctly before releasing something!
Click to expand...
Click to collapse
I'm sorry, don't get your point. If i get you ok then you mean that I need to chmod +x or 777 on linux, before publishing some?... then why people can use on windows, and then release?? (Yes windows simply damages permissions)
You just need to chmod on phone (or use unyaffs.. chmod sounds easier)
D4rKn3sSyS said:
I'm sorry, don't get your point. If i get you ok then you mean that I need to chmod +x or 777 on linux, before publishing some?... then why people can use on windows, and then release?? (Yes windows simply damages permissions)
You just need to chmod on phone (or use unyaffs.. chmod sounds easier)
Click to expand...
Click to collapse
i think he mean you can use chmod 777 while For development & testing
but set correct permissions before releasing
mean dont keep 777 but correct it if 777 not needed
(+x or what ever i dont know more permissions type lol )
heh yeah... Maybe it's my linux administration thinking:
Permission 777 is bad ^^
You should better find out which user or group shall have execute ,rewad or write-rights and then set the correct permission...
for example:
chown 0:2000 /foo
chmod 750 /foo
you see? Okay on a mobile it's really not that important but think of that there is someone who writes a bad app that exploits just a permission of CM7 or CM6 that is used in every phone... and woops ^^ or whatever ^^
D4rKn3sSyS said:
Guys, there you go, this is zImage compiled with x10_x10mini_X10minipro_x8_eclair_2.1.A.0.435.tar.gz sources, built with semc_mimmi_defconfig.
Click to expand...
Click to collapse
Hi D4rKn3sSyS (toughest nickname to write :-D),
Where do you get the sources? From SE developers' site?
What's that kernel version? If it's to 2.6.29, it should be patched to reach 2.6.32, am i wrong?
What's splboot module for? Does anybody try to kexec-tool way?
Cheers,
ff0000.it
... I almost forget: this is the best thread on the forum, thanks D4! ;-D
ff0000.it said:
Hi D4rKn3sSyS (toughest nickname to write :-D),
Where do you get the sources? From SE developers' site?
Click to expand...
Click to collapse
Yes... i think.
ff0000.it said:
What's that kernel version? If it's to 2.6.29, it should be patched to reach 2.6.32, am i wrong?
Click to expand...
Click to collapse
no... more source required.
ff0000.it said:
What's splboot module for? Does anybody try to kexec-tool way?
Click to expand...
Click to collapse
bootloader bypass.
Or at least, i think i'm right.
OmegaRED^ said:
Yes... i think.
no... more source required.
bootloader bypass.
Or at least, i think i'm right.
Click to expand...
Click to collapse
Right, s.e site, right, and right
OmegaRED^ said:
no... more source required.
Click to expand...
Click to collapse
Not such a big answer , i downloaded the sources from SE and it's a 2.6.29 kernel release as the one actually found in SE roms... now suppose i'd like to build a custom Android ROM based on Gingerbread branch that comes with kernel 2.6.35, it should be a good thing patch the kernel in order to take the SE one up to 2.6.35, isn't it?
To do that i think we've to take the Android kernel source git clone, extract all the patches from 2.6.29 to 2.6.35 (dealing with a single patch is harder than a small set of patches) and apply one by one crossing our fingers and hoping SE doesn't make so much modifications to the base parts of the kernel.
If we succeed we could maintain a custom kernel through patches.
OmegaRED^ said:
bootloader bypass.
Click to expand...
Click to collapse
If the meaning of bootloader bypassing is only to load a custom kernel, what if kexec-tool works? Isn't it a simple way to deal with a custom kernel? I never use it but it sounds easier...
ff0000.it said:
Not such a big answer , i downloaded the sources from SE and it's a 2.6.29 kernel release as the one actually found in SE roms... now suppose i'd like to build a custom Android ROM based on Gingerbread branch that comes with kernel 2.6.35, it should be a good thing patch the kernel in order to take the SE one up to 2.6.35, isn't it?
To do that i think we've to take the Android kernel source git clone, extract all the patches from 2.6.29 to 2.6.35 (dealing with a single patch is harder than a small set of patches) and apply one by one crossing our fingers and hoping SE doesn't make so much modifications to the base parts of the kernel.
If we succeed we could maintain a custom kernel through patches.
If the meaning of bootloader bypassing is only to load a custom kernel, what if kexec-tool works? Isn't it a simple way to deal with a custom kernel? I never use it but it sounds easier...
Click to expand...
Click to collapse
It's simple enough to flash using Xrecovery or CMW.
The x10 forums made almost everything flash-able via Xrecovery
It's hard to isolate what to patch... consider that the big x10 threads have been messing with modified kernels for quite some time now..
Ip-tables, (CPU undervolt, overvolt and overclock) and many other mods directly implemented into the kernels.
And even so they are still stuck on the same kernel version.
SE has not even upgraded the kernel version with the 2.3.3 update.
So it may be possible but it makes alot of work for new drivers...ect..
It's best to try and optimize the current version and already working source instead of creating a whole new ball game.
OmegaRED^ said:
It's simple enough to flash using Xrecovery or CMW.
The x10 forums made almost everything flashable via Xrecovery
Click to expand...
Click to collapse
I think you don't get my point... i was saying (from my point of view) that a kernel upgrading is mandatory (or it should be)...
It's the same if i have a Linux 2.4.x kernel with a GNU distribution that relies on mechanism such as sysfs that isn't supported in 2.4.x kernels (>= 2.6.x); so to build a custom Gingerbread ROM it's a good choice having a related kernel (from wikipedia it's 2.6.35).
And what's within Xrecovery and CWM? Flashing differs from building...
Saying that i don't want bluetooth or GPS or wifi support in my ROM, disable it from kernel and ROM building... that's the benefit of having custom kernels and ROMS.
Still i don't understand why you answer me with Xrecovery and CWM
Please don't miss under stand.
All i am saying is that without source it becomes hard.
SE did not upgrade the kernel to 35 for the big x10 or the x8 so there is very little to work with.
It would be awesome to get the kernel to that level.
But it's easier to rather tweak the kernel we currently have.
ff0000.it said:
If the meaning of bootloader bypassing is only to load a custom kernel, what if kexec-tool works? Isn't it a simple way to deal with a custom kernel? I never use it but it sounds easier...
Click to expand...
Click to collapse
^^^
This is why i commented on CWM and Xrecovery.
Afair there are even custom kernels but they are not really stable and discontinued.
s0ftcorn said:
Afair there are even custom kernels but they are not really stable and discontinued.
Click to expand...
Click to collapse
What are you talking about?, we haven't already bypassed bootloader.
s0ftcorn said:
Afair there are even custom kernels but they are not really stable and discontinued.
Click to expand...
Click to collapse
The point is not the stability or the instability of a custom kernel, it's to have the chance of building a custom one...
It's my right to have a unstable custom kernel builded by me installed on my phone, isn't it? :-D
@D4: i'm going to learn more about "git" and then i'll try (in the spare time) to patch SE kernel up to 2.6.35 (with all git tags/branches) and the i'll upload it to github... no promise at all, by i'll try ;-D
D4rKn3sSyS said:
What are you talking about?, we haven't already bypassed bootloader.
Click to expand...
Click to collapse
Yeah my bad. Have read the custom kernel stuff while i was completely new to smartphones. The X10 has custom kernels, but theire development is afair discontinued.
Sorry for the irritation.
how can i change the name of a kernel before insalling it to my device.for example rename a kernel so at the about phone it says 123 kernel?
only if you can make your own kernel you can rename it
Yeah, you have to compile your own kernel.
You can set the "local version" setting in the kernel config then.
how can i compile my own kernel?
pan24 said:
how can i compile my own kernel?
Click to expand...
Click to collapse
Download the sources, download the toolchain and off you go.
You need at least some programming knownledge for it, it's also of advantage to know how the Linux kernel building process works.
I am trying to port cwm on my SGP 4.0 (korean version/YP-GB1)
If i flash the kernel which cwm ported by me
cwm works very well(So i rooted my device with cwm), but If i boot my SGP normaly(?)
Hardware buttons(home, back, menu, volume+- like these)and screen touch do not work;;
What should i do?
Sounds like you used the wrong defconfig when building the kernel.
First try to just get a kernel working with the original initramfs - THEN port CWM.
Entropy512 said:
Sounds like you used the wrong defconfig when building the kernel.
First try to just get a kernel working with the original initramfs - THEN port CWM.
Click to expand...
Click to collapse
Thank you for reply,
But i modfied only initramfs and repacked it to original zImage..
Should i try compile kernel source with initramfs?
OR is any problen in initramfs?
Initramfs will create some devices and set their permissions - so an international/US initramfs could do weird stuff on a Korean unit.
Entropy512 said:
Initramfs will create some devices and set their permissions - so an international/US initramfs could do weird stuff on a Korean unit.
Click to expand...
Click to collapse
That means..
Should i get CWM source my self
and modifiey?
Hi to all!
So kernel bypass is "obsolete" idea for normal users but i have spend past several day trying connect uart port over Nokia CA-42 data cable without any success. I suspect that MSM Secure(tm) Debug Qfuse is blown or something else so i can't work on new kernels altho is have done ground work
>> GROUND WORK = inserted x10 mini drivers and Makefile / Kconfig / Code Fixing entries <<
In these kernel builds:
2.6.32 ( CAF) (SEMC)
2.6.35 (CAF) (SEMC)
3.0.8 ( CAF )
3.4 ( CAF )
And i can make all zImages but they do not boot...
So i decided to compile my sboot tool ( based on kexec )
I didn't have luck so far kernel exec from kernel i suspect that it is host kernel based error so i would need help with testing on diff kernels / roms. Thanks!
Please post links to files created only with tool in folder called >> make_report << and do not post garbage. Thanks!
Appendix A:
In folder u will find >> sboot_install << that script will "install" sboot tool on you mobile in folder /system/kernel
Appendix B:
Existing kernel must be compiled with
CONFIG_KEXEC=y
CONFIG_ATAGS_PROC=y
Appendix C:
Yes i will make kexec module for folks that doesn't have required from Appendix B
Appendix D:
Archive is now reuploaded it has now both armv6 and armv7 kexec module for existing kernels w/o stuff in Appendix B
sboot_install is now needs argument for install
msm7k ( for armv6 version of kexec emulation module) "
qsd8k ( for armv7 version of kexec emulation module) "
Download aZuZu SBoot v1.02.3
I know this is a dev thread, but I'm just curious, will this work on other MSM7227 devices like the X8 for example which shares the same architecture as the X10 Mini or Mini Pro. Correct me if I'm wrong but does this mean that we may see CWM flashable kernels in the near future.
souljaboy11792 said:
I know this is a dev thread, but I'm just curious, will this work on other MSM7227 devices like the X8 for example which shares the same architecture as the X10 Mini or Mini Pro. Correct me if I'm wrong but does this mean that we may see CWM flashable kernels in the near future.
Click to expand...
Click to collapse
In general sboot tool is uni tool for all armv6 / armv7, only condition is to include CONFIG_KEXEC=y and CONFIG_ATAGS_PROC=y in kernel u will use to load new kernel or kexec module to emulate same functions.
This is not for flashing kernels but for kernel bypass, so loading kernel on top running one.
So lemme get this straight. What will happen is we will already have a kernel. Then we'll flash another kernel (through CWM?) which has the kexec module. The second kernel will basically be booted up although we still have another kernel flashed. So it's like a temporary kernel, right?
souljaboy11792 said:
So lemme get this straight. What will happen is we will already have a kernel. Then we'll flash another kernel (through CWM?) which has the kexec module. The second kernel will basically be booted up although we still have another kernel flashed. So it's like a temporary kernel, right?
Click to expand...
Click to collapse
Yes temporary kernel. Like I said / explained in first post. It is for dev's like me who can use hw debug to port newer kernel cause we need /proc/last_kmsg to see where was halt. Project idea is to provide that on sw debug base.
Honestly I didn't understand anything after temporary kernel, but good luck with your project and I sure do hope you succeed.
For my understyding aZuZu is developing SBoot so devs would be able to temporarly boot a kernel in purpose of easy developing and debugging a newest version of kernel (e.g. 3.x)... Thus devs are not obligated to flash the new kernel with flashboot and then back to working one and then back to debbugging....
Am i right aZuZu?
ribben said:
For my understyding aZuZu is developing SBoot so devs would be able to temporarly boot a kernel in purpose of easy developing and debugging a newest version of kernel (e.g. 3.x)... Thus devs are not obligated to flash the new kernel with flashboot and then back to working one and then back to debbugging....
Am i right aZuZu?
Click to expand...
Click to collapse
Correct! Ping! Ping! Ping!
nice work sir....i am not a developer but still understand its potential...i smell cwm flashable kernels for x8...x10 mini and x8 quite similar right?...will help people with broken ports...:good:
aZuZu said:
Correct! Ping! Ping! Ping!
Click to expand...
Click to collapse
Hello
I am an X8 user and seriously want to unlock my boot loader but the manufacturing date was 11W43 so i couldn't do it. Then i came across your thread, found a hope to run custom kernels on my X8. Can you please say me when it might be completed and available ??
Thank You
Oh my god! This would be perfect if it does work! Cool!
My English is not good。I want know which kernel can use Sweep2Wake by crDroid 4.31？ This rom is very good。thank you very much
all kernels are capable of using sweep2wake but i think torrented has sweep2wake built into his kernel but i havnt looked at the kernels lately
t1gartist said:
all kernels are capable of using sweep2wake but i think torrented has sweep2wake built into his kernel but i havnt looked at the kernels lately
Click to expand...
Click to collapse
Thank you, although I still do not understand, but still thank you very much
ok kernels are modified and compiled to run on this device and all devices for that matter in order to have sweep2wake you must write it into the kernel and compile the kernel with sweep2wake added if that better explains so like this
1 download kernel source
2. add sweep2wake to the source code
3. compile kernel
4. run kernel for errors
5 fix errors if any and re compile kernel
6. add the kernel for the world to use also (which is a noble thing to do btw)
t1gartist said:
ok kernels are modified and compiled to run on this device and all devices for that matter in order to have sweep2wake you must write it into the kernel and compile the kernel with sweep2wake added if that better explains so like this
1 download kernel source
2. add sweep2wake to the source code
3. compile kernel
4. run kernel for errors
5 fix errors if any and re compile kernel
6. add the kernel for the world to use also (which is a noble thing to do btw)
Click to expand...
Click to collapse
thank you very much.
I heard a whoosh.
lol orange