Hi guys.
I'm an ArchLinux user and was quite disappointed to see we needed to use a Windows-based software in order to replace some partitions. This reminded me the old ages of Odin on Samsung devices, when Heimdall didn't exist yet. I initially posted my tutorial on the Elephone forums, but the latter is really buggy and trying to format the command properly does not give the expected result, seeing HTML code inserted everywhere.
Just to let you know. If you are using a UNIX based system like OS X or a GNU/Linux distribution, or if simply do not want to use the piece of software specified above. You have to know that all features implemented in the Flash Tool can be made manually. Here is a tutorial in that regard:
Please make sure Settings -> Developer options -> USB debogging is enabled. This should be the case by default, using the stock ROM or with a brand new P7000 device.
Install adb with one of the method for your OS.
In a terminal, type
Code:
adb shell
You should get a prompt like this
Code:
[email protected]_jbaol_3m_fhd_elephone:/ #
NOTE: The serial number is by default 0123456789ABCDEFG. It seems Elephone just too the SoC from MediaTek without even changing the serial number. You will thus have a problem if you connect several P7000 devices to the same computer. adb uses indeed that number to differentiate which device send commands to, with the following adb command:
Code:
adb -s 0123456789ABCDEFG shell
The recovery should be on the partition number 8. Check that by typing:
Code:
/dev/block/platform/mtk-msdc.0/by-name/
In the result, you should see a line with:
Code:
lrwxrwxrwx root root 2015-07-10 16:34 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-07-10 16:34 cache -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-07-10 16:34 expdb -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-07-10 16:34 flashinfo -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-07-10 16:34 lk -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-07-10 16:34 logo -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-07-10 16:34 metadata -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-07-10 16:34 nvram -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-07-10 16:34 para -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-07-10 16:34 proinfo -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-07-10 16:34 protect1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-07-10 16:34 protect2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-07-10 16:34 recovery -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-07-10 16:34 seccfg -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-07-10 16:34 secro -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-07-10 16:34 system -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-07-10 16:34 tee1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-07-10 16:34 tee2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-07-10 16:34 userdata -> /dev/block/mmcblk0p18
Which confirms the assumptions.
Now, make a backup of the original recovery if anything goes wrong. First we are gonna dump the partition content to the sdcard emulated location (even if you do not have a SD card, that location is present). Type:
Code:
dd if=/dev/block/mmcblk0p8 of=/sdcard/recovery_backup.img
To pull that file to your computer, open a new terminal on your computer, change dir to the location you want the backup saved in and type:
Code:
adb pull /sdcard/recovery_backup.img
Now, download the RAR archive from Elephone. Extract it. In the folder "SuperSU/p7000-recovery/", you can find the file recovery.img. Send that file to your device with adb, by typing still in a terminal on your computer:
Code:
adb push ./recovery.img /sdcard/recovery.img
Now you just need to replace the recovery with the file now on your phone.
Code:
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p8
This should have been copied with successful and you see this result appearing on the screen:
Code:
19720+0 records in
19720+0 records out
10096640 bytes transferred in 1.336 secs (7557365 bytes/sec)
Now you just need to reboot to the recovery to make sure the process worked flawlessly. From your computer type,
Code:
adb reboot recovery
or shut down the device manually, and boot it up pressing and holding the power and volume up buttons.
Hope this helps. My 2 cents.
Related
I have unlocked my Australian xt1572 and booted twrp with the following command:
fastboot boot twrp.img
Then I made a nandroid backup selecting all the options apart from /data
Does this backup my original modem as a part of the backup or is there a specific way to back up my modem from twrp?
I want to make sure that I can revert back to stock (Vodafone) so I can return to original state by restoring the nandroid backup i made and apply the 6.0 ota when its get released down here.
-Ivar
This is something I am trying to find out as well. Anyone able to confirm it?
ivaho said:
I have unlocked my Australian xt1572 and booted twrp with the following command:
fastboot boot twrp.img
Then I made a nandroid backup selecting all the options apart from /data
Does this backup my original modem as a part of the backup or is there a specific way to back up my modem from twrp?
I want to make sure that I can revert back to stock (Vodafone) so I can return to original state by restoring the nandroid backup i made and apply the 6.0 ota when its get released down here.
-Ivar
Click to expand...
Click to collapse
LBSpeller said:
This is something I am trying to find out as well. Anyone able to confirm it?
Click to expand...
Click to collapse
Run "ls -al /dev/block/bootdevice/by-name" in TWRP's terminal or ADB while in TWRP.
You need root if you want to run this command while in Android with USB debugging on.
Look for modem, fsg, modemst1, and modemst2.
Once you find them, make note of the blocks.
For example, here are the partitions of the Pure Edition:
ls -al /dev/block/bootdevice/by-name
DDR -> /dev/block/mmcblk0p4
aboot -> /dev/block/mmcblk0p5
abootBackup -> /dev/block/mmcblk0p12
bluetooth -> /dev/block/mmcblk0p18
boot -> /dev/block/mmcblk0p36
cache -> /dev/block/mmcblk0p46
carrier -> /dev/block/mmcblk0p45
cid -> /dev/block/mmcblk0p26
clogo -> /dev/block/mmcblk0p32
customize -> /dev/block/mmcblk0p43
dhob -> /dev/block/mmcblk0p23
frp -> /dev/block/mmcblk0p33
fsc -> /dev/block/mmcblk0p25
fsg -> /dev/block/mmcblk0p24
hob -> /dev/block/mmcblk0p22
hyp -> /dev/block/mmcblk0p9
hypBackup -> /dev/block/mmcblk0p15
keystore -> /dev/block/mmcblk0p42
kpan -> /dev/block/mmcblk0p35
limits -> /dev/block/mmcblk0p30
logo -> /dev/block/mmcblk0p31
logs -> /dev/block/mmcblk0p29
logs-charging -> /dev/block/mmcblk0p39
metadata -> /dev/block/mmcblk0p28
misc -> /dev/block/mmcblk0p27
modem -> /dev/block/mmcblk0p1
modemst1 -> /dev/block/mmcblk0p20
modemst2 -> /dev/block/mmcblk0p21
oem -> /dev/block/mmcblk0p44
padA -> /dev/block/mmcblk0p11
padB -> /dev/block/mmcblk0p19
padC -> /dev/block/mmcblk0p40
persist -> /dev/block/mmcblk0p34
pmic -> /dev/block/mmcblk0p2
pmicBackup -> /dev/block/mmcblk0p17
recovery -> /dev/block/mmcblk0p37
rpm -> /dev/block/mmcblk0p6
rpmBackup -> /dev/block/mmcblk0p13
sbl1 -> /dev/block/mmcblk0p3
sdi -> /dev/block/mmcblk0p8
sp -> /dev/block/mmcblk0p41
ssd -> /dev/block/mmcblk0p38
system -> /dev/block/mmcblk0p47
tz -> /dev/block/mmcblk0p7
tzBackup -> /dev/block/mmcblk0p14
userdata -> /dev/block/mmcblk0p48
utags -> /dev/block/mmcblk0p10
utagsBackup -> /dev/block/mmcblk0p16
Click to expand...
Click to collapse
"modem" = /dev/block/mmcblk0p1
"fsg" = /dev/block/mmcblk0p24
"modemst1" = /dev/block/mmcblk0p20
"modemst2" = /dev/block/mmcblk0p21
To back them up in Terminal:
For modem: dd if=/dev/block/mmcblk0p1 of=/sdcard/NON-HLOS.bin
For modemst1: dd if=/dev/block/mmcblk0p20 of=/sdcard/modemst1
For modemst2: /dev/block/mmcblk0p21 of=/sdcard/modemst2
For fsg: dd if=/dev/block/mmcblk0p1 of=/sdcard/fsg.mbn
Check on your internal storage for those files and save them somewhere.
Spasticdroid said:
Run "ls -al /dev/block/bootdevice/by-name" in TWRP's terminal or ADB while in TWRP.
You need root if you want to run this command while in Android with USB debugging on.
Look for modem, fsg, modemst1, and modemst2.
Once you find them, make note of the blocks.
Click to expand...
Click to collapse
Guess I am out of luck then since I already have installed the indian MM modem :crying:
But luckily the phone works great with this version of mm so at least I dont have a brick
SpasilliumNexus said:
Run "ls -al /dev/block/bootdevice/by-name" in TWRP's terminal or ADB while in TWRP.
You need root if you want to run this command while in Android with USB debugging on.
Look for modem, fsg, modemst1, and modemst2.
Once you find them, make note of the blocks.
For example, here are the partitions of the Pure Edition:
"modem" = /dev/block/mmcblk0p1
"fsg" = /dev/block/mmcblk0p24
"modemst1" = /dev/block/mmcblk0p20
"modemst2" = /dev/block/mmcblk0p21
To back them up in Terminal:
For modem: dd if=/dev/block/mmcblk0p1 of=/sdcard/NON-HLOS.bin
For modemst1: dd if=/dev/block/mmcblk0p20 of=/sdcard/modemst1
For modemst2: /dev/block/mmcblk0p21 of=/sdcard/modemst2
For fsg: dd if=/dev/block/mmcblk0p1 of=/sdcard/fsg.mbn
Check on your internal storage for those files and save them somewhere.
Click to expand...
Click to collapse
How can I restore modem which is backed up in TWRP?
I am currently running CM 12.1
(Used CM13 with RazorKernel For some days which had a bootlogo)
Here's the partition info of our device
Code:
lrwxrwxrwx root root 2016-01-11 17:56 DDR -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2016-01-11 17:56 aboot -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2016-01-11 17:56 abootbak -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2016-01-11 17:56 boot -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2016-01-11 17:56 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2016-01-11 17:56 config -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2016-01-11 17:56 fsc -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2016-01-11 17:56 fsg -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2016-01-11 17:56 hyp -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2016-01-11 17:56 hypbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2016-01-11 17:56 keystore -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2016-01-11 17:56 misc -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2016-01-11 17:56 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2016-01-11 17:56 modemst1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2016-01-11 17:56 modemst2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2016-01-11 17:56 oem -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 2016-01-11 17:56 pad -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2016-01-11 17:56 persist -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2016-01-11 17:56 recovery -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2016-01-11 17:56 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2016-01-11 17:56 rpmbak -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2016-01-11 17:56 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2016-01-11 17:56 sbl1bak -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2016-01-11 17:56 sec -> /dev/block/mmcblk0p21
[COLOR="Red"]lrwxrwxrwx root root 2016-01-11 17:56 splash -> /dev/block/mmcblk0p18[/COLOR]
lrwxrwxrwx root root 2016-01-11 17:56 ssd -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2016-01-11 17:56 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2016-01-11 17:56 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2016-01-11 17:56 tzbak -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2016-01-11 17:56 userdata -> /dev/block/mmcblk0p30
As you can see "mmcblk0p18" belongs to splash partiton.
I was successful in dumping splash.img on sdcard with adb shell as:
Code:
dd if=/dev/block/mmcblkp018 of=/storage/sdcard1/splash.img
But now what?
How to edit it?
I've searched for many hours but came up with mediatek or HTC guides which is pretty annoying -_-
Tools I've tried so far--> Android Kitchen, Kernel Kitchen, Logo Builder, nbimg tool.
Please help me through this.. I desperately want to make a splash image for my device.
noobpremium said:
I am currently running CM 12.1
(Used CM13 with RazorKernel For some days which had a bootlogo)
Here's the partition info of our device
Code:
lrwxrwxrwx root root 2016-01-11 17:56 DDR -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2016-01-11 17:56 aboot -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2016-01-11 17:56 abootbak -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2016-01-11 17:56 boot -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2016-01-11 17:56 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2016-01-11 17:56 config -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2016-01-11 17:56 fsc -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2016-01-11 17:56 fsg -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2016-01-11 17:56 hyp -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2016-01-11 17:56 hypbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2016-01-11 17:56 keystore -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2016-01-11 17:56 misc -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2016-01-11 17:56 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2016-01-11 17:56 modemst1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2016-01-11 17:56 modemst2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2016-01-11 17:56 oem -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 2016-01-11 17:56 pad -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2016-01-11 17:56 persist -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2016-01-11 17:56 recovery -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2016-01-11 17:56 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2016-01-11 17:56 rpmbak -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2016-01-11 17:56 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2016-01-11 17:56 sbl1bak -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2016-01-11 17:56 sec -> /dev/block/mmcblk0p21
[COLOR="Red"]lrwxrwxrwx root root 2016-01-11 17:56 splash -> /dev/block/mmcblk0p18[/COLOR]
lrwxrwxrwx root root 2016-01-11 17:56 ssd -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2016-01-11 17:56 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2016-01-11 17:56 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2016-01-11 17:56 tzbak -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2016-01-11 17:56 userdata -> /dev/block/mmcblk0p30
As you can see "mmcblk0p18" belongs to splash partiton.
I was successful in dumping splash.img on sdcard with adb shell as:
Code:
dd if=/dev/block/mmcblkp018 of=/storage/sdcard1/splash.img
But now what?
How to edit it?
I've searched for many hours but came up with mediatek or HTC guides which is pretty annoying -_-
Tools I've tried so far--> Android Kitchen, Kernel Kitchen, Logo Builder, nbimg tool.
Please help me through this.. I desperately want to make a splash image for my device.
Click to expand...
Click to collapse
Which splash? Mi Logo splash? Tux Logo splash? Razor kernel splash I assume? If its Tux Logo splash, it is needed for some LCD types to work. For Mi Logo / Razor kernel splash I think, you must edit in kernel level and compile the kernel yourself.
I want to modify bootsplash too but im soo noob to do that,
Never tried by myself, as your reference, try it at your own risk: https://www.codeaurora.org/cgit/quic/la/device/qcom/common/tree/display/logo?h=LA.BR.1.2.7_rb1.1
nick37332001 said:
Which splash? Mi Logo splash? Tux Logo splash? Razor kernel splash I assume? If its Tux Logo splash, it is needed for some LCD types to work. For Mi Logo / Razor kernel splash I think, you must edit in kernel level and compile the kernel yourself.
Click to expand...
Click to collapse
Damn I dont have time to download sources and compile the kernel myself
Any other method to edit?
And yes its razor kernel splash (which is that blue thing ) or The Mi logo splash which appears before bootanimation.
But the thing is razor kernel had its splash and Kuma's cm12.1 dont!
Just that default "Linux's Penguin" appears in corner :3
Hope you got what I wanted to say
ketut.kumajaya said:
Never tried by myself, as your reference, try it at your own risk: https://www.codeaurora.org/cgit/quic/la/device/qcom/common/tree/display/logo?h=LA.BR.1.2.7_rb1.1
Click to expand...
Click to collapse
Okay Thanks for the reply. That's from kernel source I assume.
However I'll see to it
ketut.kumajaya said:
Never tried by myself, as your reference, try it at your own risk: https://www.codeaurora.org/cgit/quic/la/device/qcom/common/tree/display/logo?h=LA.BR.1.2.7_rb1.1
Click to expand...
Click to collapse
Too bad but I romoved ubuntu from pc just 2 dyas ago.. one more reason to regret -_-
maybe nick can do it :3
BTW any other method to do it? Like using cygwin?
noobpremium said:
Okay Thanks for the reply. That's from kernel source I assume.
However I'll see to it
Click to expand...
Click to collapse
Have you tried the latest version? I think kiran removed the logo
nick37332001 said:
Have you tried the latest version? I think kiran removed the logo
Click to expand...
Click to collapse
I dont want to flash CM13 now. I'm on 12.1.
Leave razorkernel. I'm not talking about 'only' razorkernel. If he is able to do so others should be too and for defferent kernel.
I've seen threads for bootlogo for motoX etc running lollipop
Anyways, do you have ubuntu? so you can run the script Kuma gave us link of.
noobpremium said:
I dont want to flash CM13 now. I'm on 12.1.
Leave razorkernel. I'm not talking about 'only' razorkernel. If he is able to do so others should be too and for defferent kernel.
I've seen threads for bootlogo for motoX etc running lollipop
Anyways, do you have ubuntu? so you can run the script Kuma gave us link of.
Click to expand...
Click to collapse
the script is python so you should be able to run it on windows.
nick37332001 said:
the script is python so you should be able to run it on windows.
Click to expand...
Click to collapse
Okay I'm nooob man. I didn't know that i can run it on windows, but I'll see to it.
Sent from my 2014818 using Tapatalk
nick37332001 said:
the script is python so you should be able to run it on windows.
Click to expand...
Click to collapse
Okay now here I am, successfully running that script on windows.
It created splash.img successfully but it was too small in size, around 65 KB :|
The one that i dumped was exactly 10MB.
Then also I flashed it but what I got was dessorted Mi logo and the same Penguin.
Now what? I'll see if I can decompile splash.img that I dumped using PIL.
Any help will be appreciated
Sent from my 2014818 using Tapatalk
You can give a try with Android Image Kitchen.....
Lennoard said:
You can give a try with Android Image Kitchen.....
Click to expand...
Click to collapse
Okay I'll see
Sent from my Xiaomi Redmi 2
noobpremium said:
Okay I'll see
Sent from my Xiaomi Redmi 2
Click to expand...
Click to collapse
Sorry for digging up old thread but how did it go? Did you manage to change default splashscreen?
What ive done myself so far was use X-Plore app with SuperSU access to copy splash file from /root/dev/block/bootdevice/by-name to external SD. In X-Plore splash file was 0b but upon copy it was 10MB.
Then i tried to use tool from other topic nbimg to convert splashscreen from 'unknown' format to BMP but result was bad. The tool is supposed to identify image resolution but it didnt know how in Redmi case (tool was orignally designed for HTC device i think) so i tried using w1280 h720 argument but result was like below:
http://i.imgur.com/sxYl65J.png
Well then i timply took any 720x720 image and used that nbimg tool to convert it to splash and then tried to replace it in /root/dev/block/bootdevice/by-name but on reboot it was reverted back to original
KonradIC13 said:
Sorry for digging up old thread but how did it go? Did you manage to change default splashscreen?
What ive done myself so far was use X-Plore app with SuperSU access to copy splash file from /root/dev/block/bootdevice/by-name to external SD. In X-Plore splash file was 0b but upon copy it was 10MB.
Then i tried to use tool from other topic nbimg to convert splashscreen from 'unknown' format to BMP but result was bad. The tool is supposed to identify image resolution but it didnt know how in Redmi case (tool was orignally designed for HTC device i think) so i tried using w1280 h720 argument but result was like below:
http://i.imgur.com/sxYl65J.png
Well then i timply took any 720x720 image and used that nbimg tool to convert it to splash and then tried to replace it in /root/dev/block/bootdevice/by-name but on reboot it was reverted back to original
Click to expand...
Click to collapse
No problem for digging old thread.
I did all the things exactly as what you did and had same results.
I still desperately want to make bootlogos for our belowed wt88047 but I just can't @ketut.kumajaya please just one hint for us and we will figure out rest.
I tried that python script on windows too but same broken splash.
Sent from my 2014818 using Tapatalk
@noobpremium @KonradIC13
[GUIDE] How to Create Custom Splash Screen (Boot Logo) for Redmi 2
No need to edit kernel.. The kernel has the logo that displays after Mi Boot Logo..
The boot logo (splash screen) is present in a separate partition..
GokulNC said:
@noobpremium @KonradIC13
[GUIDE] How to Create Custom Splash Screen (Boot Logo) for Redmi 2
No need to edit kernel.. The kernel has the logo that displays after Mi Boot Logo..
The boot logo (splash screen) is present in a separate partition..
Click to expand...
Click to collapse
What did you do exactly?
I'll have a look at your stuff and try it right now.
Seems you posted the thread just a while ago.
Sent from my 2014818 using Tapatalk
TWRP for backing up splash
noobpremium said:
What did you do exactly?
I'll have a look at your stuff and try it right now.
Seems you posted the thread just a while ago.
Sent from my 2014818 using Tapatalk
Click to expand...
Click to collapse
Can I try the batman logo.bin file inside the zip I pointed you to, through this method?
Also, will taking a Backup through recovery work for this, or do I have to flash the whole fastbot ROM if this fails?
.
P.S - Found this, but am reluctant to try, as I have office in an hour. (Will it work if I have MM 6.0.1 installed as Primary ROM? As is says for KK in that thread)
http://en.miui.com/thread-114090-1-1.html
EDIT - Or will this be more relevant -
http://en.miui.com/thread-249552-1-1.html
shanx_verma said:
Can I try the batman logo.bin file inside the zip I pointed you to, through this method?
Also, will taking a Backup through recovery work for this, or do I have to flash the whole fastbot ROM if this fails?
.
P.S - Found this, but am reluctant to try, as I have office in an hour. [emoji14] [emoji14] (Will it work if I have MM 6.0.1 installed as Primary ROM? As is says for KK in that thread)
http://en.miui.com/thread-114090-1-1.html
EDIT - Or will this be more relevant -
http://en.miui.com/thread-249552-1-1.html
Click to expand...
Click to collapse
Just use his tool no need of any flashable zip or something.
Sorry I didn't get time for your batman logo. I'll try tonight.
Btw, you can make your logo easily with that tool.
After it's compiled, flash is with terminal emulator or just fastboot command
"fastboot flash splash splash.img" and done.
Sent from my 2014818 using Tapatalk
I have a Korean Galaxy S4, model number SHV-E330S. Copied the TWRP recovery.img to /dev/block/mmcblk0p10 but it turned out that 0p10 is the "param" partition, so now the phone cannot connect to cellular network, it shows the circle icon with strike-through. The phone still shows the correct IMEI number when dialing *#06#, and it can connect to wifi networks. Also can boot into recovery mode and wiping the system does not help.
Is there any way to make my phone work?
A bit more context of what I did:
Tried to install cyanogenmod on the phone, but it failed with "Signature verification failed". I thought it is because the stock recovery does not allow to install 3rd party roms.
So I tried to install CWM/TWRP recovery on it using ODIN3 when the phone was in download mode. It did not work, could not boot into CWM, it always started the stock recovery. I saw in the install guides that I can copy the recovery image to the phone with dd if I have root.
So I rooted it with this. It worked. Then I followed the instructions here (came from this site) and executed dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p10
This website did not talk about creating a backup of that partition first, so I did not do that. The cellular network probably stopped working at this point, but I only noticed it later.
The partitions on my phone:
[email protected]:/ # ls -l /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root root 1970-01-02 00:00 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-02 00:00 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-02 00:00 backup -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-02 00:00 boot -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-02 00:00 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-02 00:00 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-02 00:00 ddr -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-02 00:00 efs -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-02 00:00 fota -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-02 00:00 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-02 00:00 fsg -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-02 00:00 hidden -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-02 00:00 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-02 00:00 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-02 00:00 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-02 00:00 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-02 00:00 param -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-02 00:00 persdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-02 00:00 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-02 00:00 recovery -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-02 00:00 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-02 00:00 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-02 00:00 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-02 00:00 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-02 00:00 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-02 00:00 userdata -> /dev/block/mmcblk0p26
[email protected]:/ #
Would it work if I copy the /dev/block/mmcblk0p10 partition from an other phone? What is on the param partition?
sullerandras said:
I have a Korean Galaxy S4, model number SHV-E330S. Copied the TWRP recovery.img to /dev/block/mmcblk0p10 but it turned out that 0p10 is the "param" partition, so now the phone cannot connect to cellular network, it shows the circle icon with strike-through. The phone still shows the correct IMEI number when dialing *#06#, and it can connect to wifi networks. Also can boot into recovery mode and wiping the system does not help.
Is there any way to make my phone work?
A bit more context of what I did:
Tried to install cyanogenmod on the phone, but it failed with "Signature verification failed". I thought it is because the stock recovery does not allow to install 3rd party roms.
So I tried to install CWM/TWRP recovery on it using ODIN3 when the phone was in download mode. It did not work, could not boot into CWM, it always started the stock recovery. I saw in the install guides that I can copy the recovery image to the phone with dd if I have root.
So I rooted it with this. It worked. Then I followed the instructions here (came from this site) and executed dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p10
This website did not talk about creating a backup of that partition first, so I did not do that. The cellular network probably stopped working at this point, but I only noticed it later.
The partitions on my phone:
[email protected]:/ # ls -l /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root root 1970-01-02 00:00 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-02 00:00 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-02 00:00 backup -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-02 00:00 boot -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-02 00:00 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-02 00:00 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-02 00:00 ddr -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-02 00:00 efs -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-02 00:00 fota -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-02 00:00 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-02 00:00 fsg -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-02 00:00 hidden -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-02 00:00 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-02 00:00 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-02 00:00 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-02 00:00 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-02 00:00 param -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-02 00:00 persdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-02 00:00 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-02 00:00 recovery -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-02 00:00 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-02 00:00 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-02 00:00 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-02 00:00 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-02 00:00 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-02 00:00 userdata -> /dev/block/mmcblk0p26
[email protected]:/ #
Would it work if I copy the /dev/block/mmcblk0p10 partition from an other phone? What is on the param partition?
Click to expand...
Click to collapse
If you're rooted you can use the app Flashify to flash the recovery.img. I recommend TWRP though.
GDReaper said:
If you're rooted you can use the app Flashify to flash the recovery.img. I recommend TWRP though.
Click to expand...
Click to collapse
Thanks. But it is too late for that, isn't it? The phone is kind of bricked, and flashing a TWRP recovery will not magically unbrick it, right?
sullerandras said:
Thanks. But it is too late for that, isn't it? The phone is kind of bricked, and flashing a TWRP recovery will not magically unbrick it, right?
Click to expand...
Click to collapse
How is it bricked?
From what I understood, you don't have signal anymore, but other than that the phone works.
But you are right, flashing a recovery won't make your signal come back, but maybe flashing a modem will.
The param partition is setting where the boot images are stored, from what I've taken in other threads.
GDReaper said:
How is it bricked?
From what I understood, you don't have signal anymore, but other than that the phone works.
But you are right, flashing a recovery won't make your signal come back, but maybe flashing a modem will.
The param partition is setting where the boot images are stored, from what I've taken in other threads.
Click to expand...
Click to collapse
As I described in the first message in the thread, I accidentally overwrote the mmcblk0p10 partition which is the "param" partition. Since that the phone cannot connect to cellular network, so cannot make phone calls, cannot receive sms and cannot connect to LTE.
But it shows the correct "IMEI" and the correct "Baseband version" in Settings / About device. It can also connect to wifi network, so I can install/update apps and play games.
I downloaded the stock ROM from samsung-update.com: SKT-E330SKSUCNJ1-20141015090913.zip. It is 1.7GB and it took almost 24 hours to download.
I installed this ROM on the phone with ODIN but it did not help. So the problem is probably not with the "modem" partition since it was overwritten by the stock rom.
And found some details about the param partition here:
PARAM: This is the Parameter partition which contains a number of parameters,
variables and settings of the hardware. Apparently it has an 88 byte header
structure that tell us if the MODEMST1 and MODEMST2 have been backed up to the
FSG and BACKUP partitions, respectively. Furthermore it contain all the debug
settings (DLOW/DMID/DHIG etc), the "triangle" status of whether or not you have
flashed custom ROMs and the flash count (0x3FFE00). Current boot mode in use,
and much more. The info about this partition could easily occupy a book by
itself.
Click to expand...
Click to collapse
sullerandras said:
As I described in the first message in the thread, I accidentally overwrote the mmcblk0p10 partition which is the "param" partition. Since that the phone cannot connect to cellular network, so cannot make phone calls, cannot receive sms and cannot connect to LTE.
But it shows the correct "IMEI" and the correct "Baseband version" in Settings / About device. It can also connect to wifi network, so I can install/update apps and play games.
I downloaded the stock ROM from samsung-update.com: SKT-E330SKSUCNJ1-20141015090913.zip. It is 1.7GB and it took almost 24 hours to download.
I installed this ROM on the phone with ODIN but it did not help. So the problem is probably not with the "modem" partition since it was overwritten by the stock rom.
And found some details about the param partition here:
Click to expand...
Click to collapse
Try using a PIT file.
GDReaper said:
Try using a PIT file.
Click to expand...
Click to collapse
It turns out the phone is working, but the reception is bad: if I go to a better location then it works, I'm able to make and receive calls.
So the problem is not with the software. Maybe the antenna is spoiled? I suspect that because pulling the antenna out does not improve the signal level.
sullerandras said:
It turns out the phone is working, but the reception is bad: if I go to a better location then it works, I'm able to make and receive calls.
So the problem is not with the software. Maybe the antenna is spoiled? I suspect that because pulling the antenna out does not improve the signal level.
Click to expand...
Click to collapse
I would try and change the modem.
Otherwise try fixing the antenna if the modem doesn't change anything.
GDReaper said:
I would try and change the modem.
Otherwise try fixing the antenna if the modem doesn't change anything.
Click to expand...
Click to collapse
What do you mean "change the modem"?
I guess the modem's firmware was updated because after I reinstalled the original OS the phone updated itself OTA to the latest 5.0.1 android, and now it shows a different Baseband number than before.
Do you think this could still be a software issue?
sullerandras said:
What do you mean "change the modem"?
I guess the modem's firmware was updated because after I reinstalled the original OS the phone updated itself OTA to the latest 5.0.1 android, and now it shows a different Baseband number than before.
Do you think this could still be a software issue?
Click to expand...
Click to collapse
People say Modems can change reception. Although I never saw any changes myself.
How to Get a copy of boot.img Lenovo Tab 8
step 1: Download mtk-easy-su From the link Below
step 2: install mtk-easy-su.apk
step 3: open the mtk-easy-su
step 4: press the yellow circle # button
Note: wait for it to say given super user permissions to magisk manager
step 5: go to settings/About Tablet/
step 6: tap build number until it says "Your Now a Developer!" at the bottom of the screen
step 7: go to settings/Developer Options
step 8: enable Usb Debugging
step 9: plug your tablet into your computer
step 10: go to install adb from Here on your computer
step 11: type ls -la /dev/block/platform/soc/11230000.mmc/by-name
Note: It will display something like this:
lrwxrwxrwx 1 root root 20 2021-06-14 15:52 boot -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 2021-06-14 15:52 cache -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 2021-06-14 15:52 dkb -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 2021-06-14 15:52 expdb -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 2021-06-14 15:52 flashinfo -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 2021-06-14 15:52 frp -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 2021-06-14 15:52 kb -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 20 2021-06-14 15:52 lk -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 2021-06-14 15:52 logo -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 2021-06-14 15:52 metadata -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 20 2021-06-14 15:52 nvram -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 2021-06-14 15:52 para -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 20 2021-06-14 15:52 persist -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 2021-06-14 15:52 proinfo -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 2021-06-14 15:52 protect1 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 2021-06-14 15:52 protect2 -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 2021-06-14 15:52 recovery -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 20 2021-06-14 15:52 seccfg -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 2021-06-14 15:52 secro -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 2021-06-14 15:52 system -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 2021-06-14 15:52 tee1 -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 2021-06-14 15:52 tee2 -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 2021-06-14 15:52 userdata -> /dev/block/mmcblk0p22
Note : You are looking for boot:
lrwxrwxrwx 1 root root 20 2021-06-14 15:52 boot -> /dev/block/mmcblk0p8
Step 12: Then type dd if=/dev/block/mmcblk0p8 of=/sdcard/Download/boot.img
Note: the if=/dev/block/mmcblk0p8 is what we found in the list of partitions
Step 13: Wait until the copy finishes
If you would like to root follow this guide Posted Here
NOTE: You must use the filename you have from this Guide instead of the MagisBoot.img used in the other guide
I use the wrong filename. And when I reboot the device in the final step in the other guide, it just can't boot any more. The computer can't identify it through the USB. And it can't get into the fastboot mode and recovery mode. What should I do?
lester111 said:
I use the wrong filename. And when I reboot the device in the final step in the other guide, it just can't boot any more. The computer can't identify it through the USB. And it can't get into the fastboot mode and recovery mode. What should I do?
Click to expand...
Click to collapse
You can try to use a tool called flash tool with a scatter plot file which is a txt file and use the stock boot image to reflash the boot partition but idk where if at all you can get a scatter plot for this device however also it’s no guarantee the only success I know was to use the exact method in the guide because I haven’t had this issue I am not entirely sure what to do :/
https://drive.google.com/file/d/1lipGamEnpSJHdQy3f4BjsJGNwvmHvV7d/view
retry downloading that and unzip it and open the scatterplot file in so flash tool and follow this guide
link
you might luck out and unbrick it back to stock but to root will have to repeat the process of the rooting guide in going to suggest using the boot.I’m from the zip you download for so flash tool to create your magical image if you decide to root again if the device is recovered
Thank you , I will give it a try.
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.