yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] blakegriplingph:
You're welcome, glad you had things sorted out on your end. I do have an init.environ.rc on my /out folder but I am not sure if it's right at all lol:

# set up the global environment
on init
export PATH /sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin
export ANDROID_BOOTLOGO 1
export ANDROID_ROOT /system
export ANDROID_ASSETS /system/app
export ANDROID_DATA /data
export ANDROID_STORAGE /storage
export ASEC_MOUNTPOINT /mnt/asec
export LOOP_MOUNTPOINT /mnt/obb
export BOOTCLASSPATH /system/framework/core-libart.jar:/system/framework/conscrypt.jar:/system/framework/okhttp.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/telephony-common.jar:/system/framework/voip-common.jar:/system/framework/ims-common.jar:/system/framework/mms-common.jar:/system/framework/android.policy.jar:/system/framework/apache-xml.jar
export SYSTEMSERVERCLASSPATH /system/framework/org.cyanogenmod.platform.jar:/system/framework/org.cyanogenmod.hardware.jar:/system/framework/services.jar:/system/framework/ethernet-service.jar:/system/framework/wifi-service.jar
export LD_PRELOAD libsigchain.so:libxlog.so

On the stock ramdisk it looks like this:

# set up the global environment
on init
export PATH /sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin
export LD_LIBRARY_PATH /vendor/lib:/system/lib
export ANDROID_BOOTLOGO 1
export ANDROID_ROOT /system
export ANDROID_ASSETS /system/app
export ANDROID_DATA /data
export ANDROID_STORAGE /storage
export ASEC_MOUNTPOINT /mnt/asec
export LOOP_MOUNTPOINT /mnt/obb
export BOOTCLASSPATH /system/framework/core.jar:/system/framework/conscrypt.jar:/system/framework/okhttp.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/framework2.jar:/system/framework/telephony-common.jar:/system/framework/voip-common.jar:/system/framework/mms-common.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar:/system/framework/webviewchromium.jar:/system/framework/mediatek-common.jar:/system/framework/mediatek-framework.jar:/system/framework/CustomProperties.jar:/system/framework/mediatek-telephony-common.jar:/system/framework/mediatek-tablet.jar

And by init.rc do you mean init.mt8127.rc? Could you tell me which parts are wrong please, as I've based this off [MENTION=8184192]Stricted[/MENTION]'s MT8127 repo. I doubt that the missing "LD_LIBRARY_PATH" is at fault too. Also, I am getting a missing "__umodsi3" symbol error prior to introducing a (rather pointless imo) shim just to sort of make hwcomposer happy, even though I still end up not getting the GUI to show up.

You mind if we continue on discussing this on the LeapFrog development thread though? I don't want to stray off your original topic here anyway.
[Miscellaneous Android Development] Matty1993:
Hey mate sorry for late replty been helping a friend out building a twrp for them,

Yeah ill go through your init now on your guthub and ill type out into a notepad++ what i can visually see is wrong with it and any other files also,

LD_LIBRARY_PATH i beleive wont break a system and shouldn't stoo GUI loading up, also with HW composer could you notjust disabling it to run native 2D graphics ?

Anyhow yeah ill jump on the leapfrog forum when i get some time :)
[Miscellaneous Android Development] Matty1993:
Hey mate,

Yeah im not to bad sorry for late reply ahh sweet that means i dont have to decompile my kernel now :D that may have been one of the libs id changed that time id gotten it working and didnt even know id changed it, how did you figure tthat one out, as usually for cam the mains are camalgo, camdrv, gralloc & featureio i couldnt wrap my head round why i couldnt get it working again lol

Yeah 720p i found was the best optimal setting as SS 480p seemed to be a bit grainy and 1080p isnt device supportive so is so slow i havent released an update to CRdroid so may end up getting it done in the next few weeks 5044T users will be happy :) great work on figuring it out
[Miscellaneous Android Development] blakegriplingph:
I am not sure, something's keeping the loading animations from showing up, maybe I might have missed a few more blobs or whatnot. I'll have to upload an unsigned dump of the Epic for you to peruse some time. You mind if we get you a donor Epic whilst I wait for mac2612 at /r/OpenLF to get his own Epic being he's had Linux development experience before.
[Miscellaneous Android Development] blakegriplingph:
Dependency viewer? Which one are you using if you don't mind telling?
[Miscellaneous Android Development] Matty1993:
Hey bud sorry for the very late reply i feel quite rude i somehow managed to unmark my own thread :eek: just scoured my mentions section looking for a comment on it lol,

