yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] DJ Robby:
So does that mean Oppo Touch Recovery is useless? So I should just put CWM in the recovery and then flash the CyanogenMod11 with CWM If I could get more detailed instructions that would be helpful as you know I am a noob...

Edit: So I flashed it with CWM and it failed, Here is the log: https://pastebin.com/i2F55g08

What I think happens is the first image that says welcome comes up, Then the boot animation comes up but it doesn't finish before returning to the welcome image that was at the start and it stays on that forever.

Edit 2: I also don't know how to restore the backup with SP Flash Tool but that is ok since this isn't my everyday phone so i'll just wait until you fix the ROM.
[Miscellaneous Android Development] Matty1993:
Hey mate i took a look at the log,

For some reason it didnt symlink any of the system files or set the perms for them

Modified boot.img didnt flash either for some reason so surprised it started playing animation so all my adjustments from ubifs to ext4 must be correct

In the script

Format was ok

Mounting was ok

Extract system files was ok

I think it may have something to do with CWM possibly as thats the only reason its not booting none of the files have correct perms everything else went ok though, so ill see what i can do today about another recovery for you,

The oppo touch recovery is just a stock recovery i added to get rid of the 3e recoveries these phones originally come with, much nicer is all,

To restore your backup using SP flash tool open flash tool, select the scatter box,

Navigate to your backuo folder & double click on the scatter_file.txt,

All of your partitions and files will automatically load up for flash,

Change the download mode to download only

Power off phone click start download

Connect phone & wait for flash
[Miscellaneous Android Development] DJ Robby:
I will just wait for the new Recovery and ROM to work because like I said before this is a device that I didn't use at all but I will probably use it once I get the ROM. Again I just want to thank you for all your help since because of you I don't need to throw out this horrible phone.
[Miscellaneous Android Development] Matty1993:
Theres deffo nothing wrong with the rom ive been through it again so is deffo just the recovery not setting the symlinks to the device :)

Ive managed to compile a TWRP 3.1.0 for your device which i know boots as i built it also for my UBIFS r11 also to test,

Everything seems to be working but ive had to suverely slim it down,

You will need to tell me if there is any red writing saying mount - o sd card android_secure or if theres any sdcard mounting once it boots up by tapping the icon in the bottom right hand corner i need to make sure ive set the mount correctly for your sd card as usually they run through /sdcard or /external_sd but your device has a dedicated /dev/block/mmcblk0p4 for sdcard so it may be the FS for your internal EBR1 partition in which ill need to add the external_sd mount for your microsd

Let me know how it goes anyway its TWRP version 3.1.0 and all good hope we can get it working for you, shame i cant get my hands on one of the ext4 ones as id be able to build android 6.0 or 7.0 for them oh well ill get one eventually lol

https://drive.google.com/file/d/1NRi43ElrzwcnZL1NS_SZwtENl-JZlvYl/view?usp=drivesdk
[Miscellaneous Android Development] DJ Robby:
I see 2 errors

E: Invalid block device... (This one shows a few times and each one is slightly different so I'm not gonna write it all out.)

mount -o bind '/data/.android_secure' '/and-sec' process ended with ERROR: 127

Also, I can't get into the SD card for some reason to install the ROM.
[Miscellaneous Android Development] Matty1993:
Ill need just the block device errors dont need to write them all out i just need the end fs error such as as system or cache whichever they are so i know which blocks have the error to change the way they are mounted

And yeah thats why i got you to test it out to check the sd mounts so the sdcard must for sure be your EBR1 partition which is your internal sd card storage which wont contain android_secure this is for ext_sd cards so ill fix that up but i need the block devices to fix the errors

## EDIT

i dont need to fix the mount -o bind error as any rom can still be flashed fine with it as mount -o bind error refers to only the android_secure on sdcard not /system i have confirmed this by sticking my pixi kernel into it and flashing my lineage os 14.1 and 13.0 builds to it and all works fine rom boots ok even ported my Cyanogen 11 instead of building from scratch for my pixi 3 as its only a test and i have Lineage 14.1 already so no one wants to spend 7 hours compiling for a test build anyhow it flashed and booted up ok so TWRP will be ok for these models.

So all i need are the block device asserts that are listed on screen to fix them up and you will be able to flash the rom no problem then

## edit again

So i tried to fix mount -o bind error anyway wasnt successfull BUT ive gotten it to show up now at least so if you go to wipe then advanced wipe and select android_secure then tap wipe/format it will wipe android_secure completely to remove all data for the new rom even though still works fine without wipeing it for the next TWRP ill upload once finished.
[Miscellaneous Android Development] Matty1993:
Heres some pics to show TWRP all works even with sdcard mount -o error last pic is not CyanogenMod 11 Build it is my unreleased 14.1 build for 4027A :)
[Miscellaneous Android Development] DJ Robby:
Here are the beginning of the errors..

