Switch dongle from "factory" to "android based"? #8
Comments
|
I was trying to turn my android version dongle to this one use /usr/sbin/fakeiOSDevice. I did a lot of research on the autokit apk. I think most core codes hide behind binaries, which could never be reversed. For your issue, you can check the dongle's vid and pid. Cause in the apk /res/xml/device_filter.xml it allows vendor-id="4884" product-id="5408". By the way, the android dongle update image encryption differs from U2W one. I could not reverse-engineer the Auto_Box_Update.img. |
|
@milesking Sorry for the late reply. Funny, I did try to mess around with the vendor and product, but I couldn't get the tablet to do anything. I think the flow is: I've read some docs that say vendor and product id in the xml must be represented as integers After I posted this issue, I decided to order one on ebay. Unfortunately, it appears to be lost. Anyway, when it arrives, I "think" I know how |
|
Waiting for your good news. As for the U2W one, I guess there comes the license issue even if you figured out the vid/pid issue. |
|
Following up.. Unfortunately no good news. I think my wanna-be reverse engineer-er days might be over. 😃 I finally received the Carlinkit today. I tried it out on the Android tablet and it worked well. I then tried to dump the 25L12835F and I think it self destructed. The blue led started flashing bright and fast on the board, then eventually stopped and went to a faint blue glow. It is totally dead. The dump seems valid up to 0x01F3458, but well before the jffs2 file system. |
|
Eventually, I bought the U2W dongle. Did not find any clue getting into the filesystem. |
|
@ludwig-v On my working unit, I removed Unfortunately, every time the device reboots, the filesystem is reverted and Have you seen this behavior before? |
|
What do you mean by reverted ? |
|
@ludwig-v Sorry, should have been more clear, spent like 6 hours on it last night. Basically it's like
I tried scripting the same process via |
|
So I played some more and even tried to run the update manually. I noticed in your update logs, you have: Mine is definitely not doing that at the end: |
|
Closing as this is not an issue, just opened "Discussions" tab here: https://github.com/ludwig-v/wireless-carplay-dongle-reverse-engineering/discussions |
Repository owner
locked as off-topic and limited conversation to collaborators
Mar 14, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Carlinkit and CPLAY2Air come in a few varieties, ie one for "factory" head units, and one for "android based" head units. If the firmware is identical between these, how does it know the difference?
I've been trying to get my "factory" CPLAY2Air working with an android tablet after seeing this video.
The startup process uses
init.dandrcSwhich launchesstart_main_service.sh. This script looks for/usr/sbin/fakeiOSDeviceand if there launches it. If it's not there, it then tries/usr/sbin/fakeCarLifeDeviceand if there launches it. If it's not there, it then tries/usr/sbin/ARMadb-driver. I could be wrong, but I thinkARMadb-driveris the app that connects to android head units and tablets.To test, I removed
/usr/sbin/fakeiOSDevice, restarted, andARMadb-driverfinds my phone, but can never connect to the AppServer running on the tablet:ARMadb-driveroccasionally tries to runstart_accessory.sh:My device does not seem to have
/sys/class/android_usb_accessorybut rather/sys/class/android_usb.I'm not a linux wizard, but stack exchange says:
The directory /sys/class is exported by the kernel at run time, exposing the hierarchy of the hardware through sysfsI wonder if
upglooks atuuidand configures the kernel differently during an upgrade.The text was updated successfully, but these errors were encountered: