yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] ChrisDos:
Yea it looks like can't roll back to an older version either. I tried to restore to 2022-04-15 and it would not work. I took a couple of screen shots. The last screen shot only stays on the screen for a second before it disappears and I snapped the picture mid scroll.

and

So yea, it looks like you can't flash backwards older than 2022-07. That is going to suck. So much for being able to restore my Swift backups.

Hopefully someone will know about a new signing tool that will work for the newer firmware.
[Android Head-Units] ChrisDos:
I'm actually shocked there is even a problem with the screen being rotated. I would think that would be hardware encoded.
[Android Head-Units] slow66:
Agreed. But here I am. Lol
[Android Head-Units] ChrisDos:
Does changing the config.txt file fix that problem?
[Android Head-Units] slow66:
It did not adjust the update screen.

It did fix the rotation after flash.
[Android Head-Units] ChrisDos:
I have the Gen 2 Ultra, which one do you have? Does ADB work on any of your USB ports, as mine does not. Loosing root means I can't ADB (using wireless) any longer.
[Android Head-Units] slow66:
I have the S8 premium and never got adb functional.
[Android Head-Units] Magus17:
Did the screen rotation ever get figured out?
[Android Head-Units] ChrisDos:
I believe in post #42 they just created a config.txt file and put "ro.sf.swrotation = 90" in it.
[Android Head-Units] Magus17:
Oh ok seemed to be a little confusion if that actually worked or not, where do you actually put the configuration file itself?
[Android Head-Units] ChrisDos:
I think you just put it in the same place as the installation file. I did not need this. Not sure if the S8 Ultra screen is different and doesn't rotate compared to the other S8s or not.
[Android Head-Units] Magus17:
I'll try again in rhe morning with a different flash drive but I unzipped the zip file to an exfat card and my s8 recognizes it and I can access it but it doesn't see it as an update
[Android Head-Units] Magus17:
Please tell me what one earth I'm doing wrong, it's formatted to exFAT, it has the patched boot.img from the original file, renamed it, deleted and replaced boot.img from the 6315_1 file and inserted it into every USB port, they all ready and access it but no pop-up to update. These are pics of the files on the flash drive
[Android Head-Units] ChrisDos:
You have to take everything in that ATOTO directory and put it in the root of the card. So you have everything in a sub directory.
[Android Head-Units] Magus17:
So I did that and got it to try to update but said it wasn't signed so I go through that process and I get an updated zip file with 0 files in it
[Android Head-Units] shugo-chara:
Hi, I was also looking for a way to do rooting after upgrading to version 8/11. Unbelievably I checked almost all the relevant threads on xda and they all seem to work only on the April updated firmware.

Have you found a way to do root on the 8/11 firmware please.

I would like to use wireless adb but it seems that only root can use that feature, usb does not work.
[Android Head-Units] ChrisDos:
I have not found a way yet. Though I have not finished going through this entire thread yet:

https://xdaforums.com/t/general-fyt...unisoc-ums512-q-a-mods-tips-firmware.4396339/

My car was down for three weeks due to an alternator issue. I got i back up and running last week, but have not had time to dig into this yet again.
[Android Head-Units] shugo-chara:
I found that I can use fastboot command on s8 with an Android phone connected to it without root. I don't know if it's possible to flush the magisk patched boot image to the s8 in this way. If it goes well, I should get root after reboot.

But if it fails it might cause a loop so I haven't tried it yet.
[Android Head-Units] ChrisDos:
That is interested. How do you get into the bootloader to enter fastboot commands? I guess you can just patch the boot.img from the zip file, then just run "fastboot boot magisk_patched_boot.img". Once booted, you can open Magisk and patch the boot partition, reboot again and have full root.
[Android Head-Units] shugo-chara:
Android to connect to another Android (s8) via otg to send fastboot commands in root-free state.

I've experimented with it on my own Android phone, but I don't know the recovery mode of the s8 so I haven't tried it yet.

I hope someone who knows more about it will come down with good news lol
[Android Head-Units] ril3y:
I know you have an S8 ultra. But from reading though this thread it looks like this works with the S8 Standard as well. Do you known if your fully patched zip should work with the S8 Standard as well? I am too need adb wireless to work as I am working on some serial device firmware + app development. I cant use adb + serial ports in host mode. For a pretty neat little head unit they sure have crippled some of the best features of android. Thanks for the help Chris!
[Android Head-Units] ChrisDos:
From what I understand it should work fine on a S8 Standard. Though some have said that their screen is rotated 90 degrees from what it should be. Also, the root won't work at this point if your firmware is newer than July 11th I believe. I have not had time to dig into a way to get around this yet.
[Android Head-Units] ril3y:
I did find a weird way to boot this device using reset and the home key.

