yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] Enrichman:
Hi everyone!

I'm having some issues on trying to root my B1-A71. I'm on a Mac and if I do "sudo ./toolkit.sh" and follow the instructions I will get

Trying to establish ADB Connection...
bin/posix/64/adb: bin/posix/64/adb: cannot execute binary file
E: Couldn't connect to your Acer Iconia B1-A71 over adb. Plug-In the device with USB-Debugging Mode turned on.

Of course I've turned on the usb debugging.

If I try to run directly the adb file under the bin/posix/64/ I run into the same error. Btw my adb (on my sdk) is working fine and I can "ping" my device.

Do you think it's safe if I replace the adb (under bin/posix/64/) with my adb? Or it's a modified one?

Thanks in advance!

EDIT:

do you know what the @ means near the permissions (-rwxr-xr-x@) ? I found that in the "corrupted" adb.
[Miscellaneous Android Development] entonjackson:
Yes. It's safe. Some Linux Users had this problem before.
[Miscellaneous Android Development] Enrichman:
Thanks, now the error is just this (lol):

Trying to establish ADB Connection...
E: Couldn't connect to your Acer Iconia B1-A71 over adb. Plug-In the device with USB-Debugging Mode turned on.

I've tried to run the toolkit with -d (or --debug) but nothing happened (no log or increased verbosity, from the code I guess I should expect the second). What do you think could be?
[Miscellaneous Android Development] Enrichman:
In the end I've ended up to do it on Windows (thanks Parallels). It worked without any problem! :)

Thanks a lot, great script! ; )
[Miscellaneous Android Development] entonjackson:
Try to do a manual sudo ./adb devices and look if your device is recognized.

If not, ... your device is not recognized.

Missing drivers? Try other usb plug?
[Miscellaneous Android Development] alessiof89:
Update software

A friend notified me a software update (improve touch sensitivity) but I can't update because root. So, I've tried unroot but dont'work with toolkit. After remove Superuser and Supersu, Iconia Tab is again root. How is it possible? :eek:
[Miscellaneous Android Development] entonjackson:
which iconia do you have?

b1? a1?
[Miscellaneous Android Development] alessiof89:
a1-810
[Miscellaneous Android Development] entonjackson:
as the 1st post tells you. if you cannot unroot the usual way, flash back the stock system image...
[Miscellaneous Android Development] alessiof89:
I've tried but doesn't work:
[Miscellaneous Android Development] entonjackson:
Ok. This tells me, that unroot has a bug.

But never the less, you didn't flash back the stock system image.

on 1st post their is a download link to stock system image.

Download that image, put it in system_image folder and choose option "root" in toolkit.

Edit: I just looked at the code. I already fixed that bug. You should download v0.6.1 again.
[Miscellaneous Android Development] alessiof89:
Ah.. ok. I have download the stock system image, put in system_image folder, remove previously system image and choose "unroot". So, If i want unroot the tablet i have to choose "root" option? I don't understand.

I want to unroot for system update kernel 3.4.5 versione build acer AV052 a1 1.077

immagine rv18rc07WW gen1﻿. Do you have more information about this update? I need root but I'm so curious of this update. There aren't any news in internet compared to this update...
[Miscellaneous Android Development] entonjackson:
dude... this is a workaround. if the usual unroot doesn't work. if you're that clever, change my source code and and delight us!
[Miscellaneous Android Development] alessiof89:
why do you angry? I want only understand.

Nobody have received system update notification?
[Miscellaneous Android Development] blito:
Hi i received an notification znd my tablet is not rooted

Envoyé depuis mon GT-N7100 avec Tapatalk
[Miscellaneous Android Development] mrSpinx:
Hi, i have unrooted the device, flashing the unrooted image in the first post, after that i have updated without no problem.:good:

The touchscreen is now more responsiveness
[Miscellaneous Android Development] alessiof89:
I try now with "root" option
[Miscellaneous Android Development] entonjackson:
Can anybody please provide a rooted system image for the new firmware? so others can root the new firmware.

