Related
Hello!
This is a thread where potential developers can get kernel and platform source code for Samsung Galaxy S I9070 Advance, and other info. I will try to update this until we will have first custom rom ready. I encourage everybody with some experience with android development, to share their knowledge with other users here. Please if any of you will make any progress in rooting, making recovery or developing custom rom, to write here in this thread or even start a new one if some major break trough will be made.
Ok so here are the links to sources (I don't know the diference between those to, but I guess it is region related):
GTI9070_GB_OpenSoruce
GTI9070_LA_GB_OpenSoruce
All sources, can be found HERE.
In the attachment you can also find some other info I've pulled from my phone, which used to be rooted, cause I had some test version. I hope all this stuff will help us get root access, custom recovery and last but not least a whole bunch of custom roms.
NOW LETS HACKING AND DEVELOPING BEGIN!!!
One more thing, PLEASE take a minute to VOTE for this phone to get its own forum section here on XDA. Just make a post in THIS THREAD. The device is not in the poll yet, so you must write a post in thread. THANK YOU!
We've made a step into a right direction with a lot of help from forum I've made a working root method!
I've hard bricked my phone, so I am off the developemnt from this phone, only if by some chance I get a replacement. Sorry guys, in spirit of developing I've killed my phone .
I wish I was better at kernel development... I would love some development for this phone!
Sent from my GT-I9070 via Tapatalk 2
I've somehow managed to configure linux and pulled andorid sources from the repo, now I have to figured out how to compile a kernel. I have much to learn but if nobody else will give it a try, maybe I will succeed.
yeah...we as new wannabe devs are learning back the basics...i'm still trying to figure out what to do about the kernel source...afraid of bricking my phone in the process... hehe.. but all the kernel sources for all regions has been released...
kilsmap said:
yeah...we as new wannabe devs are learning back the basics...i'm still trying to figure out what to do about the kernel source...afraid of bricking my phone in the process... hehe.. but all the kernel sources for all regions has been released...
Click to expand...
Click to collapse
Dear friend. I come from China, now I already have a good i9070, I can help you with your test, you can send to my mailbox [email protected]
hmmm...qzem, im getting stuck at initramfs...how do we get these for our phones? because the kernel can only be flashed safely when it is compiled with initramfs files from our phone... and for the phone to get custom recovery, i think they will also need initramfs files...
kilsmap said:
hmmm...qzem, im getting stuck at initramfs...how do we get these for our phones? because the kernel can only be flashed safely when it is compiled with initramfs files from our phone... and for the phone to get custom recovery, i think they will also need initramfs files...
Click to expand...
Click to collapse
Same thing here. I have no idea how to get those, been asking around the forum an searching, but for now all the directions indicates that you need to have root access to get iniramfs. That really sucks...
hahaha...from this point of view, all Samsung phones after Galaxy S Advance will be quite hard to root... I'm waiting for the Galaxy SIII to launch, and for someone to root it... Maybe then we will be able to use the same way to root our phone... If only we can see what's inside our kernel.bin.md5... I'm sure the files we needed are in there...
the initrams? u mean ramdisk?
grab stock boot.img and extract from it.
the stock boot.img can be grabbed from odin flashable stock rom.
an0nym0us_ said:
the initrams? u mean ramdisk?
grab stock boot.img and extract from it.
the stock boot.img can be grabbed from odin flashable stock rom.
Click to expand...
Click to collapse
Yeah.. We have the stock rom, but can't figure out which one should we extract the boot.img from.. There was system.img.md5, cache.img.md5, hidden.img.md5, modem.bin.md5, and kernel.bin.md5... So which one? My suspicion lies to the kernel.bin, but I have no idea how to extract it..
Sent from my GT-I9070 using XDA
I have compiled a stock kernel from source code, so I got zImage file, now I have to find out how to build boot.img from this. I will contiue tommorow I hope I am close to the solution! Mabe few days to crack this baby .
qzem said:
I have compiled a stock kernel from source code, so I got zImage file, now I have to find out how to build boot.img from this. I will contiue tommorow I hope I am close to the solution! Mabe few days to crack this baby .
Click to expand...
Click to collapse
Good luck!
Hope you get to a solution soon
I can't work on it as I currently don't have a phone to test on, sent it in for repairs.
qzem said:
I have compiled a stock kernel from source code, so I got zImage file, now I have to find out how to build boot.img from this. I will contiue tommorow I hope I am close to the solution! Mabe few days to crack this baby .
Click to expand...
Click to collapse
Have u tried flashing it directly to the phone? You don't have to make it into a boot.img to flash it.. Because I'm afraid that the zImage will be useless if not paired with working initramfs.. Compiling the kernel is quite straightforward, the thing is to get the initramfs to turn the kernel insecure.. There are also scripts to extract initramfs from zImage, but I haven't had time to test it..
Sent from my GT-I9070 using XDA
Ok what exactly is in initramfs, that is what I am trying to figured out? I've recompiled some other samsung boot.img with dsixda kitchen, and I got zImage and a folder caled boot.img-ramdisk, which included different files like init, init.goldfish.rc init.rc, default.prop, etc. In a file default prop is the setting ro.secure=0, and this is the settign I belive, that makes kernel insecure. I've also tried to unpack the zImage that I got from thsi boot.img, with the kitchen to see if includes those so called initramfs, but it doesn't. So I think that if I figured out which files should be in ramdisk, and if those files can be pulled of the phone, that than maybe I can repack a working boot.img. What do you think?
qzem said:
Ok what exactly is in initramfs, that is what I am trying to figured out? I've recompiled some other samsung boot.img with dsixda kitchen, and I got zImage and a folder caled boot.img-ramdisk, which included different files like init, init.goldfish.rc init.rc, default.prop, etc. In a file default prop is the setting ro.secure=0, and this is the settign I belive, that makes kernel insecure. I've also tried to unpack the zImage that I got from thsi boot.img, with the kitchen to see if includes those so called initramfs, but it doesn't. So I think that if I figured out which files should be in ramdisk, and if those files can be pulled of the phone, that than maybe I can repack a working boot.img. What do you think?
Click to expand...
Click to collapse
Yep, you got everything right there, I think.. Initramfs, ramdisk are the same thing.. They should include the cpio.gz, init.rc, default.prop etc... Have you extracted these files from the source kernel? Cos I don't think we can copy directly from phone, cos we need to preserve the permissions set on the files... Can you do that with kitchen?
Sent from my GT-I9070 using XDA
I am following the topic and hoping it works out the development of kernels and roms to the device.
Come on it has to be a way to compile an insecure kernel without having the access to rooted phone. Cause all the options I found till now, required some files, that can only bee pull from rooted phone. But the whole point of an insecure kernel is the possibility to root the phone. Anybody can help us? Maybe I should start another thread, damn it!
Haha... Yeah, somehow I feel that Samsung is screwing with us, what with the new firmware format (never had kernel.bin before) and secured kernel, this is becoming impossible.. If we just have some devs good-hearted enough to port CWM recovery for us.. But without initramfs, I don't know if it's possible..
Sent from my GT-I9070 using XDA
The initramfs is inside kernel.bin.md5 (as for the Galaxy S firmware).
kernel.bin.md5 is a normal zImage Linux kernel (+md5).
the initramfs is included in the kernel image (see http://forum.xda-developers.com/wiki/Extract_initramfs_from_zImage)
the initramfs is in our case a uncompressed cpio archive, therefore the script in the wiki does not work, but https://github.com/mistadman/Extract-Kernel-Initramfs/blob/master/unpack-initramfs can extract it without problem.
So, there should be no difficulty to root the i9070...
The easiest way would be to change the initramfs and repack everything.
DISCLAIMER: I own Xperia X10, Xperia J, Xperia Tipo, Xperia S and Xperia V, releases of all other phones are not personally tested by me. But since the kernel is the same in FXP/KXP ROMs I presume they would not harm your device in any way
Huge props go to all TeamWIn people like Dees_Troy and bigbiff and everyone else for developing this awesome recovery and lots of thanks to FreeXperia Team (FXP, Kali-, codeworkx, bin4ry,) for maintaining device configs for Xperias
This recovery is embedded into the ramdisk of a normal AOKP 4.1.2 bootimage. The kernels are same as the latest AOKP released by KXP team. These kernels should work with FXP's CM10, and other ROM's based of it (KXP ROM, Pac-man, officialCM10 etc). These kernels will not work on stock/cm7/cm9/blah/blah/any other ROM.
INSTRUCTIONS :
1. Download the zip file for your device (twrp2.4.3-xxxxx.zip)
2. Extract the boot.img from zip on your PC, and copy the whole zip file on device's SDcard.
3. Fastboot the kernel using the terminal command
Code:
fastboot flash boot boot.img
4. To enter recovery, when LED is pink press {vol up for 2012 models} or {vol down for 2011 models}
5. Flash zip that you kept in sdcard from recovery (wifi/OTG/etc will not work without proper modules flashed).
6. Enjoy
DOWNLOADS:
Mirror1 |or| Mirror2
download according to your device name in this list
Code:
[LIST]
[*]anzu Arc/ArcS
[*]aoba ION
[*]coconut Live with WALKMAN
[*]haida Neo V
[*]hallon Neo
[*]hayabusa TX
[*]hikari Acro S
[*]jlo J
[*]iyokan Pro
[*]mango MiniPro
[*]mesona Miro
[*]mint T
[*]nozomi S/SL
[*]satsuma Active
[*]smultron Mini
[*]tapioca Tipo
[*]tsubasa V
[*]urushi Ray
[*]zeus Play
[*]zeusc Play CDMA
[/LIST]
CHANGELOG :
All official changes to TWRP is found on http://teamw.in
Code:
=============twrp 2.4.3
code updated to oficial twrp 2.4.3.0
new device J, Tipo, Miro supported
=============twrp2.4
code updated to official twrp 2.4.1.0
fixed "/boot not found" error on 2011 phones
=============twrp 2.3
official twrp 2.3 sources
first release
=======================================================================================
for advanced users/devs/modders/porters
=======================================================================================
SOURCES:
The kernels present inside the bootimages are compiled from these sources
https://github.com/KangXperiaProject/android_kernel_sony_msm7x27a (for Tipo, J, Miro)
https://github.com/KangXperiaProject/android_kernel_sony_msm8x60 (for S,Ion,AcroS, T, V, TX)
https://github.com/KangXperiaProject/android_kernel_semc_msm7x30 (for all 2011 model phones)
The device configs are found on
https://github.com/KangXperiaProject/android_device_semc_<yourdevicename> (for all 2011 model phones)
https://github.com/KangXperiaProject/android_device_sony_<yourdevicename> (for all 2012 model phones)
you can also see our merged commits to see the precise patch we applied on each repository to be able to build TWRP
http://smartdev.com.pl:8080/#/q/status:merged,n,z
BUILD FROM SOURCE
To build TWRP for your Xperia,
1. merge the patch to enable TWRP on your own device tree (for eg. http://smartdev.com.pl:8080/#/c/239/ for Xperia T)
2. replace /bootable/recovery folder with TWRP (as mentioned here http://forum.xda-developers.com/showthread.php?t=2069242)
3. If your build folder is not from CM, switch to CM's build folder (i.e the android_build repo)
4. lunch ; mka bootimage;
PORT TO STOCK/ICS/YOU-FAVOURITE-KERNEL
A boot.img consists of the kernel image and the ramdisk (additionally and optionally RPM.bin and commandline). If you want to use TWRP for some other kernel, you have to do this
1. decompile this boot.img (for 2011 models it's a true boot.img, for 2012 models, it's actually a kernel.elf file renamed to boot.img, so you have to decompile accourdingly. you can use my kernel kitchen to do the same)
2. replace the kernel zImage with the one from the kernel you want to port to
3. replace /sbin/ramdisk.cpio with the "UNCOMPRESSED" ramdisk of the kernel you want to port this to. (usually ramdisk is compressed with gzip i.e. ramdisk.cpio.gz. you need to uncompressed ramdisk image i.e. ramdisk.cpio)
4. do not touch anyother thing
5. pack it up into a boot.img (for 2011) or kernel.elf (for 2012) and fastboot it
============================================================================================
BUGS AND SUPPORT
If you have any problem with this please please please post only on this thread, not on any other thread or not on PM.
Please send me the recovery log wherever possible, and also kmsg/dmesg if you can.
If you need assistance porting TWRP to your kernel, or building from source[only for Xperia phones that I have provided builds for], then also you can post here.
Thanks, though in keeping with GPL you need to post your buildable source. In addition so that others can continue and support what you have done, since you obviously have no desire to do so, that is essential. Not very helpful to the community to do a "one-off" venture.
Would you mind publishing your device configuration files for this build so that others can pick it up & maintain it?
jerdog said:
Thanks, though in keeping with GPL you need to post your buildable source. In addition so that others can continue and support what you have done, since you obviously have no desire to do so, that is essential. Not very helpful to the community to do a "one-off" venture.
Click to expand...
Click to collapse
the source is present on http://github.com/KangXperiaProject
also check the latest merged commits on http://smartdev.com.pl:8080
building with KXP_INCLUDE_TWRP := true will give you same product as I have provided here.
the kernel is built off already present sources on KXP github, so there is no GPL violation
and yes I will update the flags on BoardConfigs on all the devices after I make KXP Milestone1-R2 releases, I will sync all local changes.
but again to reiterate, to duplicate the kernel I have posted, stuff is already present on github to do so.
Dees_Troy said:
Would you mind publishing your device configuration files for this build so that others can pick it up & maintain it?
Click to expand...
Click to collapse
just give me a day or two please
and I'll PM you when it's done. (I will update all 15 Xperia devices with the flags needed )
Could anyone post a flashable zip please? don't have a PC right now
Sent from my Xperia T using xda premium
championswimmer said:
the source is present on http://github.com/KangXperiaProject
also check the latest merged commits on http://smartdev.com.pl:8080
building with KXP_INCLUDE_TWRP := true will give you same product as I have provided here.
the kernel is built off already present sources on KXP github, so there is no GPL violation
and yes I will update the flags on BoardConfigs on all the devices after I make KXP Milestone1-R2 releases, I will sync all local changes.
but again to reiterate, to duplicate the kernel I have posted, stuff is already present on github to do so.
Click to expand...
Click to collapse
Update your first post with links to the sources, along with any specific flags. And, to be GPL compliant, you do need to provide all aspects of the build in order that anyone could come in and build from your sources. The best way to do that is to link to the exact source for the specific project (not just the overall github) and to provide the instructions and flags, etc. used in building that specific project in like the README like linux and other GPL-compliant projects do
Although getting GPL compliant is important and totally supportable, I'd still like to leave a big, fat, spelled out THANK YOU for tinkering with TWRP on the xperias. Big thing, big win :thumbup:
Nice thread, well done champ.
If any users are interested in my TWRP build/changes you can see my fork here: https://github.com/cosmicdan/Team-Win-Recovery-Project/commits/jb-wip
Here are the flags I use for Xperia Play BTW:
Code:
# TWRP
DEVICE_RESOLUTION := 480x854
TARGET_RECOVERY_PIXEL_FORMAT := "RGB_565"
TW_FLASH_FROM_STORAGE := true
pictures please? i think this is the recovery have looking for
xdarkmario said:
pictures please? i think this is the recovery have looking for
Click to expand...
Click to collapse
FFS click
Sent from my R800i using xda premium
lol, totally was my plan as well.
olokos said:
FFS click
Sent from my R800i using xda premium
Click to expand...
Click to collapse
lol thanks, that was the recovery i was looking for, but it is now compatible with ICS so i had to go back. looks goo though and easy
xdarkmario said:
lol thanks, that was the recovery i was looking for, but it is now compatible with ICS so i had to go back. looks goo though and easy
Click to expand...
Click to collapse
Not stock ICS no, maybe wedgess will one day. But Turbo Kernel works on CM9/AOKP.
Sent from Xperia Play (R800a) with Tapatalk
I have done on my xperia tx Thank you all the same
Lets hope that will see it inserted in stock kernels too alongside with the cwm recovery . It would be awesome to have 2 recoveries in one kernel.
how to enter this recovery? xperia mini-smultron
shadik555 said:
how to enter this recovery? xperia mini-smultron
Click to expand...
Click to collapse
vol down when led is pink
championswimmer said:
vol down when led is pink
Click to expand...
Click to collapse
it dont work
i tried
AOKP r2 and this kernel,before i installed AOKP,it opened TWRP,but after i installed AOKP,wont open twrp
EDIT:solved-recovery manager,boot in recovery
Thanks! I will test it soon as i get home!
Dose it supports usb otg?
Sent from my Xperia S using xda premium
Okay, so i just saw the xperia acro s got an alpha lollipop build
with nothing working, but hey!
Its a start!
I need help to port it to the xperia ion, xperia s.
THough not functional, but a first build will help.
So can someone please tell me how to port the rom from Acro S to Ion!
ACRO - S / ION / Xperia S Have the same specs too!
So if anything starts working in the hardware section, it probably would be easy to fix the bug on Ion/S too.
So please!
Can someone guide this complete noob to cross port a rom to device of completely same specifications!??
Lets build lollipop and put sony to shame! :highfive:
arjun921 said:
Okay, so i just saw the xperia acro s got an alpha lollipop build
with nothing working, but hey!
Its a start!
I need help to port it to the xperia ion, xperia s.
THough not functional, but a first build will help.
So can someone please tell me how to port the rom from Acro S to Ion!
ACRO - S / ION / Xperia S Have the same specs too!
So if anything starts working in the hardware section, it probably would be easy to fix the bug on Ion/S too.
So please!
Can someone guide this complete noob to cross port a rom to device of completely same specifications!??
Lets build lollipop and put sony to shame! :highfive:
Click to expand...
Click to collapse
You need a kernal, drivers, porting knowledge .
JustPlayingHard said:
You need a kernal, drivers, porting knowledge .
Click to expand...
Click to collapse
Same chipset
Same Resolution
Same Processor
Same Ram
Same GPU
Same Camera
I thought cross porting to devices with completely same hardware was easier than building from source:crying:
Heres the specs comparision anyways
http://www.gsmarena.com/compare.php3?idPhone1=4798&idPhone2=4781
Just to complement, the devices are pretty much indentical, hardware wise. The differences are VERY minor:
Ion has an MicroSD and a 4.55 inch screen, and 16 Gb internal.
Acro S has MicroSD, 4.3 inch screen, 16 Gb internal, is waterproof.
S doesn't have MicroSD, 4.3 inch, 32 Gb internal.
Except for that, they are exactly the same.
Felimenta97 said:
Just to complement, the devices are pretty much indentical, hardware wise. The differences are VERY minor:
Ion has an MicroSD and a 4.55 inch screen, and 16 Gb internal.
Acro S has MicroSD, 4.3 inch screen, 16 Gb internal, is waterproof.
S doesn't have MicroSD, 4.3 inch, 32 Gb internal.
Except for that, they are exactly the same.
Click to expand...
Click to collapse
I know!
Theoretically, older android roms could be ported without any hassles. to devices of same specs.
Replacing app, framework,media in the two zips should technically hvae a fully running rom.
BUt on extracting the zip for acro S, theres nothing that looks familiar:crying::crying::crying:
can anybody help!?
Felimenta97 said:
Just to complement, the devices are pretty much indentical, hardware wise. The differences are VERY minor:
Ion has an MicroSD and a 4.55 inch screen, and 16 Gb internal.
Acro S has MicroSD, 4.3 inch screen, 16 Gb internal, is waterproof.
S doesn't have MicroSD, 4.3 inch, 32 Gb internal.
Except for that, they are exactly the same.
Click to expand...
Click to collapse
Hi old buddy...what's up...long time no see...
arjun921 said:
I know!
Theoretically, older android roms could be ported without any hassles. to devices of same specs.
Replacing app, framework,media in the two zips should technically hvae a fully running rom.
BUt on extracting the zip for acro S, theres nothing that looks familiar:crying::crying::crying:
can anybody help!?
Click to expand...
Click to collapse
You tried to Google that?
I'm almost 100% sure Google will show many tutorials on XDA...
If those devices are exactly the same - that shouldn't be difficult task.
But what are you planning to do with a kernel?
funky0308 said:
Hi old buddy...what's up...long time no see...
You tried to Google that?
I'm almost 100% sure Google will show many tutorials on XDA...
If those devices are exactly the same - that shouldn't be difficult task.
But what are you planning to do with a kernel?
Click to expand...
Click to collapse
Searched google first.
Then asked here, cause last time i posted a nooby question, i was fired with Rude replies
Neways in those guides, it shows to replace files from the Port Rom and replace it with Base Rom.
For that, when i opened the zip of acro s, there are no folders!
And for the record, those guides are quite dated...
I cant even manage to port Kitkat roms. It always goes into a bootloop
For the kernel, i was hoping to use Xperia S's kernel, since that device is supported by AOSP.
arjun921 said:
Searched google first.
Then asked here, cause last time i posted a nooby question, i was fired with Rude replies
Neways in those guides, it shows to replace files from the Port Rom and replace it with Base Rom.
For that, when i opened the zip of acro s, there are no folders!
And for the record, those guides are quite dated...
I cant even manage to port Kitkat roms. It always goes into a bootloop
For the kernel, i was hoping to use Xperia S's kernel, since that device is supported by AOSP.
Click to expand...
Click to collapse
What you mean by that "when i opened the zip of acro s, there are no folders!"?
Which zip is that? AOSP Lolipop for Acro S?
If there's only META-INF folder, then you should have system image in that folder (system.ext4), you have to repack that image to see all folders and files (app, framework, bin etc...)
I don't know much about compiling or porting ROMs but if you provide more informations I'll try to help.
Post a link pf that zip for Acro S so I can see file structure or...better solution, please post screenshoots of ZIP structure (that one that doesn't have folders)
If you have a ftf file for a base you should repack it using flashtool but this is, obviously, something different.
Still....
Flashtool should be the tool you need.
Post some more informations and we'll find solution together..
Searched google first.
Then asked here, cause last time i posted a nooby question, i was fired with Rude replies...
Unfortunately...you are right...XDA has changed and there's not many users who are ready to help
funky0308 said:
What you mean by that "when i opened the zip of acro s, there are no folders!"?
Which zip is that? AOSP Lolipop for Acro S?
If there's only META-INF folder, then you should have system image in that folder (system.ext4), you have to repack that image to see all folders and files (app, framework, bin etc...)
I don't know much about compiling or porting ROMs but if you provide more informations I'll try to help.
Post a link pf that zip for Acro S so I can see file structure or...better solution, please post screenshoots of ZIP structure (that one that doesn't have folders)
If you have a ftf file for a base you should repack it using flashtool but this is, obviously, something different.
Still....
Flashtool should be the tool you need.
Post some more informations and we'll find solution together..
Searched google first.
Then asked here, cause last time i posted a nooby question, i was fired with Rude replies...
Unfortunately...you are right...XDA has changed and there's not many users who are ready to help
Click to expand...
Click to collapse
You're exactly right. But I'm not quite sure how to extract .dat files
The system consists of .dat system files
I've Attached a screenshot of the contents of the zip too
And thanks a ton for atleast trying to help!:good:
In the mean time, I'm also setting up An Ubuntu Machine to build from source.
funky0308 said:
What you mean by that "when i opened the zip of acro s, there are no folders!"?
Which zip is that? AOSP Lolipop for Acro S?
If there's only META-INF folder, then you should have system image in that folder (system.ext4), you have to repack that image to see all folders and files (app, framework, bin etc...)
I don't know much about compiling or porting ROMs but if you provide more informations I'll try to help.
Post a link pf that zip for Acro S so I can see file structure or...better solution, please post screenshoots of ZIP structure (that one that doesn't have folders)
If you have a ftf file for a base you should repack it using flashtool but this is, obviously, something different.
Still....
Flashtool should be the tool you need.
Post some more informations and we'll find solution together..
Searched google first.
Then asked here, cause last time i posted a nooby question, i was fired with Rude replies...
Unfortunately...you are right...XDA has changed and there's not many users who are ready to help
Click to expand...
Click to collapse
The same developer who's developing for Xperia Acro S is going to develop for Xperia Ion and acro S too!!
http://forum.xda-developers.com/showpost.php?p=56753406&postcount=37
Should we still continue??
arjun921 said:
You're exactly right. But I'm not quite sure how to extract .dat files
The system consists of .dat system files
I've Attached a screenshot of the contents of the zip too
And thanks a ton for atleast trying to help!:good:
Click to expand...
Click to collapse
No problem...that's why we are all here...
I'm using FTK Imager for ext4 files you can try with it maybe...
It's very simple to work with and it'll mount that image so you can extract/work on files and folders you need.
You just have to extract image from zip and mount it with FTK Imager.
File will mount to one separate virtual disk (check screenshoots)
---------- Post added at 03:13 PM ---------- Previous post was at 02:56 PM ----------
arjun921 said:
The same developer who's developing for Xperia Acro S is going to develop for Xperia Ion and acro S too!!
http://forum.xda-developers.com/showpost.php?p=56753406&postcount=37
Should we still continue??
Click to expand...
Click to collapse
Why not?
It's not bad to learn something new..
And you can build your version different, add or remove some apps and features.
Also, it's great if there's recognised developer who will build ROM for those devices.
That way, if you bump into wall you can ask him or check how did he built ROM.
As I said, I'm themer, not developer but I know few things... So if you need anything just tag me here and I'll try to help.
BTW - apparently, you have working kernel built by AOSPXS team, so that's good.
I guess you saw this already but I'll post again.
LINK
You have all sources on github (check that link), why don't you compile ROM from sources?
You'll have same problems like all the others but you'll learn many new things .. Maybe you find a solution for RIL, GPS, wifi...or something else.
funky0308 said:
No problem...that's why we are all here...
I'm using FTK Imager for ext4 files you can try with it maybe...
It's very simple to work with and it'll mount that image so you can extract/work on files and folders you need.
You just have to extract image from zip and mount it with FTK Imager.
File will mount to one separate virtual disk (check screenshoots)
---------- Post added at 03:13 PM ---------- Previous post was at 02:56 PM ----------
Why not?
It's not bad to learn something new..
And you can build your version different, add or remove some apps and features.
Also, it's great if there's recognised developer who will build ROM for those devices.
That way, if you bump into wall you can ask him or check how did he built ROM.
As I said, I'm themer, not developer but I know few things... So if you need anything just tag me here and I'll try to help.
BTW - apparently, you have working kernel built by AOSPXS team, so that's good.
I guess you saw this already but I'll post again.
LINK
You have all sources on github (check that link), why don't you compile ROM from sources?
You'll have same problems like all the others but you'll learn many new things .. Maybe you find a solution for RIL, GPS, wifi...or something else.
Click to expand...
Click to collapse
I'll try that. Mean while, waiting for repositories to get downloaded
Sent from my Xperia ion using XDA Free mobile app
funky0308 said:
No problem...that's why we are all here...
I'm using FTK Imager for ext4 files you can try with it maybe...
It's very simple to work with and it'll mount that image so you can extract/work on files and folders you need.
You just have to extract image from zip and mount it with FTK Imager.
File will mount to one separate virtual disk (check screenshoots)
---------- Post added at 03:13 PM ---------- Previous post was at 02:56 PM ----------
Why not?
It's not bad to learn something new..
And you can build your version different, add or remove some apps and features.
Also, it's great if there's recognised developer who will build ROM for those devices.
That way, if you bump into wall you can ask him or check how did he built ROM.
As I said, I'm themer, not developer but I know few things... So if you need anything just tag me here and I'll try to help.
BTW - apparently, you have working kernel built by AOSPXS team, so that's good.
I guess you saw this already but I'll post again.
LINK
You have all sources on github (check that link), why don't you compile ROM from sources?
You'll have same problems like all the others but you'll learn many new things .. Maybe you find a solution for RIL, GPS, wifi...or something else.
Click to expand...
Click to collapse
And yeah
Most probably gonna stick to building a new ROM from source but after a trial with Acro S rom. The thing is i dont know how to build from source. Though RIL, wireless etc. Might take some time, but at least its better than not sitting hand in hand!
I'll update with how it goes!
Again thanks a tonne for helping out!
Sent from my Xperia ion using XDA Free mobile app
funky0308 said:
No problem...that's why we are all here...
I'm using FTK Imager for ext4 files you can try with it maybe...
It's very simple to work with and it'll mount that image so you can extract/work on files and folders you need.
You just have to extract image from zip and mount it with FTK Imager.
File will mount to one separate virtual disk (check screenshoots)
---------- Post added at 03:13 PM ---------- Previous post was at 02:56 PM ----------
Why not?
It's not bad to learn something new..
And you can build your version different, add or remove some apps and features.
Also, it's great if there's recognised developer who will build ROM for those devices.
That way, if you bump into wall you can ask him or check how did he built ROM.
As I said, I'm themer, not developer but I know few things... So if you need anything just tag me here and I'll try to help.
BTW - apparently, you have working kernel built by AOSPXS team, so that's good.
I guess you saw this already but I'll post again.
LINK
You have all sources on github (check that link), why don't you compile ROM from sources?
You'll have same problems like all the others but you'll learn many new things .. Maybe you find a solution for RIL, GPS, wifi...or something else.
Click to expand...
Click to collapse
@funky0308
Bro,
Repositories still havent finished downloading.
Mean while i managed to build few Lollipop zips based off these guides
http://apcmag.com/port-roms-to-your-android-device.htm
http://forum.xda-developers.com/showthread.php?t=1957219
Anyways, 13 builds later.
I finally managed to get into the boot animation.
But again, its in a bootloop!
How do i know what is wrong with my zip!?
Btw first 5 builds were using the acro s's lollipop zip.
Rest were using Xperia S's lollipop zip
USing Base rom as AOSP 4.4.4 for ion for porting
arjun921 said:
@funky0308
Bro,
Repositories still havent finished downloading.
Mean while i managed to build few Lollipop zips based off these guides
http://apcmag.com/port-roms-to-your-android-device.htm
http://forum.xda-developers.com/showthread.php?t=1957219
Anyways, 13 builds later.
I finally managed to get into the boot animation.
But again, its in a bootloop!
How do i know what is wrong with my zip!?
Btw first 5 builds were using the acro s's lollipop zip.
Rest were using Xperia S's lollipop zip
USing Base rom as AOSP 4.4.4 for ion for porting
Click to expand...
Click to collapse
If it passes kernel logo and stuck/loop on OS bootanimation - you are certain that problem isn't in kernel - that's good... (at least, kernel should be OK)
Try to remove everything except necessary apps for system to boot.
It could be anything...
Driver probably...really don't know...
funky0308 said:
If it passes kernel logo and stuck/loop on OS bootanimation - you are certain that problem isn't in kernel - that's good... (at least, kernel should be OK)
Try to remove everything except necessary apps for system to boot.
It could be anything...
Driver probably...really don't know...
Click to expand...
Click to collapse
For starters the fact that it got past the kernel splash screen was great news! Atleast that's a start!
I'll try removing unnecessary apps.
Mean while, I might have another theory. Kitkat by default runs on Dalvik. Lollipop runs on ART.
Could that be a reason, why it isn't booting up?
Any idea which are the folders that house the drivers in kitkat and lollipop?
arjun921 said:
@funky0308
Bro,
Repositories still havent finished downloading.
Mean while i managed to build few Lollipop zips based off these guides
http://apcmag.com/port-roms-to-your-android-device.htm
http://forum.xda-developers.com/showthread.php?t=1957219
Anyways, 13 builds later.
I finally managed to get into the boot animation.
But again, its in a bootloop!
How do i know what is wrong with my zip!?
Btw first 5 builds were using the acro s's lollipop zip.
Rest were using Xperia S's lollipop zip
USing Base rom as AOSP 4.4.4 for ion for porting
Click to expand...
Click to collapse
That is the problem. You are using 4.4.4 ROM as a base ROM. You have to use same android version to cross port. Otherwise it won't work.
You need a Lollipop kernel and a system to do that.
Hi guys, long time no post. I have updated this guide on how to build kernels for Falcon so that anyone can learn! It's pretty simple once you get the hang of it. So yeah, here we go!
Prerequisites:
- You must have a Linux firmware running on your computer (I suggest Builduntu because you can skip the next one [build environment setup])
- Build environment setup (Put the this in terminal and follow instructions)
- Patience and a heart willing to learn
- You need to know the languages C, C++, Java, Ruby, Python... NOT! You don't need to know ANY coding languages.
[MOTIVATIONAL SPEECH]
Truth be told, when I first started out developing, I knew NO coding languages except for HTML and a little bit of Java. Both have nothing to do with kernels! I actually learned how to do this when I suffered from a concussion. So if you really want to learn how to kernel dev and you give up halfway, just know that a 14/15 year old kid could do it..
[/MOTIVATIONAL SPEECH]
Click to expand...
Click to collapse
WARNING: I am not responsible for any damages to your phone or computer or pet unicorn. When you modify the wrong partitions, set too many jobs for your compiler, break your keyboard out of frustration etc., that is not anyone's fault but yours. Or your pet unicorn.
Your Personal Handbook to the Following:
- Anything inside "CODE" boxes, type it into your terminal. If you can't find terminal, then press CTRL, ALT, t.
- If I were you, I would write these by hand instead of copying and pasting it because after a certain amount of times, you will remember the linux commands and it will be easier for you to compile more kernels for different devices
- Use this thread as a "Help Me" button. Ask for help!
Click to expand...
Click to collapse
A New Beginning:
Let's start out with something simple, getting the actual code:
Code:
git clone https://github.com/cyanogenmod/android_kernel_motorola_msm8226
This could range from 3 minutes to 2 hours!
Once that's done, open up your file manager and rename the folder (should be android_kernel_motorola_msm8226) to whatever you want. I will refer it as "mykernel".
Click to expand...
Click to collapse
Pokemon!
For this tutorial, we will be using a Sabermod 4.7 toolchain to compile. I WOULD teach you how to compile with 4.8+, but it creates errors that will take even longer for me to write about sooooooooo :fingers-crossed:. Now to get the toolchain:
Code:
git clone https://github.com/SaberMod/android_prebuilts_gcc_linux-x86_arm_sabermod-arm-eabi-4.7
Rename this to whatever you like, but I will be referring this as "toolchain"
Now go into you folder where the kernel source is stored...
Code:
cd mykernel
Click to expand...
Click to collapse
You're Almost There!:
Time to set-up the compiler!
Code:
export CROSS_COMPILE=/home/(insert linux home name here)/toolchain/bin/arm-eabi-
This tells the toolchain that "OK, we want to make ALL this code here into a kernel".
This next line tells it that your defconfig (the toolchain's manual for compiling the kernel) that it's in the arch/arm/configs folder.
Code:
export ARCH=arm
Now to tell the it what the defconfig is!
Code:
make falcon_defconfig
Hehe, now to the hardest part of all...
MuHAHHAHAHa
Click to expand...
Click to collapse
THE HARD (coding) PART
You ready for this? HERE IT IS! TIME TO BUILD THE KERNEL!
Code:
make -j4
Now sit back, relax, and watch the code! Or you could read a book, watch ****, count your fingers, play with your toes...
If you have an error during the waterfall of code, find the part where it actually says *error* (you'll probably have to scroll upwards) and search it on Google or post it here.
Click to expand...
Click to collapse
THE BEST PART
If you manage to get something that says "the kernel zImage is ready" or something like that, that means you've made it!
You have officially compiled your own kernel from source! Now you need to put it in a flashable zip.
Download this file and open it up, but DON'T EXTRACT IT.
Now go to your kernel source then "CTRL + F" and search for "zimage-dtb".
Find it and put it in the "kernel" folder of "FalconKernel - Signed.zip". Then "CTRL + F" and search ".ko".
Copy radio-iris-transport.ko and put it in the system/lib/modules (not pronto) of the zip.
Then find wlan.ko and rename it to pronto_wlan.ko. Copy and paste it in system/lib/modules/pronto of the zip.
Click to expand...
Click to collapse
Now you can put it on your phone and flash it!
I will update this in a bit. What feature would you guys want in your kernel? The most votes in the POLL above will be the one I teach you here!
Here I will walk you through on how to add the intelliplug feature made by @faux123
First, fetch my Green Machine kernel source (go into your kernel folder in terminal):
Code:
git fetch https://github.com/YoshiShaPow/green_machine_falcon
Then you could cherry-pick (basically copy) all my cherry picks for intelliplug from my source.
If you do check my source out, you can see there's a little link to a history of commits near the middle of the screen, right above the files/folders. You can see at this page of my features history, you'll see a bunch of commits for intelliplug. I will use those commits and copy it to your own kernel.
This copies the initial coding/first commit of intelliplug!
Code:
git cherry-pick 01a850f
This cherry-picks the remaining commits so that your newly added intelliplug is updated.
Code:
git cherry-pick 6623f2f^..4e1ece7
One more thing though, you need to add the line to compile intelliplug!
Almost all things compiled along with the zImage are in a file called defconfig. What a defconfig does, is tell your machine to build certain modules, kernel objects, drivers, governors, etc.etc.etc.. Now, all of them are found in the folder
arch/arm/configs
Click to expand...
Click to collapse
As stated in the OP, you have to modify the defconfig you use. (CM11 Kernel is falcon_defconfig, Gummy Kernel is msm8226_mmi_defconfig). Open up the corresponding defconfig and add this to ANY line anywhere.
Code:
CONFIG_INTELLI_PLUG=m
Now, for those who are familiar with "y=yes/n=no/m=maybe", you'll see that I specifically told you to put the "m=maybe" one. That's because when you compile the kernel again, right after you're about to start your build. Since you put that "m", the terminal will prompt you with a "y=yes/n=no" question on whether or not you would like to add the following feature. Since you would like to add the feature, put in "y". Later on when you feel more comfortable with adding features to your kernel, you can go back into the defconfig and put it as
Code:
CONFIG_INTELLI_PLUG=y
So that it will compile it without asking, since you have given it an answer.
Now you have officially compiled a "Custom Kernel" and with the knowledge you know, you could create a feature packed one by just kanging (copying one's work/features).
Always remember to
Code:
make clean && make mrproper
after every build to prevent errors and such!
Click to expand...
Click to collapse
I will use this to teach you how to make your own Bash Building scripts (and save time) to make it easier for your development life to flourish... eventually....
Any guide on adding governors or hotplug driver??
Sent from my Moto G using XDA Free mobile app
Best guide but how to add features likes s2w,dt2w etc
Flashhhh said:
Any guide on adding governors or hotplug driver??
Sent from my Moto G using XDA Free mobile app
Click to expand...
Click to collapse
Vote in the poll above! I will make a guide for one or more of the top chosen picks!
Brawn_Sg said:
Best guide but how to add features likes s2w,dt2w etc
Click to expand...
Click to collapse
DT2W and S2W are more complex. They require a few other things (ex. Powersuspend). I'll wait a bit and see what feedback I get before moving forward to something a bit more complex like DT2W, or GPU Overclock.
Can i use make menuconfig?
Krizthian said:
Can i use make menuconfig?
Click to expand...
Click to collapse
Yes you can. Normally when using "make menuconfig", you use the command after making the kernel's defconfig (falcon_defconfig).
Build using Docker
If you're on Linux, take a look at this approach which uses Docker for building CyanogenMod 12.0:
http://forum.xda-developers.com/showthread.php?t=2650345
(Disclaimer: It's written by me)
YoshiShaPow said:
Hi guys, long time no post. I have updated this guide on how to build kernels for Falcon so that anyone can learn! It's pretty simple once you get the hang of it. So yeah, here we go!
WARNING: I am not responsible for any damages to your phone or computer or pet unicorn. When you modify the wrong partitions, set too many jobs for your compiler, break your keyboard out of frustration etc., that is not anyone's fault but yours. Or your pet unicorn.
Now you can put it on your phone and flash it!
Click to expand...
Click to collapse
when i was trying to flash cm12 rom in cwm recovery it says error in zip and getting status 1 error , installation aborted ,
pls help im using moto g gpe and when trying to flash from twrp it says error executing updater binary in zip ,
no idea what to do pls help me out
karthik432 said:
when i was trying to flash cm12 rom in cwm recovery it says error in zip and getting status 1 error , installation aborted ,
pls help im using moto g gpe and when trying to flash from twrp it says error executing updater binary in zip ,
no idea what to do pls help me out
Click to expand...
Click to collapse
When you downloaded the anykernel zip, you aren't supposed to extract it. The best way to put the kernel in the zip is to just drag and drop it while IN LINUX. It will not work for windows! Or you could try signing the zip in TWRP (I think there's an option for that somewhere).
YoshiShaPow said:
When you downloaded the anykernel zip, you aren't supposed to extract it. The best way to put the kernel in the zip is to just drag and drop it while IN LINUX. It will not work for windows! Or you could try signing the zip in TWRP (I think there's an option for that somewhere).
Click to expand...
Click to collapse
im not extracting anything , i just downloaded the official cm12 nightly and flashed but didn't workout ,any ideas
karthik432 said:
im not extracting anything , i just downloaded the official cm12 nightly and flashed but didn't workout ,any ideas
Click to expand...
Click to collapse
That has nothing to do with this thread :silly:. You probably have to sign the zip again.
@YoshiShaPow.... i need some help
i compile a kernel for my device and it booted fine but no display....
can you help me in this....
sorry for posting here..my device is Redmi 1s
Luffy.d said:
@YoshiShaPow.... i need some help
i compile a kernel for my device and it booted fine but no display....
can you help me in this....
sorry for posting here..my device is Redmi 1s
Click to expand...
Click to collapse
No problem, I welcome anyone with kernel development questions here! When booted, what do you mean? And if there's no display, how do you know it booted? Also, did you use my anykernel zip? I may be wrong but I don't think it is compatible with all phones.
YoshiShaPow said:
No problem, I welcome anyone with kernel development questions here! When booted, what do you mean? And if there's no display, how do you know it booted? Also, did you use my anykernel zip? I may be wrong but I don't think it is compatible with all phones.
Click to expand...
Click to collapse
yeah it booted bro....i can hear lock unlock sound and even i can hear incoming call ring
i was trying to fix this from a week and found out it not kernel it rom problem ...
my device is build using prebuilt kernel so any compile kernel wont work...but now they are build with this kernel source so compile kernel work
thanks bro...
and one thing bro... i m new to kernel development so how can i optimize kernel
i know about and can add governors and use custom toolchain but i don't know about o2 or o3 optimization etc and all
sorry if i m being too much
great I start today
Luffy.d said:
yeah it booted bro....i can hear lock unlock sound and even i can hear incoming call ring
i was trying to fix this from a week and found out it not kernel it rom problem ...
my device is build using prebuilt kernel so any compile kernel wont work...but now they are build with this kernel source so compile kernel work
thanks bro...
and one thing bro... i m new to kernel development so how can i optimize kernel
i know about and can add governors and use custom toolchain but i don't know about o2 or o3 optimization etc and all
sorry if i m being too much
Click to expand...
Click to collapse
Those changes are a bit more advanced because it will bring build errors. The kernel is already preoptimized with o2 changes. The errors are fixable though. I don't think I'll be able to add an explanation for those in this thread, maybe through pm?
YoshiShaPow said:
Those changes are a bit more advanced because it will bring build errors. The kernel is already preoptimized with o2 changes. The errors are fixable though. I don't think I'll be able to add an explanation for those in this thread, maybe through pm?
Click to expand...
Click to collapse
thanks bro...will pm you when i finish setuping my git
etvtaglios said:
great I start today
Click to expand...
Click to collapse
Go for it bro!!
I came across CM12.1 rom for Lenovo K3 Note on needrom. Considering that K3 have the same chipset as ours, I've been thinking that it can be ported to our device.
I've tried to port it past few days but failed. Any developer would come up and try to port it?
What have you done? Device tree something else?
Nope. Just changing libs here and there, according to this guide. I'm still noob in porting roms so I can't do much.
amirarsyad97 said:
I came across CM12.1 rom for Lenovo K3 Note on needrom. Considering that K3 have the same chipset as ours, I've been thinking that it can be ported to our device.
I've tried to port it past few days but failed. Any developer would come up and try to port it?
Click to expand...
Click to collapse
Did you edit the updater script?
Gibz97 said:
Did you edit the updater script?
Click to expand...
Click to collapse
Yes. I'm actually having problem in repacking system.new.dat files. The same as the guy face here. Finding the solution require me to learn Linux. I'm still new at Linux, so I need some time to learn.
Other than that is okay (perhaps). I followed some other guides like http://forum.xda-developers.com/android/development/guide-how-to-port-lollipop-based-roms-t3223938 and http://forum.xda-developers.com/showthread.php?t=2707438.
Oh and one more thing, the rom is ported by @Cheshkin. I've tried to seek his permission to port the rom through pm, but still no answer. So I cannot post the rom here (if I done porting it) without his permission.
amirarsyad97 said:
Yes. I'm actually having problem in repacking system.new.dat files. The same as the guy face here. Finding the solution require me to learn Linux. I'm still new at Linux, so I need some time to learn.
Other than that is okay (perhaps). I followed some other guides like http://forum.xda-developers.com/android/development/guide-how-to-port-lollipop-based-roms-t3223938 and http://forum.xda-developers.com/showthread.php?t=2707438.
Oh and one more thing, the rom is ported by @Cheshkin. I've tried to seek his permission to port the rom through pm, but still no answer. So I cannot post the rom here (if I done porting it) without his permission.
Click to expand...
Click to collapse
If you have an idea for kernel, I'll help you
amirarsyad97 said:
Yes. I'm actually having problem in repacking system.new.dat files. The same as the guy face here. Finding the solution require me to learn Linux. I'm still new at Linux, so I need some time to learn.
Other than that is okay (perhaps). I followed some other guides like http://forum.xda-developers.com/android/development/guide-how-to-port-lollipop-based-roms-t3223938 and http://forum.xda-developers.com/showthread.php?t=2707438.
Oh and one more thing, the rom is ported by @Cheshkin. I've tried to seek his permission to port the rom through pm, but still no answer. So I cannot post the rom here (if I done porting it) without his permission.
Click to expand...
Click to collapse
Let's wait for the response then
Would be graet to see CM to release this device's potential. Especially since HTC is taking it's sweet time with 6.0 update and 5.1 was officially skipped.
Anyway if you would need some testers I would gladly help.
Good news! The permission has been granted. I will try my best to port this rom.
And what with 820n?
Sent from my HTC Desire 820 using XDA Free mobile app
Dragonfail said:
And what with 820n?
Sent from my HTC Desire 820 using XDA Free mobile app
Click to expand...
Click to collapse
We don't have 64-bit kernel sources for 820n MSM chipset
Hi @amirarsyad97, so did you manage to extract system files?
Gibz97 said:
Hi @amirarsyad97, so did you manage to extract system files?
Click to expand...
Click to collapse
I already did, but I can't repack it. So instead I tried looking for other roms while staying away from dat files - cm12.1 ulefone be touch 2 and blisspop k3 note.
Now I'm having problems with the kernel. The rom won't boot at all, the worse I can't get the dmesg.
I don't have much free time to explore kernels in detail. If anybody can help me with porting the kernel, it would be a pleasure.
amirarsyad97 said:
I already did, but I can't repack it. So instead I tried looking for other roms while staying away from dat files - cm12.1 ulefone be touch 2 and blisspop k3 note.
Now I'm having problems with the kernel. The rom won't boot at all, the worse I can't get the dmesg.
I don't have much free time to explore kernels in detail. If anybody can help me with porting the kernel, it would be a pleasure.
Click to expand...
Click to collapse
I will try porting the kernel using the kitkat kernel as base when I find time
Unfortunately, I did not succeed, I could not even get into the bootanimation. Hope someone can help us.
I am now trying to squeeze the Lollipop system partition so that we can liberate some more free space for the internal storage, hope it works
That would be the coolest thing???
Hello guys hope you have been doing great, Was too busy with school, exams and stuff.
Good news!! I have finally managed to boot into CM 12.1 after I successfully ported it today.
It's lightning fast but has some bugs: USB, bluetooth and Sim don't work currently and it needs some resizing of the framework images.
I will try to work on it until Sunday and hopefully someone else can take over with modifying it
Gibz97 said:
Hello guys hope you have been doing great, Was too busy with school, exams and stuff.
Good news!! I have finally managed to boot into CM 12.1 after I successfully ported it today.
It's lightning fast but has some bugs: USB, bluetooth and Sim don't work currently and it needs some resizing of the framework images.
I will try to work on it until Sunday and hopefully someone else can take over with modifying it
Click to expand...
Click to collapse
I was wondering how you can make the kernel work. Anyway good work!
amirarsyad97 said:
I was wondering how you can make the kernel work. Anyway good work!
Click to expand...
Click to collapse
Use this kernel and build.prop and use the original system (don't replace with stock files) https://mega.nz/#!c4USzSTL!rXmsjMYaxR9ECwNeiMjissLPuFRLBWBUSLIuwiBFwQk
Almost everything works right now except Bluetooth, camera and Sim
Great work keep it up
Sent from my HTC Desire 820 dual sim using XDA-Developers mobile app