yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] Matty1993:
Sorry for late reply again mate,

My notifications play up alot as i use the mobile app and dont get them most times unfortunately so dont get a chance to reply until i jump on next,

Oh real /data & /system must be diff from my 5044T but this is optus had to revert to the optus U5 system .img as the unlocked U5 system.img wont read any other simcard apart from optus any other sim it says no sim inserted but when i flash back optus system.img and simlock it prompts to enter a network unlock code eith another sim, i think optus hired a decent team of engineers and developers on this one,

Anyhow, /system & /cache both mount perfectly fine on mine its just the encrypted data that wont mount, but to get around it and to get it to mount without modifying the boot.img i built in the option to wipe /data & meta data BUT this is if you want to flash a ROM zip when one is created for this model DONT use it otherwise or the device will not boot,

So to rework that problem what i did is patch the ramdisk again for anyone that just wants to root the device with magisk as thats about all that can be done with them until a rom is developed maybe ill give it a go but without source im out of luck so will leading in blind trying to figure stuff out,

Im going to write a tutorial up and ill post the link here on getting these things safely rooted with magisk for everyone, post will have screen shots at the bottom of it also,

With my 6.0.1 its buggy but its running with SDK23 in the build.prop i have no force closes of any apps anymore apart from the launcher no matter what i do or what launcher i try it just wont work the launcher it comes up for a second then force close

My thinking is that may lie within the uiautomator.jar and framework.jar i may need to pull them down and re adjust the code within but that it all else is sweet on it :D mediatek jumble **** around in the system to say that an app is something else to what it actually is so figuring that out is just as bad haha

Oh and making flashable update zips and what not is easy as pie man :) download ADK (Android Development Kit)

Has apktool prebuilt in with a adb command terminal also,

You can import dependencies

its got prop tool,

directory explore,

generate & sign apk,

deodex tool,

Hex editor

Android image tool for unpacking and repacking .dat, .sin, boot/recovery aswell as usersata and custom packs,

Also has reverse engineering tools for

.apk

.jar

.dex

.smali & baksmali also

I recommend it i use the free version and works great
[Android Q&A, Help & Troubleshooting] Matty1993:
Hey mate,

Yeah tried all that seems optus have stuffed part of the imei within the actual system.img as imei is there and working with otpus system.img but when i flash just the alcatel U5 system.img it says the imei is invalid however the SVN is still there and active, very weird indeed i was under the assuption it was all controlled through NVDATA, Protect S, Protect F, and in some MTK the persist, never seen it within a system.img before, i liked the U5 interface tho so gonna just copy all the priv-app/app & framework-res.apk from U5 and manually push them to the system and chmod 644 them while the shells stopped now ive got Root access, gonna remove all the crappy bloatware to while im at it lol,

Yeah good thinking on the boot.img and recovery i forget sometimes that this stuff can be pretty hard and eery to the inexperienced for sure haha,

Im going to be changing all my props to insecure within boot & recovery,

