yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] JMeister234:
I actually don't see the USB debugging options in the developer options. I did the 3368 thing but nothing in that menu looks anything close to USB debugging, ie same as my phone.

Without that, I don't know how to adb shell into the unit.
[Android Head-Units] kramttocs:
I'll have to check later but I believe it was from the top right 3 dot menu.
[Android Head-Units] JMeister234:
1. I can confirm that I flashed/updated the S8 Ultra using the Dropbox zip file above and after it reset Android, it did nothing but reset my google credentials. My apps were still there.

But it also didn't brick my S8 Ultra .

It has the similar files as the Joying zip file which has the same chipset.

After the flash, my phone asked to authorize the adb debugging, while connected to the head unit. I'll see if I can get the head unit to turn on adb debugging so I can root it.
[Android Head-Units] JMeister234:
Another?

View attachment 5261929
[Android Head-Units] buffaloquinn:
Any new developments?
[Android Head-Units] JMeister234:
Well I brought my Ouya back from the dead with LineageOS, converted a Chromebook to GalliumOS for pen testing, or it can connect to Ouyas using adb, or analyze a Lenovo Smartclock to try and add APK's to it before giving up (as others on XDA have also done).

But for this? I can't get ADB to see the head unit. Because there is no ADB Debugging in any of the menus (yes its has Dev Options enabled). No idea how others have done it. If I reboot into Recovery it might show up in "adb devices" command but if the device is simply on, there's nothing returned.
[Android Head-Units] buffaloquinn:
I use one of the Play Store apps to get into Developer options and it does show an ADB debugging option and most of the other choices available in a typical Developer's menu. The one I use is the first one that comes up in the search on play store, I think the author is Singlebyte.
[Android Head-Units] JMeister234:
Update. I changed USB logging. But two laptops, 2 cables and 4 USB cables coming out of the head unit, and I still was unable to see adb devices anything.

https://xdaforums.com/t/howto-root-joying-sc9853i-head-unit.3915530/

However, feeling invincible and comparing their boot.img to their patched IMG file (5kb difference) I tried to root my head unit using the Joying patch.

It didn't brick anything but it also didn't do anything positive. Radio doesn't work and big red letters are stuck across my screen.

I'll revert back using the Atoto firmware tomorrow.
[Android Head-Units] buffaloquinn:
I was looking at the same root idea myself. Disappointed it didn't pan out.

Let us know if it reverts back okay If it does I might get a little more daring myself.
[Android Head-Units] buffaloquinn:
So here is another option that might be worth a try. You have the firmware that you updated from and you said it works well so in theory you should be able to extract the working boot image from that. If so, might this method work?

https://xdaforums.com/t/root-magisk...-device-with-magisk-without-recovery.3779454/
[Android Head-Units] buffaloquinn:
Backtracking a little here. How did you do the update? Did you put the update zip file on a USB flashdrive or did you use an SD card in the TF slot? Also, how did you get the unit to do a cold boot, which I assume you need to do to flash the update?
[Android Head-Units] JMeister234:
Yup it's back to normal minus my installed apps and maps.

The Joying sc9853i and the Atoto S8 series have very close boot.img files. I suspect some audio drivers caused the radio app to crash. So don't go that route.

But I'd also guess that you can flash those two files if you get into trouble. If you're worried just beg Atoto for the rom for your unit.

Claim:

- touch screen doesn't work and you have only Bluetooth mouse and eventually let them suggest the idea of flashing your unit...
[Android Head-Units] JMeister234:
Saved to a MicroSD card with the right zip file on it which launched an immediate option to Start flashing or Cancel.

Not necessary to use the reset button (pin hole) or hold down the power button for 10 sec.

Magisck installs but doesn't give me the option to select a boot.img to patch. I'm not sure if I can do it on another device with Atoto's boot.img and then flash it via a signed Zip using the java jar.

Can't hurt I suppose.
[Android Head-Units] JMeister234:
So able to patch on my phone using the Atoto boot.img. But not able to sign the zip and the odds are against it working. There's a deprecated java library (BASE64 from sun) which which means I have to go back to Java8.

