yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 4 Q&A, Help & Troubleshooting] thisisapoorusernamechoice:
M,

Sorry , I'm always running (at least) one step behind you. I got the listing of the /system/lib/modules folder, also zipped and attached below. I'm going to go through the system folder (and then take a look at the other images in the tar if that doesn't work) to see if I can find anything about the display.

/system/lib/modules/ listing:

A folder named pronto (so /system/lib/pronto/) with a single file, pronto_wlan.ko

ansi_cprng.ko

core_ctl.ko

dma_test.ko

evbug.ko

gator.ko

mmc_block_test.ko

mmc_test.ko

msm-buspm-dev.ko

oprofile.ko

radio-iris-transport.ko

spidev.ko

tcp-htcp.ko

tcp_westwood.ko

test-iosched.ko

UPDATE: I know this isn't what you're asking for but these lines in the build.prop seemed interesting enough to mention:

ro.product.device=matissevewifi
ro.product.board=MSM8916
ro.chipname=APQ8016

ANOTHER UPDATE [MENTION=5864662]moonbutt74[/MENTION], am I annoying you yet? :silly: I opened a couple files (/system/usr/idc/Synaptics_RMI4_TouchPad_Sensor.idc and /system/usr/idc/Synaptics_RMI4_TouchPad.idc) and they both talk about "Atmel Maxtouch touch screen", is this what you were looking for? I'm going to keep combing the system folder to be thorough. And screw it, I'm going to zip and attach those two files, since why the hell not?
[Galaxy Tab 4 Q&A, Help & Troubleshooting] :
for reference

CPU-Z for Android Report - 1.15

CPUs : 4

SoCs : 1

CPU 0 : ARMv7 Processor rev 0 (v7l)

Name : Qualcomm Snapdragon 400/410

CPUs : 4

Core set 0 : ARM Cortex-A53

Core set 0 Nb Cores : 4

Core set 0 Max Clock : 1190 MHz

Core set 0 Impl.id : 0x41

Core set 0 Arch.id : 0x7

Core set 0 Var.id : 0

Core set 0 Part.id : 0xd03

Core set 0 Rev.id : 0

Core set 0 Revision : r0p0

Arch : 4x ARM Cortex-A53 @1.19 GHz

Codename :

Process : 28 nm

GPU Vendor : Qualcomm

GPU Renderer : Adreno (TM) 306

Model : SM-T533 (matissevewifixx)

Manufacturer : samsung

Board : MSM8916

Hardware : qcom

Android Ver. : 4.4.4

Kernel Arch. : armv7l

Battery capacity : 6800

--- CPUInfos ---

abi : armeabi-v7a

abi2 : armeabi

processor : 0

model name : ARMv7 Processor rev 0 (v7l)

BogoMIPS : 38.40

Features : swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt

CPU implementer : 0x41

CPU architecture: 7

CPU variant : 0x0

CPU part : 0xd03

CPU revision : 0

processor : 1

model name : ARMv7 Processor rev 0 (v7l)

BogoMIPS : 38.40

Features : swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt

CPU implementer : 0x41

CPU architecture: 7

CPU variant : 0x0

CPU part : 0xd03

CPU revision : 0

processor : 2

model name : ARMv7 Processor rev 0 (v7l)

BogoMIPS : 38.40

Features : swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt

CPU implementer : 0x41

CPU architecture: 7

CPU variant : 0x0

CPU part : 0xd03

CPU revision : 0

processor : 3

model name : ARMv7 Processor rev 0 (v7l)

BogoMIPS : 38.40

Features : swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt

CPU implementer : 0x41

CPU architecture: 7

CPU variant : 0x0

CPU part : 0xd03

CPU revision : 0

Hardware : Qualcomm Technologies, Inc APQ8016

Revision : 0002

Serial : b38cd6490de57cef

Processor : ARMv7 Processor rev 0 (v7l)

--- Debug Infos ---

4=400000000

5= 0 1028763655

8=400000000 310000000 200000000

15=-1

20=tsens_tz_sensor0=39

21=tsens_tz_sensor1=36

22=tsens_tz_sensor2=34

23=tsens_tz_sensor4=36

24=tsens_tz_sensor5=37

25=pm8916_tz=29345

26=pa_therm0=10

27=stc3117-fuelgauge=-4000

28=battery=27400

51=tsens_tz_sensor0=39

52=tsens_tz_sensor1=36

53=tsens_tz_sensor2=34

54=tsens_tz_sensor4=36

55=tsens_tz_sensor5=37

56=pm8916_tz=29345

57=pa_therm0=10

58=stc3117-fuelgauge=-4000

59=battery=27400

clock0=1190400

clock1=-1

clock2=-1

clock3=-1

i am guessing this is the panel -- samsung_panel_init : ss_dsi_panel_TC358764_LTL101A106_WXGA
[Galaxy Tab 4 Q&A, Help & Troubleshooting] :
H,

can you run uname -a in terminal or give me a screenshot of the tab in your settings that shows kernel version information?

also can you run the following command,

ls -al /proc/config.gz

if it comes back with an actual listing of that file, i need it, if so then run

cp /proc/config.gz /sdcard/config.gz and attach that to your post.

[MENTION=3132221]sub77[/MENTION] has resources for a twrp build for matissevewifi using prebuilt kernel,

https://github.com/GalaxyTab4/twrp_device_samsung_matisseve/blob/twrp-cm12/BoardConfig.mk

if he has a build of twrp available for your tab then

that would be the way to go.

i did stumble onto this source for a kernel https://github.com/MSM8916-Samsung/android_kernel_samsung_e53g

it has dts's for your device,

/dts-v1/;

#include "msm8916-sec-matissevewifi-eur-r00.dtsi"
#include "msm8916-memory.dtsi"

so once my internet gets fixed maybe i'll be able to clone that and get something working. :confused:
[Galaxy Tab 4 Q&A, Help & Troubleshooting] HausiX10:
from uname -a:

Linux localhost 3.10.28-4271302 #1 SMP PREEMPT Wed Jul 8 14:21:44 KST 2015 armv7l GNU/Linux

there is no config.gz in the kernel

btw I tried the twrps from sub77, but none would install/display

hans
[Galaxy Tab 4 Q&A, Help & Troubleshooting] HausiX10:
sub & moon,

copied a few logfiles from cache/recovery, maybe that helps ...

hans
[Galaxy Tab 4 Q&A, Help & Troubleshooting] :
[MENTION=3126603]HausiX10[/MENTION]

okay try this test out,

the name of the file is sm-t533-test-recovery-philz.tar https://www.androidfilehost.com/?fid=24269982086999167

okay if this boots [or boots but no display] connect your tab to pc and run

adb shell logcat -d

and post that output.

instructions-

download image

boot tab into odin/download mode

start odin on pc then connect tab

in odin uncheck/deselect auto restart function

load the downloaded image into AP tab/field and click start

when flash is done/complete [resok] , disconnect tab and manually reboot TO RECOVERY!!

OKAY NOW IF IT BOOTS,

run the previous command i requested, also test out screen navigation/menus

if all going well so far, then find the option in recovery to set backup format...

choose tar/compressed, set medium compression

use the recovery to make a full backup.

reboot to normal operation and check if the backup looks correct for size.

report back.

OKAY IF IT DOESN'T BOOT

restore your stock recovery

boot into normal operation and run the following command

dmesg > /sdcard/sm-t533-dmesg.txt --and attach that in next post or pastebin and link.

i am using prebuilt stock kernel for the moment.

m
[Galaxy Tab 4 Q&A, Help & Troubleshooting] HausiX10:
Hi Moon, it does not boot:

>>Could not do normal boot

>>ODIN MODE

Hans
[Galaxy Tab 4 Q&A, Help & Troubleshooting] :
h,

just to be clear, this is the dmesg from the tab DURING regular operation ?

i'm not seeing panel information [display]

there is still no "Official" source i can find so i'm bouncinf between sources :rolleyes:

fyi, it doesn't boot is not an adequate response, for testing a recovery you should include a brief desciption of your

process, device prep, image flashing, odin version [if relevant] etc.

also , always plug into pc after booting a recovery and attempt/confirm if you can get, adb access.

i'm still going through your dmesg and other logs, as i find out what your hardware is, i'll try to mod my working sources for the current

sm-t53x's and sm-t33x's i've have covered. i am thinking the display panel could be a "generic" kind of thing ... maybe?

m
[Galaxy Tab 4 Q&A, Help & Troubleshooting] HausiX10:
>>just to be clear, this is the dmesg from the tab DURING regular operation ?

-- Yes, I have pulled e new dmesg and attach it (looks different)

>>process, device prep, image flashing, odin version [if relevant] etc.

-- Win7 Odin3.10 / Manjaro Linux Heimdall 1.4.1

>>also , always plug into pc after booting a recovery and attempt/confirm if you can get, adb access.

-- no devices listed in adb

>>i'm still going through your dmesg and other logs, as i find out what your hardware is, i'll try to mod my working >>sources for the current

thanks and keep going :)

