[DEV] Building ROM with closed Qualcomm sources (vendor_qcom_proprietary) - Android Software/Hacking General [Developers Only]

Chinese internet contains a lot of closed QCOM sources (proprietary, modem, tz, etc).
To find these sources type in the google/bing:
Code:
AU_LINUX_ANDROID_JB_MR1_RB1.04.02.02.050.175_msm8974_JB_MR1_RB1_CL3847824_release_AU
At the beginning of June 2016, I decided to try to build a CM11 , using the QCOM proprietary source codes.
My device is based on msm8228 (overclocked msm8226).
Build result: a fully working CM11 with QCOM libs compiled by UBERTC 4.8.5.
CM11 ROM download (250 MB)
My local manifest: https://github.com/jsr-d10/local_manifest/blob/cm-11.0/d10f-qc.xml#L38
Repositories with suffix "-qc" using with QCOM sources.
QCOM proprietary for msm8226: magnet:?xt=urn:btih:313a2f9bc1f2b1fe3ad830e9dfbf4d4432fea384&dn=qcom_msm8x26_vendor

May I send you a pm?

I wrote yesterday converter fo libchromatix files.
It converts binary file to h-file.
https://github.com/remittor/chromatix2c

I was able to make a fully working firmware!
Even the camera began to work!
Sources:
kernel: https://github.com/jsr-d10/android_kernel_jsr_msm8226/commits/mm-qc
proprietary: magnet:?xt=urn:btih:313a2f9bc1f2b1fe3ad830e9dfbf4d4432fea384&dn=qcom_msm8x26_vendor
Reversed sensor Toshiba t4k37ab: http://v2.pikacode.com/jsr-d10/andr...ontroller/modules/sensors/sensor_libs/t4k37ab
Source codes are actively removed by QCOM employees.
To search for these on the Internet, I advise you to do so:
1) search on google.com archive "android_vendor_qcom_proprietary-msm8226-kk.zip"
2) search on github.com file "t4k37ab_lib.c"

Installing camera SONY imx214 into budget phone
Device: innos D10F (msm8228)
Original camera: Toshiba t4k37ab (13MP)
Installed camera: SONY imx214 (13MP)
Camera replacement procedure takes 5 minutes.
Black module: t4k37ab
Metallic module: imx214
Camera imx214 was taken from broken OnePlus One.
Kernel sources: https://github.com/jsr-d10/android_kernel_jsr_msm8226/commits/mm-qc
Camera libs sources: magnet:?xt=urn:btih:313a2f9bc1f2b1fe3ad830e9dfbf4d4432fea384&dn=qcom_msm8x26_vendor(android_vendor_qcom_proprietary branch msm8226-kk)

Strange this didn't get enough interest, i mean, these are "old" (up to SD800 if i understand well) but they should be useful even for newer socs. However great demonstration, remittor

Thanks for the work.
Am really interested on this but it is hard to find some information.
I have the idea to start a full open source rework of the camera hal but am not good enough to work on this alone.
Am looking for people who can help me

Related

Huawei C8600 Kernel Discussion - Version 2.6.32

Recently, I compile the kernel version of 2.6.32 based on Kernel source from Huawei V858.
Everything works except the wifi. The ar6002.ko cannot be insmod.
Then I compiled the Artheros kernel from Huawei website. It cannot insmod too.
But after merge these 5 symbols in msm_sdcc.c, it can be loaded, and 1.2V pull up success.
But Wifi still cannot be bring up. And ar6000_avail_ev seems not called.
Anyone has any idea?

[Q] [DEV] [HELP] Compile a android kernel for Huawei CM980