E: Invalid block device 'boot'

E: Invalid block device 'logo'

E: Invalid block device 'misc'

E: Invalid block device 'nvram'

E: Invalid block device 'recovery'

Edit: Also you said before that you could've made android 6.0 or 7.0 for the phone if you had it, But if the problem is that you can't test it then I can test it for you! Android 6.0 or 7.0 would be very nice, Or maybe android 8.1 go? Since it takes less space, Anyways if even android 5.0 or above is possible I would be happy to test it for you.
[Miscellaneous Android Development] Matty1993:
Hmmm strange i didnt expect those to be the error blocks as your stock recovery fstab is set out as

/boot boot

/logo logo

/misc misc

/nvram nvram

Which is usually the way they are to be mounted in custom recoveries,

What ill do is switch them all out to mount through /dev/ to see if that will clear the issue up as some mtk mmc devices all of the above are run through mmcblk0 which is also home partition to preloader so ill see if that works,

As for android 6.0 or 7.0 it is only a possibility as these all have 3.4.67 kernel and ive built LineageOS 13 and 14.1 for Alcatel 4027A with 3.4.67 kernel BUT there is no kernel source available for china phones at all so it would be hit and miss for months and months on end to try and get it working so would need a test device in front of me for beta testing

Same with cyanogenmod 11 took me 7 months of hit as miss compiling from various sources to get a working custom rom for the R11 max UBIFS models

Only reason i was able to compile for Alcatel 4027A is due to MicroMax A102 being practicall the same apart from the way the vold, nvram, EGL and mali all work

Android 8.1 GO is definitely not possible at all on these boards android 8.1 go requires a minumum of MT6580 Quad core to run, MT6572 Dual core cannot handle the cpu strain, and TBH i had to add 70 lines of code to my alactel 4027A LOS 14.1 build.prop and adjust the dalvik heapsizes etc just to get 98MB of useable free ram and a mostly smooth GUI.

Anyhow ill get onto the recovery today sometime and will post a new link here once ive added the microsd mount and fixed your emmc mounts
[Miscellaneous Android Development] Matty1993:
Try this one

Twrp 3.1.0 R10 emmc #002

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

Ive set the error blocks as

/dev/bootimg

/dev/logo

/dev/misc

/dev/recovery

As i have a feeling they are mmcblk0 managed

Anyhow let me know how it goes and if theres any red writing again i fiddled with android_secure again also so it may or may not still have the mount -o error for sd card but will flash rom fine with error once all blocks are mounted.

External SD card has been mounted under mmcblk1p1 mmcblk1 but you also have the internal sdcard storage under mmcblk0p4

So 1 should state sdcard this is your intenal phones storage which is set under vfat mmcblk0p4 the MicroSD should appear as MicroSD but may also appear as external_sd.

I went through the logs again also my cm boot.img didnt flash either,

Once the mounts are right and boot is good ill compile and upload a boot patch with the correct mount point for raw_write of the boot.img
[Miscellaneous Android Development] DJ Robby:
TWRP seems fine now but it looks like I still get the same error when flashing the ROM as I did with CWM: https://pastebin.com/tGigSRkd
[Miscellaneous Android Development] Matty1993:
Hey mate

Great stuff are all partitions mounting in the mount menu and is the mount -o bind error still there also or gone now ?

I took a look at the logs this time your /data partitiion didnt mount log says device or resource busy and all the symlink tried to set but were denied permission for some odd reason,

