Database Users

partition names and partition dump

Hi,
i extracted the partition names for you and made a parition dump after unlocking and rooting.
I hope you find this helpful.
I skipped partition 28 since that is userdata.
Where should I host the dumped files?
Code:
/dev/block/platform/msm_sdcc.1/by-name # ls -al
ls -al
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
drwxr-xr-x 2 root root 620 Jan 22 00:29 .
drwxr-xr-x 4 root root 700 Jan 22 00:29 ..
lrwxrwxrwx 1 root root 20 Jan 22 00:29 DDR -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 Jan 22 00:29 DRIVER -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 Jan 22 00:29 LOGO -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 20 Jan 22 00:29 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 Jan 22 00:29 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 Jan 22 00:29 cache -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 20 Jan 22 00:29 dbi -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 Jan 22 00:29 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 Jan 22 00:29 fsg -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 Jan 22 00:29 grow -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 Jan 22 00:29 misc -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 20 Jan 22 00:29 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 Jan 22 00:29 modemst1 -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 Jan 22 00:29 modemst2 -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 Jan 22 00:29 oppodycnvbk -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 Jan 22 00:29 oppostanvbk -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 20 Jan 22 00:29 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 Jan 22 00:29 persist -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 Jan 22 00:29 recovery -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 Jan 22 00:29 reserve1 -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 Jan 22 00:29 reserve2 -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 Jan 22 00:29 reserve3 -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 Jan 22 00:29 reserve4 -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 20 Jan 22 00:29 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 Jan 22 00:29 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 Jan 22 00:29 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 Jan 22 00:29 system -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 20 Jan 22 00:29 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 Jan 22 00:29 userdata -> /dev/block/mmcblk0p28
/dev/block/platform/msm_sdcc.1/by-name #

Polarfuchs said:
Hi,
i extracted the partition names for you and made a parition dump after unlocking and rooting.
I hope you find this helpful.
I skipped partition 28 since that is userdata.
Where should I host the dumped files?
Code:
/dev/block/platform/msm_sdcc.1/by-name # ls -al
ls -al
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
drwxr-xr-x 2 root root 620 Jan 22 00:29 .
drwxr-xr-x 4 root root 700 Jan 22 00:29 ..
lrwxrwxrwx 1 root root 20 Jan 22 00:29 DDR -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 Jan 22 00:29 DRIVER -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 Jan 22 00:29 LOGO -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 20 Jan 22 00:29 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 Jan 22 00:29 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 Jan 22 00:29 cache -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 20 Jan 22 00:29 dbi -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 Jan 22 00:29 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 Jan 22 00:29 fsg -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 Jan 22 00:29 grow -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 Jan 22 00:29 misc -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 20 Jan 22 00:29 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 Jan 22 00:29 modemst1 -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 Jan 22 00:29 modemst2 -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 Jan 22 00:29 oppodycnvbk -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 Jan 22 00:29 oppostanvbk -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 20 Jan 22 00:29 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 Jan 22 00:29 persist -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 Jan 22 00:29 recovery -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 Jan 22 00:29 reserve1 -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 Jan 22 00:29 reserve2 -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 Jan 22 00:29 reserve3 -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 Jan 22 00:29 reserve4 -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 20 Jan 22 00:29 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 Jan 22 00:29 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 Jan 22 00:29 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 Jan 22 00:29 system -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 20 Jan 22 00:29 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 Jan 22 00:29 userdata -> /dev/block/mmcblk0p28
/dev/block/platform/msm_sdcc.1/by-name #
Click to expand...
Click to collapse
Duplicate post...
See....
http://forum.xda-developers.com/showthread.php?t=2751530

HELP ME RUN THIS SCRIPT AND BACK UP YOUR ZE550KL GPT.bin

please help me run this emmc dumper batch file on your ZE 550KL (it requires adb access on your phone)
and help backup and share your gpt.bin file with me.
The program is here. https://drive.google.com/open?id=0B39xYnt0Q7O0cWQwVlRXVFNIWHM
Thank you.

