Database Info

[Q] How to unlock bootloader with no boot on original everything???

Hi all,
So I have my firends TF300 or TF300T that does not boot. It hangs on the Asus splash screen but I can go into the recovery mode.
This tablet went ahead and messed up on its own, no flashing or unrooting attempted :/
So, now I cant get the boot unlock from Asus, so I cant flash a new recovery or rom... is there anyway to get around this??
I can connect to USB mode from the recovery, but the android and RCK both stop at "signature match".
When wiping data I get the following error:
Code:
Booting failed
unrecoverable bootloader error (0x00000000)
The reason I dont know the exact model number is because I cant boot and find any information about the tablet
Any help greatly appreciated.

Can you copy stock Asus rom to sd and install it from recovery?

stenc55 said:
Can you copy stock Asus rom to sd and install it from recovery?
Click to expand...
Click to collapse
No problem to copy stock to SD, but how would I install from recovery with no CWM and locked bootloader?

Snarlster said:
No problem to copy stock to SD, but how would I install from recovery with no CWM and locked bootloader?
Click to expand...
Click to collapse
You wrote that you can get into recovery. If it is stock Asus rom then original recovery is OK, because stock rom is signed.
Or you can try with ADB or Fastboot.

stenc55 said:
You wrote that you can get into recovery. If it is stock Asus rom then original recovery is OK, because stock rom is signed.
Or you can try with ADB or Fastboot.
Click to expand...
Click to collapse
Thanks for that, I was under the assumption that I couldn't install the stock also!
But Im far from there yet, I just spent many hours trying to install the stock that I downloaded from asus website in various way's. The file I downloaded was:
HTML:
US_epaduser_10_4_2_20_UpdateLauncher
This computer is bought in the US, and this is the exact version nr that they describe in the recovery.
Fastboot lists the device and now I've tried 2 different computers and different usb ports with:
Code:
fastboot -i 0x0B05 flash system blob
And it erases the system and say's that its going to write the system... but thats it. After a long time of waiting (many times), I eventually unplug and get an error:
FAILED (data transfer failure (Too many links))
I also tried copying the file to the SD card (two of them) both with and without renaming it "epad_update.zip" but that gives me a dead (lying) android with a triangle above the belly...
Then sometimes when trying to flash with fastboot I start getting the error:
HTML:
load_file: could not allocate 818942949 bytes
error: cannot load 'blob': Not enough space
But I found a way to get rid of that by: "flashboot update US_epad-user-10.4.2.20_2.zip" which gives an error but allows me to flash again.
I was thinking the cord might be the problem but then why wouldn't the SD card method work?
So, I'm confused
You mention ADB? I thought that was only possible if I would boot into android?

I just did the "fastboot getvar all" and figured it could possibly help someone to help me, so I'll toss it in here.
HTML:
(bootloader) version-bootloader: 1.0
(bootloader) version-baseband: 2.0
(bootloader) version: 0.4
(bootloader) serialno: some.long.number, possibly private? :)
(bootloader) mid: 001
(bootloader) product: Cardhu
(bootloader) secure: yes
(bootloader) unlocked: no
(bootloader) partition-size:bootloader: 0x0000000000800000
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:recovery: 0x0000000000800000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:boot: 0x0000000000800000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:system: 0x0000000030000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x000000001ac00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x00000006e5680000
(bootloader) partition-type:userdata: ext4
all:
finished. total time: 0.083s
Any help greatly appreciated!

Snarlster said:
I just did the "fastboot getvar all" and figured it could possibly help someone to help me, so I'll toss it in here.
HTML:
(bootloader) version-bootloader: 1.0
(bootloader) version-baseband: 2.0
(bootloader) version: 0.4
(bootloader) serialno: some.long.number, possibly private? :)
(bootloader) mid: 001
(bootloader) product: Cardhu
(bootloader) secure: yes
(bootloader) unlocked: no
(bootloader) partition-size:bootloader: 0x0000000000800000
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:recovery: 0x0000000000800000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:boot: 0x0000000000800000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:system: 0x0000000030000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x000000001ac00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x00000006e5680000
(bootloader) partition-type:userdata: ext4
all:
finished. total time: 0.083s
Any help greatly appreciated!
Click to expand...
Click to collapse
I also tried copying the file to the SD card (two of them) both with and without renaming it "epad_update.zip" but that gives me a dead (lying) android with a triangle above the belly...
The above line is bothersome. You don't rename the zip file you unzip once and find another zip which you place on your sdcard and boot into stock recovery, as when you got the red triangle.
Good Luck!

tobdaryl said:
I also tried copying the file to the SD card (two of them) both with and without renaming it "epad_update.zip" but that gives me a dead (lying) android with a triangle above the belly...
The above line is bothersome. You don't rename the zip file you unzip once and find another zip which you place on your sdcard and boot into stock recovery, as when you got the red triangle.
Good Luck!
Click to expand...
Click to collapse
I knew I didn't need to rename it, and I didn't for the first 20 times As that failed, I found this on some forum and gave it a try.
Booting into stock recovery gives you the red triangle? do you mean with a dead android underneath? After a while of the dead android with triangle, it just turns off... I dont get the huge triangle sign like I do on my galaxy... this one has a broken android included. any hints on that?

Snarlster said:
I knew I didn't need to rename it, and I didn't for the first 20 times As that failed, I found this on some forum and gave it a try.
Booting into stock recovery gives you the red triangle? do you mean with a dead android underneath? After a while of the dead android with triangle, it just turns off... I dont get the huge triangle sign like I do on my galaxy... this one has a broken android included. any hints on that?
Click to expand...
Click to collapse
I just used the red triangle since you were familiar with how to get there. I was hoping your recovery would take over and install the proper zip.
Rename the once unzipped file EP201_768_SDUPDATE.zip and try the exact same procedure as before.
Sorry I didn't put these together on the other post. Long week!

tobdaryl said:
I just used the red triangle since you were familiar with how to get there. I was hoping your recovery would take over and install the proper zip.
Rename the once unzipped file EP201_768_SDUPDATE.zip and try the exact same procedure as before.
Sorry I didn't put these together on the other post. Long week!
Click to expand...
Click to collapse
Aww, that was promising! I saw the android working for about 3 seconds... then it died again with open belly container and red triangle exclamation mark
Why would renaming it like this make a difference?

Snarlster said:
Aww, that was promising! I saw the android working for about 3 seconds... then it died again with open belly container and red triangle exclamation mark
Why would renaming it like this make a difference?
Click to expand...
Click to collapse
I can't say but for me when one doesn't work the other may. Asus has several methods of delivery these are the two which have been used with success in your situation.
Asus also uses dlpkgfile with the zip extension removed for ota updates but they are much smaller files and the updater-script is handled differently. I admit I have not tried to get stock recovery to process them from the bootloader. You can try as you can't get much worse.
Keep an eye on this thread and I'll try to do some searching, going through notes, and thinking and report back if anything else comes up.
I won't be able to do this until 3-10-2013 unless I get a break. Sorry.
I don't have any other methods that can be done with stock recovery and locked bootloader!
I'm sorry.

tobdaryl said:
I can't say but for me when one doesn't work the other may. Asus has several methods of delivery these are the two which have been used with success in your situation.
Asus also uses dlpkgfile with the zip extension removed for ota updates but they are much smaller files and the updater-script is handled differently. I admit I have not tried to get stock recovery to process them from the bootloader. You can try as you can't get much worse.
Keep an eye on this thread and I'll try to do some searching, going through notes, and thinking and report back if anything else comes up.
I won't be able to do this until 3-10-2013 unless I get a break. Sorry.
I don't have any other methods that can be done with stock recovery and locked bootloader!
I'm sorry.
Click to expand...
Click to collapse
I'll keep an eye out for sure, actually have been refreshing the page but didn't notice that it went over to second page
Thanks for the reply, I'll also post if I find something, but at this point it seems pretty hopeless... perhaps I'll start another thread since the topic on this one is incorrect now that I know I can flash stock recovery instead of trying to unlock the bootloader, I'll also post the link to the new thread when that happens
Thanks again for your help, if you get any ideas im all ears

Error: CWM does not enter Recovery mode, turn off phone

Hello I did all the procedures to unlock the bootloader, I took notice of warning logo.bin, so q can not install CWM or TRW, the error message Mismatched partition size (recovery), and every time I put q in the recovery screen goes blank or turns black Reboot help me. my android is 4.4.2

