[DEV] AOSP 2.3 Gingerbread for Optimus3D - LG Optimus 3D

If you are not a developer out of here!! these manipulations can definitely brick your phone​
Hi all,
I try to port the source from TI blaze developpement board with OMAP4430 to our O3D.
I followed the tutorial bellow to compile the source of the TI Blaze :
http://www.omappedia.org/wiki/L27.G.3_OMAP4_GingerBread_Release_Notes
(you can see lot of drivers are include in these sources like Graphic, Wifi, etc...)
And Cyanogen tutorial to compile the boot.img with kernel for O3D
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
http://wiki.cyanogenmod.com/wiki/Building_Kernel_from_source
But I have meet some trouble because the O3D is not mtd device (cat /proc/mtd display error) and when I try unpacking the O3D boot.img from Rom Manager Backup the tool display : "header is not present in boot.img" so I can do anything...
I get same error boot.img when I have try to use "dsixda's Android Kitchen" tool.
So for the last i try to use directly compiled sources and kernel of TI blaze in our O3D by creating update.zip file with dsixda's tool but the recovery of Rom Manager can't apply it..
I have recover my backup stock rom with Rom Manager with any problem.
Compiled Sources and kernel of OMAP4430
--- EDIT : Finaly I get working boot.img from O3D ---​
How to get boot.img from O3D
Code:
Optimus3D rooted connected to PC with debug mode activated
>./adb shell
>$
open Super-utilisateur app in O3D
>$ su
Accept root acces popup in Super-utilisateur app in O3D
>#
># cat /proc/partitions (display partitions in your O3D, mmcblk0p5 is the boot.img)
># cat /dev/block/mmcblk0p5 > /sdcard/boot.img (dump to sdcard)
boot.img from O3D with tools​
I have made new boot.img with Blaze kernel and new update.zip with dsixda's tool but RomManager recovery refuse to apply it...
Please Help!
Sorry for my very bad english...
Br,

I've same problem, i'm a noob with lg stuff.
maybe boot.img is similar to optimus 2x, i've asked to lg2x kernel developers but without answer

Finaly i have got working boot.img from O3D! look first post.

Perhaps you have an older version rom manager.
what exactly is the difference between the blaze and the stock kernel?

I think they are same kernel.
Can anyone have brickedO3D can try with fastboot command?
Code:
Reboot the phone into bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
I hope that Ricardo (who have porting CM7 into O3D) write a few words to guide us.

zizouth said:
I think they are same kernel.
Can anyone have brickedO3D can try with fastboot command?
Code:
Reboot the phone into bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
I hope that Ricardo (who have porting CM7 into O3D) write a few words to guide us.
Click to expand...
Click to collapse
So the kernel in gingerbread stills "the same" as actually on Froyo? unveliable!

I mean same for modules (drivers) not for fonctionnality
Sent from my LG-P920 using XDA App

zizouth said:
I mean same for modules (drivers) not for fonctionnality
Sent from my LG-P920 using XDA App
Click to expand...
Click to collapse
SO there arent diference on performance? due drivers are the same...

Ok.... I said same because Blaze and O3D use OMAP4430 SO same mean we can porting gingerbread from blaze to O3D .
Sent from my LG-P920 using XDA App

zizouth said:
Ok.... I said same because Blaze and O3D use OMAP4430 SO same mean we can porting gingerbread from blaze to O3D .
Sent from my LG-P920 using XDA App
Click to expand...
Click to collapse
There is something wrong with the omap4430 DPS, because photos suffer from post processing and high level compression....
THats why because photos looks orrible... maybe there is a value lower than usual...
Same happens with droid 3, with the same processor, have the same "effect" on photos like on O3D....

The goal now is booting the O3D with Gingerbread source from blaze, after that we can rebuild the kernel and check the driver to optimise the pictures.
@|ErosizeD| just send you PM, the Optimus 3D have imx072 sensor (5mp).
Br,

zizouth said:
The goal now is booting the O3D with Gingerbread source from blaze, after that we can rebuild the kernel and check the driver to optimise the pictures.
@|ErosizeD| just send you PM, the Optimus 3D have imx072 sensor (5mp).
Br,
Click to expand...
Click to collapse
Sure at all is an IMX072? i cant find that driver on the Kernel ( official ) from LG.
I answered the pm and waiting another answer.
Thx.

Related

Froyo (2.2) for HUAWEI U8120 [based on AOSP] (under development)