please can anyone try this application Partitions Backup https://youtu.be/sikZ3IBAdew on their phone to backup all the hidden system partitions like sbl1, tz. etc. and post a screenshot of the partitions that are available for backup?
i'm hoping there's a chance the msimage.mbn and MPRG.mbn may be listed for backup. in which case you would be saving a life.

No one really should upload you full dump of their mmcblk0. It contains very sensitive informations like IMEI, whole /data and more...
BTW there are no msimage and MPRG partitions.
[email protected]:/ # ls -la /dev/block/bootdevice/by-name/
total 0
drwxr-xr-x 2 root root 960 1970-06-23 16:04 .
drwxr-xr-x 4 root root 1040 1970-06-23 16:04 ..
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 ADF -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 APD -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 20 1970-06-23 16:04 DDR -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 aboot -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 abootbak -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 abootdebug -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 asdf -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 asusfw -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 asusgpt -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 asusgpt1 -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 asusgpt2 -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 asuskey -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 asuskey2 -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 asuskey3 -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 asuskey4 -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 asuskey5 -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 boot -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 cache -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 config -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 devinfo -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 factory -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 factorybak -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 fsc -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 fsg -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 20 1970-06-23 16:04 hyp -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 1970-06-23 16:04 hypbak -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 keystore -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 misc -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 modem -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 modemst1 -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 modemst2 -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 oem -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 persist -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 persistent -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 recovery -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 20 1970-06-23 16:04 rpm -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 1970-06-23 16:04 rpmbak -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 1970-06-23 16:04 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 1970-06-23 16:04 sbl1bak -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 sec -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 splash -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 ssd -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 system -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 20 1970-06-23 16:04 tz -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 1970-06-23 16:04 tzbak -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 userdata -> /dev/block/mmcblk0p46
Click to expand...
Click to collapse

LuK1337 said:
No one really should upload you full dump of their mmcblk0. It contains very sensitive informations like IMEI, whole /data and more...
BTW there are no msimage and MPRG partitions.
Click to expand...
Click to collapse
I don't want the whole thing. It will be too large anyway. I have the stock rom.
I need the files i already outlined.
BTW i read somewhere that the gpt.bin can be renamed to the msimage as they both contain the same thing i.e. the partition table

Needless to say, what exactly is wrong with my trying to revive my device? i bought this device with my hard earned money just 3 months ago.
if i ask for help and nobody answers, so be it. its my prerogative to ask.
Could have sworn this is XDA and i'm allowed to hack my own device if possible..

It is not your "prerogative" to ask. Where in XDA's terms and services did you get that from? Continuously spamming threads won't suddenly compel someone to do the things you ask.

andrehsu said:
It is not your "prerogative" to ask. Where in XDA's terms and services did you get that from? Continuously spamming threads won't suddenly compel someone to do the things you ask.
Click to expand...
Click to collapse
ok. Noted.
@MikeChannon please close this thread. its served its / its useless

Need help extracting firmware from AT&T Galaxy Tab E 8.0 (SM-T377A)

Hey guys, so recently I've been trying to extract the stock Android 7.1.1 firmware from my AT&T Tab E so that I can package it into a flashable .tar.md5 file for Odin.
So far this is what I have:
First I typed this into the Terminal Emulator app on the tablet:
Code:
ls -al /dev/block/platform/13540000.dwmmc0/by-name
And it spit this out:
Code:
lrwxrwxrwx 1 root root 21 2018-06-02 00:30 BOOT -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 20 2018-06-02 00:30 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 2018-06-02 00:30 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 2018-06-02 00:30 CACHE -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 20 2018-06-02 00:30 CARRIER -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 2018-06-02 00:30 CDMA-RADIO -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 20 2018-06-02 00:30 CPEFS -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 2018-06-02 00:30 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 2018-06-02 00:30 OTA -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 2018-06-02 00:30 PARAM -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 2018-06-02 00:30 PERSDATA -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 2018-06-02 00:30 PERSISTENT -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 2018-06-02 00:30 RADIO -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 2018-06-02 00:30 RECOVERY -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 2018-06-02 00:30 RESERVED2 -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 2018-06-02 00:30 SYSTEM -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 2018-06-02 00:30 TDATA -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 2018-06-02 00:30 TOMBSTONES -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 2018-06-02 00:30 USERDATA -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 20 2018-06-02 00:30 m9kefs1 -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 2018-06-02 00:30 m9kefs2 -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 2018-06-02 00:30 m9kefs3 -> /dev/block/mmcblk0p7
This information lets us know which partition file in /dev/block is for the boot, system, recovery etc.
But when I try using this command to dump any of the files into my internal SD card:
Code:
dd if=/dev/block/mmcblk0pXX of=/sdcard/XXXXXXXX.img bs=4096
or external SD card:
Code:
dd if=/dev/block/mmcblk0pXX of=/storage/C35A-1CE6/XXXXXXXX.img bs=4096
It keeps on spitting out "Permission denied" and it doesn't do anything.
Correct me if I'm wrong, but I think it has something to do with me not having root access on my Tab E :/
Anyways, if somebody can help me with this it would be awesome!

