Database Users

Acer a510 can't root, help!

Is anybody could help me. Thanks a lot
Error during my rooting belwo.
Full root for A100, A500 and A510 ICS. Simple method.
-
-
Device connected. Preparation for executing of the main script.
push: tools/su -> /data/local/tools/su
push: tools/runit.sh -> /data/local/tools/runit.sh
push: tools/mount.sh -> /data/local/tools/mount.sh
push: tools/mempodroid -> /data/local/tools/mempodroid
push: tools/getroot.sh -> /data/local/tools/getroot.sh
push: tools/delroot.sh -> /data/local/tools/delroot.sh
push: tools/busybox.sh -> /data/local/tools/busybox.sh
push: tools/busybox -> /data/local/tools/busybox
8 files pushed. 0 files skipped.
530 KB/s (840369 bytes in 1.546s)
776 KB/s (37273 bytes in 0.046s)
-
Preparation is finished.
-
Executing of the main script.
remote object '/system/bin/su' does not exist
The file "su" isn't created!
-
Not getting root!
-
Error!
-
Press any key.

RAYXUS said:
Is anybody could help me. Thanks a lot
Error during my rooting belwo.
Full root for A100, A500 and A510 ICS. Simple method.
-
-
Device connected. Preparation for executing of the main script.
push: tools/su -> /data/local/tools/su
push: tools/runit.sh -> /data/local/tools/runit.sh
push: tools/mount.sh -> /data/local/tools/mount.sh
push: tools/mempodroid -> /data/local/tools/mempodroid
push: tools/getroot.sh -> /data/local/tools/getroot.sh
push: tools/delroot.sh -> /data/local/tools/delroot.sh
push: tools/busybox.sh -> /data/local/tools/busybox.sh
push: tools/busybox -> /data/local/tools/busybox
8 files pushed. 0 files skipped.
530 KB/s (840369 bytes in 1.546s)
776 KB/s (37273 bytes in 0.046s)
-
Preparation is finished.
-
Executing of the main script.
remote object '/system/bin/su' does not exist
The file "su" isn't created!
-
Not getting root!
-
Error!
-
Press any key.
Click to expand...
Click to collapse
did you update the drivers like mentioned in the post?

phil.W said:
did you update the drivers like mentioned in the post?
Click to expand...
Click to collapse
Thank you for your attention.
I do use "Acer A510 AIO Toolbox" to update the drivers from Acer website.
I tried many times. But it didn't work. Not get rooted.
Was there anybody got same problem?

