• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

Bricked Atoto A6, Need some help.

Search This thread

stabone00

Member
Jul 25, 2010
48
22
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.
 
Last edited:

stabone00

Member
Jul 25, 2010
48
22
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 .
 

Croak

Senior Member
Oct 9, 2007
1,629
271
Mulberry
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 .

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.
 
Last edited:

stabone00

Member
Jul 25, 2010
48
22
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.
 

Croak

Senior Member
Oct 9, 2007
1,629
271
Mulberry
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.
 

tagara1

New member
Dec 31, 2017
1
0
Knoxville
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
 

stabone00

Member
Jul 25, 2010
48
22
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.
 

stabone00

Member
Jul 25, 2010
48
22
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.
 

smithkt

Member
Dec 31, 2017
9
1
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.

I have the same unit. If you can tell me how to pull it, I'd be happy to help.
 

stabone00

Member
Jul 25, 2010
48
22
I have the same unit. If you can tell me how to pull it, I'd be happy to help.

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.
 

smithkt

Member
Dec 31, 2017
9
1
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.

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.
 

stabone00

Member
Jul 25, 2010
48
22
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.

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.
 

scoolro

Member
Aug 18, 2010
45
4
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
 

stabone00

Member
Jul 25, 2010
48
22
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

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.
 
  • Like
Reactions: bluemind497

scoolro

Member
Aug 18, 2010
45
4
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
 
Last edited:

stabone00

Member
Jul 25, 2010
48
22
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.
 

Croak

Senior Member
Oct 9, 2007
1,629
271
Mulberry
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.
 

Croak

Senior Member
Oct 9, 2007
1,629
271
Mulberry
I ended up sending my 62721p back and am waiting for the pb model.
Did you have it rooted?

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.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    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
    1
    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

    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.
    1
    After the last time I did a factory reset, I used kingoroot and then I used the supersu.apk from the zip and installed it with adb. After it said it failed I reset and SuperSu had root. Then I removed kingouser. The first time I pretty much did this: https://appuals.com/replace-kingoroot-supersu/ . Give that a try.
    1
    I dont have any experience with the Metra kit for the SWC but with my PAC unit in my Chevy Tahoe, PAC told me just to use the Key plus wire I think it was but that didnt work. I ended up having to use both the key and key plus wire. I soldered a 3.5mm female jack to the two and then just pluged in the 3.5 mm male plug from the PAC unit into it and worked great.

    EDIT: I know my PAC unit wont work with steering wheels that the climate controls on them. And by that, I mean the climate controls on the steering wheel wont work anymore but everything else will. Getting the SWC to work can be a pain sometimes. Took a bit for me to figure it out on the head unit once I got them actually working.