Related
Hi there,
I have a TF300T which I am trying to unlock. I downloaded the Asus APK file, and initially it did not work. After a bit of troubleshooting I was able to get it to work by registering my device on the Asus website.
However, even though the application ran, the bootloader is not unlocked.
Code:
C:\Program Files\android_sdk\sdk\platform-tools>fastboot -i 0x0b05 getvar all
(bootloader) version-bootloader: 1.0
(bootloader) version-baseband: 2.0
(bootloader) version: 0.4
(bootloader) serialno: 015d15b51c0c0e04
(bootloader) mid: 001
(bootloader) product: Cardhu
(bootloader) secure: yes
[B][COLOR="Red"](bootloader) unlocked: no[/COLOR][/B]
(bootloader) uart-on: yes
(bootloader) partition-size:bootloader: 0x0000000000800000
(bootloader) partition-type:bootloader: basic
(bootloader) partition-size:recovery: 0x0000000000800000
(bootloader) partition-type:recovery: basic
(bootloader) partition-size:boot: 0x0000000000800000
(bootloader) partition-type:boot: basic
(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.104s
Each time I run the Unlocking application from Asus, I get a toast message saying "Device is unlocked". I take this to mean that the APK has detected somehow that the bootloader is unlocked and doesn't attempt to unlock the device.
I tried using an older version of the Unlock tool (Version 7 instead of 8) but it's the same problem.
Has anyone had this issue before? Any ideas?
CatalystNZ said:
Hi there,
I have a TF300T which I am trying to unlock. I downloaded the Asus APK file, and initially it did not work. After a bit of troubleshooting I was able to get it to work by registering my device on the Asus website.
However, even though the application ran, the bootloader is not unlocked.
Code:
C:\Program Files\android_sdk\sdk\platform-tools>fastboot -i 0x0b05 getvar all
(bootloader) version-bootloader: 1.0
(bootloader) version-baseband: 2.0
(bootloader) version: 0.4
(bootloader) serialno: 015d15b51c0c0e04
(bootloader) mid: 001
(bootloader) product: Cardhu
(bootloader) secure: yes
[B][COLOR="Red"](bootloader) unlocked: no[/COLOR][/B]
(bootloader) uart-on: yes
(bootloader) partition-size:bootloader: 0x0000000000800000
(bootloader) partition-type:bootloader: basic
(bootloader) partition-size:recovery: 0x0000000000800000
(bootloader) partition-type:recovery: basic
(bootloader) partition-size:boot: 0x0000000000800000
(bootloader) partition-type:boot: basic
(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.104s
Each time I run the Unlocking application from Asus, I get a toast message saying "Device is unlocked". I take this to mean that the APK has detected somehow that the bootloader is unlocked and doesn't attempt to unlock the device.
I tried using an older version of the Unlock tool (Version 7 instead of 8) but it's the same problem.
Has anyone had this issue before? Any ideas?
Click to expand...
Click to collapse
I'm not home, if no one helps you by time I get home I will. But I believe there's a modified apk or an apk not from Asus here on the forums for unlocking the boot loader. That's what I used when I unlocked my tf300t, not the one from Asus.
Edit. I just saw you said you used v7 and 8, don't remember if it's needed but is USB debugging on?
Sent from my LG-P769 using Tapatalk
I can't find any tools other than the official Asus one
CatalystNZ said:
I can't find any tools other than the official Asus one
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2094746&page=1
Try that toolkit
Sent from my LG-P769 using Tapatalk
I tried the toolkit, all it does is install the official Asus Unlock app... which as before, tells me that it has worked, however it does not actually unlock the device
CatalystNZ said:
I tried the toolkit, all it does is install the official Asus Unlock app... which as before, tells me that it has worked, however it does not actually unlock the device
Click to expand...
Click to collapse
After some quick reading, if I understood correctly some people weren't able to unlock till a day or 2 later, and the Asus registration was suspected to be the issue like it takes a day or something to register in their system. Wait till tomorrow if you can and try again and if it still doesn't work I'll see what else I can find.
Sent from my LG-P769 using Tapatalk
When you boot up your device does it say Your device is unlocked in the top left? If it does, then it actually is unlocked.
Sent from my GS3 on 4.4 KitKat using Tapatalk 4
Actually fastboot doesn't see our bootloader status, so only hint is "device is unlocked" line during boot.
No, unfortunately I do not see the message when booting up. And all attempts to flash an unsigned Recovery image fail with the message
Code:
C:\Program Files\android_sdk\sdk\platform-tools>fastboot -i 0x0B05 flash recovery recovery.img
sending 'recovery' (6890 KB)...
OKAY [ 2.666s]
writing 'recovery'...
[COLOR="Red"][B]FAILED (remote: (InvalidState))[/B][/COLOR]
finished. total time: 5.215s
I have tried flashing TWRP, and have tried a couple of versions intended for 4.2, none have worked, all with the same error.
My suspicion is that the Unlock tool only works one time per device. Mine failed during the initial unlock and now my device is flagged as unlocked on the Asus servers and cannot be unlocked again. This makes sense, otherwise people could spoof/change their device serial number and a cracked version of the Unlock tool could be made which would not void your warranty on the Asus side.
I feel like my only hope is to contact Asus, however I don't feel hopeful about that. This is the sort of thing which makes me not recommend Asus.
If they just unlocked the bootloader, without the need to phone home, it would be a lot better.
Well I contacted Asus 24 hours ago... still nothing back from their Email support.
The Unlock tool is giving now me a different error now, which is different than the usual "Device is unlocked" message from before.
The message is "An unknown error occurs...". From what I understand, this happens if the Serial Number is not in their Database, or if their server is down.. or if there is a local network problem.
I will keep trying it periodically.
First Asus response today
Hi, we're very glad to help you. For this issue, I have emailed your problem to our BU(technical department) in Taipei,I will give you the answer as soon as I receive it and I have written down your checking number.
So sorry for waiting and causing your inconvenience.
If you not get any reply from asus within 48 hours, please feel free to contact us again.
Sorry for the inconvenience.
Click to expand...
Click to collapse
I tried to run the unlock tool, and it worked this time!
So in summary, use the vip.asus.com support site to email Asus if this happens to you!
CatalystNZ said:
First Asus response today
I tried to run the unlock tool, and it worked this time!
So in summary, use the vip.asus.com support site to email Asus if this happens to you!
Click to expand...
Click to collapse
Hi guys,
I have resolved.
I confirm that the reburbished tablet isn't right registered on Taipei Asus's server.
You must contact your Asus country support and ask to update this serve with your right serial number.
My italian support good ask me a screenshot but after they help me without problem.
The day after you can unlock the tablet.
Have a good enjoy with your unlocked tablet
device tracker is down
I want to use the device tracker excuse since my last 3 vip support tickets got denied /closed with no resolution over a year ago but now the device tracker website has been phased out. Any advice? Help! I won't give up.
diesburg said:
http://forum.xda-developers.com/showthread.php?t=2094746&page=1
Try that toolkit
Sent from my LG-P769 using Tapatalk
Click to expand...
Click to collapse
Thanks sir, you saved so much time, that root kit worked like charm, as ASUS is not providing "Unlocker apk" download.
Hi all,
I recently bought this phone and I really love it, unfortunaly no root/recovery methode available for now :crying:
With my little knowledge (I'm not a dev) I have successfully ported TWRP on the Archos Platinum 50 and rooted it.
and now i'm trying to do the same with the XA.
The bootloader was unlocked with official procedure but now I have a problem when trying to hotboot in fasboot mode: FAILED (remote: oem unlock is false)
When trying :
C:\Flashtool\x10flasher_lib>fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 0.496s]
booting...
FAILED (remote: oem unlock is false)
finished. total time: 0.505s
Click to expand...
Click to collapse
Maybe a bad unlocked Bootlader?
C:\Flashtool\x10flasher_lib>fastboot oem unlock
...
FAILED (remote: Not necessary)
finished. total time: 0.002s
Click to expand...
Click to collapse
and
C:\Flashtool\x10flasher_lib>fastboot getvar all
(bootloader) max-download-size: 0x8000000
(bootloader) partition-size:flashinfo: 1000000
(bootloader) partition-type:flashinfo: raw data
(bootloader) partition-size:system: d7000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:userdata: 32000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: c800000
(bootloader) partition-type:cache: ext4
(bootloader) partition-sizeem: 12800000
(bootloader) partition-typeem: ext4
(bootloader) partition-size:diag: 1000000
(bootloader) partition-type:diag: ext4
(bootloader) partition-size:apps_log: 1000000
(bootloader) partition-type:apps_log: ext4
(bootloader) partition-size:keystore: 800000
(bootloader) partition-type:keystore: raw data
(bootloader) partition-size:secro: 600000
(bootloader) partition-type:secro: raw data
(bootloader) partition-size:tee2: 500000
(bootloader) partition-type:tee2: raw data
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw data
(bootloader) partition-size:logo: 800000
(bootloader) partition-type:logo: raw data
(bootloader) partition-size:boot: 2800000
(bootloader) partition-type:boot: raw data
(bootloader) partition-size:lk2: 100000
(bootloader) partition-type:lk2: raw data
(bootloader) partition-size:lk: 100000
(bootloader) partition-type:lk: raw data
(bootloader) partition-size:nvram: 500000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-size:md3img: 500000
(bootloader) partition-type:md3img: raw data
(bootloader) partition-size:md1arm7: 400000
(bootloader) partition-type:md1arm7: raw data
(bootloader) partition-size:md1dsp: 4c0000
(bootloader) partition-type:md1dsp: raw data
(bootloader) partition-size:md1img: 1800000
(bootloader) partition-type:md1img: raw data
(bootloader) partition-sizeroinfo: 300000
(bootloader) partition-typeroinfo: raw data
(bootloader) partition-sizeemkeystore: 800000
(bootloader) partition-typeemkeystore: raw data
(bootloader) partition-size:seccfg: 40000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-size:metadata: 2000000
(bootloader) partition-type:metadata: raw data
(bootloader) partition-size:nvdata: 2000000
(bootloader) partition-type:nvdata: ext4
(bootloader) partition-sizepl: 40000
(bootloader) partition-typepl: raw data
(bootloader) partition-size:frp: 100000
(bootloader) partition-type:frp: raw data
(bootloader) partition-size:expdb: a00000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-sizeara: 80000
(bootloader) partition-typeara: raw data
(bootloader) partition-size:fotakernel: 2800000
(bootloader) partition-type:fotakernel: raw data
(bootloader) partition-size:ltalabel: 1000000
(bootloader) partition-type:ltalabel: ext4
(bootloader) partition-sizerotect2: b80000
(bootloader) partition-typerotect2: ext4
(bootloader) partition-sizerotect1: a00000
(bootloader) partition-typerotect1: ext4
(bootloader) partition-size:ta: 200000
(bootloader) partition-type:ta: raw data
(bootloader) partition-sizereloader: 40000
(bootloader) partition-typereloader: raw data
(bootloader) version-preloader:
(bootloader) version: 0.5
(bootloader) secure: no
(bootloader) version-baseband: 1300-9504_33.2.B.2.35
(bootloader) version-bootloader: 1298-9241 S1_Boot_MT6755_M0.MP6_13
(bootloader) serialno: RQ3000TNHH
(bootloader) product: F3112
all: Done!!
finished. total time: 0.062s
Click to expand...
Click to collapse
Under Android , the OEM unlock switch is ON in dev settings and in the hidden service menu:
Bootloader unlocked: Yes
Remote Lock State: Unlocked
I never tryed with flash commands because I don't know which tool to use for reflash if needed (Flashtool, WMshua, any MTK tools, ...)
If someone could shed some light on the fastboot error and tell me which flash tool to use, may be that I can share something with the community
Thanks
07/07/2016: You can flash stock firmware with Flashtool V0.9.22.3
10/07/2016: It seem that Sony removed hotboot ability on Unlocked BL. Now I need headers offsets for repacking .elf or a way to find them
14/07/2016: Finally I found offsets with "readelf" command, but no way for building new boot image.
I can't find correct commands with "mkbootimg" or "mkelf".
17/07/2016: For now I will wait for Sony to give us the good commands for compiling with mkbootimg
24/07/2016: Can't wait for Sony... After having sweated blood, I successfully compiled,repacked, flashed and... booted with
persistent changes a new boot.img !!! Rooted device is for soon
24/07/2016 MAJ 2: Finally rooted !!! (see screenshot) Will release as soon as possible !
Hello i know it's not the topic but i want to know what is the battery life of your xperia xa in use on facebook YouTube phone and message because i have the same phone but i don't finish the day With
Sorry for my bas english and thank you for your answer
Sent from my LT18i using XDA-Developers mobile app
hassan1999 said:
Hello i know it's not the topic but i want to know what is the battery life of your xperia xa in use on facebook YouTube phone and message because i have the same phone but i don't finish the day With
Sorry for my bas english and thank you for your answer
Click to expand...
Click to collapse
You need to turn off always scanning in wifi settings there is a software problem that Sony know about and are going to release a update it's stopping the device from into deep sleep.
aidy.lucas said:
You need to turn off always scanning in wifi settings there is a software problem that Sony know about and are going to release a update it's stopping the device from into deep sleep.
Click to expand...
Click to collapse
Thank you for the answer and I want to Know from where this information come to you please
Thank you !
Sent from my LT18i using XDA-Developers mobile app
hassan1999 said:
Thank you for the answer and I want to Know from where this information come to you please
Thank you !
Click to expand...
Click to collapse
See Sony support forum there's a message/reply on a thread in the xa section stating that Sony know about the software problem and they will fix it in the next update though there's no eta on it yet. Following everything closely as I going to replace my trusty m2 with a xa in a couple of weeks.
hassan1999 said:
Thank you for the answer and I want to Know from where this information come to you please
Thank you !
Sent from my LT18i using XDA-Developers mobile app
Click to expand...
Click to collapse
See this, about the wifi scanning bug.
any news ?
I am looking for working method.
hp6830s said:
I am looking for working method.
Click to expand...
Click to collapse
Everyone is, but our hands are tied at the moment...
SDee96 said:
Everyone is, but our hands are tied at the moment...
Click to expand...
Click to collapse
I think it'll be unlocked Bootloader root only due to drm-verity introduced by Sony on z3+. I'll know more when I get mine
I found working method to unlock it,even without DATA wipe.
https://www.youtube.com/watch?v=nSNDSyeys2g&authuser=0
PS : KingRoot PC and app ,KingoRoot,+ few more stuck or failed on 30 % while rooting.
I will release new boot and TWRP recovery before this week-end, all is working fine but I need more time to check all one more time. Your will need unlocked bootloader and 33.2.B.2.35 firmware.
Edit: Sony released 33.2.B.2.73 open source archive yesterday, will update my work before release.
rrvuhpg said:
I will release new boot and TWRP recovery before this week-end, all is working fine but I need more time to check all one more time. Your will need unlocked bootloader and 33.2.B.2.35 firmware.
Edit: Sony released 33.2.B.2.73 open source archive yesterday, will update my work before release.
Click to expand...
Click to collapse
What about drm restore fix? +ta keys backup? For bravia engine x-reality and probably camera too. Guessing locked Bootloader root days are finished. Hopefully pick mine up tomorrow or Thursday latest firmware includes new kernel+wifi bug fix
I don't see any changes before and after unlock, Bravia engine is present, no visible differences in camera quality, all Sony apps are working like on first day (TrackID too) . Like on other devices you lose Xperia Care, OTA updates and PC Compagnon updates. I'm not a dev and it must be confirmed after release, for now it's just my feedback. Other information, SELinux stay in enforcing mode after root
rrvuhpg said:
I don't see any changes before and after unlock, Bravia engine is present, no visible differences in camera quality, all Sony apps are working like on first day (TrackID too) . Like on other devices you lose Xperia Care, OTA updates and PC Compagnon updates. I'm not a dev and it must be confirmed after release, for now it's just my feedback. Other information, SELinux stay in enforcing mode after root
Click to expand...
Click to collapse
bravia engine x-reality relies on drm/ta keys why I've always left my bootloader locked on my M2 I know updates won't install not a problem i will need to update my flashtool though as I'm still using 9.18.6 as it just seems to work better I take it this device works with Flashtool OK then as with C4 +c5 mediatek powered Xperia devices it hard bricks them. I don't think I'll be able to cope long without root anyway I'll certainly help where I can once I get mine
you have the boot.img for us? how'd you root? i appreciate your work btw but I'm anxious to get this thing rooted lol need xposed and a couple modules ..... uhhhhh nvm just read the previous post lol. ugh ill hold on lol thanks again
Can you give to me link Flashtool V0.9.22.3. I can't find it.
Sorry my bad english
How did you manage to root yours :crying:
I tried mine to no avail had the same "Remote: oem unlock is false" thing at the end my bootloader is unlocked by official method and "allow oem unlock" is on under dev settings plz help
[Xperia XA user said:
;69816547]How did you manage to root yours :crying:
I tried mine to no avail had the same "Remote: oem unlock is false" thing at the end my bootloader is unlocked by official method and "allow oem unlock" is on under dev settings plz help
Click to expand...
Click to collapse
If the "fastboot oem unlock" command end with (not necessary) at the end of the error, you are good and you can continue the guide.
Explanation
rrvuhpg said:
Hi all,
I recently bought this phone and I really love it, unfortunaly no root/recovery methode available for now :crying:
With my little knowledge (I'm not a dev) I have successfully ported TWRP on the Archos Platinum 50 and rooted it.
and now i'm trying to do the same with the XA.
The bootloader was unlocked with official procedure but now I have a problem when trying to hotboot in fasboot mode: FAILED (remote: oem unlock is false)
When trying :
Maybe a bad unlocked Bootlader?
and
Under Android , the OEM unlock switch is ON in dev settings and in the hidden service menu:
Bootloader unlocked: Yes
Remote Lock State: Unlocked
I never tryed with flash commands because I don't know which tool to use for reflash if needed (Flashtool, WMshua, any MTK tools, ...)
If someone could shed some light on the fastboot error and tell me which flash tool to use, may be that I can share something with the community
Thanks
07/07/2016: You can flash stock firmware with Flashtool V0.9.22.3
10/07/2016: It seem that Sony removed hotboot ability on Unlocked BL. Now I need headers offsets for repacking .elf or a way to find them
14/07/2016: Finally I found offsets with "readelf" command, but no way for building new boot image.
I can't find correct commands with "mkbootimg" or "mkelf".
17/07/2016: For now I will wait for Sony to give us the good commands for compiling with mkbootimg
24/07/2016: Can't wait for Sony... After having sweated blood, I successfully compiled,repacked, flashed and... booted with
persistent changes a new boot.img !!! Rooted device is for soon
24/07/2016 MAJ 2: Finally rooted !!! (see screenshot) Will release as soon as possible !
Click to expand...
Click to collapse
Embrath,
How did you do it man.Please share.I am stuck with xperia c4 dual without recovery mode.the fastboot gives me a false oem unlock.Shed some light
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.
I recently got my hands on a Fire HD 8 (9th gen, 2020?), specifically a pre-production model that is both really locked down and not super locked down. For instance, I can pull a bunch of files from system directories and look at them on my PC, but I can't get it to install apps outside of a small selection Amazon seems to think are okay. I'm trying to rip sensor and spec data off the thing but I haven't had any luck.
after looking a bit closer at things, I can tell that your actually given root perms out of the box. I'm able to do stuff like disable every app, chmod, and overall just mess around. The codename is onyx and it seems the 10th gen is just the 9th gen but slightly altered.
Images:
{
"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"
}
https://imgur.com/a/XJMwNuG <-- More here
Here's the unit itself: https://youtu.be/v1BrM1GdoM4?t=4467
That timestamp is when I have it pulled apart and I do some close-ups of parts of the board.
More pics and some dumped data (incl. dumped partitions) https://drive.google.com/drive/folders/1Xl3CfJnkY7NuR_sEkEf2XlifT7S7wE2S
Let me know if there's anything interesting to try on this thing that you're aware of.
If you wanna chat about this somewhere, I've got a discord server for general purposes: https://discord.gg/pPQtYnS
It seems you have the same model (onyx) as the one currently on sale (HD 8 2020/ 10th generation): https://forum.xda-developers.com/showpost.php?p=82747107&postcount=1.
MontysEvilTwin said:
It seems you have the same model (onyx) as the one currently on sale (HD 8 2020/ 10th generation): https://forum.xda-developers.com/showpost.php?p=82747107&postcount=1.
Click to expand...
Click to collapse
If the specs are the exact same, then I basically have an OEM image containing working fastboot and a rooted-stock version of Fire OS that just needs patching to allow me to install apps.
Amazon's impl of PackageManager (iirc) has some checks in it that prevent me from installing anything but whitelisted apps, but I have yet to find a way to either disable that check or intercept and manipulate the whitelist.
lokio27 said:
I recently got my hands on a Fire HD 8 (9th gen, 2020?), specifically a pre-production model that is both really locked down and not super locked down. For instance, I can pull a bunch of files from system directories and look at them on my PC, but I can't get it to install apps outside of a small selection Amazon seems to think are okay. I'm trying to rip sensor and spec data off the thing but I haven't had any luck.
after looking a bit closer at things, I can tell that your actually given root perms out of the box. I'm able to do stuff like disable every app, chmod, and overall just mess around. The codename is onyx and it seems the 10th gen is just the 9th gen but slightly altered.
Here's the unit itself: https://youtu.be/v1BrM1GdoM4?t=4467
That timestamp is when I have it pulled apart and I do some close-ups of parts of the board.
Let me know if there's anything interesting to try on this thing that you're aware of.
Click to expand...
Click to collapse
Hey there,
First time I see something like this.
Would you mind dumping your bootloader/preloader/tz?
You should run in adb shell:
Code:
dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0.bin
dd if=/dev/block/platform/bootdevice/by-name/lk of=/sdcard/lk.bin
dd if=/dev/block/platform/bootdevice/by-name/tee1 of=/sdcard/tee1.bin
After you ran those commands, just exit the shell and pull out the files.
EDIT: Also, if you reboot to bootloader (adb reboot bootloader) and you run
Code:
fastboot getvar all
what's the output?
EDIT2: Assuming this is a non-production device (engineering?) you should be able to use SP Flash Tools? Maybe @diplomatic can throw us here some light.
Regards!
I wonder why Amazon have so tightly controlled which apps can be installed on a pre-production device which looks like it has an unlocked bootloader and allows root access? Are they experimenting with blocking apps from Google and other non-Amazon sources?
If you know the name of the gatekeeper app you can try 'pm disable-user --user 0' plus the name of the app to disable it and test. This is reversible.
Rortiz2 said:
Hey there,
First time I see something like this.
Would you mind dumping your bootloader/preloader/tz?
You should run in adb shell:
Code:
dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0.bin
dd if=/dev/block/platform/bootdevice/by-name/lk of=/sdcard/lk.bin
dd if=/dev/block/platform/bootdevice/by-name/tee1 of=/sdcard/tee1.bin
After you ran those commands, just exit the shell and pull out the files.
EDIT: Also, if you reboot to bootloader (adb reboot bootloader) and you run
Code:
fastboot getvar all
what's the output?
EDIT2: Assuming this is a non-production device (engineering?) you should be able to use SP Flash Tools? Maybe @diplomatic can throw us here some light.
Regards!
Click to expand...
Click to collapse
Here's the folder with all my dumps: https://drive.google.com/drive/folders/1Xl3CfJnkY7NuR_sEkEf2XlifT7S7wE2S
All the files are compressed, and everything should be there.
Also, here's the fastboot getvar all output
Code:
C:\platform-tools>fastboot getvar all
(bootloader) unlock_status: false
(bootloader) unlock_code: 0xcbc541c615958bf408416cfd
(bootloader) antirback_tee_version: 0x0001
(bootloader) antirback_lk_version: 0x0102
(bootloader) antirback_pl_version: 0x0102
(bootloader) rpmb_state: 1
(bootloader) prod: 0
(bootloader) secure: yes
(bootloader) lk_build_desc: 6930388-20191017_215445
(bootloader) pl_build_desc: 1087595-20191021_214610
(bootloader) max-download-size: 0x8000000
(bootloader) variant:
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x0
(bootloader) hw-revision: 0
(bootloader) battery-soc-ok: yes
(bootloader) battery-voltage: 4313mV
(bootloader) partition-size:userdata: 64e27be00
(bootloader) partition-type:userdata: f2fs
(bootloader) partition-size:vendor: e000000
(bootloader) partition-type:vendor: ext4
(bootloader) partition-size:system: c0000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 1f400000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:recovery: 2800000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: 2000000
(bootloader) partition-type:boot: raw data
(bootloader) partition-size:cam_vpu3: f00000
(bootloader) partition-type:cam_vpu3: ext4
(bootloader) partition-size:cam_vpu2: 2000000
(bootloader) partition-type:cam_vpu2: ext4
(bootloader) partition-size:cam_vpu1: f00000
(bootloader) partition-type:cam_vpu1: ext4
(bootloader) partition-size:nvcfg: 800000
(bootloader) partition-type:nvcfg: ext4
(bootloader) partition-size:boot_para: 100000
(bootloader) partition-type:boot_para: raw data
(bootloader) partition-size:metadata: 2000000
(bootloader) partition-type:metadata: raw data
(bootloader) partition-size:tee2: 500000
(bootloader) partition-type:tee2: raw data
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw data
(bootloader) partition-size:lk: 100000
(bootloader) partition-type:lk: raw data
(bootloader) partition-size:misc: 100000
(bootloader) partition-type:misc: raw data
(bootloader) partition-size:keys: 800000
(bootloader) partition-type:keys: raw data
(bootloader) partition-size:dkb: 100000
(bootloader) partition-type:dkb: raw data
(bootloader) partition-size:kb: 100000
(bootloader) partition-type:kb: raw data
(bootloader) partition-size:preloader: 40000
(bootloader) partition-type:preloader: raw data
(bootloader) serialno: [[REDACTED]]
(bootloader) off-mode-charge: 1
(bootloader) warranty: no
(bootloader) unlocked: yes
(bootloader) kernel: lk
(bootloader) product: onyx
(bootloader) slot-count: 0
(bootloader) version-baseband: N/A
(bootloader) version-bootloader: onyx-6930388-20191017120652-20191017215
(bootloader) version-preloader: 0.1.000
(bootloader) version: 0.5
all: Done!!
Finished. Total time: 0.099s
MontysEvilTwin said:
I wonder why Amazon have so tightly controlled which apps can be installed on a pre-production device which looks like it has an unlocked bootloader and allows root access? Are they experimenting with blocking apps from Google and other non-Amazon sources?
If you know the name of the gatekeeper app you can try 'pm disable-user --user 0' plus the name of the app to disable it and test. This is reversible.
Click to expand...
Click to collapse
Disabling the gatekeeper app just breaks the notification, things are still being blocked by an internal implementation of the package manager service.
lokio27 said:
Here's the folder with all my dumps: https://drive.google.com/drive/folders/1Xl3CfJnkY7NuR_sEkEf2XlifT7S7wE2S
All the files are compressed, and everything should be there.
Also, here's the fastboot getvar all output
Code:
C:\platform-tools>fastboot getvar all
(bootloader) unlock_status: false
(bootloader) unlock_code: 0xcbc541c615958bf408416cfd
(bootloader) antirback_tee_version: 0x0001
(bootloader) antirback_lk_version: 0x0102
(bootloader) antirback_pl_version: 0x0102
(bootloader) rpmb_state: 1
(bootloader) prod: 0
(bootloader) secure: yes
(bootloader) lk_build_desc: 6930388-20191017_215445
(bootloader) pl_build_desc: 1087595-20191021_214610
(bootloader) max-download-size: 0x8000000
(bootloader) variant:
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x0
(bootloader) hw-revision: 0
(bootloader) battery-soc-ok: yes
(bootloader) battery-voltage: 4313mV
(bootloader) partition-size:userdata: 64e27be00
(bootloader) partition-type:userdata: f2fs
(bootloader) partition-size:vendor: e000000
(bootloader) partition-type:vendor: ext4
(bootloader) partition-size:system: c0000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 1f400000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:recovery: 2800000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: 2000000
(bootloader) partition-type:boot: raw data
(bootloader) partition-size:cam_vpu3: f00000
(bootloader) partition-type:cam_vpu3: ext4
(bootloader) partition-size:cam_vpu2: 2000000
(bootloader) partition-type:cam_vpu2: ext4
(bootloader) partition-size:cam_vpu1: f00000
(bootloader) partition-type:cam_vpu1: ext4
(bootloader) partition-size:nvcfg: 800000
(bootloader) partition-type:nvcfg: ext4
(bootloader) partition-size:boot_para: 100000
(bootloader) partition-type:boot_para: raw data
(bootloader) partition-size:metadata: 2000000
(bootloader) partition-type:metadata: raw data
(bootloader) partition-size:tee2: 500000
(bootloader) partition-type:tee2: raw data
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw data
(bootloader) partition-size:lk: 100000
(bootloader) partition-type:lk: raw data
(bootloader) partition-size:misc: 100000
(bootloader) partition-type:misc: raw data
(bootloader) partition-size:keys: 800000
(bootloader) partition-type:keys: raw data
(bootloader) partition-size:dkb: 100000
(bootloader) partition-type:dkb: raw data
(bootloader) partition-size:kb: 100000
(bootloader) partition-type:kb: raw data
(bootloader) partition-size:preloader: 40000
(bootloader) partition-type:preloader: raw data
(bootloader) serialno:
(bootloader) off-mode-charge: 1
(bootloader) warranty: no
(bootloader) unlocked: yes
(bootloader) kernel: lk
(bootloader) product: onyx
(bootloader) slot-count: 0
(bootloader) version-baseband: N/A
(bootloader) version-bootloader: onyx-6930388-20191017120652-20191017215
(bootloader) version-preloader: 0.1.000
(bootloader) version: 0.5
all: Done!!
Finished. Total time: 0.099s
Disabling the gatekeeper app just breaks the notification, things are still being blocked by an internal implementation of the package manager service.
Click to expand...
Click to collapse
Hey!
Thanks for those images! Very appreciated!
Well, so definelety your tablet looks unlocked.
Would you mind dumping your boot1 (/dev/block/mmcblk0boot1) or just the "idme print" output and sharing it via PM (as it contains your serial, etc)? Having the idme unlock can be useful:good:
Regards.
PS: Delete the kb partition from the folder and your serial number from getvar all output
Rortiz2 said:
Hey!
Thanks for those images! Very appreciated!
Well, so definelety your tablet looks unlocked.
Would you mind dumping your boot1 (/dev/block/mmcblk0boot1) or just the "idme print" output and sharing it via PM (as it contains your serial, etc)? Having the idme unlock can be useful:good:
Regards.
PS: Delete the kb partition from the folder and your serial number from getvar all output
Click to expand...
Click to collapse
I'm not terribly concerned about the serial number or anything myself as it's already been shown like 30 times in all sorts of different media, including pics and videos of the unit. I uploaded boot1 to the folder so check the link again.
If there's a good reason to remove the s/n I will, but I'm not too terribly worried myself.
lokio27 said:
I'm not terribly concerned about the serial number or anything myself as it's already been shown like 30 times in all sorts of different media, including pics and videos of the unit. I uploaded boot1 to the folder so check the link again.
If there's a good reason to remove the s/n I will, but I'm not too terribly worried myself.
Click to expand...
Click to collapse
Hi again,
Thanks for the boot1 dump. Nothing interesting in idme unlock (blank).
If i'm allowed to ask, how did this tablet (prototipe?) ended in your hands...? Just wondering
EDIT: Could you verify if fastboot it's really unlocked? Try wiping misc:
Code:
fastboot erase misc
Regards!
Rortiz2 said:
Hi again,
Thanks for the boot1 dump. Nothing interesting in idme unlock (blank).
If i'm allowed to ask, how did this tablet (prototipe?) ended in your hands...? Just wondering
Regards!
Click to expand...
Click to collapse
Wandered into my possession via eBay. Didn't even spend half of what the 10th gen costed on it, funnily enough. I'd like to fix the app installation issue so I can install stuff on it (notably Discord and/or Google Chrome)
Also, yes I'll try that.
Rortiz2 said:
Hi again,
EDIT: Could you verify if fastboot it's really unlocked? Try wiping misc:
Code:
fastboot erase misc
Regards!
Click to expand...
Click to collapse
It does work!
Code:
C:\platform-tools>fastboot devices
XXXXXXXXXXXXXXXX fastboot
C:\platform-tools>fastboot erase misc
Erasing 'misc' OKAY [ 0.019s]
Finished. Total time: 0.026s
lokio27 said:
It does work!
Code:
C:\platform-tools>fastboot devices
XXXXXXXXXXXXXXXX fastboot
C:\platform-tools>fastboot erase misc
Erasing 'misc' OKAY [ 0.019s]
Finished. Total time: 0.026s
Click to expand...
Click to collapse
Hey,
Nice so yeah working fastboot.
Do you have telegram? I would like to talk with you via there.
Regards.
Rortiz2 said:
Hey,
Nice so yeah working fastboot.
Do you have telegram? I would like to talk with you via there.
Regards.
Click to expand...
Click to collapse
Sure, I'll DM you my Telegram.
Thanks to help from @Rortiz2, we were able to get a stock system image from the Fire HD 8 (2020) running on this tablet. Sure enough, still have root permissions, and now I can actually install apps! Will be updating as more things are discovered.
You guys are amazing.
a guide maybe?
hi guy/gals, is there a guide for rooting the Onyx variant? thanks for your efforts!!!
I hope you guys find a way to crack this baby.
joining in this baby as well
Welp i tried shorting every test point and wont work for some reason but when i disconnect the battery and connect it via pc it keeps rebooting to the Preloader already so was wondering if its possible to use that to exploit the bootloader?
Awesomeslayerg said:
Welp i tried shorting every test point and wont work for some reason but when i disconnect the battery and connect it via pc it keeps rebooting to the Preloader already so was wondering if its possible to use that to exploit the bootloader?
Click to expand...
Click to collapse
no there isnt a bootrom exploit at this time on the hd8 (10). Mediatek seems to have fixed the exploit on their chip. If anyone can find a way to get into the bootrom there is hope for the old exploit. Maybe someone will get a root exploit that will force a bootrom boot. still early in the device....
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 GuideDEVICE 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.