Database Users

3.0.8 Kernel in U8800 pro

The last 2 days I started playing around with Aurora rom both DZO's and Sakura's.
I was curious enough to try some "crazy" things and flashed some roms modded by me.
I tried the following.Unrared the DZO aurora rom and edited the updated script with notepadd ++. I changed the model from u8800 to u8800pro (you can copy-paste the 1st line which is what we need from a sakura aurora updater script) and then I rezipped the dzo aurora rom with winrar and it flashed normally.It even booted normally!
I also tried copying the boot.img from DZO release to Sakura release.Again the rom flashed ok.
But the 2 modded roms have these problems in common(other things I tried like camera,messaging were working normally):
1) No bluetooth working (it just writes turning on).Sometimes the phone reboots.
2) No wifi working. Same as bluetooth. Just turning on and phone reboots sometimes. Also tried with new wifi driver option.
I also provided a screenshoot from the second method I used(sakura rom with 3.0.8 kernel).
Anyway.Maybe the day that we can use 3.0.8 kernel in our phones isn't far away from us.Moreover it may also be possible to "port" the x5 aurora to our x5 pro without having to rely any more on the chinese guys(seriously I hate it everytime I flash a sakura rom that i have to change the language ).
Well hope that this thread will be the start for a better aurora rom for the u8800 pro

It is more safe if you dont unrar the rom. Just open in a window and drag n drop the files you want to change.
For the language, open the build.prop file and change the following lines:
ro.product.locale.language=zh
ro.product.locale.region=CN
to:
ro.product.locale.language=en
ro.product.locale.region=US

ela re patrioth
i know that I can change the language even before flashing the rom but that's not the reason I started this thread. I started just to prove that 3.0.8 kernel can also run on our phones because I have seen a lot of posts in different forums complaining about u8800 PRO not getting a 3.0.8 kernel release

Oraios...but can you fix those bugs or just post it here!!!

I tried to do it,but I failed.After some flashing I got a not working phone.
You can help me at this thread here if you like : http://forum.xda-developers.com/showthread.php?p=25748225#post25748225
Edit: Problem solved and phone working. But guess I will do a break after this little adventure and will start modding again in the near future.
Maybe it's better because aurora and the kernel will be even better then

Moihack said:
The last 2 days I started playing around with Aurora rom both DZO's and Sakura's.
I was curious enough to try some "crazy" things and flashed some roms modded by me.
I tried the following.Unrared the DZO aurora rom and edited the updated script with notepadd ++. I changed the model from u8800 to u8800pro (you can copy-paste the 1st line which is what we need from a sakura aurora updater script) and then I rezipped the dzo aurora rom with winrar and it flashed normally.It even booted normally!
I also tried copying the boot.img from DZO release to Sakura release.Again the rom flashed ok.
But the 2 modded roms have these problems in common(other things I tried like camera,messaging were working normally):
1) No bluetooth working (it just writes turning on).Sometimes the phone reboots.
2) No wifi working. Same as bluetooth. Just turning on and phone reboots sometimes. Also tried with new wifi driver option.
I also provided a screenshoot from the second method I used(sakura rom with 3.0.8 kernel).
Anyway.Maybe the day that we can use 3.0.8 kernel in our phones isn't far away from us.Moreover it may also be possible to "port" the x5 aurora to our x5 pro without having to rely any more on the chinese guys(seriously I hate it everytime I flash a sakura rom that i have to change the language ).
Well hope that this thread will be the start for a better aurora rom for the u8800 pro
Click to expand...
Click to collapse
You have to grab dzo kernel 3.0 sources, also extract the config file for 2.6.35 u8800pro kernel (with extract-ikconfig, using zImage from boot.img), and start compiling the 3.0 kernel generating modules for wifi&bt.

I'm also pretty sure that the non working wifi and bt have something to do with the modules (wifi is system/lib/modules I think) and maybe some init.rc and huawei.rc in the boot.img.
I messed a little with them and the results were not pleasant according to my above post. I will definitely try modding again in the future although

i think it would be easier to collect some money from all interested users and pay DZO to make 3.0 kernel for Pro users

rom porter patch beta 1

