Database Users

Championswimmer's Ultimate HOW-TO

after numerous requests here we go!!!
no it's not complete yet, just starting...
firstly i'll just link up all threads from where i took collected my info, and then i'll start wiriting my how-to
it'll take time as my school and entrance exams are main priority at the moment but i'll do it in bits and pieces and i'll manage to pull it off before you x10 dies off .. ha ha ha
==========================================================================================================
SIMPLE GUIDE TO COMPILE KERNEL FOR X10i/X10a
=====================================================================================================
COMPILE AOKP FOR ANY XPERIA PHONE
=====================================================================================================
REFERENCE TO COMPILE AOSP/AOKP/CM7/CM9 FOR X10i/X10a
==========================================================================================================
firstly credits : >
1. DoomLord -> whose tools and info thread are just awesome
2. Zdzihu -> the biggest ever dev for x10 and for doing impossible feats
3. Freexperia Team -> for supporting this device for 2 years
4. Spaarc -> for his guide and his vast knowledge (guys!! this dude is 1 yr younger than me!!)
5. Azuzu -> for his awesome windows based tools
6. Androxyde -> flashtool and awesome shell scripts
7. Colossus -> for being the best mod ever !!! (yes i mean it buddy) and for guiding me a lot
8. Sahibunlimited -> for being me buddy and a really good friend to everybody here
9. GregBradley -> for being having the most useful signature in xda (and having helped me out when i was a noob)
10. LzVebz -> Pestering me to write this
phew!!! hope that's all?? more left?? please pm me, i'lll add you
EDIT
11. pvyParts -> for showing how to work on apk files
12. iridaki -> for being helpful and encouraging and pepping me up for all the good work i did and mostly for being an elder sister
13. ~Pilot~ -> for keeping xda clean
14. TAL333 -> for standing by me and believing in me

So firstly the threads that I read and YOU SHOULD PLEASE GO THOUGH ONCE before reading my Howto
spaarc's porting guide
doom's guide 1
doom's guide 2
doom's guide 3
doom's all in one info thread
doom's kernel.sin and ftf creator
doom's kernel.sin unpacker
dsixda kitchen (for "cooking" roms)
using android kitchen for xperia devices
http://forum.xda-developers.com/showthread.php?p=12875

Ok so as they say "safety first"
Let me give you your CRASH HELMET
It is said that x10 is UNBRICKABLE, though that is true but not hard and fast rule. Jerpelea and Doomlord have bricked x10 devices before and it's not all that impossible. Still, if you keep care of following things, you'll never brick your phone
1. NEVER DISCONNECT USB CABLE while flashing/bootloader unlocking/pccompanion upgrade is going on
2. Be extremely careful while using the_laser or 9Lukas5's unlock procedure. It changes device partition and mapper modules so they are delicate ares and can brick your device if procedure is not followed
3. DO NOT PANIC, THINGS CAN BE SET RIGHT. BE CALM, BE PATIENT, ASK FOR HELP AT XDA
=======================================================================================================================
Ok so, there can be bad flashes or whatever..... what to do if device does not boot up??
1. If the problem is about RED flashing led, then just plug your phone into a charger and wait over night it's a low charge problem. Once charged, all will be ok
2. If you face boot loop and you just do not know what to do (i.e. you cannot go to recovery too) then do this
a.) either download PC companion and update/upgrade your phone
OR
b.) download latest flashtool and flash a 2.1 for 2.3.3 firmware (that you get in .ftf format) that will set you on track

ok so to tell a few things first....
please do not pm me.regarding this.
ask any questions here.
i or any other member would definitely help
and dont get impatient.... I'm busy...so it'll take time to complete the guide
Sent from my X10S using xda premium

Finally it's here!!! Thanks man, I've been waiting for this

LzVebz said:
Finally it's here!!! Thanks man, I've been waiting for this
Click to expand...
Click to collapse
I've not yet started....feeling too lazy...but dont worry...in a week or two it'll be complete
Sent from my X10S using xda premium

Alright pretty dumb question feel free to shoot me. If I take an system ui apk and framework apk from say arc and just change it with my existing system ui n framework will I be getting the same theme of Sony arc.
Sent from my X10S using XDA