If all partitions are mounting in the mount menu what ill do is rebuild the META-INF folder using meta-data which is what twrp uses and upload it so you can just unzip the rom with 7zip or winrar & delete the old META-INF folder replace with new then zip back up and flash,

Im also wondering if possibly your bootloader has a lock on it of some sort but very doubtful i think or TWRP wouldnt be booting up,

Anway so ill do that today sometime and upload it here
[Miscellaneous Android Development] DJ Robby:
1 o-bind error is still there but you said it doesn't matter so no point in trying to remove it.

Edit: Also what timezone are you in? I'm kinda curious because I am in EST and you always come on either really early or really late.

Edit 2: Also, Lately I've been wondering how I could build my own LineageOS or CyanogenMod ROMS, Could you make a guide for noobs if you get the chance?
[Miscellaneous Android Development] Matty1993:
Yeah mount -o wont matter about rom flash,

Im on AWST probably why its 11am here now lol,

New script is done and written up for meta-data with twrp im just generating a new update binary for it and will upload,

You need to learn a good few years worth of android also to build aswell as having a decent linux machine for compiling the rom i use BBQ linux for compiling etc, ive been working on androids for 10 years now though and have my own repair shop so ive got probably to much experience haha,

If you look on github youll see there device trees for all different devices, for the R11 max i found that micromax A102 and some alactel devices had very similair config in the .mk files etc pretty advanced stuff but if your keen to learn you can acheive anything :)

Anyhow ill post link soon as the new META-INF folder is uploaded for you to switch out
[Miscellaneous Android Development] Matty1993:
New META-INF and binary is done wont have the Aroma installer this time will just be on screen install in the TWRP GUI,

Zip also has a new boot.img which ive patched some more and busyboxed to make the kernel permissive,

& the new Cyanogen logo.bin as i think the one i added to the rom zio was an old one plus a new patched SU root by me also

What you need to do is extract the rom to an empty folder using 7zip or winrar,

Once extracted open folder,

You will see META-INF, logo.bin, boot.img & supersu or possibly magicroot i forget which i added but delete all of these from the extracted rom zip anyway

Now unzip my new meta-inf and what not from here

https://drive.google.com/file/d/118CXCmOZMQY46pdZ4XbFCNXheVkgFoRu/view?usp=drivesdk

Copy or move the files over to the rom zip,

Once done

Hold the ctrl button on your pc keyboard and then press A at the same time all files will now be highlighted,

Right click on the highlighted files now select add to archive on either 7zip or winrar,

Now MAKE SURE you select .zip format and not .rar or anything else,

Also make sure that the compression is set to normal.

Now click start wait for it to be zipped,

Copy to SD and flash,

If you get error 6 when trying to flash let me know as it will be the EOL to spacing within the script as ive added the boot.img, logo, and supersu root to it but i did make sure there were no unnecessary spaces so it should be fine.

If it fails on symlinks or permissions this time flash the boot.img only from the new zip i added using SP flash tool then try install rom again as i mentioned i busyboxed it so it could help with symlinking even though generally symlinking is run through toolbox or toybox
[Miscellaneous Android Development] DJ Robby:
Error 6.
[Miscellaneous Android Development] Matty1993:
Stupid error 6 is i really do hate it so badly Haha,

Try this one

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

Ive made sure it was set to unix language in notepad + and ive also additionly used the remove EOL and uneccessary spacing so should be good this time if not ill change the updater binary back to the old one but with the new script.

Let me know how you go anyhow
[Miscellaneous Android Development] DJ Robby:
I still get error 6.
[Miscellaneous Android Development] DJ Robby:
Are you working on it? You haven't replied in a while.
[Miscellaneous Android Development] Matty1993:
Yep still working on it,

Im manually writing the script out this time instead of generating it,

Theres alot of lines of writing involved especially with setting meta data out has to to be perfect or the binary will generate error 6 when flashing,

Speaking of which im also going to change that out also as it was generated using -t mount on system and data but as i had to remove busy box from recovery it may also be why its generating the error so will ad a block mounted binary once im done with script and will upload again
[Miscellaneous Android Development] Matty1993:
Ok try this one,

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