Hans
[Galaxy Tab 4 Q&A, Help & Troubleshooting] :
h,

can you run

cat /proc/partitions

i'm still looking for a kernel source to cobble something together, so far no official

your kernel is apparently 64 bit with some kind of binder hook to function with a 32bit userspace though compiling

for this supposed 64bit kernel seems to be just about the same as compiling 32 bit

your recovery binaries are 32 bit.

currently i am looking at the setup/device tree/kernel for the e53g/e500x, cortex a53 msm 8916-ish

m
[Galaxy Tab 4 Q&A, Help & Troubleshooting] HausiX10:
m, here goes...

hans
[Galaxy Tab 4 Q&A, Help & Troubleshooting] :
H, [MENTION=3132221]sub77[/MENTION]

okay , in spite of the cortex a53 armv8 blah-bitty-blah, your kernel is apparently 32-bit armv7

from your stock boot.img "clipped list"

root@kali:/AIK-Linux/split_img# strings boot.img-zImage | grep -i -e "32-bit" -e "64-bit" -e "arm"
[COLOR="Red"]ARMv7 Processor[/COLOR]
aarm_dt8
armv7
s ARMv7 D:
cm_armv8
[COLOR="Red"]v 32-bit[/COLOR]
Varmv8
arm_elf_read_implies_exec
Tarmv8
arm,armv7-timer-
[COLOR="Red"]arm,cortex-a15-pmu[/COLOR]
arm11mpcore
army

