Full root for A700 and A701 tablets

Search This thread

andlommy

Senior Member
Aug 19, 2006
97
55
I fot full Root now with method 3.
First do a nandroid, unlock the bootloader and install cwm patch1 first ;)
Then apply the zip-file from method 3.

Reboot and Full Root with R/W :)

Depends on your bootloader version apparently.
None of 3 methods work 4 me :(

Need a patched bootloader :(

Sent from my A701 using Tapatalk 2
 

andlommy

Senior Member
Aug 19, 2006
97
55
Update. Got root+rw remount to work.
The problem was a weird busybox version that mount references.

Can anybody give a quick reference on how to extract current firmware so i can share.
1.017 seems to be a rarity out there still...
 
Last edited:

RiceDie

Senior Member
Nov 27, 2011
156
27
127.0.0.1
I fot full Root now with method 3.
First do a nandroid, unlock the bootloader and install cwm patch1 first ;)
Then apply the zip-file from method 3.

Reboot and Full Root with R/W :)

I think Im going to try as you suggest. Yesterday got another Iconia A701 in silver color this time. I unlocked the bootloader but cant ROOT it.. yett..
 

TomONeill

Senior Member
Dec 4, 2008
236
64
I fot full Root now with method 3.
First do a nandroid, unlock the bootloader and install cwm patch1 first ;)
Then apply the zip-file from method 3.

Reboot and Full Root with R/W :)

How do you do a Nandroid backup without having CWM installed??


Edit:
I looked it up on the internet and you can't do that.

You can by using Clockwork and then after flashing back remove the root.


Can anyone confirm that the following commands in the Android Terminal work to UNroot our tablets?:

[...]

then after booting you'll still be rooted, to unroot you'd need to open terminal again and:

su
mount -o remount,rw /system
rm /system/bin/su
rm /system/xbin/su
rm /system/app/SuperUser.apk

then reboot, you should be back to full stock.

Source:
http://androidarea51.com/q-kernel-and-recovery-releases/nandroid-backup-before-rooting/
 
Last edited:

RiceDie

Senior Member
Nov 27, 2011
156
27
127.0.0.1
Trying via Method 1

Installing CWM looks cumbersome and the fact that there are no CUSTOM Roms to flash (except CM for A700 but I dont have that one) I see no point! :eek:

Here is what I get VIA method 1 its still hanging here, device is rebooted and stuck at ACER logo. Unpluging the USB back and forth brings null results...

I ROOT'ed two A701's before.. although I used dif methods..
 
Last edited:

GenghisKhan67

Senior Member
Dec 8, 2010
404
44
Sherbrooke
Trying via Method 1

Installing CWM looks cumbersome and the fact that there are no CUSTOM Roms to flash (except CM for A700 but I dont have that one) I see no point! :eek:

Here is what I get VIA method 1 its still hanging here, device is rebooted and stuck at ACER logo. Unpluging the USB back and forth brings null results...

I ROOT'ed two A701's before.. although I used dif methods..

I just got my A700 yesterday, tried all three methods but only #2 worked, and only by typing in ADB commands manually.

