yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] AlgoryThm1st:
I don't know man, I didn't do anything special. I just paired the devices as any other Bluetooth device and they worked out of the box. Have you installed the latest early 2024 Joying update? I first installed their update and only then rooted and started working on it. Maybe that plays a role.

Also, we have legit SU adb access. I was able to pull and flash back recovery.img partition through adb a few hours ago and do a whole ROM backup before that. There's no need for Custom Recovery to have access to the system partition, somehow access to true system partition through adb works, at least for me. Read AND write permissions. Did you give it a try yourself first or it was an impression you made based on other people's writings? Because it seems very strange to me, everything works fine here.

And if you have SystemUI modding experience, I would really love your help on that, cause I'm very unfamiliar with the structure and I'm reading to learn how it works and what needs to be modified as we speak. So any previous experience you have would be very useful here. Would you like to give it a try? Or if you already did, what's the error message you're getting?
[Android Head-Units] nFiniti:
Out of the box, it went straight on the bench and I did the Update right away. I got the download from Joying directly before I received the unit. I played with it a little bit but then came on here looking for root and went on with the Magisk Root method from Life. I didn't know the bluetooth issue until another person on the other post asked about how I was connecting all these bluetooth devices on previous devices. Which then there was 2 completely different Bluetooth devices listed with 2 different names and the 2nd one worked with everything I've thrown at it. So I made a video and quickly ended with a "WTF?" as I couldn't get anything to connect except my Galaxy S21. I tried a few different things from cheap ebay bluetooth keyboard, a Logitech MX Ergo Trackball, 12 Dollar amazon Bluetooth OBD2 Device, OBDX Pro VT, 2 Xbox Bluetooth Gaming controllers. The Logi and the keyboard didn't even show up during Sync and Search. the Xbox Controller and OBD2 Devices showed up but just sits there and does nothing. If I use the 2nd Bluetooth mode its the same exact name as the 1st and when I try to connect it sits for hours with the "waiting" circle. I figure Joying finally legit locked BT Down to only their devices or phones. Thats why its in its shipping box right now sitting on a chair next to me.

I did try to mess with ADB. I tried using the method used to download the Boot Partition on Magisk but I couldn't get the System Partition to mount. I could get SU Privileges. but unable to mount the System Partition. And the device rebooted automatically fast so I couldn't continue trying without restarting the process. I'd rather have full root, BUT if we have a for sure ADB Pull and Push of System Partition its just a matter of time before a Full System Root, then custom roms....

It has been about 8 years since. But maybe its like riding a bike? I thought it was pretty fun. Especially if you have some minor photoshop image skills. You can design. I made an animated LCARS looking TouchWiz SystemUI with widgets and buttons. It wasn't perfect but it was fun.
[Android Head-Units] nFiniti:
Moved from the discussion thread, felt this was a better place for it to be. This method was provided by @life and amended by me to help assist with root. This Method is a "Systemless Root" achieved with Magisk. It does require you to open the device. But according to Joying, it will not void your "warranty" due to the HDMI Port being inside as well and the only way to access it is to open the case.

All files needed were attached to this post for safe keeping.

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

Done.

Here is a link to the 1/6/2024 Update with an already patched boot image.

MOD-QCM6125 Android 12 1280X800 1920X720 2024.1.24.zip

drive.google.com

Flash exact same way you would the non rooted Joying Update. This will reset your device but you'll have a Systemless Root with Magisk.
[Android Head-Units] pajo985:
Hi,

For all standard settings, just install this app:

Hidden Settings - Access Hidde - Apps on Google Play

Hidden Setting app allows you to access hidden setting which hide from the user.

play.google.com

I haven't played with Bluetooth, but on older (intel android 8.1 units) it didn't work.
[Android Head-Units] AlgoryThm1st:
Could someone examine the ROM dump I have uploaded and explain to me what the heck they've done with the boot sequence? Recovery.img is useless. Although the partition exists, they somehow override it. Commands adb reboot bootloader, adb reboot recovery, adb reboot fastboot, all do the same thing: They reboot the device into that fastboot menu:

