Database Info

[HUAWEI U8100/U8110/U8120] Froyo Kernel Development / Porting (Your help needed!)

Many people want to run a working froyo on their devices.
This won't be possible in a clean way without compiling a new kernel.
To archive this goal, we need to merge the Huawei specific device drivers (which are for 2.6.29) into a new kernel tree, the 2.6.32.9 one (or even 2.6.35 but 2.6.32.9 comes first since it is stable and thus important to us).
I did some research and preliminary work which I will explain here:
- The base kernel Huawei started with is available here (gitweb) - also check their wiki.
- Huawei started with the Q8650BSDCANLYA324020 tag on the donut_glazed branch (see instructions at the end of the post)
- Huawei has written it's own board driver (note they have used a Q8650 kernel release not a MSM7x25 one, most likely because this board driver is a little older and was not available for the version they wanted)
- After they were finished writing their drivers they released the kernel source (as you can download it from Huawei)
I have checked out the Q8650BSDCANLYA324020 base kernel version and diffed it against the kernel release of Huawei, generated a patch file (and stripped out the DOS linebreaks wtf) which can be applied to the base kernel.
Applying this patch to a more recent kernel (2.6.32.9) is not possible without merging the code into the new kernel tree (and since I'm not a programmer I can't do it - this is were your help is needed).
The other question is in which kernel tree we can port the patch I have extracted. I think we can use Q8650BSDCANLYA504005 on the froyo_almond branch since Huawei used an older version of it. Merging it into the AOSP msm-2.6.32.9 tree may be possible too (but the code aurora msm kernel is an improved AOSP version, so I guess we want that one).
My patch (and some non-pulse-mini fixup patch) alongside with a freshly extracted and fixed .config for the U8120 can be found at http://nico.core.ws/misc/huawei_kernel_u8100_8110_8120/
To port the source you need to checkout the original source (Q8650BSDCANLYA324020), create a new branch in which you apply the Huawei patch, then checkout the froyo kernel (Q8650BSDCANLYA504005) and merge your branch containing the changes from the patch into it.
Another way may be porting the froyo kernel tree back to the eclair one with Huawei patches.
Please post any results/questions/etc. here!
If we should get this working we can also enable the GPU driver (Adreno 200) as requested by many people (and much more (CyanogenMOD anyone? )).
Appendix:
Instructions on how to get the original source:
$ git clone git://codeaurora.org/kernel/msm.git
$ git checkout Q8650BSDCANLYA324020
Instructions on how to apply the patch (assuming "msm" is the kernel tree):
$ cp diff_kernel_msm_aurora_Q8650BSDCANLYA324020.diff msm/
$ cd msm/
$ patch -p1 < diff_kernel_msm_aurora_Q8650BSDCANLYA324020.diff
If you are compiling for U8100 or U8120 phones, you need to apply another
patch which fixes sensors (otherwise your phone won't be able to read battery
level and stuff):
$ cp needed_fixes_for_non_u8110_devices.diff msm/
$ cd msm/
$ patch -p1 < needed_fixes_for_non_u8110_devices.diff
Note that the above instructions will get you nothing new, only the kernel already running on your device.
This thread is about porting the Huawei patch to a froyo kernel.

Very nice! Thank you for this topic!
I hope this will be successfull

Are the Atheros sources included aswell?

[GER]Roxxor said:
Are the Atheros sources included aswell?
Click to expand...
Click to collapse
To be honest, I don't know. They should be in there though (maybe under a more generic driver name or integrated in the board driver) otherwise Huawei would have violated the GPL.

The problems with the fixes:
wifi
They got almost wifi working in other post
radio
FM radio too with an 3rd party app
dpad
dpad crash in this post too 2 pages back just disable this
screen calibration
calibration fix can meaby be fixed with HTC calibrate??(its an calibration app)
sound
I solve the sound problem with my phone is to replace the libaudio.so from 2.1rom,maybe you can try.\