The updater script is perfect i know that 100% as i triple checked it after writing it out and is all spaced accordingly

Ive also switched the updater binary out to one that was already using emmc block mounts and meta-data so it should run my script no problem,

Additionally ive also switched out the manifests etc etc from the meta-inf i used to swap the updater binary out

Let me know how this one goes anyhow

A side Note for the R11 Max UBIFS HS_Q6_MB_V1.0 users update build #003 will be up sometime in the next week with major improvements yet again including GUI performance boot.img selinux for some which will be listed in the changelog when update is posted
[Miscellaneous Android Development] DJ Robby:
I'll try when I get home, Also will this get OTA updates?

Edit: Now I get Error 7.
[Miscellaneous Android Development] Matty1993:
:eek: for real ok ill try again thats more than likely the binary or manifests i added ill see what i can do today sometime and try again,

With OTAs i wasnt sure if i was going to do OTAs or just release the new updates here still havent decided but ive added the OTA props to the build.prop anyhow but left the manifest for OTA download blank has also been marked as

# this may be depracted before it is used.

# OTA feature.

ro.

ro.

ro.
[Miscellaneous Android Development] DJ Robby:
I really want to use the phone tomorrow so if you can please try to finish in the next 30 mins as I need to go to sleep I would appreciate that.
[Miscellaneous Android Development] Matty1993:
Yeah wont be in the next 30 mins ive got stuff to do today first and its gonna take longer than 30 minutes to re do please have some patience as i mentioned i have 8 other projects also
[Miscellaneous Android Development] Matty1993:
Ok replace the META-INF with this one zip back up and flash

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

Ive rebuilt another aroma installer binary & script based on the original from 2012 so there will 100% be no binary errors this time its using perms and not meta data as twrp can use both so if there are any issues again take a log at the end

if it fails to boot rom still reboot the recovery this time go to wipe then advanced wipe select every partition exept android secure and external sd card and wipe them manually,

Then run the installer again also take a log at the end again incase it still dosent work in which i dont know what would be the problem then as the TWRP works perfectly fine on my pixi 3 with the mount -o android secure error and the aroma binary has no problem installing to both my pixi 3 and r11 max ubifs so im starting to run out of ideas tbh
[Miscellaneous Android Development] DJ Robby:
This one is really short so I will just post it here...

AROMA INSTALLER version 2.00
(c) 2012 by amarullz xda-developers

ROM Name : AROMA INSTALLER
ROM Version : 2.00
ROM Author : <support@amarullz.com>
Device : Not Defined
Start at : Mon Dec 31 18:07:44 2012

line 161 col 15: syntax error, unexpected EQ, expecting IF or STRING or '!' or '('
1 parse errors

Installer Error (Status 6)

End at : Mon Dec 31 18:07:44 2012
[Miscellaneous Android Development] Matty1993:
Hmm thats really weird the log is complaining about an if config or invalid character on a ui_print line however looking at it now it is correctly laid out and has no errors that the log mentions, so what ill do is remove it upload a new one
[Miscellaneous Android Development] Matty1993:
Ok try this one.

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

Fourth times gotta be a charm surely lol
[Miscellaneous Android Development] DJ Robby:
Failed again, Here is the log: https://pastebin.com/VwCPaMEi
[Miscellaneous Android Development] Matty1993:
formatted ok

Mounted system ok

But data still says device or resource busy,

All system files are extracting ok

permission from bin to chmod files however are recieving permission denied still,

Bootimg still didnt flash,

But you can just flash that with sp flash tool,

Ive got no idea why its giving permission denied on symlinking did you try manually formatting all partitions in the wipe menu under advanced menu except external sdcard and android secure ?

Also did you try running the installer multiple times as there is nothing wrong with the installer now apart from the boot.img flash asserts permissions have nothing to do with the binary id say its something with your device possibly as my twrp and installer both work fine on other devices other than that im not sure what more i can do unfortunately
[Miscellaneous Android Development] DJ Robby:
I tried to wipe everything and run the installer multiple times and it still doesn't work, It says