from your stock recovery.img [again, clipped]

root@kali:/AIK-Linux/split_img# strings recovery.img-zImage | grep -i -e "32-bit" -e "64-bit" -e "arm"
[COLOR="Red"]ARMv7 Processor[/COLOR]
aarm_dt8
armv7
s ARMv7 D:
cm_armv8
[COLOR="Red"]v 32-bit[/COLOR]
Tarmv8
arm,armv7-timer-
[COLOR="Red"]arm,cortex-a15-pmu[/COLOR]
arm11mpcore

Soooo, unless i'm wrong it means the specs on gsmarena and pdadb are wrong oooor, samsung is LYING RAAAAAARGH... and stuff. :silly:

I have found two sources containing your device dts/dtsi/dtb and they are for the;

serranoveltexx a.k.a. Samsung GT-i9195I Galaxy S4 Mini Plus 4G LTE

e53g a.k.a. Samsung SM-E500M Galaxy E5 4G LTE Specs

there are more.

the kernel version is roughly

VERSION = 3
PATCHLEVEL = 10
SUBLEVEL = 49
EXTRAVERSION =
NAME = TOSSUG Baby Fish

arch/arm/boot/dts/samsung/msm8916/msm8916-pinctrl-sec-matissevewifi-eur-r00.dtsi
arch/arm/boot/dts/samsung/msm8916/msm8916-pinctrl-sec-matissevewifi-eur-r02.dtsi
arch/arm/boot/dts/samsung/msm8916/msm8916-sec-matissevewifi-eur-battery-r00.dtsi
arch/arm/boot/dts/samsung/msm8916/msm8916-sec-matissevewifi-eur-r00.dts
arch/arm/boot/dts/samsung/msm8916/msm8916-sec-matissevewifi-eur-r00.dtsi
arch/arm/boot/dts/samsung/msm8916/msm8916-sec-matissevewifi-eur-r02.dts
arch/arm/boot/dts/samsung/msm8916/msm8916-sec-matissevewifi-eur-r02.dtsi