cedric123 said:
here is an source for the adreno drivers.
https://www.codeaurora.org/gitweb/q...b819424af4be;hb=refs/heads/android-msm-2.6.32
Click to expand...
Click to collapse
Basically this is the complete kernel source for froyo without Huawei patches (it's the wrong tag too).
When we have ported the drivers we easily can enable that driver.
cedric123 said:
the froyo kernel source: http://www.huaweidevice.com/tcpsdow...&attachmentName=kernel-2.6.32-U8150-Froyo.zip
Click to expand...
Click to collapse
Thats the source for the U8150, not the ones we want. The only thing which may help us at a future point in there is the kernel config.
cedric123 said:
If you compile a kernel right now you'd get a kernel that won't read the batterylevel and the magnetic compass won't work so we need to make a few adjustments.
Click to expand...
Click to collapse
This is in needed_fixes_for_non_u8110_devices.diff
So nothing new here.

So what can we do to help?
Is there a way to chat in XDA?

Any news on this?

cedric123 said:
here is an source for the adreno drivers.
LINK REMOVED
Here are some are adreno 200 drivers from a Custom nexus one ROM:
Areno Drivers package contains the adreno rivers only(i could miss some drivers here so look for the package above contains all drivers from the nexus rom
LINK REMOVED
Click to expand...
Click to collapse
Possible to make an update.zip for this Adreno 200 driver on 2.1 while 2.2 is not working?

editeditediteditediteditedit

Maybe he's working on the project.

Leito92 said:
Maybe he's working on the project.
Click to expand...
Click to collapse
I dont think so he's not saying anything about it for 1 week now...

But even if he doesnt say anything, this topic can be useful.

Someone with git/kernel/c knowledge need to port the patch.

nicoderboss said:
Someone with git/kernel/c knowledge need to port the patch.
Click to expand...
Click to collapse
Who can do That?
Kallt_kaffe meaby?

nicoderboss said:
Someone with git/kernel/c knowledge need to port the patch.
Click to expand...
Click to collapse
You need some elemental knowledge in C and then simply cut and paste the text in the files.
However, I think that it is more important to be able to compile from source and install the existing Huawei Linux kernel for the U8120. That is, can we compile from source all the code for Android 2.1-update1 and install on the U8120?
It might be good to try to get CyanogenMod on the U8120 for the kernel version that Huawei provides. Then, we can cut down the 1.5MB patch into smaller parts, and even try to get the drivers included in the Linux kernel.
I have not idea how to compile Android 2.1-update1 and get the plain old android source on the phone. I am willing to invest the CPU clocks to compile it, though.

cedric123 said:
Who can do That?
Kallt_kaffe meaby?
Click to expand...
Click to collapse
Dunno, it's quite a huge and advanced task.
Sent from my Vodafone 845 using XDA App

maybe we can get some kernel developers from the desire topic to help us?
I have send Benee, deovferreira, Kali- a PM maybe they could help us

nicoderboss said:
Dunno, it's quite a huge and advanced task.
Sent from my Vodafone 845 using XDA App
Click to expand...
Click to collapse
Can we just replace the normal kernel in the command list for the new kernel so you apply patch in the new kernel(u8150)froyo kernel?

I have had contact with benee a kernel developer for the htc desire. He is willing to help but he needs a device so he can test kernels he build. It is not possible to build kernels without a device because this is a huge project without a good base.
Maybe we can setup a fund raiser to get him a device?

Impossible to find working tun.ko

Hello people,
i'm looking for a working tun.ko for my motorola xoom device:
uname tells me:
Code:
# busybox uname -a
Linux localhost 2.6.36.3-00010-g3139c20 #1 SMP PREEMPT Fri Jul 8 06:11:47 CDT 2011 armv7l GNU/Linux
any help is really appreciate.. i do need openvpn to work.. thank you
--edit--
eventually, please redirect where i can find instructions on how to build such a module.. i mean.. i can easly do it for my linux distro, but no idea about androd versions and arm stuff

No one? I'm running stock 3.1 rom, this is a 3G european tablet
Thank you

is it really so impossible to get that?
please guys, i need some help

Its hard to find anything that works right if you are stock Tun.ko works fine on Tachi. Get root sir. You will lead a happier more fruitful life

bigrushdog said:
Its hard to find anything that works right if you are stock Tun.ko works fine on Tachi. Get root sir. You will lead a happier more fruitful life
Click to expand...
Click to collapse
I'm am root, of course (or there would be no reason nor way to use openvpn itself) i'm just using stock rom intead of other flavors.
all other tun.ko i found are not working because of a different kernel version number. mine again, is:
2.6.36.3-00010-g3139c20

anubisg1 said:
I'm am root, of course (or there would be no reason nor way to use openvpn itself) i'm just using stock rom intead of other flavors.
all other tun.ko i found are not working because of a different kernel version number. mine again, is:
2.6.36.3-00010-g3139c20
Click to expand...
Click to collapse
Gotcha. Just flash Tachi or latest Launchpad kernel and you should be good to go.

[Q] does anyone have XOOM ftdi_sio.ko kernel driver?

Hi there,
did anybody build ftdi_sio kernel driver for XOOM? I desperately need it and I doesnt know how to compile it against xoom kernel.
my kernel version is:
Code:
Linux version 2.6.36.3-gc2bee64 ([email protected]) (gcc v
ersion 4.4.3 (GCC) ) #1 SMP PREEMPT Tue May 3 15:33:26 PDT 2011
If anyone has it or can do it for me, I would be very happy

jupiik said:
Hi there,
did anybody build ftdi_sio kernel driver for XOOM? I desperately need it and I doesnt know how to compile it against xoom kernel.
my kernel version is:
Code:
Linux version 2.6.36.3-gc2bee64 ([email protected]) (gcc v
ersion 4.4.3 (GCC) ) #1 SMP PREEMPT Tue May 3 15:33:26 PDT 2011
If anyone has it or can do it for me, I would be very happy
Click to expand...
Click to collapse
Tell me more about this module. We can likely add it to our kernel config.

that's the usb to serial i/o driver. Also known as pl2303 chipset support. It would go great with the bt5 mod. Would allow connection to ttl serial ports likethe ones in routers, phones, and NAS devices. I.d be glad to test it as I've got several pl2303 serial converters.

I'd like this too. Have several FTDI usb/serial devices.. but only used in Windows. Is there a terminal app that could talk to a virtual com port? I see FTDI even has pages devoted to Android!

+1
+1
i can test it if will be possible

I use FTDI on android with the RXTX library: v-lad.org/projects/gnu.io.android witch allows me to work only in java and this library creates input output streams for me. Its fine but my application has to actually instal ftdi_sio.ko to kernel every time it is running first time after reboot and for xoom I cannot even find this module and I dont know how to build one. It would be nice if there were some kernels supporting this so that it can be used straight away after pluging in usb2serial chip.

+1 for the USB to serial adapter support. I use these guys all the time with windows to talk to FPGAs and the sort. I'd be willing to test, possibly even assist with the work (though I've never successfully compiled a kernel before - I tried tiamat once).
Thanks.

OK guys ill cook this up. Nice to get to a "more experienced " user thread.
Ok guys, give this a run
http://goo.gl/MhIBX

The link to the driver is not working anymore. Would the driver work for the ICS stable version of the eos ROM?

[DEV] LANYU 910 / Airpaid RK2918 - Kernel / ICS WorkInProgress

Working on porting ICS to the Lanyu 910 / X10 Airpad MID-910. I think the kernel sources used for the Pascal2 could possibly work with the 910 after some config changes.
Basically with the 910 we have no stock kernel source available for reference, no stock configuration, no detailed hardware inside the device.. We know it uses the rk2918 rockchip and I know it uses the SWL-2480 / Marvel 8686, simply from observing the identifying markings on the chip. Other than that, all we know is that it uses a 2.6.32 kernel with android 2.3, has an unknown 7" capacitive touch screen, unknown camera, etc. In order for ICS to work with the 910 we'll have to use a 3.0.8+ kernel or backport all of the required components from 3.x to our working 2.6.32 sources -however we don't have the patched sources for the stock firmware, so we are better off to just use 3.0.8 kernel that the source is available for on many rk2918 devices - of course we'd have to make configuration changes to our specific hardware, and possibly patch the sources with modified/new source code for our specific hardware (if we can obtain it).
Pascal 2 has a realtek based wireless chipset.. 910 uses the SWL-2940 / Marvel 8686, the module for this is also included in the kernel sources. The 910 has an unknown touchscreen, so the kernel for the pascal2 may or may not work with the touch screen settings. It is quiet difficult to work on the kernel without in depth knowledge of all the hardware. The 910 has Lanyu printed on the motherboard, and I'm not successful in finding any detailed hardware information for the board on the 910.
Also I am concerned with the memory mappings since the 910 only has 512mb ram and the pascal2 has 1GB+
Really wish these Chinese tablet manufacturers would follow the rules of GPL and release their source code, it would help A LOT with getting ICS to work with the 910.
As far as the rockchip and the ICS rom that vurrut has put together, I am almost 100% sure that the system.img that he used will work with the 910 as long as I get a working 3.0.8 kernel for ICS reconfigured/recompiled and implement some changes in the boot.img for the init services relating to hardware.
If anyone has the X10 airpad (rk2918 based) or the Lanyu 910 and has some important information regarding the internal hardware, please contact me with details, as I can probably get a working kernel for our device in a matter of hours.
Needed:
Gsensor/Accelerometer MFG/Model
Input Keys Controller - MFG/Model
Battery Sensor Chip - MFG/Model
TouchScreen/Display - MFG/Model
Other mainboard chipsets - MFG/Model (excluding RK2918 Rockchip SoC)
It would be of much help if there was someone here knows the MFG/Model of any of the above hardware, and it would also be a great help if anyone knows what linux kernel drivers are used for any of the components inside the 910.
When I was working with the Kindle Fire kernel I had found a very helpful information page on the internal parts of the device, with very detailed information - it was really helpful. I know that with these generic Chinese tablets finding such info may be much more difficult due to lack of interest and lack of popularity when compared to major brand tablets such as the Kindle Fire - but if anyone out there has ran across similar information it would give us GREAT progress in developing an ICS ROM for the 910. Here is a link to the breakdown of components in the Kindle Fire:
http://www2.electronicproducts.com/Amazon_Kindle_Fire_D01400_Tablet-whatsinside_text-123.aspx
The thread to the ICS ROM for Pacal 2 (rk2918) device is here: http://forum.xda-developers.com/showthread.php?t=1734181
A big thanks to Vurrut for all of his work! Hopefully we can use parts of his ROM to get ICS running on our Lanyu/Airpad!

Pls open a terminal, type "dmesg" and upload the log. Then we will see
If you have luck your build has also the kernel config file. You will find it under /proc/config.gz.
- Oma -

Oma7144 said:
Pls open a terminal, type "dmesg" and upload the log. Then we will see
If you have luck your build has also the kernel config file. You will find it under /proc/config.gz.
- Oma -
Click to expand...
Click to collapse
Do you honestly think I would be working on a Linux kernel without a knowledge of the existence of dmesg or config.gz? Did you also forget to remind me of adb shell logcat -d >> logcat.log ?
Sent from my A100 using xda premium

linuxsociety said:
Do you honestly think I would be working on a Linux kernel without a knowledge of the existence of dmesg or config.gz? Did you also forget to remind me of adb shell logcat -d >> logcat.log ?
Click to expand...
Click to collapse
Sry. You've been asking for touch, sensors etc.. In the named logs you will find all that.
- Oma -

Oma7144 said:
Sry. You've been asking for touch, sensors etc.. In the named logs you will find all that.
- Oma -
Click to expand...
Click to collapse
Only partial information can be obtained in this manner as it will only show what device modules are loaded, the information I was wanting was precise model information of the chipsets used in the tablet. And the config for the stock kernel is not included in procfs anyway as the developers must have not said =Y to CONFIG_IKCONFIG
Sent from my A100 using xda premium

]
Code:
CONFIG_INPUT_TOUCHSCREEN=y
# CONFIG_TOUCHSCREEN_AD7879_I2C is not set
# CONFIG_TOUCHSCREEN_AD7879 is not set
# CONFIG_I2C_LZ300 is not set
CONFIG_I2C_LZ300_ST=y
# CONFIG_I2C_SIS809 is not set
# CONFIG_INPUT_MISC is not set
CONFIG_INPUT_GPIO=y
#
# Magnetometer sensors
#
# CONFIG_COMPASS_AK8975 is not set
# CONFIG_COMPASS_AK8973 is not set
CONFIG_G_SENSOR_DEVICE=y
# CONFIG_GS_MMA7660 is not set
CONFIG_GS_MMA8452=y
# CONFIG_GS_L3G4200D is not set
# CONFIG_INPUT_JOGBALL is not set
# CONFIG_LIGHT_SENSOR_DEVICE is not set
With the Model (SIS809, MMA8452, AK8975 etc.) you have all what you need. This you will also find in the dmsg log.
That's enough to compile from sources.
Anyway.
- Oma -

