Full root for A700 and A701 tablets
- Thread starter ZeroNull
- Start date
-
- Tags
- development
You have a choice. You can either wait for as long as it takes for the problem to be fixed, and no one knows how long that will be... or you can brick your tab.
It's quite a simple choice really.
Moscow Desire
Retired Senior Moderator
Currently, most of the folks who could probably work on this issue, bricked their tabs, and are probably in a Service Center. So any development is going to be a slow process. It might be another month. It depends on when they get functional tablets again.
But this is the price one pays when dealing with new "development". And everybody can read the warnings on this, so if you are not prepared to risk bricking your tab, then one should have stopped at the 1st step "Fastboot OEM Unlock"
Just be patient.
MD
Method one wouldn't work for me (a700) kept hanging on the Acer fastboot screen, terminal said waiting for device. Tried method two, worked in seconds, now have SU. Thanks for this!
I had the same experience. It would be great if someone can update the original post with notes for others.
To Recap:
Method #1, the "General" approach, just hangs after flashing on my A700.
Method #2, the A700-only approach, succeeds within 30 seconds, point-and-click easy!
Thanks to OP!
Hi, my a700 has been updated to Acer_AV043_A700_1.028.00_EMEA_FR, is it still possible to unlock and root the tab woth any of this method?
I got two questions:
1) Is the patched kernel still the same version that is included in the latest OTA?
2) I tried booting the patched kernel with "fastboot boot <kernel-image>" but it blinked and i was in the loader again. the same happend with the method 1 kernel. using current fastboot from sdk
help apreciated
1) Is the patched kernel still the same version that is included in the latest OTA?
2) I tried booting the patched kernel with "fastboot boot <kernel-image>" but it blinked and i was in the loader again. the same happend with the method 1 kernel. using current fastboot from sdk
help apreciated
This method worked for me with the version 6.0.1.0 from http://forum.xda-developers.com/showthread.php?t=1812635
Whereas method 1 and 2 did not.
Cheers
EDIT: sorry meant this link http://forum.xda-developers.com/showthread.php?t=1791165
Last edited:
A short time after I got my a700, I have rooted my tab with the method 2. I had a lot of bugs, apps, games was crashing, also the launchers, Nova or Go launcher HD. But to have the availability to install the new version it was necessary to install again the stock ROM because the OTA update was not working with the rooted tab.
The new version 1.060.00_EMEA_FR was very stable, no crash, the heat issue was better managed, and this was the case during several weeks. Then I decided to root again, and what happen directly after the root, the games and launchers are crashing again.
I don't know why, but with this root method, it looks like that the a700 is not so table as with no root.
Envoyé depuis mon A700 avec Tapatalk
The new version 1.060.00_EMEA_FR was very stable, no crash, the heat issue was better managed, and this was the case during several weeks. Then I decided to root again, and what happen directly after the root, the games and launchers are crashing again.
I don't know why, but with this root method, it looks like that the a700 is not so table as with no root.
Envoyé depuis mon A700 avec Tapatalk
Hi there,
some noob questions:
I have the lated original firmware installed. Tried method 1 because I do not want to change the bootloader.
Also 'fastboot boot rooting.img' does not work for me. As I understood, 'fastboot flash recovery rooting.img' will actually flash the img. Can I make a backup of the current recovery?
If nothing helps I would flash the boodloade, but also here: Is there a way to make a backup before flashing?
some noob questions:
I have the lated original firmware installed. Tried method 1 because I do not want to change the bootloader.
How can I make these backups exactly? If I would install CWM, I would have no backup of the recovery partition.
Also 'fastboot boot rooting.img' does not work for me. As I understood, 'fastboot flash recovery rooting.img' will actually flash the img. Can I make a backup of the current recovery?
If nothing helps I would flash the boodloade, but also here: Is there a way to make a backup before flashing?
Regrettably, there is no way to make a backup if "fastboot boot" doesn't work. I would recommend you to flash CWM onto the recovery partition and make a backup of your system there, because OTA will depend on you having the original boot.img that comes with your tablet but does not really depend on the recovery. In addition, some stock ROMs will also re-flash the recovery every boot if it detects that the recovery has been modified.
So what you're basically saying is that when I use Method 1, I can still update my A700? How do you know?
Can I make a nandroid backup when I only rooted my tab, so that when I want to unroot, I just flash my own nandroid backup? Or do I need to install Clockwork? How does that work?
Now, as I understood, reflashing the bootloader that CWM backed up will result into an un-rooted device that is able to receive OTA updates. Am I right?
I wonder why my backup boot.img is 8MB while the boot-patched.img is only 3.9MB. Am I looking to the wrong file or ist the patched one just really good compressed?
I wonder why my backup boot.img is 8MB while the boot-patched.img is only 3.9MB. Am I looking to the wrong file or ist the patched one just really good compressed?
boot.img is the kernel not the bootloader, but yes, restoring it will allow you to install OTA assuming you did not modify other system files.
The backed up version is 8MB which is the partition size. The actual image is probably less than that, but CWM has no info on it and thus dumped the whole partition.
B
b1oh4zard
Guest
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 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 thought method 3 isn't working
I'm still trying to figure out which method to use, and now I have to choose 1 out of 3 methods...
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
19WARNING. 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:
Your firmware is now rooted.Code:runit.bat
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:
Your boot.img is now patched and firmware is now rooted.Code:flash-ICS-patchedBoot.bat
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
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
MD2
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).
MD2CWM 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.