This step wouldn't be necessary if I could just get adb to work.
[Android Head-Units] buffaloquinn:
I put in a request to ATOTO for my firmware, well see what happens. I suspect it uses the same one as the Ultra though because some of the options in system menu are hardware features only available in Ultra devices. If you get a chance can you grab me all relevant info on the Ultra firmware so I can compare it to mine.
[Android Head-Units] buffaloquinn:
I'm going to try to get ADB working sometime this weekend. I'll let you know if I have any luck. Did you unlock the bootloader already?
[Android Head-Units] JMeister234:
No. I've signed the Zip 6521_1.zip using the jar file for Joying under an assumption that it will work.

=> Oracle didn't send me a frickin password reset so I had to get Java8 from OpenLogic

=> the size of the 6521_1.zip is half what it was (the boot.img vs patched is only 5kb bigger)

=> I've copied the patched boot.img into the zip file and resigned it which I think means that I'm "fooling" the bootloader (and don't need to unlock it).

No adb, no fast boot. Working on a chromebook with GalliumOS. We'll see how this goes shortly.

Edit: latest SignApk2.jar created a similarly sized 6521_1.zip file. So I'm going to use that instead.
[Android Head-Units] JMeister234:
Created a MEGA account to upload the zip. Recommend you create one as well (to copy zips to yours MEGA) to avoid hitting download limits

=> click the "Import to my Cloud Drive" in upper right

3.33 GB folder on MEGA

11 files

mega.nz
[Android Head-Units] buffaloquinn:
So it's this the Update to Ultra with the Magisk patched boot?
[Android Head-Units] JMeister234:
The same two files are used in the Joying and the Atoto head units (both based on sc9853i intel/GPU head units). Which makes me believe (?) that you can take just the two 6521_1.zip and 6521update files, load them onto a microSD card, and it will kick off the update.

925.05 MB folder on MEGA

mega.nz

The S8 ULTRA zip file contains the whole thing with the patched boot.img and the signed 6521_1.zip (and the unpatched one as "goodboot.img" should you want to flash it back to original) but that should be avoided if you don't have an ULTRA.

Are you able to do the "safe" flashing where it resets back to stock on reboot if it doesn't work?

% adb reboot bootloader (wait a couple of seconds then)

% fastboot boot boot.img
[Android Head-Units] buffaloquinn:
So, do you have root after all of this?
[Android Head-Units] JMeister234:
I thought I did but I don't. My bad.

I have a new plan though. I'll edit the flashing shell script to load busybox and SU binary.
[Android Head-Units] buffaloquinn:
Did you run the Magisk app after you updated the boot image?
[Android Head-Units] JMeister234:
Yes. Which led me to believe I was successful, along with Termux saying I had the root # prompt. But RootCheck and SuperUser tells me no.

=> so now I'm looking at copying su, busybox *in the atoto flashing script* and chmod 7775 them so they're basically a part of the image.

Most people who do this either have a) an unlocked bootloader and b) access to Recovery/ADB/fastboot but I can sign (I'm sure) the firmware so I don't find a lot of help on the inter-web.

I also muck with the apps pre-installed (editing the Allapp.pkg using "xar") because EasyConnect.apk gets in the way.
[Android Head-Units] buffaloquinn:
RootCheck has been know to return a false negative. And are you talking about the Superuser in Magisk or a separate program? Because a separate program won't recognize Magisk's binaries.
[Android Head-Units] JMeister234:
I think it was a true negative. I couldn't do anything that I couldn't already do.

I was able to flash my head unit one last time before that damn little microSD card disappeared somewhere (taking all my updates with it). It's slid into the back of the car seat and now I have to wait for Amazon to deliver another (or choose to lose all my Nintendo Switch game data).

=> I changed a script to copy the su/busybox binaries to /system/xbin/ and chmod them to be executable.

I have not tested to see whether it worked or not.
[Android Head-Units] buffaloquinn:
That sucks. I've always got at least a half dozen SD cards floating around. I use them in USB readers as flash drives and a number of my laptops have built in SD readers as well.

I'm going to drag one of my laptops out to the car this morning to try my luck at ADB.
[Android Head-Units] buffaloquinn:
So. Good news is I got ADB working. The Developer Options three dot second USB choice allows for the computer connection. Unfortunately, it resets on reboot. So if I ADB reboot bootloader, it restarts in fastboot mode but it is no longer connected to the computer. Haven't been able to figure a way around this. It's there any way to send fastboot commands by a connected keyboard perhaps?
[Android Head-Units] buffaloquinn:
When I did "ADB reboot fastboot" I got nothing. When I did " ADB reboot bootloader" I got a line that said "fastboot mode" at the top of the screen, but nothing else. No menu. Did you get a fastboot menu?

Also the USB computer connection mode resets on reboot, so you don't have access to the unit anymore after the reboot command. Haven't found a workaround, have you?
[Android Head-Units] JMeister234:
If you have fastboot, then you can try

$ fastboot boot patched_boot.img

Can you "su" in adb shell?
[Android Head-Units] buffaloquinn:
I think you missed the point. Although I can get ADB to reboot into FASTBOOT, I cannot send any commands to it because the head unit reset the USB connection on reboot so Fastboot just sits there waiting for a connection. I haven't tried "su" in the ADB shell yet. I also want to try it in Termux on the head unit.

BTW, I did get ATOTO to send me the update file for my unit.
[Android Head-Units] JMeister234:
Cool.

Because I found the below link which is basically what I'm trying to do for the Ultra, which they did for Joying using the same scripts. I just need to remount /system as rw and then I can copy su/busybox into /system/xbin/

https://xdaforums.com/t/modding-you...it-without-root.3974357/page-12#post-82485735

Amazon sent me a 64gb card overnight so I'm trying this again.
[Android Head-Units] JMeister234:
Update: And then I patched the boot.img file and flashed it using DD, only to be thrown into a boot loop.

I reached out to Atoto and they suggested unplugging the car for 10 min...

I added the clean MicroSD and on booting the first time after the 10 min battery disconnect, it relflashed the unit.

So that's good to know....

Before patching, I was able to use the script to copy over su and busybox and chmod them but that didn't get a rootchecker pass.

Are there special su for Android 8? The root kit was for KitKat.
[Android Head-Units] buffaloquinn:
It is my understanding that root kits that worked on KitKat are pretty much useless on higher versions.
[Android Head-Units] JMeister234:
I found an Oreo root kit from a Samsung S7/Oreo and I'll use that instead.

Only two files are required + the two binaries (under /root on the sdcard):

lsec6521update

lsec_updatesh/lsec.sh

mount -o rw,remount /system

cp /storage/sdcard1/root/su /system/xbin/su

chmod 6775 /system/xbin/su

cp /storage/sdcard1/root/busybox /system/xbin/busybox

chmod 6775 /system/xbin/busybox

Pretty simple/quick. I'd rather not flash the Joying boot.img again. It uses the flash/patched boot.img and risk another boot loop.

https://xdaforums.com/attachments/rooting_fyt_sc9853i-zip.5017101
[Android Head-Units] buffaloquinn:
Am I to understand you put the above lines of code into the update file?

Did it work?
[Android Head-Units] JMeister234:
It works in so much that it was "successful" but not that it appears to do anything.

=> I also copied the Joying script to take a backup/dump all the partitions to IMG files

=> the script itself is like being able to run root commands (but only until it reboots)

I popped out the head unit to remind myself about the set up. I have 4 usb cables coming out of the ultra, split from two actual connection plugs. Being able to "adb" or "fastboot" is still the sticking point. I wished I had bought the lower end models (since adb/fastboot seem to work on those).
[Android Head-Units] buffaloquinn:
I've got the premium and ADB works but it's of limited use since you can't do much without root. If I could input to Fastboot when it reboots into it, I'd be all set, but the computer connection is reset on reboot..
[Android Head-Units] buffaloquinn:
I'm pretty sure the key is getting the bootloader unlocked. I wonder if there's any way to do that from within an update script.

I think the Joying Magisk method would work then.
[Android Head-Units] buffaloquinn:
So I've made a little bit of progress. Found a link on XDA for updated ADB/FASTBOOT drivers and now I can actually send FASTBOOT commands. It recognizes the unit when it boots and lists it when I do a Fastboot Devices command. It will even reboot back into bootloader when I issue that command. It isn't unlocking the bootloader however. Using either the "Fastboot flashing unlock_bootloader" or "Fastboot flashing oem unlock" just returns a line with "..." on the computer & it just waits there.

It seems like it's waiting for something from the unit, but there is nothing on the unit screen. I'm wondering if I'm supposed to press one or more of the buttons to initiate something. Haven't got a clue.
[Android Head-Units] buffaloquinn:
Ok not sure why you can't ADB, makes no sense. Try updating via this link. This is the guy that finally got my computer to run Fastboot commands to the head unit.

[Tool] Latest ADB Fastboot and USB Driver installer tool for Windows

All praise and All Thanks to God ADB Fastboot and USB Driver installer tool for Windows, which will always install the latest version. To update the adb fastboot and usb drivers again, just rerun the tool. OS Requirements: Windows 7 and Above...

xdaforums.com
[Android Head-Units] b0b88:
i'm following all of this closely lol, I thought your other post was the newest update... now I realize there are still issues... I am really stupid excited to possibly root this damn thing, all so I can keep PDAnet from closing and lagging because its always running in the background XD and maybe play with some other things as well. i did try to flash the s8 premium with the ultras firmware and it threw an error and rebooted without any problems. I'll wait for atoto to hand me the premium firmware before I play anymore :) I definitely think you are onto something and i'll really delve into the russian site, my wife is russian so maybe she can help translate some things :)
[Android Head-Units] jayone24:
hello