Meanwhile, any USB access to fastboot is disabled. The only access is probably using physical buttons that connect to one of the two ports on the PCB.

I even tried to flash TWRP directly to the boot.img, replacing the whole boot.img. Nothing, the same fastboot screen again.

Meaning we have to find what partition they store the bootloader and call that fastboot menu from.
[Android Head-Units] AlgoryThm1st:
Just crossed my mind it boots to fastboot due to verity check. Although I have disabled it through adb and also flashed an empty vbmeta.

(Just "thinking loudly" in case someone wants to follow the process and/or suggest any solutions)
[Android Head-Units] AlgoryThm1st:
After dozens of tries, I've finally managed to port and flash TWRP: Click me . I'll pass more info when I have it ready. The current status is it works perfectly, but somewhere there is an autoreboot timer, either in recovery ramdisk or boot ramdisk and I have to find it and disable it. Otherwise it autoreboots no matter what you're doing at the time, and obviously that's not good...
[Android Head-Units] nFiniti:
Dude that just made my heart pound! This is awesome news!

I've been trying to refresh myself with the Samsungs SystemUI I used to mod so I can jump in on the Joying unit. I am determined to enable the Soft Keys, or "Find Them", since they seem to be active in the Build.prop file already. That only means that the SystemUI has them mapped off the screen or mostly deleted. Its a feature they offer Active on the 11.6 on up. But not the 10.1. But it is a basic Android feature since the very first "Tablet Mode".
[Android Head-Units] AlgoryThm1st:
I knew you'd be happy to read that! :D We're getting closer man, I just need some time more and it will be done. About the soft keys, at least for my screen, I don't think the screen itself supports it but I may be wrong. I hope you'll find something, it would be good to also have soft keys onboard.
[Android Head-Units] nFiniti:
Its not about the screen size. This is an Android specific thing, Not a Joying specific thing. You can enable soft keys on Any Android Device from the very first Tablet Mode. Even on your cell phone if it doesn't have them enabled already like my S21 does. But I'll figure it out. I know its either mapped off the screen or they have modified it to something unrecognizable.

I sent you a lil more off topic message if you have any know how.
[Android Head-Units] DMon04:
Just throwing myself in here. I've been talking with nFiniti through Facebook Messenger and in the Facebook android groups. I'm willing to help out any way I can short of damaging our new head unit😂. Just got our Joying Snapdragon in the mail last week for our 2008 Toyota Sienna. I have networking experience but am not even close to knowing programming languages or anything like that. I know some basic Linux commands and networking stuff.
[Android Head-Units] CCJ22:
I have the 13.3" model and happy to test.

I see we have root for the 720p units but not the 1080 units
[Android Head-Units] AlgoryThm1st:
I'm sorry for the delay. I'm currently very busy and I don't have much time to work on the device. Things will get better later this month though.

Thanks for the offer man, we really appreciate it. If anything comes to mind I'll let you know but it's kind of everyone working on their own HU and sharing info here. So if you'd like, feel free to experiment with it and share any findings.

It is possible for the 1080p devices too, but I'd need the recovery image of one of them to modify it and upload it back. Currently I'm stuck with a timer issue though, I can't find the file that triggers the countdown. After a while the device reboots itself, no matter what someone is doing at the time. That timer is inherited from the old recovery, where if it didn't find any update files, it was programmed to auto reboot. Maybe a more experienced developer could help.
[Android Head-Units] Flame Red:
I tried to pull the recovery image of a 1080p unit, but I was unable to get ADB to work. I got the Joying into Developer Mode using Chrome, then get into developer mode and turn on USB debugging, but when I attached my laptop to a USB on the Joying and tried to connect using "adb devices" none were listed.

