yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] Matty1993:
I need the log from the installer regardless,

I need to see what happening or i dont know Ill need a log from cyanogen recovery but both would be better cyanogenCTR has busybox to create symlinks wheras twrp does not, only reason installer was failing before was due to the boot img assert it would have still passed and completed with the failed symlinks thats why i always say to get the logs,

STATUS UPDATE FOR R11 MAX HS_Q6_MB_V1.0

=UBIFS

Im behind a little on build #003 so may need to push it back on release as im having some troubles with the settings.apk after restringing it if i cant fix soon ill revert back to old settings and hopefully have new settings in build #004, some updates include a whole new SystemUI with drop down bar to simulate CRdroid 7.1.2, new battery icon, animated drop down icons & status bar icons, facelock for extra security just for some sneak peaks

New build will be updated in a new post on this thread once completed.
[Miscellaneous Android Development] DJ Robby:
Here is the log from TWRP: https://pastebin.com/J8mtrYbv
[Miscellaneous Android Development] Matty1993:
I need the cyanogenCTR log also as mentioned in last post, TWRP has no busybox for symlinks i had to remove it to make the recovery small enough for your partition size in that log you provided nothing is being symlinked still CyanogenCTR has busybox so i need to see if CTR is symlinking to figure out if its just the install process or if your kernel is not compatible with my rom
[Miscellaneous Android Development] DJ Robby:
Ok, So here is what I did...

1. I used "Wipe All Data" in the Wipe Menu.

2. I mounted System, Data and Cache in the Mounts And Storage Menu.

3. I installed the test ROM from the Install Zip Menu.

4. I used "Report Error" from the Advanced Menu to save the CyanogenCTR log.

Aroma Installer Log: https://pastebin.com/FzF0xrSY

CyanogenCTR Log: https://pastebin.com/ja4H5AK2
[Miscellaneous Android Development] Matty1993:
Is the aroma installer log from cyanogenCTR also ? If so its mounting data this time unlike twrp saying device or resource busy but for some reason symlinks are still receiving permission denied read only file system which has got me really stumped as the /system needs to be ro in the fstab

What ill do anyway just to rule it out is change it from ro to rw and check the init.rc for any remount issues weird though as it works perfectly on my ubifs thats why i built cyanogenCTR specifically to install the rom so very weird indeed.
[Miscellaneous Android Development] DJ Robby:
The aroma installer log IS from cyanogenCTR.
[Miscellaneous Android Development] Matty1993:
Ok cool thanks for confirming that do mounts /data ok in cyanogenCTR so i think ill try to see if ive got some time today to go through the recovery and mount system as RW and look at the init.rc also for any mounting errors might take another look at the installer also see if i can make any more adjustments to the script

Im a bit busy today atm trying to fix the strings for my new settings apk but ive got nearly half of settings working so far so will try to squeeze it in today sometime and will upload here again once done.
[Miscellaneous Android Development] DJ Robby:
I know your busy but it's been a while so I was just wondering if you are almost done?
[Miscellaneous Android Development] Matty1993:
Havent had any time to look at it as of yet as i mentioned if i had some free time i would look at been busy getting update #3 finished for the R11 max UBIFS model ill get started on looking at the recovery and such for your EMMC R10 wont get much done tonight but will do as much as i can and finish rest off hopefully in morning for you.
[Miscellaneous Android Development] DJ Robby:
Please don't forget about me :)
[Miscellaneous Android Development] Matty1993:
Havent forgotten bud going right through everything to make sure its all correct i should have a new recovery and meta-inf for you today just about finished i just need to edit the init.rc and recovery fstab in recovery now all other inits and files ive been through and made some edits to eo hopefully we can get CM11 up and running for you soon
[Miscellaneous Android Development] Matty1993:
Hey mate sorry took so long,

I wanted to go through absolutely everything to make sure there is as little chance as possible that something will not work again, hopefully we can get you CM 11 installed now :)

New meta-inf to swap out

https://drive.google.com/file/d/1QHvV2hmD39K1OZc-eKbdR4UUEYMTLHcb/view?usp=drivesdk

New CyanogenCTR #002

Board variant = R10 ZM19E emmc + ext4

https://drive.google.com/file/d/14e7IrFO714MSDMY89b_nT8rJ0kP6JsuF/view?usp=drivesdk