Froyo 2.2.2 port for Huawei U8120.
Maybe it will work on Huawei U8100/U8110 series, but for now it is focused on U8120.
So I dont know what behavior has on U8100 etc.
I must say a big thanks to Tom_G for his awesome work, especially for his froyo port on pulse.Without his work and his posts
on modaco forum, I will not be able to accomplish this.
kalt kaffe's 2.6.29 kernel.
Android 2.2.2 from aosp with some codeaurora changes.
JIT enabled.
Working:
RIL
Audio
GPS
Bluetooth
Wifi
SD card
Sensors
TSCalibration from codeaurora(still the app needs some improvements.For now use a stick or pen when you calibrate the screen)
Not working/bugs:
camera
broken layout on dialer
sdcard cannot be mounted in pc
Its still under development.This is not a finished rom and its not fully tested.
Probably it has problems that I have not yet encountered.So I would not suggest you to try it,
except if you have some experience and you want to help.
I have tried to make it as plain and simple as it gets.No google apps, no bootanimation etc.When all bugs are fixed then I will include them or I will post
my rom.But there are guys that are more expert in rom cooking than me.
Here is a zip with already compiled image files if someone wants to try it and post any bugs/fixes that have found.I have also uploaded here gapps if someone wants them(gmail,market etc)
Code: https://github.com/tas0s
Device tree: https://github.com/tas0s/android_device_huawei_u8120
Try it at your own risk.
Im not responsible for any damage that this may cause.
v.1 initial build
How to build it:
- Install git and gpg (gnupg).
- Download repo - http://source.android.com/source/git-repo.html
$ mkdir android
$ cd android
$ repo init -u https://github.com/tas0s/platform_manifest.git
$ repo sync
- Extract necessary binaries
Some compiled code from the official eclair roms is re-used in froyo. Because some of this code is not opensources I cannot included in the git repository.
The files can be extracted from any u8120 eclair rom.
Place the rom zip in the android directory an rename it to u8120_update.zip
navigate to /device/huawei/u8120:
cd device/huawei/u8120
Then execute from the android directory
$sh device/huawei/u8120/unzip_files.sh
else you can extract them from a working u8120 phone with an eclair rom (check that adb is enabled)
$device/huawei/u8120/extract_files.sh
- Building the system
Once thats done you can start compiling.
Follow the aosp instructions on setting up the build environment. - http://source.android.com/source/download.html
After the environment is setup.
$ cd android
$ source build/envsetup.sh
$ lunch
Select the device u8120.
$ make
I recommend using multiple threads for make if you have a multi core/processor system. By default make will use
1 thread (-j1), set it to use 2*NumberOfCPUsAvailable (so on my dual core -j4). Reducing the number of threads used will reduce the impact on
system performance while the build is running.
The output will be image files in {buildroot}/out/target/product/u8120/. Flash with fastboot.
$ fastboot flash boot out/target/product/u8120/boot.img
$ fastboot flash system out/target/product/u8120/system.img
$ fastboot flash userdata out/target/product/u8120/userdata.img
$ fastboot reboot
For some reason the generated boot.img fails to boot.Maybe I have something wrong about kernel base etc in the BoardConfig.mk.
For now just use the ramdisk.img and the provided kernel and pack it with dsixda's kitchen or with the huawei-u8100 tools that have been posted on the forum.
Then just use fastboot as stated above.
for the future
thnx for the gifts up to it tomorrow
A question about camera problem, only video or all features?
bitye said:
A question about camera problem, only video or all features?
Click to expand...
Click to collapse
The camera fails after a few secs.When an image appears in the preview window.
I have read that the the way that android handles camera has changed in froyo.In cyanogen they are using a libcamera2 (just libcamera with a few changes I think so it can work with the new framework).
As you can see in the BoardConfig.mk I have already include the libcamera2 statements but not the lib
When I manage to get some free time I would try the libcamera2.Maybe until the end of the week or sooner.
Ρε πατριδα αξιζει η rom ή οχι;
tas0s said:
For some reason the generated boot.img fails to boot.Maybe I have something wrong about kernel base etc in the BoardConfig.mk.
For now just use the ramdisk.img and the provided kernel and pack it with dsixda's kitchen or with the huawei-u8100 tools that have been posted on the forum.
Then just use fastboot as stated above.
Click to expand...
Click to collapse
There's a little fix using bootbuilder for U8120, see this post:
http://android.modaco.com/content/t...l-r1-bootbuilder-for-pulsemini-alpha-release/
In the 6th reply you can find the info you could need it
Good luck!
Hi can you tell me on wich kernel it runs?
the 2.6.32 or2.6.29?
and if wiifi is completly fixed no crashes sleep works mac adress?
thanks
calibration fixed at this repo?
larissamafia said:
Ρε πατριδα αξιζει η rom ή οχι;
Click to expand...
Click to collapse
Πατριωτάκι δεν είναι για καθημερινή χρήση ακόμα.Γιαυτό δεν έχω βγάλει και έτοιμη rom.
@Shiftok:
The calibration is integrated in the framework etc but it has some small issues.
As I say in the first post, it needs improvement.
@Cedric123:
Im using 2.6.29 kernel.The wifi works normally.If I remember right and MAC address.
tas0s said:
@Shiftok:
The calibration is integrated in the framework etc but it has some small issues.
As I say in the first post, it needs improvement.
@Cedric123:
Im using 2.6.29 kernel.The wifi works normally.If I remember right and MAC address.
Click to expand...
Click to collapse
ah okey
does this work?
i extract boot.img
put my own zImage in it
repack boot.img
start Phone?
i rly want my own kernel in the ROM with my overclock funtion adn all my +kalt+kaffes optimizations
cedric123 said:
ah okey
does this work?
i extract boot.img
put my own zImage in it
repack boot.img
start Phone?
i rly want my own kernel in the ROM with my overclock funtion adn all my +kalt+kaffes optimizations
Click to expand...
Click to collapse
The kernel Im using is kalt kaffe's kernel.So I think that if you just replace the kernel and the kernel modules in /system/lib/modules you will be fine.
Im uploading now a zip with the compiled images.
It has the problems I mention in the first post etc.
Just an observation.If the calibration isnt correct the screen is always on landscape mode Propably because it gets wrong screen dimensions.So if you see something like that, calibrate your screen with the TSCalibration app.
When im done with the camera, I will fix the calibration bugs.
Hi. Im testing your rom.
I cannot mount the sdcard on computer. when i press to activate usb storage it does nothing in computer.
EDIT - i cant install anything because i dont have a file explorer to see the sdcard files. can you please add one or make an .img with the stock apps
joilaroi said:
Hi. Im testing your rom.
I cannot mount the sdcard on computer. when i press to activate usb storage it does nothing in computer.
EDIT - i cant install anything because i dont have a file explorer to see the sdcard files. can you please add one or make an .img with the stock apps
Click to expand...
Click to collapse
Thank you very much for the feedback joilaroi.I have updated the first post with the sdcard bug.I tried myself and you are right.I will try to fix it.
As I know the stock android froyo hasnt any file manager/explorer.Maybe we can get it from cyanogens.
For now, you can do this.Flash the gapps update that I have in the first post,setup market etc and download a file manager from the market(ex.astro file explorer).
tas0s said:
Thank you very much for the feedback joilaroi.I have updated the first post with the sdcard bug.I tried myself and you are right.I will try to fix it.
As I know the stock android froyo hasnt any file manager/explorer.Maybe we can get it from cyanogens.
For now, you can do this.Flash the gapps update that I have in the first post,setup market etc and download a file manager from the market(ex.astro file explorer).
Click to expand...
Click to collapse
thanks. its what i am doing. if i find anything i will give feedback
EDIT - Cant install superuser and have permissions. it downloads su-2.3.1-bin-signed.zip to sdcard but its corrupted. maybe its better if its already on .img
Im getting more MFLOPS with 633Mhz in this rom than with 691Mhz with the other kernel. its now with 4.45 MFLOPS vs 4.1MFLOPS. Nice
Do you know where i can find su-2.3.1-bin-signed.zip?
Ubuntu 10.10 x64 under W7 VMWare will be enought for compile?
PC: C2D [email protected],2GHZ 8GB RAM
Laptop: Lenovo T410 i5 vPro 2,4GHz Quad Core 4GB RAM
I think yes

Flash Kernel