Oma7144 said:
]
Code:
CONFIG_INPUT_TOUCHSCREEN=y
# CONFIG_TOUCHSCREEN_AD7879_I2C is not set
# CONFIG_TOUCHSCREEN_AD7879 is not set
# CONFIG_I2C_LZ300 is not set
CONFIG_I2C_LZ300_ST=y
# CONFIG_I2C_SIS809 is not set
# CONFIG_INPUT_MISC is not set
CONFIG_INPUT_GPIO=y
#
# Magnetometer sensors
#
# CONFIG_COMPASS_AK8975 is not set
# CONFIG_COMPASS_AK8973 is not set
CONFIG_G_SENSOR_DEVICE=y
# CONFIG_GS_MMA7660 is not set
CONFIG_GS_MMA8452=y
# CONFIG_GS_L3G4200D is not set
# CONFIG_INPUT_JOGBALL is not set
# CONFIG_LIGHT_SENSOR_DEVICE is not set
With the Model (SIS809, MMA8452, AK8975 etc.) you have all what you need. This you will also find in the dmsg log.
That's enough to compile from sources.
Anyway.
- Oma -
Click to expand...
Click to collapse
Mr. Oma, I am sorry but I think you may be in the wrong thread, the Lanyu 910 only shares one thing in common with the other common RK2918 based tablets, and that is the RK2918 its self, the rest of the hardware that makes up the full system is different on the 910/Airpad than the more popular tablets that are using the RK2918. For example you probably use a RTL based wifi chip in the config you are using also, where the 910/AP uses the SWL-2480 which uses a Marvel 8686 driver in the linux kernel or you can use the libertas driver in more recent kernels. What exactly is the config you pasted here from? At this point I know the internal hardware enough to get a proper config file for the 910/Airpad, however there are compile issues with certain components and without resolving the compile issues there is no kernel image going to be generated unless I disable the problems at hand in the config, if you want more up-to-date information then head over the the x10 forums and check the original thread for 910/AP kernel development: http://forums.x10.com/index.php?topic=27184.0

