Is bare metal linux possible on XTRONS? - Android Head-Units

Quick question before i purchase one...
So i am a bit of a fiddler, and enjoy writing software, So im wondering, would it be possible to completely wipe android off a XTRONS head unit, and replace it with a custom linux distribution?
For those who are wondering why? - I have complete control over my car's canbus network after reverse engineering the entire interior CAN system, so i would like to write custom UI apps on a Linux device that lets me control various aspects of the car. A pi has worked as a prototype, but does not look pretty at all in the car. If i could somehow replace it with an android head unit, it would be fantastic!
Any help appretiated.

UKSFM99 said:
So i am a bit of a fiddler, and enjoy writing software, So im wondering, would it be possible to completely wipe android off a XTRONS head unit, and replace it with a custom linux distribution?
For those who are wondering why? - I have complete control over my car's canbus network after reverse engineering the entire interior CAN system, so i would like to write custom UI apps on a Linux device that lets me control various aspects of the car. A pi has worked as a prototype, but does not look pretty at all in the car. If i could somehow replace it with an android head unit, it would be fantastic!
Click to expand...
Click to collapse
You need to do a lot of reverse engineering. Possibly much more then you want to. Note that it is not a phone. There is a lot of hardware around it that is controlled via the MCU. All brand units still use all kind of broadcasts / events/ services etcetera to get info and controls back and forth, so closed source, instead of Android automotive. Your CAN bus is only one detail.
There have been multiple projects like this, including projects where they combined several "linux compliant" hardware parts to build a unit from scratch. As far as I know none is successful.

Well, I bought a head unit last night. Exact model is IN89M209PL.
I do have a fair amount of reverse engineering knowledge, so first stage would be to do a ton of data tracing on a rooted ROM, for basic things like touch screen and brightness / LED controls. Once I have that, in theory the hardest part would be getting it to boot Linux. (Writing device drivers is fairly easy once I can understand the protocol).
I shall keep this post updated as I find new things though, obviously if the whole Linux idea is a total flop, I suppose the next best thing is a bare bones custom android ROM, where only the apps I need are installed and use a custom build launcher to serve as a dashboard UI for the car.

I made some progress!
So turns out the unit is rk3326 based, and after gaining root via adb, I was able to browse all the partitions on the device.
It looks like it's using uboot to boot android, using custom kernel command line args to boot the kernel, the bootloader appears to be default (like what you get on the rock64).
The only step now would be to get uboot to boot off the sdcard rather than emmc storage, then I can get full Linux!
Regarding proprietary hardware, the canbus communication is done using a serial device (ttyV0) which relays can frames directly to the headunits OS,
Screen and touch controls seem to be using default Linux kernel drivers, so no modifications will be needed driver wise!

Watching this with interest, good luck!

Well currently the issue is in uploading the firmware via maskrom. It appears the unit will disconnect mid way through flashing. I've tried about 10 times and it keeps cutting off anywhere from 40% to 70% complete