assert failed: write_raw_image("/tmp/boot.img","/dev/bootimg)

Edit: I also tried flashing the boot.img with SP Flash Tool and it is stuck on the "Welcome" screen.
[Miscellaneous Android Development] Matty1993:
Yeah i did mention the boot asserts were not correct this is where it is causing error 7 but the bootimg is flashed lastly so even if it does fail everything else in theory works fine as mtk bootimgs can be flashed with sp flash tool.

Now so the rom boots to the setupwiz then ?

if thats the welcome screen your talking about Blue with a yellow arrow button in the centre with white writing at the top saying welcome ? This means that the rom is flashing and compatible with the hanset BUT the xbin applets havent been symlinked this is why you cannot continue past welcome screen

flashing bootimg wont make anything better if the /xbin hasnt been symlinked ill check the /xbin on my end but theres deffo chmod in mine maybe check your /xbin in the zip file for a file called chmod and or toolbox if toolbox is not there it will be in /bin so dont worry about that,
[Miscellaneous Android Development] DJ Robby:
No I mean the welcome boot animation
[Miscellaneous Android Development] Matty1993:
Ah you need to be more specific in that case then as there is the bootlogo which is logo.bin which is the first picture that appears, then there is the bootanimation not welcome animation this should be the CyanogenMod face with white writing at the bottom then there is the welcome screen which is the start of the setupwizard.

Ill look into the xbin problem anyway as the binary and installer are fine now apart from the bootimg write which ill fix check your /bin & /xbin for the chmod and toolbox files tell me where there located and ill see what i can do about getting it to boot, if its playing the bootanimation it will boot on your r10 no problem once the xbin symlinks properly if it wasnt compatible it wouldn't go past the first logo.bin screen so it will work just need to figure out where the problem is
[Miscellaneous Android Development] DJ Robby:
It doesn't play the boot animation, It just shows the welcome image but it doesn't get to the animated part.
[Miscellaneous Android Development] Matty1993:
Hmm okay no worries so xbin is not linking absolutely anything at all in that case give me a bit ill go through the rom see if i can spot anything missing or out of place
[Miscellaneous Android Development] Matty1993:
Try this TWRP

Ive removed the sdcard mount from fstab for mmcblk0p4 as it ls not needed for a rom install.

Ive also adjusted the fstabs to use your device mount path being dev/block/mmcblk instead of /emmc@android as such and have also added all emmc partitions to fstabs also,

TWRP 3.1.0 mk.3 ZM19E R10 eMMC

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

Now try this rom also

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

this is the same rom but it has been suverly slimmed down to be basically a test shell once it boots and works ill add all apps back etc ive added busybox to /bin and linked it in script aswell as changing the flash layout for boot in script so the boot.img should flash no problem,

your xbin already contains chown,busybox & toolbox, aswell as /bin already has toolbox so im not sure but symlinking in this case is controlled by busybox this is why i have added a second to /bin

Remember to get the logs for me after flash also
[Miscellaneous Android Development] Matty1993:
## edit

building you my Cyanogen recovery from my ubifs one in top OP managed to get it to behave nicely with ext4 & emmc as i somewhat think possibly it could also be recovery though it may work for me maybe not for other phones this is why im building it for you additionally though do try it first link will be attached to this post when uploaded.

CyanogenCTR eMMC ZM19E R10

https://drive.google.com/file/d/1UfYtCmdlRS07aO0lyDi_EO1ngAAO-i1M/view?usp=drivesdk
[Miscellaneous Android Development] DJ Robby:
No errors with the installer but when I go to reboot twrp says no OS installed and it is still stuck on that first welcome image.

Edit: I don't think CyanogenCTR would help but you didn't make it public so I can't access the file.
[Miscellaneous Android Development] Matty1993:
Did you get the log from the installer?

CyanogenCTR is the recovery i originally made to flash the rom, try download link again forgot to turn link sharing on

Also did you make sure that system,data,cache were all checked in the mount menu of TWRP before running the installer ?

Try with my modifed CTR anyway i tested it on pixi 3 before posting mounts all partitions and wipes everything ok,
[Miscellaneous Android Development] DJ Robby:
Still stuck on welcome and I did mount system, data, cache in CyanogenCTR but I didn't in TWRP.

Edit: Also I don't think the log would say anything because there were no errors.