after too many test i finally made a patch for porting ics stock roms from arc/s (and maybe other xperia 2011 devices) to pur lovely xperia play
it will install all the things that you need for fully working rom on xperia play and deletes the cybershot camera(because it not working on our device)
installation guide:
there are 2 ways for installing
1-if the rom has armo installer
2-if it doesnt have armo installer
if it has armo installer its very easy to use this
here is the instruction
1-open rom zip and ics rom porter.zip files with winrar
2-find the device section in rom zip file
3-drag all the files inside system folder in the ics rom porter.zip to lt28i(xperia arc) folder of rom zip
4-now simply flash the rom zip ans choose xperia arc as your device and everything will be fine
if the rom doesnt have armo installer
do the same thing as i said for the the roms with armo installer but instead of draging the files to lt28i folder drag them to system folder
bugs:
1-no touchpad. i need help for this part.
2-flashable.zip is broken. i need help for this one too
3-build.prob will be replaced with xperia z v5 by markphyton so you wont see the original tweaks after the port
4-some of the roms will give bootloop because they have more space than our system partition. if some one can repartiton a kernel with more system storage it will be great
to do list:
1-making an armo zip with all build.prob form popular roms and the requested roms
2-adding touchpad fix
tested on(working):
1-anzumi : by myself
2-4.1.b.1.13(arc version by jader) : by myself
tested on(not working):
xperia ray 4.1.b.1.13 (touchscreen had some problems)
download link:
http://d-h.st/eJv
thanks to:
1-markphyton : i have taken my files from his rom
2-all the developers of xperia arc :for making roms(that gived me the idea of this patch)
3- xda: all of us know why
4-dev host : i use it for uploading my files
5-xperia play users : for not giving up

reserved
please help me for fixing the bugs
i will start working on gb and jb patch as soon as i get time

waiting for reports now
that all i can do now
if you want to help for completing this patch i need help for these things
1- someone with good knowledge in making armo installer and update.zip files
2-someone for helping me in making build.prob files of requested roms
3-(the moost ipmortant) helping me for fixing touchpads

Smokerman is good in porting roms, you should ask him for touchpad fix
I have basic knowledge of aroma installer and build.prop editing, if i can, i'll help

touchpads
@smokerman
can you help me for fixing the touchpads?

i will release an update soon
things that i changed:
1-fixed the flashable zip
2-im using 4.0.4 ics build.prob instead of xperia z rom by markphyton
jb patch is being tested now
for now i only get bootloops
but im trying to solve the problem
i aslo wanted to make an gb patch but i saw that we will get a little problem in gamepad after porting gb roms from arc
(always open game pad. you cant use touchscreen for gaming anymore in ported gb roms.)

pedyvirus said:
@smokerman
can you help me for fixing the touchpads?
Click to expand...
Click to collapse
i can help for sure..what is the rom? send me the link..i will look into it on the weekend.

well im making a patch for all of the roms
i need to know the way so i can support all the roms that xperia play users want
do you use farenheith's patch for fixing the touchpad in stock based roms?

