Related
Hi all,
Firstly apologies for the long post, and thanks for all the info that is up here... however I have managed to get quite lost. I'll try to take you though the whole story as much as I understand it, but I woke up this morning and decided (after 8 months) to finally root my android.
That was 8am, it is now midnight, and I've had sandwiches while working at it, all day. It has been in various stages of bricked, and I think I might have just sent it back that way - should not be playing with it when tired.
Things I have
1 x UK Vodafone HTC Magic, doing return plus power = 32B, HBOOT-1.33.0009 (another story here).
1x 16GB SD-HC card
1x 1gb Card
1x cheap nokia I can use as a reader for the 1gig card, but it can't handle SD-HC
Anyway I started off with the 1 click root idea, which obviously doesn't work these days, so followed the next link, then the next, finding I need to do the 'goldcard' method.
theunlockr.com/2009/08/14/how-to-root-your-mytouch-3g/comment-page-3/
Anyway I'm not sure where all the time has gone (16 hours now), but I have learnt what an SPL was, flashed mine to an ‘imperfect’ one, managed to flash it to deteethed google, then cyanogen on top, but it would never boot, and just hangs saying HTC Magic, then managed to flash it using 'myhero' which gave me a Hero like phone.
However I now seem to have messed it up again as I'm determined to do the cyanogen mod - I really want to be able to tether, and lots of other bits and pieces.
The state at the moment therefore is I have it all working with fastboot, and can easily get the Amon_RA recovery image going, but the cm_recovery one makes it hang and do nothing. If I try and replace the recovery section using fastboot it tells me it has failed (I forget the exact message).
I can therefore upgrade things using the Amon_RA backup, but as I said things don't seem to entirely work, and at the moment my phone is hanging (I think as I'm tired I've overwritten my backup). I'm also not sure if this goldcard method is working – I asked a question in the thread and it seems that it might not be.
I guess I'm just looking for a few pointers, after 16 hours sat here I'm generally pretty frustrated and totally lost - there is a lot of information, but there are so many permutations of hardware, and a lot of the information is now out of date. Trying to take everything in as well as deal with a specific problem may actually be beyond me Which is something I hate- being the newbie needing help with a potentially simple problem (though I have had a good go at it).
I'm really not sure what stage the phone is at, have I rooted it? After all I can use the myhero rom, but on the other hand I can't do what I want to do, so therefore is there a problem? Exactly which step makes it ‘rooted?’ as every guide is obviously a chain of events to make it in to something else. I'm honestly not sure, but it isn't a fun feeling – I’m stressed and at the momentI have no phone just a brick that I can fastboot to recovery, and a bunch of backups as soon as I get it working again.
I really had no idea it would be this difficult, and am a big angry at Google/HTC for making it so - it is easier to get Hackintosh working than this! I’ve also managed to do hundreds of other similar things without any problem – Xbox Media Center (including soldering), and a few more spring to mind, all to use the hardware I already own! My hardware!
Anyway advice and pointers are appreciated, as although I've learnt a lot today, I'm still blundering about, and it is a matter of time until I cause serious damage in my attempts to make it better, al alternatively just throw in the towel, but then I don’t think I can go back as I have a horrible feeling that the restore I did didn’t work.
Again anything you can offer is appreciated, and if you need more detail, I’ll do what I can!
Anthony
Also just to add I've tried searching, which is partially how I've got myself in to this mess - solve one problem but make another!
Also I do have my APN settings, so when I get it installed, I can get my google account workign with it - I think i've had to do this about 6 times now! So if there is a way to get it in to 'myhero' which I think I can do again, and download an apk, then I should be able to do that.
Ant
There is a lot of information and everyone is recommended to do their research before rooting the phone.
That being said, it sounds like your phone is rooted if you can boot into recovery and load up a sense ROM. It'd been much easier to follow cyanogen's wiki instructions for non T-mobile 32B Magics. I also have a vodafone Magic and I rooted my phone successfully using the method.
Not having used the goldcard method, I don't exactly know where it went wrong. Have you done full wipes before applying a zip file? Stuff like that which might be easily overlooked?
Yeha I've been wiping it all before flashing, so that isn't the problem.
I also did as much reading as I could before starting (and watching the youtube guides before doing anything), but I guess a lot of the problems were unexpected (aren't they always?), for example I only found out half way through that I would need to flash the SPL, and it took me 40 minutes to figure out what SPL was, and what it did, then another 40 to work out how I was going to do it, then 40 to do so.
I have been following guides though - for the cyanogen one I get all the way down to flashing it with the detoothed google build, then cyanogen (obviously wiping before doing these). All the steps appear successful but then it doesn't boot.
The phone is also a rather strange one, a vodafone branded one that says 32B, but I'm sure it has more RAM.
Currently trying 'method 2' from here
android-dls.com/wiki/index.php?title=Magic_Rooting
to see if that works, but I'm not optimistic.
Yup 15 minutes laters same problem - it hangs on HTC magic screen, which is exactly what it does when I go for the Cyanogen one.
I'll goign to try and google for other roms, see if any of them work sucessfully (and might provide a bridghe to what I want to have.
Again however anybody knows good guides, sites or anythign else let me know.
As I said a big problem before is I'm reliant heavily on google, and a lot of the informaion out there is useless, as it is out of date in a big way. Also I don't know anyoen else who has doen this, so recommendations ofmethods/roms are dependent on my reading, not wword of mouth (which is generally better).
Ok I've tried the method 2, defiantely no sucess, went back to the myhero (which performs awfully, so much lag!), and have now tried flaskrec.apk on there.
It does not backup, but then bypassing that step, it gives me the error 'Flash failed'.
Really stuck now, and no idea what to try, any suggestions at all would be helpful. I'm almost at the stage of wishing I'd got an iphone :-(
I hate to have to write this asking for help but I wasn't able to use the other posts I found to help me. The directions for touchnooter seemed straight forward, but I am stuck anyway. Here is what I did and what is happening, and what I have tried to remedy situation. It is a bit long, but I wanted to be as complete as I can.
I have a new nook bought at end of March so assuming it has latest update. I followed directions and was able to get touchnooter onto microsd card. I stuck it in nook and turned on. I got an instruction screen saying to take card out when screen goes black and reboot. My screen did go dim but you could still see the writing behind. I wasn't sure if this what they meant by going black or if I was waiting for complete darkness. I think I panicked for a second (don't know why) and might have rebooted with the card still in (would this have created a problem that I will be describing).
So upon rebooting, it goes through the same reboot nook screen, gets to a screen with an n and the balls and that is the furthest I have gotten it. Messing with the power key seems to initiate a reboot, but it still never makes it past the n screen. Cannot turn off the nook. I was able to get it to give me the factory reset message by doing the failed reboot 8 times. I tried that a couple times but wasn't able to get any further past the screen with the n, so it seems it may not be doing any resetting. I tried repeating the rooting process (except for the shuting down the nook part since I can't actually get it to shut down) and it gave me the same rooting instruction page but no change the problem of not getting past n screen.
I have seen people asking similar questions about rooting with something else called CNW or something because the touchnooter didn't work for them but I didn't understand the instructions and wanted to get help first before trying something else. I had also read that there is something called a factory restore, which is supposed to be different from reset but I don't know how to do that. I downloaded barnes and nobles latest update thinking I would just reload it/ but I can't see my nook from my computer (do I need to download some drivers? Or is this because it can't get past the n screen?). I tried using a different microsd card in case the first was faulty, but didn't help.
Does it seem there is something wrong with the touchnooter content on the card, like maybe it doesn't work with the latest nook update? Also wanted to mention, I did not do a backup before trying to root. I originally planned to but after I was done researching what I needed to do and got to the touchnooter downloading directions, they didn't mention it, so I didn't do it (besides that, I don't know how to do it and don't know if it would help in this situation anyway). Could it be that the nook itself has a problem?
Anyway, I would still like to root but would be happy to at least get a basic nook back. If you have made it this far in reading my problem, what do you think I should try? I am thinking of taking it back since I don't think it actually rooted but if I can fix it, that would be better. Thanks in advance for anyone who takes the time to work on this with me. I wish I had someone right in front of me to ask questions to but this the next best thing.
Thanks!
Tara
I am really leaning towards just seeing if I can return it. The instructions for touchnooter seemed so straight forward and I thought I could handle it. Since it didn't work and I don't even know if it was a problem with something I did, the device, or the touchnooter (since other people with new nooks are having similar problems), then I don't even know if it is something that will work at all. Trying to use some of the other methods are just way beyond my ability without more detailed instructions. Sigh.
http://forum.xda-developers.com/showthread.php?t=1289233
Should help You to restore to factory state. After You can use any other ways to root(if You want )
PS: From what You say, You haven`t done anything irreversible yet. So calm down reread the forum and go on
Thanks for the reply! I did come across that at one point but didn't try it. But I will give it a go once I get the nook charged (it discharges by the end of everyday while having this prob so I have to charge it back up everyday). These directions look pretty straight forward though, so I am crossing my fingers.
"I did not do a backup before trying to root...besides that I don't know how to do it and don't know if it would help in this situation anyway."
After you get your Nook back to stock state don't shy away from making the backup. And do it before you make any other changes. Having a pristine image of your Nook's original state will make you nearly bulletproof. Give yourself time to understand the issues involved in making the backup. This new knowledge will generalize to other aspects of rooting.
The instructions for making the backup are here but you may find this isn't enough information. I found this post from Renate extremely helpful.
Finally, it will be helpful to know that, done correctly, your Nook v.1.1.2 backup will be exactly 1,958,739,968 bytes.
Efemmeral said:
Finally, it will be helpful to know that, done correctly, your Nook v.1.1.2 backup will be exactly 1,958,739,968 bytes.
Click to expand...
Click to collapse
Depend on nook memory chip used (manufacturing date) it should be either 1,958,739,968 or 1,962,934,272 bytes
ApokrifX said:
Depend on nook memory chip used (manufacturing date) it should be either 1,958,739,968 or 1,962,934,272 bytes
Click to expand...
Click to collapse
Yes? I have always gotten 1,957,616,640.
Hmm, mine is 2.000.683.008.
EDIT: I think that was 1.1.0 (or 1.1.1?)
Hi,
I am starting this thread hoping to find a solution to backup the working tablets so we will be able to revive them despite the kill switch being triggered.
The only solution so far seams to be by using nvflash in apx mode.
So far I have managed to boot my tablet in APX mode, but I have not done any other testing.
The tablet (still not killed one) is recognized by computer as being in APX mode.
Requirements:
1. Rooted tablet
2. Terminal app from Google play
Commands issued for APX mode:
1. Open terminal app and write "su" followed by enter to get root
2. Write "reboot" and press enter while keeping the volume up key pressed
Let's continue!
OP's 2nd post deleted - no need for it. Just edit Post #1
LenAsh said:
OP's 2nd post deleted - no need for it. Just edit Post #1
Click to expand...
Click to collapse
where are or name from other post, this thread is very important for us research and i think could useful.
thanks for advance.
I just received my replacement tablet a few days ago. My device has never been rooted or anything prior. I turned on the new device and started using it. I went back to my old device (connected to wifi and everything) and it still boot and i was able to use it all night. 2 days later I tried to use it and it powered on and everything was fine. I just rooted the mofo and installed a custom rom. I never seemed to have received the "kill switch"
The note in my package said to dispose of the device. So... I guess I now have 2 shields. My battery has never gotten warm, I dont use it very often though.
JuStAdsor said:
Hi,
I am starting this thread hoping to find a solution to backup the working tablets so we will be able to revive them despite the kill switch being triggered.
The only solution so far seams to be by using nvflash in apx mode.
So far I have managed to boot my tablet in APX mode, but I have not done any other testing.
The tablet (still not killed one) is recognized by computer as being in APX mode.
Requirements:
1. Rooted tablet
2. Terminal app from Google play
Commands issued for APX mode:
1. Open terminal app and write "su" followed by enter to get root
2. Write "reboot" and press enter while keeping the volume up key pressed
Let's continue!
Click to expand...
Click to collapse
I don't really understand the issue here, can you confirm that the tablet is still active cf. not hit by the killswitch? Why would you get an apx connected message? On a working tablet you would be directly send to an adb/fastboot interface? Usually only the killed tablets would be recognized as apx when you then connect it to a pc.. People are looking for a solution on how to nvflash via apx mode, which is an nvidia proprietary protocol and probably won't be pushed any time soon, if ever.. Possible solutions are moving to linux at the moment, where people try to connect their bricked tablets in apx mode hoping that linux would recognize the drivers, eventually, and maybe use open source universal flashing tools to recover their bricked devices..
doomedromance said:
I just received my replacement tablet a few days ago. My device has never been rooted or anything prior. I turned on the new device and started using it. I went back to my old device (connected to wifi and everything) and it still boot and i was able to use it all night. 2 days later I tried to use it and it powered on and everything was fine. I just rooted the mofo and installed a custom rom. I never seemed to have received the "kill switch"
The note in my package said to dispose of the device. So... I guess I now have 2 shields. My battery has never gotten warm, I dont use it very often though.
Click to expand...
Click to collapse
Yes, your tablet is still alive because you flashed another rom (and that's exactly what you should do to be sure to never get hit by the kill switch) - it is very likely that the kill switch isn't triggered immediately, and than the silent update might not hit immediately neither, you're very lucky, most of the people were hit in very few hours, they couldn't even get their research done before the trigger - that said: the best way is to root the old tablet before setting up the new one, and deleting tegraota.apk and its parent directory - as explained in bogdacutu's thread in this very forum, and/or flashing a new rom to not have any nvidia apps anymore.. You can do both if you even use multirom port for nvidia shield tablet.. I can manifest that all this is working since i did it - i tryed it all and do have 2x tablets now like many others too
This isn't cool man, why steal from Nvidia? Or from anyone. Stealing is not OK.
Sent from my SM-N910T
not stealing XBlack, my tablet was getting hot before recall...I did researched and spent time and efforts to fix the issue which i did. Nvidia sends new tablets to cover their ass for potential law suites in case of a situation happening again. Specifically states to dispose or return and why return if they will dispose for you? Why dispose of a tablet when the user fixed it by the user community. Is it taking advantage YES, we are smart people, we fix it. It was their choice to send new tablets without having to receive old ones prior. In no way is it stealing, tucking it in my pants and walking out of a Best Buy or FRYs without paying for it is stealing. We as a community with fixed tablets can be looked at as beta testers who get to keep their prototype and are given a NEW updated consultation model. Pretty much sums it up you can look at it in any way you like but we as a smart community in no way are criminals that steal from NVIDIA. Thanks NVIDIA i will forever be a loyal customer who buys your products since i think they are great. thank you for my new updated tablet.6
The problem is if you "fix" the tablet and then give it to else, and it catches fire, will nvidia be liable? They want the defective devices off the street, not disassembled and reassembled with non spec parts by potentially incompetent consumers.
Sent from my HTC M9 using Tapatalk
I have read every single thread that exists on the internet about this problem, the bootloops, the faulty bootloaders, the wrong rooting and image installations, every single posible way to brick this piece of device that everyone seems to have problems with. Yet none of them has gave me a solution. First of all, it's my girlfrinds tablet, she told me that one day, she tried to upgrade the android software and while it was installing it, the tablet bricked. She was able to go to fastload mode (power + volume up) we've tried recovery mode, factory reset, every option there, nothing. She gave me the tablet, I plugged it on my pc and used Nexus Root Kit to install a new android software to the device. After a painful search of how to make the Kit recognize the tablet because usb debugging was not on, I was able to start the process of installing the new software. Yet, in the middle of the installation, the micro-usb moved a little bit and the tablet got disconected. The process was cancelled and the tablet screen froze. I turned the tablet off and that was when it just bricked and never wanted to turn back on. Neither with any combination of the buttons, nor while leaving it charging a long time, nor any possible solution the internet may have about this. Just fully totally and simply bricked. Yet, when I connect it to my pc (windows 7 ultimate 64 bits) sometimes, it reads it as an unknown device, sometimes it reads it as a random APX device, and when I install any kind of drivers that already exist on every thread that there is about it, it reads it as an ASUS Transforme Prime APX Interface, yet the tablet never displays anything, and I'm not able to access it in any way nor make any changes to it whatsoever. I live in a country were there is no google or asus techical support, and third-party technical supporters are dumb as f***. My girlfrind took the tablet to 2 other places before giving it to me and they said to her that "it didn't have any software installed" (which was wrong) and that "it was beyond repair" (which was also wrong). The only thing I want to know is: is there any way to fix it now? or do I just have a very nice and fancy paperweight in my hands.
Makatown said:
I have read every single thread that exists on the internet about this problem, the bootloops, the faulty bootloaders, the wrong rooting and image installations, every single posible way to brick this piece of device that everyone seems to have problems with. Yet none of them has gave me a solution. First of all, it's my girlfrinds tablet, she told me that one day, she tried to upgrade the android software and while it was installing it, the tablet bricked. She was able to go to fastload mode (power + volume up) we've tried recovery mode, factory reset, every option there, nothing. She gave me the tablet, I plugged it on my pc and used Nexus Root Kit to install a new android software to the device. After a painful search of how to make the Kit recognize the tablet because usb debugging was not on, I was able to start the process of installing the new software. Yet, in the middle of the installation, the micro-usb moved a little bit and the tablet got disconected. The process was cancelled and the tablet screen froze. I turned the tablet off and that was when it just bricked and never wanted to turn back on. Neither with any combination of the buttons, nor while leaving it charging a long time, nor any possible solution the internet may have about this. Just fully totally and simply bricked. Yet, when I connect it to my pc (windows 7 ultimate 64 bits) sometimes, it reads it as an unknown device, sometimes it reads it as a random APX device, and when I install any kind of drivers that already exist on every thread that there is about it, it reads it as an ASUS Transforme Prime APX Interface, yet the tablet never displays anything, and I'm not able to access it in any way nor make any changes to it whatsoever. I live in a country were there is no google or asus techical support, and third-party technical supporters are dumb as f***. My girlfrind took the tablet to 2 other places before giving it to me and they said to her that "it didn't have any software installed" (which was wrong) and that "it was beyond repair" (which was also wrong). The only thing I want to know is: is there any way to fix it now? or do I just have a very nice and fancy paperweight in my hands.
Click to expand...
Click to collapse
Hello,
Thanks for using XDA Assist.
Your thread will be moved to Nexus 7 Q&A,Help and Troubleshooting.Experts there may be able to help you
___
v7
XDA Assist
Ha, yes...same boat and similar situation happened where USB became disconnected during bootloader flash. Surprised there haven't been any snarky comments made on your (and now my) situation. I have a totally non-responsive device now and Windows is also not recognizing the USB device (because it does not respond back when attempting to connect/mount). Looks like the only magic at this point would be cracking open and trying a completely different path to restoring, otherwise it is time to find a nice door needing a doorstop!
~Dubhead
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.