Hello friends, I'm part of a group of novice developers who are developing a CyanogenMOD9 for Huawei CM980, a phone sold in Venezuela with the following hardware features:
SoC: MSM7627b @ 800 Mhz ARMv6 - CPU-Core: ARM1136EJ-S
Touchscreen: Synaptics-ts-CMI.1
LCD: Innolux ILI9481
Camara: mt9p017 @ 5 MP with AF (BRAND: Aptina)
NAND Flash: Hynix
Compass AKM8975 (BRAND: Akemi)
Wifi / FM / BT Broadcom BCM4329 (BRAND: Broadcom)
BMA150 3-axis Accelerometer (BRAND: Bosch)
Magnetic field sensor AK8973 (BRAND: Akemi)
Proximity sensor CM3602 (BRAND: Capella)
Now we know that this phone has great hardware level like the Huawei C8651, until the point that can be identified as board id: MSM7x27_C8651.VerD, we used this because the official kernel source for this phone has not been released, and isn't possible obtain the build information from /proc/config.gz. Now to the point:
I tried to build the kernel on several occasions, I have the source of CyanogenMod (2.6.37) and Huawei (2.6.35) kernel, I built the modules and drivers are required and I have compiled the code without errors and for the right architecture (the command file to zImage tells me that file is a ARM little-endian), I joined and created a boot.img using the original rom initramfs, but the cellphone refuses to boot.
My questions are:
1) What can be going to not work?
2) Is there any way to make a more specific kernel compilation in which the use of force and optimization for ARMv6 ARM1136EJ-S?
Your ideas and suggestions are welcome, greatly appreciate any help the.
PD: Sorry for my bad English
Here is the kernel my friend
Yukiteru said:
Hello friends, I'm part of a group of novice developers who are developing a CyanogenMOD9 for Huawei CM980, a phone sold in Venezuela with the following hardware features:
SoC: MSM7627b @ 800 Mhz ARMv6 - CPU-Core: ARM1136EJ-S
Touchscreen: Synaptics-ts-CMI.1
LCD: Innolux ILI9481
Camara: mt9p017 @ 5 MP with AF (BRAND: Aptina)
NAND Flash: Hynix
Compass AKM8975 (BRAND: Akemi)
Wifi / FM / BT Broadcom BCM4329 (BRAND: Broadcom)
BMA150 3-axis Accelerometer (BRAND: Bosch)
Magnetic field sensor AK8973 (BRAND: Akemi)
Proximity sensor CM3602 (BRAND: Capella)
Now we know that this phone has great hardware level like the Huawei C8651, until the point that can be identified as board id: MSM7x27_C8651.VerD, we used this because the official kernel source for this phone has not been released, and isn't possible obtain the build information from /proc/config.gz. Now to the point:
I tried to build the kernel on several occasions, I have the source of CyanogenMod (2.6.37) and Huawei (2.6.35) kernel, I built the modules and drivers are required and I have compiled the code without errors and for the right architecture (the command file to zImage tells me that file is a ARM little-endian), I joined and created a boot.img using the original rom initramfs, but the cellphone refuses to boot.
My questions are:
1) What can be going to not work?
2) Is there any way to make a more specific kernel compilation in which the use of force and optimization for ARMv6 ARM1136EJ-S?
Your ideas and suggestions are welcome, greatly appreciate any help the.
PD: Sorry for my bad English
Click to expand...
Click to collapse
here is the original kernel from huawei:
jeffersonlicet.*com/article/android/31/Kernel-CM980-Liberado.html

[ROM][4.1.2] Goclever TAB R70 (RK2926)

