Related
I am trying to build OMNI 4.4.4 for H60-L02. Right now I have managed to see the bootanimation of omni and then I have a bootloop. These are the logs for anyone who are willing to help
Logcat : http://pastebin.com/RT5x5EjJ
Dmesg : http://pastebin.com/PSzj9XJR
So, let's try to build roms for honor 6 !!! Any help is welcome ....
I don't have the skills but I'm willing to support the initiative as far as I can!
Sounds like the same issue i had, check google-cert folder that you have it and also build the files so that you edit default storage path. It was a few months ago i tried to build my own and i ended up with similair problem and it was related to missing cert and wrong storage path.
Im no expert, its just a hobby of mine so i might be wrong
Is Cyanogenmod avialable to Honor 6
Is Cm 11 available to Honor 6
Kanth's said:
Is Cm 11 available to Honor 6
Click to expand...
Click to collapse
No Cyanogenmod available yet, we all wait for.
HTC HD2 has CM12 already ^^
spanorg said:
I am trying to build OMNI 4.4.4 for H60-L02. Right now I have managed to see the bootanimation of omni and then I have a bootloop. These are the logs for anyone who are willing to help
Logcat : http://pastebin.com/RT5x5EjJ
Dmesg : http://pastebin.com/PSzj9XJR
So, let's try to build roms for honor 6 !!! Any help is welcome ....
Click to expand...
Click to collapse
@spanorg, what do you think of the information of codeworkx?
Daniel Hillenbrand a.k.a. codeworkx is a member of Team CM and TeamHacksung, is a legend
panamera2011 said:
@spanorg, what do you think of the information of codeworkx?
Click to expand...
Click to collapse
Go! go! go!
panamera2011 said:
@spanorg, what do you think of the information of codeworkx?
Daniel Hillenbrand a.k.a. codeworkx is a member of Team CM and TeamHacksung, is a legend
Click to expand...
Click to collapse
I have in my hands this info from the first hour I took the phone. I have built a whole device tree not only the partitions. Anyway, I appreciate any help. The big problem is that some sources of Huawei are not given. Especially for the kirin920 soc. That's why development is very difficult. Anyway, I am still trying for building... For any news, I will immediately tell you.
spanorg said:
I have in my hands this info from the first hour I took the phone. I have built a whole device tree not only the partitions. Anyway, I appreciate any help. The big problem is that some sources of Huawei are not given. Especially for the kirin920 soc. That's why development is very difficult. Anyway, I am still trying for building... For any news, I will immediately tell you.
Click to expand...
Click to collapse
Ok, thanks for try to build a CM :good:
Let's hope so!
spanorg said:
I have in my hands this info from the first hour I took the phone. I have built a whole device tree not only the partitions. Anyway, I appreciate any help. The big problem is that some sources of Huawei are not given. Especially for the kirin920 soc. That's why development is very difficult. Anyway, I am still trying for building... For any news, I will immediately tell you.
Click to expand...
Click to collapse
I've no doubt about this. @spanorg please help codeworkx (this IP the thread: http://forum.xda-developers.com/showthread.php?p=58283578).
He's searching for a tester whit competences. I think your help could be more precious now, you are a recognized developer and you can do more than a tester. you can collaborate whit him, and finally became our leader.
(we can ask for donations or other, if possible, to support your works)
Thanks.
spanorg said:
I have in my hands this info from the first hour I took the phone. I have built a whole device tree not only the partitions. Anyway, I appreciate any help. The big problem is that some sources of Huawei are not given. Especially for the kirin920 soc. That's why development is very difficult. Anyway, I am still trying for building... For any news, I will immediately tell you.
Click to expand...
Click to collapse
What do you need?
Here's a kernel for inline building:
https://github.com/codeworkx/android_kernel_huawei_h60
In original sources, have at look at drivers/vendor/hisi.
There are some "acore" folders with android userspace stuff. Doesn't belong there, but it's there.
I've seen some kirin stuff for bionic.
For everything else you have to use their libraries and make them working with aosp.
I assume this requires a ****load of bad hacks.
codeworkx said:
What do you need?
Here's a kernel for inline building:
https://github.com/codeworkx/android_kernel_huawei_h60
In original sources, have at look at drivers/vendor/hisi.
There are some "acore" folders with android userspace stuff. Doesn't belong there, but it's there.
I've seen some kirin stuff for bionic.
For everything else you have to use their libraries and make them working with aosp.
I assume this requires a ****load of bad hacks.
Click to expand...
Click to collapse
Hi codeworkx, I tried to compile cyanogenmod11 with your reposity, but I haven't not file local_manifests.xml .. you can send me right local_manifests.xml ?
Steve Giordano said:
Hi codeworkx, I tried to compile cyanogenmod11 with your reposity, but I haven't not file local_manifests.xml .. you can send me right local_manifests.xml ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/honor-6/orig-development/cyanogenmod-dev-thread-t3008138
please don't build if you don't know what you're doing.
This will not boot into android and requires a ton of work.
codeworkx said:
What do you need?
Here's a kernel for inline building:
https://github.com/codeworkx/android_kernel_huawei_h60
In original sources, have at look at drivers/vendor/hisi.
There are some "acore" folders with android userspace stuff. Doesn't belong there, but it's there.
I've seen some kirin stuff for bionic.
For everything else you have to use their libraries and make them working with aosp.
I assume this requires a ****load of bad hacks.
Click to expand...
Click to collapse
Do you have a link for the kirin stuff for bionic?
spanorg said:
Do you have a link for the kirin stuff for bionic?
Click to expand...
Click to collapse
sorry, my fault.
just stuff for the bootloader.
vendor/hisi/modem/drv/acore/bootable/bootloader/legacy/arch_balongv7r2
Is this project still active? Just curious.
This is a test build I take no responsibility for what this may or may not do to your device.
Click to expand...
Click to collapse
NEED TESTERS
currently i don't have the device to test i will be getting my device in the next week .
Click to expand...
Click to collapse
1. Install CWM Recovery
2. Do Full Wipe If coming from another ROM
3. Flash ROM
4. Flash Google Apps (my recommendation is to install minipal gapps due to /system partition size limits)
5. Reboot
Click to expand...
Click to collapse
]Not Booting
Click to expand...
Click to collapse
Code:
[B]Source[/B]
Here are the device tree :
Device Tree (from cm13 Nexus 9) : https://github.com/vickdu31/android_device_xiaomi_mocha
Kernel Tree (from Xiaomi KK) : https://github.com/vickdu31/android_kernel_xiaomi_mocha
Vendor Tree (old Xiaomi KK) : https://github.com/vickdu31/android_vendor_xiaomi_mocha
Thank you
@faust93 for cwm
XDA:DevDB Information
CM-13, ROM for the Xiaomi Mi Pad
Contributors
Rohit99, tank0412, vickdu31
ROM OS Version: 6.0.x Marshmallow
Based On: CyanogenMod
Version Information
Status: Testing
Created 2016-12-10
Last Updated 2016-12-13
Reserved
Edit 1:initial build didn't boot for me, no adb can't get log
Ok im gonna try it.
If you want, i can leave logcat for you
OoSTARTERoO said:
Ok im gonna try it.
If you want, i can leave logcat for you
Click to expand...
Click to collapse
Can get logcat? Try please.
Ofc, it doesn't boot. And don't create threads without testing.
Sudeep Duhoon said:
Can get logcat? Try please.
Click to expand...
Click to collapse
unfortunately....I couldn't get logcat too...
Sudeep Duhoon said:
Can get logcat? Try please.
Click to expand...
Click to collapse
we can't get logcat. It doesn't boot, i mean there are problems with kernel or init scripts or both. Kernel needs patches.
Nihhaar said:
Ofc, it doesn't boot.
Click to expand...
Click to collapse
As I thought
Prebuilt kernel from cm11
Sudeep Duhoon said:
As I thought
Click to expand...
Click to collapse
hey can i use prebuilt kernel from cm11 source @Nihhaar
Rohit99 said:
hey can i use prebuilt kernel from cm11 source @Nihhaar
Click to expand...
Click to collapse
Always try to build kernel with source. I think you can't, but you can try.
Please edit the link in OP, its me who miswrote it... : /android_device_xioami_mocha --> /android_device_xiaomi_mocha
You need to fix up SELinux and the init scripts. Taking a shield tablet device tree, renaming things to mocha and changing the fstab isn't enough. As far as I can tell the shieldtablet device tree also has dependency on a shield common tree. There's also no value in creating a new thread each time you push new commits
Our kernel from Xiaomi is also pretty useless without commit history. The device tree is also from shield tablet, not Nexus 9.
We also have a tree for building TWRP with OmniROM that you can compile TWRP 3.0.2.0 with.
What kernel repo is upstream one for tegra android? Like CAF for quallcom.
I've tried to merge xiaomi changes on l4t kernel https://github.com/HighwayStar/android_kernel_xiaomi_mocha
Merged dts files and arch/boot/march-tegra with some required drivers, but still cant boot it. Found somewhere here that l4t kernels is not for android, but for GNU/Linux, but what kernel is for android?
Cyanogenmod's shield kernel?
highwaystar_ru said:
What kernel repo is upstream one for tegra android? Like CAF for quallcom.
I've tried to merge xiaomi changes on l4t kernel https://github.com/HighwayStar/android_kernel_xiaomi_mocha
Merged dts files and arch/boot/march-tegra with some required drivers, but still cant boot it. Found somewhere here that l4t kernels is not for android, but for GNU/Linux, but what kernel is for android?
Cyanogenmod's shield kernel?
Click to expand...
Click to collapse
git://nv-tegra.nvidia.com/linux-3.10.git
I used rel-tn8-l-r7-shieldtablet8 to make a start on doing this. You could also use android_kernel_shield from CyanogenMod repo as it comes from the same place. But it will have a lot of extra commits for things not useful for mocha.
Here's what I have so far:
https://github.com/harrynowl/nvidia_tegra-3.10
Harrynowl said:
git://nv-tegra.nvidia.com/linux-3.10.git
I used rel-tn8-l-r7-shieldtablet8 to make a start on doing this. You could also use android_kernel_shield from CyanogenMod repo as it comes from the same place. But it will have a lot of extra commits for things not useful for mocha.
Here's what I have so far:
https://github.com/harrynowl/nvidia_tegra-3.10
Click to expand...
Click to collapse
Oh, intresting, cloned same url, but started other branch l4t/l4t-r21.5.
What status of your tree? Cant boot? We need minimal bootable kernel to be able to get dmesg and make further progress.
highwaystar_ru said:
Oh, intresting, cloned same url, but started other branch l4t/l4t-r21.5.
What status of your tree? Cant boot? We need minimal bootable kernel to be able to get dmesg and make further progress.
Click to expand...
Click to collapse
Untested, been doing device bring up. That kernel won't work yet anyway it's missing atmel, synaptic and battery firmware. (Plus the code that goes with it)
Some devs have one that gets to recovery but only 1 CPU core can come online and the CPU gets a bit hot. Unfortunately their commit history is hard to follow so I've not had a proper look at it yet
My my...it's been a while since I've seen a cringe-worthy dev thread on XDA. So OP just used the device tree from Nexus 9 (a 64-bit device with a different processor and nothing in common with the Mi Pad other than the fact that they use Nvidia SoCs and are both tablets), unmodified KITKAT kernel sources from Xiaomi (which takes work to make it boot, even on KK) and KITKAT userspace blobs to compile the ROM, and for some reason decided to share it without testing. The 10-post rule is meant to keep such people out of the development sub-forums, but obviously that's not working.
I do not understand why the moderators are allowing this thread to remain open. It's just a thread by a wannabe dev offering a non-bootable ROM that has the potential to brick the devices of many newbies who may decide to try this.
This thread is even more useless than the other "DEVS-ONLY" thread someone else made. Honestly, the entire Mi Pad forum is filled with people who either expect Android 7.1.1 to magically appear on their tabs just because Xiaomi released outdated kernel sources or just wanna create threads like this for the "thanks or whatever". The never ask for ETA rule seems to just float over their heads.
Now to some useful information. I believe, even if we patch the kernel enough for it to theoretically boot cm13, it probably won't, considering the outdated userspace blobs for the Mi Pad. Unless someone has the knowledge to take their tab apart and figure out how to get UART data, it will be virtually impossible for the mi pad kernel to boot any new version of Android. I heard another interesting approach taken by some russian devs at the Xiaomi forums. They've managed to port the kernel from the Nvidia shield (and apparently it's booting). Now this would mean we can use the userspace blobs from the Shield to at least get the ROM booting (most peripherals won't work, but that's step 2). I do not know whether they use GitHub or if they've even open-sourced their work, but now we know that it's possible, so that could be a possible method of approach.
EDIT: LOL. I just read the OP again. The "dev" expects donations to help him work harder. This from a person who posted his way into somehow compiling his first Android build without even having the damn device.
drakonizer said:
My my...it's been a while since I've seen a cringe-worthy dev thread on XDA. So OP just used the device tree from Nexus 9 (a 64-bit device with a different processor and nothing in common with the Mi Pad other than the fact that they use Nvidia SoCs and are both tablets), unmodified KITKAT kernel sources from Xiaomi (which takes work to make it boot, even on KK) and KITKAT userspace blobs to compile the ROM, and for some reason decided to share it without testing. The 10-post rule is meant to keep such people out of the development sub-forums, but obviously that's not working.
I do not understand why the moderators are allowing this thread to remain open. It's just a thread by a wannabe dev offering a non-bootable ROM that has the potential to brick the devices of many newbies who may decide to try this.
This thread is even more useless than the other "DEVS-ONLY" thread someone else made. Honestly, the entire Mi Pad forum is filled with people who either expect Android 7.1.1 to magically appear on their tabs just because Xiaomi released outdated kernel sources or just wanna create threads like this for the "thanks or whatever". The never ask for ETA rule seems to just float over their heads.
Now to some useful information. I believe, even if we patch the kernel enough for it to theoretically boot cm13, it probably won't, considering the outdated userspace blobs for the Mi Pad. Unless someone has the knowledge to take their tab apart and figure out how to get UART data, it will be virtually impossible for the mi pad kernel to boot any new version of Android. I heard another interesting approach taken by some russian devs at the Xiaomi forums. They've managed to port the kernel from the Nvidia shield (and apparently it's booting). Now this would mean we can use the userspace blobs from the Shield to at least get the ROM booting (most peripherals won't work, but that's step 2). I do not know whether they use GitHub or if they've even open-sourced their work, but now we know that it's possible, so that could be a possible method of approach.
EDIT: LOL. I just read the OP again. The "dev" expects donations to help him work harder. This from a person who posted his way into somehow compiling his first Android build without even having the damn device.
Click to expand...
Click to collapse
I agree, this device has no development threads. Only 2 give me thanks and here's my donation link threads.
They have indeed used GitHub, but I don't believe they want to share the repo just yet so I won't post it publicly. It has many problems to sort and also sadly, they didn't keep the commit history from Nvidia as it was initialised via zip DL. It does boot to recovery though.
Harrynowl said:
I agree, this device has no development threads. Only 2 give me thanks and here's my donation link threads.
They have indeed used GitHub, but I don't believe they want to share the repo just yet so I won't post it publicly. It has many problems to sort and also sadly, they didn't keep the commit history from Nvidia as it was initialised via zip DL. It does boot to recovery though.
Click to expand...
Click to collapse
Oh! I didn't realize we were talking about the same person/team. I'd love to start developing for this device. In fact, I'm working on KEXEC-hardboot and Multirom right now, but I'd like to follow what you guys are doing and contribute as much as I can. Is there an IRC channel/IM app you guys use for communication? If so, I'd appreciate it if you could PM the info.
Heya, I just got my hands on a J200H, and I get to keep it for a while.
As I was using it, I thought if there is any lineageos for it, and there is not.
Now it would be great if you guys point me where I can find Device tree, Kernel source, Vendor blobs for this device, so that I could start working on this device and add the repo to official lineageos server for build ( provided all things goes smoothly nearly one month is enough )
Also I saw some varients of this device, it would be great if you could add device models (the codes- like J200H) and their source codes too, I could try merging them into a universal source code and patch as universal makes less problem.
Thanks In advance! And any update will be posted here.
I doubt if the things mentioned are available.
But if the are really willing to do this than this can be useful .
Have a look a this
https://web.archive.org/web/20161224192644/https://wiki.cyanogenmod.org/w/Doc:_porting_intro
and this
https://forum.xda-developers.com/an...ow-to-create-device-tree-android-rom-t3498355
ad. said:
I doubt if the things mentioned are available.
But if the are really willing to do this than this can be useful .
Have a look a this
https://web.archive.org/web/20161224192644/https://wiki.cyanogenmod.org/w/Doc:_porting_intro
and this
https://forum.xda-developers.com/an...ow-to-create-device-tree-android-rom-t3498355
Click to expand...
Click to collapse
got em on samsungs website, but holy ****e their bandwidth....they are killing me.....
Just look at these download speed.... god no...
https://ibb.co/gnDQLQ
uts58 said:
got em on samsungs website
Click to expand...
Click to collapse
I don't know but I guess they are just kernel source .
Once downloaded you can know what is that actually.
@uts58 Are you still working on it????
Hi! Because of lack of time I was unable to continue my development of LineageOS/Android Wear 2.0 for Moto 360. I created this thread to find someone who can help fix SGX drivers (probably lack of some code in Android 8.0(, because Android does not start because of them. I'm publishing all repos and sources I've already created.
Firstly we need to focus on booting LineageOS, because It is the easiest way to boot Android 7 on Moto 360. Google didn't publish sources for Android Wear 2.0, so we will need to port it using image from other watch and our Android 7.1 drivers.
https://github.com/artas182x/android_device_motorola_minnow (branch cm-14.1)
https://github.com/artas182x/kernel-omap/tree/android-7.1-wear (branch android-7.1-wear)
https://github.com/artas182x/vendor_motorola_minnow (branch master)
Logcat with SGX error: https://pastebin.com/WKDhjEzX
If you have a problem with SGX Driver you can take inspire from this project: Unlegacy-Android. They took an Omap4 Device (Samsung Galaxy Nexus) and try to import all the necessary source from omapzoom repository to build a fully functional android 7.1.
retsef said:
If you have a problem with SGX Driver you can take inspire from this project: Unlegacy-Android. They took an Omap4 Device (Samsung Galaxy Nexus) and try to import all the necessary source from omapzoom repository to build a fully functional android 7.1.
Click to expand...
Click to collapse
Moto 360 user newer SGX driver and newer kernel than Galaxy Nexus.
Wysłane z iPhone za pomocą Tapatalk
I Hope this project Will continue, because i want wear 2.0 in my moto 360!!
I am very helpful with troubleshooting builds that boot.
I've worked on GS6 for sprint.
I've done a TON of testing for moto e 2015.
I currently have GS7 and moto 360 1st gen.
Please let me know how I can help get lineage/wear 2.0 going.
I will help as much as I can and willing to donate monetarily.
Good to see people working on this. Just got my moto 360 and was bummed to see the lack of development for it.
Let's make this happen! Going to Google your issue and see of it has dropped up before.
Thanks for all the time you've spent already dev!
I also just made my interface cable. Not tested yet. Will tonight.
I also sent a pm to a Dev who has ported wear 2.0 to the LG g watch. Hopefully I hear back and he can help us out!
Edit:
I got a response from another Dev. He had ported AW 2.0 for the LG G Watch.
Mentioned it might be easier to use another os and swap out libs and other files. I will copy text and post his full reply next.
His response:
"Unfortunately, I have no experience of working with OMAP devices.
Anyway, why are you building lineage? I think, using system image of another device as a base and patching it with device-specific configs and libs would be easier"
Thoughts on this @artas182x ?
crazynapkinman said:
His response:
"Unfortunately, I have no experience of working with OMAP devices.
Anyway, why are you building lineage? I think, using system image of another device as a base and patching it with device-specific configs and libs would be easier"
Thoughts on this @artas182x ?
Click to expand...
Click to collapse
Hmm Moto 360 is only one smartwatch based on OMAP3. What's more it's has newer kernel and SGX drivers than Galaxy Nexus and other OMAP Android devices. I don't know how to fix SGX problem. Probably it's the last problem we need to solve. Everything else should work.
Unfortunately, we don't have open-source SGX drivers for Moto 360. There are some on the internet but in earlier version than we need. So we need to find how to run prebuilt drivers.
All my sources are on my GitHub, you should be able to build Lineage OS from that files.
What do you mean by "prebuilt drivers"? The drivers already on device?
And we would need to make everything work with those existing drivers rather than getting new drivers that work with everything else?
@artas182x could you point me in the direction for the sgx drivers online? Are they Intel drivers? Or....?
Sorry for all questions. Trying to research and see what I can do or find someone to help us.
I did just find this one:
https://github.com/nemomobile/ti-omap3-sgx
What about this one?
https://01.org/intel-softwareguard-extensions/downloads/intel-sgx-linux-2.0-release
Hey to both of you. I have had a moto 360 for a while and am more than willing to help. Do we wanna maybe setup a telegram chat or something similar. For easy communication.
dylanneve1 said:
Hey to both of you. I have had a moto 360 for a while and am more than willing to help. Do we wanna maybe setup a telegram chat or something similar. For easy communication.
Click to expand...
Click to collapse
Sure. I have never used it. But ok
Im rly glade to see that some ppl are trying to bring Wear 2.0 on the Moto 360 Gen1, i would like to help but i can´t program ^^
So i just can say thanks
Great to see some news
I am willing to help if you need any testers etc.
Keep it up guyz!
Spoke with Motorola today.
I took a picture of the convo. No luck...
Does anybody know if there is some android based device compatible with our hardware? If it's popular in community we could help devs with development and maybe be able to get working driver...
Deleted
Here's the wiki.
I have a nook color! But is that too old?
What about droid?
https://t.me/joinchat/FPu8TkfPJE8URYWg9x7HxA
Here's a group link
crazynapkinman said:
Here's the wiki.
I have a nook color! But is that too old?
What about droid?
Click to expand...
Click to collapse
Seems like Moto Droid 4 has OMAP as well and working 7.1. But idk if that OMAP is compatible.
https://forum.xda-developers.com/droid-4/development/rom-cm14-1-nougat-t3499338
viktorkovarik said:
Seems like Moto Droid 4 has OMAP as well and working 7.1. But idk if that OMAP is compatible.
https://forum.xda-developers.com/droid-4/development/rom-cm14-1-nougat-t3499338
Click to expand...
Click to collapse
It's omap4 not sure
Hi,
I am trying to port LineageOS to an unsupported device, an IBall Slide Cuddle A4.
Here's the guide I'm following : https://fat-tire.github.io/porting-intro.html
This is the part where I need help:
"Add the blobs to the vendor/ directory
Once you have a working recovery, it's now time to get CyanogenMod building and working.
The first thing to do is to get all the proprietary, binary blobs into the vendor/ folder, along with a .mk file that will include them in the final build.
This requires three steps:
Create extract-files.sh and setup-makefiles.sh scripts to pull those blob files from the device using adb and put them in the right /vendor/ directory. There are plenty of examples available for other devices.
Create an .mk Makefile to copy those files to the $OUT folder during the build process and put them in the right place. Again, use other devices as a guide for what this Makefile should look like. An example filename might be BoardConfigVendor.mk
Make sure that the Makefile you just created is included from your main BoardConfig.mk via a command such as -include vendor/[vendor]/[codename]/BoardConfigVendor.mk. Again, existing devices can illustrate how this is done.
Now revise the device/ directory
Since you have a working recovery, go back and start modifying the files in the device/ folder. As always, use other similar devices as a reference.
You now have a easy means to do backups and test your builds. So start tweaking the device folder itself, and see if you get it to boot... Once you do, from there its a matter of building and supporting the various parts and peripherals, one-by-one. "
Click to expand...
Click to collapse
Q #1: Where all should I look on my device for the proprietary blobs, and what do they look like? Can I manually extract them out of my existing ROM and paste them into the proper folder of the new one?
Q #2: What do I modify in the device/ folder?
Q #3: What does it mean to "build and support the various parts and peripherals" Does this mean to add the necessary drivers? If so, can I get these drivers from the stock ROM?
The reason I have to ask this here is because my device has NO similar LineageOS-supported devices with the same chipset for me to refer to. My tablet has a MediaTek MT8392 chipset, and I couldn't find any supported devices with an MT8392 (or an MT6592, which is very similar). Also, there is NO code available from the manufacturer, at all. The only resource I have is a stock ROM.
Are there any other ways in which a device can be similar enough for me to use as reference?
It would be really nice if someone could provide links to articles explaining the above 3 things, or if someone has already gone through this process, share their experience.
Also, will my kernel (v3.4.67) be compatible with the latest LineageOS 16 / Android 9 or will I have to build an earlier version?
I am very new to Android development, but that doesn't mean that I can't learn!
That's a hard task for getting started. A mtk device with no twrp available. I recommend to start with low hanging fruits. Like buying an old phone with dropped lineageOS support and building an updated version.
I understand that it is quite difficult. So instead of doing a full port myself, I am now trying the method of taking an image made for a similar MTK device and transferring the device-specific files from my stock ROM, as shown in the following guide:
https://www.techubng.com/2017/09/how-to-port-lineage-os-14-nougat-rom-on-mtk.html
It says:
"From System/lib/hw: Delete all mt6572.so blobs and replace with these blobs: DOWNLOAD BLOBS
Now copy these files from stock to port:
System/lib/hwcomposer.mt65xx.so
System/lib/gralloc
System/lib/lib.audio.primary.so
Systemlib/lib.mali.soS
System/Etc
System/lib/libcameracustom.so
System/etc/firmware
System/lib/libfeatureio.so
boot/kernel
boot/unventd.rc (only if you are getting stuck at logo)
boot/Replace only camera lines under #Camera from stock boot.img init.rc to init.mt6572.rclib/libcamdrv.solib/libcamalgo.so"
But my stock ROM does not have any of the files he listed uner /system/lib! Can I ignore these files, or is there some other place where these files could be? (I checked /vendor)
Also, what about all the other files in /system/lib? Which ones are device-specific and does anything else need to be copied into the new ROM?
As for the TWRP, I have found tools like Easy Magic TWRP Installer ( https://forum.hovatek.com/thread-5162.html ) which will automatically do the porting given the boot.img and recovery.img from the stock ROM. Are these safe to use, as long as I provide the right info to the tool?
I want to use LineageOS on this tablet because the stock OS has some annoying bugs and is quite old (Android 4.4.2) considering how recent the tablet is and how much capability the tablet's hardware has. The manufacturer (IBall) has provided no updates at all.
Lineage OS on Samsung Galaxy J3 Achieve (SM-J337P)
Can I pay a developer to make a working ROM to put Lineage OS on the Samsung Galaxy J3 Achieve (SM-J337P) ?
If so, how do I find a developer who can do it?
hey, i have a sm-t280 that have a similar supported device. how i port to it?
i have a sm-t280 that i wan't to update the android. the only exit i found it's build linegeos or aosp for it, can anyone help me?
here is the source tree:
vendor tree: huttps://github.com/gtexswifi/android_vendor_samsung_gtexswifi
-----
device tree: huttps://github.com/gtexswifi/android_device_samsung_gtexswifi
-----
kernel tree: huttps://github.com/pfent/sm-t280-kernel
[i writed huttps because i don't have posted 10 posts already]
Porting similar device mt6750t
vinaypundith said:
I understand that it is quite difficult. So instead of doing a full port myself, I am now trying the method of taking an image made for a similar MTK device and transferring the device-specific files from my stock ROM, as shown in the following guide:
https://www.techubng.com/2017/09/how-to-port-lineage-os-14-nougat-rom-on-mtk.html
It says:
"From System/lib/hw: Delete all mt6572.so blobs and replace with these blobs: DOWNLOAD BLOBS
Now copy these files from stock to port:
System/lib/hwcomposer.mt65xx.so
System/lib/gralloc
System/lib/lib.audio.primary.so
Systemlib/lib.mali.soS
System/Etc
System/lib/libcameracustom.so
System/etc/firmware
System/lib/libfeatureio.so
boot/kernel
boot/unventd.rc (only if you are getting stuck at logo)
boot/Replace only camera lines under #Camera from stock boot.img init.rc to init.mt6572.rclib/libcamdrv.solib/libcamalgo.so"
But my stock ROM does not have any of the files he listed uner /system/lib! Can I ignore these files, or is there some other place where these files could be? (I checked /vendor)
Also, what about all the other files in /system/lib? Which ones are device-specific and does anything else need to be copied into the new ROM?
As for the TWRP, I have found tools like Easy Magic TWRP Installer ( https://forum.hovatek.com/thread-5162.html ) which will automatically do the porting given the boot.img and recovery.img from the stock ROM. Are these safe to use, as long as I provide the right info to the tool?
I want to use LineageOS on this tablet because the stock OS has some annoying bugs and is quite old (Android 4.4.2) considering how recent the tablet is and how much capability the tablet's hardware has. The manufacturer (IBall) has provided no updates at all.
Click to expand...
Click to collapse
I saw Lineage OS 16 for HomTom S99….
I have HomTom HT70 with same Chipset of HomTom S99 MT6750T….
Im trying to read and follow carefully your guide but still i have bootloop..
Is it Possible to Port it to Homtom HT70 so we can have Android 9 too??
https://forum.xda-developers.com/ge...tom-ht70-6-0-hd-189-mt6750t-4gb-64gb-t3803052
hey, I have a samsung j7 j700t (t-mobile), and if it has a similar version that is the j700f / h / m, but I have tried it and it does not work for me. What do I have to do to make it work for me? Help me please!!!
AlexRsl1999 said:
hey, I have a samsung j7 j700t (t-mobile), and if it has a similar version that is the j700f / h / m, but I have tried it and it does not work for me. What do I have to do to make it work for me? Help me please!!!
Click to expand...
Click to collapse
Different processsor. J700t is Qualcomm. J700f is exynos
kurtn said:
Different processsor. J700t is Qualcomm. J700f is exynos
Click to expand...
Click to collapse
But my processor is Exynos 7580 to 1.5GHz
AlexRsl1999 said:
But my processor is Exynos 7580 to 1.5GHz
Click to expand...
Click to collapse
If you haven't already, I'd recommend checking in Geekbench as there's a lot of conflicting information on the web. Usually, Samsung only puts the Exynos chip in GSM only devices sold outside the US.
There is a custom rom for a variant of my device (Huawei g760) please how can i make it work on my device (Huawei g7-UL20) they both have the same specs and processor everything is the same
YomaAroriode said:
There is a custom rom for a variant of my device (Huawei g760) please how can i make it work on my device (Huawei g7-UL20) they both have the same specs and processor everything is the same
Click to expand...
Click to collapse
Have you unlocked the bootloader, before huawei stopped allowing it?
kurtn said:
Have you unlocked the bootloader, before huawei stopped allowing it?
Click to expand...
Click to collapse
Yes my bootloader is unlocked
kurtn said:
Have you unlocked the bootloader, befes ore huawei stopped allowing it?
Click to expand...
Click to collapse
Yes my bootloader is unlocked
I followed this guide: https://forum.xda-developers.com/t/guide-porting-twrp-without-source.3843473/
And ported the twrp recovery made for huawei g760 to my g7-UL20
Now how do i modify the custom rom for it to work on my device. Please i need your help!!
kurtn said:
That's a hard task for getting started. A mtk device with no twrp available. I recommend to start with low hanging fruits. Like buying an old phone with dropped lineageOS support and building an updated version.
Click to expand...
Click to collapse
Hi there, I just noticed this reply you had made and I have a question about a device that may have had Lineage support.
What I would like to do, once I have my new phone that is, is to take my current phone Motorola Edge+ (2020) and turn it into a small Lineage tablet.
However, there is one slight problem with this, and that is rhat there is currently no Lineage support for this device, but there is support for it's younger brother the Motorola Edge (2020).
Now I do know that porting is possible between devices, but I've seen a lot of guides says they should have the certain similarities such as processor and such.
However the CPU, GPU and Chipset are slightly different (Same brands though), will this pose a problem in porting?
I of course do realize that I will of course need the proprietary blobs from Motorola for this device and I believe I have found them.
Finally, I am curious if you know of any up to date guides on porting? I will of course continue researching myself, however I thought I would make an enquiry anyway.
Any help you may be able to provide would be greatly appreciated.
Bloodstalker
Bloodstalker82 said:
Hi there, I just noticed this reply you had made and I have a question about a device that may have had Lineage support.
What I would like to do, once I have my new phone that is, is to take my current phone Motorola Edge+ (2020) and turn it into a small Lineage tablet.
However, there is one slight problem with this, and that is rhat there is currently no Lineage support for this device, but there is support for it's younger brother the Motorola Edge (2020).
Now I do know that porting is possible between devices, but I've seen a lot of guides says they should have the certain similarities such as processor and such.
However the CPU, GPU and Chipset are slightly different (Same brands though), will this pose a problem in porting?
I of course do realize that I will of course need the proprietary blobs from Motorola for this device and I believe I have found them.
Finally, I am curious if you know of any up to date guides on porting? I will of course continue researching myself, however I thought I would make an enquiry anyway.
Any help you may be able to provide would be greatly appreciated.
Bloodstalker
Click to expand...
Click to collapse
Install a gsi
GSI Rom´s For Motorola Edge +?
Hi for everyone! I have been looking for custom rom for our Motorola Edge +. But I haven't found any yet. However there is the option of the GSI rom's, this smartphone has an A / B system partition. 64-bit ARM CPU architecture. (information...
forum.xda-developers.com
Thank you very much for your reply. I had seen that I could uae a GSI, however I had not realized it is actually possible with Lineage. I clearly misread the topic.
kurtn said:
That's a hard task for getting started. A mtk device with no twrp available. I recommend to start with low hanging fruits. Like buying an old phone with dropped lineageOS support and building an updated version.
Click to expand...
Click to collapse
yo i have a phone with an unofficial version of lineageos 15.1 (Lenovo K8 Note) how would i go about building that newer version