Database Info

[Q] IMEI 0 needs to recovery WHO CAN HELP?

Hi everyone,
i recieved yesterday my Moto G, 16GB,Retailversion, bought and live in Germany, bought used. Everything works well on it. This phone comes with KITKAT 4.4.2 with an unlocked bootloader, CMW and Superuser.
The phone is resettet, all clear. The only thing is, that the IMEI=0
The phone is on the latest german 175.44.1.falcon_umts.RETAIL.en.DE
Build Number: KLB20.9.10-1.9.1
If i am move with this phone the signal will be 1 to 5 or loss. If this phone is placed on my desk it chows the whole day 3 to 5 signalbars.
I tried to use this command in terminal or adb: echo 'AT +EGMR=1,7,"XXXXXXXXXXXXXXXX"> /dev/pttycmd1 but no success.
I have currently no backup from this phone, i have the IMEI of this phone.
Who can help me to write my original IMEI back to phone? This is quite urgent. PLEASE HELP ME OUT.
Thanks

How much did you pay for it you can try flashing stock ROM or firmware to see if you can recover imei
Sent from my XT1034 using xda app-developers app

serophia said:
How much did you pay for it you can try flashing stock ROM or firmware to see if you can recover imei
Sent from my XT1034 using xda app-developers app
Click to expand...
Click to collapse
I got quite the same problem, tried that many times, flashed different stock and custom roms, radio images, nothing worked..
Quite bad to have such a great "Tablet".. I'd really need to use the normal phone functions..

i think we need a imei backup from someone and change the imei to our original one. WHO can help us please?
Some files are missing in root, same was with wifi before, i found a file, that changes the state, but phone signal doesn't comming back without help.

From fastoboot you can get:
Fastboot getvar imei (you can view you imei)
Fastoboot oem writeimei your imei. (Take original imei from box)
You must have bootloader unlocked

cicciocant said:
From fastoboot you can get:
Fastboot getvar imei (you can view you imei)
Fastoboot oem writeimei your imei. (Take original imei from box)
You must have bootloader unlocked
Click to expand...
Click to collapse
If I try this it just gets out
FAILED (remote failure)
finished. total time: 0.020s

RestlessScreams said:
If I try this it just gets out
FAILED (remote failure)
finished. total time: 0.020s
Click to expand...
Click to collapse
hi, i did this command: Fastboot getvar imei
IMEI is listed correctly , but i can't do this command after too: Fastoboot oem writeimei "your imei"
Same problem as user "RestlessScreams"
FAILED (remote failure)
finished. total time: 0.016s

Jerome-X said:
hi, i did this command: Fastboot getvar imei
IMEI is listed correctly , but i can't do this command after too: Fastoboot oem writeimei "your imei"
Same problem as user "RestlessScreams"
FAILED (remote failure)
finished. total time: 0.016s
Click to expand...
Click to collapse
Try using :
fastboot oem writeimei "your imei".... I think "cicciocant" made a typo, if i'm not mistaken.

mardobloom said:
Try using :
fastboot oem writeimei "your imei".... I think "cicciocant" made a typo, if i'm not mistaken.
Click to expand...
Click to collapse
This is what i got in fastboot: (fastboot.exe getvar all)
(bootloader) version: 0.5
(bootloader) version-bootloader: 4105
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 16GB Toshiba REV=06 PRV=01 TYPE=17
(bootloader) ram: 1024MB Hynix S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: TA8900FI4F
(bootloader) cid: 0x0007
(bootloader) uid: 28F911020F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 3X5XX2X5XX16XX7 (the IMEI is shown correctly)
(bootloader) meid:
(bootloader) date: 12-26-2013
(bootloader) sku: XT1032
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Feb 24 8:58:15 UTC 2014"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_retde/falcon_umts:
(bootloader) ro.build.fingerprint[1]: 4.4.2/KLB20.9-1.10-1.24-1.1/1:user
(bootloader) ro.build.fingerprint[2]: /release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.176.44.1.falcon_umts
(bootloader) ro.build.version.full[1]: .Retail.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-gf3bf
(bootloader) kernel.version[1]: 628 ([email protected]) (gcc version 4.
(bootloader) kernel.version[2]: 7 (GCC) ) #1 SMP PREEMPT Thu Feb 6 23:07
(bootloader) kernel.version[3]: :13 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.062s
but IMEI shows 0 while running system.
No signal, no provider, only WIFI is useable