First I just want to repeat what you said, to make sure I understand. You followed the instructions to unlock the bootloader. Then you saw the warning screen so you know the unlocked worked. You tried to install a recovery, got a "mismatched partition size" error, and you can't get into your recovery. Is this correct?
The "mismatched partition size" error is normal, and you will get this message even if the new recovery flashes properly. Are you able to get to the bootloader without any problems? From where did you download the recovery that you tried to flash?

grrrrrrrrrrrrrrrrrrrr
FaultyFirmware said:
First I just want to repeat what you said, to make sure I understand. You followed the instructions to unlock the bootloader. Then you saw the warning screen so you know the unlocked worked. You tried to install a recovery, got a "mismatched partition size" error, and you can't get into your recovery. Is this correct?
The "mismatched partition size" error is normal, and you will get this message even if the new recovery flashes properly. Are you able to get to the bootloader without any problems? From where did you download the recovery that you tried to flash?
Click to expand...
Click to collapse
so I did it all you said, the only thing different foia message on boot that the phone was unlocked with the bootloader, you know that warning?
Dai to remove this message from the unlocked bootloader, flash the logo.bin file to go back to the original boot animation from motorola, I think that the bootloader is still unlocked ...
I grab the file from CWM downloaded here XDA same, this message of "Mismatched partition size (recovery)".
Ta many say that this message is normal, it happens that I put in the recovery squeeze the power button and the phone gets the black screen, and not everything goes back even after 2 minutes.
I believe that it shuts down, a version ai step before CWM, of the mismatched message ... however I enter recovery, and he does not turn off, just restarts ...
I mean I can not even get into recovery, and therefore can not make root .
Got the point? if you want to put the names of the files I tried to flash.

Here is a program that will help you install the recovery. USB debugging should be turned on on your phone, and you should be booted into the system. Also be sure that the proper USB drivers are installed on your computer.
http://forum.xda-developers.com/showthread.php?t=2635706
Here is the latest version of TWRP.
http://forum.xda-developers.com/showthread.php?t=2561757
Here is the latest version of PhilZ. It is a modified version of CWM.
http://forum.xda-developers.com/showthread.php?t=2639583
Choose one of the recoveries listed above and install with the tool. If you flash the recovery in this way, I think it will work for you. As always, read everything carefully. Know the type of Moto G you have and be sure to choose the right files.

this is complicated again tried to do what was already done with the files that I step, and the Moto tool aio tool and also via adb, and he clicking recovery restarts, do not know what to do more lost. I made a video and played on youtube showing the process, and what happens there happened to all types of file recovery and point out that the latter (philz_touch_6.13.2-xt1033.zip).
In the video also has all specifications. Please help me

So after you select and activate recovery and you see the Motorola logo, it boots into the normal system? You have the 8GB dual-sim Brazil/India/Malaysia version? This is not a Google Play Edition? Does the box it came in say "XT1033"?
The PhilZ you chose is not the latest version. They use a unified build now, which should work on all types of Moto G. It is here: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/falcon//philz_touch_6.26.6-falcon.zip That one is worth a try. Your TWRP version is correct, though, so I don't know why that didn't work.
Your USB connection seems to be working fine, and you have tried ADB and the AIO tool. Have you tried using fastboot from the bootloader? The command would be "fastboot flash recovery recovery.img" and you would do this while you are in the bootloader. You should still expect to see the partition size mismatch error.
If that fails we can try flashing everything back to stock and start fresh. Please use "fastboot getvar all" and post the results (you can remove IMEI, Serial Number, and other private information). This will tell us which stock to use.

FaultyFirmware said:
So after you select and activate recovery and you see the Motorola logo, it boots into the normal system? You have the 8GB dual-sim Brazil/India/Malaysia version? This is not a Google Play Edition? Does the box it came in say "XT1033"?
The PhilZ you chose is not the latest version. They use a unified build now, which should work on all types of Moto G. It is here: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/falcon//philz_touch_6.26.6-falcon.zip That one is worth a try. Your TWRP version is correct, though, so I don't know why that didn't work.
Your USB connection seems to be working fine, and you have tried ADB and the AIO tool. Have you tried using fastboot from the bootloader? The command would be "fastboot flash recovery recovery.img" and you would do this while you are in the bootloader. You should still expect to see the partition size mismatch error.
If that fails we can try flashing everything back to stock and start fresh. Please use "fastboot getvar all" and post the results (you can remove IMEI, Serial Number, and other private information). This will tell us which stock to use.
Click to expand...
Click to collapse
i have same problem. but i cant boot into ROM or custom recovery. i try flash latest phillz recovery but still not working. there is my log
H:\MotoToolAioV3\mfastboot-v2>fastboot devices
TA929046PR fastboot
H:\MotoToolAioV3\mfastboot-v2>fastboot -w
erasing 'userdata'...
OKAY [ 3.244s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.022s]
erasing 'cache'...
OKAY [ 0.413s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.024s]
finished. total time: 3.727s
H:\MotoToolAioV3\mfastboot-v2>fastboot flash recovery cwm.img
target reported max download size of 536870912 bytes
sending 'recovery' (8556 KB)...
OKAY [ 0.356s]
writing 'recovery'...
OKAY [ 0.314s]
finished. total time: 0.676s
H:\MotoToolAioV3\mfastboot-v2>fastboot reboot recovery
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater th
an
size. 0 to disable
H:\MotoToolAioV3\mfastboot-v2>fastboot reboot recovery
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater th
an
size. 0 to disable
H:\MotoToolAioV3\mfastboot-v2>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 4105
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: TA929046PR
(bootloader) cid: 0x0007
(bootloader) uid: E98452020F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 359276056402244
(bootloader) meid:
(bootloader) date: 01-24-2014
(bootloader) sku: XT1032
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 8 8:20: 6 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_o2de/falcon_umts:4
(bootloader) ro.build.fingerprint[1]: .4.2/KLB20.9-1.10-1.9.1/1:user/rel
(bootloader) ro.build.fingerprint[2]: ease-keys
(bootloader) ro.build.version.full[0]: Blur_Version.175.44.1.falcon_umts
(bootloader) ro.build.version.full[1]: .O2.en.DE
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_JB_3.2.3.04.03.0
(bootloader) ro.build.version.qcom[1]: 0.166.006
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.0-gc6fc9e1-00001-g6ff8
(bootloader) kernel.version[1]: 71f ([email protected]) (gcc version 4.
(bootloader) kernel.version[2]: 7 (GCC) ) #1 SMP PREEMPT Mon Jan 13 04:4
(bootloader) kernel.version[3]: 6:14 CST 2014
(bootloader) sdi.git: git=MBM-NG-V41.05-0-gac19e15
(bootloader) sbl1.git: git=MBM-NG-V41.05-0-g6863770
(bootloader) rpm.git: git=MBM-NG-V41.05-0-g4018bbe
(bootloader) tz.git: git=MBM-NG-V41.05-0-g11658be
(bootloader) aboot.git: git=MBM-NG-V41.05-0-gf4ab363
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 1/1
all: listed above
finished. total time: 0.060s
H:\MotoToolAioV3\mfastboot-v2>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 4105
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: TA929046PR
(bootloader) cid: 0x0007
(bootloader) uid: E98452020F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 359276056402244
(bootloader) meid:
(bootloader) date: 01-24-2014
(bootloader) sku: XT1032
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 8 8:22:49 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_o2de/falcon_umts:4
(bootloader) ro.build.fingerprint[1]: .4.2/KLB20.9-1.10-1.9.1/1:user/rel
(bootloader) ro.build.fingerprint[2]: ease-keys
(bootloader) ro.build.version.full[0]: Blur_Version.175.44.1.falcon_umts
(bootloader) ro.build.version.full[1]: .O2.en.DE
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_JB_3.2.3.04.03.0
(bootloader) ro.build.version.qcom[1]: 0.166.006
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.0-gc6fc9e1-00001-g6ff8
(bootloader) kernel.version[1]: 71f ([email protected]) (gcc version 4.
(bootloader) kernel.version[2]: 7 (GCC) ) #1 SMP PREEMPT Mon Jan 13 04:4
(bootloader) kernel.version[3]: 6:14 CST 2014
(bootloader) sdi.git: git=MBM-NG-V41.05-0-gac19e15
(bootloader) sbl1.git: git=MBM-NG-V41.05-0-g6863770
(bootloader) rpm.git: git=MBM-NG-V41.05-0-g4018bbe
(bootloader) tz.git: git=MBM-NG-V41.05-0-g11658be
(bootloader) aboot.git: git=MBM-NG-V41.05-0-gf4ab363
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 1/1
all: listed above
finished. total time: 0.061s
H:\MotoToolAioV3\mfastboot-v2>
Click to expand...
Click to collapse

