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!
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.
Help all, While trying to get root access (I managed temporary sofar), and removing some apps after that (as I still didn't got the desired result : have my custom launcher as default) the unit is stuck at startup.
It's running on android 7.0, model, for what it's worth ; an alps hla1280 *480, 4gb ram, 32gb storage.
Before this happened I tried to connect to the unit trough my laptop but never succeeded. Hope someone can help!
I already did a hard reset, and took the power off, but no result.
A friend of mine got tha same mt6735 from mekede but he has the real Android 9 (CPUZ)
I'm in same situation as you but without rooting...
Really wanna try to get a custom launcher to replace the actual one (with the white ball for menu) but i'm so scared to brick it like you... Hope someone gonna help you
Look like this CPU isnt really common on the server
AxoO69 said:
A friend of mine got tha same mt6735 from mekede but he has the real Android 9 (CPUZ)
I'm in same situation as you but without rooting...
Really wanna try to get a custom launcher to replace the actual one (with the white ball for menu) but i'm so scared to brick it like you... Hope someone gonna help you
Look like this CPU isnt really common on the server
Click to expand...
Click to collapse
It's quite disappointing that no one reacts.. Guess it's not the mcu people want to help for. Or they think we should search at xda but nothing helpful to find.
muish002 said:
It's quite disappointing that no one reacts.. Guess it's not the mcu people want to help for. Or they think we should search at xda but nothing helpful to find.
Click to expand...
Click to collapse
Can't even use Carplay dongle lol my usb isn't recognized :/
Hey I recently purchased a Hikity 10.1 head unit. This thing has an awful custom rom and I was hoping to be able to flash the stock or a modded rom onto it. Its def all over the place as well I can't tell what exactly its on. It says its android 11 which is obviously wrong but aida64 says api level 29. So gives me a little bit of a clue. But one thing that's puzzled me a bit is the android number in the radio itself it reads as D02022HA16_AHD_0012_V009_HIFI which I'm guessing is some custom version from hikity but I can't find much info on it and I don't want to end up bricking it. I've included some shots from the head unit of their screen, aida64, and faketest. I do know its a full_8227L_demo by aida's screens but I want to make sure I am flashing the right thing if its even possible to flash it. Id love to put on supermod as that's what I had on my last unit but again, I want to be sure. (This was a christmas present, had I bought it myself, would have just got one I knew.)
Also I tried multiple times to install CPU-Z but it will not work no matter what I do. It opens and closes soon as it opens. I've tried different versions and tried factory resetting and trying it. Still won't work so I have no way of getting any information at this time from it.
Any help is greatly appreciated. Let me know if more info is needed!
https://hosting.photobucket.com/images/c287/dlynnjr/1.jpg
https://hosting.photobucket.com/images/c287/dlynnjr/2.jpg
https://hosting.photobucket.com/images/c287/dlynnjr/3.jpg
https://hosting.photobucket.com/images/c287/dlynnjr/4.jpg
So i was able to get CPU-X to work. Here is what I got off of that.
https://hosting.photobucket.com/images/c287/dlynnjr/6.jpg
https://hosting.photobucket.com/images/c287/dlynnjr/7.jpg
https://hosting.photobucket.com/images/c287/dlynnjr/5.jpg
Not (MTCD) requested moderator move to (Android head-units) forum
Op suggest read of forums, get sense of what your unit is and you could then search for unit based on MCU prefix. There's a million posts that detail that (mostly from yours truly
Alternatively first contact is reseller
I swore I got it in the right spot. Guess not though. I couldn't never find the correct forum I guess. But I appreciate the help I'll look around more. Unfortunatley the reseller was absolutely no help. Basically holding any information hostage for good feedback and refused any help at all until I left some.