Database Info

getting stock rooted Calkulin rom converted to data/cache f2fs

@Calkulin (because you uploaded the rom)
@katinatez (because you are good folk)
@zaphodbeeb (becasue you are the one that taught me to convert to mixed partitions)
hoping to get some help on this for me and others wanting to try out the update.
i am trying to get the rooted 05q to work on my mixed f2fs/etx4 partitions. data/cache f2fs - system etx4 so i don't have to wipe my /data partition.
i have gone through several routes so far to no avail. sideloading/flashing. flashing the ak 113 kernel with instructions for the new update. updated to the new katinatez philz with the new f2fs comits.
1. updater script - i did not see a need in changing the /data to use busybox for f2fs as the line of code is already there.
2. fstab.bacon - i used zaphods new f2fs all or f2fs mixed
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,barrier=1 wait
/dev/block/platform/msm_sdcc.1/by-name/system /system f2fs ro,noatime,nosuid,nodev,discard,nodiratime,inline_xattr,errors=recover wait
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 noatime,nosuid,nodev,barrier=1,data=ordered,noauto_da_alloc,errors=panic wait,check,encryptable=/dev/block/platform/msm_sdcc.1/by-name/reserve4
/dev/block/platform/msm_sdcc.1/by-name/userdata /data f2fs noatime,nosuid,nodev,discard,nodiratime,inline_xattr,errors=recover wait,nonremovable,encryptable=/dev/block/platform/msm_sdcc.1/by-name/reserve4
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 noatime,nosuid,nodev,barrier=1,data=ordered,noauto_da_alloc,errors=panic wait,check
/dev/block/platform/msm_sdcc.1/by-name/cache /cache f2fs noatime,nosuid,nodev,discard,nodiratime,inline_xattr,errors=recover wait
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 nosuid,nodev,barrier=1,data=ordered,nodelalloc,nomblk_io_submit,errors=panic wait,check
/dev/block/platform/msm_sdcc.1/by-name/boot /boot emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/recovery /recovery emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/misc /misc emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,shortname=lower,uid=1000,gid=1000,dmask=227,fmask=337,context=u:object_r:firmware_file:s0 wait
/devices/platform/xhci-hcd auto vfat defaults voldmanaged=usbdisk:auto
at first i just flashed the the new extras file (firmware modem linked with Calkulin's rom. then flashed the rom. i got stuck on the bootanimation for ten minutes.
then i thought it might be the kernel not 'jiving' with f2fs. so i sideloaded the ak_113 (on top of what i had already done) with the instructionsfrom @xlollomanx (thanks) linked from the ak kernel thread.
still.... stuck on cyanogen boot for ten minutes
then i restored my backup and sideloaded everything, ak kernel and all, from scratch.
once again... grrr. still stuck on boot animation for ten minutes.
any ideas on what i can do?

Encryption failure

Dears,
I installed TWRP on SM-A530F/DS and flashed no-verity-opt-encrypt-6.0 and formatted data to let the phone boot.
Well, I'd like to re-encrypt the phone like I've always been doing on sammys after TWRP or Magisk installation, but it doesn't work on this phone.
No matter if it's Nougat or Oreo, applying encryption nothing happens and phone crashes backing to lock screen in a minute.
Any suggestions?
Thanks everybody.

Id like to encrpt mine too. Twrp and rooted with magisk. when i try and encrpt it just reboots after a minute. SMA530W

Dear @jcadduono,
sorry to bother, I think this issue is caused by Samsung's firmwares but, in your opinion, could it be related to no-dm-verity patch?
Or, is it possible to edit the patch in order to not to disable encryption?
There's a modification (red color in code), I think operated by the patch, to ramdisk's fstab.
Stock fstab:
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
# system and vendor partition will be early-mounted by kernel
/dev/block/platform/13500000.dwmmc0/by-name/SYSTEM /system ext4 ro,errors=panic wait,verify
/dev/block/platform/13500000.dwmmc0/by-name/CACHE /cache ext4 noatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic wait,check
/dev/block/platform/13500000.dwmmc0/by-name/USERDATA /data ext4 noatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic wait,check,[COLOR="Red"]forceencrypt=footer[/COLOR],quota
/dev/block/platform/13500000.dwmmc0/by-name/EFS /efs ext4 noatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic wait,check
/dev/block/platform/13500000.dwmmc0/by-name/CPEFS /cpefs ext4 noatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic wait,check,nofail
# VOLD
/dev/block/platform/13500000.dwmmc0/by-name/HIDDEN /preload ext4 defaults voldmanaged=preload:auto
/devices/platform/13550000.dwmmc2/mmc_host/mmc1* auto vfat defaults voldmanaged=sdcard:auto
/devices/platform/13600000.usb/13600000.dwc3* auto auto defaults voldmanaged=usb:auto
Patched fstab:
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
# system and vendor partition will be early-mounted by kernel
/dev/block/platform/13500000.dwmmc0/by-name/SYSTEM /system ext4 ro,errors=panic wait
/dev/block/platform/13500000.dwmmc0/by-name/CACHE /cache ext4 noatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic wait,check
/dev/block/platform/13500000.dwmmc0/by-name/USERDATA /data ext4 noatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic wait,check,[COLOR="red"]encryptable=footer[/COLOR],quota
/dev/block/platform/13500000.dwmmc0/by-name/EFS /efs ext4 noatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic wait,check
/dev/block/platform/13500000.dwmmc0/by-name/CPEFS /cpefs ext4 noatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic wait,check,nofail
# VOLD
/dev/block/platform/13500000.dwmmc0/by-name/HIDDEN /preload ext4 defaults voldmanaged=preload:auto
/devices/platform/13550000.dwmmc2/mmc_host/mmc1* auto vfat defaults voldmanaged=sdcard:auto
/devices/platform/13600000.usb/13600000.dwc3* auto auto defaults voldmanaged=usb:auto
Patch operation sounds correct, but this is the only device that fails in encryption them.
Thank you so much.

It's actually not uncommon for a ROM to not be able to re-enable /data encryption from the regular settings, once disabled manually.
As far as I can tell, no-verity-opt-encrypt-6.0.zip replaces the "must encrypt" flag on /data with a "can encrypt if you want" flag. When you format /data from TWRP after flashing that zip, you obtain a non-encrypted partition, but it should be possible to re-encrypt it.
Have you guys tried encrypting data from the adb shell? Details here: http://niki.hammler.net/wiki/Android_Device_Encryption#Setting_up_encryption
This is also recommended reading: https://source.android.com/security/encryption/full-disk
You should also check the system log to see what goes wrong when you try to activate encryption. This is how: https://android.stackexchange.com/questions/26123/android-boot-up-messages-for-debugging

Genius wanted: TWRP for LENOVO TB-X104F

Could a genius with some time on there hands make TWRP for this device, its driving me insane, everything provided below.
Android 8.1
2GB RAM
Snapdragon 210
MSM8909
GPU Adreno 304
Times like these i wish i could follow a tutorial correctly.
Thanks in advance!
I had to archive the recovery as the IMG was over 8MB.

frankieuk said:
Could a genius with some time on there hands make TWRP for this device, its driving me insane, everything provided below.
Android 8.1
2GB RAM
Snapdragon 210
MSM8909
GPU Adreno 304
Times like these i wish i could follow a tutorial correctly.
Thanks in advance!
I had to archive the recovery as the IMG was over 8MB.
Click to expand...
Click to collapse
I know this reply is a little late... but have you tried twrp builder app? Search xda... got a working recovery for an obscure UMX budget phone... I have this tablet but I haven't bothered trying to do anything with it.

i have ported the Lenovo Tab 10 TB-X103F twrp to {TB-X104F}
tdawgg777 said:
I know this reply is a little late... but have you tried twrp builder app? Search xda... got a working recovery for an obscure UMX budget phone... I have this tablet but I haven't bothered trying to do anything with it.
Click to expand...
Click to collapse
i have ported the Lenovo Tab 10 TB-X103F twrp to {TB-X104F}but.... i having problems with partitions when i boot into it
i think my problems has to do with recovery.FSTAB file
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
heres my current recovery.fstab for twrp
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
#device mount point fstype [device2] [length=]
/boot emmc /dev/block/bootdevice/by-name/boot flags=display="Boot";backup=1
/recovery emmc /dev/block/bootdevice/by-name/recovery flags=display="Recovery";backup=1
/system ext4 /dev/block/bootdevice/by-name/system flags=display="System";backup=1;wipeingui
/misc emmc /dev/block/bootdevice/by-name/misc flags=display="Misc";backup=0
/cache ext4 /dev/block/bootdevice/by-name/cache flags=display="Cache";backup=1;wipeingui;wipeduringfactoryreset
/data ext4 /dev/block/bootdevice/by-name/userdata flags=display="Data";backup=1;wipeingui;wipeduringfactoryreset;length=-16384
/sdcard0 vfat /dev/block/mmcblk1p1 flags=display="Micro SDCard";storage;wipeingui;removable;backup=0
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
______________________________________________________________________________________________________________________
heres he stock recovery.fstab
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
#device mount point fstype [device2] [length=]
/dev/block/bootdevice/by-name/system /system ext4 ro,barrier=1 wait
/dev/block/bootdevice/by-name/vendor /vendor ext4 ro,barrier=1 wait
/dev/block/bootdevice/by-name/cache /cache ext4 noatime,nosuid,nodev,barrier=1,data=ordered wait,check
/dev/block/bootdevice/by-name/userdata /data ext4 noatime,nosuid,nodev,barrier=1,data=ordered,noauto_da_alloc wait,check,encryptable=footer
/dev/block/mmcblk1p1 /sdcard vfat nosuid,nodev wait
/dev/block/bootdevice/by-name/boot /boot emmc defaults defaults
/dev/block/bootdevice/by-name/recovery /recovery emmc defaults defaults
/dev/block/bootdevice/by-name/misc /misc emmc defaults defaults
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
none of the partitions show up except (microsd card)
what am i doing wrong

Interested in recovery for this tablet also. Any luck?
Sent from my SM-N960U using Tapatalk

Hello Good People,
Is there a working TWRP for this tablet?
T.I.A.

Hello again,
Is there any working recovery for this tablet.
Its very very difficult to find a custom ROM.
Are people using LineageOS ?
T.I.A.

recover FDE encrypted data xiaomi 5a

Hello:
I have a Xiaomi Redmi 5A stuck at boot logo. I was able to dump all partitions, including userdata, with miracle box software and test point, but it seems that userdata partition is encrypted.
Bootloader is locked, so I think I can't mount encrypted partition with TWRP whitout wiping data.
I can mount system partition. fstab.qcom content is like this:
/dev/block/bootdevice/by-name/system /system ext4 ro,barrier=1,discard wait,verify
/dev/block/bootdevice/by-name/userdata /data ext4 nosuid,nodev,barrier=1,noauto_da_alloc wait,resize,reservedsize=128M,forceencrypt=footer <-----
/dev/block/bootdevice/by-name/cust /cust ext4 ro,nosuid,nodev,barrier=1 wait,check
/devices/soc/7864900.sdhci/mmc_host* /storage/sdcard1 vfat nosuid,nodev wait,voldmanaged=sdcard1:auto,noemulatedsd,encryptable=footer
/dev/block/bootdevice/by-name/config /frp emmc defaults defaults
/devices/soc/78db000.usb/msm_hsusb_host* auto auto defaults wait,voldmanaged=usbotg:auto,encryptable=footer
/dev/block/bootdevice/by-name/misc /misc emmc defaults defaults
Androrid version is 7.1.2 and MIUI V10.2.1.0.NDFMIXM
I know the pattern.
I have read about some expoits to get MasterKey. Here are some links
- *******forensicswiki.org/wiki/How_To_Decrypt_Android_Full_Disk_Encryption
- ********nelenkov.blogspot.com/2014/10/revisiting-android-disk-encryption.html
- ********area41.io/downloads/slides/area41_16_kunz_semioffline_attack.pdf
- ********github.com/laginimaineb/android_fde_bruteforce
I tried bruteforce script included in Santoku Linux and it gives me an error. I passed as header parameter first 2048 bytes of userdata partiton and last 16K as footer parameter.
At footer region, "aes-xts" string can be read.
I am afraid about doing a hard reset, if it will reset / change some kind of random key....

Advice needed porting TWRP to AllWinner a50

Heya guys!
So I've been busy making a TWRP recovery image for my unlocked chinese tablet (a Deejoy q728) that I bought from Amazon. It's a reaaaaally generic one with literally no firmware available over the entirety of the webs(yes I followed every tutorial you could think of that explains how to find firmware, believe me *sigh*).
Now I've gotten TWRP 2.3.6 to actually boot. I used the recovery img from another tablet with almost the same hardware(Concord HS or something) as a base and brought the necessary files into a TWRP 2.6.3 for the AllWinner A23 SoC. with Android Image Kitchen. The steps I took are from this post on DroidWin. It boots but I am encountering the following(major) problems.
1. Even though it displays in landscape, the touch screen seems to think it's in portrait.
2. Partitions just can't be found whatsoever. I think this might have to do with the fact that I don't know too much about fstab.
3. Adbd doesn't work.
By the by, I also edited the fstab files so that they contain the specific partition info of my tablet, not the Concord, as the Concord has several partitions that simply don't exist on mine. Code for twrp.fstab and recovery.fstab down below:
Code:
twrp.fstab:
/boot emmc /dev/block/by-name/boot
/recovery emmc /dev/block/by-name/recovery
/system ext4 /dev/block/by-name/system
/data ext4 /dev/block/by-name/UDISK flags=encryptable=/dev/block/by-name/metadata
/cache ext4 /dev/block/by-name/cache
/misc emmc /dev/block/by-name/misc
/external_sd vfat /dev/block/mmcblk1p1 flags=removable;storage;display="SDCARD"
/usb-otg auto /dev/block/sda1 flags=removable;storage;display="USB-OTG"
recovery.fstab:
# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
/dev/block/by-name/system /system ext4 ro,barrier=1 wait,first_stage_mount,logical,avb=vbmeta,avb_keys=/avb/q-gsi.avbpubkey:/avb/r-gsi.avbpubkey:/avb/s-gsi.avbpubkey
/dev/block/by-name/vendor /vendor ext4 ro,barrier=1 wait,first_stage_mount,logical
#product /product ext4 ro,barrier=1 wait,first_stage_mount,logical
/dev/block/by-name/UDISK /data ext4 noatime,nosuid,nodev,discard wait,check,formattable,fileencryption=adiantum,quota,reservedsize=33554432
/dev/block/by-name/cache /cache ext4 noatime,nosuid,nodev,barrier=1,data=ordered,nomblk_io_submit,noauto_da_alloc,errors=panic wait,check,formattable
/dev/block/by-name/metadata /metadata ext4 nodev,noatime,nosuid,errors=panic wait,first_stage_mount,formattable
/dev/block/by-name/boot /boot emmc defaults defaults
/dev/block/by-name/recovery /recovery emmc defaults defaults
/dev/block/by-name/misc /misc emmc defaults defaults
#/dev/block/by-name/super /super emmc defaults defaults
/dev/block/by-name/frp /persistent emmc defaults defaults
/dev/block/zram0 none swap defaults zramsize=75%
/devices/platform/soc/sdc0/mmc_host/mmc* auto auto defaults voldmanaged=extsd:auto,encryptable=footer
/devices/platform/soc/usbc0/usb* auto auto defaults voldmanaged=usb:auto,encryptable=footer
/devices/platform/soc/5101000.ehci0-controller/usb* auto auto defaults voldmanaged=usb:auto,encryptable=footer
/devices/platform/soc/5200000.ehci1-controller/usb* auto auto defaults voldmanaged=usb:auto,encryptable=footer
/devices/platform/soc/5101000.ohci0-controller/usb* auto auto defaults voldmanaged=usb:auto,encryptable=footer
/devices/platform/soc/5200000.ohci1-controller/usb* auto auto defaults voldmanaged=usb:auto,encryptable=footer
/external_sd vfat /dev/block/mmcblk1p1 flags=removable;storage;display="SDCARD"
/usb-otg auto /dev/block/sda1 flags=removable;storage;display="USB-OTG"
# add for recovery
none /sdcard emmc defaults defaults
Edit: The main reason I really want this to end up working is because there are a ton of cheap allwinner a50 tablets and most of them(at least mine) are bootloader unlockable. Add Magisk to these babies and voila! Ya got a cheap device that you can theme to your hearts content. Toying around with tech has always been my thing haha.
So if anyone has any tips for me to get a sorta head start on this, I would really appreciate it!
Sincerely,
Snow

snowlily said:
Heya guys!
So I've been busy making a TWRP recovery image for my unlocked chinese tablet (a Deejoy q728) that I bought from Amazon. It's a reaaaaally generic one with literally no firmware available over the entirety of the webs(yes I followed every tutorial you could think of that explains how to find firmware, believe me *sigh*).
Now I've gotten TWRP 2.3.6 to actually boot. I used the recovery img from another tablet with almost the same hardware(Concord HS or something) as a base and brought the necessary files into a TWRP 2.6.3 for the AllWinner A23 SoC. with Android Image Kitchen. The steps I took are from this post on DroidWin. It boots but I am encountering the following(major) problems.
1. Even though it displays in landscape, the touch screen seems to think it's in portrait.
2. Partitions just can't be found whatsoever. I think this might have to do with the fact that I don't know too much about fstab.
3. Adbd doesn't work.
By the by, I also edited the fstab files so that they contain the specific partition info of my tablet, not the Concord, as the Concord has several partitions that simply don't exist on mine. Code for twrp.fstab and recovery.fstab down below:
Code:
twrp.fstab:
/boot emmc /dev/block/by-name/boot
/recovery emmc /dev/block/by-name/recovery
/system ext4 /dev/block/by-name/system
/data ext4 /dev/block/by-name/UDISK flags=encryptable=/dev/block/by-name/metadata
/cache ext4 /dev/block/by-name/cache
/misc emmc /dev/block/by-name/misc
/external_sd vfat /dev/block/mmcblk1p1 flags=removable;storage;display="SDCARD"
/usb-otg auto /dev/block/sda1 flags=removable;storage;display="USB-OTG"
recovery.fstab:
# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
/dev/block/by-name/system /system ext4 ro,barrier=1 wait,first_stage_mount,logical,avb=vbmeta,avb_keys=/avb/q-gsi.avbpubkey:/avb/r-gsi.avbpubkey:/avb/s-gsi.avbpubkey
/dev/block/by-name/vendor /vendor ext4 ro,barrier=1 wait,first_stage_mount,logical
#product /product ext4 ro,barrier=1 wait,first_stage_mount,logical
/dev/block/by-name/UDISK /data ext4 noatime,nosuid,nodev,discard wait,check,formattable,fileencryption=adiantum,quota,reservedsize=33554432
/dev/block/by-name/cache /cache ext4 noatime,nosuid,nodev,barrier=1,data=ordered,nomblk_io_submit,noauto_da_alloc,errors=panic wait,check,formattable
/dev/block/by-name/metadata /metadata ext4 nodev,noatime,nosuid,errors=panic wait,first_stage_mount,formattable
/dev/block/by-name/boot /boot emmc defaults defaults
/dev/block/by-name/recovery /recovery emmc defaults defaults
/dev/block/by-name/misc /misc emmc defaults defaults
#/dev/block/by-name/super /super emmc defaults defaults
/dev/block/by-name/frp /persistent emmc defaults defaults
/dev/block/zram0 none swap defaults zramsize=75%
/devices/platform/soc/sdc0/mmc_host/mmc* auto auto defaults voldmanaged=extsd:auto,encryptable=footer
/devices/platform/soc/usbc0/usb* auto auto defaults voldmanaged=usb:auto,encryptable=footer
/devices/platform/soc/5101000.ehci0-controller/usb* auto auto defaults voldmanaged=usb:auto,encryptable=footer
/devices/platform/soc/5200000.ehci1-controller/usb* auto auto defaults voldmanaged=usb:auto,encryptable=footer
/devices/platform/soc/5101000.ohci0-controller/usb* auto auto defaults voldmanaged=usb:auto,encryptable=footer
/devices/platform/soc/5200000.ohci1-controller/usb* auto auto defaults voldmanaged=usb:auto,encryptable=footer
/external_sd vfat /dev/block/mmcblk1p1 flags=removable;storage;display="SDCARD"
/usb-otg auto /dev/block/sda1 flags=removable;storage;display="USB-OTG"
# add for recovery
none /sdcard emmc defaults defaults
Edit: The main reason I really want this to end up working is because there are a ton of cheap allwinner a50 tablets and most of them(at least mine) are bootloader unlockable. Add Magisk to these babies and voila! Ya got a cheap device that you can theme to your hearts content. Toying around with tech has always been my thing haha.
So if anyone has any tips for me to get a sorta head start on this, I would really appreciate it!
Sincerely,
Snow
Click to expand...
Click to collapse
I realize this port is now months old, but I did want to ask how your TWRP port worked out? I'm presently working on Allwinner-a50 and Allwinner-100 tablet projects.

Viva La Android said:
I realize this port is now months old, but I did want to ask how your TWRP port worked out? I'm presently working on Allwinner-a50 and Allwinner-100 tablet projects.
Click to expand...
Click to collapse
Welllll I have no idea how I did it, but I got it to boot. Touch screen drivers functioned overall but while being horizontal, the touch screen responded as if in portrait, so I literally ended up measuring where what button would be on the touch screen compared what was actually displayed. I eventually gave up as something tells me that the A50 might have very proprietary storage drivers, because no matter what I do, twrp refuses to see any device attached. Also, though most allwinner socs are well docd, the a50 isn't as much and afaik the allwinner barely acknowledges the a50. Though I am really happy I got to develop some more experience with things like fstab and it was a lot of fun

snowlily said:
Welllll I have no idea how I did it, but I got it to boot. Touch screen drivers functioned overall but while being horizontal, the touch screen responded as if in portrait, so I literally ended up measuring where what button would be on the touch screen compared what was actually displayed. I eventually gave up as something tells me that the A50 might have very proprietary storage drivers, because no matter what I do, twrp refuses to see any device attached. Also, though most allwinner socs are well docd, the a50 isn't as much and afaik the allwinner barely acknowledges the a50. Though I am really happy I got to develop some more experience with things like fstab and it was a lot of fun
Click to expand...
Click to collapse
Outstanding job. That's no small feat when dealing with Allwinner, and especially their more obscure A-series chipset like the a50. So, TWRP will not recognize USB OTG device or other attached devices?

Viva La Android said:
Outstanding job. That's no small feat when dealing with Allwinner, and especially their more obscure A-series chipset like the a50. So, TWRP will not recognize USB OTG device or other attached devices?
Click to expand...
Click to collapse
It won't even recognize the internal storage. When maneuver my why with the barely functional touchscreen to the log option, it just shows a long list of "couldn't mount"s. And no matter what I do TWRP has zero access to internal or external storage. Be it otg or microsd. I've tried several way of formatting the fstabs layout. Be it the average template I would find within twrp, or base my fstabs on those in stock recovery. Anyhow, it was taking alot of time in my life and started to get annoying /hj. Though I am glad I developed some experience. But I wanted to make something that would require alot more time, but would be alot more fun to make. It's a series called "Bull[censored] simulator." Though it's not really a simulator. And the real game lies within. Well... The game itself. As in the hexadecimal, the itchio page's assets and so on. Atm I am busy with a part that inserts it's lore into a Pokémon rom hack I will probably call Bull**** Sim: Pokémon Edition(Working title of course lol) so sorry for abandoning this job. Though I AM glad that people still take interest. Maybe I'll get back to it someday if I ain't beaten to the chase