Let me know how you go this time :)
[Miscellaneous Android Development] DJ Robby:
Still stuck on that same Welcome image.

CyanogenCTR: https://pastebin.com/501FkaGd

Aroma: https://pastebin.com/sd2EZK3W
[Miscellaneous Android Development] Matty1993:
You didnt swap the META-INF out with the new one i completely re wrote it as i beleive the formatting of system and data is causing the device resource busy error so id changed it to delet_recursive which is pretty much just rm -f it dosent actually format only wipes, if you look at the new updater script it states # Start Work ! Before it starts to do anything & at the end it states # Finish Work !

Try switch the scripts out,

Some progress though the new recovery seems to be working properly with symlinks this time and is setting them no problem at all, i added fstab, fstab.nand & fstab.fat.nand aswell as rewriting init.rc and editing all other .rc files so it seems to have paid off in that aspect symlinks are the second most important process after installing, then permissions.

Youll need to flash your boot.img with SP flash tool also as CTR seems to not be liking your mount path under /dev/boot even though its correct so its not flashing boot.img

So yeah switch out META-INF in rom, zip back up

Flash with new recovery then flash boot.img with SP flash tool and let me know how you go
[Miscellaneous Android Development] DJ Robby:
I don't know why the meta-inf wasn't changed, Anyways now I installed the ZIP and then flashed the boot.img and I get the "Welcome" screen and then the "Welcome" boot animation but after that, it goes back to the "Welcome" screen and doesn't change any more.

CyanogenCTR: https://pastebin.com/pTkVf6jh

Aroma: https://pastebin.com/CZUPcqKp
[Miscellaneous Android Development] Matty1993:
The logs are very weird indeed apparently it couldnt mount system and data but yet it extracted all /system files perfectly fine to /system so thats got me stumped i might change it to

Mount("ext4", "EMMC", "system", "/system");

Instead of

Mount("ext4", "EMMC", "/dev/block/mmcblk0p4", "/system");

I might also change the fstabs to include your /system usually though its not required for 4.x.x only 5.x and older and if it still has problems with system mounting ill chnage paths to your /dev/block/mmcblk paths in the recovery fstabs instead of them being /emmc@usrdata as such,

symlinks were all perfect this time again so that went sweet and confirmed that the system was placed within the /system dir

Boot.img did not flash either though, did you make sure you flashed boot.img i provided that i patched with busybox and made SELinux=permissive on with SP Flash tool? As all the extra cyanogenmod stuff may not run on SELinux=Enforcing.

But anyhow sounds positive when you say welcome boot animation is it the Cyamogenmod bootanimation with the spinning blue circle ? Any chance you can upload pics of the screens easier for me to be able to see whats happening
[Miscellaneous Android Development] DJ Robby:
No, it's the original boot animation, and yes I flashed the boot.img
[Miscellaneous Android Development] DJ Robby:
Are you working on it? You haven't replied yet...
[Miscellaneous Android Development] Matty1993:
Computer got KIA other day cant build anymore until its fixed been trying to get it working last few days to no avail but i need to get it fixed anyways as its got all my f*@#ing work on it :'( so it will deffo be fixed sooninsh in next day or two hopefully ive sprayed the PCB off with board cleaner and changed out a few thermal fuses on it that i found blew so now im just waiting for it to dry overnight to test again tomorrow morning and hopefully i can get back to it,

Ill comment here as soon as im back up and running again sorry anyways ,

Apologies to everyone else also who are waiting for the UBIFS Google play fix update.
[Miscellaneous Android Development] DJ Robby:
It's been 3 days, Is it working yet?
[Miscellaneous Android Development] DJ Robby:
Soo...................................Still waiting here.
[Miscellaneous Android Development] Matty1993:
Ive been on work holidays as i work near on 12 hours days running a phone repair shop most days plus computer at home which i use to develop these roms in my "free" time also died as i did mention in the last post on here i would comment when i would be getting back to it please have some patience i will be back at it today as i have a brand new computer which i bought when i got back and set up last night so i will be compiling 2 more versions of twrp for you to test install aswell as making 2-3 different rom bases with different /bin & /xbin configs however i beleive the problem is with the recoveries so will be trying to compile one with busybox to run all of the applets correctly located in the recoveries /sbin
[Miscellaneous Android Development] blakegriplingph:
Take your time mate, I can understand that real life does get in the way sometimes.
[Miscellaneous Android Development] Matty1993:
Try this twrp the screen will be small but it all works and has busybox, make sure all partitions are mounting and unmounting properly.

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