MCU dump to image file

Hello, I was trying to dump my MCU partition into img file. That way I could try to reflash it back within the update mcu settings on device. My goal was to flash it with the dmcu.ext file that controls the resolution. I read I am supposed to flash MCU with text file dmcu.ext "screen:1" in the root of where the mcu image is. When I flash the entire image it does not seem to work, thought it could be because firmware is in one large bin file that contains all of the images like system and boot. I dumped the tee1 and tee2 to image file, would that be mcu? My resolution is showing 1024x600, instead of 800x480.
no matter what mcu img I attempt to update, MCU update says failed to update file. I was reading about mismatch, but don't see that error.
If I am not on the right track here, please correct me.
FF-5000:/ # ls -al /dev/block/platform/soc/11230000.mmc/by-name
total 0
drwxr-xr-x 2 root root 560 2010-01-01 00:01 .
drwxr-xr-x 4 root root 680 2010-01-01 00:01 ..
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 ANDROID -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 20 2010-01-01 00:01 ARM2 -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 BOOTIMG -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 CACHE -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 DKB -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 EXPDB -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 FRP -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 KB -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 20 2010-01-01 00:01 LK -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 LOGO -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 METAZONE -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 MISC -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 20 2010-01-01 00:01 NVRAM -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 ODMDTBO -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 20 2010-01-01 00:01 PROTECT_F -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 2010-01-01 00:01 PROTECT_S -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 2010-01-01 00:01 PRO_INFO -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 RECOVERY -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 20 2010-01-01 00:01 SECCFG -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 SEC_RO -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 2010-01-01 00:01 TEE1 -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 2010-01-01 00:01 TEE2 -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 VENDOR -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 forfanzone -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 tszone -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 userdata -> /dev/block/mmcblk0p26

Onn 11.6 Pro 100043279 with keyboard, no wifi after installing magisk (solved + minor tutorial)

Hi, I bought a 11.6 inch onn Tablet Pro yesterday, running android 11, model hardware 100043279. I followed this guide onn tablet magisk guide and I used this firmware link to thread with firmware. I'm running Linux as my host machine and using adb. I'm not sure if I made a huge mistake because this is my first time installing Magisk, it's possible that I messed up by not ensuring wifi was connected before flashing the image, or that I incorrectly did so.
I was able to install Magisk and am able to get root permissions. The main issue is that wifi is no longer working. I try to set it on in the toolbar and it just turns off automatically and greys out. I tried to set it using adb with ``` adb shell su -c 'svc enable wifi' ``` and
```
adb shell am start -a android.intent.action.MAIN -n com.android.settings/.wifi.WifiSettings
adb shell input keyevent 20 & adb shell input keyevent 23
```
and no luck. Wifi refuses to start. I tried to reset the device a few times already and re-flash the device using the boot.img that came with the mega.nz download. I also tried resetting it in various ways. No luck. I think I may have made a mistake by not logging in fully and setting everything up before flashing the device (I had set up google and wifi the first time, but then turned on fastboot and didnt set up everything a second time) so maybe its stuck in some kind of "setup" phase. But thats just my un-educated guess, I'm a complete noob at the moment.
Any advice or anything that I could try? Maybe I'm doing something blatantly incorrect that you could point out? It's kind of tough jumping into the rooting scene when everyone knows what everything means so there are no posts that bother to explain it, and every post and youtube video is entirely different in a thousand ways.