I'm looking forward to more custom ROMs coming out, especially running Jellybean. I'm somewhat disappointed in the lack of dev interest for the Acer tablets, they have great potential and are currently selling at lower prices (I wanted to buy the Asus Transformer Infinity but didn't want to pay an extra $100).
 
  • Like
Reactions: RiceDie

Moscow Desire

Retired Senior Moderator
I think Im going to try as you suggest. Yesterday got another Iconia A701 in silver color this time. I unlocked the bootloader but cant ROOT it.. yett..

Oh, RiceDie.. I suppose I'm going to see you slumming around in "this" forum also? :good:

As with the root, on my 701, I could use method 3, however, I had to goto the SU site and flash the binaries. Agree with what was said earlier, about BusyBox being messed up. As SU couldn't update the binaries by itself.

Of course I got the super brick with that crappy original CWM, so hope to get the tab back this coming week.

MD
 
  • Like
Reactions: RiceDie

Moscow Desire

Retired Senior Moderator
I just got my A700 yesterday, tried all three methods but only #2 worked, and only by typing in ADB commands manually.

I'm looking forward to more custom ROMs coming out, especially running Jellybean. I'm somewhat disappointed in the lack of dev interest for the Acer tablets, they have great potential and are currently selling at lower prices (I wanted to buy the Asus Transformer Infinity but didn't want to pay an extra $100).

Well, there's not a lack of development per say, just a lack of "Devs and Modders" because........

They all bricked their tabs getting all the initial issues worked out (so other people didn't), and some still waiting for them from the Service Center! :laugh::laugh::laugh:

Hope to get mine back next week....

MD
 
  • Like
Reactions: aticatac

tube

Senior Member
Apr 9, 2005
66
1
So, I rooted my A700 using method #2. (Having stock FW AV043_A700_1.055.00_EMEA_DE).
It does work excellent - except HDMI out.
I am pretty HDMI worked well before rooting. After rooting I can see a picture on the external screen, but the touch screen is not working anymore. When I disconnect HDMI, the touchscreen does work instantly. Any ideas?
 
  • Like
Reactions: RiceDie

Moscow Desire

Retired Senior Moderator
So, I rooted my A700 using method #2. (Having stock FW AV043_A700_1.055.00_EMEA_DE).
It does work excellent - except HDMI out.
I am pretty HDMI worked well before rooting. After rooting I can see a picture on the external screen, but the touch screen is not working anymore. When I disconnect HDMI, the touchscreen does work instantly. Any ideas?

I can remember my HDMI worked fine (701) as I played the monopoly game. Shortly before I bricked it with the original CWM.

Might just try a reboot.

MD
 

_WiNNa_

Senior Member
Jun 14, 2012
162
36
Xiaomi Poco F1
Xiaomi 11T Pro
So, I rooted my A700 using method #2. (Having stock FW AV043_A700_1.055.00_EMEA_DE).
It does work excellent - except HDMI out.
I am pretty HDMI worked well before rooting. After rooting I can see a picture on the external screen, but the touch screen is not working anymore. When I disconnect HDMI, the touchscreen does work instantly. Any ideas?

I have the same FW running on my A700, and I also rooted it with method #2.
HDMI is running without a problem. The touchscreen is still running while the Tablet is connected to my TV.

Did you already restarted the A700?
Sometimes it behaves really strange, but for me a restart always fixed the problem...

Tapa tapa tapa from HTC Desire
 

RiceDie

Senior Member
Nov 27, 2011
156
27
127.0.0.1
I just got my A700 yesterday, tried all three methods but only #2 worked, and only by typing in ADB commands manually.

I'm looking forward to more custom ROMs coming out, especially running Jellybean. I'm somewhat disappointed in the lack of dev interest for the Acer tablets, they have great potential and are currently selling at lower prices (I wanted to buy the Asus Transformer Infinity but didn't want to pay an extra $100).

Will try #2 now! Update: Yes! Thanks my 3rd rooted A701

Oh, RiceDie.. I suppose I'm going to see you slumming around in "this" forum also? :good:

As with the root, on my 701, I could use method 3, however, I had to goto the SU site and flash the binaries. Agree with what was said earlier, about BusyBox being messed up. As SU couldn't update the binaries by itself.

Of course I got the super brick with that crappy original CWM, so hope to get the tab back this coming week.

MD

Hey MD! Oh cr@p! I hope I wont brick this A701!
I remember you bricking your A701 is it still in service from that time?
 
Last edited:

Moscow Desire

Retired Senior Moderator
Hey MD! Oh cr@p! I hope I wont brick this A701!
I remember you bricking your A701 is it still in service from that time?

I hope you don't also! I think the current CWM is ok, and the Super Brick bug is hopefully a thing of the past. (however, a couple guys this past week bricked their 510's, and they can't remeber which version of CWM they were using!!! Duhhhh)

If and when I ever get mine back, I'll finish the custom rom. Hopefully will get the rest of the issues with the OC kernel worked out (not that I think it needs it). Really can't do much of anything, as I have no tab to do testing, except my 501.

Yeah, mine is still in the local service center. I have no idea what the issue is.

Should have just been a mainboad change. Well, they did, installed the OS, the tab worked. But, when I picked it up, NO 3G! Would not even recognize Sim card as being installed. So it never left the shop.

Second mainboard ordered. Not sure what went up with that one, but whatever, they had to order another part. They should have recieved it last week. So I would HOPE, this week I get it back. Will have the wife call them....... again. It's been a week and a half since last call.

Regardless, it's past the 45 day mark in the service center, and according to Russian law, The Place I bought it from is obligated to replace it, or issues a refund. (should opt for a refund, as the tab is now 50$ cheaper than when I bought it).

Glad to see you in the forum! :good:

MD
 

RiceDie

Senior Member
Nov 27, 2011
156
27
127.0.0.1
I hope you don't also! I think the current CWM is ok, and the Super Brick bug is hopefully a thing of the past. (however, a couple guys this past week bricked their 510's, and they can't remeber which version of CWM they were using!!! Duhhhh)

If and when I ever get mine back, I'll finish the custom rom. Hopefully will get the rest of the issues with the OC kernel worked out (not that I think it needs it). Really can't do much of anything, as I have no tab to do testing, except my 501.

Yeah, mine is still in the local service center. I have no idea what the issue is.

Should have just been a mainboad change. Well, they did, installed the OS, the tab worked. But, when I picked it up, NO 3G! Would not even recognize Sim card as being installed. So it never left the shop.

Second mainboard ordered. Not sure what went up with that one, but whatever, they had to order another part. They should have recieved it last week. So I would HOPE, this week I get it back. Will have the wife call them....... again. It's been a week and a half since last call.

Regardless, it's past the 45 day mark in the service center, and according to Russian law, The Place I bought it from is obligated to replace it, or issues a refund. (should opt for a refund, as the tab is now 50$ cheaper than when I bought it).

Glad to see you in the forum! :good:

MD

Hey MD! I didnt install CWM on any A701 yett! Will do once there are Roms to flash!
Im kinda disappointed with the lack of Roms therefore I tend to mess around with my HOX more.
I guess Im a flahaholic with OC UV favor :laugh:
Thanks for the worm welcoming!
 

tube

Senior Member
Apr 9, 2005
66
1
Is JB rootable with the same methods (e.g. method #2)?
Can I go back to the original kernel after rooting while keeping root?

Sent from my A700 using xda app-developers app
 

benjieb

Senior Member
Sep 24, 2008
305
69
Paris
Hi,


I have a stock A700 running the latest JB Rom.

Simple question, how do I root ? Is this thread still relevant, has there been new devs since, is JB specific in regards of unlocking/moded recovery/rooting ?


thanks
 

bschrib

Senior Member
Feb 18, 2009
187
61
Columbus
Hey all -- I'm trying to get some root on my new A700 but I have some questions (after doing lots of reading through the forms). Hopefully the community can help me out here?

1.) I see that so far the only methods of obtaining root involve unlocking the bootloader and then running some sort of root.img file. However I also noted in the bootloader unlock thread that you CANNOT relock the bootloader via typical "fastboot oem lock" command, so the only way to restore a locked bootloader is to flash a backup, or original firmware. Is this correct?

2.) CWM ~DOES NOT~ work for the A700, so far as I can read (at least not reliably..?), or more specifically you have to have specific bootloaders for it to be compatible. With this in mind, would it be possible to just "fastboot boot cwm.img" and make nandroid backups, without actually flashing the CWM recovery, or would that too risk bricking the device?

3.) Ultimately my goal is to download the OTA's that my device is getting during it's journey to the OTA JB 4.1.1, however since the /cache/ directory is locked I understand that I'll need root to accomplish this, so if I understand things right, the first thing I'll need to do is to unlock the bootloader (which I can't relock easily), then hopefully I can boot to cwm.img and make my nandroid backups, then I should obtain root via the provided root.img files in the root thread (method 2 is reported as working), does that sound right? Since ultimately my goal is to get updated to stock ~EVERYTHING~ JB 4.1.1, will I be able to revert these changes at the end of this process, or will one of the earlier steps prevent me from actually getting to 4.1.1?

Currently I've got a completely stock device with original 4.0.4 ICS on it (I had to order a replacement from Amazon, first one had a patch of dead pixels and something stuck between screen).
Android Version: 4.0.4
Kernel version: 2.6.39.4+
Image Version: Acer_AV043_A700_RV05RC02_PA_CUS1
Build number: Acer_AV043_A700_1.017.00_PA_CUS1
Image P/N: FM.S1MA0.00A

The reason that I want to get the OTA update files is so I can pull it apart and see if there's someway to get root in JB (MD indicates that we just patch the boot.img file, right?)

Sorry for the long post, just hoping to get some clarity on this before I jump in and start making changes that are irreversible.
 

Moscow Desire

Retired Senior Moderator
Hey all -- I'm trying to get some root on my new A700 but I have some questions (after doing lots of reading through the forms). Hopefully the community can help me out here?

1.) I see that so far the only methods of obtaining root involve unlocking the bootloader and then running some sort of root.img file. However I also noted in the bootloader unlock thread that you CANNOT relock the bootloader via typical "fastboot oem lock" command, so the only way to restore a locked bootloader is to flash a backup, or original firmware. Is this correct?

2.) CWM ~DOES NOT~ work for the A700, so far as I can read (at least not reliably..?), or more specifically you have to have specific bootloaders for it to be compatible. With this in mind, would it be possible to just "fastboot boot cwm.img" and make nandroid backups, without actually flashing the CWM recovery, or would that too risk bricking the device?

3.) Ultimately my goal is to download the OTA's that my device is getting during it's journey to the OTA JB 4.1.1, however since the /cache/ directory is locked I understand that I'll need root to accomplish this, so if I understand things right, the first thing I'll need to do is to unlock the bootloader (which I can't relock easily), then hopefully I can boot to cwm.img and make my nandroid backups, then I should obtain root via the provided root.img files in the root thread (method 2 is reported as working), does that sound right? Since ultimately my goal is to get updated to stock ~EVERYTHING~ JB 4.1.1, will I be able to revert these changes at the end of this process, or will one of the earlier steps prevent me from actually getting to 4.1.1?

Currently I've got a completely stock device with original 4.0.4 ICS on it (I had to order a replacement from Amazon, first one had a patch of dead pixels and something stuck between screen).
Android Version: 4.0.4
Kernel version: 2.6.39.4+
Image Version: Acer_AV043_A700_RV05RC02_PA_CUS1
Build number: Acer_AV043_A700_1.017.00_PA_CUS1
Image P/N: FM.S1MA0.00A

The reason that I want to get the OTA update files is so I can pull it apart and see if there's someway to get root in JB (MD indicates that we just patch the boot.img file, right?)

Sorry for the long post, just hoping to get some clarity on this before I jump in and start making changes that are irreversible.

If you hold off for a couple days, will post a insecure boot.image, so you don't have to do all this stuff.

Simple unlock bootloader, Fastboot the new boot.image.

The above method, is outdated, and doesnt give true root/System RW access.

Already works great for 701. Just need to modify 700 boot.img

MD
 

bschrib

Senior Member
Feb 18, 2009
187
61
Columbus
Thank you so much MD, I really didn't want to go through all of that.. hahaha.. I'll just wait patiently. In the meantime (for myself and any other users who jumped on the lowered Amazon Price), should we stick around on ICS, or do you think bumping to JB would be OK?

Thanks again man.
 

Moscow Desire

Retired Senior Moderator
Thank you so much MD, I really didn't want to go through all of that.. hahaha.. I'll just wait patiently. In the meantime (for myself and any other users who jumped on the lowered Amazon Price), should we stick around on ICS, or do you think bumping to JB would be OK?

Thanks again man.

Well, I can't tell you what to do.

Is JB Better? Of course. I feel they somewhat fixed some things, Definately a lot smoother. Also, temp seems to be lower. Display a bit more responsive.

My advice before taking OTA. (I took mine immediately after going through wizard).
1. If you have installed any apps, like launchers, Task killers, etc, uninstall them).
2. If you activated that useless Anti-virus app included, kill it.
3. Try to get it as close to stock as possible.