Have you seen this?
Here is another Tab using SWL-2480 (looks like an Aoson M12).
Here is another 3.0.8 source, originally from a Chinese Tab named Xinboa.
Maybe that helps.
- Oma -

Oma7144 said:
Have you seen this?
Here is another Tab using SWL-2480 (looks like an Aoson M12).
Here is another 3.0.8 source, originally from a Chinese Tab named Xinboa.
Maybe that helps.
- Oma -
Click to expand...
Click to collapse
I appreciate your effort in helping me find info, but I have already researched most the possibilities and am already aware of the sites you linked. The problems aren't finding hardware specs, the problem now is getting 3.0.8 sources to compile with the Airpads hardware selected in the configuration, as I posted in the x10 forum, it doesn't appear that any 3.0.8 kernels have been successfully compiled for other devices using the same board-config as the 910, in fact the link you specified with the swl-2480 is the only device that has similar hardware aside from the rk2918 that I have found. The wifi and audio both fail to compile with Ody.se sources. I have decided to put most of my work now into testing/development of Jelly Bean for the Acer Iconia Tab, as it doesn't seem that many others are interested in the 910/Airpad development. Thanks again

Ok.
Odys-Xpress sources? That's kernel 2.6.32.27, isn't it?
But try the sources from above link. Could search for that
A library for Marvell 8686 SDIO WLAN devices.
So far, the following modules have been verified:
(1) Samsung SWL-2480
(2) Azurewave AW-GH321
(3) USI WM-G-MR-09
(4) Murata SP-8HEP-P
I don't know if they will compile.
- Oma -