so i am attempting to stitch together a defconfig.

m

EDIT okay, so i am explaining kernel drivers to my 8 year old niece... xD
[Galaxy Tab 4 Q&A, Help & Troubleshooting] :
[MENTION=3126603]HausiX10[/MENTION]

okay test two,

https://www.androidfilehost.com/?fid=24269982087005179 sm-t533-test_2-recovery-philz.tar

Flash in Odin with auto/restart UNCHECKED, maunually reboot to RECOVERY after flash completes.

OKay so far the points of trouble in the kernel source i'm working on are with the display panel and

pronto wlan, I am not sure about that one, if your device does use pronto it might be built into kernel instead of out as module ?

Also, i am uncertain if your device uses concatenated zimg/dtb. this image has a seperate dtb image.

I am somewhat sure that display will not come up, but plug back in and check for adb access, if yes run

dmesg

logcat

kmsg or last_kmsg

NOTE previous test was absent fstab.qcom, DERP, hopefully got it right this time.

Still unclear on how to compile a 64-bit kernel for this pig but, i am pretty sure a 32-bit kernel will do.

m
[Galaxy Tab 4 Q&A, Help & Troubleshooting] HausiX10:
m, its past midnight here. i give it a try tomorrow, thanks anyway.

hans
[Galaxy Tab 4 Q&A, Help & Troubleshooting] HausiX10:
m,

flashed with various odins, rebooted recovery -> device shuts down after the seandroid message.