I have the last atoto s8 gen 2, does anyone know how to acces the hidden menu for the carlink app ? I saw this menu the very first time I launch it but now it never appears...
[Android Head-Units] blk.kalel:
Still cant figure out how to get to Developer Options. Can you share the secret?
[Android Head-Units] mrphil101:
I think this is how it happened: in the settings menu tap the User& accounts icon 4 times and it activates the developer options in the system section. Didn't see this posted anywhere or i missed it. Not really sure that this is how it happened but don't recall seeing the option before.

EDIT:

I loaded Total Commander for a file explorer and it shows pretty much everything on the unit. I can see that there are two "settings" there. One is the crappy knocked down version we get and the other is the full blown settings app. That is what I was attempting to get to when I found the developers menu in above post. SO, does anybody know how to get the full settings app working?
[Android Head-Units] c_86:
Hello everyone, I need some assistance... I am trying for the life of me to get ADB on my atoto s8 premuim, and cannot.

I have dev options on, i set the USB mode from the 3 dots to the 2nd option, made sure that the ADB debugging is turned on in dev options, have installed the latest drivers onto my PC, and have the default usb set to file transfer , and nothing....

I am connected with a high graded USB going from USB C (computer) to USB A phone link on desk, open my adb window and nothing, never shows any connected devices ....