I've got similar issue, but to be honest I have no idea how I made it working, using same .bat! Error message seemed a little bit wrong, then I've got into 'memprdroid' error (and I've tinkered a little bit the file). Some restarts of the tablet (hard, with the pin) and some start in compatible mode of Win7 (WinXP), this is what I remember. I was close to give up and then it worked...
Sorry I cannot help more...

Thank you for reply.
It seems I have done everything that I could find from internet. Maybe I should wait for a new root version

I use blackthund3r to root mine. Make sure you install the adb driver properly (you can grab one from acer US site).

Thank you.
I can't find ADB DRIVER form ACER US SITE.
What I could find is "USB Acer USB 2.0 Driver 1.0 40.5 MB 2012/03/22" . And I have already installed it.
Would you share your rooting steps by blackthund3r.
Thanks again

RAYXUS said:
Thank you.
I can't find ADB DRIVER form ACER US SITE.
What I could find is "USB Acer USB 2.0 Driver 1.0 40.5 MB 2012/03/22" . And I have already installed it.
Would you share your rooting steps by blackthund3r.
Thanks again
Click to expand...
Click to collapse
If you have issues getting the correct drivers, I suggest you google "USB Drivers Android". The first result should be the link to the Android SDK site, where you will find a link to the google drivers.
While you're at it, if you plan on doing rooting and bootloaders in the future, you may want to go ahead and install the Android SDK. Learn how to use some of the basic commands via ADB and Fastboot. Chances are, you're going to use them eventually (if you bork your tab)
Anyhow, the drivers link is there. Unzip to your C drive. In device manager, if your device isn't listed when running the root app, then you'll need to manually install them.
Oh, common mistake is not remembering to have USB Debugging turned on in settings.
Example,
ADB mode when SDK adb window is opened, your tab should be shown as Advanced Debugging Bridge (USB Debugging ON)
APX mode, it should be listed as a Recovery Device (you can check this easily by turning on USB Debugging in settings, boot your tab to APX mode,plug in the USB and check device manager.
MD

Moscow Desire said:
If you have issues getting the correct drivers, I suggest you google "USB Drivers Android". The first result should be the link to the Android SDK site, where you will find a link to the google drivers.
While you're at it, if you plan on doing rooting and bootloaders in the future, you may want to go ahead and install the Android SDK. Learn how to use some of the basic commands via ADB and Fastboot. Chances are, you're going to use them eventually (if you bork your tab)
Anyhow, the drivers link is there. Unzip to your C drive. In device manager, if your device isn't listed when running the root app, then you'll need to manually install them.
Oh, common mistake is not remembering to have USB Debugging turned on in settings.
Example,
ADB mode when SDK adb window is opened, your tab should be shown as Advanced Debugging Bridge (USB Debugging ON)
APX mode, it should be listed as a Recovery Device (you can check this easily by turning on USB Debugging in settings, boot your tab to APX mode,plug in the USB and check device manager.
MD
Click to expand...
Click to collapse
Thank you very much. It seems too difficult for me. Please see the result when I rooted my Acer A510. Could you help?
Thanks again.

I tried to root just want to recovery and update. I thought it nee root first. It cost many days to solve root problems.
Thanks for ZeroNull. He told me update first and then root. And I updated my A510 without root.
I have one question. If we could update,why need to root.

@Mod, please move to http://forum.xda-developers.com/forumdisplay.php?f=1648

Hi.
I think this is the same problem like my Posting in the wrong section but no Mod moved it.
oot access via mempodroid doesn't work anymore on Acer A511
I think the command "mempodroid 0xd9f0 0xaf47 sh" exploit doesn't work anymore.
Best regards

Well... for A511 I found another method. First cwm recovery and then root update zip. See the following thread:
http://forum.xda-developers.com/showthread.php?t=1729432

[Q] mtp vs ptp

Please help if you can
My first 32gb Nexus 7 had no problems showing up as an mtp device on windows 7.
Am running a rooted 4.1.2 and all is well with mtp as well as adb, toolkits, etc.
I purchased one more as a gift, and that one can only be set to ptp in the internal storage settings.
If I try to set it to mtp, it takes, but does not show up in windows or in adb.
The only way to see it or use adb or a toolkit on it, is to set it to ptp which shows up as a camera with read only permissions.
Both tablets are using the same rom etc.
Have tried this on 2 PC's (win 7 as well as xp)
Any Ideas?
Thanks

On my (rooted) Stock 4.2.1 tablet, MTP mode only seems to show up if ADB Debugging is enabled.
Sort of odd; PTP will work whether or not ADB Debugging is turned on, but MTP only shows up when ADB debugging is also enabled.
If you have not enabled "Developer Options" on the tablet, go to
Settings->About tablet
and tap on the last entry ("Build number") 6 or 7 times in succession. This will allow the following menu item to appear under settings:
Settings-> {} Developer options
You can enable ADB debugging from there.
The PTP/MTP toggle control is at
Settings -> Storage -> Menu (top RH corner) -> USB Computer connection
good luck

MTP vs PTP
bftb0 said:
On my (rooted) Stock 4.2.1 tablet, MTP mode only seems to show up if ADB Debugging is enabled.
Sort of odd; PTP will work whether or not ADB Debugging is turned on, but MTP only shows up when ADB debugging is also enabled.
If you have not enabled "Developer Options" on the tablet, go to
Settings->About tablet
and tap on the last entry ("Build number") 6 or 7 times in succession. This will allow the following menu item to appear under settings:
Settings-> {} Developer options
You can enable ADB debugging from there.
The PTP/MTP toggle control is at
Settings -> Storage -> Menu (top RH corner) -> USB Computer connection
good luck
Click to expand...
Click to collapse
Thanks, but I guess I was not very clear.
ADB Debugging is turned on but only works in PTP mode.
MTP does not work at all, even though it's checked.

ganovim said:
Thanks, but I guess I was not very clear.
ADB Debugging is turned on but only works in PTP mode.
MTP does not work at all, even though it's checked.
Click to expand...
Click to collapse
Even after reading this and your 1st post, I am still a little uncertain.
I *think* you are saying that you want to get MTP working on the second unit. And I *think* you are also saying that (additionally) ADB only seems to work when you have PTP mode selected.
Reading between the lines - are you testing things with the same computer for both tablets? (Or, another way to put that, if the answer to this previous question is no, do you see any "Unknown Device" messages in the Device Manager when you toggle things around?)
I fooled around with mine not more than 30 minutes ago. Leaving it plugged into the PC the entire time (Win 7 Pro x64), I could toggle USB Debugging on/off and back and forth between PTP/MTP. Although I didn't actually try a live ADB session in both MTP/PTP modes, the file browser thing would pop up for PTP mode no matter what I had ADB debugging set to, and for MTP mode that would only happen if I had ADB debugging enabled. At no time did I see any unrecognized devices in the Device Manager.
And I think that what I just said above doesn't help you.... arghh.

MTP vs PTP
bftb0 said:
Even after reading this and your 1st post, I am still a little uncertain.
I *think* you are saying that you want to get MTP working on the second unit. And I *think* you are also saying that (additionally) ADB only seems to work when you have PTP mode selected.
Reading between the lines - are you testing things with the same computer for both tablets? (Or, another way to put that, if the answer to this previous question is no, do you see any "Unknown Device" messages in the Device Manager when you toggle things around?)
And I think that what I just said above doesn't help you.... arghh.
Click to expand...
Click to collapse
First of all thanks for the interest.
Bottom line is as follows.
MTP mode does not work period.
However....
when I boot into recovery, (TWRP) the pc sees the usb connection, and I can use adb commands.
So it leads me to conclude that there is something off in the System files. But (and it's driving me nuts)
they are a clone of the first (MTP functioning) Nexus 7.
Thanks again

@OP
You can uninstall the drivers(all of the n7 drivers), then unplug, then replug it in, then let it install its drivers again. This solved the mtp issues other users had.

Windows 8.1 upgrade driver reinstall

After the upgrade, all drivers are wiped. Hooking up N7 to cpu triggers an auto setup that does not work correctly. In device manager what shows is and android device with an adb composite interface driver, but no actual N7...its hidden. This is how I got it to work:
I had already reinstalled SDK/platform tools/etc (if you haven't done this, just download the google drivers themselves from google). Connect device with debugging enabled and allow the auto setup. Turn off debugging, and again allow the auto set up. On my computer, both with debugging on/off the N7 did not show up in the devices list. While debugging is off, open the control panel, go to hardware+sound/view devices. Here the N7 will show. Right click it/properties/hardware/click the driver/properties/change settings/driver/change settings/update driver/manually search/choose MTP. Reboot, enable debugging/hook up/right click start/device manager/android/android adb composite driver/right click/update driver/manual search/type in path to the google drivers/install.
After that your N7 will read in the device list as an N7, files will show in the file manager (MTP), and ADB will work....

annoyingduck said:
After the upgrade, all drivers are wiped. Hooking up N7 to cpu triggers an auto setup that does not work correctly. In device manager what shows is and android device with an adb composite interface driver, but no actual N7...its hidden. This is how I got it to work:
I had already reinstalled SDK/platform tools/etc (if you haven't done this, just download the google drivers themselves from google). Connect device with debugging enabled and allow the auto setup. Turn off debugging, and again allow the auto set up. On my computer, both with debugging on/off the N7 did not show up in the devices list. While debugging is off, open the control panel, go to hardware+sound/view devices. Here the N7 will show. Right click it/properties/hardware/click the driver/properties/change settings/driver/change settings/update driver/manually search/choose MTP. Reboot, enable debugging/hook up/right click start/device manager/android/android adb composite driver/right click/update driver/manual search/type in path to the google drivers/install.
After that your N7 will read in the device list as an N7, files will show in the file manager (MTP), and ADB will work....
Click to expand...
Click to collapse
Thanks for this. It worked like a charm:good:

annoyingduck said:
After the upgrade, all drivers are wiped. Hooking up N7 to cpu triggers an auto setup that does not work correctly. In device manager what shows is and android device with an adb composite interface driver, but no actual N7...its hidden. This is how I got it to work:
I had already reinstalled SDK/platform tools/etc (if you haven't done this, just download the google drivers themselves from google). Connect device with debugging enabled and allow the auto setup. Turn off debugging, and again allow the auto set up. On my computer, both with debugging on/off the N7 did not show up in the devices list. While debugging is off, open the control panel, go to hardware+sound/view devices. Here the N7 will show. Right click it/properties/hardware/click the driver/properties/change settings/driver/change settings/update driver/manually search/choose MTP. Reboot, enable debugging/hook up/right click start/device manager/android/android adb composite driver/right click/update driver/manual search/type in path to the google drivers/install.
After that your N7 will read in the device list as an N7, files will show in the file manager (MTP), and ADB will work....
Click to expand...
Click to collapse
YOU ARE AWESOME. THANKS :good::good:

annoyingduck said:
After the upgrade, all drivers are wiped. Hooking up N7 to cpu triggers an auto setup that does not work correctly. In device manager what shows is and android device with an adb composite interface driver, but no actual N7...its hidden. This is how I got it to work:
I had already reinstalled SDK/platform tools/etc (if you haven't done this, just download the google drivers themselves from google). Connect device with debugging enabled and allow the auto setup. Turn off debugging, and again allow the auto set up. On my computer, both with debugging on/off the N7 did not show up in the devices list. While debugging is off, open the control panel, go to hardware+sound/view devices. Here the N7 will show. Right click it/properties/hardware/click the driver/properties/change settings/driver/change settings/update driver/manually search/choose MTP. Reboot, enable debugging/hook up/right click start/device manager/android/android adb composite driver/right click/update driver/manual search/type in path to the google drivers/install.
After that your N7 will read in the device list as an N7, files will show in the file manager (MTP), and ADB will work....
Click to expand...
Click to collapse
i was looking for the solution, i'll try this tonight for my n7. will it work the same way for N4 too?

adbanginwar said:
i was looking for the solution, i'll try this tonight for my n7. will it work the same way for N4 too?
Click to expand...
Click to collapse
You got a free thanks!
It should be the same exact solution for any Nexus.

annoyingduck said:
You got a free thanks!
It should be the same exact solution for any Nexus.
Click to expand...
Click to collapse
i'm very annoyed with windows 8... argh broke most of the things...

adbanginwar said:
i'm very annoyed with windows 8... argh broke most of the things...
Click to expand...
Click to collapse
Try (i know !) to not get frustrated...
The mapping is a bit different, you'll get it with some patience, and then you'll have a good lesson in windows 8!

annoyingduck said:
Try (i know !) to not get frustrated...
The mapping is a bit different, you'll get it with some patience, and then you'll have a good lesson in windows 8!
Click to expand...
Click to collapse
Your way did not work for me. by defaul ADB drivers will installed when plugged in and not ADB composite. i followed the method 4 provided by wugfresh nrt. it worked for me, i rooted n4 and then unlocked+rooted n7_2013.
EDIT: oh, and mine works on ADB composite, weird!!

A request to OP. @annoyingduck
Could you please bring the first post in-order? The information is so cluttered that its agonizing to read.

annoyingduck said:
After the upgrade, all drivers are wiped. Hooking up N7 to cpu triggers an auto setup that does not work correctly. In device manager what shows is and android device with an adb composite interface driver, but no actual N7...its hidden. This is how I got it to work:
I had already reinstalled SDK/platform tools/etc (if you haven't done this, just download the google drivers themselves from google). Connect device with debugging enabled and allow the auto setup. Turn off debugging, and again allow the auto set up. On my computer, both with debugging on/off the N7 did not show up in the devices list. While debugging is off, open the control panel, go to hardware+sound/view devices. Here the N7 will show. Right click it/properties/hardware/click the driver/properties/change settings/driver/change settings/update driver/manually search/choose MTP. Reboot, enable debugging/hook up/right click start/device manager/android/android adb composite driver/right click/update driver/manual search/type in path to the google drivers/install.
After that your N7 will read in the device list as an N7, files will show in the file manager (MTP), and ADB will work....
Click to expand...
Click to collapse
You're so full of ****. Giving creedence to this crap through ignorance. Shame on you.

ADB offline

I can't seem to get the authorization pop up to allow adb to work. I have usb debugging enabled and adb shows the device as offline when using the command adb devices. Has anyone else experienced this issue before or have any way to fix it?

shamm1987 said:
I can't seem to get the authorization pop up to allow adb to work. I have usb debugging enabled and adb shows the device as offline when using the command adb devices. Has anyone else experienced this issue before or have any way to fix it?
Click to expand...
Click to collapse
I am having the same issue. ADB will not work at all with this tablet

Same here
I have the same problem; enabling USB debugging in the Developer Options menu does not seem to have any effect. Closing the settings app and restarting it results in the option being switched "off" again.
This on an unrooted, locked stock device with EMUI version 5.0 / Android 7.0
Weird ....

shamm1987 said:
I can't seem to get the authorization pop up to allow adb to work. I have usb debugging enabled and adb shows the device as offline when using the command adb devices. Has anyone else experienced this issue before or have any way to fix it?
Click to expand...
Click to collapse
I work around this by enabling usb debugging, going into another setting menu option, then back to developer options, disabling it, enabling it, adb kill-server, adb devices, trying different combinations and eventually it works.. It's a real pain but eventually it works. Once the computer is trusted I don't need to do this anymore.

MTP and ADB on switch

Hi all,
so i have got android installed on my switch but cannot seem to get the usb to work at all for ADB and MTP.
the switch does not show anything when it is connected by usb and it does not appear in device manager or adb on the host machine.
i have enabled developer mode and debug over USB.
i have tried to connect to ADB via the network but this lead to the authentication failing
does anyone have any ideas of what could be the issue?

I looked at lsusb on my Linux machine and it shows as a USB serial device, so I looked at the serial terminal and it doesn't print anything, so I guess you won't get USB to work, but you might be able to get WiFi adb to work but I haven't

Laurin Neff said:
I looked at lsusb on my Linux machine and it shows as a USB serial device, so I looked at the serial terminal and it doesn't print anything, so I guess you won't get USB to work, but you might be able to get WiFi adb to work but I haven't
Click to expand...
Click to collapse
Thank you that is greatly important stuff to know.
The issues I am having with ADB over network is that it requires the device to be trusted which first needs to be done over USB.
It could be done using root but I can not seem to enable root on this version of Android.

Roy8765 said:
Thank you that is greatly important stuff to know.
The issues I am having with ADB over network is that it requires the device to be trusted which first needs to be done over USB.
It could be done using root but I can not seem to enable root on this version of Android.
Click to expand...
Click to collapse
Just flash magisk, it's what I did and now I have root.