Then do OTA.

MD
 

Top Liked Posts

  • There are no posts matching your filters.
  • 19
    WARNING. THIS is ONLY for tablets running ICS. If you are running Jelly Bean, You May Brick your device!!

    Again, this is for ICS ONLY!

    Running this root on a Jelly Bean OS can cause your tablet to stop functioning as it is designed for ICS only. If you have a Jelly Bean Operating system, then please use Vorbeth's or Moscow Desire's Easy Root Package located in the Development Forum. If you do not know which OS you currently have, then you should ask questions before rooting.




    Method 1. Universal for A700 and A701 Tablet

    1. Enable adb mode: Settings -> Developer options -> USB debugging - check it point.
    2. Unlock your bootloader for fastboot, follow here. Then reboot a tablet.
    3. Download arhive. Unpack it to any place.
    4. Open the directory with the unpacked archive. Execute file:
    for windows with the rights of administrator:
    Code:
    runit.bat
    Your firmware is now rooted.
    5. At first it is necessary to start the Superuser program, at least 1 time after receiving root. And only then programs that require root access.

    ATTENTION!
    Don't install Busybox! It is already installed and established! If you reinstall it, some programs will become unable to access root permissions!

    ------------------------------------------------------------------------------------------------------

    Method 2. With the patched kernel from the A700 tablet
    For ICS A700 firmware only!

    1. Enable adb mode: Settings -> Developer options -> USB debugging - check it point.
    2. Unlock your bootloader for fastboot, follow here. Then reboot a tablet.
    3. Download this arhive. Unpack it to any place.
    4. Open the directory with the unpacked archive. Execute file:
    for windows with the rights of administrator:
    Code:
    flash-ICS-patchedBoot.bat
    Your boot.img is now patched and firmware is now rooted.
    5. At first it is necessary to start the Superuser program, at least 1 time after receiving root. And only then programs that require root access.
    6. Now you will have to install the following programs:
    BusyBox
    Titanium Backup
    7. Run BusyBox and go through the install steps. During this SU should ask permission to give BB root access, if it does, it worked!

    ------------------------------------------------------------------------------------------------------

    Method 3. From CWM recovery for A700 and A701 Tablet - Not available due to problems in the work of CWM recovery!

    1. At the tablet must be installed CWM recovery.
    2. Download arhive ICS_Rooting_recovery.zip. Put it on SD-card. Insert the SD-card in the tablet.
    3. Run CWM recovery on the tablet and flash ICS_Rooting_recovery.zip.
    Your firmware is now rooted.
    4. Now you will have to install the following programs:
    SuperUser
    Titanium Backup
    At first it is necessary to start the Superuser program, at least 1 time after receiving root. And only then programs that require root access.

    ATTENTION!
    Don't install Busybox! It is already installed and established! If you reinstall it, some programs will become unable to access root permissions!

    ------------------------------------------------------------------------------------------------------

    Method 1, in contrast to method 2, does not affect the core of the system. This makes it possible to receive future firmware update. But only if you do not forget to make backups before making changes to the system and restore it before upgrading. ;)

    PS: I tried to make a method 1 as safe as possible. But I have not had a chance to test it completely. So if it does not work, be sure to let me know in this thread and I modified it.
    3
    Hey all -- I'm trying to get some root on my new A700 but I have some questions (after doing lots of reading through the forms). Hopefully the community can help me out here?

    1.) I see that so far the only methods of obtaining root involve unlocking the bootloader and then running some sort of root.img file. However I also noted in the bootloader unlock thread that you CANNOT relock the bootloader via typical "fastboot oem lock" command, so the only way to restore a locked bootloader is to flash a backup, or original firmware. Is this correct?

    2.) CWM ~DOES NOT~ work for the A700, so far as I can read (at least not reliably..?), or more specifically you have to have specific bootloaders for it to be compatible. With this in mind, would it be possible to just "fastboot boot cwm.img" and make nandroid backups, without actually flashing the CWM recovery, or would that too risk bricking the device?

    3.) Ultimately my goal is to download the OTA's that my device is getting during it's journey to the OTA JB 4.1.1, however since the /cache/ directory is locked I understand that I'll need root to accomplish this, so if I understand things right, the first thing I'll need to do is to unlock the bootloader (which I can't relock easily), then hopefully I can boot to cwm.img and make my nandroid backups, then I should obtain root via the provided root.img files in the root thread (method 2 is reported as working), does that sound right? Since ultimately my goal is to get updated to stock ~EVERYTHING~ JB 4.1.1, will I be able to revert these changes at the end of this process, or will one of the earlier steps prevent me from actually getting to 4.1.1?

    Currently I've got a completely stock device with original 4.0.4 ICS on it (I had to order a replacement from Amazon, first one had a patch of dead pixels and something stuck between screen).
    Android Version: 4.0.4
    Kernel version: 2.6.39.4+
    Image Version: Acer_AV043_A700_RV05RC02_PA_CUS1
    Build number: Acer_AV043_A700_1.017.00_PA_CUS1
    Image P/N: FM.S1MA0.00A

    The reason that I want to get the OTA update files is so I can pull it apart and see if there's someway to get root in JB (MD indicates that we just patch the boot.img file, right?)

    Sorry for the long post, just hoping to get some clarity on this before I jump in and start making changes that are irreversible.

    If you hold off for a couple days, will post a insecure boot.image, so you don't have to do all this stuff.

    Simple unlock bootloader, Fastboot the new boot.image.

    The above method, is outdated, and doesnt give true root/System RW access.

    Already works great for 701. Just need to modify 700 boot.img

    MD
    2
    I'd like to know too, especially since I flashed the CWM in that thread.

    Here's what I can tell you about the CWM recovery.

    It installs fine with unlocked bootloader. The root process is a little strange, as it required a flash through CWM to get root and /System R/W permissions.

    After everything is done, SU could not update it's binaries. Said no /System R/W, even though root explorer has it set to R/W. Strange, but could just be a busy box bad install with the root program. (took a binary flash to update binaries)

    Next, CWM Recovery Back-up. It worked, although a bit slow for a stock device with no applications.

    Next, deleted a couple system apps. Fine. Added some useful apps from market. Set up tab to my liking, then made another CWM Recovery backup. It took forever (30 minutes at least).

    Then, tried a modified kernel ramdisk for init.d support, Cifs, and a couple other tweaks. Normally this is a pretty simple procedure and rarely causes problems.

    System hung at boot animation after flash through CWM. No problem, will restore latest backup. The restore took almost an hour. Took forever restoring /Data. After re-boot, none of the apps downloaded in /Data would function. Force Close on all of them, including SU. Couldn't download anything from the market either. Would just hang at downloading.

    Looks like a bad recovery? Ok, lets recover the Stock Backup'

    No, it hangs at the /Data also, so a corrupted /Data partition. You can't wipe it through CWM, it just hangs. And eventually, the same will happen with /System partition.

    You could probably wipe it through Fastboot, but I doubt it. You would only be re-installing a corrupted partition again.

    Also noticed, in the recovery folder, there is no mention of Flexrom partition, and possibly one or 2 more (dalvik cache partition?). If you are lucky enough to get a 701/700 rom re-named to update.zip to install and boot, you can consider yourself lucky. If not, send it to an Acer Service Center for repair. Pay the money if you have to.

    The problem, there are only 1 or 2 701 roms, and just a few 700 roms to try. It would be luck to find one that works.

    If you have the current CWM installed, take my advice, and don't do anything to your tablet that "might" mess things up. (Stay the heck out of CWM). Wait for some more Dev work to get done, and a better functioning CWM. It will eventually happen as it always does.

    As far as deleting a thread, I can tell you that it was done to protect anybody else from getting a bricked tab. It's not an easy thing for any moderator to do. Hopefully, things get fixed and the thread will be restored (without the download link, unless it's a better working CWM).

    MD
    2
    CWM recovery

    The thread containing CWM Recovery referred to in method 3 seems to have been deleted?

    Is that because it doesn't work? Does anyone have a working recovery?
    How moderator informed me were many complaints about the wrong job 'CWM recovery'. I was absent for 3 days. So I do not know the details yet.
    I sent message to moderator with a request to provide me with text messages from removed thread.
    2
    Excuse me

    I apologize. Uploaded the wrong file ... It was the repository for the tablet A510.
    Now everything is fixed.