and also, what was the first firmware version?
[Miscellaneous Android Development] alessiof89:
I update software :) The firmware version is this:
[Miscellaneous Android Development] entonjackson:
what was it before the update?
[Miscellaneous Android Development] alessiof89:
this: https://lh5.googleusercontent.com/-...24-h565-no/Screenshot_2013-06-24-19-33-22.png

Old: 1.039 Now: 1.077
[Miscellaneous Android Development] sodaFR:
In Eastern Europe, the update is Acer_AV052_A1-810_RV18RC07_WW_GEN1 (RV03RC08 before)

This update clear all SUID flag for unallowed binaries in mmcblk0 area.

The method to root is still functional. Tonight, I will provide system.img with pre-installed

working

superSU

Edit: RV18RC07 already available on the first post... then no need to waste my bandwith :)
[Miscellaneous Android Development] min-dfreak:
No, it is not available. (Only placeholder without link)

Can you please upload your prerooted Image ?

Thanks!
[Miscellaneous Android Development] NemoKOF:
So after update root will be 100% functional with system rw access?
[Miscellaneous Android Development] stu667:
No
[Miscellaneous Android Development] sodaFR:
Oops

Ok then... upload in progress
[Miscellaneous Android Development] entonjackson:
To prevent from losing root through update, you could use OTA Root Keeper.
[Miscellaneous Android Development] NemoKOF:
So we still need some kind of modified kernel to allow system partition write? Or is there any other way to do that?
[Miscellaneous Android Development] entonjackson:
OTA Root Keeper is only a way to save your root before losing it through an update. it doesn't change anything in the su binary or even kernel.
[Miscellaneous Android Development] sodaFR:
Image version : Acer_AV052_A1-810_RV18RC07_WW_GEN1

Build number : Acer_AV052_A1-810_1.077.00_WW_GEN1

pre-installed :

working

modified SuperSU (v1.34)

as you can see at the bottom, you can enable/disable the su binary (then you can upgrade from OTA)

system.img.gz - 517.5 MB
[Miscellaneous Android Development] cakadut:
How to Change Logo "ICONIA"

Hi ....

it is possible to change Boot Logo.

I want to change "Iconia" Logo with any thing else....

Thanks in advance..
[Miscellaneous Android Development] entonjackson:
Yep, you can do a lot of funny things with the ROM Toolbox.
[Miscellaneous Android Development] cakadut:
Thanks I have Done,

Using "image Search Editor"

Regards,
[Miscellaneous Android Development] cazza88:
Iconia rooted without problem! :good:
[Miscellaneous Android Development] entonjackson:
New version v0.3.1 is up.

Dialer app no more needed, thanks to bullbrand and pawitp! :good:
[Miscellaneous Android Development] bullbrand:
i found the image.version listed in the system/build.prop file and tried a adb pull and it pulled it so

i dont think it requires root to check it

could something like this be added to prevent users trying the tool without following the required prerequisite outlined

i know this searches for a given string and returns yes or no would stop the boot loop issue

if not string_found:

print("E: The line 'ro.build.pandora.id=Acer_AV051_B1-A71_RV05RC05_WW_GEN1' wasn't found in /system/build.prop.")

sys.exit(1)

another image.version

if string_found:

print("E: The line 'AV051_B1-A71_RV04RC04_WW_GEN1' was found in /system/build.prop.")

sys.exit(1)

then warn they need to OTA upgrade first ??
[Miscellaneous Android Development] entonjackson:
You're awesome! Thanks a lot, helping me getting this tool better and better! I will add it today or tomorrow.

My girlfriend is getting her Huawei Ascend P1 and of course I can't leave it with the stock Rom :cool:
[Miscellaneous Android Development] entonjackson:
New version v.0.4.0 is up.

Now you lazy guys can really sit back and push the button from the distance :cool:

Throw away your ex Dialer and contacts app, because the only purpose for it, to dial the engineer mode, is gone.

Also you won't need to start the telnet server manually anymore. All is done automatically, just watch the magic flow.

Also I'm checking now if your firmware version is up to date, so you won't get a bootloop afterwards.

This release wouldn't be possible without bullbrand and pawitp, so don't hesitate pushing their thanks buttons until your screen burns.

Thanks a lot! you guys are brilliant! :good:
[Miscellaneous Android Development] arif41:
how about adding feature like "Deodex" ?
[Miscellaneous Android Development] entonjackson:
Good idea, i will take it on my todo list.

Restore odexed state would make sense.
[Miscellaneous Android Development] firazka:
Dear Eaton,

thanks for your work....

after dowbload and runToolKit] Acer Iconia B1-A71 v0.4.0 ***New: Super Auto Root*** , still found same problem.

No Progress bar during copy image.

and system shown

Checking firmware version.

1476 KB/s (4537 bytes in 0.003s)

Firmware version 'RV05RC05' installed.

Make sure folder 'system_image' contains a prerooted system.img.gz

Press Enter when you're ready to continue...

Copying rooted system.img.gz onto Acer Iconia B1 (This will take 1-2 minutes)...

cannot stat 'system_image/system.img.gz': No such file or directory

Traceback (most recent call last):

File "easy_root_iconia_b1.py", line 652, in <module>

main()

File "easy_root_iconia_b1.py", line 79, in main

win_root()

File "easy_root_iconia_b1.py", line 294, in win_root

push_system_image()

File "easy_root_iconia_b1.py", line 599, in push_system_image

out = subprocess.check_output(adb + "push system_image/system.img.gz /cache"

, shell=True)

File "subprocess.pyc", line 575, in check_output

subprocess.CalledProcessError: Command 'bin\windows\32\adb.exe push system_image

/system.img.gz /cache' returned non-zero exit status 1

Note I am using windows 7ultimate.- 32 Bit

Regards,
[Miscellaneous Android Development] entonjackson:
Your system.img.gz is missing
[Miscellaneous Android Development] firazka:
what must i do :confused: where i can find system.img.gz?
[Miscellaneous Android Development] entonjackson:
Download link is in the 1st post. download it and put in in folder system_image.
[Miscellaneous Android Development] daniel910821:
U, this tool it's really useful. Thank you.

I just want tank now if you could port this: http://xdaforums.com/showthread.php?t=1780970 I have seen the tablet UI on smaller screen resolution (800x480)

Thanks again for your work

Enviado desde mi B1-A71 usando XDA Premium HD app
[Miscellaneous Android Development] wide_n:
Dear Eaton

thanks for your work

My Acer Iconia B1 is now rooted,I take a pin and press the reset button,but the device keeps restarting after a few seconds
[Miscellaneous Android Development] firazka:
i was download that file with size 359,76kb winrar and disc image file with size 627,712kb but it's still error...

and the text is same with the older that i 1st post

pls give me a solution...

thx....
[Miscellaneous Android Development] entonjackson:
Don't extract the system.img.gz... just place it in the system_image folder.
[Miscellaneous Android Development] bullbrand:
jelly bean 4.1.2 released for B1 downloading it now will check if its still got the needed files in it

to enable root .

in the 1st post

File Description

1.Add Acer widget.

2.Enhance support language.

3.Updated version:4.1.2

size 305.6 meg
[Miscellaneous Android Development] entonjackson:
Thanks.

Can I put this on the 1st page?

is this binary giving RW access for /system ?
[Miscellaneous Android Development] sodaFR:
Of course you can...

It does not fix the RW issue

Let me explain where the problem is

Every application can mount /system with RW permissions but the kernel only allows THAT specifical application to write in system partition. Only the the process who remount /system with RW permissions can write into.

For the others application, the /system partition is always RO; they need to remount RW to gain that possibilty

Sorry if I am not very sharp or clear... I have trouble in writing in english