FaultyFirmware said:
So after you select and activate recovery and you see the Motorola logo, it boots into the normal system? You have the 8GB dual-sim Brazil/India/Malaysia version? This is not a Google Play Edition? Does the box it came in say "XT1033"?
The PhilZ you chose is not the latest version. They use a unified build now, which should work on all types of Moto G. It is here: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/falcon//philz_touch_6.26.6-falcon.zip That one is worth a try. Your TWRP version is correct, though, so I don't know why that didn't work.
Your USB connection seems to be working fine, and you have tried ADB and the AIO tool. Have you tried using fastboot from the bootloader? The command would be "fastboot flash recovery recovery.img" and you would do this while you are in the bootloader. You should still expect to see the partition size mismatch error.
If that fails we can try flashing everything back to stock and start fresh. Please use "fastboot getvar all" and post the results (you can remove IMEI, Serial Number, and other private information). This will tell us which stock to use.
Click to expand...
Click to collapse
ok this is the print:
D:\Downloads\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tool
oot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 4108
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x5
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Hynix S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: xxxxxxxxxxxxxx
(bootloader) cid: 0x000C
(bootloader) uid: F66F3B020F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
(bootloader) meid:
(bootloader) date: 2014-01-24
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Apr 18 15:49:10 UTC 2014"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_amxbr_ds/falcon_um
(bootloader) ro.build.fingerprint[1]: tsds:4.4.2/KXB20.25-1.31/15:user/r
(bootloader) ro.build.fingerprint[2]: elease-keys
(bootloader) ro.build.version.full[0]: Blur_Version.171.44.31.falcon_umt
(bootloader) ro.build.version.full[1]: sds.AmericaMovil.en.BR
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_JB_3.2.3.04.03.0
(bootloader) ro.build.version.qcom[1]: 0.166.006
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.0-g13e395f ([email protected]
(bootloader) kernel.version[1]: lclbld52) (gcc version 4.7 (GCC) ) #1 SM
(bootloader) kernel.version[2]: P PREEMPT Thu Jan 23 21:22:07 CST 2014
(bootloader) sdi.git: git=MBM-NG-V41.08-0-gac19e15
(bootloader) sbl1.git: git=MBM-NG-V41.08-0-g6863770
(bootloader) rpm.git: git=MBM-NG-V41.08-0-g8ef2ac8
(bootloader) tz.git: git=MBM-NG-V41.08-0-gcebfadf
(bootloader) aboot.git: git=MBM-NG-V41.08-0-g04a4bc3
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 1/1
all: listed above
finished. total time: 0.057s

Yeah, I have the same issue :-/ phone just reboots instead of going into recovery :-/ I tried cwm and philz...
Sent from my XT1032 using xda app-developers app
---------- Post added at 06:36 PM ---------- Previous post was at 06:19 PM ----------
Guys, I have just discovered how to enter recovery... In fastboot mode press vol-down (this selects recovery option) and then vol-up. It goes into recovery. Tested with latest philz. I tried million of times but I expected power button to choose options... Is it normal behavior?
Sent from my XT1032 using xda app-developers app

Bro, try this method.
1.Download the Android SDK
2.Download the recovery you want (I used CWM but TWRP works aswell)
3.Go to Your SDK directory then go to \adt-bundle-windows-x86_64-20140321\sdk\platform-tools\
4.Inside you will find adb, fast boot stuff like that, now put your recovery inside there and rename it to recovery.img
5.Reboot into fasboot mode (power off + Vol- )
6.Go to your platform-tools folder, now hold Shift + press Right click, and select open command window here.
7. Type in:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
8.When that is complete reboot into recovery via the fastboot menu (Volume - then Volume + to select).
I hope this works, i had this problem before so now i just do this and i dont use the MotoTool AIO.

Wow, so much activity. Let's get this sorted.
sinkadorable: The command for rebooting into recovery is "fastboot reboot-recovery". Without the dash, nothing happens. That's what your log describes. You can use "adb reboot recovery" to enter recovery if you are fully booted into the system.
Routerm4N: For privacy you may want to edit your post to remove the lines labeled "imei" and "serialno". These can be used to uniquely identify your phone. So you tried flashing the file I liked in my last post and were unsuccessful? I don't have a copy of you ROM you are currently using, but it looks like this stock ROM is compatable with your phone. http://sbf.droid-developers.org/download.php?device=14&file=130 Are you on Android 4.3 or 4.4? The ROM I linked will take you back to 4.3, but you can always use OTA updates to get back again later. Here are the instructions for flashing stock firmware: http://forum.xda-developers.com/showthread.php?t=2542219 It is a bit of an involved process. Only do this if you have exhausted your other options.
fabus: Yes, it is unintuitive that the "up" button activates the selected option. However, it says on the bootloader screen that this is how it works. They probably wanted to reserve the power button for powering the device on and off.

FaultyFirmware said:
Wow, so much activity. Let's get this sorted.
sinkadorable: The command for rebooting into recovery is "fastboot reboot-recovery". Without the dash, nothing happens. That's what your log describes. You can use "adb reboot recovery" to enter recovery if you are fully booted into the system.
Routerm4N: For privacy you may want to edit your post to remove the lines labeled "imei" and "serialno". These can be used to uniquely identify your phone. So you tried flashing the file I liked in my last post and were unsuccessful? I don't have a copy of you ROM you are currently using, but it looks like this stock ROM is compatable with your phone. http://sbf.droid-developers.org/download.php?device=14&file=130 Are you on Android 4.3 or 4.4? The ROM I linked will take you back to 4.3, but you can always use OTA updates to get back again later. Here are the instructions for flashing stock firmware: http://forum.xda-developers.com/showthread.php?t=2542219 It is a bit of an involved process. Only do this if you have exhausted your other options.
fabus: Yes, it is unintuitive that the "up" button activates the selected option. However, it says on the bootloader screen that this is how it works. They probably wanted to reserve the power button for powering the device on and off.
Click to expand...
Click to collapse
Thanks I use 4.4.2

FaultyFirmware said:
Wow, so much activity. Let's get this sorted.
sinkadorable: The command for rebooting into recovery is "fastboot reboot-recovery". Without the dash, nothing happens. That's what your log describes. You can use "adb reboot recovery" to enter recovery if you are fully booted into the system.
Routerm4N: For privacy you may want to edit your post to remove the lines labeled "imei" and "serialno". These can be used to uniquely identify your phone. So you tried flashing the file I liked in my last post and were unsuccessful? I don't have a copy of you ROM you are currently using, but it looks like this stock ROM is compatable with your phone. http://sbf.droid-developers.org/download.php?device=14&file=130 Are you on Android 4.3 or 4.4? The ROM I linked will take you back to 4.3, but you can always use OTA updates to get back again later. Here are the instructions for flashing stock firmware: http://forum.xda-developers.com/showthread.php?t=2542219 It is a bit of an involved process. Only do this if you have exhausted your other options.
fabus: Yes, it is unintuitive that the "up" button activates the selected option. However, it says on the bootloader screen that this is how it works. They probably wanted to reserve the power button for powering the device on and off.
Click to expand...
Click to collapse
Still cannot boot into recovery with every method was i found. When i choose boot into recovery it just looping in boot logo

Even with adb?
sinkadorable said:
Still cannot boot into recovery with every method was i found. When i choose boot into recovery it just looping in boot logo
Click to expand...
Click to collapse
Are you getting same error when you fully boot into system, connect it to pc via a data cable
and run
Code:
adb reboot recovery
??

deej_roamer said:
Are you getting same error when you fully boot into system, connect it to pc via a data cable
and run
Code:
adb reboot recovery
??
Click to expand...
Click to collapse
I think in fastboot menu cannot run adb command

sinkadorable said:
I think in fastboot menu cannot run adb command
Click to expand...
Click to collapse
This is true. I was saying you can use adb if you happen to be fully booted into the system.
Edit: Obviously you weren't referring to my post. Now I can't find the delete button.... Oh well.
Sinkadorable: have you tried flashing everything back to stock from the bootloader?
Routerm4N: How's your progress?

FaultyFirmware said:
This is true. I was saying you can use adb if you happen to be fully booted into the system.
Edit: Obviously you weren't referring to my post. Now I can't find the delete button.... Oh well.
Sinkadorable: have you tried flashing everything back to stock from the bootloader?
Routerm4N: How's your progress?
Click to expand...
Click to collapse
Yes. Every method was i found

While in bootloader menu, VOLUME DOWN(-) is for navigation, and VOLUME UP(+) is to select or choose the option.
POWER BUTTON DOES NOTHING!
DO NOT USE THE POWER BUTTON FOR ANYTHING WHILE IN BOOTLOADER MENU!

