[Android Head-Units] sylcat:
Just gotta say I urgently wave anyone off of this project as it is.

Most importantly this line of tablets sucks. The screen sucks, the specs suck, the performance sucks, it's max 2g crap that'll still suck after it's hacked, the screen glare is laughable/day-unusable, it crashes, stops responding to physical buttons randomly, and it has no amp which will throw unsuspecting people. The audio it does provide is a total diarrhea blast through a cheap rca canbus adapter with ground interference for miles so again, you better have a rated amp and isolater for your speakers and know audio wiring. Also hey the software is clearly disingenuous chinese spycrap that would probably try to kindnap your child if it could, to the point that I don't know if I'd even trust root hunting to find all the lies.

Past that I can't endorse this tutorial either I'm afraid. Look at the failure/success ratio in this thread already and add mine to the failure pile.

Modders are going to get into this and dl a folder sequence that looks step by step for each but then opens up into different subinstructions requiring knowledge bases you didn't know you needed until you're in it. You're gonna be messing with device manager and secure boot modes in windows and custom power wiring outside the car just to get going. To deal with that you're going to go down more forum nightmares mid way, stuff that should all be on a unified 1,2,3,4 instruction set in the main post imo. I'm capable and I'd call this written procedure luring unsuspecting people into bad times.

I had to bail on this project some weeks ago after that "boot into secure mode in windows to install temporary unsigned USB drivers (which can revert and fail while you're working on the project with so much as a windows update) just to get it to communicate" process. Then of course it never did communicate, step by step trying across 3 devices in specifiied acc wiring positions and every other attempt under the sun. This is of course after you've and soldered up this failure of a unit to a power source to hack it outside the car which is ridiculous to need to do in itself, and a dozen more things most people wouldn't sign up for if it were made a bit more clear.

I'd be willing factory reboot and get that guy from the android 8 thread the clean yt9216bj image except I don't want to waste day 4 screwing with the non working ass-up usb/windows head unit software.

The product itself is obviously not worth it and...rant but yeah this tutorial suffers from the super common XDA problem where the author is super tech skilled!...but just too in their own head to relate 1:1 what regular people need to know as if visitors were working along side them all year. I respect all the work that went in but imo this as presented seems to be tanking people's efforts and stress them out. It'd be more worth it to risk the brick if this were a hack that you shove in the usb and it goes. It's very not that.

At the time of writing I suggest saving yourself xda therapy costs, spend on a cruthfield screen that actually works, is nice, you can see in the daytime, you can mod into an enclosure yourself, and will probably have a way easier hack with much better function before and very much after a hack. I'm probably going to shove an m80 into this aptly named BJ unit and explode it like the chinese firework trash it is.