Did that with my MTK6572 im porting also set adb to default in boot.img and recovery, still havent managed to get a custom recovery on it though proving a real pain with only 6.1mb recovery and a 512mb flash nand partition all my attempt at porting and even building from scratch result in a flash of a white screen and reboot on this POS haha closest ive gotten so far is a heavily modified stock recovery with adb set to enabled when recovery first boots and also in adb sideload mode, ive tried even manually adding the new info into the cpio list and placing resources and packing it but it never packs up, i think it may be the kernel though it pretty acient and again with no source i got nothin to build from :(

I got alot of bugs at first on the 6.0 also almost everything was force closing but i manged to debug it all the way down to just the launcher now :D im a persistent person tho so ill get there eventually ive got a box full of phones at my disposal all rooted that i can pull buts and peices from and mod into it to make the sucker work,

Yeah check the adk out tho brilliant can do pretty much anything as long as you know what your doing but youll have no problem at all should be a breeze for you

---------- Post added at 12:09 PM ---------- Previous post was at 11:37 AM ----------

Tutorial is up for rooting 5044T & 5044D is also compatible with standard U5 i got one of those aswell and works with that also all links for everything are at the bottom of the tutorial please read it carefully first time/inexperienced users ive tried to make it as user friendly as possible,

Dont forget to hit the thanks button on the tut if it helped you out couldnt get the screenshots up as XDA app freezes on uploading them so will get them up when its working again

https://xdaforums.com/android/development/guide-optusxspirit5044d-tmt6737m-t3886631
[Android Q&A, Help & Troubleshooting] Matty1993:
Yeah me either i couldn't beleive it but its definitely something with it ive tried over and over and over again its 100% in the system.img ive been scouring /dev /system & system/firmware for it but nothing yet i think it may be a ranamed file to put people off so chance of me finding it were slim lol

I ended up just changing the frameworks and system UI out aswell as getting rid of all the useless crap they installed to it interface is absolute crap aswl compared to the U5 inteface icons are diff and the wallpapers far better on U5 also minor changes to system UI aswell hence me changing it all,

Thinking about the fstab also your probably right bo fiddling about then great idea mate, me i just stop when stuff works haha had to leave it for a day or two tho to catch up on my other two projects,

Finally built 3 working custom recoveries for my MT6572 nand as there are litterally none available but i had to build them from emmc source and im having such a hard time trying to get them all to mount partitions as UBIFS im somehow thinking its possible as when i mount them as yaffs2 they end in the argument is wrong with it same with Vfat format for the logo recovery etc, weird set up this one according to my boot.img the cache, system and userdata are all emmc@system etc and are ext4 but yet run through and MTD partition its got me so stumped im only able to properly mount the partitions when they are set as emmc inwhich it takes backups and what not and the system storages are there and not 0mb but when restoring them the system breaks so been working on that flat out, im about to have another attempt at TWRP now for the 5044 :) and you are correct again also it seems all our models use the 5044D recovery so that cross compatible throughout the variations

Ill eventually get around to porting a custom rom to it hopefully with android P but that will be a long long way away yet i need to build myself another rig to run BBQ linux again so i can build from the P source and what not, my old one is kaput & fubar all in one haha

If i get a working twrp ill let you know here UI is alot better than philz and more simplistic to use
[Android Q&A, Help & Troubleshooting] Matty1993:
Little update for everyone ive finally managed to get a booting TWRP after rebuilding like 30 diff sources to see what was compatible now all i need to do is figure out the mounting points as it wont mount /system /data /cache :D
[Android Q&A, Help & Troubleshooting] Matty1993:
Hey mate,

so true the TWRP source i found that i was able to build a working bootable source from and the only one was a russian built emmc for a LG G5 with no english option LOL i managed to get everything to english so far i cant get it mount still so im gonna use adb for the cat proc/dumchar_info

And cat proc/partitions to see exactly where they attach to and see if i can figure out the device map im trying to do it based off the U5 source instead of the optus as the props for the optus firmware are severely edited and riddled with ro.security codes to lock the system down, stock U5 has not as much and is alot more readable,

You want me to have a look at your lineage 14.1 build ? Im pretty good with bug fixing and can do just about anything woukd be alot easier to fix it on the OS in front of me than trying to pinpoint what the issue could be as it could be many many things, up to you anyhow if you want to happy to look at all other bugs aswell for you,

With the dm-verity also i removed the encryption footer on the /userdata so no wonder it didnt boot after that, ill give what you mentioned a go see if that will work, once it does and i get TWRP to mount i can continue building my flashable zip to disable all device security related to OEM lockdown etc,

Init.d scripts i added are

00_Syscleaner

00banner

01_zipAlign

01_purging_trash

01serial no

02_Loopy_smoothness

02_internet speed

03increas_battery_life

05pdbiot

06pdbvmt

06removecache

10pdbkms

23-dap.sh

69removelogger

70zipalign

90userinit

98SdBoost

99SuperSUDaemon

S70darky_zipalign

Sqlite_optimise,