wow nice thanks

Hey i am having the same problem
anyone got any solution.
please update it.

Messed up installing 5.1.11. now only fastboot boots and can't boot twrp image.

i tried to install the newest 5.1.11 in full ( as i am magisk rooted, twrp installed, and bootloader unlocked). i kept getting system ui crashes over and over and eventually, after so many, the phone just powers down by itself. I had tried clearing cache after going back into twrp. Rebooted. Same ui issue. Then i decided to restore a backup in twrp i had made a few weeks ago stored on internal memory. This was a bad idea. It said it restored successfully but upon reboot, i only get fastboot now. i think it is communicating with fastboot but when i try to fastboot boot twrp-3.2.1-0 (or 3.2.2-0) i get, "remote: Failed to load/authenticate boot image: Load Error". I do not know what to do and am hoping you guys can figure out how to fix this. Any attempt to enter recovery via buttons results in fastboot booting. restart is also fastboot.
This is what my phone says:
FastBoot mode
Product_name- sdm845
variant- sdm ufs
basband version-
serial- it's there
secure boot- yes
device state- unlocked
Don't know if this helps fastboot getvar all reports this:
C:\Adb\OnePlus 6 Files>fastboot getvar all
(bootloader) unlocked:yes
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3837
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) variant:SDM UFS
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x1B800B7000
(bootloader) partition-type:system_a:ext4
(bootloader) partition-size:system_a: 0xB2C00000
(bootloader) has-slot:modem:yes
(bootloader) has-slot:system:yes
(bootloader) current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:6
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:0
(bootloader) slot-unbootable:a:yes
(bootloader) slot-successful:a:no
(bootloader) slot-count:2
(bootloader) secure:yes
(bootloader) serialno: omitted
(bootloader) product:sdm845
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
all:
finished. total time: 0.047s
Is there anyone that has had this set of circumstances and got out of it? Any help is appreciated. There are some things i've seen that i can do but don't want to do further damage. Thanks to all for any and all help.

thejase said:
i tried to install the newest 5.1.11 in full ( as i am magisk rooted, twrp installed, and bootloader unlocked). i kept getting system ui crashes over and over and eventually, after so many, the phone just powers down by itself. I had tried clearing cache after going back into twrp. Rebooted. Same ui issue. Then i decided to restore a backup in twrp i had made a few weeks ago stored on internal memory. This was a bad idea. It said it restored successfully but upon reboot, i only get fastboot now. i think it is communicating with fastboot but when i try to fastboot boot twrp-3.2.1-0 (or 3.2.2-0) i get, "remote: Failed to load/authenticate boot image: Load Error". I do not know what to do and am hoping you guys can figure out how to fix this. Any attempt to enter recovery via buttons results in fastboot booting. restart is also fastboot.
This is what my phone says:
FastBoot mode
Product_name- sdm845
variant- sdm ufs
basband version-
serial- it's there
secure boot- yes
device state- unlocked
Don't know if this helps fastboot getvar all reports this:
C:\Adb\OnePlus 6 Files>fastboot getvar all
(bootloader) unlocked:yes
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3837
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) variant:SDM UFS
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x1B800B7000
(bootloader) partition-type:system_a:ext4
(bootloader) partition-size:system_a: 0xB2C00000
(bootloader) has-slot:modem:yes
(bootloader) has-slot:system:yes
(bootloader) current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:6
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:0
(bootloader) slot-unbootable:a:yes
(bootloader) slot-successful:a:no
(bootloader) slot-count:2
(bootloader) secure:yes
(bootloader) serialno: omitted
(bootloader) product:sdm845
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
all:
finished. total time: 0.047s
Is there anyone that has had this set of circumstances and got out of it? Any help is appreciated. There are some things i've seen that i can do but don't want to do further damage. Thanks to all for any and all help.
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 your solution lies here

tabletalker7 said:
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 your solution lies here
Click to expand...
Click to collapse
I saw this. Will i keep my data with this method?

thejase said:
I saw this. Will i keep my data with this method?
Click to expand...
Click to collapse
no, but if you can't even boot to TWRP then you have nothing left to save at this point.

Try booting the latest twrp (3.2.3.0) before giving up and wiping. If you can get to fastboot, you're not bricked.

iElvis said:
Try booting the latest twrp (3.2.3.0) before giving up and wiping. If you can get to fastboot, you're not bricked.
Click to expand...
Click to collapse
thanks for the suggestions but no dice.

According to your first posting, the phone knows that the boot partition on both your slots are a mess and can't load - you need the fastboot rom to make the phone start over and try again. Sorry buddy - I would like to save your data but it doesn't seem feasible at this point.

tabletalker7 said:
According to your first posting, the phone knows that the boot partition on both your slots are a mess and can't load - you need the fastboot rom to make the phone start over and try again. Sorry buddy - I would like to save your data but it doesn't seem feasible at this point.
Click to expand...
Click to collapse
That's alright. I appreciate the point in the right direction. Doing that fastboot method bat file that you suggested now... Thanks for the help.

thejase said:
That's alright. I appreciate the point in the right direction. Doing that fastboot method bat file that you suggested now... Thanks for the help.
Click to expand...
Click to collapse
tabletalker7 said:
According to your first posting, the phone knows that the boot partition on both your slots are a mess and can't load - you need the fastboot ROM to make the phone start over and try again. Sorry buddy - I would like to save your data but it doesn't seem feasible at this point.
Click to expand...
Click to collapse
So as it turns out that method worked using the bat file flash all fastboot. Though, not at first. When it first rebooted after the bat file finished flashing. system UI was still crashing. When you initially run the bat file at the beginning, it asks if you want to delete your data. First time around i said no, just to see what it would do. Well it booted, but kept getting that system ui crash that I had in the beginning of all this mess. I rebooted and this time chose to erase data and then it re-flashed all again (same bat file). Turns out, when it booted, same deal, system UI crash. So this time i was looking things up while the crashes where happening and then it just rebooted on its own (as it does with a number of system UI crashes in succession). When it came up it was that Chinese menu (which i assume to be download mode or something). Anyway, i chose English and it's a menu to clear dalvik and cache, system settings reset, and one other i can't remember. i did system settings then dalvik and finally, when i rebooted, it was like it was booting for the first time with no crashes. Only thing i can figure is that setting in the bat file at first launch actually didn't erase user data since when it booted, all my icons where there in the background. doing it "on device" in download mode seems to have worked. I am only adding this information as an f.y.i.. Thanks again for all your help, guys.

thejase said:
When it came up it was that Chinese menu (which i assume to be download mode or something).
Click to expand...
Click to collapse
That's stock recovery.

maigre said:
That's stock recovery.
Click to expand...
Click to collapse
Oh, ok. Funny thing is, I had never seen what that looked like as I immediately installed twrp from the time I bought it. Makes sense, though I still wonder why it booted to stock recovery after systemui crashing. Unless it senses the crashes and does that by default to clear system settings and data for a successful boot?

moto one vision hard bricked

i unlocked the bootloader and then unknowingly i gave command " fastboot erase all ".
now the device is not powering on and not even responding,no screen on (even when inserting charger).
can anyone suggest a solution??

D A R K 9 said:
i unlocked the bootloader and then unknowingly i gave command " fastboot erase all ".
now the device is not powering on and not even responding,no screen on (even when inserting charger).
can anyone suggest a solution??
Click to expand...
Click to collapse
Take it to a service center for flashing the firmware?

D A R K 9 said:
i unlocked the bootloader and then unknowingly i gave command " fastboot erase all ".
now the device is not powering on and not even responding,no screen on (even when inserting charger).
can anyone suggest a solution??
Click to expand...
Click to collapse
Don't take strictly right but I've done it some time ago on a Snapdragon phone . For this you absolutely need for Motorola One Vision Qfil files and Flashone app for Windows . The whole process is very simple but finding proper Qfil files ROM is a pain in the butt .
If you find these files somehow , anywhere , anytime don't forget to share .
...............................
Or use this : https://forum.xda-developers.com/moto-z/help/help-moto-z-dead-brick-t3809740
Or this : https://forum.xda-developers.com/showpost.php?p=76310273&postcount=183

muppetz said:
Don't take strictly right but I've done it some time ago on a Snapdragon phone . For this you absolutely need for Motorola One Vision Qfil files and Flashone app for Windows . The whole process is very simple but finding proper Qfil files ROM is a pain in the butt .
If you find these files somehow , anywhere , anytime don't forget to share .
...............................
Or use this : https://forum.xda-developers.com/moto-z/help/help-moto-z-dead-brick-t3809740
Or this : https://forum.xda-developers.com/showpost.php?p=76310273&postcount=183
Click to expand...
Click to collapse
ya but i used to do same cmd for sony and mi mobile but never faced this issue,i didnt expect this thing from a motorola device.now they are saying to change sub board for not power on reason reason at service center.