Here is a video.

https://photos.app.goo.gl/CUDNkqxk3JQFgqoR7

Its a little loud due the fan I have to have on this thing while I have no heat sink on it.

Basically, it pops up a picture of an android and "NO COMMAND" error message the restarts.

I have made a video of this. FYI I also took apart the device and am looking for any hardware access that might be available. If anyone wants to know anything in particular let me know :)
[Android Head-Units] nbetcher:
If you're going this far, just interface directly with the eMMC. After all, these silly Chinese manufacturers wouldn't know security if it hit them with a bat: they left the eMMC encryption (and its support) disabled/unimplemented.

(Yes, in regards to the 8/11 -- aka 220811 patch level: ) Did you try the fastboot method? Just

adb reboot bootloader

And you're in fastboot mode. I didn't try much in it. Actually, the only thing I tried was

adb unlock
# and:
adb oem unlock

and both caused fastboot to hang. Honestly, I didn't really put much effort into doing anything else because I have too much else to be working on, and now the stereo is firmly mounted back into my car.

If you try:

fastboot flash boot magisk_patchedXXX.img
# or:
fastboot boot magisk_patchedXXX.img

Let me know what happens! I'm sure there is going to be more to be done, but I'm curious of the results. I may eventually try fiddling around with it myself.

It's funny they bothered to put a halt to rooting and what-not. Their security is a JOKE and they obviously don't know their clientele if they're trying to prevent rooting. After seeing how abysmal these head units (and their user interfaces) are, it makes me highly motivated to create my own company to make an American-made one to show them how it's really done. (Along with complying with applicable laws, like say, releasing GPL source.) Will it happen? Doubt it; not enough time with a full-time job and 50+ projects going, but it's a nice pipe dream!
[Android Head-Units] nbetcher:
I also found that they distributed an old, hacked version (I assume, since it's pre-installed without a Google Account*) of Torque Pro (1.8.16, current version is like 1.12.x) now with the 220811 patch level, unless of course the Torque developer agreed to it, which I doubt. So, am I to assume they have taken to just blindly robbing developers? I wonder how many other apps on the head unit are stolen.

You can find it in /oem/vital-app. It's preventing an upgrade with the one on the Play Store which I believe I need to support the Scantool OBDLink SX or EX (USB connected). So now I have an absolute NEED to hack this head unit, or at least /oem so I can nuke the distributed Torque APK (doubt an overlay or bind will work, but I'm going to try that first). The way /oem is mounted is very strange:

'oem' partition on mmcblk0 (block device) -> /fem -> /dev/oem_link -> /oem

And /dev/oem_link isn't a block device.

* Confirmed, APK was re-signed from logcat entry:

com.android.vending I Finsky: [2] fzq.<init>(18): org.prowl.torque is installed but certificate mismatch

As a developer myself, this makes me livid. I'm emailing them asking them WTF they're thinking...
[Android Head-Units] nbetcher:
The option to Uninstall the app was completely missing from the App Info screen, but I was able to force an uninstall by using SecureTask with Device Owner provisioning (Device OWNER, NOT just Device Admin). So, for now, I get to ignore having to hack through the security on this thing.

While the .apk file is still in /oem/vital-app/, Android is effectively ignoring it and allowed me to install Torque Pro from the Play Store without issue.
[Android Head-Units] clauton:
My friend. I have the S8 Standard. I downloaded the "ATOTO_S8_Gen2_7_Inch_OS_220811.zip" update from Atoto support.

Do I do these steps to root?

1) Unzip: ATOTO_S8_Gen2_7_Inch_OS_220811.zip

2) Replace the boot.img with the file patched by Magisk from within the 6315_1.zip file

3) I sign the file 6315_1.zip

4) I put everything on the flashdrive and apply the update

If I do all these steps I won't brick my S8 ???
[Android Head-Units] j21blackjack:
I cannot guarantee, but this sounds correct. It's been a long time since I rooted mine. I recently applied the 20220811 update and never bothered to try root again, it works fine without it really.
[Android Head-Units] nbetcher:
PUBLIC SERVICE ANNOUNCEMENT: DO NOT UPDATE TO 220811 IF YOU WANT TO ROOT YOUR S8! There is no known root method at this time. This concludes the public service announcement — please resume your normal driving activities. Thank you.
[Android Head-Units] clauton:
Thanks !!!
[Android Head-Units] nbetcher:
Although not applicable much to the main topic of this thread, I wanted to update some of the information I provided above.