All that is required is for busybox to be installed and busyboxes applets run the scripts in the background, i also mirrored these scripts into and addon.d directory just incase some dont catch in the init.d directory,

Have also edited the build prop with tweaks for system performance aswell,

Am happy to look at your build and do some optimising for you if you dont its all good i just like to help :D
[Android Q&A, Help & Troubleshooting] Matty1993:
Hey mate wont need the twrp source i been messing around with the one i got booting ive got most partitions mounted i need to do some major debugging but i successfully backed up boot and system and restored them successfully also, internal storage is also mounting properly,

Yeah if you need a hand pm me the link to the zip and ill do some fixing up for you cameras are very tricky on them, overall though from what youve told me youve done a great job so far :)

I changed the following also from both the stock optus & U5 boot.img aswell to remove dm verity but was a no boot unfortunately,

/system ext4 rw (removed wait,verify

/userdata ext4 etc etc etc(removed encrypted mount text for meta data)

Also removed

Encrypted=data drom further down,

Also did the same in the f.stab in recovery just incase still no boot, boot logo goes to start over to the animation but never gets to it,

Ill probs have another look tomorrow with a freah mind haha but yeah wouldnt mind checking your rom out, anythings better than the OS on it haha

Yeah theres alot of init.d scripts but theyre only like 2-3kb so dont hog any space diff is amazing aswell with the scripts and a few tweaks to build.prop performance is almost doubled on MT6572 makes this 5044 go alot faster aswell
[Android Q&A, Help & Troubleshooting] Matty1993:
With great great difficulty i managed to get them to mount turns out its all in the argument required to mount the partition it has to be the correct syntax to the tee also spacing out of the partitions correctly is required aswell, gona get back onto it this arvo after work,

Cheers for the F.stab aswell ill give it a flick over and look at the diff,

Amazingly though my boot.img started working with all edits id made weird, all i did was take a nandroid through my TWRP i made & then restore it through TWRP and it booted straight up no problems maybe due to the partitions being encrypted and me removing encryption from it,

Either way ill patch it up so its all good hopefully,

With your camera also you should chech the cam libs in /system/lib

Try and replace the following with newer & older libs from diff firmwares thats what i did to increase the cam performance on my MT6572 with only 5MP camera

camera_adapter

camera_metadata

And change this one in /lib/hw,

Camera_default.so

Each lib you replace though run the camera app each time to initialize the new lib it should try to initialize and the app eill crash open it again & if the lib is compatible the camera will now start up perfectly,

If the lib is incompatible it will force close the app or say cannot connect to camera,

Dont switch out any other cam libs but those ones though it will cause the system to possibly break,

Yeah id be keen to check it out, once ive got this TWRP all sweet and working well ill post it up on a thread so you can download and try etc,

Much much easier than the philz to use in terms of ui
[Android Q&A, Help & Troubleshooting] Matty1993:
Ok so i think ive gotten it all ironed out after days of messing around with it still a few little bugs with it but everything is mounted and i can backup and restore no problems, MTP finally is working on it aswell as sideload which is tempermental,

I had to skip on the russian TWRP that i was originally working with as i just couldnt get the applets to mount to the twrp applet properly and hence functions wouldnt work and would break recovery, ive ended up building from an old MT6572 TWRP 3.1 applet i had lying in my TWRP folder that i managed to get to work with the MT6735M processor,

Ill have it up tonight or tomorrow for everyone latest to try but it should be treated as BETA software and i cant gaurantee it will be 100% bug free so please keep that in mind also but i think we finally have twrp for out 5044T,

However just incase you should have issues with TWRP for any reason ive fixed my Philz recovery build completely and is all working well now and link will be replaced with the updated version,

No problems at all with new philz can mount & unmount

System

Data

Cache

No problems at all now ive also patched for DM-Verity removal in the boot.img however yous may need to format the data partition in recovery before booting or it WILL NOT boot,

Oh looked at your recovery.fstab aswell [MENTION=5125635]user154[/MENTION]

Unfortunately mine is much more complex than yours and was not interchangeable seems our 5044T have 3 sets of encryption 1 for /system, 2nd on /data & again on /data but at a different mounting point why they arent universal i dont know condisering they use the same chipset must be the vendors edits to boot.img before release of phone i think optus has gone above and beyond on security ive found 15 lines of ro. Code in the build.prop that enables extra security on the devices i found this out with magisk would install the zip said it flashed successfully then reboot and magisk app is there but no magisk imstalled, when i did get it installed and working busybox wouldnt install any applets to the system then upon reboot root was gone, ive redone the build.prop and also made a flashable .zip for low ram enabling on the devices so they run alot smoother, got the idea from android GO they use the same ram optimisation to enable it to be run on 512mb of ram :D, havent tested it yet though still removing ro. Code from build.prop and /etc folder

Hows your lineage going aswell did you get the camera issue sorted out yet ?
[Android Q&A, Help & Troubleshooting] Matty1993:
Hey everyone ive posted a TWRP 3.1 beta build up for download is available now here on my XDA post

https://xdaforums.com/android/development/recovery-t3891883

I cant gaurantee all fucntions work but most should there are no errors in the dialog upon booting it.

Enjoy everyone any problems or bugs you find comment on the post and ill try to work them out ASAP for everyone
[Android Q&A, Help & Troubleshooting] Matty1993:
Hey mate,

No dramas at all im bad for it to haha,

Thats great i tried that aswell on both my TWRP applets using just the philz rcovery.fstab wouldnt recognise the argument on both for me unfortunately so was stuck using the old MTK6572 recovery still newer version at 3.1 but applets are somewhat outdated on it, i had to mount all.my partitions in a precise way with weird spacinging in between,

Youd think they would make a generic F.stab for all model that are 5044 i think its just silly the amount of effort gone into locking it down with all the "security features" indeed ive had a good chuckle at some of the lines of crap ive come across so far haha,

I didnt notice about the init either ill have to take a look at it not that i need it now ive patched for low ram the system is alot smoother even window transitions are alot quicker,

Speeking of the low ram .zip all it actually is, is another one of my addon.d scripts from my collection to enable the low ram all ive done is tweaked it for this device specs and packed it up so it can be flashed through recovery rather than installing it via adb or through a file explorer and manually creating the addon.d directory then setting perms and placing within so yeah very basic peice of script but very very effective they actually utilize the same script within android 8.1 GO ehich is what makes it compatible with the 512mb ram minimum requirement for it,

Managed to patch it for my MT6572 also aswell as getting the SDK23 6.0 dedicated system functioning and working for it now i just need to figure out why its force closing only downloaded or installed apps and not system apps, strange it is but i got it functional at least :D

With your cam libs to most you shouldnt replace as they have attached code for system functionality if you remove the wrong one you will bootloop,

Safe to change cam libs include,

/lib/hw/camera_default.so

/lib/

libcam.camadapter.so

libcamera_metadata.so

If you still face troubles with the camera after changing these out to other working ones takes same from the stock firmware for the device and replace them, if still not working properly take the following from the stock firmware from

/lib/

libcam.campipe.so

libcam.camshot.so

libcamdrv.so

libcamalgo.so

lib.cameracustom.so

Not to sure if your model has it either but check out /framework/

For a .jar file called "org.codeaurora.camera.jar" see if you have it in there and tranfer to Lineage i can confirm this .jar is cross intergrateable between android 4.4.2-7.1.2 and works,

I set perms for the .jar as =rw r-- r-- and rebooted in return upon factory reset and checking again it generated a .odex for the .jar maybe that could help possibly ?,

Anyhow ill dig through my pc at some point today for the low ram zip and ill post it up here for you
[Android Q&A, Help & Troubleshooting] Matty1993:
Link is here for the low ram enabler see how you go with it finally found it lol,

Low ram enabler:

https://drive.google.com/file/d/1VoicoEC2v55Owwi4fU0X7iENsr_deJqH/view?usp=drivesdk

everyone else is also welcome to flash it through twrp,

Or philz which is now fixed and lineage themed aswell :)
[Android Q&A, Help & Troubleshooting] Matty1993:
Hey mate,

