Related
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 only just upgraded to Oreo a few weeks ago - mostly delayed by my CID / dual SIM model causing me to not receiving the OTA for ages. I just noticed today that TWRP no longer works. All that happens is the screen turns black, still backlit, and oddly enough, fastboot devices still lists it.
I use fastboot boot <twrp.img> so I can keep the stock recovery installed. I'm hesitant to try flashing TWRP as I don't have a backup of the current recovery, and can't see how to make one. I suppose to restore it, I could track down a link for the OTA I applied to extract it from, but I doubt flashing TWRP would help anyway.
I've tried all the versions available from the TWRP website:
Code:
twrp-3.1.1-1-ocn.img
twrp-3.2.1-0-ocn.img
twrp-3.2.1-1-ocn.img
twrp-3.2.1-2-ocn.img
Here's my output of
Code:
fastboot getvar all
:
Code:
(bootloader) kernel: lk
(bootloader) product: htc_ocndugl
(bootloader) version: 1.0
(bootloader) max-download-size: 2399200000
(bootloader) serialno: FA78H1800284
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: 356133083656859
(bootloader) version-main: 2.42.400.3
(bootloader) boot-mode: download
(bootloader) version-baseband: 8998-002772-1712011153
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PZC30000
(bootloader) cid: HTC__060
all:
finished. total time: 0.004s
Could it be to do with some partition structure change that could be part of my model's Oreo update that TWRP has yet to reflect? I don't know what else could cause this.
Does TWRP place a log file somewhere?
Is it even getting into the TWRP boot process at all? The fact it's still listed in fastboot devices is intriguing.
I've been rooting for several years, and as a developer and avid Arch Linux user, I tend to be able to sort out most issues myself, and so only have the need to post very rarely. I've tried hard to find information on this issue, but I'm completely stumped and would very much appreciate some help. Cheers!
Edit: I thought I should probably try flashing it just in case - lo and behold, it worked! Though I'm still quite curious as to why booting directly could have stopped working.
Twrp versions are now related to the android versions, at least for htc. I think I remember reading something to do with the encryption and how twrp interacts with the os..
Newest os = newest twrp. Once you have the device running don't change/upgrade twrp. It is meant to be safe but i dont trust it.
I do recall seeing something to do with encryption, actually. Surely they're aiming for backwards compatibility though. And I'd like to think it'd show a message if it's not working.
i tried to install the newest 5.1.11 in full ( as i am magisk rooted, twrp installed, and bootloader unlocked). i kept getting system ui crashes over and over and eventually, after so many, the phone just powers down by itself. I had tried clearing cache after going back into twrp. Rebooted. Same ui issue. Then i decided to restore a backup in twrp i had made a few weeks ago stored on internal memory. This was a bad idea. It said it restored successfully but upon reboot, i only get fastboot now. i think it is communicating with fastboot but when i try to fastboot boot twrp-3.2.1-0 (or 3.2.2-0) i get, "remote: Failed to load/authenticate boot image: Load Error". I do not know what to do and am hoping you guys can figure out how to fix this. Any attempt to enter recovery via buttons results in fastboot booting. restart is also fastboot.
This is what my phone says:
FastBoot mode
Product_name- sdm845
variant- sdm ufs
basband version-
serial- it's there
secure boot- yes
device state- unlocked
Don't know if this helps fastboot getvar all reports this:
C:\Adb\OnePlus 6 Files>fastboot getvar all
(bootloader) unlocked:yes
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3837
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) variant:SDM UFS
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x1B800B7000
(bootloader) partition-type:system_a:ext4
(bootloader) partition-size:system_a: 0xB2C00000
(bootloader) has-slot:modem:yes
(bootloader) has-slot:system:yes
(bootloader) current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:6
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:0
(bootloader) slot-unbootable:a:yes
(bootloader) slot-successful:a:no
(bootloader) slot-count:2
(bootloader) secure:yes
(bootloader) serialno: omitted
(bootloader) product:sdm845
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
all:
finished. total time: 0.047s
Is there anyone that has had this set of circumstances and got out of it? Any help is appreciated. There are some things i've seen that i can do but don't want to do further damage. Thanks to all for any and all help.
thejase said:
i tried to install the newest 5.1.11 in full ( as i am magisk rooted, twrp installed, and bootloader unlocked). i kept getting system ui crashes over and over and eventually, after so many, the phone just powers down by itself. I had tried clearing cache after going back into twrp. Rebooted. Same ui issue. Then i decided to restore a backup in twrp i had made a few weeks ago stored on internal memory. This was a bad idea. It said it restored successfully but upon reboot, i only get fastboot now. i think it is communicating with fastboot but when i try to fastboot boot twrp-3.2.1-0 (or 3.2.2-0) i get, "remote: Failed to load/authenticate boot image: Load Error". I do not know what to do and am hoping you guys can figure out how to fix this. Any attempt to enter recovery via buttons results in fastboot booting. restart is also fastboot.
This is what my phone says:
FastBoot mode
Product_name- sdm845
variant- sdm ufs
basband version-
serial- it's there
secure boot- yes
device state- unlocked
Don't know if this helps fastboot getvar all reports this:
C:\Adb\OnePlus 6 Files>fastboot getvar all
(bootloader) unlocked:yes
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3837
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) variant:SDM UFS
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x1B800B7000
(bootloader) partition-type:system_a:ext4
(bootloader) partition-size:system_a: 0xB2C00000
(bootloader) has-slot:modem:yes
(bootloader) has-slot:system:yes
(bootloader) current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:6
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:0
(bootloader) slot-unbootable:a:yes
(bootloader) slot-successful:a:no
(bootloader) slot-count:2
(bootloader) secure:yes
(bootloader) serialno: omitted
(bootloader) product:sdm845
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
all:
finished. total time: 0.047s
Is there anyone that has had this set of circumstances and got out of it? Any help is appreciated. There are some things i've seen that i can do but don't want to do further damage. Thanks to all for any and all help.
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 your solution lies here
tabletalker7 said:
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 your solution lies here
Click to expand...
Click to collapse
I saw this. Will i keep my data with this method?
thejase said:
I saw this. Will i keep my data with this method?
Click to expand...
Click to collapse
no, but if you can't even boot to TWRP then you have nothing left to save at this point.
Try booting the latest twrp (3.2.3.0) before giving up and wiping. If you can get to fastboot, you're not bricked.
iElvis said:
Try booting the latest twrp (3.2.3.0) before giving up and wiping. If you can get to fastboot, you're not bricked.
Click to expand...
Click to collapse
thanks for the suggestions but no dice.
According to your first posting, the phone knows that the boot partition on both your slots are a mess and can't load - you need the fastboot rom to make the phone start over and try again. Sorry buddy - I would like to save your data but it doesn't seem feasible at this point.
tabletalker7 said:
According to your first posting, the phone knows that the boot partition on both your slots are a mess and can't load - you need the fastboot rom to make the phone start over and try again. Sorry buddy - I would like to save your data but it doesn't seem feasible at this point.
Click to expand...
Click to collapse
That's alright. I appreciate the point in the right direction. Doing that fastboot method bat file that you suggested now... Thanks for the help.
thejase said:
That's alright. I appreciate the point in the right direction. Doing that fastboot method bat file that you suggested now... Thanks for the help.
Click to expand...
Click to collapse
tabletalker7 said:
According to your first posting, the phone knows that the boot partition on both your slots are a mess and can't load - you need the fastboot ROM to make the phone start over and try again. Sorry buddy - I would like to save your data but it doesn't seem feasible at this point.
Click to expand...
Click to collapse
So as it turns out that method worked using the bat file flash all fastboot. Though, not at first. When it first rebooted after the bat file finished flashing. system UI was still crashing. When you initially run the bat file at the beginning, it asks if you want to delete your data. First time around i said no, just to see what it would do. Well it booted, but kept getting that system ui crash that I had in the beginning of all this mess. I rebooted and this time chose to erase data and then it re-flashed all again (same bat file). Turns out, when it booted, same deal, system UI crash. So this time i was looking things up while the crashes where happening and then it just rebooted on its own (as it does with a number of system UI crashes in succession). When it came up it was that Chinese menu (which i assume to be download mode or something). Anyway, i chose English and it's a menu to clear dalvik and cache, system settings reset, and one other i can't remember. i did system settings then dalvik and finally, when i rebooted, it was like it was booting for the first time with no crashes. Only thing i can figure is that setting in the bat file at first launch actually didn't erase user data since when it booted, all my icons where there in the background. doing it "on device" in download mode seems to have worked. I am only adding this information as an f.y.i.. Thanks again for all your help, guys.
thejase said:
When it came up it was that Chinese menu (which i assume to be download mode or something).
Click to expand...
Click to collapse
That's stock recovery.
maigre said:
That's stock recovery.
Click to expand...
Click to collapse
Oh, ok. Funny thing is, I had never seen what that looked like as I immediately installed twrp from the time I bought it. Makes sense, though I still wonder why it booted to stock recovery after systemui crashing. Unless it senses the crashes and does that by default to clear system settings and data for a successful boot?
Hi,
I’ve been an owner of a Moto G7 Power device for a few months now. As we all know, life is not perfect and I still experience several problems (such as unavailable VoLTE/VoWiFi and no SMS notifications on a locked screen), that were present in LOS17.1 and are still there in 18.1. Since I am not an expert and therefore might had made some mistakes during flashing my phone, I’d like to give it a (last) shot and to try to do a fresh install of LOS – maybe it will help? What would be the best possible way to do that (in order to eliminate any doubts that anything was done wrong during flashing, etc)?
So what I have:
- Moto G7 Power (ocean, X1955-5), now "almost new".
- The device is manufacturer unlocked, all hardware seem to be completely OK.
- LOS18.1 installed (and is pretty much OK except for the problems I mentioned above).
That said, here is what I’d like to ask:
1. Does it make any sense to go back to the stock ROM, thren get all official Android/Motorola updates first and only after that to flash LOS?
2. Which LOS to flash: older 17.1 or the most recent 18.1?
3. Which custom recovery to use: TWRP or the one provided by LOS? Both have the versions specific for my device and seem to be maintained and updated.
4. Is it better to flash the custom recovery or just to load it via fastboot boot recovery.img? I used the latter option before and it seemed to work.
5. Does it matter which version of platform-tools to use? My Linux distro definitely does not have the latest one, though it works.
Thanks for any advice!
Stilbium said:
Hi,
I’ve been an owner of a Moto G7 Power device for a few months now. As we all know, life is not perfect and I still experience several problems (such as unavailable VoLTE/VoWiFi and no SMS notifications on a locked screen), that were present in LOS17.1 and are still there in 18.1. Since I am not an expert and therefore might had made some mistakes during flashing my phone, I’d like to give it a (last) shot and to try to do a fresh install of LOS – maybe it will help? What would be the best possible way to do that (in order to eliminate any doubts that anything was done wrong during flashing, etc)?
So what I have:
- Moto G7 Power (ocean, X1955-5), now "almost new".
- The device is manufacturer unlocked, all hardware seem to be completely OK.
- LOS18.1 installed (and is pretty much OK except for the problems I mentioned above).
That said, here is what I’d like to ask:
1. Does it make any sense to go back to the stock ROM, thren get all official Android/Motorola updates first and only after that to flash LOS?
2. Which LOS to flash: older 17.1 or the most recent 18.1?
3. Which custom recovery to use: TWRP or the one provided by LOS? Both have the versions specific for my device and seem to be maintained and updated.
4. Is it better to flash the custom recovery or just to load it via fastboot boot recovery.img? I used the latter option before and it seemed to work.
5. Does it matter which version of platform-tools to use? My Linux distro definitely does not have the latest one, though it works.
Thanks for any advice!
Click to expand...
Click to collapse
Your problems are more like related to the carrier the device is on, the software channel, radio firmware, and maybe apns included with LOS
sd_shadow said:
Your problems are more like related to the carrier the device is on, the software channel, radio firmware, and maybe apns included with LOS
Click to expand...
Click to collapse
So, in other words, you do not think that anything like this could be screwed up during installation/flashing?
I also have a feeling that it (VoLTE part) is somehow related to the carrier... but what can I do? I tried to make a new apn (based on the carrier's instructions) and it worked exactly the same as that included into LOS (i.e. no VoLTE, IMS is always reported "not registered"). On the other hand, I (as well as a couple of others) did not have these problems on the stock.
The reason why I'd like to try a fresh install is that someone (Moto G7: river, which is very similar; also the same carrier) reported that a) he got VoLTE working by going back to stock and then flashing a new version of LOS17.1 and b) his VoWiFi stopped working (on the same device) after an upgrade to 18.1:
https://gitlab.com/LineageOS/issues/android/-/issues/3269
Stilbium said:
So, in other words, you do not think that anything like this could be screwed up during installation/flashing?
I also have a feeling that it (VoLTE part) is somehow related to the carrier... but what can I do? I tried to make a new apn (based on the carrier's instructions) and it worked exactly the same as that included into LOS (i.e. no VoLTE, IMS is always reported "not registered"). On the other hand, I (as well as a couple of others) did not have these problems on the stock.
The reason why I'd like to try a fresh install is that someone (Moto G7: river, which is very similar; also the same carrier) reported that a) he got VoLTE working by going back to stock and then flashing a new version of LOS17.1 and b) his VoWiFi stopped working (on the same device) after an upgrade to 18.1:
https://gitlab.com/LineageOS/issues/android/-/issues/3269
Click to expand...
Click to collapse
Flashing stock is a possible fix, even likely, if others have reported just that.
Doesn't mean you installed it incorrect.
Custom Roms don't include radio firmware, and sometimes it needs to be reflashed.
If you want you can just flash the stock radio firmware.
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
sd_shadow said:
Flashing stock is a possible fix, even likely, if others have reported just that.
Doesn't mean you installed it incorrect.
Custom Roms don't include radio firmware, and sometimes it needs to be reflashed.
If you want you can just flash the stock radio firmware.
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Click to expand...
Click to collapse
Thanks for a hint! Honestly, I bought this phone with a sole purpose of using a custom ROM without google apps... so I am not going back to stock.
Do I understand it correctly that the code you provided implies that I follow only the part of the instructions on "how to flash a stock ROM back" from here:
https://forum.xda-developers.com/t/...ersions-flash-back-to-stock-firmware.3927138/ ? The sequence of commands is different there - erasing comes after the both flashing commands (I am not an expert, sorry).
One more thing - which stock ROM should I use? I mean, which version - the latest, the closest to the current version of LOS or it does not matter? As far as I can see, the latest stock is for Android 10, and I have LOS18.1 installed.
Stilbium said:
Thanks for a hint! Honestly, I bought this phone with a sole purpose of using a custom ROM without google apps... so I am not going back to stock.
Do I understand it correctly that the code you provided implies that I follow only the part of the instructions on "how to flash a stock ROM back" from here:
https://forum.xda-developers.com/t/...ersions-flash-back-to-stock-firmware.3927138/ ? The sequence of commands is different there - erasing comes after the both flashing commands (I am not an expert, sorry).
One more thing - which stock ROM should I use? I mean, which version - the latest, the closest to the current version of LOS or it does not matter? As far as I can see, the latest stock is for Android 10, and I have LOS18.1 installed.
Click to expand...
Click to collapse
The commands I posted are just the radio parts.
That order sometimes fixes radio issues, that the normal order does not.
There may be a benefit to flashing the newer firmware, rarely is the older firmware better, unless you are flashing an older custom ROM.
sd_shadow said:
The commands I posted are just the radio parts.
That order sometimes fixes radio issues, that the normal order does not.
There may be a benefit to flashing the newer firmware, rarely is the older firmware better, unless you are flashing an older custom ROM.
Click to expand...
Click to collapse
Thanks a lot! Though it did not help... maybe I did something wrong.
So first I looked at getvar:
Code:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_retail-16222030b3b-201001
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG GD6BMB RV=08 PV=01 FV=0000000000000001
(bootloader) ram: 3GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: ....................
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: A37CC9D800000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: ....................
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 07-08-2020
(bootloader) sku: XT1955-5
(bootloader) carrier_sku: XT1955-5
(bootloader) battid: SB18C28956
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Apr 29 15:45:40 UTC 2021"
(bootloader) ro.build.fingerprint[0]: motorola/ocean/ocean:10/QPOS30.85-
(bootloader) ro.build.fingerprint[1]: 23-3/dc622c:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.6.2.r1-06600-89xx.0
(bootloader) version-baseband: M632_41.00.01.162R OCEAN_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.9.206-perf+ ([email protected]
(bootloader) kernel.version[1]: oid-build) (clang version 8.0.12 for And
(bootloader) kernel.version[2]: roid NDK) #1 SMP PREEMPT Thu Oct 1 00:21
(bootloader) kernel.version[3]: :27 CDT 2020
(bootloader) sbl1.git: MBM-2.1-ocean_retail-a30e356d6d-201001
(bootloader) rpm.git: MBM-2.1-ocean_retail-20f2cf34-201001
(bootloader) tz.git: MBM-2.1-ocean_retail-6814a8d41f-201001
(bootloader) devcfg.git: MBM-2.1-ocean_retail-6814a8d41f-201001
(bootloader) keymaster.git: MBM-2.1-ocean_retail-6814a8d41f-201001
(bootloader) cmnlib.git: MBM-2.1-ocean_retail-6814a8d41f-201001
(bootloader) cmnlib64.git: MBM-2.1-ocean_retail-6814a8d41f-201001
(bootloader) prov.git: MBM-2.1-ocean_retail-6814a8d41f-201001
(bootloader) aboot.git: MBM-2.1-ocean_retail-16222030b3b-201001
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retus
(bootloader) current-slot: b
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _b
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: Yes
(bootloader) slot-successful:_b: Yes
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
(bootloader) pcb-part-no: SP69A6P7PU
all: listed above
finished. total time: 0.014s
and noticed that the current-slot/running-slot is b.
Grabbed the latest retus Moto firmware from lolinet (the same 10/QPOS30.85) and then, as probably expected:
Code:
$ fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modemb' (65428 KB)...
OKAY [ 2.616s]
writing 'modemb'...
(bootloader) Invalid partition name modemb
FAILED (remote failure)
finished. total time: 2.617s
Then:
Code:
$ fastboot flash modem_b NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem_b' (65428 KB)...
OKAY [ 2.612s]
writing 'modem_b'...
OKAY [ 1.110s]
finished. total time: 3.722s
$ fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.017s]
finished. total time: 0.017s
$ fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.017s]
finished. total time: 0.018s
$ fastboot flash fsg_b fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg_b' (9204 KB)...
OKAY [ 0.368s]
writing 'fsg_b'...
OKAY [ 0.121s]
finished. total time: 0.490s
After reboot everything is exactly the same as before - i.e. the same problems remained, no new ones showed up.
UPD: actually, no - the phone is reachable, it rings, but neither I can hear the other party, nor I am heard by anyone.
Maybe I had to flash both a and b slots?
Since my carrier is T-Mobile (though the phone is retail), would it make any sense to try to flash the radio from the T-mobile ROM? There are two ROMs available - RETUS (which I used) and TMO.
Looks like I'll have to temporarily go back to the stock... my fault anyway, needed to check more carefully what the LOS "official support" actually means
Thank you.
Well, back to stock (RETUS) for a while. IMS status is registered, so I guess VoLTE should work. Will try it and VoWiFi a bit later.
However, the settings in APN are a bit different from what is supplied with LOS - could this be the problem?
I'll try to flash LOS ROM once again, so going back to my initial questions - which recovery would you recommend and should I really flash it or fastboot boot?
Thank you.
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.