Also note that my computer doesnt seem to show the device in device manager, but I get a prompt when i connect it via USB that my PC is not able to charge... not sure if that matters...

All i want to do is disable the navbar for gesture navigation so i get some more screen real estate.

Thank in advance for the help!
[Android Head-Units] c_86:
Ok, i got it figured... I have using a high quality USB C to A and was plugging the A into the head unit and the C into my computer. It was partially detected doing this. Computer would say that it cannot charge.

This morning, I decided to create my own USB A male to USB A male cable, and plugged into the head unit and computer, and boom, computer fully detected it. Was able to ADB device it without issue and was picked up immediately, and was able to run commands.

Now, not sure if this is a limitation of the android version thats on it, or android in general, but what I wanted to do was run the command to nide the navbar/status bar to gain some height in apps when running in split screen (as some of them look funny and are a bit "compressed". So wanted to gain back the couple of pixel at the top.

Well ran the command and the nav/status bar auto hides now on the home screen, and full screen apps, however doesnt when apps are running in split screen mode... So this is where I am at now..

Anyone know how to hive the navbar/status bar completely? Even in split screen?

I have searched an all commands I ran to hide the navbar/status result in the same, so I am thinking its either a limitation of this version of android, or its so customized that something is over riding the hide ADB command.

Anyways, thanks for the help!
[Android Head-Units] ODIN679:
Just did the latest upgrade to mine, the option to disable birds eye view is now in the main settings, don't need to enter the ones protected by code. The code is the same still..

Manual and Installation Video

ATOTO Electronics car stereo and in-car entertainment products including in-dash & on-dash GPS navigation, wireless Android Auto Enabled Receivers, wireless Apple Car Play enabled Receivers, Android car stereo, Double-DIN car radios, bluetooth car stero, car multimedia system, car speakers and...

resources.myatoto.com
[Android Head-Units] ODIN679:
Use the cell phone to browse, on the PC it just sucks
[Android Head-Units] 03hdfatboy:
Site is kinda jacked up isn’t it?
[Android Head-Units] stepir:
1
[Android Head-Units] stepir:
hey did you got this working or made any progress? I found you because I'm trying to achieve exactly the same - gain more height in split screen - and was actually struggling in getting ads to work....
[Android Head-Units] 03hdfatboy:
I have a usb 2.0 to usb 2.0 for ROG connect (PC MotherBoard overclock tools), I wonder if it would work. I also have another but don't remember what it was for. Might have to explore. what software are you using?
[Android Head-Units] stepir:
I sorted it

I sorted it - you need to go into dev options and enable usb debugging + change usb config to file transfer (default is no data transfer) + top right click 3 dots -> USB connections and select second options (it written in Chinese). It will immediately connect now
[Android Head-Units] stepir:
BTW: can confirm that even with System UI - you can enable full immersive mode but the status bar will be back as soon as you split screen
[Android Head-Units] 03hdfatboy:
Here is mine Latest MD w/MainService, Rooted (Android 10 Joying AllAppUpdate) runs flawless
[Samsung Galaxy S9  Questions & Answers] pables69:
I'm trying to following the instructions located here. I have done an OEM unlock and have the latest Samsung firmware installed to my device. I have put my S9 in download mode and plugged it into my Mac. When I try to run the heimdall command in terminal I get this error:

Pables-MBP::usr:local:bin Pables$ heimdall print-pit

Heimdall v1.4.2

Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna

http://www.glassechidna.com.au/

This software is provided free of charge. Copying and redistribution is

encouraged.

If you appreciate this software and you would like to support future

development please consider donating:

http://www.glassechidna.com.au/donate/

Initialising connection...

Detecting device...

ERROR: Failed to detect compatible download-mode device.

I also have tried on my windows laptop and run into a different error (I've removed the part that identifies my specific device):

C:\Users\Pables\Desktop>heimdall print-pit
Heimdall v1.4.2

Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/

This software is provided free of charge. Copying and redistribution is
encouraged.

If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/

Initialising connection...
Detecting device...
libusb: error [init_device] device '\\.\USB#VID_17E9&PID_4323&MI_01#7&3[removed]' is no longer connected!
libusb: error [init_device] device '\\.\USB#VID_17E9&PID_4323&MI_02#7&3[removed]' is no longer connected!
ERROR: Failed to access device. libusb error: -12

When I plug in the device normally both computers can detect it and access the files. Any advice?
[Samsung Galaxy S9  Questions & Answers] B1nz:
I don't really know about heimdall, but what are you trying to do? maybe I can give you the alternative

If you're using windows have you install the necessary phone drivers?
[Samsung Galaxy S9  Questions & Answers] djtomex:
I am not an expert here but just by reading this errors, to me your mac software says the phone is not in download mode, meaning the phone will not accept the connection the mac is sending. Are you certain your phone is download mode? Maybe change the cable as i had many issues when i was not using the original cable of Samsung( phone was connected and i can transfer to it but, in download mode the pc/ mac would actually not see it).

Windows seems like is not finding the USB driver to establish connection to the phone. Maybe I am wrong but i just did a search on the error and and HP USB driver seems to show up.
[General Questions and Answers] afriddle:
So I just got this phone,literally 2 hours ago and love it. Had to do some tweaking to get the 120hz forced but one thing I can't get over is the PiP with YouTube. Basically when I try to restore the video to normal size the animation is wild. See attached. If anyone knows how to fix this I would appreciate it greatly!!

[IMG="animationbug"]

https://imgur.com/gallery/BADwRfY[/IMG]
[Advantage X7500, MDA Ameo General] sgres:
Misters, help please!

My handheld computer HTC x7500 has ceased to work.

By pressing soft-reset or hard-reset the indicator on the central button shortly blinks red color. More nothing occurs.

At connection of an external feed the indicator of the central button is not shone, indicators bluetoth, wifi do not blink also.

If to take out the battery and to connect an external feed - the indicator of the central button is shone by red light constantly.

The device sometimes itself was switched off at a full charge battery for a week before it.

Yesterday it was switched off and does not join. Soft-reset does not help.

The device did not fall on a floor or in water.

I have replaced the battery. Has not helped.

Please prompt what to do! The service is not available yet. In my city such devices - units.