i have the problem that my sound is to low. i flashed feacore kernel but is not better. i read that a vitaly kernel is better for more higher sound but i dont understand how i install it. There a wrote :
To activate it you need to edit the build.prop file with this :
Code:
debug.gr.swapinterval=0 to build.prop
What the guys mean? Can anyone write a step by step list how i can flash kernel on my KQE stockrom? it seemd that is not the same way like a feacore kernel flash
HHHHEEEEELLLLLPPPPP!!!!!!
asc1977 said:
i have the problem that my sound is to low. i flashed feacore kernel but is not better. i read that a vitaly kernel is better for more higher sound but i dont understand how i install it. There a wrote :
To activate it you need to edit the build.prop file with this :
Code:
debug.gr.swapinterval=0 to build.prop
What the guys mean? Can anyone write a step by step list how i can flash kernel on my KQE stockrom? it seemd that is not the same way like a feacore kernel flash
HHHHEEEEELLLLLPPPPP!!!!!!
Click to expand...
Click to collapse
Ask in your device forum. Anyway for build prop, it is at the system folder and a text file. Find the line that you need to edit and edit it. It its not there, add it.
Sent from my SGH-T959 using xda app-developers app
or has anyone a tip for a kernel which change volume higher which i can flash with odin or cwm or something else. a kernel without change thing in any txt files, only flashing
Goto /system/build.prop and add the line with a text editor. Reboot. That's it.
m_atze said:
Goto /system/build.prop and add the line with a text editor. Reboot. That's it.
Click to expand...
Click to collapse
must i change the kernel before or after this or can i do this anyway
asc1977 said:
i have the problem that my sound is to low. i flashed feacore kernel but is not better. i read that a vitaly kernel is better for more higher sound but i dont understand how i install it. There a wrote :
To activate it you need to edit the build.prop file with this :
Code:
debug.gr.swapinterval=0 to build.prop
What the guys mean? Can anyone write a step by step list how i can flash kernel on my KQE stockrom? it seemd that is not the same way like a feacore kernel flash
HHHHEEEEELLLLLPPPPP!!!!!!
Click to expand...
Click to collapse
to edit build.prop use Notepad++ or a tool from Market to edit it on your phone directly i.e. build.prop Editor then restart phone
usually to flash a kernel you have to enter download/ fastboot mode by a key combination at phone startup and flash it by
Code:
fastboot flash boot boot.img
better is to test the kernel before by this
Code:
fastboot boot boot.img
by this way in case of some problems just restart/remove battery and you revert to previous status (it means the new kernel will boot but never flashes on phone memory)
to work this you need Android SDK and USB drivers
remember : never flash a kernel not made for your phone because of a possible hardware failure
better is to get informed before to do that
ruscan.calin said:
to edit build.prop use Notepad++ or a tool from Market to edit it on your phone directly i.e. build.prop Editor then restart phone
usually to flash a kernel you have to enter download/ fastboot mode by a key combination at phone startup and flash it by
Code:
fastboot flash boot boot.img
better is to test the kernel before by this
Code:
fastboot boot boot.img
by this way in case of some problems just restart/remove battery and you revert to previous status (it means the new kernel will boot but never flashes on phone memory)
to work this you need Android SDK and USB drivers
remember : never flash a kernel not made for your phone because of a possible hardware failure
better is to get informed before to do that
Click to expand...
Click to collapse
what is please the fastboot. i know recovery modus and download modus and what i have to do with this codes????
asc1977 said:
what is please the fastboot. i know recovery modus and download modus and what i have to do with this codes????
Click to expand...
Click to collapse
well take a look here for a tutorial but do not flash anything at this time spend some days searching/ reading about these problems the secret word is search this site has good tutorials for almost everything !
ruscan.calin said:
well take a look here for a tutorial but do not flash anything at this time spend some days searching/ reading about these problems the secret word is search this site has good tutorials for almost everything !
Click to expand...
Click to collapse
ok i taste it and hope i can
So after a lot readings i flashed skyhigh Kernel 1.4d. My Volume is perfekt loud and the System runs :thumbup:
Sent from my GT-I9001 using xda app-developers app
thx for the tip
Has someone a tip for a louder kernel like skyhigh? Its loud but i want louder the sound is good but in navi it can be louder
Sent from my GT-I9001 using xda app-developers app

[DEV][Bootloader] u-boot / omap4boot for P920/P720/P940 and its variant