Edit: I am trying to write a workaround where mount/busybox/toolbox are just a script who call the correct binary with the good syntax... stay tuned
[Miscellaneous Android Development] NemoKOF:
I replied to wrong post. I meant can we have access to system after rooting new firmware. Or still this action will be blocked on our devices. I just love my Acer but I wait for this feature. Your software is very nice, I just read that Acer makes some kernel changes to prevent mounting /system with write permissions. I'm not a developer so I cannot alter the kernel, also I don't know if it's possible on device with locked bootrom.

We are waiting, that's great news! Maybe then we will be able do some magic on our devices :)
[Miscellaneous Android Development] mrSpinx:
I tried to flash the new system.img, but When the toolkit try to connect to devices it say "Could not connect to your A1-810 over adb. plug-in device with the USB Debugging Mode turned on."

if i run manually in cmd "adb devices" it is here "KNKJPFS8MV5H6P9H device"

I have the A1-810 with the latest ota update "RV18RC07"
[Miscellaneous Android Development] entonjackson:
Could it be that acer updated the device name with the newest update? because i heard this issue from multiple users now.

Before the update it worked with the device name from Acer Iconia B1-A71.

Can anyone confirm? I don't own one.
[Miscellaneous Android Development] min-dfreak:
What do you mean?

EDIT: Yes it is different.
[Miscellaneous Android Development] sodaFR:
yes I can confirm that the device number is different for everyone who made the update

For me, I get this :

List of devices attached
MJAQEYGE6HIRYTAM	device

then check_adb() is the problem
[Miscellaneous Android Development] min-dfreak:
So we have to change it manually?

Open .toolkit.py go to line 1281 and replace "0123456789ABCDEF" with our device? (Only for Linux)

Or what we have to do?
[Miscellaneous Android Development] sodaFR:
Correct...

There is 2 choices :

1- change the hardcoded value to your (that is printed when you type adb devices)

2- comment check_adb() everywhere it is called for a1

First choice is faster :)

But please, if you are not sure of what you are doing, wait for Anton and his next version of his tool
[Miscellaneous Android Development] min-dfreak:
Okay, but this works only for Linux right?

Should be easy, will try it.

EDIT: It works now.

EDIT: Your version works great. Will try some apps.
[Miscellaneous Android Development] paugustin:
Hi same error here with a new A1-810 running RV18RC07.
[Miscellaneous Android Development] sodaFR:
You have a clue on the previous page :)

Since the update, the adb ident differs then the script needs to be updated or... just edit .toolkit.py as explained page 79 :)
[Miscellaneous Android Development] entonjackson:
This doesnt work for executing the .exe. I will upload a New Version tomorrow.
[Miscellaneous Android Development] paugustin:
Thanks entonjackson !

btw Acer has released an B1-710 that seems very similar to the B1-A71 but with a different ROM of course. What would you need to make your tool compatible ?
[Miscellaneous Android Development] sodaFR:
Hello folks

I just finished to upload a new system image with a /system RW workaround

Titanium Backup (v6.0.5), SuperSu (v1.41) and busybox (v1.17.2) are installed and are untouched and fully functional.

To have Titanium Backup working well, you need to force the use of system busybox in the Preferences.

FX File Explorer + root addon (boh are free) works

Ad Away works ... etc ...

Apk with their own binaries (ie Titanium Backup) won't work but if we can enable the use of system's busybox (ie Titanium Backup) :)

As usual, there is a risk as it is a modification of the system partition. Use it at your own risk. I am using this trick since 2 weeks without problem. Feel free to modify/update the script. Maybe an APK why not ?

YOU MUST HAVE ALREADY DONE THE UPDATE TO RV18RC07 BEFORE INSTALLING THAT IMAGE

If you install that image, I have to recommand you to do a factory reset before and of course a reboot after installation

here is the link (md5 = c33dd172895690a1afcf78a422eb96a7)