Yeah i know took me forever to get it i redid the script at least 80 times to get them to mount, seems i forgot to add SD card mount in mine tho so need to add that to it its on my list lol , but yeah would be interested to see if your TWRP applets in the sbin are cross compatible with my TWRP applet as the newer versions are much much more stable,

Can buy the optus x spirtit 5044T currently for $89 in aus atm and never had so much trouble with a phone whereas my S7 & S8 cost alot alot more and were so so simple to modify,

Anyhow yeah give the low ram script a go it made a huge diff on the 5044T stock firmware so should optimise your lineage system also, if you for any reason want to move it or remove it, it will be located in /system/addon.d or /system/etc/init.d,

Bugger on the camera to usually lib swaps work quite well, ill take a look at the logcat see where the error is defined within hopefully it shows each process and the origin of the problem,

Logcatting errors i define from the letters in the logs

I= information

E= error

V= verbose

D= debug

W= warning

F= fatal

S= silent

The main two that will break your system are usually defined under E or F also include S aswell S is one of the highest priorities to sort as it prints nothing within a logcat but in general speaking E & F are system breakers ill look through the log for you anyhow and ill post my findings back here for you hopefully with a source to the problem :)

Oh with the release id say if its stable enough system wise and a majority of apps and functions are working then why not :) ive currently got LOS 16 on my S7 and the camera crashes every time a picture is taken with the flash on lol aswell as pics not saving sometimes if you do just list it as beta and with a list of known issues, hopefully we can get this ironed out for you soon though :)
[Android Q&A, Help & Troubleshooting] Matty1993:
Hey mate,