so no dmesg etc :(

hans
[Galaxy Tab 4 Q&A, Help & Troubleshooting] :
okay , does it shut down or go back into odin mode ?

the seandroid message doesn't mean anything.
[Galaxy Tab 4 Q&A, Help & Troubleshooting] HausiX10:
it shuts down...
[Galaxy Tab 4 Q&A, Help & Troubleshooting] :
okay so,

test 1 booted past samsung splash logo , to black screen.

test 2 crashed/power off after samsung logo splash screen but DID NOT reboot to odin/download mode.

Correct?

probably including dt.img or incorrect fstab entry? You have root correct?

If so download this; https://www.androidfilehost.com/?fid=23991606952606321 parted.zip

extract it and copy to system/xbin

chmod 755 /system/xbin/parted

parted /dev/block/mmcblk0

print all

q

post that output.

m

for reference parted listing

GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
Model: MMC 400073 (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number Start End Size File system Name Flags
1 4194kB 19.9MB 15.7MB apnhlos
2 19.9MB 80.2MB 60.2MB modem
3 80.2MB 80.7MB 524kB sbl1
4 80.7MB 80.7MB 32.8kB ddr
5 80.7MB 82.8MB 2097kB aboot
6 82.8MB 83.3MB 524kB rpm
7 83.3MB 83.9MB 524kB qsee
8 83.9MB 84.4MB 524kB qhee
9 84.4MB 87.5MB 3146kB fsg
10 87.5MB 87.5MB 16.4kB sec
11 87.5MB 98.6MB 11.0MB pad
12 98.6MB 109MB 10.5MB param
13 109MB 124MB 14.7MB ext4 efs
14 124MB 127MB 3146kB modemst1
15 127MB 130MB 3146kB modemst2
16 130MB 144MB 13.6MB boot
17 144MB 159MB 15.7MB recovery
18 159MB 173MB 13.6MB fota
19 173MB 180MB 7331kB backup
20 180MB 183MB 3146kB fsc
21 183MB 183MB 8192B ssd
22 183MB 192MB 8389kB ext4 persist
23 192MB 201MB 9437kB persdata
24 201MB 3137MB 2936MB ext4 system
25 3137MB 3347MB 210MB ext4 cache
26 3347MB 3379MB 31.5MB ext4 hidden
27 3379MB 15.8GB 12.4GB ext4 userdata

for reeference cat /proc/partitions

major minor #blocks name

179 0 15388672 mmcblk0
179 1 15360 mmcblk0p1
179 2 58816 mmcblk0p2
179 3 512 mmcblk0p3
179 4 32 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 3072 mmcblk0p9
179 10 16 mmcblk0p10
179 11 10768 mmcblk0p11
179 12 10240 mmcblk0p12
179 13 14336 mmcblk0p13
179 14 3072 mmcblk0p14
179 15 3072 mmcblk0p15
179 16 13312 mmcblk0p16
179 17 15360 mmcblk0p17
179 18 13309 mmcblk0p18
179 19 7159 mmcblk0p19
179 20 3072 mmcblk0p20
179 21 8 mmcblk0p21
179 22 8192 mmcblk0p22
179 23 9216 mmcblk0p23
179 24 2867200 mmcblk0p24
179 25 204800 mmcblk0p25
179 26 30720 mmcblk0p26
179 27 12089328 mmcblk0p27
179 32 4096 mmcblk0rpmb
179 64 30437376 mmcblk1
179 65 30433280 mmcblk1p1

for reference display panel is;

TC358764/5 Display Bridge (MIPI® DSI to LVDS)
Toshiba TC358764_LTL101AL06 @ drivers/video/msm/mdss/samsung/TC358764_LTL101AL06_KTD3156

[RFC PATCH v2 08/21] drm/panel: add TC358764 driver

http://lists.freedesktop.org/archives/dri-devel/2014-February/053713.html
[Galaxy Tab 4 Q&A, Help & Troubleshooting] HausiX10:
m, test 1 is correct, samsung splash, then shutdown

hans

n.b. it takes about >5 secs of pressing power button to come back booting
[Galaxy Tab 4 Q&A, Help & Troubleshooting] :
H,

okay test 3, ain't this fun ? :silly:

https://www.androidfilehost.com/?fid=24269982087007398 sm-t533-test_3-recovery-philz.tar

Flash with auto/restart disabled, force reboot to recovery, NOTE; if you accidentally reboot to normal then you

need to re-flash recovery again as per instructs.

okay so test 1 was with stock zImage

test 2 was frankenstein source without display issue un-resolved and questionable dt.img

test 3 is freaky frankenstein source with display hopefully resolved and dt.img correct hopefully

as usual check for adb access, if yes get

logcat

dmesg

kmsg

m
[Galaxy Tab 4 Q&A, Help & Troubleshooting] HausiX10:
m,

it flashes ok, but when i boot into recovery, it shows the samsung splash for a few seconds and then reboots to normal mode.

so no logcat et al

hans
[Galaxy Tab 4 Q&A, Help & Troubleshooting] :
hmm, same as before or this time it actually hung for a bit ?

i've got a few more tests, but as of yet there is still no official source for the kernel.

my next test would probably be to clip the dt.img.

m

after thought, might be the fstab. or ramdisk compression, i used lzma, should probably used gzip
[Galaxy Tab 4 Q&A, Help & Troubleshooting] :
H,

quick question, how did you root your tab ?

THE 64-BIT CAKE IS A LIE !!!!!!!!!!!!!!!!!!!!! :silly:

m
[Galaxy Tab 4 Q&A, Help & Troubleshooting] HausiX10:
Kingo Root
[Galaxy Tab 4 Q&A, Help & Troubleshooting] :
H, okay thanks, i was hoping for a cf autoroot for this device but no-go. I have written opensource.samsung requesting the sourcecode

for the SM-T533 and the SM-T333, pretty sure i sent it along with typos. :silly:
[Galaxy Tab 4 Q&A, Help & Troubleshooting] :
H,

from samsung ,

Can you get and post the information in red please ?

m
[Galaxy Tab 4 Q&A, Help & Troubleshooting] HausiX10:
m, i got a screenshot, but it is not in red (shame on me), i hope that is ok with you

hans
[Galaxy Tab 4 Q&A, Help & Troubleshooting] HausiX10:
hi m, did you get an answer (source) from the opensource people?

hans
[Galaxy Tab 4 Q&A, Help & Troubleshooting] :
No answer saying the requested source has been made available, I received an email yesterday which seems to be the same as the one sent on Dec 1st.
[Galaxy Tab 4 Q&A, Help & Troubleshooting] HausiX10:
funny guys ?
[Galaxy Tab 4 Q&A, Help & Troubleshooting] :
SM-T533 T533XXU1AOG1	SM-T533_KK_Opensource.zip !
[Galaxy Tab 4 Q&A, Help & Troubleshooting] repey6:
[MENTION=5864662]moonbutt74[/MENTION] great !:D
[Galaxy Tab 4 Q&A, Help & Troubleshooting] HausiX10:
good news, took them a while, but still... :o:good:
[Galaxy Tab 4 Q&A, Help & Troubleshooting] myheroduane:
Does this mean you can build a recovery?
[Galaxy Tab 4 Q&A, Help & Troubleshooting] :
M,

that's the intention as per the thread title. This is however not a discussion thread, if/when a successful build is completed and H confirms it working then, that will be posted in the appropriate thread.

m
[Galaxy Tab 4 Q&A, Help & Troubleshooting] :
H,

okay test 4

sm-t533-test_4-recovery-philz.tar

The same routine as before, i still have some question on the dt.img as mine comes out smaller than stock's by about 3kb :confused:

I will push the kernel source to git when my connection stops crapping out on me.
[Galaxy Tab 4 Q&A, Help & Troubleshooting] HausiX10:
M, does flash, but not start and no connection with adb...

Hans
[Galaxy Tab 4 Q&A, Help & Troubleshooting] :
H, thanks. A quick question, does your stock recovery boot normally?

Samsung has released the LL source for the sm-t533 as well

http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=sm-t533

Provided real life gets out of my way for a bit i will have another test up shortly, if that doesn't do it i will scrap my current device tree and start over.

m
[Galaxy Tab 4 Q&A, Help & Troubleshooting] HausiX10:
m, stock recovery boots normal. all the best for your real life! hans
[Galaxy Tab 4 Q&A, Help & Troubleshooting] :
okaay, test 5,

sm-t533-test_5-recovery-philz.tar

same routine as before, this is from the LL kernel source release , selinux should be disabled.

the kernel source is official so i can't see how a hardware issue could be the cause, my guess then

would be flaws in my fstab, or error in the kernel cmdline

the commandline of the stock boot.img posted is:

boot.img: Android bootimg, kernel, ramdisk, page size: 2048, cmdline (console=null androidboot.hardware=qcom user_debug=23 msm_rtb.fi)

the commandline of the stock recovery.img posted is:

recovery.img: Android bootimg, kernel, ramdisk, page size: 2048, cmdline (console=null androidboot.hardware=qcom user_debug=23 msm_rtb.fi)

The above is just a reference, but this test 5 does not have a commandline, like i said test. :silly:

crossing my fingers.

m
[Galaxy Tab 4 Q&A, Help & Troubleshooting] HausiX10:
M, good news: it boots :svetius:, bad news: it does not work because of mount errors.

Logcat is not available.

If I do Reboot system, it reboots recovery

I attach a screenshot and some text I was able to get.

cheers Hans

n.b. I like the background
[Galaxy Tab 4 Q&A, Help & Troubleshooting] :
h,

okay good deal. the resolution looks off though :confused:

what's the actual dimension ? i thought it to be 1280x800.

The fstab is the culprit ! give me a little while to post another test and see what the correct layout is.

while in regular operation can you run

cat /fstab.qcom

and post in reply and not as attachment ? thanks

m

if the resolution works for you then i won't worry about it.
[Galaxy Tab 4 Q&A, Help & Troubleshooting] HausiX10:
m, the resolution looks ok to me (old eyes, 71 :))

hans

u0_a195@matissevewifi:/ $ su

root@matissevewifi:/ # cat /fstab.qcom

# 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

#TODO: Add 'check' as fs_mgr_flags with data partition.

# Currently we dont have e2fsck compiled. So fs check would failed.

#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>

/dev/block/bootdevice/by-name/system /system ext4 ro,errors=panic wait

/dev/block/bootdevice/by-name/userdata /data ext4 nosuid,nodev,noatime,noauto_da_alloc,discard,journal_async_commit,errors=panic wait,check,encryptable=footer

# VOLD

/devices/soc.0/7864900.sdhci/mmc_host/mmc1 auto vfat devault voldmanaged=extSdCard:auto,noemulatedsd

/devices/platform/msm_hsusb_host/usb1*sda auto vfat default voldmanaged=UsbDriveA:auto

/devices/platform/msm_hsusb_host/usb1*sdb auto vfat default voldmanaged=UsbDriveB:auto

/devices/platform/msm_hsusb_host/usb1*sdc auto vfat default voldmanaged=UsbDriveC:auto

/devices/platform/msm_hsusb_host/usb1*sdd auto vfat default voldmanaged=UsbDriveD:auto

/devices/platform/msm_hsusb_host/usb1*sde auto vfat default voldmanaged=UsbDriveE:auto

/devices/platform/msm_hsusb_host/usb1*sdf auto vfat default
[Galaxy Tab 4 Q&A, Help & Troubleshooting] :
h,

yeah my eyes are shot too :silly: <-- this is why.

okay here is test 6 - confirmed booting, resolution suitable, tinkering with fstab to get mounts up.

sm-t533-booting-test_6-recovery-philz.tar

On this one, even if mounts fail check for adb access, if good and root # , then please run and post output of

mount

m
[Galaxy Tab 4 Q&A, Help & Troubleshooting] HausiX10:
M, here are my findings

rootfs on / type rootfs (rw)

tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,size=721748k,nr_inodes=180437,mode=755)

devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)

proc on /proc type proc (rw,relatime)

sysfs on /sys type sysfs (rw,seclabel,relatime)

selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)

tmpfs on /tmp type tmpfs (rw,seclabel,relatime,size=721748k,nr_inodes=180437)

tmpfs on /storage type tmpfs (rw,seclabel,relatime,size=721748k,nr_inodes=180437,mode=050,gid=1028)

tmpfs on /mnt/secure type tmpfs (rw,seclabel,relatime,size=721748k,nr_inodes=180437,mode=700)

tmpfs on /mnt/fuse type tmpfs (rw,seclabel,relatime,size=721748k,nr_inodes=180437,mode=775,gid=1000)

adb on /dev/usb-ffs/adb type functionfs (rw,relatime)

Backup & Restore works OK

Problems:

* rooting on exit results in a hang on bootanimation screen, this cannot be undone, had to reinstall (5.1 now, hope that this does not matter too much)

* reboot shuts down

Hans