Flash the old slimmed down rom base i uploaded a while ago with this twrp first to see if it wont flash and boot,

If it dosent then try this base which i finished compiling today not long ago and see if that works its compiled from a diff models source than the last base and ive set it up as vendor build theres no boot.img either so just flash your stock with SP flash tool after flashing on reboot as ive disabled all the cyanogenmod stuff until a working base is consteucted

https://drive.google.com/file/d/1Toyzha94Qra3alTCWiG9t6uXIRasH5ZI/view?usp=drivesdk
[Miscellaneous Android Development] Matty1993:
Cheers mate :) yeah it does get quite hard with so little free time lately took today off tbh i need the rest and wanted to test new pc out i started looking back on your github also and my notes trying to figure out where i left off so will be hoepfully looking at the rest of it today and see if i can find anything wrong, any further luck with it ?
[Miscellaneous Android Development] blakegriplingph:
You're welcome. I can very well understand that real life can get in the way and all, so it's alright.

As for the Epic, nah, still haven't gotten that damn thing to boot to the GUI yet; all I get the most is the default wallpaper showing up and that's about it. It's a shame as I've spent months making it tick yet this is as far as I could muster at the moment.
[Miscellaneous Android Development] DJ Robby:
I can't get into my SD card with the new TWRP.
[Miscellaneous Android Development] Matty1993:
Try to sideload the rom to the device via adb terminal and using the sideload menu in the twrp

I set /sdcard mmcblk0p4 partition as /sdcard in the fstab and /ext-sd /mmcblk1p1 for you external sdcard so will need to be changed around,

To sideload open adb terminal on your PC, boot to twrp go to sideload option in advanced and connect usb cable to device and plug into pc

Make sure your adb driver is installed and is showing your device by issuing this command without the " "

"adb devices"

Once you have device showing type

"adb sideload dragromziphere"

The sideload it,

If sideload fails then push the file for flash to the device by typing this command, again without the " "

"adb push dragromziphere /sdcard"

This will send a copy of the file to your mmcblk0p4 internal sdcard partiton you can then go to the install menu select storage and select the sdcard partiton or which ever displays for mmblk it was pushed to,

Ill get around to changing the block mount probably tomorrow afternoon as i have quite a bit to get done tonight & tomorrow.
[Miscellaneous Android Development] Matty1993:
Bugger on the epic i still cant spot anything obvious in your github repo but theres gotta be something hiding somewhere anyhow youll get there eventually with it have you tried porting a 5.1 version from diff mt6××× cpu thats very similar Ive done it before with an mt6572 eMMC device i managed to port an mt6589 rom to

I just stuck all mt6572 files into vendor/hw and left the 6589 in lib/hw then all i did was add to /vendor/lib while leaving originals in /lib

libackd.so

libcamalgo.so

libcamdrv.so

libcustomnvram.so

libcameracustom.so

libegl.so

libmali.so

libfeatureio.so

libimageio.so

all libnvram.so files

Then switched out vold in /bin

Booted straight up on boot

not sure if your device has vendor support though my mt6737m had no specs on being vendor compatible but i tried to make a vendor build anyway and mine is deffo vendor compatible as its giving me greif about the vendor image being out of date on one of my CRdroid 7.1.2 builds,

Ive been keeping my eyes peeled for an epic still hopefully i can get one soon so i can help out
[Miscellaneous Android Development] blakegriplingph:
Yeah, I haven't tried porting other MT8xxx ROMs to the Epic though. Lucky for you, you were able to get 3.4.67 to boot Lollipop and later. Not sure what I've done wrong here.

And I'll see if I could arrange for having an Epic sent to your place for a nominal fee. I know a friend who has one actually. ;)
[Miscellaneous Android Development] Matty1993:
Maybe it could be worth a shot to find a similar spec mt68 with a cm 5.1 lollipop and switch all the gui out from /bin /framework & /lib just to rule it out as im nearly finished going through your github repo and tbh it all looks good so far i can spot anything i originally thought it may have been due to the vold but i can confirm on my 5.1 build i made for the pixi 4027a that vold was not set correct but the gui and whatnot still booted up anyway even with no vold managed storage available, this is what leads me to beleive its something to do with gui,