cross post from http://forum.xda-developers.com/showpost.php?p=33627806&postcount=43
I have only KU5400(the same hardware spec of SU540)
but I can port the omap4boot / u-boot for SU760/SU870 with others help.
LG Prada 3.0 is very similar with the P920/SU760 and P720/P725/SU870
So I cross post it in this dev section.
Now SU540/SU760/SU870 are unbrickable with this omap4boot + u-boot,
and with the new ported u-boot you can even change your kernel too!
milaq said:
thanks for the headsup. any of such is much appreciated (as many stuff for the prada is in korean, chinese, etc.)
these are the opensource gpl components for the ku5400 (which essentially is the p940 for the eastern market). you can get the zips for the p940 here http://www.lg.com/global/support/opensource/opensource-detail.jsp?detailCustomerModelCode=LGP940
this includes the kernel sourcecode which allowed me to build e.g. the cifs. module.
unfortunately we are still st(r)uck with an encrypted bootloader. therefore it is not possible to boot any custom kernel atm.
Click to expand...
Click to collapse
Now it is possible
from http://forum.xda-developers.com/showpost.php?p=32885643&postcount=23
wkpark said:
wkpark said:
Currently Im working on "Unbrickable Optimus 3D"
LG accidently leaked the RSA keys of the P920/SU760 and the signing tool
in the GB source.
http://www.lg.com/global/support/opensource/opensource-detail.jsp?detailCustomerModelCode=LGSU760
(I guess the leaked RSA keys could be the reference keys of the TI signing tool)
so I can signing it's x-loader / u-boot etc.
the leaked RSA keys are used by Prada3.0(SU540 model), P920, SU760, SU870(Korean version of Optimus 3D Cube known as P720)
and the omap4boot port of the Prada3.0 working nicely with the new u-boot based on the SU760/SU870 u-boot source.
http://cafe.naver.com/androidhacker/406 (written in Korean)
Click to expand...
Click to collapse
Finally, the omap4boot port of SU760/SU870 + u-boot port of SU760/SU870 works nicely!!
http://cafe.naver.com/androidhacker/406 (written in Korean)
Instruction
Please see also
http://forum.xda-developers.com/showthread.php?t=1244490
(this method does not recover from broken bootloader at all)
1. Install OMAP4430 USB driver
If you plug your Phone on PC without battery, OMAP4430 device appeared for seconds and then disappeared.
2. start start_fastboot.bat using the omap4boot + u-boot (win32 port of omap4boot included)
1. Turn off your Phone, pull out battery.
2. start "start_fastboot.bat" (it will waiting until phone connected)
3. connect USB cable, the usbboot will start
4. insert battery while the usbboot is waiting
5. unplug USB cable the LG logo will appeard and the fastboot started.
If you have some time please test it with your phone.
Click to expand...
Click to collapse
Im not sure It is working for P940
just test it and report about it. it is almost there to unlock change your bootloader(lk bootloader) to the new u-boot bootloader
to circumvent locked booloader.
original post from http://cafe.naver.com/androidhacker/406 (in Korean)
you can get the latest omap4boot + signed u-boot from.
ChangeLog
●P940 signed u-boot added (11/12) muxtable dumped by milaq
●P920 signed u-boot added (11/12) muxtable dumped by iodak (v1.17a or v1.17b)
●P920: replace mux table with new one (11/28) dumped by kidkoala_uk (v1.18)
- script rewritten
- fixed p920-u-boot_fastboot.bin (v1.18a)
●P920/SU760: revert charging mode support to fix 0% battery (v1.21)
- SU870/SU540/P720 fixup to support charging mode and reboot/poweroff
I have p725. Will this work?
And kernel means zimage or boot.img?
Sent from my LG-P725 using xda premium
p725 is pretty much the same as p720 so yea it should boot into recovery/fastboot. I'm presuming kernel is kernel.img from a dump or some sort.
I can boot into fastboot, but not get u-boot binary to work and boot unsigned boot/recovery.
got P920 with SU760 ics port edition here
P940 confirmed working
http://forum.xda-developers.com/showpost.php?p=33650068&postcount=46
booting unsigned recovery/boot images not yet tested
What really does that give us?
Thank You
Nice to see you are still working with the omap4boot project wkpark. :good:
Believe me your tool has helped me in so many cases (apart from porting ICS) that it really is priceless.
Once again THANK YOU for your hard work on this and most of all because i am not afraid to brick my phone anymore.
It's your hard work that made me come back to the O3D party and try new stuff.
You are great.
where is his recorgnized DEv/Contributer imo he Deserves it MOds?
defcomg said:
where is his recorgnized DEv/Contributer imo he Deserves it MOds?
Click to expand...
Click to collapse
Exactly as above.
Hi, great you are.
Btw, I wonder how can get signed file, example: p920-u-boot_fastboot-signed.bin while p920-u-boot_fastboot.bin maybe can get from LG opensources files.
And after extract files from KDZ, which file is uboot, x-loader, gpt.....
http://forum.xda-developers.com/attachment.php?attachmentid=1451220&d=1351868951
Thanh_GSM said:
Hi, great you are.
Btw, I wonder how can get signed file, example: p920-u-boot_fastboot-signed.bin while p920-u-boot_fastboot.bin maybe can get from LG opensources files.
And after extract files from KDZ, which file is uboot, x-loader, gpt.....
http://forum.xda-developers.com/attachment.php?attachmentid=1451220&d=1351868951
Click to expand...
Click to collapse
Please read the original post first.
LG leaked their RSA signing keys and the signing tool
Thats why it can be born
Sent from my LG-KU5400 using xda app-developers app
Dexter_nlb said:
I can boot into fastboot, but not get u-boot binary to work and boot unsigned boot/recovery.
got P920 with SU760 ics port edition here
Click to expand...
Click to collapse
LG changed their RSA sign keys for the ICS firmware except the root RSA key.
so we have to re-sign its x-loader(1st bootloader) to work with this u-boot
for SU760/SU870 devices and I guess P920/P720 too.
attached file include resigned x-loader (LG no more use x-loader/u-boot, LG changed their bootloader to the LK bootloader) for SU760 ICS.
you can try this attached resigned x-loader with the new u-boot.
(or dump your x-loader/u-boot/boot.img and attach it for resigning)
wkpark said:
you can try this attached resigned x-loader with the new u-boot.
(or dump your x-loader/u-boot/boot.img and attach it for resigning)
Click to expand...
Click to collapse
thanks, i will send you the files after work, since i already extracted them at home, but i could not use them for much.
i will include a recovery.img if you can sign that, so we have a 100% solution for ClockWorkMod on p920.
and thanks again for work put into this on your side
wkpark said:
(or dump your x-loader/u-boot/boot.img and attach it for resigning)
Click to expand...
Click to collapse
I attached a zip with x-loader, u-boot and a fresh build of cwm with cm9 repo and based on lg ics stock kernel
(x-oader and U-Boot are both taken from xbsalls su760 ics port to p920)
wkpark said:
LG changed their RSA sign keys for the ICS firmware except the root RSA key.
so we have to re-sign its x-loader(1st bootloader) to work with this u-boot
for SU760/SU870 devices and I guess P920/P720 too.
attached file include resigned x-loader (LG no more use x-loader/u-boot, LG changed their bootloader to the LK bootloader) for SU760 ICS.
you can try this attached resigned x-loader with the new u-boot.
(or dump your x-loader/u-boot/boot.img and attach it for resigning)
Click to expand...
Click to collapse
confirmed working.
if i use your xloader,uboot and boot.img it starts normally.
would it mean its possible to make workaround so it can boot unsigned boot/recovery then?
here is the recovery img i made for p920, i could only test its not working, using "adb reboot recovery" and it starts looping.
i seem not able to start from any key combo here? and regular shell "reboot recovery" did not trigger it either.
but anyways it bootloops when this image is used.
can you try and sign it and lets see how it works. ( i assume you are not uploading your compiled binaries+rsa used for signing, so we can experiment and make changes faster) (i did download lg release but do not see any rsa keys included)
wkpark said:
LG changed their RSA sign keys for the ICS firmware except the root RSA key.
so we have to re-sign its x-loader(1st bootloader) to work with this u-boot
for SU760/SU870 devices and I guess P920/P720 too.
attached file include resigned x-loader (LG no more use x-loader/u-boot, LG changed their bootloader to the LK bootloader) for SU760 ICS.
you can try this attached resigned x-loader with the new u-boot.
(or dump your x-loader/u-boot/boot.img and attach it for resigning)
Click to expand...
Click to collapse
Anyone pls share me Flashtool for Su870, I use flashtool 1.1 when choose SU870.dll soft crash. Use omap tool phone has SW download mode but can't find tool to up Ap.bin to have stabel bootloader.
Thanks much.
Dexter_nlb said:
...
(i did download lg release but do not see any rsa keys included)
Click to expand...
Click to collapse
RSA keys and the ift signing tools found at the old GB tarball of SU760
Iwill post or edit the exact site again~!
http://www.lg.com/global/support/opensource/opensource-detail.jsp?detailCustomerModelCode=LGSU760
download SU760(Optimus3D)_Android_GingerBread_SU760V20c.zip
extract it => Optimus3D_KR-SKT_Android.tar.gz =>
●OSLT/LGE_SU760_Gingerbread/SU760(Optimus3D)i_Android_Gingerbread/Optimus3D_KR-SKT_Android/bootable/bootloader/x-loader/ift : the ift tool + RSA keys
●reference : reference settings used by the ift tool
Sent from my LG-KU5400 using xda app-developers app
wkpark said:
RSA keys and the ift signing tools found at the old GB tarball of SU760
Iwill post or edit the exact site again~!
http://www.lg.com/global/support/opensource/opensource-detail.jsp?detailCustomerModelCode=LGSU760
download SU760(Optimus3D)_Android_GingerBread_SU760V20c.zip
extract it => Optimus3D_KR-SKT_Android.tar.gz =>
●OSLT/LGE_SU760_Gingerbread/SU760(Optimus3D)i_Android_Gingerbread/Optimus3D_KR-SKT_Android/bootable/bootloader/x-loader/ift : the ift tool + RSA keys
●reference : reference settings used by the ift tool
Sent from my LG-KU5400 using xda app-developers app
Click to expand...
Click to collapse
thanks,
and i just downloaded "SU760(Optimus 3D)_Android_froyo_SKT" so thats why i failed finding anything.
i am on it, and hope to be able to continue testing here.
---------- Post added at 08:43 PM ---------- Previous post was at 07:54 PM ----------
you seem to have done some digging into the ift parameters to use for "boot.img"? right
do i really need to configure new files setting offsets and chosing specific sigs here?
only reference settings i see are those for MLO which is not boot.img based.
can you help with the command line parameters used here?
wkpark said:
you can try this attached resigned x-loader with the new u-boot.
Click to expand...
Click to collapse
Did you changed anything inside the attached boot.img?
And if you changed how did you resigned it?