meili_33 said:
Any advice or anything that I could try?
Click to expand...
Click to collapse
I believe the problem is that the WiFi driver is outside the kernel.
So if you replace the working kernel with a different one (where all the kallsyms are different) everything will work except external modules.
When you Magisk'ed I presume that you took the boot image from somewhere and not directly off your device?
If you had taken it off your device there would have been no discrepancy.
Solutions (pick one):
Find the original boot image of your device and Magisk that
Find the WiFi driver that is compatible with your updated kernel

Renate said:
I believe the problem is that the WiFi driver is outside the kernel.
So if you replace the working kernel with a different one (where all the kallsyms are different) everything will work except external modules.
When you Magisk'ed I presume that you took the boot image from somewhere and not directly off your device?
If you had taken it off your device there would have been no discrepancy.
Solutions (pick one):
Find the original boot image of your device and Magisk that
Find the WiFi driver that is compatible with your updated kernel
Click to expand...
Click to collapse
Thank you, I'm wondering where I would be able to get the original boot image since I already overwrote mine? Is it potentially still there?

I'm replying to my own thread for the sake of being a completion-ist. I found the firmware for the 11.6 Pro 100043279 from a secondary source and it looks identical to what is linked in my original comment (I am not 100% sure admittedly). It was under a Youtube video with the title of the device in the name. I cannot say that this is safe otherwise I would link it. Yall can message me if you really really need to and I can point you there or provide you with my copy.
I downloaded it and went through and flashed every single image (vbmeta, vbmeta_system, vbmeta_vendor, super.img etc... anything I could flash, I did) and the tablet has wifi again. I'm going to try to use magisk on the image and retry the process. I also switched to a better cord and used the older USB port on my PC.
# Side note - the keyboard has to be disconnected for USB debugging to be recognized and should not be connected during the entire process.

