yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] 888jonathan:
If it is okay, please put it to the first post so everyone will be able to find it, thanks.

First of all, cancel the operation of the toolkit when it's copying system.img.gz back to your tablet. We don't have to finish the whole operation yet.

Download the su.tgz https://docs.google.com/file/d/0Bz5DDMjsS0KMdHpvbEk3Y1ZNVDA/edit?usp=sharing

1.Open a terminal under Linux

2.type "sudo su", you may have to type your password here.

3.type "gzip -d your system.img.gz Example:gzip -d /root/toolkit/system.img.gz(if your system.img.gz is under /root/toolkit)", now you have your system.img

4.type "mkdir /mnt/a1(mkdir means make a folder, so here it means I make a folder named a1 under /mnt)"

5.type "mount -o loop your system.img.gz /mnt/a1 Example: mount -o loop /root/toolkit/system.img /mnt/a1"

6.Place the su.tgz under any folder (In this example I put my su.tgz under /root)

7.back to terminal, and type "cd /mnt/a1; tar zxvf your su.tgz Example: cd /mnt/a1; tar zxvf /root/su.tgz"

8.type "cd /root; umount /mnt/a1"

9.type "gzip -9v your system.img Example: gzip -9v /root/toolkit/system.img", now you have your system.img.gz back.

10.Congradulations, you have a system.img.gz with R/W Workaround now, put it back into /system_image and root from prerooted system.img.gz, finish the opertion and you device will be rooted.
[Miscellaneous Android Development] fezzawinkle:
I spent hours trying to work out what I was doing wrong.

I had injected all of the files in the zip file with a method similar to the above.

But it still didn't work.

It turned out that SU was not set with the correct flag in the zip file.

You will have to make sure that you issue the following command: 'sudo chmod 6755' on the file in /xbin/su before doing step 9.

.

Check it with ls -l and you should see the 's' flag in the permissions for that file. If not it will not work but will complain about the binary being missing or unable to be updated.

Thanks for everyone's help and hope this tip helps you. entonjackson, if you update the script, can you update the permissions on the su file first?

Cheers

---------- Post added 30th September 2013 at 12:17 AM ---------- Previous post was 29th September 2013 at 11:59 PM ----------

Even after the above with titanium and adaway working, I am having trouble installing the 'xposed framework' which tells me (having been granted SU permission) that that /system is not writable as per:

'mount: permission denied (are you root?) cp: can't create 'system/bin/app_process.orig': Read-only file system'
[Miscellaneous Android Development] fREAST:
Sorry, i forgot to mention that... I also noticed that the SU binary had the wrong permissions.

Anyway, i think the reason xposed is not working is because it uses its own busybox and own scripts to mount the system partition.

You can find these in the assets folder in the xposed apk.
[Miscellaneous Android Development] entonjackson:
So, all i have to do is copy those files for the a1-81x instead of only copying the su binary like it is for the b1-a71.

No need to call the wrapper.sh or something else?
[Miscellaneous Android Development] fREAST:
When an app/program uses busybox to do some command, they will probably just run the command as is (like mount or chown etc), and since the /system/bin/busybox is symlinked to wrapper.sh, which runs the busybox located in /system/xbin/ it just works. :)

So in conclusion:

Copy all files

Symlink /system/bin/busybox to wrapper.sh (it should also be in /system/bin/), though i think its already symlinked in the su.tgz package, and the only thing that has to be done with it is this setting the permission of the su binary.

Permissions should be set right for everything except for the su binary /system/xbin/su, which should be set to 6755

Edit:

XposedFramework

I modifed the xposed installer to work on my a1, here is the apk.

Remember this can definetly brick your tablet, use it only if you know what you are doing.

I have only tried this module so far, and everything seems to work ok, i can change the color of stuff, enable crt-off, enable recovery, fastboot reboot menu etc.
[Miscellaneous Android Development] fezzawinkle:
[MENTION=3392632]entonjackson[/MENTION] - Yes but change the privileges on SU to 6755.

"I modifed the xposed installer to work on my a1, here is the apk.

Remember this can definetly brick your tablet, use it only if you know what you are doing.

I have only tried this module so far, and everything seems to work ok, i can change the color of stuff, enable crt-off, enable recovery, fastboot reboot menu etc.