I was surprised when i got 7.1.2 functional on the stock 3.4.67 but i guess i kinda have a gift for stuff like that i guess as i managed to even compile miui 7.1.3.0 from xiaomi note 1 source and make it work on an mt6572 UBIFS device running a 3.4.67 kernel and is bug free :)

I just dont understand how a newer version of kernel like yours is receiving so much greif with it as even my 3.19.20+ kernel on mt6737m booted crdroid, rr remix & lineageos 14.1 build i created no problems at all,

With the epic also may have to give it a while so i can save some coin up and will take you up on that offer atm though i kinda splurged $4000 on a brand new top end pc as the other one just wasnt running right still after getting working again once i got some coin again but im in :)
[Miscellaneous Android Development] Matty1993:
Ill have the new recovery up today for you with changed mounts, how did you go with sideloading or pushing it to device with adb ?
[Miscellaneous Android Development] blakegriplingph:
Yeah it's puzzling that you were able to somehow get things to work on an earlier kernel. Think it may have something to do with integrating the shims to libutils but idk where else to shove it in as the libxlog method only results in being stuck on logo.bin.

As for getting the Epic, do you mind if I have a friend of mine send one your way? The only payment being the shipping fee so you don't have to splurge so much on one just for development's sake. It's an ex-demo unit that his niece previously used iirc.
[Miscellaneous Android Development] Matty1993:
Yeah ive got no idea how i keep managing it either stuff always just seems to work straight away most of the time for me,

Yeah if you want to have one sent my way so i can help out id be happy to cover the shipping costs on it
[Miscellaneous Android Development] Matty1993:
Ok try this one

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

microsd card has been set as

/sdcard vfat /dev/block/mmcblk1p1

Your onboard sdcard that is mmcblk0p4 i have set

/ext-sd auto /dev/block/mmcblk0p4

You should be able to install the test bases with it now, if you still cant get into sdcard let me know i will change it from /mmcblk1p1 to mmcblk0p1 and it will work should be ok though afaik all emmc use the 1p1 mounting.
[Miscellaneous Android Development] blakegriplingph:
I guess it's a matter of luck then.

Do you have Discord or some other venue where I can contact you privately? As I need your shipping address so that my friend can send his spare Epic to you. ;)
[Miscellaneous Android Development] DJ Robby:
It didn't work, At this point, I don't know what's wrong so I'll just flash the original ROM back and just stick with that. I REALLY appreciate how much you helped me especially for free and maybe one day I'll come back and we can continue. For now, Goodbye.
[Miscellaneous Android Development] DJ Robby:
Nevermind, The phone is pretty much unusable since it has some malware called FotaProvider and I tried everything to remove it and I couldn't, It just spams me with pop-ups and most likely steals all my data.
[Miscellaneous Android Development] Matty1993:
I only use xda i dont even have facebook tbh i like to stay off the grid especially since the fb privacy leaks i dont think ill be using that again had a notification stating they stored my password on there servers in plain text for anyone to be able to read, all i got was "we are sorry this has happened" havent been on since,

If you want to tee it up and what not though just flick me a pm my notifications dont work most if time for pm but when i get round to looking and what not we can work it out, if you can get me a rough total of what shipping would be id be happy to forward payment through beforehand :)
[Miscellaneous Android Development] Matty1993:
Not sure why you qouted that string of txt as i did mention its very hard to work blindly without having a device in front of me to figure out how to build for it, especially also as these devices have no source it takes time to perfect,

Id also strongly advise againt flashing the stock firmware back and if you do whatever you do DO NOT sign into it with your google account the devices software is riddles with chinese spyware and adware, even the stock cooee launcher on all the device downloads popup and spyware material,

If i could get my hands on one of the devices i can build something with ease after 6 months of studying the R11 max ubifs i now have a folder containing 15 different roms all built for the R11 max from miui 7 & 9 plus many more others most are ports but the miuis and a few others are all compiled from advan S5E sources as everything is basically the same as my r11 max.

If your feeling adventurous and willing to learn and put the hours in i suggest maybe checking out the xda-university you could learn a few things and maybe build & debug your own rom.
[Miscellaneous Android Development] blakegriplingph:
Yeah I do understand that. Problem is that my folks message me from there so I'm pretty much stuck there for the time being. I could set up a private and secure Jabber server just in case, but eh.