To Anton, if you want to, you can push the script from your toolkit.
[Miscellaneous Android Development] entonjackson:
Thanks for your work, sodaFR.

But I don't think it's legal to include paid apps into the system image. Could you please remove the link and upload a new version without paid apps?

The same also for SuperSU, if it's the paid version.

Sorry, but that's the rules of XDA.
[Miscellaneous Android Development] sodaFR:
There is no paid application

Both are given without licence key or pro apk; busybox has been installed from free app and I just manually generated the correct symbolic links.. Nothing illegal then...
[Miscellaneous Android Development] yurimura:
Is there an estimate when will be an update on this excellent toolkit, for those who did the OTA update, and now can’t run the toolkit because the adb device ID changed? (In this case, for the .exe, ie, for those working on Windows)

Thanks!
[Miscellaneous Android Development] entonjackson:
Some people here report their device name is "MJAQEYGE6HIRYTAM" now.

Some have "KNKJPFS8MV5H6P9H".

I could accept all three names, including "0123456789ABCDEF".
[Miscellaneous Android Development] yurimura:
On my case, after running the toolkit with -d, I can see that the ID seems to be: H6DUNB89LFQWOZ4H
[Miscellaneous Android Development] entonjackson:
wtf?

how can it be that the same device has so much different IDs?

Are we all talking about A1-810?
[Miscellaneous Android Development] yurimura:
Yes, I am talking about the A1-810, with 16gb. I bought it a week or so, and I'm from Europe (Portugal).
[Miscellaneous Android Development] entonjackson:
I released.

v0.6.2

======

- A1-810: Supporting new device names after update to RV18RC07. Following device IDs are known: 0123456789ABCDEF, KNKJPFS8MV5H6P9H, MJAQEYGE6HIRYTAM, H6DUNB89LFQWOZ4H
[Miscellaneous Android Development] Reno_kun:
My ID is SSQK4DLF59PNUCR8 and the one of my girlfriend is NVTOHEGA55R8M7WO (both tablet bouht at the same time)
[Miscellaneous Android Development] entonjackson:
Ok, i think i figured out, what's going on here. I assume Acer doesn't want their devices to be rooted and therefore generate an own device id for each single device. I could ignore the device ID for owners of the A1-810, but this could be extremely dangerous if different devices are plugged in, which have usb debugging mode turned on and a telnet server running.
[Miscellaneous Android Development] yurimura:
Thank you! I already did try the new version of the toolkit, and its working great. Root checker says it's rooted and I have Paragon NTFS&HFS+ working 100%. Soon I'll try more apps that need root access.

About the adb device ID, is it possible that the ID is somehow randomly generated? On the last post, where Reno_kun says that 2 bought at the same time have different ids... idk, maybe something like that.

And thanks again!
[Miscellaneous Android Development] entonjackson:
Ok i just changed the code for the v0.6.2 to support any device id when rooting the A1-810.

Please beware and don't plug in any other device than the A1-810 otherwise that other device could be bricked under specific circumstances (USB-Debugging Mode activated + telnetd running for localhost with port 1234 (which should be rare...))

have fun.

v0.6.2

======

- A1-810: Since update to RV18RC07 each A1-810 has its own device ID. Therefore up from v0.6.2 any device id is accepted for rooting A1-810. Make sure no other devices are plugged in, when applying my toolkit!

- A1-810: Supporting new device names after update to RV18RC07. Following device IDs are known: 0123456789ABCDEF, KNKJPFS8MV5H6P9H, MJAQEYGE6HIRYTAM, H6DUNB89LFQWOZ4H
[Miscellaneous Android Development] sodaFR:
Anton, maybe you should better do this way

/system/bin/getprop ro.product.model

abd expecting for "A1-810" as return (without quotes)

you can do get the firmware version with this command