UKSFM99 said:
Well currently the issue is in uploading the firmware via maskrom. It appears the unit will disconnect mid way through flashing. I've tried about 10 times and it keeps cutting off anywhere from 40% to 70% complete
Click to expand...
Click to collapse
After this disconnected flash: is it still working or bricked?
And after how many minutes? And always after the same time?
Some units have a watchdog in the MCU that checks for "illegal" operations on the unit.
You are one of the first on this car unit forum that knows how to flash via the mask Rom (and I'm not one of those users although I do know what it is and why and for what reason it is used.).

surfer63 said:
After this disconnected flash: is it still working or bricked?
And after how many minutes? And always after the same time?
Some units have a watchdog in the MCU that checks for "illegal" operations on the unit.
You are one of the first on this car unit forum that knows how to flash via the mask Rom (and I'm not one of those users although I do know what it is and why and for what reason it is used.).
Click to expand...
Click to collapse
@surfer63, this is no new way to get a bricked RK back to life.
I use RK-Batchtool since years now and could get a completely bricked PX5 back again with flashing in MASKROM.
By the way @UKSFM99, there is a nice thread here https://forum.xda-developers.com/an...px3-5-headunit-mod-recover-flash-som-t3766892 wich should be helpful.
I think it would be a good idea to get the SOC off from the board to get this working.

rigattoni said:
@surfer63, this is no new way to get a bricked RK back to life.
I use RK-Batchtool since years now and could get a completely bricked PX5 back again with flashing in MASKROM.
By the way @UKSFM99, there is a nice thread here https://forum.xda-developers.com/an...px3-5-headunit-mod-recover-flash-som-t3766892 wich should be helpful.
I think it would be a good idea to get the SOC off from the board to get this working.
Click to expand...
Click to collapse
I've tried that and doesn't work.
It's a random amount of time (between 1 and 2 minutes) before it randomly resets.
After leaving it in my desk all day I've noticed it seems to be rebooting even if it's just plugged in in maskrom mode! I don't even have to flash it for it to reboot back into maskrom

UKSFM99 said:
I've tried that and doesn't work.
It's a random amount of time (between 1 and 2 minutes) before it randomly resets.
After leaving it in my desk all day I've noticed it seems to be rebooting even if it's just plugged in in maskrom mode! I don't even have to flash it for it to reboot back into maskrom
Click to expand...
Click to collapse
I remember about someone who ran into the same issue and had to unsolder 2 Pins from a chip.
I don´t know where and what, because I never ran into this issue in the past. May be @marchnz remembers and can link you to the right point.

rigattoni said:
I remember about someone who ran into the same issue and had to unsolder 2 Pins from a chip.
I don´t know where and what, because I never ran into this issue in the past. May be @marchnz remembers and can link you to the right point.
Click to expand...
Click to collapse
That would be really useful is @marchnz remembers...
However I managed to flash a custom kernel at least. Got kernel 4.4 working for Ubuntu

Awesome work! Which DE are you planning on running with it?

UKSFM99 said:
That would be really useful is @marchnz remembers...
However I managed to flash a custom kernel at least. Got kernel 4.4 working for Ubuntu
Click to expand...
Click to collapse
As posted elsewhere (crossposts...) use a jig, not the mainboard. The MCU will cut power to the SOM and risk mainboard/SOM damage.
Ive written about this extensively in my OTG/Recovery posts, with documented steps and images, use that.

jrobbom5 said:
Awesome work! Which DE are you planning on running with it?
Click to expand...
Click to collapse
It's a strange one. This sits in my W203 mercedes and I'm part of a group who enjoy hacking those cars.
Tldr; it's gonna be running a ported version of MBUX interface so it'll look like a stock mercedes infotainment system.
Hardest part will be writing the interface code to hijack calls MBUX components are making to hardware and converting them for my headunit and car

Related

US-JY-UL135N2 crashing and won’t recover for hours.

Hi all
the text below is an email exchange between me and joying support. Besides the obvious language barrier I also don't think they are willing or able to do much troubleshooting. I was wondering if anyone here would be kind enough to point me to the right direction.
The problem basically has started after two or three unsuccessful root attempts that most likely left some script that I cannot erase with a factory reset. It could also be one of those very unlucky coincidences where the problem appeared then but rooting was not the cause.
It looks like the unit powers up normally after a period of complete inactivity that has to last at least a few hours and then everything is normal for about one hour. Then it shuts itself off again but will not restart for a few hrs. i didn't get a chance to troubleshoot further and provide detailed timing but I don't think its a heat issue as described elsewhere
After I rooted it successfully I installed the "joying extra tools" but was not really able to use the app.
any help would be appreciated
thanks
Hi I just installed my US-JY-UL135N2 a few weeks ago. It was working fine for a few days but had the same problems described in various posts.
I tried to install superSU in order to install a complete backup application (titanium backup) following the directions from this forum (cant post link yet) first couple of times I was unsuccessful (could not get permission to write the files). After that it started rebooting at random times and sometimes it wont wake up for a few hrs. A couples of days later I rebooted the unit and tried again to root and this it worked. The crashes did not stop so I did a factory reset from the settings menu. When that was completed I looked at the applications and superSU was still there and the crashes continue. I think that maybe some incomplete files have remained when I tried to root the first time. What else can I do? If I did a factory reset shouldn’t it wipe everything? Also should I upgrade from 5.1.1 to 6.0? how? Will that solve the problem?
Do you have support in the USA? Can I talk to someone here?
Dear friend,
Thanks for your email .
Do you mean that the head unit will be crashed after you download the backup application ?
we think that maybe the application is not much more compatible with our head unit .
could you try to directly unload the SuperSu app ? and then check whether it will still crashed ?
and could you show a video to us how it crash ? so that we can know more ?
Hope your positive reply and then we will help you .
Thanks
candy
Thanks
Candy
No I never got a chance to install the application. The unit is now dead it does not start at all so there is noting to show. Is there is a way to make it start? If there is I can uninstall the superSu and let you know if it helped but for now I can't do anything
Dear friend,
Thanks for your reply .
please noted :
You said that you have not installed the application , so how your head unit go dead ? we are a little confusing .
could you please explain what you have done before then the head unit go dead ?
because you also said the Supersu is there , if you have not installed it successfully , bow it will be there .
we hope your kindly reply then we can know that how to help you .
I Said I did not install the backup application (titanium backup) but i did install superSu.
I tried to root the unit but failed a couple of times. The third time I rooted it but then It started random crashes and reboots so I didn't get the chance to install anything else. Can you just tell me if there is a way to restart it or do I have to send it back for warranty repair?
hope you can have a try and feedback us .
Candy
Add joy to your car with Joying !
Because sometimes root also will make mess the head unit .
you can try to update the head unit and then check whether it will solve your problems .
here is the update link : sorry cant post links yet
please try to update (2017-7-7 )
please check whether it can update successfully .
Sent: Wednesday, August 09, 2017 7:03 AM
Subject: Re: US-JY-UL135N2 crashing and wont recover for hours.
Dear friend,
Thanks for your reply .
Sent: Wednesday, August 09, 2017 7:23 AM
To: 'Joying support'
Subject: RE: US-JY-UL135N2 crashing and wont recover for hours.
Hi
The unit came back on today by itself after about 15 hours. I uninstalled superSU and reset it again. I don’t know if its going to be stable this time but I will let you know in a few hours
The update you’re suggesting is 6.01 and I read that there is problems with it. Isn’t it better to stay with 5.1.1?
Where can I find the latest file for 5.1.1?
From: Joying support
----
Date: 8/9/17 11:38 PM (GMT-05:00)
Subject: Re: US-JY-UL135N2 crashing and won’t recover for hours.
Dear friend,
so we suggest that you go to update the system to android 6.0 .
because it will enter the recovery interface . please check whether it can .
Hope your try .
Thanks
Candy
Ok so I left the car off for a few hours and just tried it again. I turned the car on and the unit DID NOT TURN ON AGAIN. It just wakes up whenever it feels like it.
I can’t do anything to it until it turns on again. I there a way to reset it completely?
here is the blog on how to update the android 6.0 : sorry cant post links yet
(please update to 2017-7-7 )
you update the head unit according to the blog , then it will occurred the recovery interface .
Hope you can try .
Thanks
Candy
How do I make it enter recovery?
-------- Original message --------
Ok I just I did the update 2 hrs ago. Then I drove for about 40 minutes and shut off the car. Went back 20 minutes later and tried it and it turned on without problem. I just tried it again now and it won’t turn on. I don’t know what else to do at this point. Is there a way to get logs when it turns back on? It usually turns back on after 6-7 hours
From: Joying support
Sent: Thursday, August 10, 2017 6:25 AM
To: Spiro S
Subject: Re: US-JY-UL135N2 crashing and won’t recover for hours.
Dear friend,
additional observations/thoughts
I just noticed something else. When I start the car in the morning to go to work the headunit is always on immediately. Does this mean that it stays on after it restarts itself at some point at night ? or does it boot up that fast? (less than a second)? I dont remember ......if this is a heat issue and it started at the same time as when I was trying to root it wouldn't that issue kind of go away when I installed 6.0.1? its supposed to have better cpu management right?
idlt said:
Ok I just I did the update 2 hrs ago. Then I drove for about 40 minutes and shut off the car. Went back 20 minutes later and tried it and it turned on without problem. I just tried it again now and it won’t turn on. I don’t know what else to do at this point. Is there a way to get logs when it turns back on? It usually turns back on after 6-7 hours
Click to expand...
Click to collapse
In my opinion it's the heat that's causing the problems combined with with the fact that maybe some of the electronics gave out. It returns back to life when it's cool enough.
Either way make a video demonstrating the issue, complain and demand a new unit under warranty.
In the meantime you can install an app that can monitor the CPU temperatures
Like :
1. https://play.google.com/store/apps/details?id=info.kfsoft.android.MemoryIndicator
2. https://play.google.com/store/apps/details?id=com.yanyan.cputemp
That can display the temperature at all times no matter the app that you are in
Use this app to test the stability and temperature under heavy CPU load : https://play.google.com/store/apps/details?id=com.into.stability
Check the temperature it reaches before blacking out.... it could be the CPU giving out on high temps or maybe something else... just a thought...
Thank you for your reply I will try to work around its schedule and do that. I just went and disconnected the power completely so it stays cool until I'm able to work on your suggestion. Hopefully after work it will start up normally and I can sit there for an hr looking at the temperatures (not happy bout that for a brand new unit) .
the funny thing is that it gives out when the car is off so the unit should be on sleep. How can the temps go up high enough to shut it off when its not even doing anything? The dormancy setting is on so I was assuming it went to sleep.
here is the reply i got from joying below. Basically suggesting to do what I have already done to it
Also some people suggesting sending them a video but a video of what? when its on its running ok when its off its off for hrs and when it comes back its normal again.....it would be a veeeery boring video
Dear friend,
Thanks for your well-cooperated with us together .
please noted :
1) we think that the files on the head unit maybe mess after your root the head unit .
2) So now the head unit can not turn on again , and it may turn back on after 6-7 hours ?
3) if yes , please try to do following processes and check whether will be workable for your problems :
1. Download the update file from window syetem computer, then upzip it and copy the files into
SD card without any folder. Then please insert the SD card into GPS maps card slot.
The files also will be the same updated file :
2. Put ACC wire(red one) and BATT wire(yellow one) together, then connect it to positive power supply 12V;
Put GND wire(black one) to GND.
3. Turn on the head unit,it stuck on JOYING logo, please click "reset"( first time).
4. After the first time reset, the item will restart and it stuck on JOYING logo, please click" reset"(second time)
5. After the second time reset, the item will reboot and it stuck on JOYING logo, please click " reset"(third time)
6. After the third time reset, please don't power off the head unit and wait for a while to update the head unit.
Then watch this video to learn how to update the system: xxxxxxxxxxx
Please check whether it can appear the "Joying logo " and go on the processes we suggested .
Thanks for your time
Candy
Add joy to your car with Joying !
Please have a try . and then feedback us how it going on ?
Thanks
Candy
Oh man... you made a big error telling them that you rooted the unit... rooting had nothing to do with the behavior at hand but it's enough to give them something to talk about and delaying to delivering a new unit.
What you should have done before telling them you have a warranty problem.
1. Start the default Joying File Manager go to the internal storage, select all, delete
2. Take out all the SD card and USB sticks and DON'T put them back
3. Reset the unit to defaults, that does not remove root but removes all the apps and settings
4. if the unit is still unstable and it seems related to heat... wait till it cools down
5. prepare a stick with the firmware that you have already on the unit for a reflash
6. flash the unit - now the root is gone - everything is back the way it was when you bought the unit
7. test for stability... if you still have issues that means it's not software it's hardware.... warranty time.
Thanks a lot man!
You have no idea how many times I searched for a way to restore back and wipe all data because I could still see the garbage in there even after a factory reset but couldn't find out how to.
I will follow your steps and then call it a day because it would have to be a heat issue at that point
I ts funny though that it didn't show up prior to root.
On the rooting issue now. I thought they provide a link on "how to root" on their blog....I didn't think I was doing something wrong by just rooting it. I didn't really get a chance to use the root access anyway! You would think they would provide a way to do a full back up in case something went wrong this way we didn't have to resort to rooting
thanks again. I will update the post when I have news
BTW does anyone know what temp the CPU should be running at? or whats the max before it shuts down?
idlt said:
BTW does anyone know what temp the CPU should be running at? or whats the max before it shuts down?
Click to expand...
Click to collapse
Search!
The past weeks have been full of this in 2 threads: the upgrade thrad and the heatsink thread.
And edit, who also answered you in this post, added even more on this in his Q&A thread, which you obviously also missed.
Update .....and some thoughts
@ surfer63. Point taken....I realize I was been lazy. Please accept my sincere apology for taking all the work you guys do for granted.
I don't have much to contribute but here is an update on my issue and also some thoughts on what to do in order to be able to enjoy the best of both worlds _Reliability and function_ in a car radio experience.
BTW. I ripped out my very expensive but very restrictive factory rocford fosgate navigation/camera/Bluetooth/overhead console/back up sensor/ infrared headphone ..blah, blah, blah system in order to install this one, so I had high hopes that I could get this to at least function somewhat reliably but I've been driving for two weeks without a radio or Bluetooth for my phone.
anyway...
Joying USA finally came through with a solution. They offered to send me a 6021 to replace my most likely burned out 5009 unit _new one is on the way_
I had to pay shipping and I was charged $300.00 for the unit but I will be refunded $200.00 when I send the other one back. I'm happy that at least I will have a radio again and have learned my lesson about how real a Chinese warranty is. I hope I wont have any problems getting my $200.00 refund ( I have only used the old radio for about 2 weeks before it burned out)
I chose to "upgrade" to the 6021 _ It would be the same cost for either unit _ because I was told it is more stable after the re-design of the main board and the LCD board. I'm hoping that the overheating issue will be less of a problem with this one although I read reports to the contrary....
I also took surfer63's advise and read up a little and I now know that there is no way to rely on a Chinese android unit to replace a factory head-unit or even a brand name one for that matter because the stability is not there yet (my opinion). We should probably be thankful though that at least Joying and others are not afraid to try and provide this alternative.
I also read up on all the newest high end brand name head-units and nothing has changed since last time I looked. They are all crippled, restrictive and proprietary for the most part when it comes to peripherals. They offer really good sound quality but the ones with the most features also suffer from software and hardware glitches though less frequent than the Chinese ones. The Chinese android units do offer a glimpse into the future but my experience is that they are not at all reliable or fully functional. I believe that in a car environment the most important functions are ease of use, radio reception and phone/Bluetooth quality and reliability (terrestrial radio is still more reliable than internet radio for people that want to listen to the news or traffic updates or local events and such...) . Once that's covered then I guess sound quality, internet connectivity for online content, online navigation and voice commands as well as other similar features become important.
I don't think there is one single head-unit out there that covers all that but maybe not all hope is lost.
My solution is to purchase a single din head-unit with a reliable radio, good sound quality, stellar quality hands-free phone Bluetooth function and maybe USB phone connectivity. I have a spare space in my console so I will install that in there and install the Joying unit _or the next android experiment_on the double din space above. If space is not available on the console one could probably hide it in the glove-box or under the dash.
when the Joying dies again _notice I wrote "when" not if... I can revert back to the simple one until I replace it with the next upgrade or maybe with a tablet. They now make some nice built in mounts for them https://soundmanca.com/
I haven't had time to research the single din unit yet but it most likely will be one of the major brands. maybe this one https://www.amazon.com/Pioneer-DEH-...ud-20&linkId=644693c89a21ea33f675e3023ce5cc4b
I will try to figure out a way to make them both work through the same amplifier and be able to use the hands free function on the single din one, navigation and backup camera on the android and have the choice to play music from either one. I'm not sure how to do that yet but looking into it now. Maybe I can use the Aux input or another "source" input on the single din one which could also be wired to the factory steering wheel controls so that when I answer the phone the AUX switches off and the hands free takes over. I think when the phone call ends it would have to switch back to AUX . I will try to update this post when I figure this out and in the mean time I welcome any thoughts or suggestions
Thank you all for your support