And we have a success! Im happy thats my first ever magisk install. I'm going to list some of the resources that helped me and some general help.
Here is the output of
> adb shell ls -l /dev/block/by-name
Code:
total 0
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 boot_a -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 boot_b -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 20 2023-06-23 23:00 boot_para -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 cam_vpu1_a -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 cam_vpu1_b -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 cam_vpu2_a -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 cam_vpu2_b -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 cam_vpu3_a -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 cam_vpu3_b -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 dtbo_a -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 dtbo_b -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 20 2023-06-23 23:00 expdb -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 flashinfo -> /dev/block/mmcblk0p50
lrwxrwxrwx 1 root root 20 2023-06-23 23:00 frp -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 gz_a -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 gz_b -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 lk_a -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 lk_b -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 logo -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 20 2023-06-23 23:00 md_udc -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 2023-06-23 23:00 metadata -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 18 2023-06-23 23:00 mmcblk0 -> /dev/block/mmcblk0
lrwxrwxrwx 1 root root 23 2023-06-23 23:00 mmcblk0boot0 -> /dev/block/mmcblk0boot0
lrwxrwxrwx 1 root root 23 2023-06-23 23:00 mmcblk0boot1 -> /dev/block/mmcblk0boot1
lrwxrwxrwx 1 root root 22 2023-06-23 23:00 mmcblk0rpmb -> /dev/block/mmcblk0rpmb
lrwxrwxrwx 1 root root 20 2023-06-23 23:00 nvcfg -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 2023-06-23 23:00 nvdata -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 nvram -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 otp -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 20 2023-06-23 23:00 para -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 persist -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 23 2023-06-23 23:00 preloader_a -> /dev/block/mmcblk0boot0
lrwxrwxrwx 1 root root 23 2023-06-23 23:00 preloader_b -> /dev/block/mmcblk0boot1
lrwxrwxrwx 1 root root 30 2023-06-23 23:00 preloader_emmc_a -> /dev/block/by-name/preloader_a
lrwxrwxrwx 1 root root 30 2023-06-23 23:00 preloader_emmc_b -> /dev/block/by-name/preloader_b
lrwxrwxrwx 1 root root 15 2023-06-23 23:01 preloader_raw_a -> /dev/block/dm-4
lrwxrwxrwx 1 root root 15 2023-06-23 23:01 preloader_raw_b -> /dev/block/dm-5
lrwxrwxrwx 1 root root 30 2023-06-23 23:00 preloader_ufs_a -> /dev/block/by-name/preloader_a
lrwxrwxrwx 1 root root 30 2023-06-23 23:00 preloader_ufs_b -> /dev/block/by-name/preloader_b
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 proinfo -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 20 2023-06-23 23:00 protect1 -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 protect2 -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 scp_a -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 scp_b -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 sec1 -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 seccfg -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 spmfw_a -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 spmfw_b -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 sspm_a -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 sspm_b -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 super -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 tee_a -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 tee_b -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 userdata -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 vbmeta_a -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 vbmeta_b -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 vbmeta_system_a -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 vbmeta_system_b -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 vbmeta_vendor_a -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 vbmeta_vendor_b -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 vendor_boot_a -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 2023-06-23 23:00 vendor_boot_b -> /dev/block/mmcblk0p44
Installation
The Magic Mask for Android
topjohnwu.github.io
the above link is very helpful in giving clarity as to what images you should be using and how to handle separated vbmeta files. In the case of the 11.6 Pro android 11, the vbmeta files are separate and we are booting from the Ramdisk, so we are flashing "boot" and NOT "boot_recovery" or otherwise.
Hook up the device to the PC, enable the developer mode by going into settings > tablet info (at the bottom) > and tap the firmware 7 times or so. Then enable USB debugging.
On linux you just need to install adb on your PC and run:
adb devices
adb reboot bootloader
flasing unlock
fastboot devices
fastboot flashing unlock
fastboot reboot
Boot your tablet into fastboot mode. With the device powered off, hold the Power and Volume Up buttons for several seconds, until a boot mode menu appears on your tablet display. Use Volume Up to navigate to Fastboot Mode and then press Volume Down to select it.
(Mine was already in fastboot for some reason and I thought the screen was frozen, it was NOT. Its just unresponsive. It looked like a menu but fastboot was already selected and all I had to do was move to the next step which was to boot in and install magisk)
1.) Download Magisk from the github page and use adb to install it with:
adb install /path/to/Magisk.apk
2.) Copy local boot image from the firmware zip archive to the tablet device (explicitly called "boot.img" there are a lot of img files so it could be confusing) with:
adb push /path/to/directory/boot.img /sdcard/download
(the path is the relative path to the boot.img file. it could be in the directory that you are in for example and the full relative path would be ./boot.img on linux and .\boot.img\ on windows. You can also do this without the dot slash but it is important to note that you are specifying the path whether you are in the working directory with the files or not. I did it while inside the firmware directory to make it easy)
3.) Open magisk, hit install, patch image and click on the image you pushed to the device in the previous step. This will produce a patched image.
Then use:
adb pull /storage/emulated/0/Download/magisk_patched-26100_[random-string].img .
(the DOT is the current directory) this will copy the image to where your current dir.
Finally run these commands:
adb reboot bootloader
fastboot flash boot ./magisk_patched-26100_peoUE.img
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
NOTE: that this is for the 11.6 Pro with the keyboard. The above github link will help you determine these last two commands. It IS important so please read it. Some devices use boot_recovery or something else and some devices use a different command to flash the vbmeta files based on your configuration. You can use the "adb shell ls -l /dev/block/by-name" command to see if you have separate vbmeta files or not. The above link has more info on this process but this is the general idea.
Note that they keyboard must NOT be connected to the device otherwise it wont be recognized by the PC for USB debugging. To fix the broken wifi, I downloaded the firmware and flashed ALL images listed in /dev/block/by-name and restarted the process. I hope this helps clarify some things for someone out there messing around with niche hardware. Good luck and feel free to ask me questions. I had to learn the hard way, Idk a lot about the topic but I can help guide a little bit. Thanks.