Had troubles with pc also blowing just got it fixed today so looking forward to getting camera all working well with it managed to make some progress with my rom before it did though

Ive turned my build into a vendor image as im also trying to incorporate all the test tools from the stock rom aswell as the VOLTE modem thats been attached to custpack in stock,

Managed to get most test tools working well but something wrong with the modem not engaging properly it says YES OPTUS but has no signal or service and imei is also blank not invalid but blank & gone lol :eek: yet sim still registers optus so i think im gonne be doing some debugging on it to see whats going wrong ive got a feeling i may need to reverse engineer the modem libs hoepfully not other than that ive only got a small bug when it first boots up that states "a vendor image mismatch has been detected, typically this means your vendor image is out of date please ensure your vendor image matches NJH47F"

Got me stumped a bit on it as i cant spot anything obvi wrong but ill persevere as having it as a vendor build seems to use at least 60-100mb less ram, first boot is quicker & there is virtually no lag at all compared to a traditional build and i was able to add all the SLPencryption and Fpsv files and libs without getting a bootloop as im trying to get encryption to work with it, not sure if its working though as i didnt get a chance to test yet.

Ill keep you updated on progress anyhow as i go when i get round to it i gotta help blake first though as i promised him id help him get his CM 12.1 working when i got my computer working again as hes been dying to get it working on his leapfrog epic :)

Hows things on your end with your rom ? Did you manage to make any progress with getting IMS, VOLTE or VILTE anywhere near working im struggling to say the least with it lol
[Miscellaneous Android Development] bigrammy:
MTK source code

Hi [MENTION=9139800]Matty1993[/MENTION]

Not sure if this will help but I have found the FULL Mediatek source code for the MT6737x.

The Android 8.1 sources can be found HERE along with some other useful things like the Android SDK source (This is the full 6.0 source code). :good:

I have downloaded the 8.1 source and it seems to be complete. :D

There are also full build instructions although you will need to create your own "Build Project" from what I understand or maybe you can just cherry pick what you need. :fingers-crossed:

Below are the officially maintained repository's on github.

OrangePi 4G-IOT

OrangePi 4G-IOT build on MTK6737 Soc, the officially maintained repository as follows:

kernel:

https://github.com/orangepi-xunlong/OrangePi4G-iot_kernel.git

u-boot:

https://github.com/orangepi-xunlong/OrangePi4G-iot_bootloader.git

build scripts

https://github.com/orangepi-xunlong/OrangePi4G-iot_scripts.git

external binary file

https://github.com/orangepi-xunlong/OrangePi4G-iot_external.git

toolchain

https://github.com/orangepi-xunlong/OrangePi4G-iot_toolchain.git

:fingers-crossed:
[Miscellaneous Android Development] Matty1993:
Havent worked on the build in a while been in hosptial with pneumonia horrible just horrible wouldnt wish it upon anyone, before hand though yeah vendor build was going great so much more can be added and works where it dosent in /system, such as the slp encryption and cloud test suites etc would all give me bootloop when added to /bin /etc and /lib so what i did is made the system think its got an emulated /vendor partiton instead of me going to all the trouble to create a logical /vendor partitiion by editing a few things in the boot.img .rc files and slinking it in the cpiolist so that the dir is set in the rootfs with 0644 permission but still using 0755 permissions in /system/vendor ;) took me a while to figure it out but even makes system boot and run faster and smoother dont know how thats possible though as it even uses 100mb less ram deffo works as /vendor but as the message i stated in the earlier post just wont go TF away no matter what i do lol,

Still fixing front camera trying to compile my own camera lib for the front but havent gotten round to it yet
[Miscellaneous Android Development] Matty1993:
Big rammy my friend how have you been and thank you so much for linking me to some proper oreo source for these SoCs as i was trying to port lineage 15.0 32bit rom i found for Moto G4 MT6373M but just cant get it past the logo no natter what i do, being complete or near complete sources though i should be able to make something works :D cant thank you enough for the links again
[Miscellaneous Android Development] bigrammy:
Sorry to hear you have been seriously ill with pneumonia :eek:

I thought you had gone kind of quite on the forum, I do hope your all sorted now and feeling better. :fingers-crossed:

Yes the source is probably the best I have seen thus far and providing you have the necessary drivers and a little know how I am pretty sure you could bring up a new Project for your own device. :fingers-crossed:

Not sure about your booting issue as it could be just about anything but I am sure you will hunt down the problem. :fingers-crossed:
[Miscellaneous Android Development] Matty1993:
All good dude yeah lots of nasty stuff in my lungs i got the privledge to know what a tube being stuck down your throat to make you breathe felt like :mad: yeah ill be sure to check it out as ive looked at a few but none of them were by far near complete which is probs why i couldnt get oreo to boot,

optus have finally switched to Qualcomm's snapdragon so they can run 8.1.0 on there new updated Optus x spirit 2 so they even have abandoned mtk i on the other hand prefer the overjoyable mess that mediatek is haha :) yeah thats what i figured about the boot issue to could be an init.xx.rc or se_contexts or even the init possibily everything else is perfect in bootimg, either that or could be one of the binaries in /bin or .jars in /framework could even be in /lib ill just keep picking away while i go through the oreo source until some magic happens :laugh:
[Miscellaneous Android Development] bigrammy:
Yes most definitely not a good experience I am sure. :crying:

Hope you work out your booting issue :good:

I may need to pick your brains later on regarding the Lenovo TAB2 A10-70F/L I managed to get the KK 3.10.65 kernel source to build without any real errors but I think it maybe arm rather than arm64 IDK the old style MediaTek layout is very confusing and I am not sure how it all works eg which parts come from the actual kernel and what comes from the Mediatek project which config's it use or how to make config changes even etc etc. :eek:

I have had a lot on recently so not really had time to fully explore it Github lenovo_kernel_a10-70f

I can't seem find any good guides for working with this old style layout unless you know of any. :fingers-crossed:
[Miscellaneous Android Development] Matty1993:
Yeah was horrible, made some minor progress on the boot issue dosent switch straight off now is sitting on logo for about 30 seconds before it switches off so getting there bit by bit haha,

Never worked on a lenovo Tab 2 what MTK specs is it running ?

your correct to also about it being confusing the word id use is uniqe experience to say the least last time i worked on older style mtk sources however i did make some notes as i got stuck a fair amount of times aswell not knowing where to put things but it varies from source to source where things go and configs etc etc so i dont know if the layouts would be the same
[Miscellaneous Android Development] bigrammy:
The tablet is based on the mt6752/6732 chip set (Quad Core) although Lenovo's specs say HERE

WiFi: MediaTek® MT8165 64-bit 1.7 GHz Quad Core

4G LTE: MediaTek® MT8732 64-bit 1.7 GHz Quad Core

The kernel will boot on either device WiFi or 4G so clearly not much difference between them and seems to be more of a naming thing and possibly some minor tweaking.

The Lenovo K3 kernel source is called the aio (All in One) so I am thinking it may well build for this Tablet too as all the drivers seem to be present in that source. android_kernel_lenovo_aio_otfp I just need to workout the defconfig and what device specific parts I need from the tablets KK source code.

:fingers-crossed:
[Mogul, XV6800 General] SKullman:
Ok oddest thing. I was on the road driving up an Interstate on a 4 hour trip that should have evdo coverage all the way up, about 1.5 hours into the drive and about 15 minutes after a phone call, my screen went black.

Now I say black and not blank because the backlight was on. If you held the phone in the dark you could see the LCD light up, just all the pixels were black. From that point I did a soft reset, all the correct noises came out of the phone, but the screen didn't change. While waiting to think of something I even received another call.

Once I got to my destination I looked further. It did seem that the screen did not accept any input, touches with the stylus or my finger did nothing, but all the buttons seem to respond. Next I tried the Camera/Power Reset to put it in bootloader thinking my DCD rom was flakey (3.0.1) nope, nothing, blank. From this point I did a hard reset, 99% of my stuff is on the Exchange box and the Micro card...nothing, all the sounds, no screen detail.

Done, tossed in in my car and went on with my weekend.

That was Friday, now it's Sunday morning, I grabbed the phone out of my car and hit the power button...the screen came on and it started to boot!!!??!?!?? Since I buttoned the hard reset and never did the screen sync song and dance, that what I was greeted with. I aligned the screen, it did its reboot and done, the phone was happy. I reloaded my server settings, added my couple of apps and off I went.