You van try this:
http://forum.xda-developers.com/showthread.php?t=2623587
Inviato dal mio XT1032 utilizzando Tapatalk

doesent work, how to get my imei back? any possible solution here let me not write my imei back to phone. Why do i see my imei in fastbootmode and not in Android OS?
Gesendet von meinem LG-D802 mit Tapatalk

Got same problem since three weeks.
Tried re flashing stock, changing radio, break fastboot... Nothing worked, i was going to give it back to Motorola but i see many people got same problem so I think i'll wait a bit for a potential solution.
Getvar all gave me correct imei, system shows 0.
Sent from my XT1032 using Tapatalk
---------- Post added at 08:09 AM ---------- Previous post was at 07:39 AM ----------
sorry to add more to my previous reply:
"AT +EGMR=1,7,"XXXXXXXXXXXXXXXX"> /dev/pttycmd1" only works for MTK based phones.
And
writeimei isn't supported in fastboot
I was thinking if there is a way to physically remove battery from Moto G, haven't found any in google

Did you flash your phone without Sim Card?
If i understand this statement right, he had the same problem while flashing his phone without sim card.
herbesi01 said:
I solved the problem, place to charge the phone, let him take some of the load and flash the original ROM, after that flash CM11, and run perfectmente, I think at first it was because I had done without the SIM, the second time you make with the SIM sunset ...
Click to expand...
Click to collapse

mokkami said:
Did you flash your phone without Sim Card?
If i understand this statement right, he had the same problem while flashing his phone without sim card.
Click to expand...
Click to collapse
I tried flashing always with SIM Card on it, i even changed Cards but still 0 imei.

Maybe this is compatible with Moto G?!

The go back to stock without SIM, skip all and going home, boot off, reinsert another SIM isn't working.
will try other solutions, i hope

any news, about restore IMEI?

Jerome-X said:
any news, about restore IMEI?
Click to expand...
Click to collapse
Not yet unluckly...

Edit

mokkami said:
Maybe this is compatible with Moto G?!
Click to expand...
Click to collapse
DId someone try ?

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.

Flashing Problem (Bricked phone)