Oma7144 said:
Ok.
Odys-Xpress sources? That's kernel 2.6.32.27, isn't it?
But try the sources from above link. Could search for that
A library for Marvell 8686 SDIO WLAN devices.
So far, the following modules have been verified:
(1) Samsung SWL-2480
(2) Azurewave AW-GH321
(3) USI WM-G-MR-09
(4) Murata SP-8HEP-P
I don't know if they will compile.
- Oma -
Click to expand...
Click to collapse
They won't compile with 4.2.0 or 4.4.0 arm eabi toolchain in 3.0.8 sources, i tried them, since 3.0.8 it has been replaced with libertas instead of mv8686, i've done looked into all of it man

linuxsociety said:
They won't compile with 4.2.0 or 4.4.0 arm eabi toolchain in 3.0.8 sources, i tried them, since 3.0.8 it has been replaced with libertas instead of mv8686, i've done looked into all of it man
Click to expand...
Click to collapse
Use gcc 4.5.2 or higher.
- Oma -

Oma7144 said:
Use gcc 4.5.2 or higher.
- Oma -
Click to expand...
Click to collapse
I also tried gcc 4.6.2 and 4.6.3 natively setup with cross compile in Gentoo / Funtoo - I get the same same errors with the wifi and the audio as using the appropriate eabi-arm toolchains.. I tracked down the problems though, it is a dephell with major code changes in common headers. The headers that are included in the sources have changed from 2.6.32.27 and to 3.0.8 and porting everything up to current is quiet more code changes than I am willing to work on. Like I have said though, I am no longer working on this kernel for the generic devices 910/AP, I have more work on my slate now than I need working on the Acer Vangogh / Vendetta kernels for Jelly Bean to incorporate Tiny HAL and newer tegra changes keeping compatability with the only Acer source we have available. But at least I am not limited to products that aren't following the GPL appropriately, and the use of uncommon hardware that makes debugging damn near impossible. I almost have the Vangogh board and Acer specifics ported over to 3.1's grouper from the nexus project and it's much more smoother than working with that chinese developed tab