Today out of paranoia I loaded DCD 3.0.4 just in case its a .1 bug.

Anyone else??
[Mogul, XV6800 General] bakntyme:
Did you have the phone located where the AC or heat was blowing on it? Extreme temps can make the LCD display stop working temporarily.
[Mogul, XV6800 General] SKullman:
Nope, outside jacket pocket, no sun, cool day.
[Xiaomi Mi A2 / 6X Questions & Answers] NguyenQui:
My a2 phone has updated to android 9 pie v10.0.2.0.PDIMIFJ with anti-rollback is 1. Now I can downgrade to android 8 oreo or convert 6x?

sorry for my english not being good.
[Xiaomi Mi A2 / 6X Questions & Answers] vagsvag:
At android one if u have unlock bootloader and critical anti rollback not working you can do everything u want, only be careful if u convert to 6x because anti rollback working unlocked or not.
[LG V20 Questions & Answers] thchipmunk:
Hello,

Most of the phone details are in the title as well as the question.

For some reason when I receive GIFs through MMS they do not play. When I try to save them locally they save as a JPG. I am on Verizon and can send GIFs and they play fine, but when I receive they do not.

I can post my APN settings if that would show anything. Texting has always been a problem. After every reboot I have to turn of WiFi and make a phone call before I can do any SMS/MMS.
[LG V20 Questions & Answers] paco3346:
Same issue here. A few differences:

ZTE Axon 7

I don't have to disable WiFi for sms to work

I had this issue on 14.1 as well

Using the Verizon messages app I can receive gifs but I assume this is because it's using black magic to receive the payload from vzw instead of the MMS endpoint in the APN.
[Nokia 8.1 Questions & Answers] Oswald Boelcke:
Guide to Nokia Device Forums (Please Read before Posting)

Please visit the linked thread prior to posting:

Device Forum Rules (Please Read before Posting)

In this thread, we will provide a short Q&A for your stay on this forum. Please read thoroughly and act accordingly. While most that is needed to know is pointed out in the Forum Rules, history shows that some points of these rules are not...

xdaforums.com
[Nokia 8.1 Guides, News, & Discussion] Oswald Boelcke:
Guide to Nokia Device Forums (Please Read before Posting)

Please visit the linked thread prior to posting:

Device Forum Rules (Please Read before Posting)

In this thread, we will provide a short Q&A for your stay on this forum. Please read thoroughly and act accordingly. While most that is needed to know is pointed out in the Forum Rules, history shows that some points of these rules are not...

xdaforums.com
[Nokia 8.1 ROMs, Kernels, Recoveries, & Other Devel] Oswald Boelcke:
Guide to Nokia Device Forums (Please Read before Posting)

Please visit the linked thread prior to posting:

Device Forum Rules (Please Read before Posting)

In this thread, we will provide a short Q&A for your stay on this forum. Please read thoroughly and act accordingly. While most that is needed to know is pointed out in the Forum Rules, history shows that some points of these rules are not...

xdaforums.com
[Nokia 8.1 Themes, Apps, and Mods] Oswald Boelcke:
Guide to Nokia Device Forums (Please Read before Posting)

Please visit the linked thread prior to posting:

Device Forum Rules (Please Read before Posting)

In this thread, we will provide a short Q&A for your stay on this forum. Please read thoroughly and act accordingly. While most that is needed to know is pointed out in the Forum Rules, history shows that some points of these rules are not...

xdaforums.com
[Android Software/Hacking General [Developers Only]] Ricky Divjakovski:
So, some of you may have seen my work from the Android TV Platform, as i have done with AMLogic based devices im in the process of doing the same for MTK based devices, im making a full functional tool to disassemble and reassemble MTK firmware, suprisingly the firmware structure is very similar.

If anyone is interested in learning more about MTK firmware i made a video on manually splitting MTK dumped firmware HERE, so check it out, like and subscribe to my channel for more content!

What i have done

- Made a program to split an MTK firmware dump

- Split the ramdisk header to allow unpacking

- Unpack the kernel/recovery

- Unpack system

- Unpack cache

What i need help with?

i need the following info

- How to make an MTK scatter file manually

- How to repack the system with the proper partition length

- How to unpack logo.bin manually