SecureTask does NOT appear to have any or much Proguard obfuscation in its decompiled bytecode, surprisingly! As such, if the developer abandons it, does not communicate, and does not assert his legal right to copyright, I will decompile it and re-release it (legally).

Secondly, I have confirmed: SecureTask does NOT use the password for anything at all in its configuration, and in fact doesn't even store the password once entered (if I remember that last part correctly). Do not use SecureTask if you do not have a SECURE lockscreen (with something other than a stupid-ass Z as a swipe pattern, or 9998 as a PIN, etc) or you have reason to expect the lockscreen can be easily defeated (E.g Samsung phones and others).
[Android Head-Units] drsuse:
I got it rooted with that version today. I have the S8g2104 PR-N. I manually did the install for the newest update and checked on the developer options and my bootloader was still unlocked from before. And then went into developer options. Enabled USB debugging booted into the bootloader ran the command fast boot flash boot.img from my magisk patched image and booted it back up. I had to run magisk again but after that everything is perfect and everything is rooted and running perfect now
[Android Head-Units] nbetcher:
I've tried this, yet Magisk continued to detect it wasn't loaded. I'll be honest, I didn't debug the issue a lot, but based on what others said here and my own experience, I reposted that it isn't possible yet in order to prevent lost time.

Can you please reply with the full filename (prior to extracting) of the firmware update you used? And the MD5 / SHA1 sum of the entire file? (sha1sum < filename.zip) Should just establish a baseline with your setup first.

Thanks
[Android Head-Units] drsuse:
Here are the steps I used:

1. went to the atoto download site

https://www.myatoto.com/ibookDetail?catalogueId=2820&ibookId=125

2. Searched for my version S8G2104PR-N and then clicked on the update which was named ATOTO_S8_Gen2_8&10_Inch_OS_220811.zip

3. Downloaded and extracted

4. put the firmware on an usb drive and plugged into the side usb of the floating screen.

5. Once you plug it in it will say update needs to be ran and rebooted.

6. i also went to the settings on the head unit and factory reset

7. wait till its all good and running the newest firmware

8. Opened the 6315_1.zip with 7zip (NOT EXTRACT), dragged the boot.img out of the 6315_1.zip to my desktop

9. plugged in my rooted pixel3xl (not sure if it has to be rooted) with magisk and selected the install option when you open magisk

10. Do a select file to patch, and patch the boot.img you had from your 6315_1.zip

11. it added a file to the downloads on my phone to magisk_patched.img or something like that

12. copied magisk_patched.img to my laptop in the "platform tools" folder, (assuming since you are in the thread, you already have it)

13. i renamed it to boot.img

14. now back to the head unit,

15. go to the play store and download an app called "developer options shortcut"

16. once you open it make sure oem locking is not locked, enable usb debugging.

17. top right of the developer options screen, click on the 3 dots and select the second option. (after reboot it will revert to the first one, so make sure its on the second.

18. plug in a USB A to USB A cable ( i have found that a usb c to usb a dont work)

19. now back to your laptop

20. i connected via adb and adb reboot bootloader

21. fastboot flash boot boot.img

22. fastboot reboot

then once its done and rebooted i installed magisk and ran it and updated it and it worked. when i hit install on the top option, it said direct install this option, i did that. and it updated then the install on one underneat it then tested it .
[Android Head-Units] shugo-chara:
If you did not unlock the Bl lock before upgrading to version 8/11, you will not be able to load custom boot files with magisk.

But unfortunately, 8/11 and later versions don't seem to be able to unlock the bl lock, I tried some methods and they all end up causing fostboot to hang. And it is not possible to roll back the update to before 8/11.

Not unlocking bl→magisk can't load custom boot→no root→dead loop
[Android Head-Units] drsuse:
yes i believe you are right, i unlocked my when i got it stock
[Android Head-Units] 03hdfatboy:
You can rotate it with a config.txt file. It’s up here somewhere how to do it. I had to do it at one time.
[Android Head-Units] 03hdfatboy:
I was looking that saw a post where someone had the rotated screen, LOL
[Android Head-Units] Douglas_D:
I figured it'd work itself out 😉
[Android Head-Units] themrgoats:
anyone able to root the new 8/11 update yet?
[Android Head-Units] scorpie67:
Maybe someone can help me. I own a S8 ultra gen1 and the bootloader is not locked

What I did - copied from the first post:

1) Patched the boot.img using Magisck (using my phone)

