Related
Hey everyone..
..since the first update of the M Developer Preview I experience that the WiFi-MAC address of my nexus 5 changes on every reboot. I've read in other threads that this has something to do with the kernel, but I've no idea what should be wrong there. Can anyone help me?
Thanks!
PS: I'm new here, so don't judge me for any mistakes I will surly will make!
Xelfmade said:
Hey everyone..
..since the first update of the M Developer Preview I experience that the WiFi-MAC address of my nexus 5 changes on every reboot. I've read in other threads that this has something to do with the kernel, but I've no idea what should be wrong there. Can anyone help me?
Thanks!
PS: I'm new here, so don't judge me for any mistakes I will surly will make!
Click to expand...
Click to collapse
Can you run a mount command in adb shell or in a terminal emulator on the phone? If I can guess the persist partition is not mounted.
Tapatalk-kal küldve az én Nexus 5-el
Which commands for example?
But yeah I think the command working as asprected..
How could that happen? And how can I fix it, if it doesn't work, without needing to root my nexus?
I have noticed this also.. And the phone shows up a epigram instead of nexus 5.
Do you have an idea to get rid of that thing?! I've been flashing my nexus now again on preview 2, but I don't really know if this will change annything..
I really need help
Hello.
I have the same problem as Xelfmade, my WiFi MAC address changes on every reboot. This is very annoying because my router's dhcp server identifies the different devices by their MAC addresses and thus my Nexus 5 gets a new IP after every reboot.
1) What I tried so far to fix this: I followed a guide to give the file /persist/wifi/.macaddr the correct rights and set the correct owner:group for the folders and files. This didn't help.
2) I flashed the latest factory image and made a backup of the EFS partition. Then I restored a backup of my current ROM (Resurrection Remix but I didn't restore EFS and thought this might solve my issues. It didn't.
Now bitdomo wrote that probably the persist partition wasn't mounted. I know how I could check and maybe even solve this in Linux but I don't know how I could do this in Android .
This is the content of /fstab.hammerhead:
Code:
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,$
/dev/block/platform/msm_sdcc.1/by-name/userdata /data f2fs rw,$
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 noa$
/dev/block/platform/msm_sdcc.1/by-name/cache /cache f2fs rw,$
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 noa$
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 nos$
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,$
/dev/block/platform/msm_sdcc.1/by-name/boot /boot emmc def$
/dev/block/platform/msm_sdcc.1/by-name/recovery /recovery emmc def$
/dev/block/platform/msm_sdcc.1/by-name/misc /misc emmc def$
/dev/block/platform/msm_sdcc.1/by-name/modem /radio emmc def$
/dev/block/platform/msm_sdcc.1/by-name/sbl1 /sbl1 emmc def$
/dev/block/platform/msm_sdcc.1/by-name/tz /tz emmc def$
/dev/block/platform/msm_sdcc.1/by-name/rpm /rpm emmc def$
/dev/block/platform/msm_sdcc.1/by-name/sdi /sdi emmc def$
Any help would be really appreciated, thank you :good:.
Hi guys,
I've got a trouble. My phone has turned off and had a google screen loader . I can turn on TWRP and the phone is shown on the computer, but i can't push any file in "can not copy file" and the phone is empty. A few months ago i had the same trouble, on my phone all the files dissapeared and after 15 times of reloading it turned on and all the files appeared and it was working a week then it repeated when the phone turned on again i reinstalled SuperSu and the phone was working for 2 months correctly, but this trouble repeated tomorrow again.
When i turn it off i can see this
E: primary block device /dev/block/platform/msm_sdcc/1./b
y-name/userdata for mount point /data is not present!
E:unable to mount /data
E:unable to find partition size for /boot
E:unable to find partition size for /recovery
E:unable to find partition size for /misc
E:unable to find partition size for /radio
E:unable to find partition size for /sbl1
E:unable to find partition size for /tz
E:unable to find partition size for /rpm
E:unable to find partition size for /sdi
E:unable to find partition size for /aboot
E:unable to find partition size for /imgdata
E:unable to find partition size for /efs1
E:unable to find partition size for /efs2
I'm so sorry for my English, but people on my native forum couldn't help me.
I have solved this problem I have just installed recovery 3.0 from fastboot and it has worked, there are all the files on my phone.
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....
#########Concept########
When phone data is encrypted so twrp can't decrypt it and ask for password.
So We need to find a "fstab" named file in "etc" folder and change its "encrypt" word to "decrypt"
This Fstab file is located inside "System" OR "Vendor folder".
Click to expand...
Click to collapse
For TWRP Recovery Users ( who don't have root)
PHP:
Open recovery mode and tap on "Advance>file manager" and go to this path
For Root Users Use any "Root File Manager".
PHP:
Go to "System/etc" path
OR
PHP:
go to "system_root/system/etc
If Fstab isn't available inside "system" then search it in *vendors* folder
PHP:
go to "vendor/etc"
find ("fstab") named file in etc folder.
maybe more than 1 fstab file will be there.
In that condition.
You need to check which one fstab file has partition blocks names like ("system, vendor, userdata) etc.
so just copy this Fstab file to SD card Or anywhere you like, for editing.
###Editing####
Download"Quick Edit Apk" from store.
Open This fstab file using this Quick edit tool and find line which has word like "data" or "userdata".
Something like these two lines.
PHP:
"dev/block/bootdevice/by-name/userdata"
OR
PHP:
"dev/block/bootdevice/by-name/data"
Something like these above lines.
Click to expand...
Click to collapse
Now Find word similar to "Encrypt" in this line.
Change "encrypt" word to "decrypt" of this userdata line.
You will find one of these like words .
Hint
PHP:
"forceencrypt" >>>>>>>>>>>>>>change it to "forcedecrypt"
PHP:
"encryptable" >>>>>>>>>>>>>>>>>change it to "decryptable"
PHP:
"encrypt" >>>>>>>>>>>>>>>>>>>>change it to "decrypt"
PHP:
"encryption" >>>>>>>>>>>>>>>>>>change it to "decryption"
See I Just Change "en" to "de"
Mean ”En”crypt to ”de”crypt
For example on my phone fstab the line was this.
PHP:
/dev/block/platform/bootdevice/by-name/userdata /data f2fs noatime,nosuid,nodev,discard,noflush_merge wait,check,quota,reservedsize=128M,formattable,resize,forceencrypt=/dev/block/platform/bootdevice/by-name/metadata,
You can see, for me the word was "forcedecrypt".
Click to expand...
Click to collapse
After (by-name) the word was "Userdata" .
Click to expand...
Click to collapse
Now I founded both "userdata" and "forceencrypt" and i changed it according to my need.
("Root Users, You have done eding" Now reset you device and enjoy")
### TWRP Users you can continue ###
go back to recovery and copy this edited fstab to
"it's original location (where you found it).
(For me it was founded in vendor/etc path and i pasted this edited fstab there)
after pasting done, then again go to it's original location (Pasted location)(For me it was vendor/etc)
And tap on this edited "fstab" and select on "chmod" option And set permission to 0644 of this file.
wipe your data, internal storage and dalvik-cable.
Reboot
now error is completely gone
Watch this video of you're still confused.
I think this would cause error, if we ever want to re encrypt the device. Just change forceencrypt to encryptable and perform a factory reset. You will have a unencrypted device with encryption option available.
Please Correct me if I am wrong.
Yes, after your device is decrypted then you can again encrypt it by just changing the word from decrypt>>> to "encrypt" and do a factory reset.
The important part is to find the right "fstab" file from (etc) folder located inside system OR vendor directory's.
And change the encrypt word to decrypt and do a factory reset.
Wrong,
Force-encrypt to decrypt.
Riight
Force-encrypt to force-decrypt.
The number of words should be same after changed.
Like "forceencrypt" (12 words) and i changed it to "forcedecrypt" (12 words).
You just need to change en to de.
Understand.
That's a Common sense.
Abdulrehman130 said:
Yes, after your device is decrypted then you can again encrypt it by just changing the word from decrypt>>> to "encrypt" and do a factory reset.
The important part is to find the right "fstab" file from (etc) folder located inside system OR vendor directory's.
And change the encrypt word to decrypt and do a factory reset.
Wrong,
Force-encrypt to decrypt.
Riight
Force-encrypt to force-decrypt.
The number of words should be same age changed.
You just need to change en to de.
Understand.
That's a Common sense.
Click to expand...
Click to collapse
Wouldn't it be easy just to re-encrypt from setting menu instead of everyone we have to encrypt or decrypt, changing the fstab file. While your way is working, it would be best to make device encrypt-decrypt from setting. Also a plus side we don't need to perform factory reset after we encrypt and decrypt it again.
Cheers!
SHAH RUKH 45 said:
Wouldn't it be easy just to re-encrypt from setting menu instead of everyone we have to encrypt or decrypt, changing the fstab file. While your way is working, it would be best to make device encrypt-decrypt from setting. Also a plus side we don't need to perform factory reset after we encrypt and decrypt it again.
Cheers!
Click to expand...
Click to collapse
But Every device doesn't have encryption and decryption option available in settings.
Sometimes this process failed and phone OS said that we need a factor reset.
Abdulrehman130 said:
But Every device doesn't have encryption and decryption option available in settings.
Sometimes this process failed and phone OS said that we need a factor reset.
Click to expand...
Click to collapse
I have never seen a device without a encryption option.
SHAH RUKH 45 said:
I have never seen a device without a encryption option.
Click to expand...
Click to collapse
Yes, true.
But sometimes encryption needs to be disabled to fix 0mb/ unable to mount /data partition error.
My edition here, looking reasonable and feeling good? My device is Samsung A125F
Code:
# /system/etc/recovery.fstab
rootfs / ext4 rw,barrier=1 wait,logical,first_stage_mounst
system /system ext4 rw,barrier=1 wait,logical,first_stage_mount
system /system_root ext4 rw,barrier=1 wait,logical,first_stage_mount
vendor /vendor ext4 rw,barrier=1 wait,logical,first_stage_mount
product /product ext4 rw,barrier=1 wait,logical,first_stage_mount
odm /odm ext4 rw,barrier=1 wait,logical,first_stage_mount
/dev/block/platform/bootdevice/by-name/md_udc /metadata ext4 noatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic,sync wait,check,formattable,first_stage_mount
/dev/block/platform/bootdevice/by-name/userdata /data ext2 rw,noatime,nosuid,nodev,discard,usrquota,grpquota,fsync_mode=nobarrier,reserve_root=32768,resgid=5678,inlinecrypt latemount,wait,check,quota,reservedsize=128M,forcedecrypt=/dev/block/platform/bootdevice/by-name/metadata
/dev/block/platform/bootdevice/by-name/cache /cache ext4 noatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic wait,check,formattable
/dev/block/platform/bootdevice/by-name/protect1 /mnt/vendor/protect_f ext4 noatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic wait,check,formattable
/dev/block/platform/bootdevice/by-name/protect2 /mnt/vendor/protect_s ext4 noatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic wait,check,formattable
/dev/block/platform/bootdevice/by-name/nvdata /mnt/vendor/nvdata ext4 noatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic wait,check,formattable
/dev/block/platform/bootdevice/by-name/nvcfg /mnt/vendor/nvcfg ext4 noatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic wait,check,formattable
/dev/block/platform/bootdevice/by-name/prism /prism ext4 ro,barrier=1 nofail,avb,first_stage_mount
/dev/block/platform/bootdevice/by-name/optics /optics ext4 ro,barrier=1 nofail,avb,first_stage_mount
/dev/block/platform/bootdevice/by-name/efs /efs ext2 noatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic wait,check,formattable
/dev/block/platform/bootdevice/by-name/keydata /keydata ext4 noatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic,inlinecrypt wait,check,formattable,fileencryption=aes-256-xts,nofail
/dev/block/platform/bootdevice/by-name/keyrefuge /keyrefuge ext4 noatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic,inlinecrypt wait,check,formattable,fileencryption=aes-256-xts,nofail
/dev/block/platform/bootdevice/by-name/frp /persistent emmc defaults defaults
/dev/block/platform/bootdevice/by-name/nvram /nvram emmc defaults defaults
/dev/block/platform/bootdevice/by-name/proinfo /proinfo emmc defaults defaults
/dev/block/platform/bootdevice/by-name/lk /bootloader emmc defaults defaults
/dev/block/platform/bootdevice/by-name/lk2 /bootloader2 emmc defaults defaults
/dev/block/platform/bootdevice/by-name/para /para emmc defaults defaults
/dev/block/platform/bootdevice/by-name/misc /misc emmc defaults defaults,first_stage_mount
/dev/block/platform/bootdevice/by-name/boot /boot emmc defaults first_stage_mount,nofail,
/dev/block/platform/bootdevice/by-name/recovery /recovery emmc defaults first_stage_mount,nofail,
/dev/block/platform/bootdevice/by-name/logo /logo emmc defaults defaults
/dev/block/platform/bootdevice/by-name/expdb /expdb emmc defaults defaults
/dev/block/platform/bootdevice/by-name/seccfg /seccfg emmc defaults defaults
/dev/block/platform/bootdevice/by-name/tee1 /tee1 emmc defaults defaults
/dev/block/platform/bootdevice/by-name/tee2 /tee2 emmc defaults defaults
/dev/block/platform/bootdevice/by-name/scp1 /scp1 emmc defaults defaults
/dev/block/platform/bootdevice/by-name/scp2 /scp2 emmc defaults defaults
/dev/block/platform/bootdevice/by-name/sspm_1 /sspm_1 emmc defaults defaults
/dev/block/platform/bootdevice/by-name/sspm_2 /sspm_2 emmc defaults defaults
/dev/block/platform/bootdevice/by-name/efuse /efuse emmc defaults defaults
/dev/block/platform/bootdevice/by-name/md1img /md1img emmc defaults defaults
/dev/block/platform/bootdevice/by-name/md1dsp /md1dsp emmc defaults defaults
/dev/block/platform/bootdevice/by-name/md1arm7 /md1arm7 emmc defaults defaults
/dev/block/platform/bootdevice/by-name/md3img /md3img emmc defaults defaults
/dev/block/platform/bootdevice/by-name/gz1 /gz1 emmc defaults defaults
/dev/block/platform/bootdevice/by-name/gz2 /gz2 emmc defaults defaults
/dev/block/platform/bootdevice/by-name/spmfw /spmfw emmc defaults defaults
/dev/block/platform/bootdevice/by-name/boot_para /boot_para emmc defaults defaults
/dev/block/platform/bootdevice/by-name/odmdtbo /odmdtbo emmc defaults defaults
/dev/block/platform/bootdevice/by-name/dtbo /dtbo emmc defaults defaults
/dev/block/platform/bootdevice/by-name/vbmeta /vbmeta emmc defaults defaults
/dev/block/platform/bootdevice/by-name/uh /uh emmc defaults defaults
Abdulrehman130 said:
#########Concept########
For TWRP Recovery Users ( who don't have root)
PHP:
Open recovery mode and tap on "Advance>file manager" and go to this path
For Root Users Use any "Root File Manager".
PHP:
Go to "System/etc" path
OR
PHP:
go to "system_root/system/etc
If Fstab isn't available inside "system" then search it in *vendors* folder
PHP:
go to "vendor/etc"
find ("fstab") named file in etc folder.
maybe more than 1 fstab file will be there.
In that condition.
You need to check which one fstab file has partition blocks names like ("system, vendor, userdata) etc.
so just copy this Fstab file to SD card Or anywhere you like, for editing.
###Editing####
Download"Quick Edit Apk" from store.
Open This fstab file using this Quick edit tool and find line which has word like "data" or "userdata".
Something like these two lines.
PHP:
"dev/block/bootdevice/by-name/userdata"
OR
PHP:
"dev/block/bootdevice/by-name/data"
Now Find word similar to "Encrypt" in this line.
Change "encrypt" word to "decrypt" of this userdata line.
You will find one of these like words .
Hint
PHP:
"forceencrypt" >>>>>>>>>>>>>>change it to "forcedecrypt"
PHP:
"encryptable" >>>>>>>>>>>>>>>>>change it to "decryptable"
PHP:
"encrypt" >>>>>>>>>>>>>>>>>>>>change it to "decrypt"
PHP:
"encryption" >>>>>>>>>>>>>>>>>>change it to "decryption"
See I Just Change "en" to "de"
Mean ”En”crypt to ”de”crypt
For example on my phone fstab the line was this.
PHP:
/dev/block/platform/bootdevice/by-name/userdata /data f2fs noatime,nosuid,nodev,discard,noflush_merge wait,check,quota,reservedsize=128M,formattable,resize,forceencrypt=/dev/block/platform/bootdevice/by-name/metadata,
Now I founded both "userdata" and "forceencrypt" and i changed it according to my need.
("Root Users, You have done eding" Now reset you device and enjoy")
### TWRP Users you can continue ###
go back to recovery and copy this edited fstab to
"it's original location (where you found it).
(For me it was founded in vendor/etc path and i pasted this edited fstab there)
after pasting done, then again go to it's original location (Pasted location)(For me it was vendor/etc)
And tap on this edited "fstab" and select on "chmod" option And set permission to 0644 of this file.
wipe your data, internal storage and dalvik-cable.
Reboot
now error is completely gone
Watch this video of you're still confused.
Click to expand...
Click to collapse
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