And sure, just check your inbox mate, I hope you'd be happy with that Epic xD
[Miscellaneous Android Development] blakegriplingph:
[MENTION=9139800]Matty1993[/MENTION] Sorry for the double-post, but did you get the PM I sent to you?
[Miscellaneous Android Development] blakegriplingph:
[MENTION=9139800]Matty1993[/MENTION] Did you get the message I sent to you earlier? I am still waiting on getting your mailing address so I can have one of my friends send the Epic to you at a nominal fee.
[Miscellaneous Android Development] blakegriplingph:
Sorry for spamming your thread, mate, but I haven't heard from you in a while so thought I'd say hi.

I sort-of rebased my ROM with a cm12.1-test branch kanged from [MENTION=3064479]pix106[/MENTION]'s Lenovo ROM just to sanitise things and rule out the Frankenstein device tree I made previously as the culprit; the latter did sort of work after fixing the fstab and other stuff per your suggestions, but still it was a rather hammy mismash so I thought I'd refactor it to a more credible base.
[Miscellaneous Android Development] Matty1993:
No problem at all blake, ive pmd you back,

Attention all there will be no new development for CM 11 for the coming weeks to a month i am quite ill,

Your patience is appreciated and i will be back at it once better.
[Miscellaneous Android Development] blakegriplingph:
Cheers mate, and don't worry about the Epic either, I'll see what some of my other mates can come up should they be able to pitch in with things.
[Miscellaneous Android Development] paperbird:
th a n k s ...................... :good:
[Miscellaneous Android Development] Matty1993:
Your most welcome mate,

Ive got even better news tho i have lineageOS 13.0 android 6.0.1 for the R11 max hs_q6@R11 Max lso just need to fix sd card mount now and can release it will also be releasing for all zm12@r11 & also zm9@r10 devices as well on seperate threads so no one gets confused

So as of today there will be no new support for cyanogenmod 11 android 4.4.4 due to the updates in android security on 6 and the all the security vulnerabilities on 4.4 i think its best to move on to something more secure.
[Miscellaneous Android Development] SiXtyNiNe:
hi I have lost imei with accidental command "format all + download" is there a method to fix this? :(
[Miscellaneous Android Development] Matty1993:
Youve wiped your nvram and protect partitions flashing with sp flash tool will not restore them even with backups of the partitions

Do you have the Q6_MB_V1.0 R11 max board variant if so i can possibly help you out ?
[Miscellaneous Android Development] SiXtyNiNe:
Matty thanks for the reply. Yes I have the variant Q6_MB_v1.0 is there a possibility of recovery?

sorry my english I'm Italian :mad:
[Miscellaneous Android Development] Matty1993:
Yeah should be able to help so your in luck i just posted an android 6.0.1 MokeeOS rom which is based on CM13 for the Q6_MB_V1.0 board which includes the sec related files in the installer so should restore your imei and what not when you uprgade link is here id suggest to update not as stable as CM11 but far more secure than android 4.4 :)

https://xdaforums.com/android/development/ubifs-t3965140
[Miscellaneous Android Development] SiXtyNiNe:
ok i try it ...i follow the instructions. then i'll let you know. thank you so much. :o:good:
[Miscellaneous Android Development] HD_Man_2000:
Good day

Good day, I can’t flash the phone according to this instruction, is it possible to provide this firmware in the form of a backup for recovery?
[Miscellaneous Android Development] Matty1993:
Hey mate what model is your R11 firstly before doing anything if you take the back cover off you should see where the sim cards sit there is a slight gapp with a bit of the logic board showing, this will have a printed nnumber on the board ill need that first as you might be trying to flash this to the wrong model,

Secondly also cyanogenmod 11 is outdated i have a newer lineageOS 6.0 build i did a while ago for the ubifs R11 max, this model is Q6_MB_V1.0 anyhow,

If your model number is diff i can still try to build a working firmware for you.

I cant provide a working backup however as this is set to be flashed via Carliv based recovery which backups from when my test device was still working were having mismatched MD5 so couldnt be restored, and i cant take a block backup as my test device is stuffed with a dead lcd now unfortunately.

Cheers