Related
This thread will contain my port from FreeX10 for the big x10 by zdzihu.
Status:
Creating vendor setup, man, this takes ages!
Next:
Compile
Fix basic drivers (like my Sense release)
Share
The Work's
Nothing, atm
The Won't 's:
Booting
Camera
Update:
I've made a script to install xrecovery, root and fix busybox after updating to 2.0.2.A.0.24
I have packed it into an exe for your ease. Of course I know you'll want a virusscan so I've added links on the bottom. It's just a extracting sfx archive so if you have knowledge with that you can just extract it and see, if you don't trust me
x10 Mini Pro VirusScan @ virusscan.jotti.org
x10 Mini VirusScan @ virusscan.jotti.org
I'll be more and happy to assist in the port for mini pro. only thing is i have exams until mid of feburary. but i think i'll be able to make some free time and help!
which tool chain do we need? codesourcery?
Mikevhl said:
Hello, I have a minor issue in porting over FreeX10.
Namely the camera, it is really being a pain in the {nasty word goes here}
the compiling process keeps on pooping me out with errors related to libcamera.so.
the libcamera.so is looking for android::CameraParameters::ORIENTATION, android::CameraParameters::ORIENTATION_LANDSCAPE and android::CameraParameters::ORIENTATION_PORTRAIT
which aren't devined in the AOSP source and are something Sony Ericsson has added in.
I tried putting in libcameraservice.so, libfacedetection.so and libfacedetectjnitest.so, but it's still complaining about resources.
Anyone wants to team up and help me port?
Greetings
Click to expand...
Click to collapse
Here's the whole change: https://github.com/xian1243/android_frameworks_base/commit/8e309093776b259a23077feb095aee082f68a2f8
But still, I suggest to compile with USE_CAMERA_STUB := true and worry about it later
Cheers,
z
Can i be like beta tester when ur done?
zdzihu said:
Here's the whole change: https://github.com/xian1243/android_frameworks_base/commit/8e309093776b259a23077feb095aee082f68a2f8
But still, I suggest to compile with USE_CAMERA_STUB := true and worry about it later
Cheers,
z
Click to expand...
Click to collapse
Thanks, I'll take a look at that tomorrow
maxaan said:
Can i be like beta tester when ur done?
i know i only have 2 posts but i know android and know some basic stuff about adb and i have a rooted u20i with xRecovery (Thank you so much Zdzihu!)
Ask if u need to know something more...
Click to expand...
Click to collapse
Sure, I'll put the rom online as soon as I have it booting, in pre-alpha stage that is.
Don't expect too much though, by 'booting' I mean that you get to the launcher.
Camera won't work for sure for the time being, but other than that I don't expect too many issues.
Thanks for your interest!
Mikevhl said:
Sure, I'll put the rom online as soon as I have it booting, in pre-alpha stage that is.
Don't expect too much though, by 'booting' I mean that you get to the launcher.
Camera won't work for sure for the time being, but other than that I don't expect too many issues.
Thanks for your interest!
Click to expand...
Click to collapse
Will you put it up in this thread or somwhere else?
Sounds great but Is this only going to be for the Mini
If you want to - I could just be the alpha and beta tester.
Way to go pal!
maxaan said:
Will you put it up in this thread or somwhere else?
Click to expand...
Click to collapse
I'll post it in the first post, it'll probably be sometime later today.
Manny- said:
Sounds great but Is this only going to be for the Mini
Click to expand...
Click to collapse
Pretty easy to port this over to the Mini once I got this running, but the build I'm working on right now is for the x10 Mini Pro.
zyker said:
Way to go pal!
Click to expand...
Click to collapse
Thank you,
but It'll take a long time before I get this to run smoothly
ok its working .. whats next?
Mikevhl said:
This thread will contain my port from FreeX10 for the big x10 by zdzihu.
Mind testing my port from xRecovery-installer? I've attached it.
Status:
Redownloading the Repo.
Commiting changes released by zdzihu from his Github repo.
Compiling the AOSP using zdzihu's changes.
Next:
Test on device.
Help Needed with:
Nothing at the moment, pre-alpha will probably be up later today.
Click to expand...
Click to collapse
Is there a xRecovery 0.2?
So Nice !
Waiting for this
maxaan said:
Is there a xRecovery 0.2?
Click to expand...
Click to collapse
This is a port of the xRecovery installer by zoz33.
The big x10 which the original installer is from is using xRecovery 0.2 but I replaced the files with our xRecovery 0.1
So this is basically an "easy install mode" for our xRecovery 0.1
Mikevhl said:
This is a port of the xRecovery installer by zoz33.
The big x10 which the original installer is from is using xRecovery 0.2 but I replaced the files with our xRecovery 0.1
So this is basically an "easy install mode" for our xRecovery 0.1
Click to expand...
Click to collapse
Ok. When will you upload the rom? Im so excited!!
Next:
Uploading, any preferences for mirrors?
Mediafire
Please put up some screens ASAP then, + info on whats working and whats not.
Anyone thought of compiling a 2.3 ROM for the X10 mini pro.
Or is it not possible yet? if so, why ? =)
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.
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.
Intro
Ok, this will be another fun.
Again, my first attempt (like FroyoBread and GingerDX!) to build a custom Linux kernel for a phone. I've just found some free time this weekend This time, this is a kernel. Again, you can guess it's a Linux kernel having my customized features. We will gradually see what can be done
The main goal is to have a fast, smooth, lightweight kernel with special features.
This Linux kernel is based on our great FreeXperia Project (Jerpelea) kernel. Thank you for your unbelievable contribution for our Xperias. I still use racht's great compiling machine for this project. Thank you racht.
Features
Linux 2.6.29
Default GingerDX logo
X8Gesture / AX8MT for (fake) dual touch
ext 2/3/4 support
FXP's merged minmax / smartass / smartass V2 governor
netfilter / iptables
swap. NOT recommended.
MDDI fix
Brain **** Scheduler
Known bugs
None (?)
Requirements
Unlocked bootloader
Flashtool 2.9.1
Desire to void your warranty!
Downloads
v004
v003
v002
v001
Install instruction
1. Download
2. Turn off the phone
3. Run flashtool
4. Press Flash, choose downloaded file
5. Turn on phone while pressing back button
6. Wait till progress finishes
7. Unplug the phone, turn it on back
8. Enjoy.
Notice
1. This kernel is tested by me only on GingerDX. I don't test with other ROMs, so it is only supported if you are using GingerDX. (Perhaps this will change in future, but not now)
2. This kernel is written for E15i. I don't have E15a, so if you have problems with E15a, I cannot help.
3. This kernel is in development. It may contain bugs. If you have bugs (reboot, something not working, etc...), post it here. Don't send me PM for technical problems. I will not answer most of technical PMs
4. Incompatible with FXP ROM. Wifi will not work on his ROM.
5. Source: it has been on github for a long time but how come I forgot to put the link here @[email protected]
Thanks
Thanks go to the_laser, jerpelea, racht, nobodyAtall, zdzihu, Bin4ry and lots of other contributors...
Release history
October 04 v004.
SD Card compatibility fix.
Notice: after this release I'll be very busy. I will not work on both GDX and LDX for some time.
September 27 v003. Fully working.
Wifi fix! Thanks to FXP.
Remove chargemon compatibility to solve 100% load of init process.
September 24 v002. Improvements.
Integrated ClockworkMod 4.0.1.5. Use touchscreen to activate it during boot.
Built in UV/OC. Set 614MHz as default and removed 600MHz. I'm not a fan of OC.
BFS 0.313
Chargemon compatible!
September 19 v001. Initial public release.
Development (What has been done in my development kernel)
Nothing yet
Disclaimer
I'm not responsible if this kernel bricks your lovely phone. Use it at your own risk!
Donation
You like my kernel? Feel free to
. I'd like some beer in this hot summer!
Wow dx, you are truly rocking X8!
Amazing job, im going to wait a little bit til this gets better!!!
Goodbye!
I agree with the comment before mine
Keep up the good work...
Can this be flashed on top of gdx ROM or we need to do it from stock ROM?
Sent from my X8 using xda premium
thanks so much dx, you are really awesome
this kernel can be used with other rom, like mini cm? thanks u
wow.. thanks and keep it up bro..
ps. noob here about this kernel thing, do I need to unlock first the bootloader or just flash it? Sorry co'z i don't see it in the installation procedure..thanks
Thanks, doixanh, you're the man! Although i'll keep my paws away from my bootloader for a little longer until all this custom kernel thing settles down
Keep up the awesome work!
Well dx, what word should we use to describe you? I'm just happy to see you joining this another fun time. Thks for such good job.
Sent from my X8
@DX you need to change wifi module to make wifi work
come to think of it.
what are kernel?
where is the screenshot? (for example?)
Rycon33 said:
Can this be flashed on top of gdx ROM or we need to do it from stock ROM?
Sent from my X8 using xda premium
Click to expand...
Click to collapse
my question also
Nice work, dx
Nice work DX !!!
unfortunately i use WiFi a lot so i will w8 for next update
I'm really sorry to see these guys that want kernel but they dont know what it is:
fakhry7 said:
come to think of it.
what are kernel?
where is the screenshot? (for example?)
Click to expand...
Click to collapse
Don't get disappointed for them
Yes I remember Angga has the same question regarding wifi, it will be fix soon
GJ, DX
anyways... shouldn't u have a warning of some sort to remove the modules already included in your kernel? it will mess up the memory addressing and cause bootloops, no?
also, requirements should have "Unlocked bootloader" too for those ignorant twits
Wow, nice worck!!!
chewdaniel said:
GJ, DX
anyways... shouldn't u have a warning of some sort to remove the modules already included in your kernel? it will mess up the memory addressing and cause bootloops, no?
also, requirements should have "Unlocked bootloader" too for those ignorant twits
Click to expand...
Click to collapse
Wow! You're so great. Maybe you can be one of the president of SE. Nice bro.
Can't boot with stock rom. Appear the GDX boot image but then go to black screen.
Thanks but I guess it will be hard for just one man to develop a kernel and a rom at the same time....so i appreciate all of this contribution to this community
Sent from my X8 using xda premium
Good work
Sent from my Xperia X8 using Tapatalk
ANDROID RAMDIZK FOR JB ON XPERIA U
Hi all, my purpose is to create a mount point for the android system jb, according to knowledge, with modifications you can start ramdizk latest android on the same kernel.
ACCORDING TO MY EXPERIENCE IN JB ICS AND LIBRARIES USED FOR THE SAME IN THIS CASE MALI400 GPU, so it's nothing to make forced changes in the kernel.
What you need to do is make changes to the ramdizk.
You can obtain these files from a jb kernel and extract the ramdizk creating mount points for the start of the software ...
I invite you to participate and contribute to achieving ramdizk, I'm working on this ...
IN X8 SECTION, IS POSSIBLE BOOT ANDROID 2.2 AND 2.3 ON STOCK KERNEL WITH MODIFICATIONS ON RAMDIZK
Based on some reference books I read, an Android system starts up in following main steps:
CPU reads a hard-coded address which usually points to some bootloader program
The bootloader initializes the RAM, puts basic hardware in a quiescent state, loads the the kernel and RAM disk, and jumps to the kernel.
start_kernel() initializes subsystems and proceeds to call the init function of built-in drivers.
The kernel mount its root system (from ramdisk.img).
init.rc is then called to set up the environment variables such as system path, mount other filesystems, start native daemons and so on.
Now, to answer your question: "Is it possible to mount a ramdisk in Android before the Android framework starts, but after the underlying Linux kernel has started?" -- I think this is exactly what android did.
INITS
The fixes required for ramdisk.tar :
init.rc file should have 2 parts from original sony init.rc that are marked as #SEMC
add original init.delta.rc and init.delta.sh from sony or one of my ramdisks, those are responsible for service declarations.
THIS IS A KERNEL FOR GB, ICS AND JB NAA KERNEL
Ramdizk Inector tool
INIT FOR JB HERE
IM ALREADY HAVE THE ROM... IM NEED BOOTIMG FROM JB... ONLY INITS AND COMPILE THIS... WE CAN USE ATIS RAMDISK AS A BASE
PROGRESS
I AM STARTING TO WORK ON THIS
IM WORKING ON THIS...
Interesting....i can help
You can close the thread
jb need new graphics driver into KERNEL
DevSwift1 said:
You can close the thread
jb need new graphics driver into KERNEL
Click to expand...
Click to collapse
NOT NECESARY....
REALLY NOW WHAT I CAN DO, NOT LIKE YOU, CM10.1 COMPILED FROM SOURCES WITHOUT MORE THAN BIG CHANGE CAMERA SOLUTION, NOT MAKE ME LAUGH, I'll show WHAT REALLY IS A JOB.
JB CAN WORK WITH THEIR DRIVERS FOR ICS AND WITH THE SAME BLOBS, already checked ON XPERIA X8
xperiafan13 said:
NOT NECESARY....
REALLY NOW WHAT I CAN DO, NOT LIKE YOU, CM10.1 COMPILED FROM SOURCES WITHOUT MORE THAN BIG CHANGE CAMERA SOLUTION, NOT MAKE ME LAUGH, I'll show WHAT REALLY IS A JOB.
Click to expand...
Click to collapse
ok so show what you can do
could this mean a bug free jellybean?
lol so you are comparing X8 with Xperia U? really? go on and do something then you smart455 LOL
it would be worth a try, imagine, jelly bean on locked bootloader
leave him alone he is the only one that is helping us and we have asked you all so many times to help and now someone suggest something you argue
Dear brother, I was a X8 user and a fan of your stock SGM CM7. I agree with the fact that stock ramdisk can goes a long way. But brother, it is not the same here in Xperia U. But I'm waiting for you to hear good news
P.S: Our X8 cannot run 4.0 and up well. You know that. And also CM7 is a big laggy. At some point, it will be same here for booting up JB with ICS ramdisk
Sent from my ST25i using Tapatalk 2
---------- Post added at 05:47 AM ---------- Previous post was at 05:46 AM ----------
DevSwift1 said:
ok so show what you can do
Click to expand...
Click to collapse
We shall see
Sent from my ST25i using Tapatalk 2
HELLO
Im already pack all files from jb ramdisk... Please test this with atis patch
REMOVED
xperiafan13 said:
Im already pack all files from jb ramdisk... Please test this with atis patch
RAMDISK ALPHA
Click to expand...
Click to collapse
You try first
Sent from my ST25i using Tapatalk 2
little zed said:
you try first
sent from my st25i using tapatalk 2
Click to expand...
Click to collapse
im make the current changes to test this....
xperiafan13 said:
im make the current changes to test this....
Click to expand...
Click to collapse
Provide screenshot if you really booted man.
Sent from my ST25i using Tapatalk 2
little zed said:
provide screenshot if you really booted man.
sent from my st25i using tapatalk 2
Click to expand...
Click to collapse
progress:
Well finally i can compile in tar format
already mount ramdisk, but this is recovery mode
IM NEED MAKE CHANGES AND DELETE SOME FILES IM ONLY NEED MOUNT SYSTEM AND ALL IS DONE
xperiafan13 said:
progress:
Well finally i can compile in tar format
already mount ramdisk, but this is recovery mode
IM NEED MAKE CHANGES AND DELETE SOME FILES IM ONLY NEED MOUNT SYSTEM AND ALL IS DONE
Click to expand...
Click to collapse
the method to properly pack ra.disk in tar is on atis112 his firedroid git repo,s
Sent from my S500 using xda app-developers app
SpaceCaker said:
the method to properly pack ra.disk in tar is on atis112 his firedroid git repo,s
Sent from my S500 using xda app-developers app
Click to expand...
Click to collapse
Waiting
Sent from my ST25i using Tapatalk 2
Sorry for spamming, i am not a developer, just a ROM tester and active member on XDA....reading all posts and i can't understand many things like TAR etc.... This trhead wants to achieve having JB on locked Bootloader? If so, this is simply great and KEEP GOING!
Ready to test! I don't care if I brick my phone! I just want JB on my xperia u LB! And leave @xperiafan13 because he is the only one trying, if it works works if not thanks for trying!
Sent from my Xperia U using xda app-developers app
SpaceCaker said:
the method to properly pack ra.disk in tar is on atis112 his firedroid git repo,s
Sent from my S500 using xda app-developers app
Click to expand...
Click to collapse
you can also use winrar or ubuntu to just change the files inside one of the existing ones from atis, it does work afaik
i modified the current atis ramdisk with stuff from the XNovathor 4.0.4 Ramdisk in order to make XNovathor 4.0.4 boot on LockedBL, just drag and drop worked fine i guess, but yeah there are troubles in mounting some partitions, i think i forgot to change something lolz