Not quite sure what I am doing wrong as I have a lot of experience with ADB on rooted phones, but this is my first with Joying. I will see if I can figure it out.
[Android Head-Units] AlgoryThm1st:
Probably a windows driver issue (if you use windows of course). Try to look for adb google drivers, they should work fine.
[Android Head-Units] Flame Red:
Thank you. I installed Andriod Studio and then went into Andriod STK ==> SDK Tools tab and checked off Google USB Drivers which it then seemed to install.

But no luck - no devices listed (blank).

I'll keep trying. Got to be something stupid...
[Android Head-Units] Pulpster:
I think you need to change the USB mode to device. Go to the settings on the head unit. Settings>Display>App Management and Permissions. Use the 3 dot menu in the upper right hand of screen. Select USB Computer Connection. Change USB Mode to device. You should now get adb devices. I got a ? but adb worked fine.
[Android Head-Units] Flame Red:
Thank you. I was wondering where the "MTP" setting was hidden. Unfortunately, still not seeing the Joying. I'll keep playing with it.

I tired the laptop with my Samsung phone and the laptop and adb worked with the laptop. So this is something related to the Joying side I think. I don't hear the laptop beep when I plug in the USB to the Joying where I do get a beep and a permission question on the phone. So something seems to be needed on the Joying side I think.
[Android Head-Units] jm001:
I have the 1280x800 screen. I loaded the magisk image above in the thread with no problem. I do not see a reboot issue. The only two problems I have are 1.) I can't pair some Bluetooth devices, and 2) the Bluetooth audio on calls is terrible. I also can help support testing of this unit
[Android Head-Units] nFiniti:
You positive you are changing over from Host to Device in the Android Settings? You wouldn't hear anything until you go into Device mode.

The Reboot issue mentioned is in the devices Recovery. Not the OS. If you used the image I've shared that is already done with Magisk, you're missing the actual root process that went through originally. In which you will notice that you have a limited amount of time with the device in recovery or fastboot before it will auto reboot without any reason. Even with TWRP Recovery flashed. AlgoryThm1st has been combing through system files for evidence of such a timer put in place by Joying to prevent people from modding.
[Android Head-Units] jm001:
Is there some setting that affects Bluetooth pairing, I am unable to pair any other devices than phones. --
[Android Head-Units] Coatezy:
Hey, looks like some good progress has been made here, I’m happy to assist where I can. It’s been a few years since I got involved in this kind of thing but happy to test etc. I’m a software engineer building Android and iOS apps so happy to get my hands dirty and reverse engineer. I only got my UZS07N8 installed yesterday but already these limitations are frustrating me.
[Android Head-Units] nFiniti:
This question has been moved to the other post. Just trying to help keep this specific to ROM Development.

Well Hello there! Some minor progress has been made thanks to a few. But everyone is busy so its been slow development. @AlgoryThm1st has made some great strides to help break us into the device but he has hit a wall trying to locate some Anti-Modding Timer Joying has somehow implemented. This timer restarts the device no matter what when you're in bootloader or recovery. TWRP has been successfully ported over but due to the timer, you can't safely flash anything because the device will restart no matter what you're flashing.

If you haven't updated your device to the Jan Update, you can but if you do I suggest using the file I have shared. Its the Update file with the Magisk Root already applied. OR you can perform the Magisk Root Method I also shared on the pre update system.

However there are issues with the update that Joying doesn't want to address right now. The main issue is the Call To Home spyware they have added that forces the user to keep their device connected to data at all times. If you shut off any data sources, a transparent pop up will appear telling you to connect and it wont go away until you do. I don't know for sure but I wouldn't be surprised if this is sending user information to some sort of Chinese party.

Another issue, is about half of the users I've read about or spoken to have experienced the same Bluetooth Limited Functionality that I have. This is limiting what bluetooth devices can connect to the unit. In previous FYT (Non Snapdragon) units, to connect a Bluetooth Device that isn't approved by the Joying BT App, we would perform a workaround by accessing the "Android System Settings" and use what looks like a 2nd Bluetooth Device with a completely different name and password as the 1st found in the Joying BT App. This would let us connect anything we wanted. But now, this workaround doesn't work. Both the Systems BT and the Joying BT App share the same name and most devices that are not a phone will not connect. Some BT Devices wont even be visible. I Personally have tried a few XBox Wireless Controllers, a couple different Logitech Bluetooth devices. And I have tried a couple different OBD2 Devices. The only devices that connect are my phones. The others either show up and don't connect or wont show up at all.

