Related
I currently have the AT&T version of SGN2 which is t0lteatt. I really like Liquidsmooth, but there is only a t0lte version (T-Mobile). I can flash and it runs great. The problem I'm having is that my voice/data network keeps cutting out. I believe this is due to it being a t0lte version. Can someone explain the difference? Do I just need to flash over an AT&T radio? I don't believe this is so, because the rom wouldn't flash over the current AT&T radio I have. The APN settings I have are correct for AT&T by the way.
Thanks ahead for any help offered
voice and data doesn't cut out on other roms?
t0lteatt is our att note ii, t0lte is the international lte note ii and t0ltetmobile or w/e is the t-mobile version, ver little differences, the build.prop reflects proper phone and some other minor changes, that said all 3 dont include a modem so no you dont need one if you didnt change it to the wrong one.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Have you tried the UCAMC3 radio image ?
That radio may help...
Also check the dev section for the thread that offers the RIL files that have been pulled from the official UCAMC3 update.
Loading those libraries, to run along side the radio should give you the performance of the update build on the custom rom.
You "should " be okay loading RIL files into your rom, but please read the OP of those threads carefully.
And of course ...backup the current build if not done already.
I feel that RIL files are often overlooked or left incomplete, resulting in broken functionality on certain radio\rom combinations.
These critical files are normally included with radio images if packaged properly.
That being said, a re-flash of just the radio package should help as well.
But that question as to whether or not any given radio does contain the needed RIL's for the current network, should be forwarded to the respective dev or creators of the desired radio flash package.
Happy flashing ....g
I will try to answer this question as best I can. Up until about two months ago if you wanted to build a ROM from source for the GT-N7105, SGH-I317, or the SGH-T889 Galaxy Note 2 you had to use the t0lte folder as your device folder in your work tree. But Steve Klondik, A.K.A Cyanogen, made the partial device folders t0lteatt and t0ltetmo to start splitting the three devices apart. Now notice I said partial folders because even though these folders are for the SGH-I317 and SGH-T889 individually. They still use the t0lte folder to build as it has all the other folders in it that the device needs like overlays, configs, bluetooth, audio, device settings, and rootdir. this means that the compiler starts in the t0lteatt or the t0ltetmo depending on what device you are building for. But the full_t0lteatt.mk or full_t0ltetmo.mk directs it to go into the t0lte folder to use the t0lte.mk, or commonly called the device.mk file because neither the t0lteatt or the t0ltetmo folder has a device.mk file in them. Then only real difference in the folders is the name of the device in the files.
But this does not really address the difference between the t0lteatt and t0lte. The main difference is the t0lte is a build using only the t0lte device folder. This means that the build will probably not have the device model correct in the build-prop so it will not be the correct model number in Settings/About phone unless the build-prop is edited. The tolteatt is a build that used both the t0lteatt and t0lte device folders and should have the correct model number in the build-prop and Settings/About phone. But it is nothing wrong with building with just the t0lte folder as long as you do not mind editing the build-prop or that the build does not have the correct device model number. if you would like to look at all three folders below are links to all three on CyanogenMod github.
t0lte= https://github.com/CyanogenMod/android_device_samsung_t0lte
t0lteatt= https://github.com/CyanogenMod/android_device_samsung_t0lteatt
t0ltetmo= https://github.com/CyanogenMod/android_device_samsung_t0ltetmo?ref=commandbarr
Now to address you problem, if it is a t0lte build the it is more than likely a older build. Look in the the build.prop and see if you see this line. "ro.telephony.ril_class=SamsungQualcommUiccRIL" If you do you need to change it to " ro.telephony.ril_class=SamsungQualcommRIL". The ril file was changed on these devices in the t0lte.mk file about a month ago, below is a link to the commit showing the change. Maybe this will help you understand and help you fix yor issue.
Ril commit https://github.com/CyanogenMod/andr...mmit/f3459ea5651152c322334376f6c3c8b8b50375a3
Edit: I forgot that when Cyanogen made the t0lteatt and t0ltetmo folders he also added the smdk4412-qcom-common folder as a device dependency. But that is just for better GPS support so it further supports my point that it is no real big difference between t0lte and t0lteatt.
T-Macgnolia said:
I will try to answer this question as best I can. Up until about two months ago if you wanted to build a ROM from source for the GT-N7105, SGH-I317, or the SGH-T889 Galaxy Note 2 you had to use the t0lte folder as your device folder in your work tree. But Steve Klondik, A.K.A Cyanogen, made the partial device folders t0lteatt and t0ltetmo to start splitting the three devices apart. Now notice I said partial folders because even though these folders are for the SGH-I317 and SGH-T889 individually. They still use the t0lte folder to build as it has all the other folders in it that the device needs like overlays, configs, bluetooth, audio, device settings, and rootdir. this means that the compiler starts in the t0lteatt or the t0ltetmo depending on what device you are building for. But the full_t0lteatt.mk or full_t0ltetmo.mk directs it to go into the t0lte folder to use the t0lte.mk, or commonly called the device.mk file because neither the t0lteatt or the t0ltetmo folder has a device.mk file in them. Then only real difference in the folders is the name of the device in the files.
But this does not really address the difference between the t0lteatt and t0lte. The main difference is the t0lte is a build using only the t0lte device folder. This means that the build will probably not have the device model correct in the build-prop so it will not be the correct model number in Settings/About phone unless the build-prop is edited. The tolteatt is a build that used both the t0lteatt and t0lte device folders and should have the correct model number in the build-prop and Settings/About phone. But it is nothing wrong with building with just the t0lte folder as long as you do not mind editing the build-prop or that the build does not have the correct device model number. if you would like to look at all three folders below are links to all three on CyanogenMod github.
t0lte= https://github.com/CyanogenMod/android_device_samsung_t0lte
t0lteatt= https://github.com/CyanogenMod/android_device_samsung_t0lteatt
t0ltetmo= https://github.com/CyanogenMod/android_device_samsung_t0ltetmo?ref=commandbarr
Now to address you problem, if it is a t0lte build the it is more than likely a older build. Look in the the build.prop and see if you see this line. "ro.telephony.ril_class=SamsungQualcommUiccRIL" If you do you need to change it to " ro.telephony.ril_class=SamsungQualcommRIL". The ril file was changed on these devices in the t0lte.mk file about a month ago, below is a link to the commit showing the change. Maybe this will help you understand and help you fix yor issue.
Ril commit https://github.com/CyanogenMod/andr...mmit/f3459ea5651152c322334376f6c3c8b8b50375a3
Edit: I forgot that when Cyanogen made the t0lteatt and t0ltetmo folders he also added the smdk4412-qcom-common folder as a device dependency. But that is just for better GPS support so it further supports my point that it is no real big difference between t0lte and t0lteatt.
Click to expand...
Click to collapse
Awesome write up man!
ROOTBOXED!
Please read forum rules before posting
Questions and help issues go in Q&A and Help sections
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Thanks for the information in this thread. :good:
I have used both t0lte, t0ltetmo, and t0lteatt ROMs on my SGH-T889 (T-Mobile branded) device and they all work (voice, text, 3G, LTE) with the usual minor nuisances like device model being listed wrong in About Phone. I recently switched from T-Mobile to AT&T as my carrier, so I am wondering which ROM would be most appropriate for my device now? Any input or advice would be appreciated.
Hello All,
This may be in the wrong place so if it is, I am sorry, anyway to my question I'm trying to build CM for my S4 Mini LTE Serranoltexx everything was going fine until I got this message after running extract-files.sh
Code:
Extracting /system/lib/egl/libGLESv2S3D_adreno200.so ...
remote object '/system/lib/egl/libGLESv2S3D_adreno200.so' does not exist
Now after adding "libGLESv2S3D_adreno200.so" (if you search Google for it it's the top github link) I managed to get it to build the actual .zip and it does flash properly but it doesn't seem to have the correct graphics drivers (I thought this process wouldn't work and I was right), the guide on the how to build it doesn't help with this problem either so any help would be extremely appreciated
I've attached the logcat for reference (if it's needed) as a .docx file as the .txt file was 1.1mb and because I don't have a pro account on pastebin.
The problem with newer Android versions is that if often require new libraries which are not available in stock rom, so the extract method is actually not very useful unless we have a stock rom of the same version we are building for. To bypass this issue we use libraries from other phones that have the matching Android version. I suggest using the blobs that's on TheMuppets github, as those are up to date.
https://github.com/TheMuppets/proprietary_vendor_samsung
Hi everyone,
recently I have built and flashed on my sgh-t999 (galaxy S3 US tmobile version) CM11 Nightly. For my pro0ject however I need to modify two libraries of the Radio Interface Layer (RIL), libril.so and libreference-ril.so. I tried to modify the ones in the forlder /hardware/ril/ and build everything again with no results. Any change that I made to those files (such as ril.cpp in the folder libril) would not affect the functionality of the phone.
Finally yesterday I understood that when I build those libraries for the target cm-d2tmo-eng, those files that I have modified are not considered at all! When the libraries are built indeed, the system automatically takes the libril.so and libreference.so present in the vendor folder!
The problem is that those libraries in the vendor folder and already compiled and I cannot modify them. The question is:
Is there any way that I compile those libraries from the source code that I have modified?
Thanks,
brok85
Given that there is a unified D2LTE Build on CM, can you elaborate on what changes you wish to make to these libraries ?
To answer your question, You can do one of two things.
Grab the CM Source Code from the Device Tree of D2LTE. Make your relevant changes and check in the changes if they boot ok on your device. That way those changes will be included in future builds of CM and other Roms that use it.
If you do not wish to do so, then you will have to compile those libraries using C++ Compiler on a *NIX box and replace them in the Vendor folder.
Perseus71 said:
Given that there is a unified D2LTE Build on CM, can you elaborate on what changes you wish to make to these libraries ?
Click to expand...
Click to collapse
Well, as fisrt I just wanted to insert some log to be able to follow the code execution from the logcat or do something similar.
Perseus71 said:
To answer your question, You can do one of two things.
Grab the CM Source Code from the Device Tree of D2LTE. Make your relevant changes and check in the changes if they boot ok on your device. That way those changes will be included in future builds of CM and other Roms that use it.
Click to expand...
Click to collapse
Sorry but I am kind of new on this things. I have already downloaded the source code from the device tree and made my modifications in the files ril.cpp contained in [path-to-android-source]/hardware/ril/libril/ril.cpp. What I did was commenting the whole code within the function RIL_onUnsolicitedResponse() and listenCallback() such that in theory, the phone is not able to display incoming calls for example. However after flashing the re-built android I am still able to receve calls. How can I "check in the changes if they boot ok on my device"?
Perseus71 said:
If you do not wish to do so, then you will have to compile those libraries using C++ Compiler on a *NIX box and replace them in the Vendor folder.
Click to expand...
Click to collapse
I tried to remove the libril.so in the vendor folder and compile again using
# . build/envsetup.sh
# lunch (and select d2tmo)
# mmm [path-to-android-source]/hardware/ril/libril".
The problem is that when I indicate the target after lunch, the compiler looks for the vendor libraries and stop the build. What I am doing wrong?
Sounds like Compiler Dependacy path is set different from the code base. I will look further before commenting.
For when your changes are for the benefit of the community of users, you check in the changed code back to the Device Tree with detailed comments within the code and while checking in.
Perseus71 said:
Given that there is a unified D2LTE Build on CM, can you elaborate on what changes you wish to make to these libraries ?
To answer your question, You can do one of two things.
Grab the CM Source Code from the Device Tree of D2LTE. Make your relevant changes and check in the changes if they boot ok on your device. That way those changes will be included in future builds of CM and other Roms that use it.
If you do not wish to do so, then you will have to compile those libraries using C++ Compiler on a *NIX box and replace them in the Vendor folder.
Click to expand...
Click to collapse
Perseus71 said:
Sounds like Compiler Dependacy path is set different from the code base. I will look further before commenting.
For when your changes are for the benefit of the community of users, you check in the changed code back to the Device Tree with detailed comments within the code and while checking in.
Click to expand...
Click to collapse
Actually this is what I get after deleting
libril.so in vendor/samsung/d2tmo/proprietary/lib/
and after executing mmm /hardware/ril/libril :
No private recovery resources for TARGET_DEVICE d2tmo
make: *** No rule to make target `vendor/samsung/d2tmo/proprietary/lib/libril.so', needed by `/home/brok85/Documents/android/system/out/target/product/d2tmo/system/lib/libril.so'. Stop.
make: Leaving directory `/home/brok85/Documents/android/system'
If u want to build from source, delete the line that copies in vendor-blobs.mk
If u want to copy the blob instead of building it from source, keep the line
It'll be better if u provide us the device and vendor trees links
blackbeard said:
If u want to build from source, delete the line that copies in vendor-blobs.mk
If u want to copy the blob instead of building it from source, keep the line
It'll be better if u provide us the device and vendor trees links
Click to expand...
Click to collapse
I am not sure to understand what should I provide Sorry, as I said I'm kind of new here...
Also, I can not find vendor-blobs.mk...Where it should be?
brok85 said:
I am not sure to understand what should I provide Sorry, as I said I'm kind of new here...
Also, I can not find vendor-blobs.mk...Where it should be?
Click to expand...
Click to collapse
You said you built a cm11 for ur device. So for that you needed the device and the vendor trees. Give the link of those, if they are on the git
And vendor-blobs.mk would be present in the vendor folder under your device folder
blackbeard said:
You said you built a cm11 for ur device. So for that you needed the device and the vendor trees. Give the link of those, if they are on the git
Click to expand...
Click to collapse
Well I have followed the guide in the following page
http://wiki.cyanogenmod.org/w/Build_for_d2tmo
The link from where I have obtained the repository is
$ repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
and then
$ breakfast d2tmo
blackbeard said:
And vendor-blobs.mk would be present in the vendor folder under your device folder
Click to expand...
Click to collapse
Actually now I think I was able to compile the library following your instructions. Unfortunatly, when I have built and flashed everything in the galaxy S3, I was not able to use the network. Probably some compatibility issue?
When I compiled libril.so, I have obtained it from the folder /hardware/ril/libril which should contain google source code, maybe not compatibale with my device...is it right?
thanks a lot for the help guys
brok85 said:
Actually now I think I was able to compile the library following your instructions. Unfortunatly, when I have built and flashed everything in the galaxy S3, I was not able to use the network. Probably some compatibility issue?
When I compiled libril.so, I have obtained it from the folder /hardware/ril/libril which should contain google source code, maybe not compatibale with my device...is it right?
Click to expand...
Click to collapse
You know, silly question. But just so we can rule out. Did you at any point compiled the CM11 code as is and flashed to the phone ? How did Network behave ? Was everything ok ?
Galaxy S3 is a very open platform with standard hardware and chipsets. So the Default google code should work out of box with it. If you have network issues, then just for kicks you can flash a custom Kernel on top of your compiled CM 11. See how that goes.
Perseus71 said:
You know, silly question. But just so we can rule out. Did you at any point compiled the CM11 code as is and flashed to the phone ? How did Network behave ? Was everything ok ?
Click to expand...
Click to collapse
No silly question at all
I have compiled CM11 as it is and worked perfectly. I could use the network.
Perseus71 said:
Galaxy S3 is a very open platform with standard hardware and chipsets. So the Default google code should work out of box with it. If you have network issues, then just for kicks you can flash a custom Kernel on top of your compiled CM 11. See how that goes.
Click to expand...
Click to collapse
The procedure I have followed is the following one:
1) Delete the llibril.so and libreference-ril.so from the vendor library. These are the pre-compiled vendor libraries that I need to modify.
2) commented the lines from the vendor-blobs.mk that were including those two precompiled libraries.
3) go to android/system/ and run "mmm /hardware/ril/libril" and "mmm /hardware/ril/reference-ril" to obtain the modified libril.so and libreference-ril.so respectively.
4) copied the new libraries just obtained in the vendor folder where the pre-compiled libraries were
5) re-include the lines commented in point 2).
6) run brunch d2tmo
7) flash the .zip obtained
Any mistake?
Perseus71 said:
You know, silly question. But just so we can rule out. Did you at any point compiled the CM11 code as is and flashed to the phone ? How did Network behave ? Was everything ok ?
Click to expand...
Click to collapse
No silly question at all. Yes I have built everything out of the box and worked perfectly. I could use the network.
Perseus71 said:
Galaxy S3 is a very open platform with standard hardware and chipsets. So the Default google code should work out of box with it. If you have network issues, then just for kicks you can flash a custom Kernel on top of your compiled CM 11. See how that goes.
Click to expand...
Click to collapse
I followed the following procedure to include my modified libraries:
1) Eliminate precompiled vendor libraries: libril.so and libreference-ril.so from the vendor folder
2) comment lines in the vendor-blobs.mk that included those two precompiled libraries
3) from /android/system/ executed command "mmm /hardware/ril/librail" and "mmm /hardware/ril/reference-ril" to obtain the modified libril.so and libreference-ril.so
4) copied the new libraries in the vendor folder in the same places were the precompiled libraries were positioned
5) re-include the two lines that were commented in point 2)
6) build everything again with brunch d2tmo
7) flash the .zip obtained
Any mistake?
Unless I am having a brain fart that process seems about right. I wonder if your RIL changes are related to the network
What kind of issues do you see ?
Perseus71 said:
Unless I am having a brain fart that process seems about right. I wonder if your RIL changes are related to the network
What kind of issues do you see ?
Click to expand...
Click to collapse
It cannot even find the network operators. It says that it is impossible to connect and to try later...
mine is the Tmobile version of S3. May this influence?
That would depend on the changes you made. But otherwise not really. The underlying Device tree is unified for all US S3 devices.
I ported a ROM for my Tab S [SM-T800] but does not boot to system.
Boot animation comes and stucks at boot animation.
I used PACROM for SM-T800 as a base and Europhia OS for SM-T700.
Please help
Who knows? No good without logs, dmesg, last_kmsg, logcat
ashyx said:
Who knows? No good without logs, dmesg, last_kmsg, logcat
Click to expand...
Click to collapse
@TimurAlaskara_TR probably knows
Nandr0idC0nsumer said:
@TimurAlaskara_TR probably knows
Click to expand...
Click to collapse
What are you saying he's clairvoyant?
Logs are needed to have an idea of the issue. It's impossible to just guess, it could be any number of things
ashyx said:
What are you saying he's clairvoyant?
Logs are needed to have an idea of the issue. It's impossible to just guess, it could be any number of things
Click to expand...
Click to collapse
he just seems to have some magic that I don't
porting a Rom from a Tab s model to another is a pritty simple process
just Need to open boot.img with any boot Image unpacker and copy Zimage from stock to port, repack and done
also some changes in build.prop are recommended to make, it doesnt look cool if you have a t700 and System says t800
if you are porting a wifi Rom to a lte device you will need to use the boot.img of cm
also Need to change/add some libs in System/lib and 2 files in System/bin
System/Bin:
- Rild
- charon
System/Libs:
- Libc.so
- Libcec.so
- Libcharon.so
- Libcsc.so
- Libril.so
- Librilutils.so
- Libsecril.so
some of them may be irrelevant or only be in touchwiz roms, but this is the list a friend gave me some months ago
i think GPS related libs are missing there also :/
TimurAlaskara_TR said:
porting a Rom from a Tab s model to another is a pritty simple process
just Need to open boot.img with any boot Image unpacker and copy Zimage from stock to port, repack and done
also some changes in build.prop are recommended to make, it doesnt look cool if you have a t700 and System says t800
if you are porting a wifi Rom to a lte device you will need to use the boot.img of cm
also Need to change/add some libs in System/lib and 2 files in System/bin
System/Bin:
- Rild
- charon
System/Libs:
- Libc.so
- Libcec.so
- Libcharon.so
- Libcsc.so
- Libril.so
- Librilutils.so
- Libsecril.so
some of them may be irrelevant or only be in touchwiz roms, but this is the list a friend gave me some months ago
i think GPS related libs are missing there also :/
Click to expand...
Click to collapse
Oh really thanks Greetins from Turkey.
Sent from my Asus ZenFone 2 Laser (ZE550KL) using XDA Labs
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