So let me tell you the dumb things I did.
1. I thought I saw an update for TWRP in Tapatalk, so I downloaded it and flashed it in TWRP. Turned out it was for the OnePlus One... Tapatalk didn't sync with my XDA subscribed threads correctly...
2. Rebooted into recovery, and we all know what happened here.
3. No problem, I can use fastboot to flash recovery. Booted into bootloader, and did this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Basically, it saw the device, I tried to flash the TWRP image file, but it got stuck waiting for the phone. That was the last time it ever saw it.
4. Rebooted into Android just fine. Everything work exactly the way they should.
5. I figured the only way I can flash recovery now is by using dd over ADB shell.
6. I grabbed the last log written by the recovery, and found the following information by doing "cat /cache/recovery/last_log":
Code:
/recovery | /dev/block/sde14 | Size: 64MB
Flags: Can_Be_Backed_Up IsPresent Can_Flash_Img
Primary_Block_Device: [B]/dev/block/sde14[/B]
Display_Name: Recovery
Storage_Name: recovery
Backup_Path: /recovery
Backup_Name: recovery
Backup_Display_Name: Recovery
Storage_Path: /recovery
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
[B]<truncated>[/B]
[IMAGE FLASH STARTED]
Image to flash: '/sdcard/Download/TWRP+3.0.3-2-TugaPower.img'
Calculating restore details...
I:Image filename is: TWRP+3.0.3-2-TugaPower.img
I:Reading '/sdcard/Download/TWRP+3.0.3-2-TugaPower.img', writing '[B]/dev/block/sde14[/B]'
[IMAGE FLASH COMPLETED]
I:Set page: 'action_complete'
I:operation_end - status=0
I:Set page: 'clear_vars'
I:Set page: 'flashimage_confirm'
I:Set page: 'clear_vars'
I:Set page: 'install'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'reboot'
I:Set page: 'rebootcheck'
I:Copying file /cache/recovery/log to /cache/recovery/last_log
Rebooting...
I:InfoManager saving '/data/media/0/TWRP/.twrps'
I:Saved settings file values
So the recovery partition is /dev/block/sde14.
7. I first made a backup of the partition just to make sure.
Code:
[email protected]_ii:/ # dd if=/dev/block/sde14 of=/sdcard/badrec.img
dd if=/dev/block/sde14 of=/sdcard/badrec.img
131072+0 records in
131072+0 records out
67108864 bytes transferred in 1.281 secs (52387871 bytes/sec)
8. Then I "flashed" the right TWRP image file.
Code:
[email protected]_ii:/ # dd if=/sdcard/TWRP.img of=/dev/block/sde14
dd if=/sdcard/TWRP.img of=/dev/block/sde14
35824+0 records in
35824+0 records out
18341888 bytes transferred in 1.552 secs (11818226 bytes/sec)
9. I rebooted into recovery, and it worked.
In conclusion, Android and recovery themselves work fine now. I'm just worried because fastboot won't see my device in bootloader. That's a fail-safe that I can't not have. I'm not flashing anything else until I get to the bottom of it.
EDIT: I noticed in the backup section of TWRP, fastboot is listed as having 0 MB. Did it get wiped? I'm not sure how to get it back.
Within Android:
Within TWRP:
Code:
~ # [6nls -al /dev/block/platform/soc
ls -al /dev/block/platform/soc
__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 4 root root 80 Mar 16 1970 .
drwxr-xr-x 3 root root 60 Mar 16 1970 ..
drwxr-xr-x 4 root root 1100 Mar 16 1970 624000.ufshc
drwxr-xr-x 3 root root 100 Mar 16 1970 74a4900.sdhci
~ # [6nls -al /dev/block/platform/soc/624000.ufshc/by-name
ls -al /dev/block/platform/soc/624000.ufshc/by-name
__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 940 Mar 16 1970 .
drwxr-xr-x 4 root root 1100 Mar 16 1970 ..
lrwxrwxrwx 1 root root 16 Mar 16 1970aboot -> /dev/block/sde11
lrwxrwxrwx 1 root root 16 Mar 16 1970 apdp -> /dev/block/sde21
lrwxrwxrwx 1 root root 16 Mar 16 1970 bluetooth -> /dev/block/sde16
lrwxrwxrwx 1 root root 16 Mar 16 1970 boot -> /dev/block/sde12
lrwxrwxrwx 1 root root 15 Mar 16 1970 cache -> /dev/block/sda2
lrwxrwxrwx 1 root root 15 Mar 16 1970 cdt -> /dev/block/sdd2
lrwxrwxrwx 1 root root 16 Mar 16 1970 cmnlib -> /dev/block/sde19
lrwxrwxrwx 1 root root 16 Mar 16 1970 cmnlib64 -> /dev/block/sde20
lrwxrwxrwx 1 root root 15 Mar 16 1970 cryptkey -> /dev/block/sda8
lrwxrwxrwx 1 root root 15 Mar 16 1970 ddr -> /dev/block/sdd3
lrwxrwxrwx 1 root root 15 Mar 16 1970 devcfg -> /dev/block/sda5
lrwxrwxrwx 1 root root 16 Mar 16 1970 devinfo -> /dev/block/sde15
lrwxrwxrwx 1 root root 15 Mar 16 1970 dip -> /dev/block/sde9
lrwxrwxrwx 1 root root 16 Mar 16 1970 dpo -> /dev/block/sde23
lrwxrwxrwx 1 root root 15 Mar 16 1970 dsp -> /dev/block/sde8
lrwxrwxrwx 1 root root 16 Mar 16 1970 echarge -> /dev/block/sde25
lrwxrwxrwx 1 root root 15 Mar 16 1970 [B]fbop -> /dev/block/sda6[/B]
lrwxrwxrwx 1 root root 15 Mar 16 1970 frp -> /dev/block/sda7
lrwxrwxrwx 1 root root 15 Mar 16 1970 fsc -> /dev/block/sdf3
lrwxrwxrwx 1 root root 15 Mar 16 1970 fsg -> /dev/block/sde4
lrwxrwxrwx 1 root root 15 Mar 16 1970 hyp -> /dev/block/sde3
lrwxrwxrwx 1 root root 16 Mar 16 1970 keymaster -> /dev/block/sde18
lrwxrwxrwx 1 root root 15 Mar 16 1970 keystore -> /dev/block/sda4
lrwxrwxrwx 1 root root 16 Mar 16 1970 lksecapp -> /dev/block/sde17
lrwxrwxrwx 1 root root 16 Mar 16 1970 mdtp -> /dev/block/sde10
lrwxrwxrwx 1 root root 15 Mar 16 1970 misc -> /dev/block/sda3
lrwxrwxrwx 1 root root 15 Mar 16 1970 modem -> /dev/block/sde7
lrwxrwxrwx 1 root root 15 Mar 16 1970 modemst1 -> /dev/block/sdf1
lrwxrwxrwx 1 root root 15 Mar 16 1970 modemst2 -> /dev/block/sdf2
lrwxrwxrwx 1 root root 16 Mar 16 1970 msadp -> /dev/block/sde22
lrwxrwxrwx 1 root root 15 Mar 16 1970 persist -> /dev/block/sdf5
lrwxrwxrwx 1 root root 15 Mar 16 1970 pmic -> /dev/block/sde6
lrwxrwxrwx 1 root root 16 Mar 16 1970 recovery -> /dev/block/sde14
lrwxrwxrwx 1 root root 15 Mar 16 1970 reserve -> /dev/block/sdd1
lrwxrwxrwx 1 root root 15 Mar 16 1970 rpm -> /dev/block/sde1
lrwxrwxrwx 1 root root 15 Mar 16 1970 sec -> /dev/block/sde5
lrwxrwxrwx 1 root root 16 Mar 16 1970 splash -> /dev/block/sde24
lrwxrwxrwx 1 root root 15 Mar 16 1970 ssd -> /dev/block/sda1
lrwxrwxrwx 1 root root 16 Mar 16 1970 sti -> /dev/block/sde26
lrwxrwxrwx 1 root root 16 Mar 16 1970 system -> /dev/block/sde13
lrwxrwxrwx 1 root root 15 Mar 16 1970 tz -> /dev/block/sde2
lrwxrwxrwx 1 root root 15 Mar 16 1970 userdata -> /dev/block/sda9
lrwxrwxrwx 1 root root 15 Mar 16 1970 xbl -> /dev/block/sdb1
lrwxrwxrwx 1 root root 15 Mar 16 1970 xblbak -> /dev/block/sdc1
lrwxrwxrwx 1 root root 15 Mar 16 1970 ztecfg -> /dev/block/sdf4
fastboot is now a partition to pick from when I choose an image to flash. Huh? Is that the fbop (/dev/block/sda6) partition? When I run cat on it I still see data on it.
EDIT 2: I see this in the recovery logs:
Code:
/fastboot | /dev/block/sda6 | Size: 0MB
Flags: Can_Be_Backed_Up IsPresent Can_Flash_Img
Primary_Block_Device: /dev/block/sda6
Display_Name: fastboot
Storage_Name: fastboot
Backup_Path: /fastboot
Backup_Name: fastboot
Backup_Display_Name: fastboot
Storage_Path: /fastboot
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
Using dd to grab it gives me a 128 KB image. Seems normal compared to the ones uploaded here. It's mostly empty data, though, it seems.
==========FIXED==========
You're not going to believe this. I think Windows decided to update the ADB device driver right after I plugged it in (refer to the screenshot above where it just stopped working for no reason).
I went into Device Manager and saw this:
Seems normal, right? Well, if I try to update it using Windows' list of known devices, I see these:
I checked afterward; the one that's currently installed is the top one. So, I chose the second one (the supposedly outdated one).
And now we are presented with result.
I hate you, Windows.
Try a different USB port. I had issues with my m8 randomly not picking up my device in fastboot but working from adb on the same port
silverxbv2 said:
Try a different USB port. I had issues with my m8 randomly not picking up my device in fastboot but working from adb on the same port
Click to expand...
Click to collapse
I actually think something happened to my fastboot partition/binary/whatever. Check the bottom of OP.
What model are you using? And what sw version?
I fixed it! See OP for details.
I'm glad you got it working
Good troubleshooting. Glad you got whole again. ..... I also hate Windows
Sent from my Nexus 6 using XDA-Developers mobile app
My believe is not windows problem , is the new software installed on the device, when is detected and have usb debugging enable automatically install or update drivers.
So is part of ZTE doing. But good find
I had almost the same problem, device manager showed only !Android Device in fastboot mode, however, worked nicely in adb. I had to install manually the Google usb driver from here https://developer.android.com/studio/run/win-usb.html#top
<3<3<3<3<3
One thanks button is not enough. You saved me from many hours of failing!!!
Related
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
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!
Hello everyone!
I wonder where can I get/how can I create Device Tree for subject device?
I want to try porting LOS firware from Redmi 4X to ZTE Blade A6 .
Is it ever possible to do?
GPT layout is shown below
Code:
lrwxrwxrwx 1 root root 20 Jan 13 1970 DDR -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 Jan 13 1970 aboot -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 Jan 13 1970 abootbak -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 Jan 13 1970 apdp -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 21 Jan 13 1970 batweak -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 Jan 13 1970 boot -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 Jan 13 1970 cache -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 Jan 13 1970 cmnlib -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 Jan 13 1970 cmnlib64 -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 Jan 13 1970 cmnlib64bak -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 Jan 13 1970 cmnlibbak -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 Jan 13 1970 config -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 Jan 13 1970 devcfg -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 Jan 13 1970 devcfgbak -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 Jan 13 1970 devinfo -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 Jan 13 1970 dip -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 Jan 13 1970 dpo -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 Jan 13 1970 dsp -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 20 Jan 13 1970 factory -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 Jan 13 1970 fsc -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 Jan 13 1970 fsg -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 Jan 13 1970 keymaster -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 21 Jan 13 1970 keymasterbak -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 21 Jan 13 1970 keystore -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 Jan 13 1970 limits -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 Jan 13 1970 logdump -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 Jan 13 1970 mcfg -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 Jan 13 1970 mdtp -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 Jan 13 1970 misc -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 Jan 13 1970 modem -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 Jan 13 1970 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 Jan 13 1970 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 Jan 13 1970 mota -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 Jan 13 1970 msadp -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 Jan 13 1970 oem -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 Jan 13 1970 persist -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 Jan 13 1970 recovery -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 20 Jan 13 1970 rpm -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 Jan 13 1970 rpmbak -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 Jan 13 1970 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 Jan 13 1970 sbl1bak -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 Jan 13 1970 sec -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 Jan 13 1970 splash -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 20 Jan 13 1970 ssd -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 Jan 13 1970 syscfg -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 21 Jan 13 1970 system -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 20 Jan 13 1970 tz -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 Jan 13 1970 tzbak -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 Jan 13 1970 userdata -> /dev/block/mmcblk0p50
lrwxrwxrwx 1 root root 21 Jan 13 1970 ztecfg -> /dev/block/mmcblk0p23
I'm interesting in building device tree from scratch if it's possible to do using "software tools" only.
MIUI10
OK. So, not for the first time, LineageOS has managed to completely knacker my Nexus. It's too long and boring to go into in detail but, basically, the situation I'm left with is:
* I can access the device through fastboot
* I can boot TWRP through fastboot
* I can flash Boot & System images
However, I can't install TWRP [or any recovery] for that matter because it seems my Recovery partition has vanished. If I try to flash any Recovery, I get:
````
fastboot flash recovery /path/to/recovery.img
Sending 'recovery' (7598 KB) OKAY [ 0.280s]
Writing 'recovery' FAILED (remote: 'partition table doesn't exist')
````
Same with Data partition. When I boot into TWRP it's showing as 0mb. I've tried the usual tricks of formatting it [from TWRP and Fastboot] but I get 'unable to mount storage' or [from Fastboot] that 'partition table doesn't exist' message again.
I've also tried the trick of changing the format of Data from ext4 to ext2 and back. That just produces the 'unable to mount storage' error again and doesn't do anything.
I've also tried:
```
ls -al /dev/block/platform/msm_sdcc.1/by-name
```
and I don't even seem to have a [user]data or recovery partition any more:
````
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
drwxr-xr-x 2 root root 600 Jan 27 19:06 .
drwxr-xr-x 4 root root 680 Jan 27 19:06 ..
lrwxrwxrwx 1 root root 21 Jan 27 19:06 DDR -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 Jan 27 19:06 aboot -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 Jan 27 19:06 abootb -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 Jan 27 19:06 boot -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 Jan 27 19:06 cache -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 20 Jan 27 19:06 fsg -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 Jan 27 19:06 m9kefs1 -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 Jan 27 19:06 m9kefs2 -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 Jan 27 19:06 m9kefs3 -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 Jan 27 19:06 m9kefsc -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 Jan 27 19:06 metadata -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 Jan 27 19:06 misc -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 20 Jan 27 19:06 modemst1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 Jan 27 19:06 modemst2 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 Jan 27 19:06 pad -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 20 Jan 27 19:06 persist -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 Jan 27 19:06 radio -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 Jan 27 19:06 rpm -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 Jan 27 19:06 rpmb -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 20 Jan 27 19:06 sbl1 -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 Jan 27 19:06 sbl2 -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 Jan 27 19:06 sbl2b -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 Jan 27 19:06 sbl3 -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 Jan 27 19:06 sbl3b -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 Jan 27 19:06 ssd -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 Jan 27 19:06 system -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 Jan 27 19:06 tz -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 Jan 27 19:06 tzb -> /dev/block/mmcblk0p21
````
So where can I go from here. Everything I've found online says to flash stock ROM or reflash stock recovery.... etc. etc.
But how can I flash anything when the partitions don't actually exist and I just get 'FAILED (remote: 'partition table doesn't exist')' if I try to do anything with any of those partitions?
Is there anyway I can completely wipe the partition table on the device and set it up again from scratch? I'm not worried about loss of data or anything else. I've everything backed up. But I just need to <somehow> recreate my /data partition [at least] so I can write to the damned thing.
BTW --I had the device repartitioned 'flox' and I believe that LineageOS has encrypted the /data partition, which is why TWRP can't see it. I've tried running 'decrypt' from TWRP but get a 'command not found' error. I understand that this is because the 'decrypt' command only works with TWRP actually installed on the device, not when remote booted via fastboot. And I can't install it on the device because I have no recovery partition!
Similarly, I can actually boot to stock system but am presented with a dialogue asking me to enter my password to decrypt the device. When I do so, I get a message saying [from memory] something along the lines of "The password you entered was correct but your data is corrupted" with a button to do a factory reset. However, when I hit this, the phone just reboots into fastboot again.
Apparently the fix for this is to have the stock recovery flashed, so the factory reset will work. But, again, I have no recovery partition so can't flash stock recovery!
I've been going round in circles with this all afternoon and am on the verge of taking a sledge-hammer to the damned thing. Please someone tell me there's a way to force repartition my Nexus so I can start from scratch again.
Phew! --well, as is so often the case, after spending a day in frustration and getting nowhere and then posting a thread on XDA, I may have belatedly stumbled on a [at least partial] solution:
[Guide] Repartition Nexus7(2013) to increase system partition - Extra Space for Rom
Hi, this is my first time posting here. I noticed there is no guide to increase the system partition size in Nexus 7 (2013). The system partition is only around 880MB making it impossible to flash new ROMs and large package of GApps. This guide...
forum.xda-developers.com
Using the info in the above thread, I was able to use parted to recreate my /recovery and /userdata partitions. I'm still not home and dry yet as my Nexus is still not happy about installing any ROMs. But at least I've got a basis to work from here!
xxxmadraxxx said:
Phew! --well, as is so often the case, after spending a day in frustration and getting nowhere and then posting a thread on XDA, I may have belatedly stumbled on a [at least partial] solution:
[Guide] Repartition Nexus7(2013) to increase system partition - Extra Space for Rom
Hi, this is my first time posting here. I noticed there is no guide to increase the system partition size in Nexus 7 (2013). The system partition is only around 880MB making it impossible to flash new ROMs and large package of GApps. This guide...
forum.xda-developers.com
Using the info in the above thread, I was able to use parted to recreate my /recovery and /userdata partitions. I'm still not home and dry yet as my Nexus is still not happy about installing any ROMs. But at least I've got a basis to work from here!
Click to expand...
Click to collapse
got the same prob
any solutiotn?
I did get it sorted in the end. Here are the notes I saved at the time. Excuse the swearing but these were made for my own future reference and not for public consumption:
-----------------------------------------------------
Too long and boring to go into details but, basically Lineage-****ing-OS completely arse-****ed my Nexus: no /data partition nor /recovery partition. Tried every trick in the book to try and fix it, but nothing that used fastboot or TWRP [booted from fastboot] did **** all. In the end, the answer was to install parted on the Nexus. [ Downloaded from: iwf1.com/iwf-repo/parted.rar ] and use that to rewrite the partitioning map]. All from this thread:
[Guide] Repartition Nexus7(2013) to increase system partition - Extra Space for Rom
Hi, this is my first time posting here. I noticed there is no guide to increase the system partition size in Nexus 7 (2013). The system partition is only around 880MB making it impossible to flash new ROMs and large package of GApps. This guide...
forum.xda-developers.com
````
adb push parted /
adb shell
~ # chmod +x parted
~ # /parted /dev/block/mmcblk0
(parted): unit b
(parted): p
````
This was the guy in the thread’s partition map. Mine was almost the same, except my Block 25 was unnamed [so had to rename it to ‘recovery’] and I didn’t have a ‘userdata’ block at all:
````
Number Start End Size File system Name Flags
1 67108864B 156745727B 89636864B fat16 radio
2 201326592B 204472319B 3145728B modemst1
3 204472320B 207618047B 3145728B modemst2
4 268435456B 283795455B 15360000B ext4 persist
5 335544320B 336343039B 798720B m9kefs1
6 336343040B 337141759B 798720B m9kefs2
7 402653184B 403451903B 798720B m9kefs3
8 403451904B 406597631B 3145728B fsg
9 469762048B 471298047B 1536000B sbl1
10 471298048B 472834047B 1536000B sbl2
11 472834048B 474931199B 2097152B sbl3
12 474931200B 480174079B 5242880B aboot
13 480174080B 480698367B 524288B rpm
14 536870912B 553648127B 16777216B boot
15 603979776B 604504063B 524288B tz
16 604504064B 604505087B 1024B pad
17 604505088B 606041087B 1536000B sbl2b
18 606041088B 608138239B 2097152B sbl3b
19 608138240B 613381119B 5242880B abootb
20 613381120B 613905407B 524288B rpmb
21 613905408B 614429695B 524288B tzb
22 671088640B 1551892479B 880803840B ext2 system
23 1551892480B 2139095039B 587202560B ext4 cache
24 2147483648B 2148532223B 1048576B misc
25 2214592512B 2225078271B 10485760B recovery
26 2281701376B 2281709567B 8192B DDR
27 2281709568B 2281717759B 8192B ssd
28 2281717760B 2281718783B 1024B m9kefsc
29 2348810240B 2348843007B 32768B metadata
30 2415919104B 31272713727B 28856794624B ext4 userdata
````
````
(parted) name 25 recovery
(parted): rm 30 —might have to unmount it in shell if it’s busy
(parted): mkpart primary 2415919104B 100% —I used 100% instead of a stated block as he had, as I got an error about going past the end of the available space
(parted) name 30 system
(parted) p
(parted) quit
````
—then in adb shell again:
````
~ # mke2fs -b 4096 -T ext4 /dev/block/mmcblk0p30
~ # /parted /dev/block/mmcblk0 p
````
need to reboot [bootloader] to make fstab update partition table.
That at least gave me a recovery and data partitions. Though I’m still wrestling to restore any kind of OS on them.
Please kick me hard in the bollox if I ever even look at lineageOS again!
Click to expand...
Click to collapse
-----------------------------------------------------
I can't remember exactly what I did to install an OS afterwards. I didn't make any more notes, so I assuming it wasn't *too* traumatic. Just getting the partitions restored and available to install anything on is the biggest hurdle!
Hey... So Im trying to boot/flash a Custom recovery for my Xperia XZ2 however It doesnt have a recovery... The reason I suspect this is when I try to boot to recovery via the button combo or ADB... It cycles once and on the next cycle it returns to the main phone screen. I never see a recovery screen and trying to boot a recovery.img just returns this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How screwed am I?
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.