D A R K 9 said:
ya but i used to do same cmd for sony and mi mobile but never faced this issue,i didnt expect this thing from a motorola device.now they are saying to change sub board for not power on reason reason at service center.
Click to expand...
Click to collapse
You're right . It doesn't explain their proposals if you just did a simple cmd to the phone as you said . Maybe they try to squeeze some extra bucks from you . I'm sorry , man .

hard bricked one vision
its showing as exynos9610 in device manager,any leads from here??

D A R K 9 said:
its showing as exynos9610 in device manager,any leads from here??
Click to expand...
Click to collapse
good news , it seems pc recognize phone , further steps to bring back phone , no clue, but I supose it's primordial to flash partitions . Google it .

D A R K 9 said:
its showing as exynos9610 in device manager,any leads from here??
Click to expand...
Click to collapse
Look in the OP for a rom to flash in fastboot.

gee2012 said:
Look in the OP for a rom to flash in fastboot.
Click to expand...
Click to collapse
sadly its not going to fastboot mode.as of matter still screen not showing anything,only thing just pc shows a device connected in usb as exynos9610

D A R K 9 said:
sadly its not going to fastboot mode.as of matter still screen not showing anything,only thing just pc shows a device connected in usb as exynos9610
Click to expand...
Click to collapse
Try the adb command ` fastboot devices` and see if you get a serial number.

I'm also in this same situation. Been looking all around for solutions but all i come across are fixes for qualcom devices. Even all the blankflashing posts are qualcom. My guess is that we need to find software that'll work with exynos chips that isn't samsung. Adb, fastboot and mfastboot commands don't work because in its current state the device is only recognized as "Exynos9610"

I have the same problema. Im trying to follow this thread:
https://forum.xda-developers.com/galaxy-s6/general/guide-repair-hard-bricked-devices-t3573865/amp/
My problem is that my computer is Windows 10 and it can't load the Exynos drivers, I hope that you have good look with that. You should try to change the cfg archive to load bootloader.

Found something intresting on "lolinet" today. A "blankflash" for kane.
Could be worth a try for sure, if you're hardbricked.
I have not tried it so I've no idea if this is legit.
The procedure would probably be something like:
Unzip all files.
Install drivers (ImageWriterUSBDriver_1113_00.exe).
Open "Multidownloader_64bit_1.4.1.exe".
Connect device to usb and let multidownloader detect it.
In the "box", browse for the "usbbooting.cfg" that is present in the kane_blankflash and hit start.
My guess is that it's supposed to reboot to fastboot once it's done writing the files so that you can reflash full firmware from fastboot, like it is with blankflash for other moto devices.
Let us know how it goes if anyone tries it.

Error
I'm in trouble, too.
I can even enter fastboot but do not accept to update, the following error appears.
target max-sparse-size: 256MB
sending 'fwbl1' (16 KB)...
OKAY [ 0.040s]
writing 'fwbl1'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fwbl1
FAILED (remote failure)
finished. total time: 0.082s
Click to expand...
Click to collapse
My phone get vars
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.2-kane_retail-523afc7-190729
(bootloader) product: kane
(bootloader) board: kane
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 1
(bootloader) storage-type: ufs
(bootloader) ufs: 128GB WDC SDINDDH4-128G FV=1268
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: Exynos9609
(bootloader) serialno: 0057049924
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 000003B54E4B96FA0000000000000000
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 535822336
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 354154101426432
(bootloader) meid:
(bootloader) date: 05-09-2019
(bootloader) sku: XT1970-1
(bootloader) carrier_sku: XT1970-1
(bootloader) battid: SB18C43602
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Aug 28 2:48:21 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/kane/kane_sprout:9/PSAS29
(bootloader) ro.build.fingerprint[1]: .137-16-4/fc9db:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.221.4.kane.retail
(bootloader) ro.build.version.full[1]: .en.US
(bootloader) ro.build.version.samsung: 20190510
(bootloader) version-baseband: S337AP_KANE_SGCS_QB2190425
(bootloader) kernel.version[0]: Linux version 4.14.56-g1007313 (hudsoncm
(bootloader) kernel.version[1]: @ilclbld115) (Android (4691093 based on
(bootloader) kernel.version[2]: r316199) clang version 6.0.2 (]
(bootloader) kernel.version[3]:
(bootloader) kernel.version[4]: 83abd29fc496f55536e7d904e0abae47888fc7f)
(bootloader) kernel.version[5]: (
(bootloader) kernel.version[6]: hain/llvm 34361f192e41ed6e4e8f9aca80a4ea
(bootloader) kernel.version[7]: 7e9856f327) (based on LLVM 6.0.2svn)) #1
(bootloader) kernel.version[8]: SMP PREEMPT Mon Jul 29 06:52:16 CDT 201
(bootloader) kernel.version[9]: 9
(bootloader) bootloader.git: MBM-2.2-kane_retail-523afc7-190729
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retbr
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: No
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
Click to expand...
Click to collapse
Anyone can helpme?

Okay, I know the last message here was almost 2 years ago, but I'm just here to confirm, that I've tried this blankflash and indeed, it works.
So I've rewritten both bootloader A and B slots with /dev/zero and tried to reboot. Of course, nothing happened, but the device was detected and booted into fastboot. Everything was working there. Than just flashed bootloader_a and bootloader_b and it booted like nothing happened.