2) Added to the S8 Ultra zip

3) Used SignApkv2.jar (Java8) to sign the zip file (avoiding locked bootloader issues)

4) Copied the updated 6521_1.zip file into Atoto's firmware unzipped MicroSD and reflashed with patched boot.img

I have tried it with:

Magsik 22.1 or 25.2 to patch the boot.img using my phone

Winrar/7zip to open (not extrcating) 6521_1.zip

java8 32/64bit to sign the 6521.zio again

and with 3 different firmware files (all working unpatched - I have tried them all):

update file for ATOTO S8 Gen1 Series (Build Number 10.2)-25-5-21.zip (Atoto website)

system-update-only-applicable-to-S8-Ultra-Model-CA-31-8-20-no-root.zip from the first post

S8_ATOTO_ULTRA_JMEISTER234 v1.1.zip somewhere from here

no problems patching boot.img and signing the 6521_1.zip. I get a 6521_1_signed.zip and rename it back to 6521_1.zip

I can flash all these firmwares (patched and signed) without errors or issues, but after a reboot the S8 is stuck in a bootloop.

6521_1.zip from the first post gives me an error during the flash process.

Ahhhh - help, please

Done I used a firmware, found somewhere here in the forum

Universal_ROOT_7862_9863_8141_9853.zip
[Android Head-Units] 03hdfatboy:
This is my current setup Latest MD w/MainService, Rooted (Android 10 Joying AllAppUpdate) runs flawless
[Android Head-Units] rabinhood:
I confirm. All you have to do is extract that zip into root of USB flash drive, put it in ATOTO USB cable socket, an update notice will show, confirm, the device will reboot, then install magisk.apk, and your radio is rooted.

The only thing is to have latest file. It comes from Russian site:

Головные устройства TEYES SPRO+/CC2+/СС3 и Kingbeats K2+ (UIS7862, Android 10) - 4PDA

Головные устройства TEYES SPRO+/CC2+/СС3 и Kingbeats K2+ (UIS7862, Android 10), [Головное устройство][Автомагнитола][Android]

4pda.to

But before you can download it, you have to register an account, and pass an anti-bot test in Russian (it wasn't so easy to me). So I attach the latest version, at least in late 2023.
[Android Head-Units] scorpio76r:
How to you maintain root after an atoto firmware update?
[Android Head-Units] paco3346:
I just used this to flash an S8 MS. Worked perfectly without any hassle.
[Android Head-Units] Bastian90:
Here is some information about the S8. Codes and root :)

System press 4x ~> Password: 3368

Door lock malfunction ~> Password: 0000

Backlight ~> Password: 5768

Press 4-5x on user! ~> Activate developer setting: you can Turn on USB debugging.

Root: Universal_ROOT_7862_9863_8141_9853_new <<

Unzip the files onto a USB stick or Memory card, then plug it into the ATOTO and start the update, after the update remove the USB stick or memory card, then run Magisk, Magisk method direct installation, off you go. Sometimes you have to do this process 1-3 times, then you have root.
[Android Head-Units] nbetcher:
That's very useful, except you didn't provide any context to where these buttons and codes even go.

What System button? What User button? Where are these? How do we get to them?

Information is only as useful as how the person writes it.
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] IoIam:
The device conversion zip that is going around the Xiaomi EU forums is not helpful because it doesn't change the device name in the settings. All build.prop lines seem to change to K20 pro, however the name doesn't change in the settings and Amazon is not HD. Flashing pixel props changes the name in the setting to pixel 5 and unlocks HD, but breaks ANX camera. Is there a way to change my device name like pixel props does, but changing it to a K20 pro?
[Xiaomi Redmi 7 Questions & Answers] Jitosmi:
Please provide Redmi 7/Y3 Custom splash image creator tool or script!

Thanks in Advance:)
[Xiaomi Poco X2 Questions & Answers] mdSafin006:
MIUI 12.5 stable is applicable for poco X2 ?? and Link??
[Upgrading, Modifying and Unlocking] spikescot2005:
Hi,

New here so please be nice :)

I have an O2 XDA Orbit and was wondering if Windows mobile 6.1 upgrade was available for it. I am currently running Windows mobile 6.

Any help would be great thanks.
[Upgrading, Modifying and Unlocking] Rudegar:
http://wiki.xda-developers.com/index.php?pagename=HTC_Artemis