[mt6573][kernel source] ALPS development environment

I can't post to the development section because i'm new here, so feel free to move this thread
I've found some really interesting things around the internet.
I got an mt6573 device half a year ago(Star A920) and ported over some ROM'S.
Now i wan't to get deeper, the problem is the sourcecode from mediatek. Alcatel has released its sources (OT918d, OT991d) which are mt6573 phones. For building the mediatek Android, we need other files, which were not included in their sources.
Now it's getting interesting:
I've found this on the internet:
www.github.com/fanjunwei/mytqe
It seem like this is the development environment for the ALPS MTK builds.
I also found this "How-To" for the environment.
http://wenku.baidu.com/view/86c3bad749649b6648d74748.html
..and the kernelsource for the alcatel 991d.
www.sourceforge.net/projects/alcatel/files/OT_991D_20120725.tar.xz/download
I'm trying to build an android from sources, maybe we are successfull together.
If I'm wrong - correct me, please.
edit: sucessfully build Android 2.3.6 from sources!!! ( ALPS.GB.FDD2.MP.V4.5 , e1101_v73_jbl1ctp_a515, Kernel Version 2.6.35.7 )
Whoa bro !
can u make a guide how to compile from sources ?
Chrizzly92 said:
I can't post to the development section because i'm new here, so feel free to move this thread
I've found some really interesting things around the internet.
I got an mt6573 device half a year ago(Star A920) and ported over some ROM'S.
Now i wan't to get deeper, the problem is the sourcecode from mediatek. Alcatel has released its sources (OT918d, OT991d) which are mt6573 phones. For building the mediatek Android, we need other files, which were not included in their sources.
Now it's getting interesting:
I've found this on the internet:
www.github.com/fanjunwei/mytqe
It seem like this is the development environment for the ALPS MTK builds.
I also found this "How-To" for the environment.
http://wenku.baidu.com/view/86c3bad749649b6648d74748.html
..and the kernelsource for the alcatel 991d.
www.sourceforge.net/projects/alcatel/files/OT_991D_20120725.tar.xz/download
I'm trying to build an android from sources, maybe we are successfull together.
If I'm wrong - correct me, please.
edit: sucessfully build Android 2.3.6 from sources!!! ( ALPS.GB.FDD2.MP.V4.5 , e1101_v73_jbl1ctp_a515, Kernel Version 2.6.35.7 )
Click to expand...
Click to collapse
it's cool!!
can you make a tutorial for comiling android from source?
look at the second link i've posted. there is an complete tutorial. (setting up a virtual machine, for example). you have to use "./makeMtk baoxue r" to build the komplete system with recovery, boot.img etc.
then u need some cust_xxx.c files from the alcatel sources, or the build fails. ( copy them manually to the folders, shown in the error logs of the builds).
I have to get deeper into it, maybe compiling a new kernel for our devices. Sure I will make an Tutorial, but at first i have to know exactly what im dooing. I hope someone else can help me, so we can get the best results out of it.
Chrizzly92 said:
I can't post to the development section because i'm new here, so feel free to move this thread
I've found some really interesting things around the internet.
I got an mt6573 device half a year ago(Star A920) and ported over some ROM'S.
Now i wan't to get deeper, the problem is the sourcecode from mediatek. Alcatel has released its sources (OT918d, OT991d) which are mt6573 phones. For building the mediatek Android, we need other files, which were not included in their sources.
Now it's getting interesting:
I've found this on the internet:
www.github.com/fanjunwei/mytqe
It seem like this is the development environment for the ALPS MTK builds.
I also found this "How-To" for the environment.
http://wenku.baidu.com/view/86c3bad749649b6648d74748.html
..and the kernelsource for the alcatel 991d.
www.sourceforge.net/projects/alcatel/files/OT_991D_20120725.tar.xz/download
I'm trying to build an android from sources, maybe we are successfull together.
If I'm wrong - correct me, please.
edit: sucessfully build Android 2.3.6 from sources!!! ( ALPS.GB.FDD2.MP.V4.5 , e1101_v73_jbl1ctp_a515, Kernel Version 2.6.35.7 )
Click to expand...
Click to collapse
Congratulations buddy, a tut by your experience shall be highly helpful
Xperia Neo V? thas NOT an mt6573 based Phone. maybe you have a chinese fake or something, then u could be right here.
Great work! what is the latest news??
Header is missing
Hi pals,
the Problem is that the repack-MT6577.pl assumes tht the needed Header information is already in the zImage, which is because normally you would pass the zImage which you extractet from a original boot.img to the script. So it will not boot until you append the Header to the zImage,
i extracted the Header with dd and build a zImage with it. Will try that out now
Edit:
the header is the first 512bytes of the original zImage
Edit2:
It boots with my custom kernel Forgot to mention my device: Alcatel OT998 (sold by Base in Germany, almost the same as OT997/OT997D)
Edit3: sorry Wrong Thread, as it is a different MTK-Platform but the info correct for you also i guess
HUELK said:
Hi pals,
the Problem is that the repack-MT6577.pl assumes tht the needed Header information is already in the zImage, which is because normally you would pass the zImage which you extractet from a original boot.img to the script. So it will not boot until you append the Header to the zImage,
i extracted the Header with dd and build a zImage with it. Will try that out now
Edit:
the header is the first 512bytes of the original zImage
Edit2:
It boots with my custom kernel Forgot to mention my device: Alcatel OT998 (sold by Base in Germany, almost the same as OT997/OT997D)
Edit3: sorry Wrong Thread, as it is a different MTK-Platform but the info correct for you also i guess
Click to expand...
Click to collapse
Again nice work!
Can you a somewhat detailed tutorial??
balamu96m said:
Again nice work!
Can you a somewhat detailed tutorial??
Click to expand...
Click to collapse
hi ,
sorry sure i can give detail, well at least i try:
1. Get the zImage from a working boot.img eg with unmkbootimg or split_bootimg.pl
2. The needed header is in the first 512bytes of the zImge extract that:
dd if=<zImgeOrig> of=header bs=512 count=1
3. Append the header to the build zImage
3.1 dd if=header of=zImageMod
2.2 dd if=zImageCustom of=zImageMod seek=512
4. Repack Boot.img with repack-MT65xx.pl as known
5. Flash through CWM:
I flash it to my device over the adb console after putting the Image on the sdcard with adb push:
dd if=/sdcard/<boot.img> of=/dev/bootimg
NOT TESTET: flashing through the cwm update-script with write_raw_image("boot.img", "/dev/bootimg");
Thats the way i got it up to boot, but i have some Problems with the permission of pvrsrvkm.ko know, i building CM10 for my Device if anyone wants to know...
i guess you can easily modify the repack-MT6577.pl to include that for fresh kernels, i will have a look at that in the next days.
Greetz HUELK
<-----THANKS Button
HUELK said:
hi ,
sorry sure i can give detail, well at least i try:
1. Get the zImage from a working boot.img eg with unmkbootimg or split_bootimg.pl
2. The needed header is in the first 512bytes of the zImge extract that:
dd if=<zImgeOrig> of=header bs=512 count=1
3. Append the header to the build zImage
3.1 dd if=header of=zImageMod
2.2 dd if=zImageCustom of=zImageMod seek=512
4. Repack Boot.img with repack-MT65xx.pl as known
5. Flash through CWM:
I flash it to my device over the adb console after putting the Image on the sdcard with adb push:
dd if=/sdcard/<boot.img> of=/dev/bootimg
NOT TESTET: flashing through the cwm update-script with write_raw_image("boot.img", "/dev/bootimg");
Thats the way i got it up to boot, but i have some Problems with the permission of pvrsrvkm.ko know, i building CM10 for my Device if anyone wants to know...
i guess you can easily modify the repack-MT6577.pl to include that for fresh kernels, i will have a look at that in the next days.
Greetz HUELK
<-----THANKS Button
Click to expand...
Click to collapse
Bad that I can't give a double thanks for your highly useful post!
Building CM 10 = awesome!
I would like to know more....cm10 with dual sim support??
Thanks again!
balamu96m said:
Bad that I can't give a double thanks for your highly useful post!
Building CM 10 = awesome!
I would like to know more....cm10 with dual sim support??
Thanks again!
Click to expand...
Click to collapse
Hi,
building cm10 with dual sim support will be complicated as there is no support for it in cm10 , my device has no dual sim but nfc instead. i now almost got it up running, the pvrdrv loads now correctly but there is some problem with some framework files and BOOTCLASSPATH variable. I think i will get it fully up today. Was awake till 6 o'clock on this .
HUELK said:
Hi,
building cm10 with dual sim support will be complicated as there is no support for it in cm10 , my device has no dual sim but nfc instead. i now almost got it up running, the pvrdrv loads now correctly but there is some problem with some framework files and BOOTCLASSPATH variable. I think i will get it fully up today. Was awake till 6 o'clock on this .
Click to expand...
Click to collapse
Great again! Hope you complete it soon!
I would somehow try to port it.....!
Hi thanks for your procedure.
I tried , i can boot but the display is very slowly. I tried with this source code https://github.com/wiko-sources/cink-king
I have a wiko cink king with mt6577.
Have you ever used repack-MT65xx.pl for mt6577?
TY
HUELK said:
hi ,
sorry sure i can give detail, well at least i try:
1. Get the zImage from a working boot.img eg with unmkbootimg or split_bootimg.pl
2. The needed header is in the first 512bytes of the zImge extract that:
dd if=<zImgeOrig> of=header bs=512 count=1
3. Append the header to the build zImage
3.1 dd if=header of=zImageMod
2.2 dd if=zImageCustom of=zImageMod seek=512
4. Repack Boot.img with repack-MT65xx.pl as known
5. Flash through CWM:
I flash it to my device over the adb console after putting the Image on the sdcard with adb push:
dd if=/sdcard/<boot.img> of=/dev/bootimg
NOT TESTET: flashing through the cwm update-script with write_raw_image("boot.img", "/dev/bootimg");
Thats the way i got it up to boot, but i have some Problems with the permission of pvrsrvkm.ko know, i building CM10 for my Device if anyone wants to know...
i guess you can easily modify the repack-MT6577.pl to include that for fresh kernels, i will have a look at that in the next days.
Greetz HUELK
<-----THANKS Button
Click to expand...
Click to collapse
@HUELK
Where you able to boot? I would like to try the process on a mtk6573
Kudos!
myphoneuser said:
@HUELK
Where you able to boot? I would like to try the process on a mtk6573
Kudos!
Click to expand...
Click to collapse
would like to help here too, already working on rom development for mt6573...
HUELK said:
3. Append the header to the build zImage
3.1 dd if=header of=zImageMod
2.2 dd if=zImageCustom of=zImageMod seek=512
Click to expand...
Click to collapse
The zImageMod and zImageCustom is confusing me. Can you differentiate between them??
Thanks.
boots now
Hi,
NEWS: got it up to boot cm10! yes display is slow for me too, but its a start
greetz huelk
---------- Post added at 11:14 PM ---------- Previous post was at 11:12 PM ----------
balamu96m said:
The zImageMod and zImageCustom is confusing me. Can you differentiate between them??
Thanks.
Click to expand...
Click to collapse
hi yes, the zImage Custum is the zImage wich resides in arch/arm/boot/zImage after you build the kernel, the zImage Mod is the Output file which will be inside the boot.img that you will flash
HUELK
---------- Post added at 11:17 PM ---------- Previous post was at 11:14 PM ----------
balamu96m said:
The zImageMod and zImageCustom is confusing me. Can you differentiate between them??
Thanks.
Click to expand...
Click to collapse
As i told you my device is a mt6577 but the changes you need should be the same, can you send me an original boot.img of your device, i will have a look.
HUELK said:
Hi,
NEWS: got it up to boot cm10! yes display is slow for me too, but its a start
greetz huelk
---------- Post added at 11:14 PM ---------- Previous post was at 11:12 PM ----------
hi yes, the zImage Custum is the zImage wich resides in arch/arm/boot/zImage after you build the kernel, the zImage Mod is the Output file which will be inside the boot.img that you will flash
HUELK
---------- Post added at 11:17 PM ---------- Previous post was at 11:14 PM ----------
As i told you my device is a mt6577 but the changes you need should be the same, can you send me an original boot.img of your device, i will have a look.
Click to expand...
Click to collapse
Thanks for clarifying my doubt!
And great to know that CM 10 booted :highfive: !
here is my boot.img : here
btw, how can the slow touch response be solved bro ??
Chrizzly92 said:
would like to help here too, already working on rom development for mt6573...
Click to expand...
Click to collapse
Hey bro,
i'm asking this, because you had cloned the full MT6573 source........Can you upload the following folders from the source's root :
Kernel
Mediatek
I need it to try my hands at the MT6573 kernel!
Thanks in advance!