update coming in less than 30 minutes
im doing the final test
changelog:
1-you don't need to do anything yourself now. just flash the rom + the porter package and everything is finished
2-build.prob replaced with 4.1.b.1.13 for xperia play (made by myself)
3-updated most of the files
to do list:
1-building a 410mg system partition kernel.(i really need help or this one. i don't have enough experience)
2-fixing touchpads (i really dont know how to this because i never fixed touchpads for stock based ics roms. please help me )
also i saw project lard remover script
it can remover build.prob lines
if i can remove xperia arc lines and replace them with xperia play lines most of the bugs will be fixed
but my problem is with different build.prob lines like 4.1.b.1.13 or 4.1.b.0.631 and these things
for now i will add a guide about how to make the build.prob yourself for activating the build.prob tweaks of the rom after applying my patch(for better speed)
update: i got bootloop using the new zip although its working with the old way of porting (extracting the files to the system folder)
i will release it when i fix this problem

pedyvirus said:
update coming in less than 30 minutes
im doing the final test
changelog:
1-you don't need to do anything yourself now. just flash the rom + the porter package and everything is finished
2-build.prob replaced with 4.1.b.1.13 for xperia play (made by myself)
3-updated most of the files
to do list:
1-building a 410mg system partition kernel.(i really need help or this one. i don't have enough experience)
2-fixing touchpads (i really dont know how to this because i never fixed touchpads for stock based ics roms. please help me )
also i saw project lard remover script
it can remover build.prob lines
if i can remove xperia arc lines and replace them with xperia play lines most of the bugs will be fixed
but my problem is with different build.prob lines like 4.1.b.1.13 or 4.1.b.0.631 and these things
for now i will add a guide about how to make the build.prob yourself for activating the build.prob tweaks of the rom after applying my patch(for better speed)
update: i got bootloop using the new zip although its working with the old way of porting (extracting the files to the system folder)
i will release it when i fix this problem
Click to expand...
Click to collapse
is it possible to port ics stock rom of arc to our device(xperia miro) (2012) ?????
a help would be appreciated!!! and i know @pedyvirus you can help me

[Q] build CM7 for Galaxy Y GT-S5363 from source

Hi all.
I have successfully flashed PsychoGame's CyanogenMod 7 ROM for GT-s5360 together with its kernel.
Now i would like to make some changes in the source code of CM7 and to build it from source. Unfortunately i have spent already 4 days without success.
Those are the steps that i did:
1. I have downloaded CM7 source code from git://github.com/CyanogenMod/android.git -b gingerbread
2. I have cloned PsychoGame's totoro device code into /devices/samsubg/totoro
3. i have connected my device via USB and run the script extract-files.sh which successfully extracted all files.
4. during the building i realized that the above script extract all essential files (like camera related), so i cloned PsychoGame's vendor directory from github.com/PsychoGame/android_vendor_samsung_totoro.git
5. now i realized that the file cyanogem_totoro.mk in the directory vendor/cyanogen/products is missing. where i can find a suitable file?
i have found somewhere such file and succeeded to build an ROM, unfortunately CWM does't let me to flash it because the assert command checks that the current device in "totoro" but it fails. i have tried to open the zip file of the ROM and to delete the assert command but CWM still can''t flash the new ROM.
can somebody please help me with some guild about how PsychoGame built his last vertion of CM - CyanogenMod 7 Alpha 5 Release
Thank you very much!

Use percys source code - It has more fixes
Compare build.prop and update binary & scripts for cwm flashing

marcussmith2626 said:
Use percys source code - It has more fixes
Compare build.prop and update binary & scripts for cwm flashing
Click to expand...
Click to collapse
Hi, thank you for the information about gigngerDX. i found the github of the device but can you please tell me where to find all other files to build this rom? do i need to buld it without the kernel? how to do that?
thank you again!

yuripo said:
Hi, thank you for the information about gigngerDX. i found the github of the device but can you please tell me where to find all other files to build this rom? do i need to buld it without the kernel? how to do that?
thank you again!
Click to expand...
Click to collapse
Percys github is
https://github.com/percy-g2
I haven’t compiled a Cyanogen rom before
If you would like to contribute to the building of Cyanogen roms the best person to talk to is percy

I haven’t compiled a Cyanogen rom before
If you would like to contribute to the building of Cyanogen roms the best person to talk to is percy[/QUOTE]
can please somebody explain how to build only Percys ROM without the kernel?
thank you

Hi all.
Can somebody please give a small guide for how to build percy's CM7 ROM from source?
which directories in the CM7 i should replace? does the process of building is the same as with official ports?
Thank you!

[need help!!!] trying to port lenovo a1000 t

hey guys,
im trying to port a rom for Lenovo a1000 t I found this rom for a device called lava iris(with similar MTK 6577 chipset) which is a lollipop themed rom.
need some assistance in editing the build prop.

Since you are porting from a lower processor to a higher , you'll have to edit the build.prop a lot.

revolutionyzer said:
Since you are porting from a lower processor to a higher , you'll have to edit the build.prop a lot.
Click to expand...
Click to collapse
like, I edited the permissions section in the updater-script, I also made some changes in build-prop.
when I flashed it, it got flashed but it was stuck in a boot loop...

Check these :
vnktdpl said:
like, I edited the permissions section in the updater-script, I also made some changes in build-prop.
when I flashed it, it got flashed but it was stuck in a boot loop...
Click to expand...
Click to collapse
* The dpi ( if its more or less than your device's dpi , the ROM won't boot).
* Re-check if you have edited the systemui.apk or the framework.apk such that the values don't match.
* Check if the port has ' update-script ' or ' updater-script '. many new recoveries now don't support the amend format.
* Confirm that the updater-script values are not obsolete.
* Make sure you have an updated recovery.
Good Luck

Launcher
Hello Guys I Am Trying To Port sk17i's Laucher In My S duos 2 ......i am not able to do so.
Can anyone help me on how to port launchers of sony to samsung devices......please reply???:crying:

revolutionyzer said:
* The dpi ( if its more or less than your device's dpi , the ROM won't boot).
* Re-check if you have edited the systemui.apk or the framework.apk such that the values don't match.
* Check if the port has ' update-script ' or ' updater-script '. many new recoveries now don't support the amend format.
* Confirm that the updater-script values are not obsolete.
* Make sure you have an updated recovery.
Good Luck
Click to expand...
Click to collapse
Will check all the values by this weekend
Has it got anything to do with the build fingerprint??
Thanks for ur help

[MIUI] Rom for MDPI devices

I want to build MIUI V6 for my GT-P3100 but only thing is that it's an MDPI device.
I still tried something and here's what I did -->
1) setup patchrom on my Ubuntu.
2) downloaded the miui v6 repo from github
3)used slimkat as base rom for my device ( thank you @Android-Andi)
4)got stuck after issuing the "make fullota" command. I got error regarding multiple configurations while installing framework-res.apk to put folder.
5) I changed the lcd density in build.prop to 240 to at least get a flash able zip although it might not work.
But I still got the same error.
I am following the guide available on github.com/MiCode/patchrom
It is written in broken English but still is quiet clear.
Then to check if I am doing something wrong, I built miui for nexus 5 using the same method and it worked flawlessly.
Could it be due to using slimkat as my base.?
I could use some help here as its my first time with miui and I have never built from source although I will surely build from source if I get enough time and a good guide?

You could try my CM build as base to cross check.