stanzzzzz said:
Alright pretty dumb question feel free to shoot me. If I take an system ui apk and framework apk from say arc and just change it with my existing system ui n framework will I be getting the same theme of Sony arc.
Sent from my X10S using XDA
Click to expand...
Click to collapse
maybe yes with systemui
DEFINITELY NOT with framework.
the framework res is not just the ui.
it defined the whole Android system...
it just cannot be ported like that....lol
@everyone
i won't shoot if you ask dumb questions.
you can ask dumb questions if you wish to.
that's the way we learn
Sent from my X10S using xda premium

Really happy to see someone doing this, thanks CS, may I suggest adding dooms guide to create update/amend scripts? I am sure you'll get to it! Best if luck with your exams too.
Sent from my X10i using XDA

[email protected] said:
Really happy to see someone doing this, thanks CS, may I suggest adding dooms guide to create update/amend scripts? I am sure you'll get to it! Best if luck with your exams too.
Sent from my X10i using XDA
Click to expand...
Click to collapse
never heard of that guide
I'll search and see....
i learnt amend and edify on my own by looking through various zip files....ha ha ha.
btw the dsixda kitchen makes edify/amend scripts automatically
Sent from my X10S using xda premium

championswimmer said:
maybe yes with systemui
@everyone
i won't shoot if you ask dumb questions.
you can ask dumb questions if you wish to.
that's the way we learn
Sent from my X10S using xda premium
Click to expand...
Click to collapse
Excellent! In which case, can you answer this question?
http://forum.xda-developers.com/showthread.php?t=1574805

blueowl0708 said:
Excellent! In which case, can you answer this question?
http://forum.xda-developers.com/showthread.php?t=1574805
Click to expand...
Click to collapse
decompile settings.apk and go through the xml files you get and play around with them a little....
Sent from my X10S using xda premium

this one

Ok, so lets get to our stuff fast
Her we begin with some info about how a ROM works
when cooking/porting roms, you are concerned with only a few folders
download any randon ROM zip and unzip it and see what it contains
1. /system/app -> this folder contains all apk files of apps
2. /system/framework -> this folder contains lots of .jar files that defines how the base operating system will run and function
3. /system/lib -> lots of .so files that are like drivers (yep .dll files in windows), these specify how the software communicates with various hardware components
4. /system/etc -> very dangerous folder contains lots of important configurations
5. /system/etc/permissions -> these contain lots of xml files that are required to define how the .jar files in framwork folder will work
ok so i'll elaborate point 2 and 5 a little more taking example of the panorama beta app by SE. it requires the com.sonyericsson.android.seee.jar file in framework folder to work but if you just keep the jar file, it'll not work. you need to sort out its permissions too and for that you need to put com.sonyericsson.android.seee.xml file in permissions folder
Click to expand...
Click to collapse
also the etc folder contains two some files called
gps.conf (which defines which gps server the device will use)
hosts (this defines which websites will be blocked .... yes that is your adblocker file )
apns.xml (which defines your apn configuration)
screwing up these files can cause you internet/gps/data traffic problems. also intelligent editing of these fils can give you better gps/data too
Click to expand...
Click to collapse

hey champ!
First I'd like to thank you very much for this nice guide and for your kernel. With latter u saved my ass. Was on Doom's with FeraLab and phone reboots sometimes Now it's flying!!!
But I'm fan of good design. And please don't hit me, but I'd like to change the boot-logo of your kernel is there any way? Or do u have any nice guide to change logo?
Would be awesome!!!

Question
Hi champ,
Does THIS also work for X10?

LzVebz said:
Hi champ,
Does THIS also work for X10?
Click to expand...
Click to collapse
not precisely.
for the perfect repacking script, see www.github.com/championswimmer/kCernel-goro
inside build-bootimg folder
Sent from my X10S using xda premium

championswimmer said:
not precisely.
for the perfect repacking script, see www.github.com/championswimmer/kCernel-goro
inside build-bootimg folder
Sent from my X10S using xda premium
Click to expand...
Click to collapse
Thanks!
I've one question left I think
I'm currently on Windows 7 ultimate, and I have 1 TB left on drive D (which is empty) My question is.. Is there a way to Dual-boot Windows & ubuntu without wubi?
Thank u very much again