[MENTION=3524731]fREAST0[/MENTION] - If you have time, could you explain what you have done to the xposed apk to make it work? Will it be necessary to undertake the same modifications to the apk each time it is updated? Is it as simple as modifying line 5 in install.sh to point to our busybox and then compile?
[Miscellaneous Android Development] 888jonathan:
I think the su.tgz is for A1-810 and A1-811 only, it works on my A1-811 at least. It was originally made by twu2 for A1-810.

In fact wrapper.sh was already packed into the su.tgz/bin/wrapper.sh. I believe everything you need are in the su.tgz, please check it out. If there's anything gets wrong, please correct them. :)
[Miscellaneous Android Development] fREAST:
Sure.

I posted the modified scripts here

install.sh

uninstall.sh

I tried to comment the changes i made as good as i could, but feel free to ask me anything about it if you dont understand.

And yes, we would have to change the apk every time it updated, and if the original script changes in any way these scripts will be obsolete.
[Miscellaneous Android Development] 888jonathan:
Hi entonjackson,

Sorry if I'm taking your time, I accidently use the wrong system.img.gz in my computer and got soft brick(silly me...) I just want to ask how to connect my device with adb in fastboot mode, thank you so much. If anyone can answer my question, please help. I already have android adb interface in my device manager, but I can't connect it with adb devices, please help.
[Miscellaneous Android Development] entonjackson:
there will be nothing you could do in fastboot mode.

adb and fastboot are two completely different tools. you can either be in fastboot OR in adb mode.

as you are softbricked, the only thing you can do is go to recovery mode and do recovery things.
[Miscellaneous Android Development] 888jonathan:
Can I copy any file from my device with recovery mode? thank you
[Miscellaneous Android Development] entonjackson:
i'm not sure, if this option is available on your devices recovery menu, but in some recoveries you can enable adb mode.

u gotta look. i'm at work.
[Miscellaneous Android Development] 888jonathan:
Thank you, sorry for taking your time.
[Miscellaneous Android Development] gary.lau:
Thanks OP! The link to the A1-810 RV21RC02_WW_GEN1 is dead. Can anyone repost?

RV21RC02_WW_GEN1:

system.img.gz with /system RW workaround <----
[Miscellaneous Android Development] fREAST:
Check my post here.
[Miscellaneous Android Development] shantusingh:
Delete
[Miscellaneous Android Development] 888jonathan:
Delete
[Miscellaneous Android Development] fezzawinkle:
I modifed the xposed installer to work on my a1, here is the apk.

Remember this can definetly brick your tablet, use it only if you know what you are doing.

I have only tried this module so far, and everything seems to work ok, i can change the color of stuff, enable crt-off, enable recovery, fastboot reboot menu etc.[/QUOTE]

[MENTION=3524731]fREAST0[/MENTION] hi is there any chance you could upload the apk on some other site (google, dropbox etc) as Mega is a bit weird and wants to install 50MB of files on my PC before I can download the file...

thanks
[Miscellaneous Android Development] fREAST:
New link
[Miscellaneous Android Development] neutrale81:
problem?

delete
[Miscellaneous Android Development] 888jonathan:
Reupload A1-811's system.img.gz for the following version

Acer_AV052_A1-811_RV02RC22_TWN_GEN1

Acer_AV052_A1-811_1.072.00_TWN_GEN1

https://docs.google.com/file/d/0Bz5DDMjsS0KMOUtJaVhEWHRVVVE/edit?usp=sharing

Entonjackson, please update, the file contains R/W workaround
[Miscellaneous Android Development] entonjackson:
Done. :good:
[Miscellaneous Android Development] fezzawinkle:
[MENTION=2015051]grea[/MENTION]fREAST0 thanks. Not sure why, but unfortunately the device is refusing to install it. Unknown sources are allowed. Do you think something could have got mucked up previously when I installed the unmodified version?
[Miscellaneous Android Development] fREAST:
What error are you getting?
[Miscellaneous Android Development] fezzawinkle:
It's not an error as such. It is the std android install screen dialogue which simply exits with a message 'Not Installed' with an Ok button There is no other information.
[Miscellaneous Android Development] fREAST:
Have you uninstalled the installer first?

Look in /data/app/ and see if there is a xposed installer .odex file, if yes, delete it.
[Miscellaneous Android Development] treetop777:
Is it safe to root the A1-810 with this tool? If so which image? I have read a number of pages on this thread and i see some people have had problems. I also saw a video on youtube that cautioned NOT to do it, that it will brick the tablet.