This is (to my knowlodge) the very first CM port to Rockchip RK292x device.
This is a beta build of CM10 (Android 4.1.2)
Things that work: (Updated 02-13-2014)
- CM10
- Wifi
- Audio
Things that don't work
- camera (captures few frames, then freezes)
- rotation is off by 90 degrees
Install
CWM flashable image
Download:
Check the download tab above: cm_rkr70sdk-ota-eng.markus
Added working boot and recovery (CWM 6.0.2.8) images next to ROM
Extras
http://goo.im/gapps/gapps-jb-20121011-signed.zip (Gapps)
Please give Your feedback and if someone can chip in, it would be a real help!
XDA:DevDB Information
CM10 port for RK292x device, a ROM for the Android General
Contributors
Shmarkus
ROM OS Version: 4.1.x Jelly Bean
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Alpha
Beta Release Date: 2014-03-03
Created 2014-02-01
Last Updated 2014-02-13
Just tested this on my Beneve Kids Tablet, it has the same specs as Goclever TAB R70 except the screen resolution is higher. Apart from some trouble with sensors for rotation its working really well. Its way faster than stock rom. Looking forward to future releases.
oddhap said:
Just tested this on my Beneve Kids Tablet, it has the same specs as Goclever TAB R70 except the screen resolution is higher. Apart from some trouble with sensors for rotation its working really well. Its way faster than stock rom. Looking forward to future releases.
Click to expand...
Click to collapse
Thanks for Your feedback. I'm back doing this project after a small break! The camera rotation error is caused by kernel. Rockchip guys have done a dirty hack somewhere!
If You'd like, I could try to build a kernel from source for you. But I can only do this if You can pull Your kernel config from the device
Code:
adb pull /proc/config.gz ./
This feature can be disabled though (I know my device doesnt support this and it's a pain to figure out kernel config from scratch)
@Shmarkus I know I'm resurrecting an old thread here but I was wondering if I would be of some help whether as a tester or developer for this ROM of yours (Great work BTW). I have a question though is it stable enough for daily usage...
FLAmbuRNE1 said:
@Shmarkus I know I'm resurrecting an old thread here but I was wondering if I would be of some help whether as a tester or developer for this ROM of yours (Great work BTW). I have a question though is it stable enough for daily usage...
Click to expand...
Click to collapse
Hi! I think this ROM isn't just quite daily driver ready. All my sources are available at github! I haven't really done anything since the release of this ROM, so it is all quite foggy today The main stumbling block for me was the kernel, since I didn't find the correct drivers for the touchscreen (the rest worked quite ok). @FLAmbuRNE1 if you have time and motivation, then I can give you some pointers but I won't be developing it myself.
Alright man, thanks. I'll try my best but this will be my first time developing from actual sources (Thanks mediatek).

[ROM][Official][4.4.4] SlimKat Stable 6.0

thanks to tylog for the news : ( http://forum.xda-developers.com/showpost.php?p=53806120&postcount=6397 )
Stable 6.0
Download
http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1035-4-4
New Gapps Thread
http://forum.xda-developers.com/slimroms/general/gapps-official-slim-gapps-trds-slimkat-t2792842
Ok we've gotten to a point where we think we are stable, at least for most devices
New devices: I9500 (for real this time)
Dropped devices: Yuga (dm no longer owns it)
Changes
Fix Topmost feature
Fix battery charging percentage color applier
Fix Battery stat app
TRDS: Fix Volume panel background
Add ASCII logo to edify script
more translations
Device Specific
Geeb: Update fingerprint for 4.4.4
G2: update loki,recovery: Add a loki script as a recovery transformation step,Fix the loki product name
Yuga: use retail name for PRODUCT_MODEL,re-enable "Eject SD card" option,yuga: fix /dev/input/event11 permission,major upstream CM
hammerhead: major kernel upstream,update to LINUX 3.4.94
manta: update fingerprint to 4.4.4
flo: update fingerprint to 4.4.4
HLTE: Move to common msm8974 repo,fixup permissions for inputs,disable world_phone overlay,Fix GPS problem for CDMA variants
msm8974-common: remove network modes overlay,Fix audio context sepolicy error
deb: Update fingerprints to 4.4.3 OTA
m8: add bdroid config,enable LCD KCAL sysfs support,LCD_KCAL: Color Control driver for M8,lcd_kcal: Correct the copyright information
Known Bugs:
Smdk4412: Graphical glitches on some games (might be just n7100/t0lte/i9300) //Might need changing to specific devices. Sent email to Kona tabs and i925 tab dm
Devices running as Weekly
I9500
I9300
T0lte family
N7100
I9100 (Inactive Dm)
N7000 (Inactive DM)
hi can someone help me, what elementalx do I need for nexus 7 2013, I tried one but it broke my wifi, I tried the dePRIMAtor fix but that didn't work, I only want the Tap to wake feature working so if there's an easier way or a different working kernel can some one advise me please thanks
Neptune Pine
angelcalibur said:
thanks to tylog for the news : ( http://forum.xda-developers.com/showpost.php?p=53806120&postcount=6397 )
Stable 6.0
Download
http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1035-4-4
New Gapps Thread
http://forum.xda-developers.com/slimroms/general/gapps-official-slim-gapps-trds-slimkat-t2792842
Ok we've gotten to a point where we think we are stable, at least for most devices
New devices: I9500 (for real this time)
Dropped devices: Yuga (dm no longer owns it)
Changes
Fix Topmost feature
Fix battery charging percentage color applier
Fix Battery stat app
TRDS: Fix Volume panel background
Add ASCII logo to edify script
more translations
Device Specific
Geeb: Update fingerprint for 4.4.4
G2: update loki,recovery: Add a loki script as a recovery transformation step,Fix the loki product name
Yuga: use retail name for PRODUCT_MODEL,re-enable "Eject SD card" option,yuga: fix /dev/input/event11 permission,major upstream CM
hammerhead: major kernel upstream,update to LINUX 3.4.94
manta: update fingerprint to 4.4.4
flo: update fingerprint to 4.4.4
HLTE: Move to common msm8974 repo,fixup permissions for inputs,disable world_phone overlay,Fix GPS problem for CDMA variants
msm8974-common: remove network modes overlay,Fix audio context sepolicy error
deb: Update fingerprints to 4.4.3 OTA
m8: add bdroid config,enable LCD KCAL sysfs support,LCD_KCAL: Color Control driver for M8,lcd_kcal: Correct the copyright information
Known Bugs:
Smdk4412: Graphical glitches on some games (might be just n7100/t0lte/i9300) //Might need changing to specific devices. Sent email to Kona tabs and i925 tab dm
Devices running as Weekly
I9500
I9300
T0lte family
N7100
I9100 (Inactive Dm)
N7000 (Inactive DM)
Click to expand...
Click to collapse
Willl this Rom work on the Neptune Pine smart watch???
SlimKat in MI3.
The SlimKat that I have in my MI3, although it is still under development, is perfect. I had never had the opportunity to have a rom Slim. The only thing was the screen resolution to 370 in build.prop and should be at 450 to make it all right on the screen (as in the original roms).
You know who could tell? Thank you very much and congratulations for your work. :good:
Will try this on my G2 when it starts working.

[ROM][7.1.2][UNOFFICIAL] LineageOS-14.1 Xiaomi Redmi Note 4 MTK

Whats Working ?
Hardware acceleration
Wifi
Bluetooth
Vibration
Audio
MTP and Mass Storage modes
Doze
Offline charging
RIL (Calls,Msg)
Operator name
GPS
Hotspot
Known issues:
Fingerprint Scanner
Camera(install camera fix patch with twrp for solve problem)
Rotation Sensor (work partially)
SD-Card
Calls
Source code: https://github.com/LineageOS
Device Tree: https://github.com/SamarV-121/android_device_xiaomi_nikel
Credit & Thanks to :
(SamarV-121, Team_MAD , Verevka , sandstranger , vgdn1942 , DeckerSU , Danielhk , jonnyxda , Moyster , adrianom)
ROM OS Version: 7.1.2
ROM Kernel : Linux 3.18.x
Changelog: 2017-07-30
Calls [RIL] Fixed
Some Improvements
2017-08-12
Changelog:
Data Fixed
Add AGPS
Fix power off Alarm
Fix Traffic counter
Optimization of battery consumption and performance
Update sources
********Do Wipe System and Data with Twrp and install Rom*********
Download Link : https://www.androidfilehost.com/?fid=961840155545588213
Camera fix patch : https://www.androidfilehost.com/?fid=745425885120756749
Video From Rom : https://www.youtube.com/watch?v=BTs-ELobJOQ
Source : http://en.miui.com/thread-723898-1-1.html
Note: i am not tested this rom...
Bug: Could not play *.flac audios
This bug caused by mediacodec, especially MTKOMX. Only MediaTek Android 6.0 (author: cofface) has not have this bug so far.
This file may help you fix "Could not detect SD card" bug.
WARNING: You need to add a code which can create /nvcfg in /init.mt6797.rc
For fingerprint sensor and screen rotation, you may add some vendor blobs such as lib_fpc_tac_shared.so (/system/lib)(/system/lib64). Then you need to add some codes in /init.project.rc .
Here are some files unpacked from MediaTek AOSP Android 6.0 (MRA58K).
WARNING: DO NOT directly copy /init.project.rc, otherwise GSM baseband and CDMA baseband will not be loaded such as in this picture.
This device (nikel) has two basebands rather than a baseband. It means that you need to add some settings which is about CDMA baseband.
This screenshot comes from MediaTek AOSP Android 6.0 (MRA58K).
Some source codes that are about hardware:
https://github.com/archermind/MTK_X20_BASE_AOSP (MT6797 Based AOSP) (6.0)
https://github.com/mt6797/hardware (hardware)
https://gitlab.com/mt6797/vendor (vendor)
https://github.com/helio-x20/linux (kernel)
so will we have a nougat rom for this phone without these bugs or not ?
joead2010 said:
so will we have a nougat rom for this phone without these bugs or not ?
Click to expand...
Click to collapse
No. There has been no update for this ROM since last summer. There will never be a working Nougat ROM for this phone
Noter2017 said:
No. There has been no update for this ROM since last summer. There will never be a working Nougat ROM for this phone
Click to expand...
Click to collapse
I said to hear that
it would not be possible to correct these errors ... I wanted so much to use a custom Rom in my redmi
Enviado de meu Redmi Note 4 usando Tapatalk
port
can we port rom from custom rom vernee apollo lite which have helio x20 processor too?
raflyou said:
can we port rom from custom rom vernee apollo lite which have helio x20 processor too?
Click to expand...
Click to collapse
Yes, we can. But be careful especially kernel version. If you port a wrong kernel, this device will bootloop (Logo (about 1s)>reboot>Logo (about 1s)>reboot>...).
Kernel version (nikel): 3.18.22+
Kernel version (Vernee Apollo Lite): 3.18.22/3.18.35/3.18.9x ...
Any chance we get project treble running on redmi note 4 mtk? Seems very promising in theory
jellybean13 said:
For fingerprint sensor and screen rotation, you may add some vendor blobs such as lib_fpc_tac_shared.so (/system/lib)(/system/lib64). Then you need to add some codes in /init.project.rc .
Here are some files unpacked from MediaTek AOSP Android 6.0 (MRA58K).
WARNING: DO NOT directly copy /init.project.rc, otherwise GSM baseband and CDMA baseband will not be loaded such as in this picture.
Click to expand...
Click to collapse
hey, do you mind clarifying what 'codes' to add to /init.project.rc? Also, I can't figure out how to unpack the files from the .img you attached. Thanks
canaryfire said:
hey, do you mind clarifying what 'codes' to add to /init.project.rc? Also, I can't figure out how to unpack the files from the .img you attached. Thanks
Click to expand...
Click to collapse
ImageFactory can unpack boot.img
canaryfire said:
hey, do you mind clarifying what 'codes' to add to /init.project.rc? Also, I can't figure out how to unpack the files from the .img you attached. Thanks
Click to expand...
Click to collapse
Some comments in /init.project.rc
You can use kernel sources instead of prebuilt files.
https://github.com/mohancm/android_kernel_lenovo_A7010a48 (require port)
jellybean13 said:
ImageFactory can unpack boot.img
Click to expand...
Click to collapse
Thanks for the help so far! I got the libs from ranstar74's build and moved them to /system/lib and /system/lib64, but it seems that /init.project.rc does not exist after install.. I tried creating it with the codes that you showed and I tried putting those codes in init.rc and the fingerprint sensor still doesn't work. There is meta_init.project.rc, but it seems to be different, would that work?
canaryfire said:
Thanks for the help so far! I got the libs from ranstar74's build and moved them to /system/lib and /system/lib64, but it seems that /init.project.rc does not exist after install.. I tried creating it with the codes that you showed and I tried putting those codes in init.rc and the fingerprint sensor still doesn't work. There is meta_init.project.rc, but it seems to be different, would that work?
Click to expand...
Click to collapse
You'll never get scanner working on 7.0+ because theres no sources of fingerprint hal,you can get it work only in 6.0 based roms.Same for camera btw...
ranstar said:
You'll never get scanner working on 7.0+ because theres no sources of fingerprint hal,you can get it work only in 6.0 based roms.Same for camera btw...
Click to expand...
Click to collapse
Device:
https://github.com/mt6797/device
Kernel:
Source1: https://github.com/mt6797/kernel-3.18
Source2: https://github.com/helio-x20/linux/tree/helio-x20
Vendor:
https://gitlab.com/mt6797/vendor ((Zip) Size: 2.47GB)
jellybean13 said:
https://gitlab.com/mt6797/vendor
((Zip) Size: 2.47GB)
Click to expand...
Click to collapse
It's working rom?
---------- Post added at 09:47 AM ---------- Previous post was at 09:12 AM ----------
Guys the calls working?

Categories

Resources