Bricked Atoto A6, Need some help.

Have not done much with rooting android devices in years and recently bought an Atoto A6 for a work van. I started messing around with it at home. Was able to gain root with Kingoroot and the replacing it with SuperSU. I emailed them about unlocking the bootloader but I'm not sure whoever responded even knew what I was talking about. Although ADB was working with system booted, I was not able to connect to the unit in fastboot. If you boot into recovery, it automatically runs an update and reboots. And if you boot into Fastboot with acc powered, fastboot automatically restarts. So using adb to reboot into bootloader and then removing power from acc would get me to a fastboot screen(although screen is off, putting power back to acc would show screen at fastboot mode) but I was never able to connect. I was trying different things to boot into an actual recovery, the A6 has no physical buttons, just a small hole for the reset. At some point it completely stopped responding. None of the sensor buttons light up and nothing on the screen. The micro sd I had in no longer works either. I did have update.zip backed up. Anyone know if there would be a way to use that to boot from a new micro sd or any other ideas to try, any help is appreciated.
The a6 has a mediatek mt8127. Was coming up as Alps A6. The build was alps/full_A6_series/A6_series:6.0/MRA58K/1506516231:user/test-keys . I did have it apart and have pics of the board, don't know if they would be useful though.
Upon further review, board mounted reset button was screwed up, all good now. Would be nice to figure out the bootloader on this, although I don't have it installed in a vehicle, this unit seems to run pretty well. Not a fan of the the launcher setup and appearance .
stabone00 said:
Upon further review, board mounted reset button was screwed up, all good now. Would be nice to figure out the bootloader on this, although I don't have it installed in a vehicle, this unit seems to run pretty well. Not a fan of the the launcher setup and appearance .
Click to expand...
Click to collapse
Glad you "unbricked" it, and glad somebody is willing to risk rooting it. That might go on my weekend project list, would appreciate more details on Kingroot and how you swapped it with SSU. I miss ad blockers, among other things.
I got the same unit from Amazon last week (2gb touch only version), but wish I had opted for the physical button model now.
My biggest complaint is the damned FM radio app, which by default comes on when it comes out of sleep, and there's no obvious way to disable it. The volume level on FM is like 2x streaming/MP3 volume so it blasts you when starting the car if you forget to turn volume way down when you get out. I'd love to know the actual app name so I could disable it entirely, since I never listen to broadcast radio anyway.
Oh, and the parallax on the thing is annoying, getting a finger lined up on small touch targets takes some practice.
Other than that issue, I'm not unhappy with the unit. 2-second boot is legit, and living in Florida and an open sunroof junkie, I'm especially pleased with the screen brightness.
Using CarWebGuru instead of the default Atoto launcher makes for a much better experience, and I like the fact that the Atoto controls on the bottom (home, back, multi-tasking, brightness, mute) all remain there no matter what launcher you choose.
Sound quality using my car's factory amp (via a Metra CANBUS harness) is surprisingly good too, I can't tell much difference between the A6 and the Pioneer FH-X730 it replaced at the volume levels I like, though there is some RF bleed from the SoC. And it's a near-perfect fit in a Schoshe double-din GM dash kit, there's not enough room for a toothpick around the edges of the screen and the dash kit inner bezel.
For rooting use KingOroot. You need the one for windows, the app on the unit itself won't do it. Then just google replacing kingoroot with Supersu, there are lots of threads about it. You could try the simple version but I ended up manually replacing files to do it, it's not bad at all. I wouldn't be to worried about bricking it, I have been trying all different things to get to a bootloader and at worst it re-updated and was working fine. What i did with the reset button, Ive done to othere devices, those surface mount buttons are junk. After doing a ridiculous amount of research, I found that MTK units don't enable fastboot. The preloader is what you have to get into to do anything, using mtk drivers. I could catch it right when its booting, installs the mtk vcomm drivers, but jumps right out. Once you are in that you need their flash tool, SDflash and there is MTKtools. So once thats figured out, i'm hoping to be able to get a custom recovery on. Without fastboot, it seems a bit more tricky, without that reset button I could be missing something simple. Hopefully more people start screwing with these, I doubt the people at Atoto are going to be of much help. So far tho, it seems like a decent unit. Let us know if you find out anything.
So far I was able to extract the boot and recovery img files. You can connect to the preloader using SP Flash by setting it up to read
Ima let you do the heavy lifting on this one Stabone.
For now, I'm just frustrated on the damn FM app opening at startup and it's nested in the Atoto firmware somewhere, not an isolated app.
One other quirk, on my car (with GM 11bit CANBUS), the illumination signal seems to be flipped from what Atoto is expecting...lights on means brighter screen, lights off means dim. I've tried it with both an Axxess and PAC CANBUS adaptor, so it's not the harness' fault. Just using the NONE setting for now and manually dimming the screen myself.
I sure hope stabone00 keeps working on this. I have been following this thread closely. I have been wanting to root this but I have it installed in the car now. why cant this be easy like a nexus 7. I am very afraid of bricking it and I really like the head unit
Not sure what happened to my last post, it should've been a bit longer then that, hah, oh well. Anyway I'm a little stuck here. After finding out as much as I did, I was going to try a few things. I'm running a dual boot laptop with opensuse as my main and a windows 10, for occasions as such, the tools used for this head unit are more abundant for windows(at least found easier). So recently I wiped my systems and now am having this Rsa Key Fingerprint issue when trying to connect with adb. I'm spending way to0 much time on this as it is, lol. But running into this bs is really pain. Now I've tried for hours to do something here but it's almost as someone's watching what i'm doing and countering my moves. Now I've factory reset this thing about four times and never lost root. After struggling with this rsa fingerprint issue, I did a factory reset and now SuperSu is gone, although I can't say for sure totally cause I still have not access to ADB. Any suggestions for the rsa issue, let me know, otherwise I'm not going to be wasting much more time with this. BTW, anyone getting anywhere with this, you need the modified version of MTK android tools to recognize this unit. I have boot and recovery img's and a scatter file if needed.
Got passed issue with adbkeys. Now I accidentally flashed a recovery when it was not ready. I am now stuck in a boot loop. Made lots of backups, but for some reason, none contain the preloader.bin. Not sure why that happened, but that is needed to flash backups with SP tools. If anyone could send me that, it would be great. I can't pull it cause I can't get it to connect to mtk droid tools. Maybe there is another way, but I don't know it.
stabone00 said:
Got passed issue with adbkeys. Now I accidentally flashed a recovery when it was not ready. I am now stuck in a boot loop. Made lots of backups, but for some reason, none contain the preloader.bin. Not sure why that happened, but that is needed to flash backups with SP tools. If anyone could send me that, it would be great. I can't pull it cause I can't get it to connect to mtk droid tools. Maybe there is another way, but I don't know it.
Click to expand...
Click to collapse
I have the same unit. If you can tell me how to pull it, I'd be happy to help.
smithkt said:
I have the same unit. If you can tell me how to pull it, I'd be happy to help.
Click to expand...
Click to collapse
Have you tried anything with it yet? There's quite a bit to it. The info is all searchable on here, you are looking for mediatek devices, sp flash tool, mtk droid tools. Let me know if you have adb and drivers installed. All the info needed for this unit is available , but there is a lot of info on mediatek devices, so it's a lot to look at. You need to have developers options enabled and oem unlocked and usb debugging on . If you can connect to your unit through adb, thats a start. Don't attempt anything with fastboot, it's not enabled on this unit. You'll then want to look for the modified version of mtk droid tools 2.5.3. If you are able to connect with that, I'll tell you what to do next. Not so sure my unit is recoverable, i've lost the startup atoto screen and can no longer connect with sp flasher. Hopefully there is something that can be done.
stabone00 said:
Have you tried anything with it yet? There's quite a bit to it. The info is all searchable on here, you are looking for mediatek devices, sp flash tool, mtk droid tools. Let me know if you have adb and drivers installed. All the info needed for this unit is available , but there is a lot of info on mediatek devices, so it's a lot to look at. You need to have developers options enabled and oem unlocked and usb debugging on . If you can connect to your unit through adb, thats a start. Don't attempt anything with fastboot, it's not enabled on this unit. You'll then want to look for the modified version of mtk droid tools 2.5.3. If you are able to connect with that, I'll tell you what to do next. Not so sure my unit is recoverable, i've lost the startup atoto screen and can no longer connect with sp flasher. Hopefully there is something that can be done.
Click to expand...
Click to collapse
No I haven't done anything with it yet. I wasn't planning on rooting the device. The only reason it's not in my car already is it's been 10-20 F and I don't have a garage. I have the thing sitting on my kitchen table so I can play with it.
I'll look through the info and see what I can do.
smithkt said:
No I haven't done anything with it yet. I wasn't planning on rooting the device. The only reason it's not in my car already is it's been 10-20 F and I don't have a garage. I have the thing sitting on my kitchen table so I can play with it.
I'll look through the info and see what I can do.
Click to expand...
Click to collapse
I have it hooked up with two switches, one feeds constant and other switch, and other switch feeds acc. Rooting it isn't too bad, but if you look into how the sp flasher is used, you could make a stock rom before doing it. I'm hoping there are test points on the board that can be used to get this flashed again. I'm not sure how it got this far gone. I had it bootlooping at the ATOTO startup, tried to flash the original boot and recover, seems like it wiped the preloader.
Have you had luck in unbricking your atoto?
I'm thinking about buying one also buy would like to root with kingroot and put a recovery into stereo if it's possible. Let me know your success is possible.
Thanks
Steven
scoolro said:
Have you had luck in unbricking your atoto?
I'm thinking about buying one also buy would like to root with kingroot and put a recovery into stereo if it's possible. Let me know your success is possible.
Thanks
Steven
Click to expand...
Click to collapse
So far it seems to be a very solid unit. Rooting it isn't an issue. I had been trying different things with this unit and at one point I thought it was almost unbrickable. It still might be, just haven't found a solution for my issue (which was completely my fault), although I'm pretty confident there is one. There is a lot of info about mediatek devices on here, a bit different approach when flashing a custom recovery.
Overall I was liking the unit, hadn't seen any issues some of the others had. Hope to see more people getting involved.
I hope you get the unit working soon.
I'm thinking about getting the same unit and I want to root it so I can get ADAWARE and XPOSED app installed. I'm also thinking about getting a Bluetooth media steering control for it also.
I've only seen the Atoto A6 on Amazon.ca for about $280. Hopefully there is another site that sells cheaper.
Again good luck and keep us informed with your progress if possible.
Steven
Atoto offered a to replace the unit with the PB model, as this one is no longer available. After doing as much research as I did, I am certain that this can be fixed. There should either be a way for force the preloader or get into a meta mode/ flashing mode. I'm going to keep it and see. I'm ordering the PB as soon as it is available again on Amazon.
So driving home from work today, I noticed an update pending for the A6. Was in a good coverage area (using a MiFi hotspot, btw, not my phone), downloaded it at a long stop light, hit install, and after reboot, I got the dead Android ERROR! graphic. About **** myself, thought I might have bricked it. At the next red light, I did a reset (I keep a slim toothpick in the console now, for just such emergencies) and I'm back to the old November build.
I ended up sending my 62721p back and am waiting for the pb model.
Did you have it rooted?
stabone00 said:
I ended up sending my 62721p back and am waiting for the pb model.
Did you have it rooted?
Click to expand...
Click to collapse
Nope, couldn't be assed, it's basically a Poweramp/Waze/Spotify machine for me now, figured I don't need root for that, and all the cool root-level stuff the Rockchip and Sofia units get isn't available for this thing anyway.
Did get the update to stick the second time around, but noticed no changes in functionality. MCU got updated as well.