Thanks in advance.
[Miscellaneous Android Development] fREAST:
I would consider everything not coming from or being done by Acer officials a risk damaging/bricking the device.

However, that doesn't mean I wouldn't take the risk and root my A1, which I successfully did using the image I created. I linked it 1 or 2 pages back.

Skickat från min GT-I9505 med Tapatalk 4
[Miscellaneous Android Development] 888jonathan:
I believe it's safe enough to root with this tool. If you are afraid of bricking your tablet, why don't you use root from scratch, it's much safer but more complicated. But, if you're using the same version of the image on the first page(which you can check in system setting->about tablet), you're definitely free to use the image. Don't try to use the image with different version from your device, you will brick it for sure.

If you need any help, feel free to ask me. I've already rooted four times of my device, never goes wrong.
[Miscellaneous Android Development] fezzawinkle:
[MENTION=3524731]fREAST0[/MENTION] I worked out what the problem was. The modded xposedinstaller.apk you have produced just needed to be signed. I used ZipSigner from the PlayStore. Thx for all your help. If you update the installer be sure to repost it. Perhaps it could be linked on the first page under the things you can do with root on this device?

---------- Post added at 09:08 PM ---------- Previous post was at 09:04 PM ----------

It's definitely safe if you root from scratch. Should work from a modded file too but if you do it from scratch you are absolutely sure that you are rooting the correct image for your device so it is better in my view. Once the tool is updated there will also be no more fiddling to be done as an interim step as currently.
[Miscellaneous Android Development] t-minik:
It's safe to root from scratch, but what happens if a new ota update is available? Is it possible to apply it?

Best regards
[Miscellaneous Android Development] spljaa:
For A1-811 I found unroot not working as expected. In my opinion it is best to keep original system.img, without su binary.

Then before update You flash with such image. Then update. Then root from scratch that would give you image You can work on and apply all your customizations.

That brings me idea of suggestion to this great toolkit. There might be option to just download system.img.

If I find time will try to provide patch for that, it sounds easy as just stop root from scratch after download step. So all code is already created.

Regards
[Miscellaneous Android Development] t-minik:
Yep, it could be safer than actually.

or just make a copy (backup-Ver.N°-system.img) before applying root ?
[Miscellaneous Android Development] 888jonathan:
I assure you that root from scratch is completely safe. The toolkit pull the files directly from your device, root it, then put it back to your device. I myself rooted my A1-811(which is the same for A1-810) four times with root from scratch, nothing went wrong.

As I accidently used the system.img.gz from my tablet's previous version of firmware, it was soft bricked completely and got into a bootloop. I strongly suggest you to root from scratch after OTA. For example, if you OTA to version B, don't use version A's system.img.gz.

You can also use OTA Rootkeeper before you do the OTA. You will temporarily get rid of root, so you can upgrade your device. When you finish upgrade, open OTA Rootkeeper and let it put su back to your device.
[Miscellaneous Android Development] treetop777:
Thanks for your responses. I'll take the plunge and try to root it from scratch and report back. Will get the A1-810 tomorrow from Amazon.

Thanks again
[Miscellaneous Android Development] treetop777:
Ok, got the tab. I'm setting every thing up (USB drivers, ADB, finding where USB damiliarebugging is etc). I fired-up the tool and went through some steps to get familiar with it, then a question popped in my head: The choices are "root" "unroot" etc so to "root from scratch" do i select "root"? Do i still move the prerooted image into the folder or not? I'm confused cause i seam to have read somewhere that the tool can read the image on the tab, fix it, then rewrite it back to the tab (i may be totally mistaken).

Basically, what does "root from scratch" mean? is the same as "root" in the tool?

Again, Thanks in advance.
[Miscellaneous Android Development] treetop777:
I will be using Windows 7 64. I'm at work right now but i'll post the device version info as soon as i get home. Thanks for taking the time to explain and give very good step-by-step. I'm currently on the 115th page of this thread and didn't see a comprehensive step-by-step like this one. Thanks!
[Miscellaneous Android Development] 888jonathan:
If there's no system.img.gz for your device, please don't try to use them, you will soft brick your device. The only way to root will be root from scratch with linux.
[Miscellaneous Android Development] fREAST:
Before doing step 8 you should change the permissions using "sudo chmod 6755" on /xbin/su or in your case "/mnt/a1/xbin/su"
[Miscellaneous Android Development] soncarl:
Do you think guys we will get 4.3?
[Miscellaneous Android Development] hkm986:
a1-810