Compiling kernel
So letme tell you how a kernel for x10 can be compiled
1. install ubuntu (through wubi or in vmware will also do) but i prefer on a separate partition.
2. Install the following packages
git-core gnupg sun-java6-jdk flex bison gperf libsdl-dev libesd0-dev libwxgtk2.6-dev build-essential zip curl libncurses5-dev zlib1g-dev
here's how you go about doing it
Code:
sudo apt-get install git-core gnupg flex bison gperf libsdl-dev libesd0-dev libwxgtk2.6-dev build-essential zip curl libncurses5-dev zlib1g-dev
sun-java6-sdk is no more officially available through ubuntu repositories
so you will need a workaround.... so here are some helpful articles
http://www.gaggl.com/2011/10/installing-java6-jdk-on-ubuntu-11-10/
http://superuser.com/questions/353983/how-do-i-install-the-sun-java-sdk-in-ubuntu-11-10-oneric
http://softwareinabottle.wordpress.com/2011/11/17/install-sun-jdk-6-on-ubuntu-11-10/
In case you are on a 64-bit version of ubuntu, (btw i strongly recommend using a 32 bit version for android development as you'll face various problems with 64-bit at various stages) you'll need these packages too
ia32-libs lib32z1-dev lib32ncurses5-dev gcc-multilib g++-multilib​
3. Next you'll need a cross-compiler.
a cross compiler is used to compile for a different architecture than from the one you are currently working on. in this case you are either on a i686 or amd64 pc while the kernel you are compiling is for an ARMv7 processor.
for ubuntu, getting the Linaro GCC cross compiler for arm is getting as easy as
Code:
sudo apt-get install gcc-arm-linux-gnueabi
4. Now you are pretty much set up to compile kernels. Next we need sources.
So let me link you up to the most common available ones
Sony Ericcsoon Official Kernel Sources for 3.0.1.G.0.75 (gingerbread firmware)
Sony Ericsson Official Kernel Sources for Eclair Firmware
FreeXperia Kernel For ICS
FreeXperia Kernel for GingerBread
DoomKernel (this is my forked repo)
*** i'll update this list later (there are dozens of kernels for x10, all have their sources, i guess for now, this is enough)
5. So the source you have downloaded will be either a tar or zip archive. Using archiver, extract it into a directory of your liking.
6. Open terminal and 'cd' into the kernel directory. The kernel directory is the one which contains the folders arch, block, crypto, firmware, drivers .....
for compiling kernel you need to be in the root of this direcrory.
7. So here are a few codes that will get your kernel compiled
To clean source directory : -
Code:
ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- make clean
ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- make distclean
To get default configuration
Code:
ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- make semc_es209ra_defconfig
if you are compiling FXP kernel then instead of semc_es209ra_defconfig you need to write fxp_es209ra_defconfig , and likewise for DoomKernel you need to use doom_x10_defconfig
To configure the kernel
Code:
ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- make menuconfig
inside general setup you can name your kernel
and inside power management setup you can setup which CPU governors will be present and which will be default
do not mess to much with the driver setups or with "kernel hacking" area....
do not touch things that you have no idea about
Finally... to compile the kernel
Code:
ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- make
If all goes well, you'll get this message
Kernel: arch/arm/boot/Image is ready
Kernel: arch/arm/boot/zImage is ready
If you get stuck in between, nothing to fret about. Just post here what problem you faced, amd me or some other helpful soul will help you out
8. I know you are thinking "whew!! are we done??"... ha ha ha!! no buddy!! not yet... much more work to do.
Firstly from you kernel directory go to arch/arm/boot (using a file explorer, not a terminal) and inside you'll find a 2~3 MB sized file called zImage. Copy that file into a separate folder where you'll stach all your finished works.
9. Now we need to compile the wifi modules.
It is imperative to note here that wifi modules should be compiled immediately after kernel has been compiled. DO NOT run "make clean" or "make distclean" commands in the kernel folder before wifi modules have been compiled
Click to expand...
Click to collapse
For compiling wifi, you'll need the "vendor" folder (which is there in official sony kernel sources but not present in Doom's or FXP's repo). So if you need just the vendor folder, you'll HAVE TO download the official kernel sources too.
in terminal 'cd' to vendor/atheros/wlan/host/ folder
edit the localmake.linux.inc file using a text editor
Code:
sudo gedit localmake.linux.inc
edit the line ATH_CROSS_COMPILE_TYPE := arm-eabi- to ATH_CROSS_COMPILE_TYPE := arm-linux-gnueabi-
also in the line
# ATH_LINUXPATH := < kernel source path >
remove the # (uncomment it) and insert the appropriate kernel source path (the folder that contains arch, crypto, firmware, drivers etc folders.
now to compile wifi modules, run this code
Code:
ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- KERNEL_DIR=/path/to/kernel make
of course, in place of "/path/to/kernel" type the actual path to kernel on your pc
this will get your wifi module compiled
go to the folder
vendor/atheros/wlan/host/.output/QUALCOMM_ARM_NATIVEMMC_BSP_REV=3240-SDIO/image/
and you'll find a file ar6000.ko
transfer that file to the place where you kept your zImage safely earlier.
10. PHew!! done?? ha ha .. no dude.. still not...more work left
now to pack things up, you'll need a ramdisk.
so lets steal a ramdisk from a already working kernel (for stock kernel take stock ramdisk, for cm7/cm9 take respective ramdisk)
take any kernel and unpack it using instructions given here
the file ending with xyz.cpio.gz is the ramdisk. rename the file into "ramdisk" (without any extension) and put this file into the folder where you kept your zImage and wifi module.
Now transfer all these three files into a folder which is accessible from your Windows partition (oops... yeah... without windows you cannot finish this job)
Rest of the steps that follow are to be done on Windows (i have not tried on WINE)
rename zImage to "image"
now using this tool (courtesy DoomLord) pack your ramdisk and image into a flashable .ftf file
also make a copy of the file ar6000.ko and name it wifi.ko
both these ar6000.ko and wifi.ko files are supposed to be in the folder /system/lib/module of your mobile (please create appropriate flashable zip for the same)
===============================================================================================================
If you found this Guide helpful, please remember to press the thanks button ;P
================================================================================================================

LzVebz said:
Thanks!
I've one question left I think
I'm currently on Windows 7 ultimate, and I have 1 TB left on drive D (which is empty) My question is.. Is there a way to Dual-boot Windows & ubuntu without wubi?
Thank u very much again
Click to expand...
Click to collapse
send me a screenshot of you disk manager (start->computer management -> disk management)
then i'll tell you how you can set it up easily

[DISCUSSION][DEV] TWRP for X8

Okay guys. So over the past few days I've tried to compile KXP (AOKP for X8, if you didn't know) and failed.....thrice. The main aim behind this was to get
a) AOKP m6 for X8
b) TWRP running on our device
Now a) is still resulting in failures but b)....well, let's just say it can still be worked on. So this is what I've done so far:
I compiled a CWM version (without compiling KXP) just to get the environment ready for building TWRP. Next I edited the BoardConfig.mk to include these lines under a heading of #twrp like this
#twrp
DEVICE_RESOLUTION := 320x480 (the device resolution)
RECOVERY_GRAPHICS_USE_LINELENGTH := true (this line is supposed to improve graphics on some devices)
TW_NO_BATT_PERCENT := true (this line prevents battery percentage display in the recovery GUI)
TW_NO_REBOOT_BOOTLOADER := true (self-explanatory; we can't reboot into bootloader, can we?)
TW_NO_REBOOT_RECOVERY := true (this option never worked for me and so I removed it)
I sent the binary (obtained by typing make -j# recovery after copying the TWRP repo to the bootable/recovery directory) to feherneoh (the dualboot dude) and asked him to use it in a kernel, changing nothing else but the recovery binary. He said the phone didn't even boot.
Now I've noticed there are a couple of other libs and files built with TWRP. And also there's another recovery binary in /out/target/product/shakira/symbol/system/bin.
What I'm trying to do is compile a kernel with this binary. So far feherneoh's failed. And I'm pretty sure there's something else that needs to be done. I know about the recovery GUI images; I will place them in the res folder and try again but I'm pretty sure it will fail.
So i'm asking experienced X8-ians to help me out, especially devs like Daveee10, Rohin, nAa, alfsamsung, djnilse....the list doesn't end.
Looking forward to replies.

This is what lead dev of TWRP, Dees_Troy had to say:
Re: Compiling TWRP for X8
Originally Posted by sgt. meow
Dear Sir,
I have started a TWRP-porting project for the X8. I have compiled the binary (make -j# recovery) using the following flags:
#twrp
DEVICE_RESOLUTION := 320x480
RECOVERY_GRAPHICS_USE_LINELENGTH := true
TW_NO_BATT_PERCENT := true
TW_NO_REBOOT_BOOTLOADER := true
TW_NO_REBOOT_RECOVERY := true
I haven't tested it myself. However I sent a fellow member (with experience in this field) the binary (from /out/target/product/shakira/system/bin) and asked him to integrate it with a working kernel, changing nothing else but the recovery binary. He said the phone didn't boot up. I believe the images from the /bootable/recovery/gui/devices/320x480/res/images have to be placed in the kernel too, in order to get it working. I am very new to this and would greatly appreciate if you helped me with the following:
What files are related to the TWRP recovery?
What has to be done to integrate it with a kernel?
What files need to be edited?
Do the libs built along with TWRP need to be installed on the phone?
Thanking you and the rest of Team WIN in advance
sgt. meow
Click to expand...
Click to collapse
Generally speaking, the actual recovery files would be in out/target/product/shakira/recovery/root. What you have to have for integrating into your kernel build will depend a little bit on how your kernel ramdisk(s) are packed. You'll need, at the very least, the etc (for the recovery.fstab), sbin (binaries and libs), and the res (theme and zip signature keys) folders. Recovery usually gets its own init.rc so you'll have to do whatever you need to do to get the recovery/root/init.rc integrated into your kernel or at the very least, modify an exising init.rc so that recovery gets the LD_LIBRARY_PATH value as covered in the guide.

Here's the link to a zip I uploaded: http://www.mediafire.com/?ad374fp01274e3z
It contains the output files when TWRP is compiled as a binary (in the "TWRP(binary files)" folder) and the ramdisk-recovery.cpio when TWRP is compiled as an image by issuing make -j# recoveryimag (in the "TWRP(image files)" folder).
Note: The binary didn't build the res images. They had to be taken from the gui folder of the bootable/recovery directory. However the images were there when TWRP was compiled as an image in the ramdisk-recovery.cpio.
Note 2: This is compiled using jb-wip branch. The first binary and image was compiled using master branch. I later found out that I was supposed to use the jb-wip branch instead of the master branch.

Well you should make it to compile with rom together. When its built then u will get "ramdisk-recovery.img" or zip... inside this one you will have all needed binaries and images. Then just open kernel ramdisk and replace those binaries. There are lot more needed binaries than just "recovery".
But first you must compile everything
Sent from my mind using fingers

You mean like make -j# recoveryimage.

sgt. meow said:
You mean like make -j# recoveryimage.
Click to expand...
Click to collapse
Try with brunch
Sent from my X8 using xda app-developers app

Problem with brunch is I run into some errors while compiling the ROM (which stop the building) so I won't get any end product. I tried recoveryimage and got a lot of ramdisk-***.img's and cpio's and what-nots.

sgt. meow said:
Problem with brunch is I run into some errors while compiling the ROM (which stop the building) so I won't get any end product. I tried recoveryimage and got a lot of ramdisk-***.img's and cpio's and what-nots.
Click to expand...
Click to collapse
Thats good too now extract ramdisk-recovery.img if you have it
Sent from my X8 using xda app-developers app

sgt. meow said:
Problem with brunch is I run into some errors while compiling the ROM (which stop the building) so I won't get any end product. I tried recoveryimage and got a lot of ramdisk-***.img's and cpio's and what-nots.
Click to expand...
Click to collapse
The brunch not help Tried a lot of variant (compile only the recovery/compile with rom/millions of different settings/etc...) The phone start the recovery, but not work (the best result is only a flickering image). Earlier I consulted with Daveee10, but he have same results.

I couldn't extract ramdisk-recovery.img but I extracted ramdisk-recovery.cpio and I get a lot of files in the sbin directory like recovery, sdparted, fix_permissions.sh, adbd and a lot of libs. In the etc directory there is a recovery.fstab.

pilu1978 said:
The brunch not help Tried a lot of variant (compile only the recovery/compile with rom/millions of different settings/etc...) The phone start the recovery, but not work (the best result is only a flickering image). Earlier I consulted with Daveee10, but he have same results.
Click to expand...
Click to collapse
Then we are missing some files or there are wrong configurations...
Sent from my X8 using xda app-developers app

How did you try pilu1978? I mean where did you place the libs and the binary?

sgt. meow said:
I couldn't extract ramdisk-recovery.img but I extracted ramdisk-recovery.cpio and I get a lot of files in the sbin directory like recovery, sdparted, fix_permissions.sh, adbd and a lot of libs. In the etc directory there is a recovery.fstab.
Click to expand...
Click to collapse
Now replace all the files in ramdisk with these new ones
Sent from my X8 using xda app-developers app

It won't work. I'm pretty sure about it.
EDIT: Okay apparently it is the right way. Sorry Xmaster8. Lesson learned.

Xmaster8 said:
Now replace all the files in ramdisk with these new ones
Sent from my X8 using xda app-developers app
Click to expand...
Click to collapse
Yes. I examined a disassembled recovery binary from other phone (what is working correctly), the recovery depends on these binaries:
libz.so, libc.so, libstlport.so, liblog.so, libcutils.so, libstdc++.so and linker. These binaries needed in the ramdisk.

But should these be in the sbin?

sgt. meow said:
But should these be in the sbin?
Click to expand...
Click to collapse
Yes, you can place here. Or any other place, but need to add the path in init.rc. For example:
export PATH /sbin
EDIT: I forgot, libm.so also needed

One more thing. Should I try this with ICS or JB?

sgt. meow said:
One more thing. Should I try this with ICS or JB?
Click to expand...
Click to collapse
If you built with ics source tree then ics and if jb then jb
Sent from my X8 using xda app-developers app

sgt. meow said:
One more thing. Should I try this with ICS or JB?
Click to expand...
Click to collapse
I tried with cm7 For my own goal the ICS/JB is too slow/unstable. But Daveee10 working on twrp with his own JB project, looks like he have same results with CM11 than me with CM7. I think the problem source is not the CM version, maybe something missing from the device specific files.

[Q] Problem compiling jb for P3113

Hi guys.
I'm getting problems when I try a make for my aosp build (for my p3113)
I followed this guide: http://forum.xda-developers.com/showthread.php?t=1762641
and I git clone git://github.com/AOKP/android_device_samsung_espressowifi.git -b jb espressowifi
then ./extract-files.sh
when I'm extracting, I get some errors like
remote object '/system/lib/hw/lights.omap4.so' does not exist
341 KB/s (31320 bytes in 0.089s)
remote object '/system/media/battery_batteryerror.qmg' does not exist
remote object '/system/media/battery_charging_0.qmg' does not exist
remote object '/system/media/battery_charging_5.qmg' does not exist
Is this normal?
Btw.. I continue with . build/envsetup.sh which is done successfully
and a lunch done successfully too..
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.1.2
TARGET_PRODUCT=full_espressowifi
TARGET_BUILD_VARIANT=userdebug
...
HOST_BUILD_TYPE=release
BUILD_ID=JZO54K
OUT_DIR=out
Finally I try a make -j4 otapackage and I got way too much errors and it stops
Can i have help please?

rainfalls said:
Hi guys.
I'm getting problems when I try a make for my aosp build (for my p3113)
I followed this guide: http://forum.xda-developers.com/showthread.php?t=1762641
and I git clone git://github.com/AOKP/android_device_samsung_espressowifi.git -b jb espressowifi
then ./extract-files.sh
when I'm extracting, I get some errors like
remote object '/system/lib/hw/lights.omap4.so' does not exist
341 KB/s (31320 bytes in 0.089s)
remote object '/system/media/battery_batteryerror.qmg' does not exist
remote object '/system/media/battery_charging_0.qmg' does not exist
remote object '/system/media/battery_charging_5.qmg' does not exist
Is this normal?
Btw.. I continue with . build/envsetup.sh which is done successfully
and a lunch done successfully too..
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.1.2
TARGET_PRODUCT=full_espressowifi
TARGET_BUILD_VARIANT=userdebug
...
HOST_BUILD_TYPE=release
BUILD_ID=JZO54K
OUT_DIR=out
Finally I try a make -j4 otapackage and I got way too much errors and it stops
Can i have help please?
Click to expand...
Click to collapse
To build it proper you need...
https://github.com/AOKP/android_device_samsung_p3100
https://github.com/AOKP/android_device_samsung_p3113
And:
https://github.com/AOKP/vendor_samsung
for the p31xx blobs
That should get you going.

cmenard said:
To build it proper you need...
github.com/AOKP/android_device_samsung_p3100
github.com/AOKP/android_device_samsung_p3113
And:
github.com/AOKP/vendor_samsung
for the p31xx blobs
That should get you going.
Click to expand...
Click to collapse
Thanks for the reply. So if I understand correctly, the samsung_espressowifi isn't the right one I need? so i went into device/samsung/ then I git clone p3100 and p3113 there am I right?
I was wondering where do I have to clone the vendor? directly into the samsung folder?
Thanks again for your help! Greatly appreciated

rainfalls said:
Thanks for the reply. So if I understand correctly, the samsung_espressowifi isn't the right one I need? so i went into device/samsung/ then I git clone p3100 and p3113 there am I right?
I was wondering where do I have to clone the vendor? directly into the samsung folder?
Thanks again for your help! Greatly appreciated
Click to expand...
Click to collapse
Yup. Just use the links I provided and you should be able to build just fine.

cmenard said:
Yup. Just use the links I provided and you should be able to build just fine.
Click to expand...
Click to collapse
Ok. I've started from scratch, deleted all the things in the samsung folders. i git clone p3113, p3100 and vendor. So now I have p3113,p3100 and samsung_vendor folders. Do I have to pull the p31xx folders from vendor and paste it directly into the samsung one?
when I do a ./extract-files.sh, i don't have any error until there ->
180 KB/s (14268 bytes in 0.077s)
453 KB/s (45380 bytes in 0.097s)
remote object '/system/lib/libsec-ril.so' does not exist
120 KB/s (9620 bytes in 0.077s)
172 KB/s (13768 bytes in 0.077s)
My p3113 is connected with usb debugging and appears correctly in adb devices.
Plus, nothing as been added into the p3113 folders at the end of the extract-files. At the end of the extract, should a vendorsetup.sh file supposed to be created?
Sorry but I'm a noob looking to learn something
thanks
EDIT: ok I found what was wrong with the vendor.. it's not going into /device/samsung folder but /vendor/samsung/p31xx right? still having the libsec-ril issue tho..

Do you have any hint cmenard?

You have two problems. One, you need to manually add a vendorsetup.sh file to the p3113 folder. Copy one from one of the other devices, and change its only line to read something like ADD_LUNCH_COMBO_p3113. Also, if extract-files.sh gave any errors, it didn't work. I've never had any luck with the default file, I always change the two lines that have adb pull to read cp /<romlocation>/system $file and extract a JB ROM to a folder on the disk.
Posted from my Galaxy Tab with CM10

MultipleMonomials said:
You have two problems. One, you need to manually add a vendorsetup.sh file to the p3113 folder. Copy one from one of the other devices, and change its only line to read something like ADD_LUNCH_COMBO_p3113. Also, if extract-files.sh gave any errors, it didn't work. I've never had any luck with the default file, I always change the two lines that have adb pull to read cp /<romlocation>/system $file and extract a JB ROM to a folder on the disk.
Posted from my Galaxy Tab with CM10
Click to expand...
Click to collapse
Yeah I already added the vendor setup file manually. I'll resync my jb tonight maybe something went wrong. I'll have to figure out the extract file problem too. All this when I'll get back from work lol

Why are you using extract-files.sh? The reason to use it is if you don't have the vendor files for the device already downloaded, and if you look at the vendor_samsung folder, it has all the stuff you need already. All you need to do is specify the device and build after you have the source downloaded.

imnuts said:
Why are you using extract-files.sh? The reason to use it is if you don't have the vendor files for the device already downloaded, and if you look at the vendor_samsung folder, it has all the stuff you need already. All you need to do is specify the device and build after you have the source downloaded.
Click to expand...
Click to collapse
I was using it because I've followed the guide step by step but I was asking the same question myself. I'll retry again as soon as I go back home

I'm getting a bit farther now. Not compiling yet but.. will do soon.. when I'm trying to do a make -j4 otapackage, I'm getting a series and I wrote them in pastebin
http://pastebin.com/f3UP50ku
I'm using:
[email protected]:~/android$ java -version
java version "1.6.0_35"
Java(TM) SE Runtime Environment (build 1.6.0_35-b10)
Java HotSpot(TM) 64-Bit Server VM (build 20.10-b01, mixed mode)
I'm kinda lost
thanks for your help!

You have java virtual machine, but not java development kit. It's a bit difficult to find for Linux, but you can get it from http://www.cyberciti.biz/faq/howto-ubuntu-linux-install-configure-jdk-jre/
Posted from my Galaxy Tab with CM10

MultipleMonomials said:
You have java virtual machine, but not java development kit. It's a bit difficult to find for Linux, but you can get it from http://www.cyberciti.biz/faq/howto-ubuntu-linux-install-configure-jdk-jre/
Posted from my Galaxy Tab with CM10
Click to expand...
Click to collapse
Well.. this is what I've done so far
1. I downloaded java there http://www.oracle.com/technetwork/java/javase/downloads/jdk6-downloads-1637591.html (jdk-6u34-linux-x64.bin)
2. Went to terminal chmod +x jdk-6u34-linux-x64.bin
3. Then /.jdk-6u34-linux-x64.bin == install successfull
4. sudo update-alternatives --config java -> to choose the last jdk I've installed (by default, OpenJDK is installed with ubuntu instead of java jdk)
still having the same output with java -version
still having same issues

I got the same problem too when I'm trying to compile.
pastebin.co m/wcSZq6wq
it stops there and nothing.
I'm using p3113, p3110 and p3100 folder from /github.co m/AOKP/
Any idea someone?
Thanks

Finally I've been able to compile it through the end. Now time for debugging... I got a bootloop (surprising eh!?)
http ://pastebin.co m/e6STwe0E
Any help will be appreciated!
thanks!
EDIT: I've uploaded my work so far right there:
https ://docs.google.c om/file/d/0B6GzemNaw2dRY3BTT0tPWDdKYnM/edit
REMEMBER it's bootloading!

Nobody have a clue?

Problem while downloading sources

i get this error
warning: local_manifest.xml is deprecated; put local manifests in `/home/rohilshah/aospa/.repo/local_manifests` instead
after making a new folder and pasting it there i get this error:
fatal: duplicate path vendor/samsung in /home/rohilshah/aospa/.repo/manifest.xml
i have checked manifest.xml and there is no "vendor/samsung" anywhere
any help devs?
tried deleting the whole repo folder and doing a fresh sync but no help!
i'm on ubuntu 12.04.4 LTS
Sent from my GT-I9500 using XDA Premium 4 mobile app

[Q] Binaries

This is beginner talking. I was looking for a Factory images for my Nexus 4 and I saw on Google Developers's website that there are some Binaries for Nexus Devices (NFC,Graphics, GSM, WIFI....) and now I'm curious about what can I do with them ( *.sh file)?
Can I flash them separately module by module in case that I need one, or it is just enough to flash a Factory image. Are they correlated? Thanks!

A factory image contains everything you need. The OS, kernel, drivers etc. It's basically a complete image of how the phone would look if you buy it.
Sent from my Nexus 4 using xda app-developers app

volvoxxda said:
This is beginner talking. I was looking for a Factory images for my Nexus 4 and I saw on Google Developers's website that there are some Binaries for Nexus Devices (NFC,Graphics, GSM, WIFI....) and now I'm curious about what can I do with them ( *.sh file)?
Can I flash them separately module by module in case that I need one, or it is just enough to flash a Factory image. Are they correlated? Thanks!
Click to expand...
Click to collapse
Binaries are nothing but the specific hardware drivers. Its of no use to you unless you plan on compiling a ROM.
*.sh files are linux files, they are used to extract the drivers/binaries to a folder in you source code folder.

sandy-achar said:
Binaries are nothing but the specific hardware drivers. Its of no use to you unless you plan on compiling a ROM.
*.sh files are linux files, they are used to extract the drivers/binaries to a folder in you source code folder.
Click to expand...
Click to collapse
Thanks guys, that was helpful! :good: Maybe this is beginning of something revolutionary (regarding me -> compiling ROM) :laugh: