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.
Related
Hi all,
say that I'd like to try a CM7 custom compilation (e.g., removes half of packages, ...) for the sake of learning, what steps do you suggest to get into?
Compiling a full debuggable ROM and test it in the Android emulator?
Could I test It along with SE kernel (e.g., with the latest)?
In the emulator should i to install the SE related packages in order to set up the Xperia HW emulation?
Cheers!
There's a package of scripts named kitchen, made of a member here that let you customize a rom. There is even a root method that we were talking about the other day.
https://github.com/dsixda/Android-Kitchen
Hi kissmyarch,
i meant bulid It from the sources, not through the kitchen way ;-)
Oook sorry then.
LoL take a rom add ur theme, choose ur fav apps! Choose ur modules! And ur done! Custom rom is ready!
You know, I don't think people (including me) want to make a "repack" of an existing ROM, but build their own from sources instead, galvic
LoL nevermind then! This is what happening lately on mini pro forums, I just revealed how its being done!
Ravencz said:
You know, I don't think people (including me) want to make a "repack" of an existing ROM, but build their own from sources instead, galvic
Click to expand...
Click to collapse
I agree with Ravencz, building from sources is more funny than cooking... the fact is that you find a tutorial on cooking in the forum (and it's simplistic as hell) and no an hint on how to port your own CyanogenMod on your mini pro... what a pity...
Hoping someone on the devs' side will read this post ;-D... Cheers!
First of all cyanogenmod is already a cooked rom! If u want to port cyanogenmod u've to open it and then make it compatible for mini pro and repack it!
But you dont want that so rename the thread how to create custom gingerbread rom!
then use Sources from AOSP rom! Then repack 'em! Thats how its done, kitchen just provides an enviorenment for this!
galvic said:
First of all cyanogenmod is already a cooked rom! If u want to port cyanogenmod u've to open it and then make it compatible for mini pro and repack it!
But you dont want that so rename the thread how to create custom gingerbread rom!
then use Sources from AOSP rom! Then repack 'em! Thats how its done, kitchen just provides an enviorenment for this!
Click to expand...
Click to collapse
I'm sorry, but that's not completely true. CyanogenMod has it's sources as well. Sure, you can download a clean build from their website, but you can also build CM on your own.
@galvic: CM doesn't seem a cooked ROM to me, since they provide the repository from which you could clone the sources. CM seems more a fork (with enrichments/improvements) of AOSP and cooking a CM isn't the same of building its source.
So the thread is correct, because if i fetch and edit the Gingerbread branch of CM source, actually i've built a custom CM7.
Instead of linking those megabytes of ROMs, shouldn't be better working on CM's branch and attach the related patches that brought to a custom CM ROMs, as patches for kernel modules and so on? Benefits of patches are small downloads size, learning what people do in making your beloved ROM, ... On the other side you've to set up a developer's environment, that is a bit expensive (Gingerbread sources are around 7 Gigabytes, if i'm not wrong).
I don't know if Gingerbread is the best choice with the unchangeable kernel that SE stuck on our smartphone, but say Gingerbread or Froyo or whatever the fix you've to make on a CM are (logically) the same until someone will make an hackish strike and take down that damned bootloader.
See you!
Ravencz said:
I'm sorry, but that's not completely true. CyanogenMod has it's sources as well. Sure, you can download a clean build from their website, but you can also build CM on your own.
Click to expand...
Click to collapse
Sorry but CM is also bult on sources of AOSP
galvic said:
Sorry but CM is also bult on sources of AOSP
Click to expand...
Click to collapse
Of course it is, but it's modified
Ravencz said:
Of course it is, but it's modified
Click to expand...
Click to collapse
So we should also modify them exclusively for mini pro, then it'll be called a perfect ROM?
thats what free-xperia project did, use miniCM resources!
galvic said:
So we should also modify them exclusively for mini pro, then it'll be called a perfect ROM?
Click to expand...
Click to collapse
Nope, compiling gives you control over things such as source code, compiling options/flags for optimization (say that our mini pros have ARMv6 processor, why having a ROM built for generic ARM architecture? It doesn't make any sense... that's the source-oriented GNU/Linux distro way as Gentoo: compiling kernel and all application for your machine in order to have best performances and responses), possibility of adding removing code (e.g. libraries, system applications) and so on.
Cooking let's you modify something pre-made and doesn't give you *full* control on it ;-)
If we've to take over the world, we've to do it in the proper way! :-D
Cheers
So, preview of SEtweak (pre1) is out!
It's quite incomplete, without Synaptics DT, not netfilter and OC. I also forgot to enable NTFS, sorry
Just a proof of concept for those unwilling to unlock bootloader.
X8gesture will insmod fine.
Cypress users: remove DT module because this kernel already includes it!
Includes CIFS and tun - who need it, will know, who doesn't need it/know, don't bother
Download: -not working-
FTF bundle. Place to flashtool\firmwares, in GUI select X8 SEtweak-pre1 FW and flash it.
FreeXperia logo instead of SE standard, and [email protected] instead of [email protected] are easiest way to see that you have custom kernel.
Forgot to note: this kernel has gingerbread ramdisk, meaning it's for GB ROMs! Maybe works on stock, but may won't be stable!
Will include:
* Cypress dualtouch
* Syaptics fake dual touch
* custom netfilter tables
* overclock
Standard SEtweak features:
* NTFS
* ext4
* swap
* USB OTG experimental
* tun/tap/CIFS
Best regards
Wow
Now You Post Your Kernel
Will Wifi Work on your Kernel
My wifi Don't work on my kernel
Blagus said:
I flashed my kernel and it works. However, [email protected] machine name persists.
Anyways, take a look at this:
Code:
<5>[ 0.000000] Linux version 2.6.29 ([email protected]) (gcc version 4.5.2 (Sourcery G++ Lite 2011.03-42) ) #1 PREEMPT Thu Aug 18 16:30:18 CEST 2011
I need to make some more tweaks, pack correct ramdisk and remove [email protected] machine/user name.
Will include:
* Cypress dualtouch
* Syaptics fake dual touch
* custom netfilter tables
Best regards
Click to expand...
Click to collapse
So, does this work on Gingerbread? Can't wait to test it out!
@Superuser.Angga
You have a kernel?
And I think the driver Blagus was referring to is sdio.ko (commonly found in /system/lib/modules)
you need to replace wifi module.
Superuser.Angga said:
Wow
Now You Post Your Kernel
Will Wifi Work on your Kernel
My wifi Don't work on my kernel
Click to expand...
Click to collapse
Sent from my R800i
Blagus said:
you need to replace wifi module.
Sent from my R800i
Click to expand...
Click to collapse
Thank's A lot
my wifi work
@SpyderX
Take a look @ This
This is my Custom Kernel
Superuser.Angga said:
Thank's A lot
my wifi work
Click to expand...
Click to collapse
Wow...replaced in 5 minutes , quite fast.
@Blagus
Is it ever possible for a X8 kernel in the future to automatically convert /system, /data and /cache into ext4? Because I remember Galaxy Ace forums has a kernel that does this. Just a question .
XDA users stats and capabilities:
5% to develop
5% to understand development, and not to ask stupid questions
90% users are capable of spamming the dev thread with 3 pages of useless junk in 5 minutes
Sent from my R800i
Blagus said:
XDA users stats and capabilities:
5% to develop
5% to understand development, and not to ask stupid questions
90% users are capable of spamming the dev thread with 3 pages of useless junk in 5 minutes
Sent from my R800i
Click to expand...
Click to collapse
Lol nice evaluation.
I've been too busy to follow these changes recently. Btw what do you mean by nand initialization. We need to fix nand detection or something?
Send from my GingerDX using XDA App
I talked to FXP about that NAND init. and it seems it wasn't actually SE's mistake, that's why kernel works after all and NAND init is fine.
Paul1989 said:
hi blagus, im just wondering when you will be able to upload the new kernel? i dont mean to be hasty its just sony x10,x10mini and x10 are flying with thier new kernels and we seem to be lagging behind sum what. again i dont mean this in a nasty way and please dont take offence to this post im very supportive of yours and the other devs beautiful work please let us know soon thanks bro and great job
Click to expand...
Click to collapse
Being part of FXP, my SEtweak will be based on FXP's kernel from github repo, and I'll include recovery in ramdisk as well.
It will, however, be modified and will have standard SEtweak features listed in first post.
SpyderX said:
Wow...replaced in 5 minutes , quite fast.
@Blagus
Is it ever possible for a X8 kernel in the future to automatically convert /system, /data and /cache into ext4? Because I remember Galaxy Ace forums has a kernel that does this. Just a question .
Click to expand...
Click to collapse
Hmm... S1Boot actually handles partitions so I'm not sure... also, yaffs2 FS is made specially for NAND flash chips in phones, so ext4 shouldn't give much boost - absolute need for ext4 conversion is present only on Samsung phones which use rfs by default, and that's quite slow.
LINK
Blagus said:
Hmm... S1Boot actually handles partitions so I'm not sure... also, yaffs2 FS is made specially for NAND flash chips in phones, so ext4 shouldn't give much boost - absolute need for ext4 conversion is present only on Samsung phones which use rfs by default, and that's quite slow.
Click to expand...
Click to collapse
will you be uploading new kernel tonight mate or will it be in morning ??????? thanks for fast reply
as soon as i get my hands on FXP CM7 ramdisk to extract recovery and grab fxp kernel from git. should be very soon
Paul1989 said:
will you be uploading new kernel tonight mate or will it be in morning ??????? thanks for fast reply
Click to expand...
Click to collapse
Sent from my R800i
Blagus said:
as soon as i get my hands on FXP CM7 ramdisk to extract recovery and grab fxp kernel from git. should be very soon
Sent from my R800i
Click to expand...
Click to collapse
Thanks a lot I look forward to flashing it bro. Very good work. Just anuva thing do u think u will be able to share the kernel u successful flashed today please I'm itching to test bro many thanks
Blugus, could you incrase overall in-call volume?
Its pretty hard to talk when in loud place.
Sent from my Shakira using Tapatalk
Will there be a dual-recovery,or only CWM like in FXP kernel ?
Rikcon said:
Will there be a dual-recovery,or only CWM like in FXP kernel ?
Click to expand...
Click to collapse
Why would we need million of recoveries? CWM is just fine and enough, and supports restoring from xRecovery.
Blagus said:
Why would we need million of recoveries? CWM is just fine and enough, and supports restoring from xRecovery.
Click to expand...
Click to collapse
I guess that the problem is that some devs didn´t migrate to CWM, and if we switch to this ROM which is using only CWM, then we need to back to stock, install xrecovery and then the other ROM , since CWM doesn´t install zip files made for xRecovery.
biscoitu said:
I guess that the problem is that some devs didn´t migrate to CWM, and if we switch to this ROM which is using only CWM, then we need to back to stock, install xrecovery and then the other ROM , since CWM doesn´t install zip files made for xRecovery.
Click to expand...
Click to collapse
Well, ask ROM dev to convert amend script to edify, or do it yourself with aZuZu's tool. I will not include xRecovery because CWM supersedes it and it's official FXP's recovery.
biscoitu said:
I guess that the problem is that some devs didn´t migrate to CWM, and if we switch to this ROM which is using only CWM, then we need to back to stock, install xrecovery and then the other ROM , since CWM doesn´t install zip files made for xRecovery.
Click to expand...
Click to collapse
You can convert the zip for xRecovery to for CWM by a simple tool. Get it here
I had tested it, and it's really easy and works fine.
Been playing around with Kernel development and created an overclocked kernel for the 4.0.2.A.0 stock Rom.
There's nothing too speciall in it at the moment, but lets you overclock the Ray to 1.9Ghz using the source released by SE and the modified CPU steps that IF2 posted here: http://forum.xda-developers.com/showthread.php?t=1165355
There's no custom bootloader/Clockwork mod and no additional governers (at the moment) although I may add these in future as I learn more.
It seems to work well enough, and everything seems to be working as standard. I experience random lock-ups at 1.9 and occasionally 1.8Ghz, especially when it goes into/out of sleep when the screen turns off. Lower frequencies seem stable though.
This is released as-is, I'm using it myself but I can't be held responsible for any instabilities or failures you might experience. Just thought it might be of use to some people.
The new .img file can be downloaded from here: http://dl.dropbox.com/u/17615284/4.0.2.A.0-Overclock.img
To install just use fastboot in the usual way. To return to stock, extract kernel.sin from the official update image using WinZip/WinRar etc and flash using fastboot again.
Thanks a lot hartej !
Just flashed it, seems to work as described. I OC to 1.4 Ghz
Will report back if there is any issue.
Looking forward for additional CPU governors, insecure kernel, autoroot and clockwork recovery
Thanks again for your hard work
piflechien said:
Looking forward for additional CPU governors, insecure kernel, autoroot and clockwork recovery
Click to expand...
Click to collapse
That's the plan eventually, but still just learing the ropes so don't expect all that by tomorrow Glad I could help.
Thanks for the efforts. I set up to 1.3 Ghz and so far so good.
glad to see u finally posting this
my latest sources are pushed to:
https://github.com/DooMLoRD/Xperia-2011-Kernel-2.6.32.9
enjoy!
DooMLoRD said:
glad to see u finally posting this
my latest sources are pushed to:
https://github.com/DooMLoRD/Xperia-2011-Kernel-2.6.32.9
enjoy!
Click to expand...
Click to collapse
Finally? Cheeky buggar!
Not really had any time unfortunately due to work, but if you've updated the defconfig for the Ray I might have a bash at your sources in the morning (still don't understand them!)
Thanks again though - if it wasn't for your help and the fact you stopped developing for the Ray I'd never had started playing about with kernels myself!
hartej said:
Finally? Cheeky buggar!
Not really had any time unfortunately due to work, but if you've updated the defconfig for the Ray I might have a bash at your sources in the morning (still don't understand them!)
Thanks again though - if it wasn't for your help and the fact you stopped developing for the Ray I'd never had started playing about with kernels myself!
Click to expand...
Click to collapse
hehe... no defconfigs are only updated for ARC & PLAY... i wont be updating defconfigs for other devices... though u can easily figure out the additions to be done
if u need any help send me p.m./gtalk
DooMLoRD said:
hehe... no defconfigs are only updated for ARC & PLAY... i wont be updating defconfigs for other devices... though u can easily figure out the additions to be done
if u need any help send me p.m./gtalk
Click to expand...
Click to collapse
Will do - thanks again for your help
It could be a good idea to move this thread in the newly created subforum dedicated to the Ray: http://forum.xda-developers.com/forumdisplay.php?f=1351
Can you also make a kernel for cm7 with some other governors like Doomkernel's one but for fxp043. Thanks in advance
I've created a new thread in the Ray forum as I don't think I can move this one without being a mod: http://forum.xda-developers.com/showthread.php?p=18829345
nos1609 said:
Can you also make a kernel for cm7 with some other governors like Doomkernel's one but for fxp043. Thanks in advance
Click to expand...
Click to collapse
This is all pretty new to me, so don't expect too much too fast!
In future I may look at CM7 images but currently I'm on the stock firmware (at least until the flash in CM7 is fixed) and as I have to use the phone daily I'm not prepared to switch between firmwares to be developing for different sources at this time.
I've been using CM7 on my other devices (HTC Desire and ZTE Blade) so will most likely switch to it when some of the bugs have been worked out.When this happens I'll look at the CM7 Kernel.
Hey...just wondering...How to put acpuclock-7x30.c in boot.img?or after rooting the phone and use root explorer?
I found this file from another thread(http://forum.xda-developers.com/showthread.php?t=1320270&page=2)
Kudos to hartej
for a this device which has the same cpu/gpu as mine and i wanted to know where this file is and how can i replace it in order to use the new frequency and steps!!
Thank you!! (Yes i am a lil bit noob,sorry)
nfsmw_gr said:
Hey...just wondering...How to put acpuclock-7x30.c in boot.img?or after rooting the phone and use root explorer?
I found this file from another thread(http://forum.xda-developers.com/showthread.php?t=1320270&page=2)
Kudos to hartej
for a this device which has the same cpu/gpu as mine and i wanted to know where this file is and how can i replace it in order to use the new frequency and steps!!
Thank you!! (Yes i am a lil bit noob,sorry)
Click to expand...
Click to collapse
Not a trivial matter. Here's a synopsis: You'll have to get a compatible kernel source tree, then get a linux environment set up with the cross compiler chain for your target system (Arm), then modify and compile the kernel. Once you've got a good working kernel, you need to put together a boot.img for your device. You'll need a working boot.img to tear apart. You break the boot.img down into its ramdisk and kernel, then rebuild it using your new kernel. Once you've got a working boot.img, you flash it to your device.
Each of the above steps involve substeps that could fill entire posts or more. Like I said, this is anything but trivial.
Are you sure there's not a custom kernel/boot image already compiled for your device? That would be the easiest route.
Thank you sooo much for aswering!!
No,there isn't any kernel available for my device WT19i really only cm7 is the other option instead of stock rom/kernel...
It has though the ability to chose 1.6ghz instead of the stock 1.0ghz for my device,but i was just asking weather this could be done...
Sooo...i need to follow some kind of tutorial to do this on my own huh..?
nfsmw_gr said:
Thank you sooo much for aswering!!
No,there isn't any kernel available for my device WT19i really only cm7 is the other option instead of stock rom/kernel...
It has though the ability to chose 1.6ghz instead of the stock 1.0ghz for my device,but i was just asking weather this could be done...
Sooo...i need to follow some kind of tutorial to do this on my own huh..?
Click to expand...
Click to collapse
Are you sure about the kernel source? The Linux GPL requires that OEMs provide their modified kernel source code as part of the terms of use. I don't know what a WT19i is, but they probably have a site somewhere that has the kernel source code. If not, then there's really not much you can do.
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums
Moving to Q&A
answer...
Well...it's a very new device(Live with walkman is it's normal name)
The only site i could find something is http://developer.sonyericsson.com/wportal/devworld/search-downloads/opensource?cc=gb&lc=en
but it doesn't have my device name anywhere except only the firmware version(which is the same with 4 more devices!!!! :S )
Soo...i can't do anything huh..?
Gene Poole said:
Are you sure about the kernel source? The Linux GPL requires that OEMs provide their modified kernel source code as part of the terms of use. I don't know what a WT19i is, but they probably have a site somewhere that has the kernel source code. If not, then there's really not much you can do.
Click to expand...
Click to collapse
Gene Poole said:
I don't know what a WT19i is
Click to expand...
Click to collapse
This: http://pdadb.net/index.php?m=specs&id=2979&c=sony_ericsson_wt19__wt19i_walkman.
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!