Ok, than have a good time!
Greetings to Southern Kentucky.
- Oma -

linuxsociety said:
If anyone has the X10 airpad (rk2918 based) or the Lanyu 910 and has some important information regarding the internal hardware, please contact me with details, as I can probably get a working kernel for our device in a matter of hours.
Click to expand...
Click to collapse
Here you go: eboda-TS, MV8686 WLAN, MMA8452Q Sensor, WM8988 Audio, ANX7150 HDMI, HYM8563 Clock, APX192 Powermgt.
Could you pls compile a kernel?
- Oma -

[Completed] [Q] Kernel source code and concepts misunderstood

Hello:
I'm trying to build a tun module for my cellphone android OS. I'm using this guide to learn what I'm doing since it is very complete and well written:
Code:
http://xda-university.com/as-a-developer/getting-started-building-a-kernel-from-source
The problems that I found are a few:
- I can't find the source code of Gingerbread for my Galaxy Fit GT-S5670L.
Here comes confusion one, is the kernel itself the source code that I'm looking for or I need the kernel's source code? I'm confuse.
My cellphone has this kernel: Linux localhost 2.6.35.7-perf-CL700532 #1 PREEMPT Wed Nov 2 01:11:19 kst 2011 armv61 GNU/Linux
So according to this:
Code:
http://forum.xda-developers.com/showthread.php?t=1808167
I've gone to all these pages looking for my kernel or kernel's source code which should be Gingerbread:
Code:
* http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=gt-s56
* https://www.codeaurora.org/cgit/quic/le/kernel/samsung/
* https://android.googlesource.com/kernel/samsung/
I can't find the source code or kernel's source code for my Samsung Galaxy Fit GT-S5670L because I don't even know what I'm looking for exactly. Should I look for Gingerbread's kernel, or Galaxy Fit GT-S5670L Gingerbread's kernel?
At Samsung code source there isn't even my model of cellphone. (Thank you Samsung, because my phone is old doesn't mean that I will not need support)
Nevertheless I've downloaded the kernel/samsung from Android Google source with git command.
- Confusion two, nothing downloaded, I mean, the folder was created but it was empty.
.Where the 400 MB, more or less, went?!
I'm running Debian on my desktop computer.
- Confusion number three, I got the ADK and NDK tools, have no idea how to install them but I'll search and figure this out.
- Confusion four: the ADB, could someone point me to a good tutorial how to work with this.
- Confusion five: I know because I've bricked my phone several (SEVERAL) times that is not the same: Fit GT-S5670 than Fit GT-S5670L so I can't download or test or work with a kernel that it's not meant to be for my cellphone, that is if there is a kernel or kernel's source code for each model or variant of the Fit cellphones.
Please oh please help me!!
I have been trying to work with this for the last 3 weeks and surf the net for hours and I don't know what to do anymore. I have even contemplate the idea of buy a second-hand phone, though I really like mine.
PS. Sorry for my bad english.
Hope, reeeeeeally hope you guys can help me.

Hi,
There are many guides and tutorials here, and you can ask for help if you're still stuck,
> Chef Central > Android
Good luck!