So currently on the Roster is to find a way to disable this call to home function Joying has implemented. And locate potential limitations in the Bluetooth connectivity, whether it be some sort of lack of drivers or whatever. Then after this we are wanting to work on developing a custom rom or kernel to help with these issues and enhance the device. The hardware is there, the Software needs help and Joying is neglecting the users.
[Android Head-Units] Coatezy:
Thanks for summarising everything @nFiniti! I spotted the YouTube video showing the call home “feature” add recently, I have a 4G sim installed so it’s probably happily sending data in the background. I’ll grab the update with Magisk root applied and install once my replacement unit arrives, it’s probably a lost cause but I wanted to see if another unit also has the same terrible back light bleed that my first one has.

Regarding Bluetooth, I’ve had success connecting an ELM327 OBD2 device, I also used an 8Bitdo Bluetooth dongle to hook up a Bluetooth controller, I’ve not tested it with any emulators yet but I downloaded a controller input test app and all controller inputs from my Bluetooth controller were working as expected.
[Android Head-Units] nFiniti:
Is this Pre January Update? I don't understand why others have success but I cannot get squat to connect except my phone. But I didn't use a USB/Bluetooth Dongle. That is an interesting idea that I did not think about. I just been using the built in bluetooth. Maybe I should give that a try.
[Android Head-Units] Coatezy:
So I used the built in Bluetooth for phone and ODB2 but a 8bitdo dongle for the controller. The dongle connects to the controller by Bluetooth but presents itself as a wired controller to Android. I’ll grab the current version that I’m running later.
[Android Head-Units] jm001:
Ive been thinking about the Bluetooth issue, as this is significant for me. My understanding is that Android 10 and up use shared library modules in apex format for platform level code. These modules can even be swapped out for development purposes. Do you think it's possible to test by installing/swapping an ASOP Bluetooth apex with a systemless root image?
[Android Head-Units] AlgoryThm1st:
Hello again! I know it's been a while since the last time I wrote here, but things with the job went south and I'm running like the roadrunner...So no time to work on the HU right now. I'm uploading the modified recovery file, in case someone else would like to take a look or look for the timer. The file will be at the original folder, from the first post of this thread. You all take care and keep up the good work! Talk to you soon (I hope...)! (The modified file is called TWRPrecovery.img)
[Android Head-Units] nFiniti:
That is sad to hear. You're for sure much smarter in what to look for and what to do about it than I could be at this point lol. I can understand basic html sort of stuff for theming and what not. But I wouldn't know where to look for such a thing. I'll tear open the file tho just to look inside it.
[Android Head-Units] AlgoryThm1st:
Thank you for your kind words my friend, but I think I'm not nearly as skilled as some other people people here that as it seems they will be able to help much more than me. I need that HU in my car too, but it's not going anywhere until we find a solution and install either a custom UI or custom ROM. I thought things with the job would get better but I'm still deep in the tank. The good news is we have an android developer in the team now and many other people willing to help. I'm positive that a team effort will bring great fruits to the table.