Freezing and restarting Android head unit

Hello everybody! I need your help.. My android unit sometimes works just fine, but it started to act really strange.. When the music is playing, it freezes like buzzing sound, and then restarts.. Sometimes its just stuck on bootloop.. Any opinions what can i do? I asked the seller for update firmware, I updated it, but same thing keeps doing.. Factory reset from settings wont help.. Please, any opinions?
Head unit is from "Wondefoo" seller on Aliexpress.
Model : 8227L
Android version : 8.1.0
Kernel version 3.18.79 (gcc version 6.3.1 20170404 (Linaro GCC 6.3-2017.05) )
Build number : alps-mp-o1.mp5
Custom build version : alps-mp-o1.mp5
Bump
bumbazs said:
Hello everybody! I need your help.. My android unit sometimes works just fine, but it started to act really strange.. When the music is playing, it freezes like buzzing sound, and then restarts.. Sometimes its just stuck on bootloop.. Any opinions what can i do? I asked the seller for update firmware, I updated it, but same thing keeps doing.. Factory reset from settings wont help.. Please, any opinions?
Head unit is from "Wondefoo" seller on Aliexpress.
Model : 8227L
Android version : 8.1.0
Kernel version 3.18.79 (gcc version 6.3.1 20170404 (Linaro GCC 6.3-2017.05) )
Build number : alps-mp-o1.mp5
Custom build version : alps-mp-o1.mp5
Click to expand...
Click to collapse
Bump
bumbazs said:
Bump
Click to expand...
Click to collapse
It could be the overheating of cpu, check your temperatures. Have you experienced similar problem before ?
julien_blanche said:
It could be the overheating of cpu, check your temperatures. Have you experienced similar problem before ?
Click to expand...
Click to collapse
Thats what checked first.. The CPU temp at working time is 60 Highest.. i put the radiator and fan on the cpu, nothing.. Tried to heat the radio with air heater fan to 90 celsius, and it working just fine.. its just random reboots.. :/
BUMP!
I still need help to fix this issue.. Anybody..? :/
Quick reminder : Sometimes it work great, i drive and listen to music like for 30-60min and then it freezes! Leading to restart, sometimes its stuck on booting, in the bottom corner its says something about " >>Fastboot mode.. After that i have to reset unit using little button for like 5 times till i can boot to system again.. It freezes and restart faster, when i just navigating in menu, like settings.. The seller told me, that they cant give me android 9.0 flash because its not gonna work on my unit.. Next thing they said, that there is possibility im getting these freezes because i dont have CAN BUS decoder, but i dont believe them, because i got other android units which works fine without this decoder..:crying:
Was A fix found for this?
(
Adrunkmango said:
Was A fix found for this?
Click to expand...
Click to collapse
Still not..
So I'm having a similar problem and I have turned off google sync and it seems to have made it better
Clearing the cache of application and then resseting sometimes corrects the problem
Hi everyone, I bought a used 2014 Nissan Maxima S and the previous owner installed an aftermarket, unknown android radio. Worked fine the first year, but recently after getting an alternator replacement (not sure if that means anything but mentioned in case) my radio is stuck in a freeze & reboot loop. The radio isn’t even picking up signal, nor bluetooth signal. This is an unknown, old android device but attached is the device details. Could anyone help me identify the issue? Maybe even help me identify the device model itself, it would
be greatly appreciated.
qjbthereal2002 said:
Hi everyone, I bought a used 2014 Nissan Maxima S and the previous owner installed an aftermarket, unknown android radio. Worked fine the first year, but recently after getting an alternator replacement (not sure if that means anything but mentioned in case) my radio is stuck in a freeze & reboot loop. The radio isn’t even picking up signal, nor bluetooth signal. This is an unknown, old android device but attached is the device details. Could anyone help me identify the issue? Maybe even help me identify the device model itself, it would
be greatly appreciated.
Click to expand...
Click to collapse
Maybe we're taking about this device:
Eincar Quad Core R16 1.6G Android 5.1
Good Day I would like to start this forum on Eincar Radios. I found the user manual and support poor and would like to contribute my findings and ask for help in areas where I'm stuck. Also based on my experience I find the carjoying support...
forum.xda-developers.com
There is also a link to a firmware in the thread. I wouldn't invest too much time in the old head unit. Try to flash the firmware and if it doesn't work thinking about a newer device.
I think that your battery is to low in Ampers and simply cannot support multimedia device as some Chinese multimedia devices uses more that 20A when connected to battery and if not charged by alternator. Alternator must charge/recharge battery and it is not culprit for this situation, I would first check battery (like if it empty and not charging and if it has at least 64Ah for stable run of multimedia). You can check battery state with multimeter device.
Second, most probably, you should check wiring connecting from battery and multimedia device - 12V wire and red wire ACC/KEY ignition. If they have voltage either when engine is off -12v constant or with contact/engine running - 12v, then battery is not responsible and it is ok.
Third, all multimedia devices has master reset or factory settings included if booting of device fails. It is triggered with all five fingers pressed on lcd screen, and when message detected or erasing or reseting to factory settings appears. After that procedure multimedia device starts with default options as if would start for the first time (beware : erasing option deletes all settings and files stored on device).
Try with that options first and let us know what happened and if situation is resolved...
Greets...
Anton TNT said:
I think that your battery is to low in Ampers and simply cannot support multimedia device as some Chinese multimedia devices uses more that 20A when connected to battery and if not charged by alternator. Alternator must charge/recharge battery and it is not culprit for this situation, I would first check battery (like if it empty and not charging and if it has at least 64Ah for stable run of multimedia). You can check battery state with multimeter device.
Second, most probably, you should check wiring connecting from battery and multimedia device - 12V wire and red wire ACC/KEY ignition. If they have voltage either when engine is off -12v constant or with contact/engine running - 12v, then battery is not responsible and it is ok.
Third, all multimedia devices has master reset or factory settings included if booting of device fails. It is triggered with all five fingers pressed on lcd screen, and when message detected or erasing or reseting to factory settings appears. After that procedure multimedia device starts with default options as if would start for the first time (beware : erasing option deletes all settings and files stored on device).
Try with that options first and let us know what happened and if situation is resolved...
Greets...
Click to expand...
Click to collapse
What are you talking there?
These units don´t even take 3 Amps!
My PX6 with a 12.8" screen, currently working on my bench at a power supply, takes in the first 2 sec. about 1.7A and calms down to 1.4Amps when the booting process is completed (after ~3-4 sec.)
--------------------------------
The issue here is, that the radio was not complete off, when the battery was disconnected.
Most probably this leaded to a corrupt boot sector and here you are.
@qjbthereal2002 : Sorry to say, but this old unit is not worth to spend time on repairing or searching for a possibility to get it back to life.
Get rid of it and have a look for a new and properly working one. Have a look in this forum https://forum.xda-developers.com/f/fyt-android-head-units.12445/ and you are at home.
rigattoni said:
What are you talking there?
These units don´t even take 3 Amps!
My PX6 with a 12.8" screen, currently working on my bench at a power supply, takes in the first 2 sec. about 1.7A and calms down to 1.4Amps when the booting process is completed (after ~3-4 sec.)
--------------------------------
The issue here is, that the radio was not complete off, when the battery was disconnected.
Most probably this leaded to a corrupt boot sector and here you are.
@qjbthereal2002 : Sorry to say, but this old unit is not worth to spend time on repairing or searching for a possibility to get it back to life.
Get rid of it and have a look for a new and properly working one. Have a look in this forum https://forum.xda-developers.com/f/fyt-android-head-units.12445/ and you are at home.
Click to expand...
Click to collapse
There is a multimeter tool to read amps and voltage from device ... I still think it is matter with ampers and voltage.
Old devices sometimes can at peak take up to 15 Ampers and usually fuse is arround 10A, when device surpases that device reloads or reboots or just shuts down. I've seen one problem with that. Just sharing my experiences...
Maybe it is Rigatonni right I don't know. I would try all available options.
Anton TNT said:
There is a multimeter tool to read amps and voltage from device ... I still think it is matter with ampers and voltage.
Old devices sometimes can at peak take up to 15 Ampers and usually fuse is arround 10A, when device surpases that device reloads or reboots or just shuts down. I've seen one problem with that. Just sharing my experiences...
Maybe it is Rigatonni right I don't know. I would try all available options.
Click to expand...
Click to collapse
15 amps... what? May be if you use an external amplifier, connected to the same fuse, which would be a nogo.
15 Amps... ever heard about Ohm´s law? That would mean this unit would burn around 180Watts in peak... Never ever. I don´t know your multimeter, but to be honest... Don´t trust this device.
At least since 2012 (I am in "this business" since then with working with head units of any kind) I never have seen a single head unit taking more than 5Amps. In this case we are talking about some OEM units. with integrated better amplifiers.
I never have seen any Android head unit taking more than 3Amps in the past 8 years now.
Even if the unit would consume 15 Amps, the fuse would immediately burn and it would not recover as long as you change the fuse.
After burning the fuse it would not even show the boot logo.
No this is no explanation for the behavior of this particular head unit.... never ever.
Fact for some older head units is, that special circumstances as removing the power while booting or shutting down, lead to a bad boot sector. Nothing else. Can be repaired if you have the right tools and the knowledge, but does not make any sense for this old head unit. It has done it´s work for some years now... Rest in peace.
rigattoni said:
15 amps... what? May be if you use an external amplifier, connected to the same fuse, which would be a nogo.
15 Amps... ever heard about Ohm´s law? That would mean this unit would burn around 180Watts in peak... Never ever. I don´t know your multimeter, but to be honest... Don´t trust this device.
At least since 2012 (I am in "this business" since then with working with head units of any kind) I never have seen a single head unit taking more than 5Amps. In this case we are talking about some OEM units. with integrated better amplifiers.
I never have seen any Android head unit taking more than 3Amps in the past 8 years now.
Even if the unit would consume 15 Amps, the fuse would immediately burn and it would not recover as long as you change the fuse.
After burning the fuse it would not even show the boot logo.
No this is no explanation for the behavior of this particular head unit.... never ever.
Fact for some older head units is, that special circumstances as removing the power while booting or shutting down, lead to a bad boot sector. Nothing else. Can be repaired if you have the right tools and the knowledge, but does not make any sense for this old head unit. It has done it´s work for some years now... Rest in peace.
Click to expand...
Click to collapse
This does not read very friendly, but it is true.
bumbazs said:
Hello everybody! I need your help.. My android unit sometimes works just fine, but it started to act really strange.. When the music is playing, it freezes like buzzing sound, and then restarts.. Sometimes its just stuck on bootloop.. Any opinions what can i do? I asked the seller for update firmware, I updated it, but same thing keeps doing.. Factory reset from settings wont help.. Please, any opinions?
Head unit is from "Wondefoo" seller on Aliexpress.
Model : 8227L
Android version : 8.1.0
Kernel version 3.18.79 (gcc version 6.3.1 20170404 (Linaro GCC 6.3-2017.05) )
Build number : alps-mp-o1.mp5
Custom build version : alps-mp-o1.mp5
Click to expand...
Click to collapse
I have the same unit and the same problem!
chormiak said:
I have the same unit and the same problem!
Click to expand...
Click to collapse
You should install Logcat Reader (https://play.google.com/store/apps/details?id=com.dp.logcatapp) and check for errors if an update of the firmware doesn't help.

Seicane H276L -- What type HU is it? ROMs available?

Sorry for the n00b'ness of this post. I tried to post the link directly to the unit, but the forum is preventing me from doing so. If you search for "H276L" on seicane(dot)com, it's the more expensive (8-core) unit.
I'm highly considering buying this unit, but I want to make sure there are ROMs that are being developed for it. I had an MTCB Joying unit in my last car that worked like crap until I found a good ROM for it on here. If this unit's platform isn't being developed on here, I have no interest in buying it. Being a Jeeper, it'd be super handy to have my trail apps (Gaia GPS, AllTrails, etc.) run directly on my head unit, but if I'm going to spend $ on my HU, I'm gonna get one really worth my while.
TIA!
-A
Looking for Roms!
Hello,
I recently did purchase this unit and I have been extremely unhappy with the stock ROM. I am looking now to root the device later today (putting together a tutorial right now. I am still looking for a ROM however. The initial unit seriously has no apps that function fully. Every app force closes or doesn't function as expected. I am extremely technical and can usually fix any issues. I worked with Seicanes (non-existent) support for the last month with no success. They will require you to pay shipping to and return (so basically if you ship it back and want another you are spending a few 100 more). I am going to try and root and install custom ROM instead, if I can find one.
Thanks,
Brady
aklino said:
Sorry for the n00b'ness of this post. I tried to post the link directly to the unit, but the forum is preventing me from doing so. If you search for "H276L" on seicane(dot)com, it's the more expensive (8-core) unit.
I'm highly considering buying this unit, but I want to make sure there are ROMs that are being developed for it. I had an MTCB Joying unit in my last car that worked like crap until I found a good ROM for it on here. If this unit's platform isn't being developed on here, I have no interest in buying it. Being a Jeeper, it'd be super handy to have my trail apps (Gaia GPS, AllTrails, etc.) run directly on my head unit, but if I'm going to spend $ on my HU, I'm gonna get one really worth my while.
TIA!
-A
Click to expand...
Click to collapse
jerkface41606 said:
Hello,
I recently did purchase this unit and I have been extremely unhappy with the stock ROM. I am looking now to root the device later today (putting together a tutorial right now. I am still looking for a ROM however. The initial unit seriously has no apps that function fully. Every app force closes or doesn't function as expected. I am extremely technical and can usually fix any issues. I worked with Seicanes (non-existent) support for the last month with no success. They will require you to pay shipping to and return (so basically if you ship it back and want another you are spending a few 100 more). I am going to try and root and install custom ROM instead, if I can find one.
Thanks,
Brady
Click to expand...
Click to collapse
Thanks Brady,
Please keep me posted. I pulled the trigger on this guy 2 days ago -- waiting for it to ship. I had an Eonon unit in my Cadillac, and it was the same story. Support is useless, stock ROM is crap, but with the right ROM, it becomes awesome.
-A
aklino said:
Thanks Brady,
Please keep me posted. I pulled the trigger on this guy 2 days ago -- waiting for it to ship. I had an Eonon unit in my Cadillac, and it was the same story. Support is useless, stock ROM is crap, but with the right ROM, it becomes awesome.
-A
Click to expand...
Click to collapse
Hello,
After many trial and error attempts I was able to finally find an extremely amazing OS! Malaysk is the way to go once you get your Seciane Unit. Everything works fully and is extremely easy to use. The installation was really easy honestly and it didn't take long to get it to work correctly. If you go to: https://forum.xda-developers.com/member.php?u=3590033 you can view the forum based on the unit you have and get the correct firmware. I used the free (LITE) version for about 1 week and then decided to pay the $20 to the developer to get the full version (SO WORTH IT!!). @Malaysk did an amazing job and this is the way to go!
Thanks,
Brady
jerkface41606 said:
Hello,
After many trial and error attempts I was able to finally find an extremely amazing OS! Malaysk is the way to go once you get your Seciane Unit. Everything works fully and is extremely easy to use. The installation was really easy honestly and it didn't take long to get it to work correctly. If you go to: https://forum.xda-developers.com/member.php?u=3590033 you can view the forum based on the unit you have and get the correct firmware. I used the free (LITE) version for about 1 week and then decided to pay the $20 to the developer to get the full version (SO WORTH IT!!). @Malaysk did an amazing job and this is the way to go!
Thanks,
Brady
Click to expand...
Click to collapse
Brady, thanks for this link. I have h221 and it appears I might be able to use the rom. What I can't do is get into recovery, and I can't get into developers options. I'm on a stock Android 9 and for some reason, they disabled the ability to tap the build # seven times to get to developers options. Did you have this problem, and how did you get into recovery mode. I searched everywhere and tried all combos of holding the reset button, no luck. I emailed secaine but no luck so far. Any help appreciated, Thanks johnm
Update and recovery instruction
Great to hear! I actually had the exact same issue as you and I found that seicane was of no help. However I finally figured out how to get into recovery mode (don’t need to do anything with rooting or getting into developer options). To get into recovery you should have a pin hole reset button. Do the following steps.
1. Hold in reset button until unit powers off and you see side buttons blink (10-20 seconds it usually took)
2. Immediately after this happens let the reset switch go
3. Immediately after this hold in button again until lights blink once (about 1-2 seconds)
4. Press and release button a third and final time and it will boot into recovery mode. (Quick press release)
After I got into recovery I wiped cache, then factory reset, rebooted, installed the recoveryinstaller apk file (included with Rom download) it reboots you and installs new rom and you will be good to go!
Thanks,
Brady

Yuehoo YH-605 (7inch 8core Allwinner T8, 4GB/32GB) root, improvements etc

Hello to the community.
I bought this unit 5 days ago, for the simple reason that it was the only unit with 4GB of RAM for under 100 euros! I bought it from banggood using a coupon code I saw in a youtube video.
I haven't installed it in my car yet, I've got it on my desk with power applied and keep playing with it.
I searched many forums to find any information I could about it and ways to improve it, so I decided to start a new thread here and keep all information together.
HARDWARE
7inch LCD, 2 DIN
8core Allwinner T8
4GB RAM
32GB ROM
STM32 MCU
Android 8.1 (NOT 9.0 as falsely stated)
HIDDEN "FACTORY SETTINGS" MENU
Settings - System - About Devices
Alternately tap on the Kernel Version - OS Version (3 times)
Be careful when playing around this engineering menu. Many people, including myself, pressed some button that shouldn't be pressed and ended up with a screen that didn't respond correctly to touches.
If you end up in a similar situation, don't panic and follow this simple procedure:
Connect a USB mouse.
Enter the hidden engineering menu.
Go to the "Other" tab. Find "Touch Learning":
Step1:Screen learning - you adjust the touch ... =>
Step2:Key learning - press "RESET" => touch the "Power" button and select Power at the left short touch = = OK ... then the "Back" button then "Volume +" and "Volume -" => now press "Save & exit" and you're done.
PIN when needed: 666666
The "Developer Options" menu cannot be unlocked like in any other Android device.
In order to have access to this menu, simply install QuickShortcutMaker from the Play Store and find it on the menu. Don't forget to press the little star on the right to move it on Favorites.
I hope there are other users of this unit out there and get this tread going. Next post will be about rooting this device!
Have fun.
ROOTING THE YUEHOO YH-605
DISCLAIMER!!!!!
A. Dealing with firmware modifications and "upgrades", always involves a certain amount of risk bricking your device! DON'T attempt anything if you don't fully understand this and you are not prepared to end up with a "dead" device.
I'm not responsible for anything you try, don't come whining afterwards to me if anything bad happens, you accept full responsibility for your acts.
B. Having said that, I consider this procedure pretty safe. We'll be using the "update procedure" to install new firmware from an SD card. If something goes wrong, you can try to install the original unmodded firmware and go back to a working device.
C. This procedure was executed by me to my own YH-605b, with the following characteristics:
Hardware Information: 8-Core AllWinner - ROM 32GB - DDR3 4GB - 1024x600 - d2
Kernel Version: Linux 4.4.89 - Wed Aug 28 16:11:04 CST 2019
OS Version: KC1D01I1-O49-3.0.4.3.5-IVT-20190828
MCU Version: STM32-20190828-11-KC2-30
If anything is different in yours, please consider if you want to try this, even more
D. I received my unit 5 days ago. I haven't installed it to my car yet. It is sitting on my desk with just power applied to it. This means that no sound, steering wheel controls, or any other car related stuff have been tested. I'm just testing it as an Android device and everything seems to work fine. This also means that the next one who tries the procedure, has to test everything afterwards inside the car and kindly return feedback! I'm not planning in installing this unit in my car any time soon, to tell you the truth I get more pleasure in "playing" with it on my desk, than having it entertaining me in my car Unfortunately, we are living in strange times and right now it helps me kill my time and learn stuff.
E. After the "upgrade", everything will be factory reset. Self-explanatory, just have this in mind, any changes you had made or apps installed will be gone.
F. As far as I can understand, iGO is installed by hand on the device, after manufacturing, during final testing. This means that after the "upgrade", the application will not be there. If you want to keep it, just copy the iGO folder to an SD before the procedure and copy it back and reinstall the application afterwards. As far as I can see, everything else will be there. If something is missing, please report back so everybody will know.
By the way, if anyone could send me the iGO folder, would be nice
G. From my research, people kept telling that the way to do an upgrade is by using the "hidden" internal SD card slot. That's what I used, but by mistake at some point I realized that the external works too! So, you should be able to use the SD card slot on the front face left for the procedure, if this does not work, then be prepared to dismantle the device and use the internal one. Warranty void alert!
PROCEDURE!!!!!
Funny enough, the procedure will be a LOT shorter that the disclaimer! I'll try to keep things as simple as they can be...
1. You will need a microSD card, at least 4GB. Maybe it can work with a USB flash drive, but I didn't have the time to test it.
2. Download the zip file, using the following link.
https://mega.nz/#!YRZl1ADC!JGyl9Occ6CMmxxftkUDOyFxXSn2Fh8kTVI7XLn6qrPY
The file contains the already rooted image of the original firmware, done by me. Also, the PhoenixCard folder which is needed to prepare the SD card, a short video of how to use PhoenixCard (not done by me), and the Magisk Manager application for the device.
3. Extract everything, best to your root directory, e.g. C:\ .
4. Watch the short video. Execute the PhoenixCard application and "burn" the image to the SD card. Give it time, it will seem that it froze but eventually it will finish. Safely unplug the SD card from the computer.
5. Insert the SD card on the device and boot it up. There should be a progress bar if everything is going OK. Wait for it to finish, there should be a brief message like, "CARD OK". The screen then will start to change colors from gray to black and flickering. Don't worry, give it a minute or two and then remove power.
6. Remove the SD card and power it up. If everything went well, it should boot up to factory restored Android. Connect to wifi and enter your Google Play credentials, as usual.
7. Copy from the computer to your SD card, the Magisk Manager apk. Insert the SD card to the device and using ES File Explorer install the application, following the suggested steps.
8. Open Magisk Manager and follow the suggested step. The application should do its magic, reboot and you are done! You've finally got a rooted device
For anyone that tries this, please give feedback, it's essential in order to help others. If anything goes wrong, don't panic and explain what happened, I'll try to help.
If something goes very wrong, try to burn the SD card with the original image provided and "upgrade" it with this.
Original firmware:
https://mega.nz/#!9JYFGYCI!QBHeC1c3sV4Dap0iQlZUyTE8eEld7w86vjmZqwMWeok
If someone is interested in the procedure of patching the original firmware, please tell me and I will prepare a short tutorial.
Have fun
I love this unit!
Hi, by any chance when you "open" the unit did you see anyway to add external mic. Because the one in the screen is very poor quality.... Also tried any car launcher like FCC that works with Bluetooth? It is very hard to find people with technical knowledge on this....
SimonC78 said:
Hi, by any chance when you "open" the unit did you see anyway to add external mic. Because the one in the screen is very poor quality.... Also tried any car launcher like FCC that works with Bluetooth? It is very hard to find people with technical knowledge on this....
Click to expand...
Click to collapse
Unfortunately, I reassembled the unit in order not to overheat too much, due to its poor design. I didn't see anything, but perhaps because I wasn't looking for an external mic connector
Maybe you could use an external USB one, just a suggestion.
Also, I didn't have time to play with other car launchers yet, when I do I will report back.
Have fun.
Hello my friend!
First of all my congratulations on the topic, it is the first I see about the YUEHOO YH-605b Head Unit.
I am from Brazil and I acquired this head unit recently, but unfortunately my experience with it was not good. Here are some bugs I found and some things I didn't like:
1. The main screen is horrible, very different from my previous head unit with Android Oreo 8.1, what I liked most about it was that the widgets already appeared on the main screen, on this device the main screen is black and without any widget from apps
2. The music and videos freeze out of nowhere during playback
3. I cannot synchronize my phone's phonebook with the device's phonebook, the message appears synchronizing... remains forever and does not sync any contacts
4. The image on the reverse camera is horrible, the same camera had a very good image on my old head unit.
5. The touch screen is terrible when you touch the corners of the screen.
My question to you would be these:
* Could this root procedure done by you fix some of these bugs?
* Is there a firmware update to fix these problems?
* Can you tell me if is possible to update the operating system of this unit to Android 10 or downgrade to Android 8.1?
I look forward to your responses.
Super
Well have done it and all went very well.
Phoenix Card can be a little flakey but apart from that really reall good.
Thanks a lot been hopeing for this for a while.
I would be intersted in the processe so if you do a little guide that would be super.
And again thanks a million.
Jon
Hi,
I also have this headunit, and have noticed it is unstable when trying to run more than 1 app simultaneously eg launch Igo then try to operate a split screen app, it crashes before even selecting another app.
I have checked with some fake memory apps and it appears to only have 2gb memory.
2gb should be sufficient to run simultaneous apps without crashing to launcher, is it possible to fix the incorrect memory amount (and android version) with root?
The launcher also seems to be memory heavy, it appears to take nearly 1gb on its own. I assume all the apps etc on the first page are a part of the launcher, so replacing it may not be possible without loosing functions.
I will upload the igo folder when i get a chance, it's a shade under 8gb so will take me a couple of days!
I'll leave a link when it's done.
Dave
obfripper said:
Hi,
I also have this headunit, and have noticed it is unstable when trying to run more than 1 app simultaneously eg launch Igo then try to operate a split screen app, it crashes before even selecting another app.
I have checked with some fake memory apps and it appears to only have 2gb memory.
2gb should be sufficient to run simultaneous apps without crashing to launcher, is it possible to fix the incorrect memory amount (and android version) with root?
The launcher also seems to be memory heavy, it appears to take nearly 1gb on its own. I assume all the apps etc on the first page are a part of the launcher, so replacing it may not be possible without loosing functions.
I will upload the igo folder when i get a chance, it's a shade under 8gb so will take me a couple of days!
I'll leave a link when it's done.
Dave
Click to expand...
Click to collapse
Thank you obfripper for your eye-opening message!
I knew that the OS version was spoofed, but I could have never thought that they would spoof the RAM amount too! Silly me.
Unfortunately, you are right. I checked with "Fake Device Test" and your point came true. And for the fact that I was still skeptical, I double checked with a terminal emulator with the "free" command, same result :'(
As for your questions, I searched for restoring the correct amount of RAM in the OS. It's a very difficult procedure, you literally have to recompile the kernel, which is something I don't have the knowledge, neither the time to do. Guess we are stuck with a scam device.
As far the launcher goes. Some apps are indeed dependent on it, some are not. Some people replaced the default apps with others (radio, phone etc) but many of them have issues and don't work, so I'm staying away of trying to replace them. The launcher could be replaced with the stock one with some effort, but although I don't like it being too simple and too "golden", I find it convenient so I decided to keep it.
The only thing I will do is change the "golden" theme which I hate, to a more fancy "green" one. This will happen soon and I will share it when it's done.
I ordered my unit in early March from banggood. I entered their site and opened a complain asking for full refund for being scammed. I'm pretty sure I'll get at least half of my money back and then I will be a little more satisfied with my purchase.
Thank you Dave for all the interesting information and I will keep you updated.
@MarkoDiMarko
Will the device be stable when I install your custom rom. I've also this device and the navigation app keeps closing itself. When the root will fix it I hope I have a stable device. I use TomTom for navigation.
****tyNL said:
@MarkoDiMarko
Will the device be stable when I install your custom rom. I've also this device and the navigation app keeps closing itself. When the root will fix it I hope I have a stable device. I use TomTom for navigation.
Click to expand...
Click to collapse
There will be no difference in stability, neither better or worse.
It's the factory ROM, only patched to be rooted with Magisk.
I'm also contacting banggood. It's not working stable with the tomtom navigation app. I think that's becouse the app will use more ram than that's actualy available and then crash.
MarkoDiMarko said:
Thank you obfripper for your eye-opening message!
I knew that the OS version was spoofed, but I could have never thought that they would spoof the RAM amount too! Silly me.
Unfortunately, you are right. I checked with "Fake Device Test" and your point came true. And for the fact that I was still skeptical, I double checked with a terminal emulator with the "free" command, same result :'(
As for your questions, I searched for restoring the correct amount of RAM in the OS. It's a very difficult procedure, you literally have to recompile the kernel, which is something I don't have the knowledge, neither the time to do. Guess we are stuck with a scam device.
As far the launcher goes. Some apps are indeed dependent on it, some are not. Some people replaced the default apps with others (radio, phone etc) but many of them have issues and don't work, so I'm staying away of trying to replace them. The launcher could be replaced with the stock one with some effort, but although I don't like it being too simple and too "golden", I find it convenient so I decided to keep it.
The only thing I will do is change the "golden" theme which I hate, to a more fancy "green" one. This will happen soon and I will share it when it's done.
I ordered my unit in early March from banggood. I entered their site and opened a complain asking for full refund for being scammed. I'm pretty sure I'll get at least half of my money back and then I will be a little more satisfied with my purchase.
Thank you Dave for all the interesting information and I will keep you updated.
Click to expand...
Click to collapse
Hi,
two days ago I received the same radio from banggood. Have you already got any feedback concerning your complain from banggood? Did you get any money back?
_KoSTeK_ said:
Hi,
two days ago I received the same radio from banggood. Have you already got any feedback concerning your complain from banggood? Did you get any money back?
Click to expand...
Click to collapse
I opened up a dispute and they asked for photos and video, showing the problem.
I decided to upload a video on Youtube and send them the link, you can watch it here:
https://www.youtube.com/watch?v=_bRxONGk_BA
Offers, declines and counteroffers started and continued. The biggest amount someone else got back and keep the device, was 40 euros + 2200 BG points. So, that was my last counteroffer to Banggood and that is what I got.
Good luck with the dispute!
MarkoDiMarko said:
I opened up a dispute and they asked for photos and video, showing the problem.
I decided to upload a video on Youtube and send them the link, you can watch it here:
https://www.youtube.com/watch?v=_bRxONGk_BA
Offers, declines and counteroffers started and continued. The biggest amount someone else got back and keep the device, was 40 euros + 2200 BG points. So, that was my last counteroffer to Banggood and that is what I got.
Good luck with the dispute!
Click to expand...
Click to collapse
After a month struggling with Banggood they refunded me about 35euro. It seems, that through this whole time they have not considered my offers. It was very difficult to negotiate with them, consultant send very similar propositions and information all the time. I also wrote a negative opinion about the product but they did not post it at the auction.
They seems to change cpu in the device...new one purchased on 17/07 has cpu allwinner t3 with max 1200 Mhz same fake 4 Gb memory and fake android....but came with already rooted firmware but not properly working root.
I had the imprudence to buy a radio tape recorder for $ 113 YUEHOO YH-605 on banggood.com.
Everything in it is good according to the description and a video with disassembly and display of components confirms this. Unless the amplifier is soldered from 7388 to 7850.
But in fact it was not what was in the description.
Instead of Android 9 installed 8.1
Allwinner T3L 4 Core 1.2GHz is installed instead of Allwinner T8 8 Core 1.8GHz
Instead of 4GB of RAM, only 2GB is installed. But this is understandable. Allwinner T3L works with no more than 2GB.
bluetooth does not interface with anything other than the phone, you can forget about ELMs and bluetooth adapters for diagnostics of gas equipment (in my case Stag).
Which radio chip is soldered is not clear, the sticker was ripped off by the conspiracy the Chinese and without removing the shielding protection of the soldered one is not possible.
I can't add a photo. I have less than 10 posts. Who disassembled and who has a photo of a sticker with a radio chip designation? I have not yet been able to get the firmware from the seller in order to understand what kind of chip is indicated in it.
"translate by google", sorry.
Seems they brought out a yh-605b version
Ordered mine from banggood (deal price £90 delivered with insurance) from eu warehouse (to the uk)
I ran the fake test device app and although android version is still scammed, they have greatly improved the memory issue! Over 3gb ram (I'll run the test again and update my post with exact figures today).
The manual they provided shows a different stereos wire diagram which is confusing...
Does anyone know if the 8 pin (female on the stereo) is where the steering wheel controls plug into? Im struggling to get it working on a seat altea (factory fitted vw engine) i have the right adaptor so everything else works fine!
Also which igo files are safe to delete or are there any that need to stay? I use google maps and galaxy note 10+ 5g is the no brainer processor to run sat nav ?
Thanks ?
tina333 said:
Does anyone know if the 8 pin (female on the stereo) is where the steering wheel controls plug into? Im struggling to get it working on a seat altea (factory fitted vw engine) i have the right adaptor so everything else works fine!
Also which igo files are safe to delete or are there any that need to stay? I use google maps and galaxy note 10+ 5g is the no brainer processor to run sat nav
Thanks
Click to expand...
Click to collapse
As I can remember hooking it up, you use the "KEY1" cable, plus I used a ground to connect them to the 2 pins that came from my car.
I have already lost the "iGO" folder during update But I remember that there was a folder named "iGO" that contains all the files. If you use a file explorer, I'm pretty sure you will find it and remove it safely.
I have a similar unit I purchased back in March from aliexpress. I stumbled across this post as I'm hoping to find a root solution. Mine passed the android version test on Fake Device Test app even though it's reporting as 9.0 in about device, actual is 8.1, so kinda weird it's reporting correctly everywhere but the about device section. Ram was advertised as 2GB on my device, reported accurately. The sellers page said that if it has 4 cores it is T3 and 8 cores is T8 but everything on mine is reporting as T3-P1, including Fake Device Test app and CPU-Z, even though it does show it indeed has 8 cores. Your devices specs seem to fit closest to my device of any I've seen posted about. My device specs are as follows:
Android Version = 9
Hardware Information = 8 Core Allwinner -ROM 32GB - DDR3 2GB - 1024x600
Kernel Version = Linux 4.9.118 - Wed Oct. 16 13:55:41 CST 2019
OS Version = KC1C01D5-O55-1.0.4.3.1 - BLINK_NETWORK - 20191016
MCU Version = STM32-20190924-11-KC1-38
I figure these units were probably pieced together with spare parts they had a fair amount of. I want to try your root method, but I'm a bit leary of flashing anything to this unit in fear it won't work again. I at least need to make a full back up of each partition before doing much of anything. Due to the minor differences in our Kernel, OS and MCU versions I hesitate to flash the file you provided in Post 2. I learned my lesson a few years ago on an older MTCB unit that I spent two or three days recovering after flashing an incompatible file. Would you be willing to provide the steps taken to achieve root access? Thank you in advance!
Steve1698 said:
I have a similar unit I purchased back in March from aliexpress. I stumbled across this post as I'm hoping to find a root solution. Mine passed the android version test on Fake Device Test app even though it's reporting as 9.0 in about device, actual is 8.1, so kinda weird it's reporting correctly everywhere but the about device section. Ram was advertised as 2GB on my device, reported accurately. The sellers page said that if it has 4 cores it is T3 and 8 cores is T8 but everything on mine is reporting as T3-P1, including Fake Device Test app and CPU-Z, even though it does show it indeed has 8 cores. Your devices specs seem to fit closest to my device of any I've seen posted about. My device specs are as follows:
Android Version = 9
Hardware Information = 8 Core Allwinner -ROM 32GB - DDR3 2GB - 1024x600
Kernel Version = Linux 4.9.118 - Wed Oct. 16 13:55:41 CST 2019
OS Version = KC1C01D5-O55-1.0.4.3.1 - BLINK_NETWORK - 20191016
MCU Version = STM32-20190924-11-KC1-38
I figure these units were probably pieced together with spare parts they had a fair amount of. I want to try your root method, but I'm a bit leary of flashing anything to this unit in fear it won't work again. I at least need to make a full back up of each partition before doing much of anything. Due to the minor differences in our Kernel, OS and MCU versions I hesitate to flash the file you provided in Post 2. I learned my lesson a few years ago on an older MTCB unit that I spent two or three days recovering after flashing an incompatible file. Would you be willing to provide the steps taken to achieve root access? Thank you in advance!
Click to expand...
Click to collapse
If every version is not the same as yours, do NOT use my patched version, this would be a recipe for disaster.
First make sure you have some original firmware you can always revert to (you can only be sure if you have already tested it and everything went on smoothly) and then we can discuss how you can patch the original firmware, if I can remember the procedure after so many months

Categories

Resources