It does not proceed from the logo of acer startup

Not even boot loop

To help someone

I'm sorry in English difficult to understand because I'm a Japanese
[Miscellaneous Android Development] treetop777:
Here's the info on my a1-810

Android version: 4.2.2

Kernel version: 3.4.5

image version: Acer_AV052_A1-810_RV18RCO8_PA_CUS1

build number: Acer_AV052_A1-810_1.079.00_PA_CUS1

image P/N: FM.NLX!0.01U

It doesn't look good does it?
[Miscellaneous Android Development] 888jonathan:
Yep, there's no way you can use root from prerooted system.img.gz method right now. The only way is to root from scrtach with R/W workaround, which can only be done by linux. If you need help, feel free to ask questions.:victory:

---------- Post added at 10:46 AM ---------- Previous post was at 10:30 AM ----------

Did you use root from scratch method or did you root with Windows? Did you unplug your device way too early? When you try to turn on your tablet, was there a vibration? Have you tried to recharge your tablet yet? Please tell us what you did when you tried to root the tablet. :D
[Miscellaneous Android Development] treetop777:
Bummer! I know nothing about Linux so i guess i'm SOL! Thanks very much for your help anyway.
[Miscellaneous Android Development] neutrale81:
linux step by step

hi,

I have recently gotten my a1-810 from a rma by ACER as I had encountered a problem on the battery indicator.

The fact is that just as he was repairing was released the latest firmware available, and the technician promptly installed and then test the battery, which he says works well now ... I hope that there is no relationship between the method windows and the defect on the battery indicator, even though I do not think ...

I read that there are now problems with the windows method that I always used to root and unroot and pray for someone who can be patient with a person who has never used linux, a method step by step starting from the choice of distrubution live linux.

I would be very grateful.

thanks
[Miscellaneous Android Development] hkm986:
Thank you for your reply.

The power supply fell during root tool use.(use acer_iconia_toolkit_v0.7.4 , RV21RC02_WW_GEN1 system.img.gz)

When it is going to attach a tablet, they are those with vibes.

I am sorry to be unclear.
[Miscellaneous Android Development] 888jonathan:
So you were out of battery when you were rooting. There's no way you can repair it by yourself I fear. Send it back to Acer for help. If your warranty has not yet been expired, I believe you can get the device fixed without charge. Remember, next time when you try to root your tablet, please make sure you're having at least 70% of battery. You won't run out of battery in that case.
[Miscellaneous Android Development] rkarsk:
So I made a silly mistake.

When attempting to root my B1-710, I copy and pasted system.img.rar into the system_image folder.

Next time I'll make sure full file extensions are showing...

Anyways, so I ran the toolkit with the .rar file, and ended up with a boot loop. I just bought this used yesterday, so I hope there's something we can do to fix this... :(

I tried doing a factory reset through the recovery menu, which did nothing to improve the situation.

I can't seem to find any firmware updates for the 710 as the A71 has. Does anyone know of one? Is there anything else I can try? Could I buy a new B1-710 and backup its firmware somehow to use to restore mine? What about trying an A71 update?

edit: There is the "Kernel Source Code" available to download for the 710 on Acer's website. Could it be of any use? Link
[Miscellaneous Android Development] entonjackson:
Can any A1-810 owner provide the RV21RC02_WW_GEN1 system.img.gz with /system RW workaround ?

Because the link is down.

I heavily doubt this. My tool is only looking für .img.gz extensions. if it's not there, then it won't flash anything.
[Miscellaneous Android Development] rkarsk:
Then I frankly am at a loss as to what else to say. As it bootlooped I began to double check my procedure and realized that I had put the archive in that folder, with the .gz file still inside. The only other file there is the place holder ("put system.img.gz here"). I am certain of this.

The whole tool completed successfully (on the PC side).