@Coatezy Hello and welcome man! Well, I have uploaded a whole rom dump, you can find it on the first page, first post if you want to take a look. Our primary and more practical goal I think would be to make a custom UI for this thing. Building a new ROM from scratch, would be significantly more challenging and (thinking with my limited knowledge) would take considerably longer time. The worst thing they've done IMHO is they have custom programmed the accessibility options and disabled the default android menu and also access to accesibility options by the apps. That alone, at least to me, is extremely annoying, as we are stuck with their custom notifications bar/icons/notifications themselves but most important, 3rd party car launchers face significant limitations. Limitations concerning navigation between apps, something that can become quite dangerous, considering the thing is supposed to be used while driving. So the best case scenario, again in my opinion, would be 1) Build a custom UI with all android default options restored 2) take care of the bluetooth issues some people have (I personally am not facing those issues for some reason but I believe they do exist on some devices) 3) if possible build a custom proper FM radio software that could be resized and fit in a custom launcher so we can switch between all basic apps using a single button and not having to use home and back buttons while driving. Of course things like "calling home" apps must be taken care of, but that's the easy part. That's a sum of the key requests so far I think, other people can contribute with ideas as well of course.

I've read about the concept too but I have my doubts when used with a systemless root approach. Never done it but if you try it I'd be glad to hear about the results.
[Android Head-Units] capidamonte:
Could anyone point me to the ip address(es) that it phones home to? Wondering if I keep it on wifi if I can spoof something. Planning to buy this unit next month... now I wonder if I should consider a different rootable rom-able HU.
[Galaxy A3, A5, A7, A8, A9 Q&A, Help & Troubleshoot] AlphaTekk Epoch:
I am running ExOS v 2.1 on the Galaxy A3 2016 and was wondering if there is any way I can convert the root installation from system-less root to system root?

Install SuperSU into /system option is grayed out in the SuperSU app with the message

Not (currently) available in system-less root mode

Is there another way or a means of changing that to currently available?
[Galaxy A3, A5, A7, A8, A9 Q&A, Help & Troubleshoot] V0latyle:
Why would you want to?
[Galaxy A3, A5, A7, A8, A9 Q&A, Help & Troubleshoot] AlphaTekk Epoch:
Honestly, I have no idea if it's better or not or what the differences are, might I inquire what you'd prefer and why?
[General Questions and Answers] trilling:
when I launch the install for ODIN, I see the following warning:

Please be sure to delete your Google account (Samsung account) before downloading the binary. It is not possible to use the device without unlocking. Changing the partition without unlocking will cause problems.

That's a little unspecific, and a little scary.

Which account ? Google, Samsung or both ? From the phone or from existence ?

In my case, I don't have access to the phone (FRP), which is why I'm flashing it.

What does the 'unlocking' part of the warning mean in my case ? Does flashing change the partition ? There are several. Which one is it referring to ?

Can someone please clarify the warning ?
[General Questions and Answers] xXx yYy:
To answer your questions:

Which account? The warning refers to both your Google account and Samsung account.

Location of account deletion: You need to delete the accounts from the phone itself before starting the flash process. Without deleting the accounts, you won't be able to set up the phone after flashing.

Unlocking: Unlocking refers to unlocking the bootloader on your phone. This is a separate step from deleting the accounts.

Flashing and partitions: Flashing replaces the software on your phone's partitions (which are sections of the storage). ODIN likely refers to unlocking the bootloader in general, not modifying a specific partition.
[General Questions and Answers] trilling:
Thank you for your reply.

Now the situation: I have suceeded in triggering FRP by entering an incorrect password too many times. I did not set up a Samsung account. I did use gmail, but apparently I missed something, because when I try to recover access using that email, it always comes back with "something went wrong". I do have access to the email address, and use it all the time.

I did not turn on Developer mode, which I understand to be a way back into the phone.

I did back up all of my data, so I won't lose anything by wiping the phone, which I think has already happened, because when calls come in they only show the number and not the name I entered as a contact.

Now you are telling me that if I flash the phone, it will brick.

Do I have any options here ?
[General Questions and Answers] xXx yYy:
Turning on Developer mode on an Android phone does not open a backdoor to get into the phone . It won't bypass any security measures on your phone.
[General Questions and Answers] trilling:
each of the "recovery solutions" I see out there includes a dependency of having Developer mode turned on in order to make communication possible between the phone and an app installed on a PC, with a USB cable connecting them.

I also see methods involving putting the phone into Download mode in order to get an apk onto the phone.

is all of that bogus ?

do I have any options ?