http://xdaforums.com/forumdisplay.php?f=316
[LG V20 Questions & Answers] morrisonantoine25:
I'm just wondering if there are any other roms other than Lineage OS with the latest version of Android? I know Lineage OS is good and all but having variety would also be great. Is GSI supported on LG V20 H918 or something?
[LG V20 Questions & Answers] xxseva44:
Check out superior os and crdroid, both amazing roms with a great dev maintaining them, i've been running his roms for about 1 month and it is an amazing experience, stable af and performs vary well, and we have fixed the mic sensitivity issue, and are currently experimenting with V30 blobs. Both are based on android 11. His build of crdroid isn't posted on xda so join the telegram group to see that.

sos/crdroid
[Google Pixel 5 Questions & Answers] rasseru16:
Hi,

I just wanted to know where Google/Android store data that relates to specific carrier restrictions as it seems that EE in the UK restrict the ability to manually change the preferred mobile network type, can this done somewhere deep within QPST or is this something embedded in the firmware somewhere?

I am aware that you can dial the universal code *#*#4636#*#* but I want to get into the system to modify individual carrier features like the lack of preferred network type.

Thank you for anyone who is able to provide any support in relation to my query.

View attachment 5275479

EE doesn't allow access to 'Preferred network type'

View attachment 5275481
[Google Pixel 5 Questions & Answers] MrBelter:
Just to add there is no preferred network type when using a BT Mobile SIM either, BT Mobile is of course is an EE MVNO.
[Xiaomi Mi 11] fingery:
Hi all,

Anybody any idea how to install YouTube Vanced on a stock Mi11?

I've installed the manager and microg from apkmirror but can't install YouTube Vanced as still being blocked.

The previous method of disabling miui optimisations from developer options is no longer there.

.... Alternatively any other way to have YouTube with less/no ads?

Any help appreciated👍
[Xiaomi Mi 11] User699:
If your shell can be run as root, search for ad and tracking hosts lists on the net and place them inside of your /system/etc/hosts file.

Also, you could use the app "Blockada".

Those methods will block ads and tracking systemwide, however...
[Xiaomi Mi 11] pogi.paul0119:
Use puretuber🙂
[Xiaomi Mi 11] pharos23:
sorry didn't read the last bit of your question.
[Xiaomi Mi 11] fingery:
Awesome. Much appreciated. Id never seen puretuber but works perfectly 👍
[Xiaomi Mi 11] daavid1995:
I installed a older version of Vanced YouTube thats a single apk.

YouTube Vanced 14.21.54 APK Download by Team Vanced - APKMirror

YouTube Vanced 14.21.54 APK Download by Team Vanced - APKMirror Free and safe Android APK downloads

www.apkmirror.com

Its Working very good.
[Xiaomi Mi 11] Eidenz:
You might need to disable MIUI optimization in the developer options. Always work for me. Also fixes a lot of notification issues.
[Xiaomi Mi 11] cerbsium:
But the MIUI Optimization is not displayed for everyone. For some people, the entry is not there under developer options (like in my case). If you search under settings, it shows the entry but when you click on the search result, it brings you to the developer options where MIUI optimization is not displayed. Seems to be hidden.

Just wondering why for some users it is there and for others not.
[Xiaomi Mi 11] Eidenz:
Hm I see. I saw the same kind of behavior on the F2 Pro forums before. My only guess is either the region you set, or the MIUI version (globale, Europe, China).

I bought the Chinese version (with region set to France), and the option is there for me.

But yeah, if you don't have it, you either have to use another app/version of Vanced, or deal with the manual installation that requires a PC, Split APK installer and the Shizuku app (kinda a pain to install a single app, but used to do that since I really wanted it on my F2 pro).
[Xiaomi Mi 11] cerbsium:
Makes sense, thanks for the explanation. I have the global version and the region is set to Germany. The interesting thing though is that several persons bought over the same shop as I did (was a special offer) and some have MIUI displayed and others (like me) do not have it. Maybe phones coming out of different factories or different production lines may cause this.

For now, I will wait to install Vanced. I hope that MIUI 12.5 fixes those things, if not, then I will go the route via Xiaomi EU ROM.
[Xiaomi Mi 11] Jhonxs:
Hello guys,

I have the mi 11 ultra china rom and i do have the option to disable miui optimizations in developer mode.

The problem is that as soon as i do that the fonts look really big and they don't resolve when tweaking the font size etc.

Do you know what are the downsides of disabling the miui optimizations from the developer mode ?

Mind you the rom is working flawlessly so far , i have all the notifications and functions ok.

Thanks !