Dear,
I bought a mobile XT1032 in Chile and had the bright idea to install Android 5.0.0, but before that should turn my phone GPE and worked smoothly for about two months, but a few weeks ago the screen began to random failures for example the phone is locked and unlocked without my intervention or the screen, the phone is locked, blinking (as it had voltage changes, such as when you move a flashlight with almost empty and this flashing batteries). I decided to go back to Android 4.4.4 Stock, however this time I did the procedure without considering the consequences, I first downloaded and installed the GPE 4.4.4, then downloaded and installed the Stock Brasil 4.4.4, then tried to go back to stock Movistar Chile but failed to find the 4.4.4 nowhere, so I decided to install the 4.4.3. My mistake. After that my phone did not work more.
Now if I switch it displays the message "Unlocked Bootloader" then shows motorola logos (the world turning) and then the screen goes black but not off (note that is on because it has brightness and that was with that flicker as if he had mentioned voltage failures) but this does not show anything.
I tried installing all the tutorials I found on the internet to revive my phone, I got about 15 different roms and nothing works. I can enter fastboot and no problems (strangely fastboot screen does not flash, it is as if he had nothing wrong), I can also enter recovery (either in recovery flashing display). If I make a recovery "wipe data / factory reset" does well, but if I do "wipe reset partition" android logo shows the blue loading bar appears 2 seconds and the phone reboots.
I not been possible to change the recovery of stock for some other recovery (eg Philz) because although fastboot or mfastboot shows that the process was well (sometimes shown on the phone that is making a downgrade) this does not change the recovery.
Currently my phone is flashed (at least it is assumed that no starts beyond the worlds of motorola) with Android 5.0.2 I downloaded some other forum.
I think, without knowing for sure, for more than I try with the common commands this dont "touch" or change the system version. It's like I always show as well (including with commands in cmd and phone) but practically nothing happened.
I appreciate any guidance to solve my problem.
I attach a "getall var" from my phone
-----------------------------
C:\WorkingMotoG>mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 4118
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 16GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: TA9300B3Y4
(bootloader) cid: 0x000C
(bootloader) channelid: 0x00
(bootloader) uid: D3BDB4030F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 15 12:11:29 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_tefcl/falcon_umts:
(bootloader) ro.build.fingerprint[1]: 4.4.4/KXB21.14-L1.40/37:user/relea
(bootloader) ro.build.fingerprint[2]: se-keys
(bootloader) ro.build.version.full[0]: Blur_Version.210.12.40.falcon_umt
(bootloader) ro.build.version.full[1]: s.Movistar.en.CL
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.020
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-gb89c9dd ([email protected]
(bootloader) kernel.version[1]: ilclbld31) (gcc version 4.7 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Fri Jun 20 01:58:53 CDT 2014
(bootloader) sdi.git: git=MBM-NG-V41.18-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.18-0-g5742832
(bootloader) rpm.git: git=MBM-NG-V41.18-0-gcecd6e9
(bootloader) tz.git: git=MBM-NG-V41.18-0-g99c1a7c
(bootloader) aboot.git: git=MBM-NG-V41.18-0-g99084d5
(bootloader) qe: qe 0/1
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.059s

Are you manually flashing each file/partition? You will get a validation error if you try to flash the motoboot file since you are already on a lollipop bootloader. A very important file to flash in my opinion is gpt.bin.
If you want a custom recovery on your phone, flash the recovery in fastboot or mfastboot, disconnect the USB cable, use the volume buttons to immediately boot into recovery without restarting the phone.

audit13 said:
Are you manually flashing each file/partition? You will get a validation error if you try to flash the motoboot file since you are already on a lollipop bootloader. A very important file to flash in my opinion is gpt.bin.
If you want a custom recovery on your phone, flash the recovery in fastboot or mfastboot, disconnect the USB cable, use the volume buttons to immediately boot into recovery without restarting the phone.
Click to expand...
Click to collapse
All the files loads OK, gpt.bin with exception of boot.img, it says: "version downgraded for boot" in the phone.
BTW: I do what you say about recovery and keep showing stock recovery. Dont show error messages, just no work.
Thanks anyway for you time...

Which recovery are you trying to flash?
So you flash custom recovery, use volumes button to boot to recovery from fastboot screen and you keep getting stock recovery, right?

audit13 said:
Which recovery are you trying to flash?
So you flash custom recovery, use volumes button to boot to recovery from fastboot screen and you keep getting stock recovery, right?
Click to expand...
Click to collapse
I'm trying to flash philz_touch_6.58.7-falcon.img
Thanks for your time

Did you try TWRP?

audit13 said:
Did you try TWRP?
Click to expand...
Click to collapse
Yes, but dont work neither

So both recoveries flash without an error but you can't boot into either receiver right after flashing?
If it doesn't work, there may be something wrong with the internal memory?

audit13 said:
So both recoveries flash without an error but you can't boot into either receiver right after flashing?
If it doesn't work, there may be something wrong with the internal memory?
Click to expand...
Click to collapse
Now my phone is recognized by Windows as "Qualcomm HS-USB QDLoader 9008". I try to fla**** with MotoFlasher and says:
OUTPUT: opening device: \\.\COM12
OUTPUT: OKAY [ 0.000s]
OUTPUT: greeting device for command mode
OUTPUT: OKAY [ -0.000s]
OUTPUT: identifying device
OUTPUT: ...serial = 0x3B4BDD3
OUTPUT: ...chip-id = 0x800 (MSM8226)
OUTPUT: ...chip-rev = 0x0
OUTPUT: ...sv-sbl = 0x0
OUTPUT: OKAY [ 0.002s]
OUTPUT: finding files
OUTPUT: ...programmer = programmer.mbn
OUTPUT: ...singleimage = singleimage.bin
OUTPUT: OKAY [ 0.000s]
OUTPUT: validating files
OUTPUT: OKAY [ 0.000s]
OUTPUT: switching to download mode
OUTPUT: OKAY [ 0.000s]
OUTPUT: greeting device for image downloading
OUTPUT: OKAY [ 0.001s]
OUTPUT: sending programmer
OUTPUT: OKAY [ 0.010s]
OUTPUT: flashing singleimage
OUTPUT: FAILED (blank-flash:sdl-transfer-image:sdl-hello:invalid HDLC frame)
OUTPUT:
OUTPUT:

That's not good. You may have to try the unbrick method to fix it.

audit13 said:
That's not good. You may have to try the unbrick method to fix it.
Click to expand...
Click to collapse
Which method? Can you gave me instructions or a link, please...?

http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798

flashing with fastboot does nothing

My moto g get stucked on a blank screen after the motorola logo animation.
I tried going into the recovery and wiping data and cache. Nothing happened.
I tried unlocking the bootloader --> No problem, it's unlocked now.
I tried reflashing the stock ROM via fastboot. Apparently all goes OKAY, all commands pass without problems, but when I reboot, still a blank screen.
I tried flashing a new ROM (5.0.2 Lollipop). Same problem, apparently it flashes everything ok but when reboots... nothing.
I tried to update only the recovery to ither Team Wins or Clockwork, they flash without problems but when I go to the recovery I get the stock one (I didnt reboot the phone went straight to recovery after flashing, and tried rebooting the phone as well).
I also tried to update only the bootloader (right now I'm at 41.13) tried to update it to 41.18, same problem... Apparently it flashes but when I reboot I still get the 41.13
Finally, I tried to hard-brick my phone using the Bootloader Bricker Tool posted here: http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798 and nothing happened.
So basically, it seems that everything I do via fastboot (or mfastboot - I tried both) it goes through without problems, but then it either reverts back to stock when the phone reboots or actually it doesnt write anything.
Any help, will be greatly appreaciated.
This is my getvar:all
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 4113
(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: T09290UV3C
(bootloader) cid: 0x000C
(bootloader) channelid: 0x00
(bootloader) uid: ADC65E030F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Jun 26 18: 9:42 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_amxar/falcon_umts:
(bootloader) ro.build.fingerprint[1]: 4.4.4/KXB21.14-L1.40/37:user/relea
(bootloader) ro.build.fingerprint[2]: se-keys
(bootloader) ro.build.version.full[0]: Blur_Version.210.12.40.falcon_umt
(bootloader) ro.build.version.full[1]: s.AmericaMovil.en.AR
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.020
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-gb89c9dd ([email protected]
(bootloader) kernel.version[1]: ilclbld28) (gcc version 4.7 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Fri Jun 20 04:31:45 CDT 2014
(bootloader) sdi.git: git=MBM-NG-V41.13-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.13-0-g683cb0c
(bootloader) rpm.git: git=MBM-NG-V41.13-0-g71b1aae
(bootloader) tz.git: git=MBM-NG-V41.13-0-ga27c415
(bootloader) aboot.git: git=MBM-NG-V41.13-0-g7dc8e78
(bootloader) qe: qe 0/1
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.057s

Sounds like possible Bootloader corruption. I would try again with the unbrick tool. Best ask in the thread. Avoid trying to update Bootloader (motoboot.img) - Lollipop is not supported.
Here is the exact 4.4.2 Firmware Image:
http://www.filefactory.com/file/793...9_7_release-keys-cid12-AmericaMovil_AR.tar.gz

Thanks for the reply.
Ok, I'll head over to the unbrick thread again. The thing is my phone doesn't seem to be hard-bricked, because it boots to bootlader and it's not recognized by the PC as "qhsusb_bulk" in Device Manager.
That's why I tried to "brick" it using the tool on that thread, but it didnt get bricked at all :\

The unbrick tool should allow you to restore the Bootloader - if it is indeed corrupted.

lost101 said:
The unbrick tool should allow you to restore the Bootloader - if it is indeed corrupted.
Click to expand...
Click to collapse
I tried it several times now... The problem is that my phone is not being detected by Windows as "qhsusb_bulk" in the Device Manager. So I can't do what the instructions tell me to do.
So I used the Bootloader Bricer Tool
oversleeper said:
Bootloader Bricker Tool: If the previous tool had no effect or you think your bootloader is seriously damaged, this script will make your phone recognized as "qhsusb_bulk" so you can perform a blank flash
Click to expand...
Click to collapse
And this is what I get:
Code:
WARNING: READ CAREFULLY BEFORE YOU PROCEED!
THIS SCRIPT WILL DESTROY THE BOOTLOADER OF YOUR DEVICE.
DO NOT ATTEMPT TO USE UNLESS YOU'RE SURE ABOUT WHAT YOU'RE DOING.
ONLY YOU ARE RESPONSIBLE FOR YOUR ACTIONS.
Do you want to continue [Y/N]?Y
target max-sparse-size: 256MB
sending 'sbl1' (264 KB)...
OKAY [ 0.033s]
writing 'sbl1'...
OKAY [ 0.031s]
finished. total time: 0.067s
rebooting...
finished. total time: 0.002s
Your device is now hard bricked!
When it automatically reboots, it's like nothing happened: motorola logo, full animation, then blank screen. I can still enter the bootloader, run fastboot commands, etc etc...

epexy said:
I tried it several times now... The problem is that my phone is not being detected by Windows as "qhsusb_bulk" in the Device Manager. So I can't do what the instructions tell me to do.
So I used the Bootloader Bricer Tool
And this is what I get:
Code:
WARNING: READ CAREFULLY BEFORE YOU PROCEED!
THIS SCRIPT WILL DESTROY THE BOOTLOADER OF YOUR DEVICE.
DO NOT ATTEMPT TO USE UNLESS YOU'RE SURE ABOUT WHAT YOU'RE DOING.
ONLY YOU ARE RESPONSIBLE FOR YOUR ACTIONS.
Do you want to continue [Y/N]?Y
target max-sparse-size: 256MB
sending 'sbl1' (264 KB)...
OKAY [ 0.033s]
writing 'sbl1'...
OKAY [ 0.031s]
finished. total time: 0.067s
rebooting...
finished. total time: 0.002s
Your device is now hard bricked!
When it automatically reboots, it's like nothing happened: motorola logo, full animation, then blank screen. I can still enter the bootloader, run fastboot commands, etc etc...
Click to expand...
Click to collapse
I have two devices with the same problem as yours, one = motorola logo -> full animation -> black screen. And another boots up normally, but have a forgotten password, but if I try to enter recovery mode then "Boot Up Failed" message appear, and after I flash the device (and use erase userdata command), the device still have the password and all data apparently (the device boot up fast too).
The only thing that seems to work with fastboot is unlocking bootloader, and relock fails (even showing sucessful)
No one have this problems and have solutions ?????

I have the exact same problem. Was on a slim6 rom before. Tried to return to STOCK_ASIA_RETAIL. All fastboot commands successfully executed but no apparent change. I have the exact same wallpaper, the same layers RRO navbars, everything. I would not need to go to STOCK but since the slim installation is unstable and everything force closes, the phone is unusable.
Additional note: Somehow even TWRP is stuck in the splash screen, so cant flash any other ROM. Even tried to access TWRP using adb, but the TWRP service fails to start.
I fastboot flashed phillz recovery, stock recovery & newer TWRP versions, but nothing happens. Phone still stuck in TWRP screen.
To my surprise I was able to pull my personal files from the internal SD using ADB (which still works btw).
But I'm left with a phone in a zombie unusable condition, it just doesn't react to anything.
Any help from the XDA community would be greatly appreciated. I am still keeping my fingers crossed, so that one day a guide comes up to brick my device (STOCK 5.1 bootloader) and unbrick it using some sort of unbrick tool.

[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.