/system/bin/getprop ro.build.pandora.id
output = Acer_AV052_A1-810_RV18RC07_WW_GEN1
[Miscellaneous Android Development] entonjackson:
thanks! i will implement this later next week. for now, the v0.6.2 should work.
[Miscellaneous Android Development] min-dfreak:
My id is HEUKNF450BH6NRMB.

Will wait for next version ..

I don't have linux anymore :mad:
[Miscellaneous Android Development] entonjackson:
It should work under windows also.
[Miscellaneous Android Development] sodaFR:
min-dfreak, you do it right now woth 0.6.2

Changelog:

v0.6.2

======

- A1-810: Since update to RV18RC07 each A1-810 has its own device ID. Therefore up from v0.6.2 any device id is accepted for rooting A1-810. Make sure no other devices are plugged in, when applying my toolkit!
[Miscellaneous Android Development] min-dfreak:
Yes but my id has not been added in v0.6.2.

EDIT: Ah okay, i thought that he only added some id's...

EDIT2: No I'm right, he just added a few id's and my is not included.
[Miscellaneous Android Development] entonjackson:
you probably have the old 0.6.2, I have updated the link shortly after release.

Download again.
[Miscellaneous Android Development] Eudemony:
Someone correct me if I'm wrong but it is good that the A1 now has unique identifiers in adb as before using the majority of adb commands from your pc wouldn't work. Haven't been able to test this yet though as my a1 is going in for warranty return after a bootloop.

Also anyone try unlocking the bootloaders with fastboot?

Stock recovery has a fastboot mode or I believe you can use adb with the commands

adb reboot bootloader

fastboot oem unlock

Or maybe just

fastboot oem unlock

While in fastboot mode?

First you have to make sure you have the correct drivers installed while in fastboot .. guides are here on xda.

Try at your own risk, but if bootloaders are UNLOCKED it may wipe your WHOLE device.
[Miscellaneous Android Development] paugustin:
Fastboot oem unlock does not wipe devices. It never did on any of my Acer device so far.

But Acer now always removes this command from its bootloader so chances are out won't work.

Envoyé depuis mon CloudMobile en utilisant Tapatalk 4 Beta
[Miscellaneous Android Development] Eudemony:
Ok.. well it did wipe the data parition on my nexus 7
[Miscellaneous Android Development] Reno_kun:
Toolkit v0.6.2 still doesn't work with win7 x64 but adb recognizes the tablet.
[Miscellaneous Android Development] jareee:
v0.6.2 with new RV18RC07 works great ...

thanks to all DEV's

excelent work:good:
[Miscellaneous Android Development] muvensa:
it says it is rooted but I checked with "Root Checker" and it isn't rooted. :confused:

my device is iconia a1-810
[Miscellaneous Android Development] Eudemony:
I had that happen. Run the toolkit again and it should stick.
[Miscellaneous Android Development] muvensa:
do you mean rooting tab again, for the second time, without unrooting? Right?:confused:
[Miscellaneous Android Development] entonjackson:
Have you intalled Superuser / SuperSU?
[Miscellaneous Android Development] Maw2607:
For me to, same problem under Windows 8 x64.

Envoyé depuis mon GT-N7105
[Miscellaneous Android Development] entonjackson:
I'm fixing it at the moment. Please be patient.
[Miscellaneous Android Development] muvensa:
I installed superuser but no difference:(

---------- Post added at 10:20 AM ---------- Previous post was at 10:08 AM ----------

ohh, finally Root Checker says it is rooted. I have just reinstalled super user and now it's done. :good:
[Miscellaneous Android Development] NemoKOF:
Didn't you use image with preinstalled SuperSU from this thread?
[Miscellaneous Android Development] entonjackson:
Ok, Everybody trying to root A1-810 and having adb error, please download new v0.6.2.

The error should be fixed.
[Miscellaneous Android Development] min-dfreak:
Works now! Thank you :good:
[Miscellaneous Android Development] Reno_kun:
Works here too !! Thank you for your work !
[Miscellaneous Android Development] Maw2607:
It works for me too under windows 7 x64, thanks you very much.