[GUIDE][CM Port][ MT6589 only] Port CyanogenMod 10.2/11 for all MT6589 devices

@chrmhoffmann compiled first ever CyanogenMod for his Wiko Stairway which is a MT6589 device and made it possible for other MT6589 users to taste CM. Since then many are porting it to their MT6589 device and many are requesting to make a port for their device. So, I have made a guide here to make it easier for them to port themselves. You should give proper credits to respected developers and hit thanks before posting on XDA.
NOTE:I have made a list of already ported CM roms in #2 post below , if your device is not listed there download any of the ported CM rom and follow this guide to port it to your device
This is the guide to port CM 10.2/11 for all MT6589 devices.Read carefully and follow each step correctly otherwise CM won't boot
Tools Required:
1) Archive Manger (winrar,winzip,7zip)
2) boot.img Unpack Repack Tools
http://forum.xda-developers.com/showthread.php?t=1587411(For Linux)
http://forum.xda-developers.com/showthread.php?t=2036528(For Windows)
NOTE:
For CM 11 the same proceedure is followed but the stock boot.img must be having kernel with binder.c patched and SELinux enabled (This feature can be bypassed but binder.c patch is must otherwise CM 11 won't boot)
Guide:
1) First get your stock rom and download any ported CM 10.2/11 rom from #2 post below
2) Get boot.img from your phone(stock rom) and boot.img from downloaded CM-ROM.zip
3) Unpack both of them to get ramdisk and kernel of both.
4) Repack CM's ramdisk and stock kernel (your phone's) to get a new boot.img
5) Extract system folder from your phone(stock rom) and system folder from downloaded CM-ROM.zip
6) Copy and replace these files from stock to CM,
=> /lib/modules/ -> all files
=> /framework/ -> CustomProperties.jar
mediatek-common.jar
mediatek-framework.jar
mediatek-op.jar
secondary-framework.jar
=> Also all the files mentioned in the below link ( A great thanks to Kashifmin for providing this )
https://github.com/kashifmin/android_device_micromax_a116/blob/master/proprietary-files.txt
7) Now take the modified CM system folder and the new boot.img and make a zip archive with normal deflate compression ( are default in 7zip)
8) Open the newly created zip archive and downloaded CM-rom.zip .Now drag and drop the META-INF and file_contexts from downloaded CM-rom.zip to newly created zip archive.
9) Now flash the new zip using recovery (CWM/TWRP)
10) Enjoy !!
CREDITS:
@michfood for his Boot unpack/repack utils for WINDOWS.
@bgcngm for his Boot unpack/repack scripts for LINUX.
@kashifmin for his proprietary-files.txt
@kashifminfor guiding me.
@chrmhoffmann For bringing the first ever CM10.2 for an MT6589 device.
@XpLoDWilD
@Dr-Shadow
OmniROM project.
Available CM port builds for MT6589
CM 10.2 builds:
Wiko Stairway / MMX Canvas 4 (A210) -> http://forum.xda-developers.com/showthread.php?t=2467400
MMX Canvas HD (A116) -> http://forum.xda-developers.com/showthread.php?t=2673367
XOLO Q700/Q700i -> http://forum.xda-developers.com/showthread.php?t=2675963
LAVA 458Q / XOLO Q600 / CROSS A88 -> http://forum.xda-developers.com/and...-cross-a88-t2814034/post54103404#post54103404
CUBOT GT99 / Cherry Apollo / XYZ X1 -> http://forum.xda-developers.com/and...cubot-gt99-t2834832/post54542482#post54542482
CM 11 builds:
Wiko Stairway / MMX Canvas 4 (A210) -> http://forum.xda-developers.com/showthread.php?t=2676086
MMX Canvas HD (A116) -> http://forum.xda-developers.com/showthread.php?t=2676896
ACER liquid e2 v370 -> http://forum.xda-developers.com/showthread.php?t=2766290
MMX Canvas Magnus (A117) -> http://forum.xda-developers.com/canvas-magnus/development/rom-cyanogenmod-11-canvas-magnus-a117-t2790957
MMX Canvas 2+ (A110Q) / Fly IQ450 -> http://forum.xda-developers.com/mic...-2-cyanogenmod-11-port-canvas-2-plus-t2750867
MMX Canvas Turbo (A250) -> http://forum.xda-developers.com/canvas-turbo/development/rom-cyanogenmod-11-canvas-turbo-t2780905
If CM for any MT6589 device is missing here , PM me. I will add here.
i try but always stuck on boot splash, no boot up.. pleash help thanks
Uhm.... I guess I can't port cm10.2 over stock jb4.2.1 rom, right?
I ask because I first looked for cm10.1 to port, but to my surprise, I didn't find any cm10.1 builds for any mt6589 on google.
@polfrank you can port CM 10.2 using stock 4.2.1 rom. First you have to download any CM 10.2 Rom from above and follow guide to port. You can even port above CM 11 Roms if you have a working kernel source for your device
Sent from my iris458Q using XDA mobile app
@limam27 boot loop occurs if 1) boot.IMG is badly repacked 2) any file is missing from your device stock rom which has to be copied to CM ROM as mentioned in the guide. Check them first . Also Check whether you are getting errors during unpack and repack of boot.IMG.
Sent from my iris458Q using XDA mobile app
Hmm, I'm stuck on my brand's splash screen too. I don't get to see the boot animation, and as you mention I get errors during both unpacking and repacking. But it said that the file was copied though.... I 'll search for another way to upack and repack on Google and come back.
Edit: pfff, seems like the only way to do it on windows was the one you provided...
Which CM version you are trying to port ?
If have Linux use unpack scripts to unpack/repack boot.img
Windows always gave me errors.
Sent from my iris458Q using XDA mobile app
4shreyas said:
Which CM version you are trying to port ?
If have Linux use unpack scripts to unpack/repack boot.img
Windows always gave me errors.
Sent from my iris458Q using XDA mobile app
Click to expand...
Click to collapse
I chose the CM10.2 from Wiko Stairway.
Yes, I'm now setting a Virtual Machine with Linux 14. And I'll try the unpack scripts from there. Let's see...
UPDATE:
OK, i ended up doing a clean install of ubuntu.
I upacked both images SUCCESS.
I repacked using stock kernel.img and CM ramdisk folder, SUCCESS.
I Install boot.img through CWMrecovery, it now gets past boot logo(Cubot white screen) but I think that before it would enter bootanimation the screen becomes a weird mass of colours, as if the screen was broken. It lasts for 1 second, then it restarts.
ps. I can successfully go to recovery with power+volUP If i like..
Any ideas?
You should get CM boot animation even if you use stock boot.img but won't boot. Did u correctly replace all required files in rom ? Do a clean one. Check if you can get logcat. Send me the logs
Sent from my iris458Q using XDA Premium 4 mobile app
4shreyas said:
You should get CM boot animation even if you use stock boot.img but won't boot. Did u correctly replace all required files in rom ? Do a clean one. Check if you can get logcat. Send me the logs
Sent from my iris458Q using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I think I used wrong kernel.img. I repacked, will flash soon and come back to report.
EDIT: Are you sure that I have to use the META-INF folder from the CM rom? It gives me status 7 error.... (I also used the META-INF from a rom for my device, unfortunatelly it uses aroma, but it seems to install properly..)
EDIT2: I think that now I repacked the correct components of boot.img. It seems to get past the Cubot white splash screen, but after this, I get a black screen, but I can see that the screen is on, I can see the backlight. [I will try again with the CM META-INF-->still fails]
ps. Seems like I have to learn how to get a logcat if I wanna make use of your help... I'll be back in some hours.
----------------------------------------------------------------------
To sum up:
I have packed the new boot.img and replaced the needed files in the rom.
1) With the CM's META-INF folder I can't install, status 7 error.
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "stairway || getprop("ro.build.product") == "stairway"
E: Error in /sdcard/experiment/cm102last.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
2) With the stock rom's META-INF it seems to install propperly.
After reboot from recovery it goes to a black screen and stays there. I tried to logcat (adb logcat -v long > port.txt) but it just says:
[email protected]:/home/pol/Documents/sdk/platform-tools# adb logcat -v long > port.txt
- waiting for device -
Click to expand...
Click to collapse
If i write adb devices it says :
[email protected]:/home/pol/Documents/sdk/platform-tools# adb devices
List of devices attached
0123456789ABCDEF offline
Click to expand...
Click to collapse
When I am on recovery I get:
[email protected]:/home/pol/Documents/sdk/platform-tools# adb devices
List of devices attached
CWM-ZTE-V967S recovery
Click to expand...
Click to collapse
---------------------------------------------------------------------------------------------------------------
CONCLUSION: I managed to install the new boot.img and rom but it stops on a black screen, right after it passes from the white logo screen. And now, I need your ideas...
ps. I repeated the porting process from the beginning to make sure that I didn't make any mistakes... again, the same result.
--------------------------------------------------------------------------------------------------------------
NEW UPDATE: IT BOOTED!! but how....? Here it is........
I just replaced the boot.img from the wiko stairway flashable zip with the boot.img I created with repacking my phone's kernel and CM's ramdisk.
SO, I just changed the boot.img !!!! Testing.......
-------------------------------------------------------------------------------------------------------------
Testing results: buggy mobile network and sound not working. I guess this is why all those files are needed to be copied. I think I ll start copying..... But I wonder...what did I do wrong earlier while copying,,,?
You will get status 7 error because it is a security feature which doesn't allow to flash one device's ROM to other. You have to edit using any text editor and remove first line in the update-script found in meta-inf/com/Google/android/
Also don't use other rom's meta-inf as they have different symbolic links which may not boot the device.
Your phone's modules will be different from wiko's. That's why you got buggy audio and network. Replace all the mentioned files.
sent from my iris458Q using XDA mobile app
Okay, after some hours of trial and error I copied all the porting files provided in the op, except 2:
-libjpeg.so - When I port this from stock, Cm boots, but cannot show images, every single image, including the bootanimation is black.
-libmedia.so - When I port this from stock, Cm stays in the bootanimation forever. (No bootloop, just bootanimation forever)
-------------------------------------------------------------------------------------------------------------------------------------
The "extra" bugs that I have are:
1. No sound from the speaker (but yes in the headphone).
2. Weak signal. I don't know if this is normal. It has 1 bar and sometimes it has 0 and says no service. Also, the name of the tile in the QuickSettings is 20201 (weird...). I also get a message when the rom boots and it says: "Restricted Access changed. Data service is blocked." This appears sometimes at random too.
3. USB storage doesn't work through Android.... ( I don't know if this is normal too). When I plug it on PC it just charges. (Note: I now see that other devices have this problem too. I found a partial workaround in the MMX Canvas HD cm10.2 section)
PS. Would logcat help in any of these problems?
--------------------------------------------------------------------------------------------------------------------------------
I moved on, and took some adb logcats.
1. I took the audio.txt as follows: started logcat, pressed play on the apollo widget, pressed pause, stopped logcat
2. I took the signal.txt as follows: started logcat (while on Airplane mode), disable Airplane mode (from quickSettings tiles), enable mobile data, disable mobile data, enable Airplane mode, stop logcat
I'll look at logs meanwhile I never had problem with signal, speaker audio and images. To get USB storage working add these lines to build.prop and reboot
persist.sys.usb.config=mass_storage,adb
persist.sys.usb.config=mtp,adb
For signal issue , did u replace your modem.IMG in CM ROM ?
For image issue try those 2 files from wiko ROM.
Edit:
Try to freshly port CM once again as given in guide with some changes in meta-inf and build.prop as I gave. If you still have problems then report here.
I couldn't debug audio log but in signal log > network is disconnected as data is enabled and even it's saying messaging settings are false. There may be issue with modem.img
sent from my iris458Q using XDA mobile app
Thanks for the USB storage tip. At least the internal SD can be seen now by the computer.
Images are OK now with the lib of CM.
For signal issue I copied modem.IMG from stock into the CM rom, and still having problems.
Btw, I just created a new thread for my device, I hope this is not a problem.
http://forum.xda-developers.com/and...cubot-gt99-t2834832/post54542482#post54542482
Cheers !! I'll add your device in the ported list. As I said previously all necessary files should be replaced in CM to be bug free except major BT,camera,hwcomposer,FM,GPS,2nd Sim bugs.
Also USB storage is buggy now as SD card is unmounted in mass storage mode but not mounted on PC and when disconnected from PC it doesn't get mounted and you have to reboot to get it working on android. Also mtp mode sometimes doesn't work
sent from my iris458Q using XDA mobile app
Nice!
The only file missing is /lib/libmedia.so and I 'm starting to think that this may be the cause of the sound bug. But when I copy it from the stock rom, I get boot problems...
Anyway, thanks for your help, and sorry that I messed up/spammed your thread. I think the most important part of the job is done..! Good job!
EDIT: I think I sort of fixed the mobile network issue. I used a modem.img from another version of stock rom and it seems to work. However I still get the error "Restricted Access changed. Data service is blocked." But I have full signal and 3G! It's something!
Restricted access notification occurs if you enable or disable data and turn on/off airplane mode and phone and it is not a issue I think. It may be cyanogenMod's security message or something.
Also try libmedia.so from other
Stock rom which you said above.
sent from my iris458Q using XDA mobile app
thanks for repley
4shreyas said:
@limam27 boot loop occurs if 1) boot.IMG is badly repacked 2) any file is missing from your device stock rom which has to be copied to CM ROM as mentioned in the guide. Check them first . Also Check whether you are getting errors during unpack and repack of boot.IMG.
Sent from my iris458Q using XDA mobile app
Click to expand...
Click to collapse
I want to port my device MT6589T JB 4.2 to cm11 kitkat but I do not know how to activate the binder c in the boot.img.
I've tried without a binder c install process always aborted status 7
please help thank you
Hello @limam27
@Iimam27 said:
I want to port my device MT6589T JB 4.2 to cm11 kitkat but I do not know how to activate the binder c in the boot.img.
I've tried without a binder c install process always aborted status 7
please help thank you
Click to expand...
Click to collapse
You can't patch binder.c from boot.IMG. You must be having kernel source for your device and you must patch binder.c in kernel. If you don't have kernel source then its almost impossible to get KitKat. See if your device clones have kernel source for their device. Else look for almost similar specs device with same processor. My device has mt6589m but no source from vendor. I used similar mt6589m device's source to build kernel. Now CM 11 is booting but no display due to different GPU config. So it's really hard if you don't have source. Try with CM 10.2 first .
EDIT- Previously I have told why you get status 7 error. So read whole thread before posting here. Good luck
Sent from my iris458Q using XDA Premium 4 mobile app

Categories

Resources