I checked the log out for you and have created a .txt file ive cut out the errors from the original log and pasted to a new file,

Ive also added notes at the bottom of all errors which tell you what the issue is,

From what ive read it indeed seems you have incopatible cameralibs some are working however some are not as you will see defined withing the log,

1 file also does not have permission to access on 2 occasions so ive included that also,

Aswell as a file within /vendor/mediatek/proprietary/hardware/mtkcam/legacy/v1/client/displayclient/StreamImgBuf.cpp seems to have an error related to it also which ive made notes about in the .txt file also.

Hope this helps out a bit for you

Other than that everything seems good some are verbose but are of the lowest priority and dont usually hinder thy system as they are debugged usually within the system itself
[Android Q&A, Help & Troubleshooting] Matty1993:
I managed to stumble upon a lineage 16.0 android 8.1 rom im gonna try build port for this 5044 device im not kidding anyone here but the original device the 16.0 is based of legit has the exact same MT6737M (23nm) processor exact same quad core 1.3gh cotex A53 processor & exact same GPU of Mali-T720 :D should be a walk in the park

Oh also for everyone i finally got around to adding the micro SD mount to my TWRP 3.1.0 so will upload soon on my twrp post,

How did you go debugging the video camera also aswell [MENTION=5125635]user154[/MENTION] i was adding libs to my MT6572 camera from a diff model some were not originally there beforehand anyjow interestingly enough my video camera also no longer works and only the camera ? Go figure lol, it jusy popped into my mind that maybe you have a lib that isnt supposed to be there that may be also affecting the other libs making them incompatible, anyhow gonna start on this port :) hopefully itll be a booter first time
[Android Q&A, Help & Troubleshooting] Matty1993:
Hey everyone my TWRP 3.1.0 link has been updated to the new updated version, you can find it at my link here https://xdaforums.com/android/development/recovery-t3891883

Whats working,

* SD card mounted

* OTG fixed

* Terminal Fixed (no more child process exited error)

* Sideload but may still be buggy was working for me today however.

NOT WORKING :

* MTP got absolutely no idea why will look into it again tomorrow :D
[Android Q&A, Help & Troubleshooting] Matty1993:
Try my version on your alcatel U5 its for 5044T but the recoveries all seem to be the same, if it dosent work upload your recovery file and ill build it for your device but it should work no dramas