Hey, im looking for info about porting aosp (clean from aosp - 5.1.1_r2 version lollipot) to sm-t365 samsung tablet.
I run into multiple problems while trying (i didn't found the correct source for the nfc nxp chip not in the aosp sources, not in the samsung opensource web (i checked the kk and the ll versions - in opensource . samsung . com / reception / receptionSub . do ? method = sub & sub = F & searchValue = sm-t36 ) and not in nxp site (i found over there only the sources for pn7150 and pn7120 , i have pn547 chip).
How can i do the porting properly?
What are the needed steps and where do i get the necessary files?
Thanx
Related
With the exception of a modified hardware/qcom/display for legacy support this is a straight compile of Codeaurora's 4.1.1 (M76XXUSNEKNLYA2515)
http://threader.zapto.org/experimental/s7/codeaurora-4.1/102113/boot.img
http://threader.zapto.org/experimental/s7/codeaurora-4.1/102113/system.img.bz2
Unpack system.img.bz2
Flash with fastboot.
fastboot erase cache
fastboot erase userdata
fastboot flash boot boot.img
fastboot flash system.img
Not working:
Phone.
Bluetooth.
Sensors.
Wifi.
Working:
display
Kernel source:
https://github.com/threader/Huawei_S7_kernel_2.6.35
Hardware/qcom/display & devices/huawei/s7
http://threader.zapto.org/experimental/s7/codeaurora-4.1/sources-buildprefs/
Android sources:
https://github.com/threader/
Credits
Asturel, dzo. Thanks!
Boot image will boot asturels CM10 http://goo.im/devs/asturel
A boot image to boot asturels cm10.1 on 10x http://threader.zapto.org/experimental/s7/cm10.1/boot.img
Hi,
Went trough my old disks and uploaded everything i could find to https://mega.co.nz/#F!3wAQxDDL!2MgX7NmPBUIOVYP3zLYElw
Upper Folders:
* Original Firmware (Norway - Sweden - Brazil)
Norway = 103 Sweden = ? Brazil = 101-2 || Brazil boot image can be used with Norway rom, a 101 will loose its camera when presented with the wrong version kernel
Seemingly ancient Huawei update app, for updating 2.1 to 2.2. ( In Firmware Folder )
* Original Froyo and Emotion Kernel sources
Seemingly lost from Huawei's site. Could not find the 2.6.32 kernel last i checked let alone 2.6.28
* Broadcom bcm4329 sources
Original upload by Huawei, suggest downloading all and comparing. Remember there being a problem with either of the files
Dev folder:
* Device-huawei-s7 / Hardware-qcom-display-s7 ( Codeurora 4.1.x / CM 10 (?) / JB)
To be compiled against a "M76XXUSNEKNLYA2515" Codeurora 4.1.x / CM 10 (?) / JB)
* Kernels
Latest 2.6.32.61 from me, suggest using the original config instead of the mine.
Earlier release of 2.6.35.14 - Should be stable but suggest github - https://github.com/threader/Huawei_S7_kernel_2.6.35 - again use your config!
What i think is the original Huawei S7 kernel just fixed to compile.
Codeaurora msm-2.6.32 - which i suggest grabbing this amongst others, if you want to start from scratch with kernel-2.6.32-FROYO.tar.bz2
* Broadcom - bcm4329
Unknown status, suggest a thorough look and compare against original Huawei - bcm4329 release.
* Codeaurora 4.1.x ( 4.1.1 ) M76XXUSNEKNLYA2515
Latest two experimental builds i could find
Codeurora-4.1.x-s7-nov-6-2013 was actually the last 4.1.1 date i found in my build directory, this may be wrong, but i uploaded what sees to be the last build i did really, but it might require 21-10-2013 boot.img to work.
h ttp://www.hacktohell.org/2013/07/mediatek-mt6589-complete-source.html#.UrAQj_QW0bI
This is the source code for mt6589 soc . Can now cyanogenmod and other roms be ported? if not please explain .
Dude u read the edit int the op.those are not full source..
Hey Fellow XDA Developers.....Sorry I've to start this thread due to a reason that I've toggled everywhere in existing guides & Threads but I'm fed up that none of them is comprehensive or Correct...
OK I want some of the answers to (I guess extremely silly) questions
Q.1:: So I want to Develop a Custom Kernel on Backbone of Aurora and stock Linux kernel. Any possible way how can i extract, mod ;
edit and add and recompile it.... any specific tools,links.(already visited android authority)
Q.2::Can anyone tell me where i can find additional "".KO"" files(Kernel object libraries/kernel expander)
Q.3::Since most apps have a <uses sdk> so it means somewhere in /root directory the sdk is save right so latest android like
lollipop has new revision of sdk. is his possible to copy kitkat and lollipop sdk files to system from Android studio(I know this
is the worst joke or some sort of question asked by a fool but still out of curiosity of my never ending thirst of development)
Q.4::Nowadays I'm in a Quest to develop a Custom ROM since my phone is "NOT EVEN UNOFFICIALLY PORTED".I tried finding
my phones stock ROM[Panasonic P81][Xda Forum of P81 is totally Crap](Some stupid guy modded and made it worst than
sh!t).I heard Rumour that my clone "Cool pad 7320" has CM 6 or 11 Successfully installed/flashed but referring to the website
I tried and Bricked it. (Ironically I'm now using that modded coolpad ROM by Xdafirmware.com)
Q.5::Can U Tell if I can flash Stock Marshmallow Nexus image on my phone!!!!!!!![greatest question] I'M Die Hard Fan Of
Marshmallow And can Brick my phone infinite times getting it..
Q.6::What happens if I Replace my Stock kernel with original Linux (the pc one) (that im having.) . Will it work,add functionality ,or
brick it.
=======System Specs=======
Device Name : Panasonic P81
Boot loader : Unknown.(Same for all Panasonic I guess)
Processor : Mediatek MT6592 @ 1.7 Ghz 8 cores 32 bit archetecture
Kernel version: 3.4.39 [email protected] #1
Custom Build : 1012
Android Version: 4.2.2 jellybean apl 17
RAM: 1 GB
MODEL/BUILD ID: EB-90S055P81V1012
Runtime: Dalvik(libdvm.so) version 1.6.0
Motherboard: yulong92_wet_jb9
Radio: MOLY.WR8.W1315.MD.WG.MP.V19.P2
SELinuxermissive by default (stock)
CPU ABI- Armeabi
Features: swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpv4 idiva idivt
BOGO MIPS: 1685.91
Kernel Feature: Entropy & SMP PREEMPT
Toolchain: dcc version 4.6.x-google 20120106(pre release) (GCC)
**NEON SUPPORTED
==eMMC==
Name: K7XVMB
==sensors==
1: BOSCH BMA056 3-AXIS Accelerometer
2:ROHM RPR 410 PROXIMITY SENSOR
3:ROHM RPR 410 LIGHT SENSOR
==GRAPHICS==
VENDOR-ARM
GPU Renderer- MALI 450 MP
OPENGL: OpenGL ES @.0
ShaderpenGL ES GLSL ES 1.00
*****Eagerly Awaiting for answers . Please a positive cheer ups will be appreciated I'm noob here :angel::highfive: [Not that extreme I've enough xp regarding flash,boot loop,recovery,porting etc. ]*****
Most guides for this are found here,
http://forum.xda-developers.com/chef-central/android
If none there are helpful, then I'm at a loss for a suggestion. There's a lot of resources in that link. :good:
You are gonna run into a ton of issues. First off the chip that device uses never releases kernel source. So that will put a stop to your work real fast.
As for some of the other questions.
No you can't put a stock Linux kernel on the device. Kernels are made for each devices. They don't all work on every device.
zelendel said:
You are gonna run into a ton of issues. First off the chip that device uses never releases kernel source. So that will put a stop to your work real fast.
As for some of the other questions.
No you can't put a stock Linux kernel on the device. Kernels are made for each devices. They don't all work on every device.
Click to expand...
Click to collapse
Hey my kernel by default is stock aosp Linux version 2.4.39
Tanmoy Mitra said:
Hey my kernel by default is stock aosp Linux version 2.4.39
Click to expand...
Click to collapse
And the original revision of Linux I'm referring is the one created by Linus torlavads that is backbone of PC platform of Ubuntu, KDE and many other operating system. OK Aurora kernel is out of date and no support is available but I'm impressed by or rather moved by its spects and I feel that it is fantastic kernel to start with....... I just want to modify and continue from where he left a full stop to support. Many user still uses Aurora and there exist a hidden community about it.I WANT TO PROVIDE THE UPDATES AND SUPPORT OR WANTED TO DEVELOP A NEW KERNEL. OK on my 15 day research over kernel I found it is best kernel with a negligible cons and many features to opt within. Tell me which kernel can give me 16+ Governors and 9 scheduler and 6 TCP congestion algorithm to play with. With NEON and selinux support init.d and best battery backup among other kernel without even compromising a bit on graphics and rendering......Tell me
Tanmoy Mitra said:
And the original revision of Linux I'm referring is the one created by Linus torlavads that is backbone of PC platform of Ubuntu, KDE and many other operating system. OK Aurora kernel is out of date and no support is available but I'm impressed by or rather moved by its spects and I feel that it is fantastic kernel to start with....... I just want to modify and continue from where he left a full stop to support. Many user still uses Aurora and there exist a hidden community about it.I WANT TO PROVIDE THE UPDATES AND SUPPORT OR WANTED TO DEVELOP A NEW KERNEL. OK on my 15 day research over kernel I found it is best kernel with a negligible cons and many features to opt within. Tell me which kernel can give me 16+ Governors and 9 scheduler and 6 TCP congestion algorithm to play with. With NEON and selinux support init.d and best battery backup among other kernel without even compromising a bit on graphics and rendering......Tell me
Click to expand...
Click to collapse
I know what you are talking about and it won't work. Each device kernel is different from each other. Android is not the same as a desktop Linux set up. Also kernels differ from one pc to another.
As for those options you will have to add them yourself.
Again without the kernel source For that device being released you are out of luck.
zelendel said:
You are gonna run into a ton of issues. First off the chip that device uses never releases kernel source. So that will put a stop to your work real fast.
As for some of the other questions.
No you can't put a stock Linux kernel on the device. Kernels are made for each devices. They don't all work on every device.
Click to expand...
Click to collapse
Well I set to build it and yes I FOUND THE SOURCECODE FINALLY!!! although not for my board and device... While my device is Panasonic P81 and board is: yulong92_wet_jb9 the source was of Gionee Elife S5.5 same processor and features. But marked as board: vanzo92_wet_jb9
I don't think it will be issue, also found out that my device can support FDD LTE (VoLTE too) but needs a port from mt6595(helio x10)
[MT 6575 = LTE BASEBAND OF MT6590 + OCTA CORE architecture of MT6592 WHICH I USE]
So your help will be appreciated:good::laugh:
Sent from my Panasonic P81 using XDA Labs
I am trying to port Andriod O to my Oneplus 5. I know there is an existing and well-worked LOS/MOKEE for Oneplus 5, but I am trying to do it myself entirely, using the existing one as an example for study. So I can port LOS/MOKEE to my Xiaomi 8 SE ( sirius, SDM710).
I get some information that if you are porting Andriod to a device having no existing LOS/MOKEE supported, you can start it with CAF AOSP. And this is what I am doing.
Now, what I can do is :
* knowing Oneplus 5's OOS-BETA12 is based on LA.UM.6.4.r1-06100-8x98.0 (CAF AOSP version)
* use repo to download a single project of LA.UM.6.4.r1-06100-8x98.0 (like project under device/ , hardware/ , vender/ )
How can I build a device tree for LOS/MOKEE from CAF-AOSP device tree?
Is there someone can help me? Thank you!
nobody.....?
Dear all,
I successes compiling a kernel (and combined with twrp) for M3 note. Please find the source git below.
Youtube show the new kernel boot with twrp is as below:
https://youtu.be/ps6ngeDPiHc
Code:
PLEASE BE WARNED CRACKING MIGHT MAL-FUNCTIONING YOUR DEVICE. I AM NOT RESPONSIBLE TO ANY DAMAGE MADE. ALSO I AM NOT LIABLE TO ANY OF CAUSE OR DAMAGE MADE.
First of all, kernel tree is available for developer:
https://github.com/99degree/android_kernel_m3note.git
branch: m3note_20190813
Its based on a v3.18.35 kernel from below, credit goes to this git user
https://github.com/mtkkkk/mt6755_wt6755_66_n_kernel.git
TWRP image is provided here, licensed GPL, freely redistribute accordingly to GPL:
http://s000.tinyupload.com/index.php?file_id=68522221679326215968
Short summary:
The branch contain changes to make the Image.gz-dtb kernel code base working with twrp 3.3.0 (ramdisk.gz from elephone P9000)
changes included:
(1)PMIC sm5414 sm5414.c/sm5414.h/charger_hw_sm5414.c
(2)various Makefile and adding missing include path
(3)DT overlay support ported from newer branch
(4)LCM ported from MEIZUOSC/m681/
(5)various other small changes.
The idea to add kernel dt-overlay support is due to it's hacky HW's fw nature, as the combination of (1)unlocked boot-loader, together with (2)Chinese version of lk, both caused dtb overwrite by internal copy, detailed below.
With fastboot boot feature enabled, there come a very development unfriendly feature, aka dt overlay, happened before booting into the kernel. Thus the kernel might not work with many LCM (the info passed down by kernel CMDLINE within DTB node) from other model varient (included but not limited to M681A, M681G, M681C). I have to mention that the m681-intl (at least three variant) version of update.zip DOES NOT have a fastboot boot enabled lk(.bin) provided.
The full list of M3 note variant is as below:
http://deviceinfohw.ru/devices/uplo...0&brand=brand598&filter=m3+note&submit=Search
The base tree is cloned from https://github.com/mtkkkk/mt6755_wt6755_66_n_kernel.git so i dont have any idea what happened in the code. So no garentee the security/feature completeness.
Finally I would conclude the current kernel tree branch with working feature.
(0)unlock bootloader
(1)LCD/LCM
(2)PMIC charger partly supported (sm5414, bq24196) so remove usb cable wont reboot
(3)touch (gt9xx, ft5x0x)
(4)RTC/TEMPRETURE/WDT
(5)MMC/SD (internal/external)
(6)Vibrator
(7)USB mtp/adb
The sm5414 code is port from the original m681 tree from meizuosc, thus not working very well with newer mtk battery driver. BQ24196 driver added but not tested. Other feature are not tested. it might work, or not at all.
Happy hacking.
Uleak
unlock bootloader manually
removed duplicated content, plz refer to below link for unlock bootloader
https://forum.xda-developers.com/m3-note/how-to/m3note-unlock-bootloader-manually-apply-t3957419
technical detail of unlock logic is as below
sec_unlock.c
fastboot_get_unlock_perm {
...
index = partition_get_index(FRP_NAME);
...
size = partition_get_size(index);
unlock_allowed_flag_offset = size - sizeof(unsigned int);
...
}
ok, sizeof(unsigned int) is dword. the offset is (size-1 * dword). so set to 1 means unlock.