Related
Hello
Sorry for this but I am at wits end trying to figure out what is going on with my android head unit -
firstly it wouldn't load up at then then now I have to load it up in recovery mode to even see the screen, i attempt to install the image file which I was told to download and put on an empty micro SD card but this is what displays when i attempt to do what they describe, they try to be helpful at pumpkin but they tell me the same things over and over again, I know I'm not a developer but I'm certainly not a vegetable.
please see below for the errors i get can anyone make any sense as to why I'm getting these and how to find a fix for it?
It would be much appreciated greatly by me.
This is the link which i was told to download (news.autopumpkin.com/how-to-upgrade-your-android-head-unit-from-4-2-to-4-4-kitkat/)
(the first one I cant post links)
I have never been able to see the unit actually working so do i need to use something different rather than 'upgrade'?
Regards,
Chris E
I'd be concerned about the "Parse error" which is shown. Maybe a bad download? Have you tried downloading with a different browser?
You can also try Malyask's firmware. You need the 800x480, RK3066 version. I'd suggest the newest, from July 7th.
But, if it's never worked, maybe there's a hardware issue which installing firmware won't fix.
mike.s said:
I'd be concerned about the "Parse error" which is shown. Maybe a bad download? Have you tried downloading with a different browser?
You can also try Malyask's firmware. You need the 800x480, RK3066 version. I'd suggest the newest, from July 7th.
But, if it's never worked, maybe there's a hardware issue which installing firmware won't fix.
Click to expand...
Click to collapse
Just about to try with a different browser and different machine so hopefully that'll fix it, i will let you know in due course.
UPDATE: different browser still no luck so I will try Malyasks version
For what I see on the 2nd picture, it seems like the MCU is not getting installed. Since you already tried downloadin it on a different browser, ty using a different SD card and maybe do a checksum to compare the file on your PC and the file on the SD after you copy it. 99% of the times I've had probelms like this on phones (havent had them on the radio yet) it's been an error while copying.
UPDATE
Thank you for your help guys.
But I have discovered by it wasn't working - it was a silly error on my behalf it was fault in my wiring - I didn't think it would be anything to do with the wiring as I didn't think it would even power up if that was the case but it is if anyone else has this problem this is the cause -
The ignition wire coming from the stereo (normally red) doesn't have any power going to it.
(I wired the ignition wire to ground - thus no power going to it) :silly:
If anyone is unsure (as I was) - in a Vauxhall/Opel Corsa the wires are:
Black - Ground
Brown - Live
Good to hear you got it working and you posted the fix here in case it happens to somebody else.
Cheers!
Hi guys, im going round the bend with my Vauxhall head unit from A-sure, the number on top starts L2OVBR.
I have seen a few posts about upgrading by sd for the S3 models of these same units, but none for my type.
I tried the S3 rom and it trys to load but i get error message about files being missing
INFO: CANT FIND MCU FILE
INFO:CANT FIND STM32VD.BIN
DVD:INFO: CANT FIND B288ROM
INFO:NAND ID EC F1 00 95 41 EC
This is the info i get when attempting to load the S3 rom. I assume the s3 and the L2 are not compatable?
What happened was while playing from usb the usb came loose and turned off, the unit then went blank.
Now when i press the reset with a pin, the car logo will give a quick flash then cut out. I have tried holding pin in for 2 min, tried combination of buttons but still the same.
Any help hould be great, If anyone could link me to the rom i need that would be great, As it does try to load the rom but i cant get the right one. A-sure dont respond to Ebay or facebook or Email.
Thanks for taking your time to read and i hope you can help me.
Regards, Charles
chicrfc said:
Hi guys, im going round the bend with my Vauxhall head unit from A-sure, the number on top starts L2OVBR.
I have seen a few posts about upgrading by sd for the S3 models of these same units, but none for my type.
I tried the S3 rom and it trys to load but i get error message about files being missing
INFO: CANT FIND MCU FILE
INFO:CANT FIND STM32VD.BIN
DVD:INFO: CANT FIND B288ROM
INFO:NAND ID EC F1 00 95 41 EC
This is the info i get when attempting to load the S3 rom. I assume the s3 and the L2 are not compatable?
What happened was while playing from usb the usb came loose and turned off, the unit then went blank.
Now when i press the reset with a pin, the car logo will give a quick flash then cut out. I have tried holding pin in for 2 min, tried combination of buttons but still the same.
Any help hould be great, If anyone could link me to the rom i need that would be great, As it does try to load the rom but i cant get the right one. A-sure dont respond to Ebay or facebook or Email.
Thanks for taking your time to read and i hope you can help me.
Regards, Charles
Click to expand...
Click to collapse
Nobody?
wince 7?
Looks like these units are loaded with Wince 7, I have emailed A-sure but no answer as of yet, im not surprised as all over the internet it is reported they aint interested, and when they do they want you to return the unit to china!
I have been looking all over the internet for the files i would need to repair the software but cant find a thing.
I downloaded a file called 117-nav-en-wince6 that was reported to help restore windows on these units but nothing with mine, just a blank screen until you press the reset button and then you would get a quick flash of the vauxhall icon and then goes black again.
Im wondering if something has fried inside the unit? but then it does try to load the wrong android files as it should, and the picture comes up when pressing reset so would imply the graphics chip is ok?
Nobody got any ideas at all?
ran 12v to the unit and canbus connection to rule out the canbus but it still does the same with the canbus box disconnected.
so def a problem with the unit. Am i alone in the forum? lol
Fixed the unit by restoring the software. I now have the software for the L2 and L4 A-sure models
just incase somebody else runs into the same problem, and gets about as much help as i did.
Least its fixed.
same problem
chicrfc said:
Fixed the unit by restoring the software. I now have the software for the L2 and L4 A-sure models
just incase somebody else runs into the same problem, and gets about as much help as i did.
Least its fixed.
Click to expand...
Click to collapse
my friend i have
Android 6.0 DVD GPS DAB+ für OPEL Astra H Antara Corsa D Vectra Zafira B Vivaro
and have the same problem,
can you help me?
thanks
hi chris where did you find the file to download have the same issue as you did
Sofia Su6-136A Dead after After trying to Update Firmware
I have android head unit which is working fine when i try to upgrade firmware with SD Card because after some time unfortunately setting has stopped error. After inserted memory card in SD Slot my unit has been died .
Unit only show brightened screen when i insert a memory card with update file in slot, unit making SLOG file on card.
Detail of Unit:
Skystar Su6-136A
1GB Ram
32GB Rom
10" full Touch
No Physical button without DVD
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.
Xtrons TR100 UltraOcta T8 stuck in boot loop from trying to install Magisk via their manager and can't figure out how to get this thing into recovery mode. I've talked with a rep from Xtorns about this issue and he informed me that I'd have to do a "Key Wire to Ground" in order to get into recovery. He also stated that if I had my SWC hooked up I could just press any button along with the reset but yet that doesn't work either. I've gotten as far as seeing a screen that says "Start Upgrade" but then it goes right back into boot loop. I've never felt so defeated in my life..... I've reached out to some that have the same unit but haven't gotten any reply.
brknneks said:
Xtrons TR100 UltraOcta T8 stuck in boot loop from trying to install Magisk via their manager and can't figure out how to get this thing into recovery mode. I've talked with a rep from Xtorns about this issue and he informed me that I'd have to do a "Key Wire to Ground" in order to get into recovery. He also stated that if I had my SWC hooked up I could just press any button along with the reset but yet that doesn't work either. I've gotten as far as seeing a screen that says "Start Upgrade" but then it goes right back into boot loop. I've never felt so defeated in my life..... I've reached out to some that have the same unit but haven't gotten any reply.
Click to expand...
Click to collapse
Try this method like they suggested "key wire to ground", hope that help!
https://www.youtube.com/watch?v=HUAC0AUleEQ
iRcKenny said:
Try this method like they suggested "key wire to ground", hope that help!
https://www.youtube.com/watch?v=HUAC0AUleEQ
Click to expand...
Click to collapse
Holly hell! I've been looking for that video, I knew I had seen one somewhere. TY!! I'm going to go try now. I've been in contact multiple times with them via email and pm's but they are so limited on they way they give instructions. They are like hold them for 3 secs and it should go into recovery. So if the "Key 1" wire is the ground then it really shouldn't matter which button I press. But there's still a sequence that needs to be done. I think from what I seen in the video he holds the "Key 1" wire to the chassis. clicks the "Reset Button" turns on ACC then hits the "Reset Button" again all while holding the "Key 1" wire grounded. I'll watch one more time. Also I got the files from Xtrons I've upgraded my system in the past just putting the 4 files on a USB stick. But doing it this way do I need to leave as .Zip? Does it need to be renamed? Thanks for the help! I'll let you know if this works......... :fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
Yea this thing simply will not load into recovery. I get the Start Update with what looks like a bar in the middle of the screen and then back to boot loop. Do I need to create a boot SD to bypass?
brknneks said:
Yea this thing simply will not load into recovery. I get the Start Update with what looks like a bar in the middle of the screen and then back to boot loop. Do I need to create a boot SD to bypass?
Click to expand...
Click to collapse
I think you need try the entire sequence without SD card os USB connected to the unit.
After you get into recovery, need only use the "firmware file" update.zip placed in SD card or USB root.
There is another video with different sequence; myabe this work for you: https://www.youtube.com/watch?v=lPQgV_55Rkk
Good luck!
iRcKenny said:
I think you need try the entire sequence without SD card os USB connected to the unit.
After you get into recovery, need only use the "firmware file" update.zip placed in SD card or USB root.
There is another video with different sequence; myabe this work for you: https://www.youtube.com/watch?v=lPQgV_55Rkk
Good luck!
Click to expand...
Click to collapse
Yea think I'm throwing the towel in on this one and return it. Seems as if nobody has this model for some reason?? Every one I've tried hitting up hasn't contacted me back. And I'm not going to sit around for months waiting on reply's. Thanks for trying to help though! :good:
brknneks said:
Yea think I'm throwing the towel in on this one and return it. Seems as if nobody has this model for some reason?? Every one I've tried hitting up hasn't contacted me back. And I'm not going to sit around for months waiting on reply's. Thanks for trying to help though! :good:
Click to expand...
Click to collapse
If you are in warranty time, that's maybe a better solution; last resource is @marchnz [PX3 & 5] [OTG] - No Headunit Mod, recover or flash a SOM with a simple USB cable
iRcKenny said:
If you are in warranty time, that's maybe a better solution; last resource is @marchnz [PX3 & 5] [OTG] - No Headunit Mod, recover or flash a SOM with a simple USB cable
Click to expand...
Click to collapse
I've been wondering if there was a way to hook up this edge note via usb to this thing to see if I can maybe see what's going on some how?? I've been on google for hours looking for something but everything seems like you need to hook it up to a pc. Guess I'll just run a long ass USB cable out the window and leave the care running. LOL
Welp...... I've been on the phone with Amazon all morning. The lady that was helping me wanted to see what she could do about just giving me a refund and then me buying another one, then ship this one when it comes. So she puts me on hold for a while and comes back and said that the guy wouldn't let her give me a full refund in credit. They could only do $219!!! Are you kidding me?!?!?!?!? So i spoke with a supervisor and got it taken care of so now i'm sitting here thinking. Do I really want to go back to a unit that I don't know how to get into recovery if something happens again. So do i pay the extra 14 bucks for the XTRONS 7 Inch Android 8.0 Octa Core 4G RAM 32G ROM and lose the screen size but it be flush. I'm going down in screen size but gaining Rockchip octacore PX5 A 53 architecture 64 bit cpu and 4 gb DDR3 kingston memory.
Personally, I'd go for the smaller screen size with more RAM (twice as much), a faster processor and physical buttons (personally, I don't think I'd ever get a unit without a rotary volume control!). Like you said, you don't want to get stuck in this same situation again later where you can't get into recovery if you need to... Yes, a larger screen is nice, but it's not worth it in this case (IMO).
But, with that being said, the difference between 7" and 10.1" is significant. Not sure how used to 10.1" you are or if the larger screen is very important to you - but you'd be surprised how much of a difference there is between a 7" and 10.1" screen!
Just my two cents.
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