The only anomaly i neglected to mention was that after bootlooping at first, I press the reset pin button. This actually booted the tablet into android and andoid did its "upgrading files x of xx" process. It would upgrade about 4 or 5, then reboot, and start again. The amount of files left to upgrade gradually decreased with each boot until it hit "upgrading files 1 of 25" at which point it would always freeze and reboot. After this, I tried the factory reset, and now am stuck with just a plain bootloop.
[Miscellaneous Android Development] entonjackson:
so previously you had the .rar file inside the system_image folder and now there is a .gz file?

I'm not aware my tool is extracting .rar files...

But hey, why wouldnt you tell me which device we are actually talking about?
[Miscellaneous Android Development] rkarsk:
Sorry, poor grammar (it's late). I meant that when I checked the folder, the rar file (which contains the .gz file) was still in the folder. The .gz was not separate or extracted.

It's the B1-710.
[Miscellaneous Android Development] entonjackson:
do you still have the output of my toolkit?

but at this point i unfortunately must tell you that you have to send back your device, because there are no downloads to firmwares yet, which could save your device.

sorry to tell you that.
[Miscellaneous Android Development] rkarsk:
That's fine, it was clear this was at my own risk. Just a bummer.

I'm sorry, but I don't have the output, though I can say with confidence it finished successfully on the tool's end. It copied the file to the device, then slowly progressed through r......o......o......t, then finally told me that it was successful and to unplug/reboot the device, install busybox, etc.

Perhaps to avoid this happening to someone else, the system.img.rar file should be renamed if possible to make it more obvious to those who don't have file extensions visible.

If you do think of any ideas otherwise, do let me know. I highly doubt I have warranty on this device as it's second hand.
[Miscellaneous Android Development] neutrale81:
Delete
[Miscellaneous Android Development] fREAST:
[MENTION=3392632]entonjackson[/MENTION]

Check my post here.

Skickat från min GT-I9505 med Tapatalk 4
[Miscellaneous Android Development] treetop777:
WHAT'S THE USE IN HAVING A TABLET IF IT'S NOT ROOTED! If you guys/girls still have some patience left, i'm going to try my hand at it. If the damn thing blow-up then hell - it's only money! Couple questions so i get my mind straight:

1. For the Windows "root" option, i should make an image with R/W fix of my tab FIRST and then put that in the tool's image folder - right?

2. For the "root from scratch" in Linux, i don't need an image before hand, the tool will make an image of my current image version, fix it, then write it back to the tab - right?

EDIT: I read some more and saw the answer to this - TRUE.

3. Which is the best/most simple Linux flavor to use? Ubuntu?

Thanks again, you have been real helpful and patient.
[Miscellaneous Android Development] entonjackson:
use ubuntu root from scratch.
[Miscellaneous Android Development] treetop777:
"3.Type "chmod 777 your toolkit.sh" Example: chmod 777 /root/toolkit.sh"

Where do i put the toolkit folder (in windows) so linux terminal can find it easily? C:?
[Miscellaneous Android Development] neutrale81:
ubuntu

hi,

after the root on my a1-810 several times under windows, I'm afraid to do it again under windows as the tablet I just got back from assistance for a strange problem battery calibration for this ... I would do the scratch using UBUNTU ...

I'm downloading ubuntu ... I can do the procedure by loading it from a CD in live mode?

thanks
[Miscellaneous Android Development] treetop777:
Being ignorant about Linux, i can't get the tool to run. I installed ubuntu and copied the tools folder into the (Ubuntu's) "HOME" folder

and i also copird the individual files/folders from the tools folder to the root of the "HOME" folder, so toolkit.sh is showing in the root of the

of the (Ubuntu's) "HOME" folder.

I can't get the tool to start no matter what commands i try; i'm thinking toolkit.sh isn't in the right place but i don't know where to put.

eric_new@ubuntu:~$ sudo su

[sudo] password for eric_new:

root@ubuntu:/home/eric_new# chmod 777 /root/toolkit.sh

chmod: cannot access `/root/toolkit.sh': No such file or directory

root@ubuntu:/home/eric_new# chmod 777 /home/toolkit.sh

chmod: cannot access `/home/toolkit.sh': No such file or directory

root@ubuntu:/home/eric_new#

root@ubuntu:/home/eric_new# chmod +x toolkit.sh

root@ubuntu:/home/eric_new# ./toolkit.sh

python: can't open file '.toolkit.py': [Errno 2] No such file or directory

root@ubuntu:/home/eric_new#

Any ideas?