- How to dump a firmware manually over USB without SP flash tool

Ive done some research already and dug in abit myself with no success, if needed i can provide code, binaries ive built etc to help with this
[Android Software/Hacking General [Developers Only]] Matty1993:
Hey mate,

Ive gota fair bit of experience with Mediatek,

Scatters can be manually created using notepad +

All you have to do is lay them out correctly, i can upload a few in a zip if youd like ive got variations of scatters from

MT6572 nand & emmc 4 - 5 diff models

MT6737M emmc from 2 models

With taking a backup also i use NCK_MTK_Dongle theres a cracked version aswell that works takes all partitions and backs them up into singular .file format files which depending on the fs layout are as follows

Preloader

Uboot

Bootimg

Recovery

Secro

Logo

Tee1

Tee2

Simlock

Frp

Scatter_File.txt

Just for some examples,

I use mtk extractor to take the boot/recovery/system.imgs apart and repack but its only compatible with ext4 format, can also compile an ext4 system.img from scratch using it aswell, specifically though i use it for the boot and recoveries as its specifically designed to handle the MTK headers, also has a nice pull layout that consists of the kernel as a whole, ramdisk as a whole, boot.img boot_old.img, bootinfo.txt and then initrd folder containing the entire layout of the boot or recovery with init files and fstab etc but ive also noticed it will unpack and repack Qualcomm, SPD & samsung boot.imgs no problem also,

Unpacking your logo.bin also can be done with the program LogoBuilder lastest version that was released is 1.6 you can decompile the logo.bin edit the pictures etc then use the program to recompile it back into a logo.bin

Hope that helps you out a bit
[Android Software/Hacking General [Developers Only]] Ricky Divjakovski:
This info is somewhat useful, however im looking more towards a way of making a scatter file from a dumped firmware from a device, i see /proc/dumchar_info has some decent info, however some info i have no idea how its obtained

would you still be able to upload the scatter files for comparison?

As for the backup, what i wanna do is similar to what SP flash tool does, read from one memory address to another, i dont wanna use 3rd party tools either, i prefer to code them myself :)

I can unpack all that, and i can also repack the kernel, but the system im not sure how the size is defined, i may just recursively loop until a system.img larger than 2mb is created

Unfortunately that tool doesnt work with my logo.bin, ive tried but its pretty much a distorted image, and id like to code this myself aswell

Thank you for the info, if you can please upload those scatter files and ill keep you posted on the progress
[Android Software/Hacking General [Developers Only]] Matty1993:
Hey mate sorry for late reply im on aus time

Ahh i see what you mean now, im not to sure on how the system is defined to be honest mediatek is some what uniqe to say the least to me compared to everything else ive worked on before, ive noticed that aswell with fuzzy images in logobuilder inparticular on MT6979 the scatter though also had a very strange layout,

Speaking of which ive zipped up a few diff ones for you to use as reference, youll see some of the ways they are layed out is very different to one another as you will see defined within them,

https://drive.google.com/file/d/189H5EXS0ZqNuqn75A7ZNEOLo-Efq0T_h/view?usp=drivesdk

Ill be keen to try your tool once done aswell, are you going GUI based or Terminal command line based with it
[Android Software/Hacking General [Developers Only]] Ricky Divjakovski:
ah, im in aus time aswell

ill get this together one way or another, might just take a little time

it will be GUI based :)

Thanks for the upload!
[Android Software/Hacking General [Developers Only]] Matty1993:
All mate good to see another aussie on here :)

All sweet for things to work it takes time to figure out how they work first before anything is even built then debugged, completely understand im just happy to see some more MTK support happening as most of my tools are 4-5 years old for mtk so i think its great :D

Ill be waiting patiently cheers
[Android Software/Hacking General [Developers Only]] Ricky Divjakovski:
as i was saying most of the unpacking is done, the firmware structure is very similar to AMLogics(split the file from the start address to the file size in bytes), its pretty much just those few things i need, then repacking and i can dig into the GUI, id like to know more about how MTK droid tools creates a scatter file via ADB, it seems it uses some info from /proc/dumchar_info but that doesnt specify much, maybe the parameters are guessed???

ive attached a picture of my basic attempt to programatically create a scatter file, the highlighted lines are lines i dont know where this information comes from, nor do i know if those lines are the same for every MTK device