[Miscellaneous Android Development] xpmule:
This is driving me nuts !

A1-830 tried a looooooot of kits etc.

I get to reboot and waiting..

Ya ya.. the drivers i know,

I tried installing and re-installing etc and..

I also see a couple people apparently stumped on XDA with this and a HUGE amount on Youtube.

Thing is..

I have already been using Fastboot / adb on my Moto phone and that worked fine.

I have done a slew of advanced thing on my Moto phone using those to programs (as well as mfastboot)

But i am getting stone walled and denied hard here and a LOT of others are too.

All i have heard on rare occasions is "make sure the drivers are installed properly" and that is it.

I doubt anyone will post back here for me but if i figure it out i will post back.

And yup usb debugging is checked etc.. it is auth'd.

I get a good MTP connection and can run adb on it no problem.. it;s the fastboot part which is the problem.

And i am pretty sure that has a different driver.. which is the actual root of my problem here.

I'd give up but sooo many A1-830 users claim it worked so.. wish me luck LOL

Oh and i had Windows 7 crash a few times on my as i plug it in too. (no useful msg in EventViewer)

I have Driver enforcement killed permanently too.

EDIT:

Ok i got it..

So i let it fail again so i could get it into the bootloader mode.. i don't know how to launch it with the buttons.

Then in my Windows 7 device manager i could see the yellow flagged device.

So i selected "browse my computer"...

Then i selected "Let me pick"...

There was 6 items for me to choose from.

I also had previously removed any other phone drivers i could find in my add/remove programs menu on windows (uninstalled the Mototola ones)

In an effort to clean up then i installed the drivers earlier from "myKIT_BATCH"

So i am trying to say my actual ADB drivers could have come from that or one of my other installers i have used (drivers stay even though you remove the installers)

Ok so following me still ? LOL

I have now 6 items listed.. 3 signed and 3 not.

I chose to test on a Motorola phone this manual install first to see if it worked because i did not want to have problems with that instead..

The one i chose to manually install was the 2nd item listed called "Android Bootloader Interface"

Then i tested it with the Moto phone and it fastboot listed my device :)

So next i went and let the Acer fail with waiting and sit on the Bootloader screen..

Then i went and manually installed the same driver for the Acer now.. bingo !

It loaded CWM right away :)

But i noticed using "IntelAndroid-FBRL-07-24-2015" i was having some sketchy button issues navigating.. when i hot power to select an item it was turning it off on me.. so i tried "myKIT_BATCHv1.1.2d_PATCHKIT"

https://xdaforums.com/showthread.php?t=2681783

Then followed "Guide 1" here.. https://xdaforums.com/iconia-one-8/how-to/guide-root-acer-iconia-tab-8-a1-840fhd-t2933317

I used SuperSU 2.79 Stable "UPDATE" (not beta)

When i loaded it from CWM i said it installed fine and i checked it and rebooted and checked again and it reports ok with RootChecker Pro & RootExplorer.

https://www.supersuroot.com/download.html

That is the link to get the newest SuperSu.

So thanks SocialGenius LOL (and the other guy Shreps who made the other guide)

To make this real clear.. you need a different driver for windows loaded depending on whether you are actively running Android or it's in BootLoader mode.

So you can put the device into the Bootloader menu screen then go to the file location on Windows then hold down shift and select open a command prompt..

Enter "fastboot devices" to test if it's good.

It should show you a serial number then say devices.

It will NOT if Android is running !

You can run ADB commands though while Android is running.

EDIT:

My point was it's hard to install the ADB driver unless it's showing the right thing to windows.

Get it ?

If android is up & running it has no need or use for the fastboot driver and it won't be seen etc.

So you NEED to get the Tablet into Bootloader mode so Windows will see it as a totally different device... what i think a lot of us are having is a problem with only the 1 driver being setup properly and not BOTH !