danmaya said:
Error
I'm in trouble, too.
I can even enter fastboot but do not accept to update, the following error appears.
My phone get vars
Anyone can helpme?
Click to expand...
Click to collapse
So here you have probably broken UFS (device's internal storage). If the files you try to flash are signed, but you still can't load them, then it means, you have corrupted memory. With this, go to service, they could try to replace UFS chip with another one. From what I can see, your bootloader is locked, so try to unlock it and then flash the firmware, maybe this will work.

[GUIDE][ROOT] Hyundai 8" HyTab Plus (8WB1) WiFi Tablet Bootloader Unlocking & Rooting Guide

Hyundai 8" HyTab Plus
WiFi Android Tablet
Model No. HT8WB1RBK03​
{
"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"
}
​Bootloader Unlocking
And Rooting Guide​DEVICE OVERVIEW:​The Hyundai HYTab Plus (8WB1) is a budget 8" Android tablet manufactured by Hyundai Technology. This particular model relies on WiFi and does not support 4G-LTE data connectivity. (The HYTab Plus (8LB1) model has integrated 4G-LTE support.) This tablet is powered by the Allwinner-A133 chipset with a quad-core Cortex-A53 CPU which clocks at around 1.52 GHz, paired with 2 GB RAM and 32 GB of internal storage. The 8" HD IPS display has a resolution of 1280 x 800 at a 16:10 aspect ratio. For connectivity, this model supports both the WiFi 6 and Bluetooth 5.0 standards. It ships with Android 11 (Go Edition) with the Linux 5.4.99 ACK kernel. The 3500 mAh Li-Ion battery keeps the device powered for about 12 hours on moderate usage, and up to 24 hours on light usage ​DISCLAIMER:
The procedures outlined in this guide involve potentially risky system-level modifications which will most likely void your warranty. Although I have thoroughly tested these procedures on my own device, there is nevertheless an inherent risk of bricking your tablet or otherwise rendering it completely inoperable if these instructions are not closely followed. You are encouraged to fully read this guide PRIOR to initiating the instructions. In any event, by proceeding further, you are assuming sole responsibility for the integrity and operability of your device. I am not responsible or in any way liable in the unfortunate event something goes wrong. Follow the instructions carefully and pay attention to detail; things should go smoothly.
This guide will be outlined in two sections as follows: (1) unlocking the bootloader; and (2) rooting the tablet. Next, I'll go over everything you will need for these tasks.
PREREQUISITES:
Although the following procedures can be carried out using Windows, Mac or Linux, this particular guide will focus on a Windows-based setup. For both sections of this guide, you will need a PC or laptop running on Windows 7/8.1/10/11, the OEM-supplied or a quality equivalent USB-A to micro USB data sync cable, and a Hyundai HYTab Plus 8" tablet -- Model HT8WB1RBK03 Only. If you have not already installed the ADB & Fastboot tools on your computer, along with the proper USB device drivers, follow the steps in the next section; otherwise, you may skip down to the INSTRUCTIONS heading.
ADB & FASTBOOT / USB DRIVERS
For unlocking the bootloader and rooting the tablet, we will be using fastboot mode command lines. As such, it is crucial that the correct USB device drivers & ADB/Fastboot tools are correctly installed on your Windows computer. The simplest and most efficient method I've found is an all-in-one utility called the 15-Second ADB Installer, which configures ADB & Fastboot system-wide, and also installs the universal Google USB device drivers. Download the 15-Second ADB Installer from the link below and save the file on your computer. Right click the file and opt to Run as administrator. Select "Y" when prompted to install ADB & Fastboot. Select "Y" again when prompted to install ADB system-wide. THe ADB & Fastboot tools are now installed on your Windows computer. Next, you will be prompted to instal device drivers. Once again, select "Y." A Device Driver Installation WIzard window will now appear. Click on Next. The Google universal USB device drivers will now be installed. NOTE: if you get a notification dialog warming that the drivers are unsigned, choose the option to install anyway. Now click Finish. It is recommended to reboot your computer at this point to ensure proper configuration of the drivers.
INSTRUCTIONS
A. UNLOCKING THE BOOTLOADER:
WARNING: UNLOCKING YOUR BOOTLOADER TRIGGERS A NATIVE ANDROID SECURITY MECHANISM THAT FORCES THE DEVICE INTO A FACTORY DATA RESET, WHICH COMPLETELY WIPES ALL SAVED MEDIA, FILES, PHOTOS, VIDEOS, APP DATA & SETINGS, ETC., FROM INTERNAL STORAGE. BEFORE PROCEEDING FURTHER, MAKE A BACKUP OF ANY SAVED DATA THAT YOU WISH TO KEEP.
This procedure is a mandatory prerequisite to rooting your device. If you have already unlocked your bootloader prior to finding this guide, you can skip down to the rooting section. Otherwise, let us begin: ​
In your Developer Options menu, ensure that both OEM Unlocking and ADB Debugging are enabled. Connect your tablet to your computer using the OEM-supplied or a quality equivalent USB data sync cable;​
On your PC or laptop, open the File Explorer and select This PC. Double-click on your C drive, then double click again on the folder labeled "adb." Now hold the Shift key and right click anywhere inside the folder. Select the option for a Command Prompt or Power Shell window. Execute this command:
Code:
adb devices
If properly connected, ADB will return an alphanumeric string synonymous with your device serial number. Once a proper connection is confirmed, execute this command:
Code:
adb reboot bootloader
​
Your tablet will boot into fastboot mode, which will be a black, dimly backlit screen with a green Android graphic in the center. Next, execute this command:
Code:
fastboot devices
Once again, if properly connected, your device serial number followed by "fastboot" will appear in the command window. If the command window does not display your serial number, proceed to the next step. If you are connected properly, however, skip down to Step 6;​
Right click your Windows Start icon and select Device Manager from the menu. Locate your device in the menu. Most likely, it will appear under the Other Devices heading as USB Developer. Right click on your device and select Update driver. Next, select Browse my computer for drivers, then choose the option titled Let me pick from a list... From the next list, select Android Device. Click on Android Bootloader Interface and click on Next. Select Yes on the next dialog box. The correct driver will now be installed on your computer. Return to the Power Shell or Command Window and again execute
Code:
fastboot devices
You should now see your serial number followed by the word "fastboot," indicating that you are properly connected;​
In the command window, execute
Code:
fastboot flashing unlock
Follow any on-screen prompts on your tablet display to initiate the unlocking sequence. Once you receive confirmation that unlocking is successful, execute the command
Code:
fastboot reboot
A factory data reset will now be initiated after which your tablet will reboot. It will now be necessary to complete the setup process. Once complete, you must again enable Developer Options and enable USB Debugging from the menu. Your tablet is officially bootloader unlocked (OEM unlocked). ​
B. ROOTING THE TABLET:
I have simplified this step exponentially by providing a pre-rooted boot image. Now that the bootloader is unlocked, attaining root access of the Android OS is as simple as flashing the pre-rooted boot image to the /boot partition. This will install Magisk v24.3 systemless root binaries to your device. ​
Download the Magisk patched boot image from the link below and save it inside the adb directory on the root of your C drive;​
Assuming your device is still synced to your computer from the previous section, reboot into fastboot mode once again by executing the command
Code:
adb reboot bootloader
​
Once again, to ensure proper syncing, execute
Code:
fastboot devices
After verifying proper sync, execute the following commands ​
Code:
fastboot flash boot patched_boot.img
fastboot reboot
Upon reboot, your tablet will be rooted via Magisk v24.3. Once the Android OS boots up, go to your app drawer and open the Magisk app stub icon. You will be prompted to update the Magisk app to the full version, after which Magisk will finish setting up the root environment. That's it -- you are now rooted with Magisk v24.3. NOTE: After rebooting into the Android OS, if you do not see the Magisk app or its stub icon in your app drawer, simply install the latest Magisk app from the official GitHub release page I have linked below and install it on your tablet. Open the app and follow any prompts to complete root setup. ​
​DOWNLOADS: ​Magisk Patched Boot Image
15-Second ADB Installer
Official Magisk Github
V03 Factory Firmware Package​

This method is super simple, everything worked without any stumbling blocks and my tablet now has root, but unfortunately it seems to have broken wifi. I'm unable to turn on wifi or connect to any networks. I've tried tweaking some permissions and turning off battery optimization for the select few system apps responsible for handling wifi connections, but to no avail.
Im gonna try poking around in the patched boot img for any clues and hopefully figure out some kind of fix. If anyone has any advice, suggestions, or fixes I'm unaware of, please improve this thread with your knowledge.

AMShiech said:
This method is super simple, everything worked without any stumbling blocks and my tablet now has root, but unfortunately it seems to have broken wifi. I'm unable to turn on wifi or connect to any networks. I've tried tweaking some permissions and turning off battery optimization for the select few system apps responsible for handling wifi connections, but to no avail.
Im gonna try poking around in the patched boot img for any clues and hopefully figure out some kind of fix. If anyone has any advice, suggestions, or fixes I'm unaware of, please improve this thread with your knowledge.
Click to expand...
Click to collapse
Greetings friend, I'm sorry that I'm just now seeing your post. I need a bit more info regarding your tablet, so I can try to resolve your WiFi issues.
What firmware build was running on your tablet prior to attaining root?
Update: I have a fix for your WiFi issues. Others have also experienced this problem after rooting; the issue is due to an anomaly that occurs during the ramdisk patching process with Magisk. I've manually patched the boot image with Magisk, and fixed the ramdisk error. I will upload this updated patched boot image. Flash it via fastboot mode and your issue should resolve. I have also updated the boot.img.in the DOWNLOADS section above. Thanks for your feedback. Let me know if this resolves your issue. If not, I do have a full factory firmware image for this tablet so that you can flash to full stock and then root again using the new boot image.
Updated Patched Boot.img

@Viva La Android Excuse me for bothering, you don't have the firmware of the tablet right?

SamuEDL said:
@Viva La Android Excuse me for bothering, you don't have the firmware of the tablet right?
Click to expand...
Click to collapse
Yes I have it now. And you're no bother, friend. Is your model number HT8WB1RBK03? The reason I ask is because there are a couple of different variants to this particular tablet. I have added the link for the factory firmware image in the downloads section above. I will be posting a guide for firmware restoration very soon, using the PhoenixUSB Pro flash tool. Just ensure that your model number matches and, again, you're no bother. That's why I'm here. Feel free to ask if you need something. I'll help if able.

Viva La Android said:
Yes I have it now. And you're no bother, friend. Is your model number HT8WB1RBK03? The reason I ask is because there are a couple of different variants to this particular tablet. I have added the link for the factory firmware image in the downloads section above. I will be posting a guide for firmware restoration very soon, using the PhoenixUSB Pro flash tool. Just ensure that your model number matches and, again, you're no bother. That's why I'm here. Feel free to ask if you need something. I'll help if able.
Click to expand...
Click to collapse
Good morning, thanks for the rom. I don't have the tablet, but I am currently investigating tablet operation with the Allwinner a100/133. I hope you don't mind the answer and thanks for the rom.

SamuEDL said:
Good morning, thanks for the rom. I don't have the tablet, but I am currently investigating tablet operation with the Allwinner a100/133. I hope you don't mind the answer and thanks for the rom.
Click to expand...
Click to collapse
No problem at all. Yes the Allwinner A100 & A133 are being used in a number of Android tablets these days. If you need, I have two more firmwares for the A100 -- for the QLink Scepter 8 and the 7" Hyundai HYTab (7WB1). Let me know and I'll get you links.

Hello I have a very similar 10" tablet named SEBBE S23 which has the same a133 chipset and a11 go, i unlocked the bootloader following your steps but can't patch my boot with magisk because I can't find the original firmware of my device anywhere. Do you know if there is any tool or command to extract my boot image directly from the tablet? Thanks, and sorry for off-topic question.

Strike X iT said:
Hello I have a very similar 10" tablet named SEBBE S23 which has the same a133 chipset and a11 go, i unlocked the bootloader following your steps but can't patch my boot with magisk because I can't find the original firmware of my device anywhere. Do you know if there is any tool or command to extract my boot image directly from the tablet? Thanks, and sorry for off-topic question.
Click to expand...
Click to collapse
Greetings @Strike X iT. Without a factory firmware image from which to extract your stock boot image, there are a couple of other options -- but these options are somewhat risky and not guaranteed to work. In short, it is possible to end up with a device stuck in a boot loop. The key here is to obtain a boot image from a device with hardware specs that mirror the specs of your device. If you can find a perfect match, this alleviates any risk.
So, first and foremost, boot your tablet into legacy fastboot mode (not FastbootD dynamic fastboot mode). In other words, use the same fastboot mode that you used in my bootloader unlocking instructions. Connect to your PC or laptop, open a command window, and execute this command:
Code:
fastboot getvar all
The command window should yield several lines of info about your device. Post that info here. I will try to find you a matched boot image. The boot image listed in this guide may work to root your tablet, but I need to compare the specs to alleviate any potential risk. I have another tablet with an Allwinner-A133 as well, for which I have factory firmware. So maybe one of the two tablets will match a safe boot image with which you can attain root. Also, open device settings on your tablet, scroll down to About device, tap on the Android version, and find your kernel version. Post that here as well.

Thanks for your support i think could be odher rebrand of this tablet, i've seen plenty of them with similar specs on amazon btw this is the response of fastboot command
Spoiler: HERE
(bootloader) treble-enabled:true
(bootloader) first-api-level:30
(bootloader) dynamic-partition:true
(bootloader) system-fingerprint:SEBBE/S23_EEA/S23_EEA:11/RP1A.201005.006/20220408-172152:user/release-keys
(bootloader) snapshot-update-status:none
(bootloader) super-partition-name:super
(bootloader) hw-revision:0
(bootloader) off-mode-charge:0
(bootloader) battery-voltage:0
(bootloader) is-userspace:yes
(bootloader) partition-type:boot_b:raw
(bootloader) partition-type:bootloader_b:raw
(bootloader) partition-type:dtbo_a:raw
(bootloader) partition-type:vbmeta_system_b:raw
(bootloader) partition-type:userdata:raw
(bootloader) partition-type:vbmeta_vendor_b:raw
(bootloader) partition-type:env_a:raw
(bootloader) partition-type:bootloader_a:raw
(bootloader) partition-type:vbmeta_b:raw
(bootloader) partition-type:vendor_boot_b:raw
(bootloader) partition-type:dtbo_b:raw
(bootloader) partition-type:env_b:raw
(bootloader) partition-type:vendor_boot_a:raw
(bootloader) partition-type:misc:raw
(bootloader) partition-type:vbmeta_a:raw
(bootloader) partition-type:vbmeta_system_a:raw
(bootloader) partition-type:vbmeta_vendor_a:raw
(bootloader) partition-type:boot_a:raw
(bootloader) partition-type:metadata:raw
(bootloader) partition-type:super:raw
(bootloader) partition-type:system_a:raw
(bootloader) partition-type:system_b:raw
(bootloader) partition-type:vendor_a:raw
(bootloader) partition-type:vendor_b:raw
(bootloader) partition-typeroduct_a:raw
(bootloader) partition-typeroduct_b:raw
(bootloader) secure:yes
(bootloader) battery-soc-ok:yes
(bootloader) serialno:S232022HGM188XXXX
(bootloader) slot-count:2
(bootloader) cpu-abi:armeabi-v7a
(bootloader) variant:NA
(bootloader) has-slot:boot:yes
(bootloader) has-slot:bootloader:yes
(bootloader) has-slot:dtbo:yes
(bootloader) has-slot:vbmeta_system:yes
(bootloader) has-slot:userdata:no
(bootloader) has-slot:vbmeta_vendor:yes
(bootloader) has-slot:env:yes
(bootloader) has-slot:vbmeta:yes
(bootloader) has-slot:vendor_boot:yes
(bootloader) has-slot:misc:no
(bootloader) has-slot:metadata:no
(bootloader) has-slot:super:no
(bootloader) has-slot:system:yes
(bootloader) has-slot:vendor:yes
(bootloader) has-slotroduct:yes
(bootloader) product:S23_EEA
(bootloader) is-logical:boot_b:no
(bootloader) is-logical:bootloader_b:no
(bootloader) is-logical:dtbo_a:no
(bootloader) is-logical:vbmeta_system_b:no
(bootloader) is-logical:userdata:no
(bootloader) is-logical:vbmeta_vendor_b:no
(bootloader) is-logical:env_a:no
(bootloader) is-logical:bootloader_a:no
(bootloader) is-logical:vbmeta_b:no
(bootloader) is-logical:vendor_boot_b:no
(bootloader) is-logical:dtbo_b:no
(bootloader) is-logical:env_b:no
(bootloader) is-logical:vendor_boot_a:no
(bootloader) is-logical:misc:no
(bootloader) is-logical:vbmeta_a:no
(bootloader) is-logical:vbmeta_system_a:no
(bootloader) is-logical:vbmeta_vendor_a:no
(bootloader) is-logical:boot_a:no
(bootloader) is-logical:metadata:no
(bootloader) is-logical:super:no
(bootloader) is-logical:system_a:yes
(bootloader) is-logical:system_b:yes
(bootloader) is-logical:vendor_a:yes
(bootloader) is-logical:vendor_b:yes
(bootloader) is-logicalroduct_a:yes
(bootloader) is-logicalroduct_b:yes
(bootloader) vendor-fingerprint:SEBBE/S23_EEA/S23_EEA:11/RP1A.201005.006/20220408-172152:user/release-keys
(bootloader) version-vndk:30
(bootloader) unlocked:yes
(bootloader) current-slot:a
(bootloader) version-os:11
(bootloader) version-baseband:
(bootloader) max-download-size:0x10000000
(bootloader) partition-size:boot_b:0x4000000
(bootloader) partition-size:bootloader_b:0x2000000
(bootloader) partition-size:dtbo_a:0x200000
(bootloader) partition-size:vbmeta_system_b:0x10000
(bootloader) partition-size:userdata:0x67037BE00
(bootloader) partition-size:vbmeta_vendor_b:0x10000
(bootloader) partition-size:env_a:0x40000
(bootloader) partition-size:bootloader_a:0x2000000
(bootloader) partition-size:vbmeta_b:0x20000
(bootloader) partition-size:vendor_boot_b:0x2000000
(bootloader) partition-size:dtbo_b:0x200000
(bootloader) partition-size:env_b:0x40000
(bootloader) partition-size:vendor_boot_a:0x2000000
(bootloader) partition-size:misc:0x1000000
(bootloader) partition-size:vbmeta_a:0x20000
(bootloader) partition-size:vbmeta_system_a:0x10000
(bootloader) partition-size:vbmeta_vendor_a:0x10000
(bootloader) partition-size:boot_a:0x4000000
(bootloader) partition-size:metadata:0x1000000
(bootloader) partition-size:super:0xC0000000
(bootloader) partition-size:system_a:0x3D36B000
(bootloader) partition-size:system_b:0x0
(bootloader) partition-size:vendor_a:0x4CF9000
(bootloader) partition-size:vendor_b:0x0
(bootloader) partition-sizeroduct_a:0x49D1F000
(bootloader) partition-sizeroduct_b:0x0
(bootloader) security-patch-level:2022-02-05
(bootloader) version-bootloader:unknown
(bootloader) version:0.4
all:
Finished. Total time: 0.404s
and this is the kernel version
Spoiler: HERE
hope you can find something useful

Strike X iT said:
Thanks for your support i think could be odher rebrand of this tablet, i've seen plenty of them with similar specs on amazon btw this is the response of fastboot command
Spoiler: HERE
(bootloader) treble-enabled:true
(bootloader) first-api-level:30
(bootloader) dynamic-partition:true
(bootloader) system-fingerprint:SEBBE/S23_EEA/S23_EEA:11/RP1A.201005.006/20220408-172152:user/release-keys
(bootloader) snapshot-update-status:none
(bootloader) super-partition-name:super
(bootloader) hw-revision:0
(bootloader) off-mode-charge:0
(bootloader) battery-voltage:0
(bootloader) is-userspace:yes
(bootloader) partition-type:boot_b:raw
(bootloader) partition-type:bootloader_b:raw
(bootloader) partition-type:dtbo_a:raw
(bootloader) partition-type:vbmeta_system_b:raw
(bootloader) partition-type:userdata:raw
(bootloader) partition-type:vbmeta_vendor_b:raw
(bootloader) partition-type:env_a:raw
(bootloader) partition-type:bootloader_a:raw
(bootloader) partition-type:vbmeta_b:raw
(bootloader) partition-type:vendor_boot_b:raw
(bootloader) partition-type:dtbo_b:raw
(bootloader) partition-type:env_b:raw
(bootloader) partition-type:vendor_boot_a:raw
(bootloader) partition-type:misc:raw
(bootloader) partition-type:vbmeta_a:raw
(bootloader) partition-type:vbmeta_system_a:raw
(bootloader) partition-type:vbmeta_vendor_a:raw
(bootloader) partition-type:boot_a:raw
(bootloader) partition-type:metadata:raw
(bootloader) partition-type:super:raw
(bootloader) partition-type:system_a:raw
(bootloader) partition-type:system_b:raw
(bootloader) partition-type:vendor_a:raw
(bootloader) partition-type:vendor_b:raw
(bootloader) partition-typeroduct_a:raw
(bootloader) partition-typeroduct_b:raw
(bootloader) secure:yes
(bootloader) battery-soc-ok:yes
(bootloader) serialno:S232022HGM188XXXX
(bootloader) slot-count:2
(bootloader) cpu-abi:armeabi-v7a
(bootloader) variant:NA
(bootloader) has-slot:boot:yes
(bootloader) has-slot:bootloader:yes
(bootloader) has-slot:dtbo:yes
(bootloader) has-slot:vbmeta_system:yes
(bootloader) has-slot:userdata:no
(bootloader) has-slot:vbmeta_vendor:yes
(bootloader) has-slot:env:yes
(bootloader) has-slot:vbmeta:yes
(bootloader) has-slot:vendor_boot:yes
(bootloader) has-slot:misc:no
(bootloader) has-slot:metadata:no
(bootloader) has-slot:super:no
(bootloader) has-slot:system:yes
(bootloader) has-slot:vendor:yes
(bootloader) has-slotroduct:yes
(bootloader) product:S23_EEA
(bootloader) is-logical:boot_b:no
(bootloader) is-logical:bootloader_b:no
(bootloader) is-logical:dtbo_a:no
(bootloader) is-logical:vbmeta_system_b:no
(bootloader) is-logical:userdata:no
(bootloader) is-logical:vbmeta_vendor_b:no
(bootloader) is-logical:env_a:no
(bootloader) is-logical:bootloader_a:no
(bootloader) is-logical:vbmeta_b:no
(bootloader) is-logical:vendor_boot_b:no
(bootloader) is-logical:dtbo_b:no
(bootloader) is-logical:env_b:no
(bootloader) is-logical:vendor_boot_a:no
(bootloader) is-logical:misc:no
(bootloader) is-logical:vbmeta_a:no
(bootloader) is-logical:vbmeta_system_a:no
(bootloader) is-logical:vbmeta_vendor_a:no
(bootloader) is-logical:boot_a:no
(bootloader) is-logical:metadata:no
(bootloader) is-logical:super:no
(bootloader) is-logical:system_a:yes
(bootloader) is-logical:system_b:yes
(bootloader) is-logical:vendor_a:yes
(bootloader) is-logical:vendor_b:yes
(bootloader) is-logicalroduct_a:yes
(bootloader) is-logicalroduct_b:yes
(bootloader) vendor-fingerprint:SEBBE/S23_EEA/S23_EEA:11/RP1A.201005.006/20220408-172152:user/release-keys
(bootloader) version-vndk:30
(bootloader) unlocked:yes
(bootloader) current-slot:a
(bootloader) version-os:11
(bootloader) version-baseband:
(bootloader) max-download-size:0x10000000
(bootloader) partition-size:boot_b:0x4000000
(bootloader) partition-size:bootloader_b:0x2000000
(bootloader) partition-size:dtbo_a:0x200000
(bootloader) partition-size:vbmeta_system_b:0x10000
(bootloader) partition-size:userdata:0x67037BE00
(bootloader) partition-size:vbmeta_vendor_b:0x10000
(bootloader) partition-size:env_a:0x40000
(bootloader) partition-size:bootloader_a:0x2000000
(bootloader) partition-size:vbmeta_b:0x20000
(bootloader) partition-size:vendor_boot_b:0x2000000
(bootloader) partition-size:dtbo_b:0x200000
(bootloader) partition-size:env_b:0x40000
(bootloader) partition-size:vendor_boot_a:0x2000000
(bootloader) partition-size:misc:0x1000000
(bootloader) partition-size:vbmeta_a:0x20000
(bootloader) partition-size:vbmeta_system_a:0x10000
(bootloader) partition-size:vbmeta_vendor_a:0x10000
(bootloader) partition-size:boot_a:0x4000000
(bootloader) partition-size:metadata:0x1000000
(bootloader) partition-size:super:0xC0000000
(bootloader) partition-size:system_a:0x3D36B000
(bootloader) partition-size:system_b:0x0
(bootloader) partition-size:vendor_a:0x4CF9000
(bootloader) partition-size:vendor_b:0x0
(bootloader) partition-sizeroduct_a:0x49D1F000
(bootloader) partition-sizeroduct_b:0x0
(bootloader) security-patch-level:2022-02-05
(bootloader) version-bootloader:unknown
(bootloader) version:0.4
all:
Finished. Total time: 0.404s
and this is the kernel version
Spoiler: HERE
View attachment 5725133
hope you can find something useful
Click to expand...
Click to collapse
I'm guessing by the status bar icons from the screen shot you posted that your tablet is WiFi only, just like the Hyundai tablet in this thread? If so, the boot image in this thread -- which is already patched via Magisk -- should root your tablet. The kernel version on this tablet is also 5.4.99. I foresee no problems with this boot image rooting your tablet, but you know the risks. All I can confirm is that the specs are a match. Your display is larger, but the display drivers are no longer handled directly by the kernel, but by a separate proprietary vendor-specific partition. So the display size difference should not be a problem. At the end of the day, the choice is yours. Good thing about Allwinner tablets is they are almost impossible to hard brick. They have a hardware embedded boot ROM protocol known as FEL mode.

do you have a guide for the hyundai 8lab1 model?. thanks.

xsebas said:
do you have a guide for the hyundai 8lab1 model?. thanks.
Click to expand...
Click to collapse
Do you mean the 8LB1? The 4G-LTE model of this tablet, correct? In order to root your variant, you will need to obtain a stock boot image for your device. I can reach out to Hyundai Mobile to get your stock firmware, which includes the boot image you need. Open device Settings>About tablet and tap on your Android versIon. Your build number will be displayed. This is what I need to request your firmware from Hyundai.

Viva La Android said:
Do you mean the HLB1? The 4G-LTE model of this tablet, correct? In order to root your variant, you will need to obtain a stock boot image for your device. I can reach out to Hyundai Mobile to get your stock firmware. Open device Settings>About tablet and tap on your Android versIon. Your build number will be displayed. This is what I need to request your firmware from Hyundai.
Click to expand...
Click to collapse
yeah i think it is.

xsebas said:
yeah i think it is.
Click to expand...
Click to collapse
Ok post your build number please.

Viva La Android said:
Ok post your build number please.
Click to expand...
Click to collapse
Its android 10

xsebas said:
Its android 10
Click to expand...
Click to collapse
I know that. I need your build number. Tap on the Android version and it'll bring up your build number.

Viva La Android said:
Do you mean the 8LB1? The 4G-LTE model of this tablet, correct? In order to root your variant, you will need to obtain a stock boot image for your device. I can reach out to Hyundai Mobile to get your stock firmware, which includes the boot image you need. Open device Settings>About tablet and tap on your Android versIon. Your build number will be displayed. This is what I need to request your firmware from Hyundai.
Click to expand...
Click to collapse
Sorry its in spanish but i took a picture

xsebas said:
Sorry its in spanish but i took a picture
Click to expand...
Click to collapse
Thanks. That's exactly what I needed. I will put in a formal request for your firmware with Hyundai Mobile. They are usually pretty quick about getting it for me. As soon as I know something I'll post here with an update.

Viva La Android said:
Thanks. That's exactly what I needed. I will put in a formal request for your firmware with Hyundai Mobile. They are usually pretty quick about getting it for me. As soon as I know something I'll post here with an update.
Click to expand...
Click to collapse
Thank you very much. You saved me.