Related
A problem currently exists with newer Xooms when attempts are made to flash ClockworkMod 3.2.0.0 (R4c) (CMW) into the Recovery partition. This issue has been mentioned in several threads with no resolution to date.
This is what the problem seems to be:
- Fact: There was no problem flashing ClockWorkMod (CWM) to older (earlier versions than 3.2.1).
- Fact: The problem occurred with attempts to flash later versions of Android, e.g., 3.2.1 following update via OTA.
- Fact: The OTA has an incompatibility with CWM. Joe Ferreira identified the problem as one of the following files being present that will prevent CWM from working:
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
- Fact: The proposed fix involves reverting to an earlier version, i.e., 3.0 and updating to 3.2.1 via OTA. This fix is yet unproven.
- Fact: Owners of newer Xooms are being prevented from achieving root because of this problem (including myself)
To summarize:
1) Recent OTAs which bring the Xoom to 3.2.1 are incompatible with the ClockworkMod 3.2.0.0 (R4c) image (CWM)
2) Once flashed CWM is inaccessible.
This is the problem that needs to be resolved.
Note: Epic118 has suggested reverting to 3.0; updating via OTA to 3.2.1; and rerunning Xoot. I don't understand this since attempting to flash CWM on 3.2.1 updated via OTA will repeat the same issue. Perhaps EPIC118 can provide clarification.
Does anyone have a solution/fix to this problem?
microi said:
A problem currently exists with newer Xooms when attempts are made to flash ClockworkMod 3.2.0.0 (R4c) (CMW) into the Recovery partition. This issue has been mentioned in several threads with no resolution to date.
This is what the problem seems to be:
- Fact: There was no problem flashing ClockWorkMod (CWM) to older (earlier versions than 3.2.1).
- Fact: The problem occurred with attempts to flash later versions of Android, e.g., 3.2.1 following update via OTA.
- Fact: The OTA has an incompatibility with CWM. Joe Ferreira identified the problem as one of the following files being present that will prevent CWM from working:
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
- Fact: The proposed fix involves reverting to an earlier version, i.e., 3.0 and updating to 3.2.1 via OTA. This fix is yet unproven.
- Fact: Owners of newer Xooms are being prevented from achieving root because of this problem (including myself)
To summarize:
1) Recent OTAs which bring the Xoom to 3.2.1 are incompatible with the ClockworkMod 3.2.0.0 (R4c) image (CWM)
2) Once flashed CWM is inaccessible.
This is the problem that needs to be resolved.
Note: Epic118 has suggested reverting to 3.0; updating via OTA to 3.2.1; and rerunning Xoot. I don't understand this since attempting to flash CWM on 3.2.1 updated via OTA will repeat the same issue. Perhaps EPIC118 can provide clarification.
Does anyone have a solution/fix to this problem?
Click to expand...
Click to collapse
How about reverting to stock 3.0.1, then OTA updating to 3.2 and then rooting/flashing recovery and custom rom/kernel. I would think the issue is with the 3.2.1 OTA update itself.
I'm not completely sure I understand but if u can try this,
Download the universal root update zip and put it on your xoom
Flash clockwork through fastboot and then reboot into recovery, don't let it boot or the install recovery.sh will delete clockwork!
Flash the universal root.zip and boot up and use a root file manager to delete those two file and clockwork should stick through a reboot
Sent from my ADR6400L using Tapatalk
Hi
I have a UK Xoom and I am interested in putting a custom ICS on it. I have read through all of the pages of the excellent guide to unlocking and rooting etc started by okantomi. Fair play to all involved, its a great source of information.
My Xoom is showing 3.2 as the current version. When I bought it a few months ago it had 3.0 installed. I updated OTA to 3.1 and more recently to 3.2. I then got a small update a few weeks back but Android version is still showing as 3.2. Am I good to go ahead?
bandit197 said:
Hi
I have a UK Xoom and I am interested in putting a custom ICS on it. I have read through all of the pages of the excellent guide to unlocking and rooting etc started by okantomi. Fair play to all involved, its a great source of information.
My Xoom is showing 3.2 as the current version. When I bought it a few months ago it had 3.0 installed. I updated OTA to 3.1 and more recently to 3.2. I then got a small update a few weeks back but Android version is still showing as 3.2. Am I good to go ahead?
Click to expand...
Click to collapse
I'm not sure what update (after the 3.2 update) added the security "fix" that seems to cause the problem, but you might as well try to root. If it doesn't work, at least you have a potential work-around, but hopefully it will be fine.
Good luck.
okantomi said:
I'm not sure what update (after the 3.2 update) added the security "fix" that seems to cause the problem, but you might as well try to root. If it doesn't work, at least you have a potential work-around, but hopefully it will be fine.
Good luck.
Click to expand...
Click to collapse
Cheers, I went ahead with it and it worked out no problems, unlocked, rooted and I can access recovery. Ill post the details in the guide thread to keep everything in the one place.
Superchilpil,
Thank you for your reply.
There are a few points I don't fully understand.
You indicate,
Flash clockwork through fastboot and then reboot into recovery, don't let it boot or the install recovery.sh will delete clockwork!
Click to expand...
Click to collapse
1) Should I reboot into recovery using fastboot or simply reboot the Xoom using "Vol+ and Power"?
2) You indicate, "Don't let it boot". I don't understand; if I initiate a 'reboot', it reboots. How can I prevent it from rebooting???
This is the code I will use to flash Clockwork:
adb reboot bootloader
fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
Click to expand...
Click to collapse
What code should I use to effect your suggested approach?
One last question. The objective of this question is to understand if I can simply flash the "Universal Root Update Zip" to obtain root using the stock Recovery Mode, then install ClockworkMod Recovery; then remove one or the other of two problematic security files which are currently causing a problem. This will theoretically resolve the "Green Bot of !" issue Xoom users with 3.2.1 are currently experiencing.
After unlocking the bootloader, is it possible to:
1) Flash Update.zip (from the MicroSD card) using the stock Recovery Mode
2) Flash ClockworkMod Recovery through fastboot
3) Obtain root from this procedure
Thank you in advance.
Microi
microi said:
Superchilpil,
Thank you for your reply.
There are a few points I don't fully understand.
You indicate,
1) Should I reboot into recovery using fastboot or simply reboot the Xoom using "Vol+ and Power"?
2) You indicate, "Don't let it boot". I don't understand; if I initiate a 'reboot', it reboots. How can I prevent it from rebooting???
This is the code I will use to flash Clockwork:
What code should I use to effect your suggested approach?
One last question. The objective of this question is to understand if I can simply flash the "Universal Root Update Zip" to obtain root using the stock Recovery Mode, then install ClockworkMod Recovery; then remove one or the other of two problematic security files which are currently causing a problem. This will theoretically resolve the "Green Bot of !" issue Xoom users with 3.2.1 are currently experiencing.
After unlocking the bootloader, is it possible to:
1) Flash Update.zip (from the MicroSD card) using the stock Recovery Mode
2) Flash ClockworkMod Recovery through fastboot
3) Obtain root from this procedure
Thank you in advance.
Microi
Click to expand...
Click to collapse
by not letting it boot I mean don't let it boot into the rom, and both of those methods u stated will work just fine to reboot
And flash it using whatever method you desire, but I forgot to mention that you may need to flash clockwork again after you boot and delete those files because the install recovery.sh obviously flashes the stock recovery and the point of my method is to keep a custom recovery on your device
I know for a fact that the stock recovery mode won't flash anything you will find here in the forums that I know of
Sent from my Xoom using Tapatalk
superchilpil said:
I know for a fact that the stock recovery mode won't flash anything you will find here in the forums that I know of
Click to expand...
Click to collapse
Correct, the stock recovery requires that the zip files be signed with keys that only the manufacturers have access to. This is the whole reason why we have to flash a third party recovery to begin with.
teameos said:
Correct, the stock recovery requires that the zip files be signed with keys that only the manufacturers have access to. This is the whole reason why we have to flash a third party recovery to begin with.
Click to expand...
Click to collapse
I'm getting more and more confused the more times I read this.!!
I have done the update then unlocked to find I now have the green bot!!!!!
Someone please send a simple step by step with some file links to revert back to stock 3.2!
Thanks
I was HC stock, locked, unrooted, had accepted all OTA's - and therefore had the problem with the 2 files mentioned in the OP. I updated to ICS just fine. In order to root, I did the following (the differences from the standard instructions are underlined)
unlock
flash recovery
boot into recovery
root
then while still in CWM, no reboot, but instead:
adb remount
adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
reboot with CWM
Only had to flash CWM once.
willysp said:
I was HC stock, locked, unrooted, had accepted all OTA's - and therefore had the problem with the 2 files mentioned in the OP. I updated to ICS just fine. In order to root, I did the following (the differences from the standard instructions are underlined)
unlock
flash recovery
boot into recovery
root
then while still in CWM, no reboot, but instead:
adb remount
adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
reboot with CWM
Only had to flash CWM once.
Click to expand...
Click to collapse
Thanks. This makes a lot of sense. I would like to edit my rooting guide and give this procedure as the preferred approach. Is there anything you would want to add to it?
Just as a Fyi, these files are on all Android os, not something new. You can also flash an insecure boot image, and it will stop these from running.
adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
Sent from my Nexus S 4G
okantomi said:
Thanks. This makes a lot of sense. I would like to edit my rooting guide and give this procedure as the preferred approach. Is there anything you would want to add to it?
Click to expand...
Click to collapse
Hi,
First - thanks for your rooting guide - I used it with the exception of my underlined steps which were a synthesis of what I saw in a few other places.
Nothing to add - except perhaps really emphasize to keep the USB cable connected, and after rooting, do not reboot, stay in CWM, and use adb to run the 3 commands. You wrote a very detailed guide, so know you'll do a great job writing the expanded version of my short underlined additions. As you obviously know, many of the less technical users need a more detailed explanation of my underlined changes.
Thanks again for the help your guide gave me!
---------- Post added at 07:19 AM ---------- Previous post was at 07:14 AM ----------
bwcorvus said:
Just as a Fyi, these files are on all Android os, not something new. You can also flash an insecure boot image, and it will stop these from running.
adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
Sent from my Nexus S 4G
Click to expand...
Click to collapse
Yes, I saw them mentioned re several devices as I googled.
But - are you saying they were present in stock Xoom HC? Everything I've read says they were added in the 3.2 OTA, since people who are on 3.1 don't have these files to deal with.
willysp said:
But - are you saying they were present in stock Xoom HC? Everything I've read says they were added in the 3.2 OTA, since people who are on 3.1 don't have these files to deal with.
Click to expand...
Click to collapse
These are a _function_ of the OTA process. When there are kernel or recovery updates required, the stock recovery partition requires patching, hence these files.
ydaraishy said:
These are a _function_ of the OTA process. When there are kernel or recovery updates required, the stock recovery partition requires patching, hence these files.
Click to expand...
Click to collapse
Thanks, that helps explain what they are. So, if an OTA (like 3.2 apparently) wants to patch/replace stock recovery, those are the files that do it on next boot. Would be nice if they deleted themselves when done (from a hacker's POV), but for people running stock, I guess it makes sense for the OS to check the recovery partition at each boot and overwrite it with stock recovery if needed.
willysp said:
Hi,
First - thanks for your rooting guide - I used it with the exception of my underlined steps which were a synthesis of what I saw in a few other places.
Nothing to add - except perhaps really emphasize to keep the USB cable connected, and after rooting, do not reboot, stay in CWM, and use adb to run the 3 commands. You wrote a very detailed guide, so know you'll do a great job writing the expanded version of my short underlined additions. As you obviously know, many of the less technical users need a more detailed explanation of my underlined changes.
Thanks again for the help your guide gave me!
---------- Post added at 07:19 AM ---------- Previous post was at 07:14 AM ----------
Yes, I saw them mentioned re several devices as I googled.
But - are you saying they were present in stock Xoom HC? Everything I've read says they were added in the 3.2 OTA, since people who are on 3.1 don't have these files to deal with.
Click to expand...
Click to collapse
I'm no expert, but I will try to put it together based on the info in this thread, but please correct me if I'm wrong.
okantomi said:
I'm no expert, but I will try to put it together based on the info in this thread, but please correct me if I'm wrong.
Click to expand...
Click to collapse
Sure - glad to.
Yes these files were on the stock Xoom. Infact it helped us get some of the dumps. We would flash cwm, then dump, then let the OS rebuild the recovery. We then flashed cwm to boot and dumped the stock recovery.
Sent from my Nexus S 4G
bwcorvus said:
Yes these files were on the stock Xoom. Infact it helped us get some of the dumps. We would flash cwm, then dump, then let the OS rebuild the recovery. We then flashed cwm to boot and dumped the stock recovery.
Sent from my Nexus S 4G
Click to expand...
Click to collapse
Thanks for the info.
EDIT FROM THE ARCHANGEL: DO NOT USE THIS RECOVERY IT WILL BRICK YOUR TAB,btw i pulled the links
CWM Recovery v5.5.0.4 for A70x
Attention!
At the moment CWM recovery is not workable! Its use can lead to non-functionality of your tablet! For details see here.
Original article is published on this site and created by ZeroNull and steaven_zw (4pda.ru).
How to:
1. Boot your device.
2. On a tablet: "Settings" -> "Applications" -> "Development" -> "USB debugging" switch on. Connect the tablet to your PC. Be sure to install the latest driver for the tablet.
3. Download the archive and extract it to any convenient location on your computer.
4. Unlock your bootloader for fastboot, follow here. Then reboot a tablet.
5. Open the directory with the unpacked archive. Execute file:
for windows with the rights of administrator:
Code:
flash-cwm.bat
Recovery is installed.
Reboot again with Volume- and see whether you can still access recovery (or use the following command):
Code:
adb reboot recovery
PS: If you can not use this instruction, look here.
You're the man.
Sent from my GT-N7000 using xda app-developers app
should the boot image be patched our does that not matter
Works great thanks for your awesome work again.:good:
Quick questions for you ZeroNull:
Do we have to unlock bootloader first (I suppose we do) ?
Do we have to be rooted first (I suppose we don't) ?
If we don't have to be rooted first, can we root after just by flashing the supersu.zip by Chainfire from recovery (I would suppose we can) ?
Thanks a lot, again.
EDIT: I just checked and saw that the recovery in this package is the same size as the "rooting.img" in the generic root package from you. I suppose that means it is a temp recovery that you use to root the tab ? Which means we can gain root from recovery so flashing supersu from this recovery should work... just trying to understand what's going on, for my own knowledge
EDIT 2: I just opened the .bat file and saw there was some disabling at the end for recovery.sh
I also opened an Acer rom and saw inside the zip that there was some stuff about recovery.sh
From what I can understand, it looks like you disable something that Acer wants to do. What is it exactly ?
If I reflash an Acer stock rom from CWM recovery, will the recovery be reflashed with stock one, or does your script takes care of that ?
Again, just trying to understand.
Still looking for a stock .017 US ROM image...
Latoc said:
Quick questions for you ZeroNull:
Do we have to unlock bootloader first (I suppose we do) ?
Do we have to be rooted first (I suppose we don't) ?
If we don't have to be rooted first, can we root after just by flashing the supersu.zip by Chainfire from recovery (I would suppose we can) ?
Thanks a lot, again.
EDIT: I just checked and saw that the recovery in this package is the same size as the "rooting.img" in the generic root package from you. I suppose that means it is a temp recovery that you use to root the tab ? Which means we can gain root from recovery so flashing supersu from this recovery should work... just trying to understand what's going on, for my own knowledge
EDIT 2: I just opened the .bat file and saw there was some disabling at the end for recovery.sh
I also opened an Acer rom and saw inside the zip that there was some stuff about recovery.sh
From what I can understand, it looks like you disable something that Acer wants to do. What is it exactly ?
If I reflash an Acer stock rom from CWM recovery, will the recovery be reflashed with stock one, or does your script takes care of that ?
Again, just trying to understand.
Click to expand...
Click to collapse
Since you are apparently still running the stock .017 US ROM, could you make (and post or PM me) a backup copy that could be used to re-flash to stock?
Thanks,
I am currently flashed and running the .025_EMA_CUS1 ROM with teh new CWM recovery... all went very well!
You'll have to unlock the boot-loader to flash a recovery, but you don't need to be rooted for this to happen.You root the operating system to gain access behind the scenes....A recovery such as CWM (this) is the first step for you to flash non signed ROMs (modified) without the system denying you. Then you can flash an already rooted (or tweaked) ROM once they are available, but as of right now there aren't any.
So unlock boot-loader, flash this, then root your ROM...
bucklyv said:
Since you are apparently still running the stock .017 US ROM, could you make (and post or PM me) a backup copy that could be used to re-flash to stock?
Thanks,
I am currently flashed and running the .025_EMA_CUS1 ROM with teh new CWM recovery... all went very well!
Click to expand...
Click to collapse
Sorry, but I'm currently running this: SDs_Acer_AV043_A700_RV07RC06_EMEA_FR.zip
It is a french leak, but you can get it from the rom thread so I'm not going to be able to help you much on this.
By the way, did you root before pushing this recovery or did you just unlock the bootloader ?
Itchiee said:
You'll have to unlock the boot-loader to flash a recovery, but you don't need to be rooted for this to happen.You root the operating system to gain access behind the scenes....A recovery such as CWM (this) is the first step for you to flash non signed ROMs (modified) without the system denying you. Then you can flash an already rooted (or tweaked) ROM once they are available, but as of right now there aren't any.
So unlock boot-loader, flash this, then root your ROM...
Click to expand...
Click to collapse
Ok cool.
Last question then: can I root by just flashing supersu.zip from CWM ?
Latoc said:
Ok cool.
Last question then: can I root by just flashing supersu.zip from CWM ?
Click to expand...
Click to collapse
No, you'll have to use one of the scripts in the rooting threads unless someone creates a flashable root.
The script I used automatically installed su and busy box.
Latoc said:
Sorry, but I'm currently running this: SDs_Acer_AV043_A700_RV07RC06_EMEA_FR.zip
It is a french leak, but you can get it from the rom thread so I'm not going to be able to help you much on this.
By the way, did you root before pushing this recovery or did you just unlock the bootloader ?
Click to expand...
Click to collapse
Mine was both rooted and s-off... I am hoping the ROM development for the ACER takes off now that it is rooted and a recovery is working. Bought this over waiting for the Infinity to drop later this month (July)... hope it wasn't a mistake I will regret!
Thanks for the response.
Cheers!
ZeroNull said:
CWM Recovery v5.5.0.4 for A70x
Original article is published on this site and created by ZeroNull and steaven_zw (4pda.ru).
How to:
1. Boot your device.
2. On a tablet: "Settings" -> "Applications" -> "Development" -> "USB debugging" switch on. Connect the tablet to your PC. Be sure to install the latest driver for the tablet.
3. Download the archive and extract it to any convenient location on your computer.
4. Unlock your bootloader for fastboot, follow here. Then reboot a tablet.
5. Open the directory with the unpacked archive. Execute file:
for windows with the rights of administrator:
Code:
flash-cwm.bat
Recovery is installed.
Reboot again with Volume- and see whether you can still access recovery (or use the following command):
Code:
adb reboot recovery
Click to expand...
Click to collapse
Awesome, thanks ZeroNull!
---------- Post added at 08:44 PM ---------- Previous post was at 08:20 PM ----------
I have one question, is the stock Recovery out there somewhere? I am just curious, in case I had to flash the original one back.
ZeroNull, you're the ****. Awesome work, again. Tanks!
californiarailroader said:
I have one question, is the stock Recovery out there somewhere? I am just curious, in case I had to flash the original one back.
Click to expand...
Click to collapse
You mean "stock rom", right?
If someone would make a nandroidbackup of a stock-Version, then You could recover from that Backup and would be on Stock.
You just need someone to be so kind, but i guess that ont take too long.
Gesendet von meinem A700 mit Tapatalk 2
After backup using the cwm and reboot then reboot again to recovery it will boot the original acer recovery!
Is this temporary cwm recovery?
After connecting the charger when the tablet off it will restore the original recovery
doanb555 said:
ZeroNull, you're the ****. Awesome work, again. Tanks!
You mean "stock rom", right?
If someone would make a nandroidbackup of a stock-Version, then You could recover from that Backup and would be on Stock.
You just need someone to be so kind, but i guess that ont take too long.
Gesendet von meinem A700 mit Tapatalk 2
Click to expand...
Click to collapse
You are right, my bad. It's late here, 11:37 PM, my brain is slowly fading in and out lol
moom999 said:
After backup using the cwm and reboot then reboot again to recovery it will boot the original acer recovery!
Is this temporary cwm recovery?
Click to expand...
Click to collapse
In the original of Acer firmware there is a function restore original (stock) recovery. In my instruction at one stage of the script executes the CWM recovery. This is necessary, that would disable the restoration of the original (stock) recovery. If for some reason the launch has not occurred or the user manually exited from the CWM recovery, then system restore will not be disabled. And after rebooting the system will automatically be restored to the original recovery.
When it executes
Disable script /etc/install-recovery.sh
error: device not found
error: device not found
moom999 said:
When it executes
Disable script /etc/install-recovery.sh
error: device not found
error: device not found
Click to expand...
Click to collapse
1. Do you have your device connected to your PC?
2. Have you enabled USB debugging from the settings?
3. Have you installed the Acer drivers on your computer?
TomONeill said:
1. Do you have your device connected to your PC?
2. Have you enabled USB debugging from the settings?
3. Have you installed the Acer drivers on your computer?
Click to expand...
Click to collapse
yes
yes
yes
Version bootloader
moom999 said:
yes
yes
yes
Click to expand...
Click to collapse
I think the problem in version bootloader, which is installed on your tablet.
This problem can be solved in two ways:
Option 1. Change to another the firmware version, in which works command bootloader - "fastboot boot recovery.img"
Option 2. After running the installation script CWM recovery, when comes to message:
Booting recovery.img
Click to expand...
Click to collapse
turn off the tablet. And then perform the following steps:
1. Press and hold down the 'Volume -'. Power on the tablet. After starting the CWM recovery - releasing button 'Volume -'.
2. Open the directory with the unpacked archive. Launch from this directory the Windows command prompt. And enter the following commands:
Code:
adb shell "mount -a && cd /system/etc && mv install-recovery.sh install-recovery.old"
adb reboot
Now CWM recovery will not be overwritten with the original recovery.
PS: Google Translate forever.
As I have no succes in installing the OTA update for my A700, and cant get the solution offered somewhere else here to work, i have a question:
Is it possible to lock an unlocked A700 again? After which - i think - it should be able to install the OTA.
Anyone here knows if this is possible?
I was in the same situation, until I flashed an emea_cus1 version. I hope you get this answered, or someone comes up with a flashable pa_cus1 version.
Consider this a bump...
Sent from my A700 using XDA Premium HD app
Can you or anyone tell me what is the difference between emea_cus1 & pa_cus1 versions?
As above, anyone with flashable pa_cus1 version?
i heard that 'unlock' is unrecoverable. Maybe it's work if you can use Flash Tool to flash the whole system by computer.
but there'r no any resources available by now.
I had to do this myself a couple days back so I could return to stock. I made this quick link-list.
1. Get Android SDK & the official Acer USB Drivers http://developer.android.com/sdk/index.html http://support.acer.com/us/en/product/default.aspx?tab=1&modelId=4318
2. Unlock the bootloader: http://forum.xda-developers.com/showthread.php?t=1710755
3. Install Clockwork Recovery: http://forum.xda-developers.com/showthread.php?t=1791165
- I had to install this recovery.img using the BAT file from this post. IMPORTANT! DO NOT INSTALL THE recovery.img FROM THAT LINK! It will brick you. Replace it with the one from the thread above (6.0.1.0).
4. Download the appropriate ROM for your device. You'll want the first CUS1 as it is 1.0.29: http://forum.xda-developers.com/showthread.php?t=1729692
5. Follow the directions in this link. If you can't get update.zip to run from an external SD (I couldn't) then try it from the root directory of your internal SD (I just noticed the post was updated after I messaged him). http://forum.xda-developers.com/sho...m.xda-developers.com/showthread.php?t=1812635
After you've done it all, be sure to choose "NO" when you reboot the system from CWM, otherwise CWM is still going to be there and you're probably going to be unable to get future updates.
It took me about two hours of trial and error to figure all this out, and in the end my bootloader was relocked, my root was unrooted, and I was on stock 1.0.29 and able to get OTA updates.
ExtremeRyno said:
I had to do this myself a couple days back so I could return to stock. I made this quick link-list.
1. Get Android SDK & the official Acer USB Drivers http://developer.android.com/sdk/index.html http://support.acer.com/us/en/product/default.aspx?tab=1&modelId=4318
2. Unlock the bootloader: http://forum.xda-developers.com/showthread.php?t=1710755
3. Install Clockwork Recovery: http://forum.xda-developers.com/showthread.php?t=1791165
- I had to install this recovery.img using the BAT file from this post. IMPORTANT! DO NOT INSTALL THE recovery.img FROM THAT LINK! It will brick you. Replace it with the one from the thread above (6.0.1.0).
4. Download the appropriate ROM for your device. You'll want the first CUS1 as it is 1.0.29: http://forum.xda-developers.com/showthread.php?t=1729692
5. Follow the directions in this link. If you can't get update.zip to run from an external SD (I couldn't) then try it from the root directory of your internal SD (I just noticed the post was updated after I messaged him). http://forum.xda-developers.com/sho...m.xda-developers.com/showthread.php?t=1812635
After you've done it all, be sure to choose "NO" when you reboot the system from CWM, otherwise CWM is still going to be there and you're probably going to be unable to get future updates.
It took me about two hours of trial and error to figure all this out, and in the end my bootloader was relocked, my root was unrooted, and I was on stock 1.0.29 and able to get OTA updates.
Click to expand...
Click to collapse
Thanks for your answer. Now I just am left with one question. I have image version Acer_AV043_A700_1.026.00_WW_GEN1
The CUS1 you mention can be flashed over that without a problem, after which I should be able to use the OTA from Acer?
CheopsChefren said:
Thanks for your answer. Now I just am left with one question. I have image version Acer_AV043_A700_1.026.00_WW_GEN1
The CUS1 you mention can be flashed over that without a problem, after which I should be able to use the OTA from Acer?
Click to expand...
Click to collapse
Whoops..I originally posted this on another forum where someone asked the same question. They had the US tablet. Get the appropriate file for your country/device. After you flash your country's stock, you will be able to get OTA updates. This relocks and unroots your device back like new.
ExtremeRyno said:
Whoops..I originally posted this on another forum where someone asked the same question. They had the US tablet. Get the appropriate file for your country/device. After you flash your country's stock, you will be able to get OTA updates. This relocks and unroots your device back like new.
Click to expand...
Click to collapse
i need to take my a701 back to acer so i have flashed my a701 back to ICS with Acer_AV043_A701_1.015.00_WW_GEN1 (got from somewhere in this forum i think, i forgot ... sorry). the process went without any trouble.
but my bootloader is still unlock.
when i try the fastboot oem lock .. it showed the lock lock and the door icon on the display ... choose the lock ... and the display show "Please wait.."
wait for more than half an hour .. still "Please wait" and i decided to turnoff the device.
my question is how long does it take to relock (fastboot oem lock) the bootloader? please advice. Thanks
I'm on Acer_AV043_A700_1.026.00_EMEA_GB.
Still no update available - is any one else having this problem?
chrisgeller said:
I'm on Acer_AV043_A700_1.026.00_EMEA_GB.
Still no update available - is any one else having this problem?
Click to expand...
Click to collapse
It's not a problem. It can take up to 2-3 months for updates to roll out completely to all regions and serial numbers.
Yeah, I dont have it either.
I do know it takes time though
which is why most of the time we force it with a ROM update
chrisgeller said:
I'm on Acer_AV043_A700_1.026.00_EMEA_GB.
Still no update available - is any one else having this problem?
Click to expand...
Click to collapse
I don't know if you did it, but you won't get the update once you unlocked the bootloader and rooted your tab.
....That wouldn't prevent the OTA from being showing as available and downloading, though. It just prevents install. That can be remedied, though...I was rooted and unlocked and just returned to stock to get the last OTA.
Returning to stock...
ExtremeRyno said:
....That wouldn't prevent the OTA from being showing as available and downloading, though. It just prevents install. That can be remedied, though...I was rooted and unlocked and just returned to stock to get the last OTA.
Click to expand...
Click to collapse
Can you please post how you returned the bootloader to stock, or "locked" ? My A700 is rooted and unlocked. I can "hide" the root with OTA Rootkeeper, but I am not sure how to return the unlocked bootloader back to stock.
Any help is much appreciated and thanks in advance!
Even though this worked for me, you should still do this at your own risk....I'm not an expert, I just got lucky.
1. Get Android SDK & the official Acer USB Drivers http://developer.android.com/sdk/index.html & http://support.acer.com/product/default.aspx?modelId=4318
2. Unlock the bootloader: http://forum.xda-developers.com/showthread.php?t=1710755
3. Install Clockwork Recovery: http://forum.xda-developers.com/showthread.php?t=1791165
- I had to install this (6.0.1.4) recovery.img using the BAT file from this post. IMPORTANT! DO NOT INSTALL THE recovery.img FROM THAT (5.5.0.4) LINK! It will brick you. Replace it with the one from the first thread above ( CWM v.6.0.1.4).
4. Download the appropriate FULL ROM for your device. http://forum.xda-developers.com/showthread.php?t=1720157
5. Follow the directions in this link. If you can't get update.zip to run from an external SD (I couldn't) then try it from the root directory of your internal SD. http://forum.xda-developers.com/showthread.php?t=1812635
After you've done it all, be sure to choose "NO" when you reboot the system from CWM, otherwise CWM is still going to be there and you're probably going to be unable to get future updates.
It took me about two hours of trial and error to figure all this out, and in the end my bootloader was relocked, my root was unrooted, and I was on stock 1.0.29 and able to get OTA updates.
Thanks!
ExtremeRyno said:
1. Get Android SDK & the official Acer USB Drivers http://developer.android.com/sdk/index.html & http://support.acer.com/product/default.aspx?modelId=4318
2. Unlock the bootloader: http://forum.xda-developers.com/showthread.php?t=1710755
3. Install Clockwork Recovery: http://forum.xda-developers.com/showthread.php?t=1791165
- I had to install this (6.0.1.4) recovery.img using the BAT file from this post. IMPORTANT! DO NOT INSTALL THE recovery.img FROM THAT (5.5.0.4) LINK! It will brick you. Replace it with the one from the first thread above ( CWM v.6.0.1.4).
4. Download the appropriate FULL ROM for your device. http://forum.xda-developers.com/showthread.php?t=1720157
5. Follow the directions in this link. If you can't get update.zip to run from an external SD (I couldn't) then try it from the root directory of your internal SD. http://forum.xda-developers.com/showthread.php?t=1812635
After you've done it all, be sure to choose "NO" when you reboot the system from CWM, otherwise CWM is still going to be there and you're probably going to be unable to get future updates.
It took me about two hours of trial and error to figure all this out, and in the end my bootloader was relocked, my root was unrooted, and I was on stock 1.0.29 and able to get OTA updates.
Click to expand...
Click to collapse
Thanks! I was able to get the 1.0.29 flashed back and have stock bootloader with no root. I did NOT install CWM because I am going to wait for JB before I do any root or recovery modes. I am looking to try to find the Acer ROM AV043.RV23RC03_PA_CUS1 ROM because it was what I had on the tablet and was an update over 1.0.29. If you know where I can get it, I would appreciate it. I can't find it anywhere!- Thanks again!
For A701 users only running Jelly Bean Only.
Boot image used: AV051_A701_1.021.00_WW_GEN1. Should work fine on other JB builds.
New Version 3 uploaded 23/10/2012
Should fix ADB commands for /System Remount Thanks Vorbeth
2 Parts. Part 2 is full /system RW.... also know as ROOT for the A701 on JB who took the OTA
Part 1 is For people using the previous "andlommy" image flash..... For JB OTA see part 2...
Part 1
This is meant to replace your boot.img after performing the Root image flash from this thread by andlommy;
http://forum.xda-developers.com/showthread.php?t=1911437
Ok people, as some may realize, the current "root" procedure of fastbooting images doesn't allow full /system remount. This can be seen if you try to update your superuser binary. Superuser can't remount /system. Yes, you can probably delete some files via file manager, however, if you use a root app that calls for a /system remount, well, it's not going to happen. Not like it should be.
Also, the 701 doesn't have a reliable CWM, so we do things the old fashioned (and safer) way.
This method has been around in the 500 forums for some time now. Recently, I gave info to the 210 users to get the /system remount working on their tabs. I currently use the same. Why nobody tried it here, well.....
Basically it involves modifying the zimage to change security, and allow remounts. It does not involve the kernel itself, as it remains stock.
Replaces Stock A701 Boot.img
1. Allows for full /System RW
2. Increased IO over stock.
And yes, I do use the modified boot image, 2nd revision.
As always, you have to thank people who helped you in the past and present:And I owe a lot to these guys. (which is why I hit the Donate button for them)
Vorbeth
Civato
EZTerry
Skrilax_CZ
LinuxSociety
NOTE" You must have unlocked bootloader"
Also, you do this at your own risk.Most of you know this already.
Installation:
For previous somewhat Rooted JB installations.
Download the following package and unzip to your system.
FIX-JB-ROOT
1. Connect your tablet
2. USB Debugging is on
3. Open a command window where you unzipped the Fix-JB-Root
4. Type: adb reboot bootloader
after tab reboots to bootloader download, Type;
5. fastboot flash boot JB_701V3_boot.img
6. After success, reboot tablet.
7. Start Superuser and update binaries.
Part 2
AS A ROOT PROCESS. 701 only After OTA to JB.
Note that this is an alternative to the image flash method. You need only to OTA to JB, then follow the instructions.....
Needs Testing on a Stock JB 701 Make sure you've unlocked your bootloader
1. Follow the above procedures in part 1
2. After restart, with tab connected, open a CMD Window where you unzipped the package.
3. Type the following commands;
a. adb devices (and hit Enter. You should see your device listed)
b. adb remount /system (and hit Enter. You should see remount successful)
c. adb push su /system/xbin
d. adb shell chmod 6755 /system/xbin/su
e. Get Superuser and Busybox from the Playstore. Start Superuser, check for updating binaries. Install Busybox.
Hopefully this roots and grants /system RW. I don't have a stock 701JB, so would appreciate feedback if this works or not.
MD
Works perfect Thank you. Now we only nee CM10 for our 701
Thanks MD! Going to give the 4.1.1 another go this weekend, using this boot. Will let you know how it goes )
MD are you able to delete apk from "/system/vendor/app"?
IronFly said:
MD are you able to delete apk from "/system/vendor/app"?
Click to expand...
Click to collapse
Absolutely. Just moved Solitaire.apk into /Data/app
Use your root explorer and check for RW.
Remember, this just fixes a shortcoming in the original "pre-rooted image flashing" from 4.0.4 to 4.1.1 where you can't get system remounts from some root apps.
As stated near the end of the post, I haven't tried it on a "stock non-rooted" JB build.
MD
Hi,MD,Can you help me for the problem:
http://forum.xda-developers.com/showthread.php?t=1934569
fishwood said:
I installed a update.zip(Acer_AV043_A701_0.006.00_WW_GEN1.zip).
then,My A701 restarted, but it's stuck at the ACER logo.
I hook up this device to the PC ,but not go to fastboot mode , "MTB drivers" is no found.
I pressed the "volume up"- and the "power"-button at the same time, released the power-button when the screen turns on and switched the lock switch on and off and on and off: top left corner of the screen says "Erasing Userdata... Unrecoverable bootloader error (0x19000008).
Who can help me? thks.
Click to expand...
Click to collapse
fishwood said:
Hi,MD,Can you help me for the problem:
http://forum.xda-developers.com/showthread.php?t=1934569
Click to expand...
Click to collapse
I answered in your original thread.
MD
Hi MD,
Slightly off-topic, but just to let you know. Tried this with the flawed 4.1.1 install we've discussed in the other thread, still no joy!! It was a long shot that I thought was worth a go anyway
misteral1970 said:
Hi MD,
Slightly off-topic, but just to let you know. Tried this with the flawed 4.1.1 install we've discussed in the other thread, still no joy!! It was a long shot that I thought was worth a go anyway
Click to expand...
Click to collapse
Yeah, I meant to tell you yesterday it won't help your situation. Your issue, is you're stuck on the ICS bootloader and it won't update to the JB one. Not to mention now, you have that "Hybrid Mix". Maybe one day can come up with a solution for it. Trying to get my hands on a 701 Service Rom.
Acer won't fess up the SBK (Secure Bootloader Key), so it sort of makes NVFlash non-usable unless we have it.
The service rom uses NVFlash, which in theory will change bootloaders (it's what we used in the 500 forums).
But until then, we're sort of stuck. I still have one trick up my sleeve, but's it's a long shot, and not even sure it'll work. Might perma-brick your tab. Will look at my old files.
MD
MD got your method working thanks for sharing this MOD!
RiceDie said:
MD got your method working thanks for sharing this MOD!
Click to expand...
Click to collapse
Which method? Experimental Root? Or just the full System RW?
Also, which build Rom are you running Mate?
MD
MD -- Any chance to get this working on the A700 with OTA 4.1.1? Your post seems very specific about being only for the A701, so I don't want to risk it.
I tried looking into the exploit involving adb restore, but it looks like the A700 must have this fixed as "ADB Restore xxx" results in being told how to use ADB commands.. (a la http://forum.xda-developers.com/showthread.php?t=1886460)
Also I looked into symlinking, like they do for the Kindle HD exploit but that only works since 4.0 let you rename tmp to tmp.bak and then do a link exploit.. :\
Also I was thinking if we could somehow maybe apply this root, if it's still applicable in 4.1?
http://sed.free.fr/root_android.html
My problem is I don't know how to get the init.rc file to read what's going on -- does anyone have a stock init.rc file and can provide the contents?
--edit--
Oh I see, this may not work for the A700 as there hasn't been a "full ROM" released, therefore we don't have the boot.img to modify? Is that correct? As I can see the kernel is actually blocking the system remount, right?
bschrib said:
MD -- Any chance to get this working on the A700 with OTA 4.1.1? Your post seems very specific about being only for the A701, so I don't want to risk it.
I tried looking into the exploit involving adb restore, but it looks like the A700 must have this fixed as "ADB Restore xxx" results in being told how to use ADB commands.. (a la http://forum.xda-developers.com/showthread.php?t=1886460)
Also I looked into symlinking, like they do for the Kindle HD exploit but that only works since 4.0 let you rename tmp to tmp.bak and then do a link exploit.. :\
Also I was thinking if we could somehow maybe apply this root, if it's still applicable in 4.1?
http://sed.free.fr/root_android.html
My problem is I don't know how to get the init.rc file to read what's going on -- does anyone have a stock init.rc file and can provide the contents?
--edit--
Oh I see, this may not work for the A700 as there hasn't been a "full ROM" released, therefore we don't have the boot.img to modify? Is that correct? As I can see the kernel is actually blocking the system remount, right?
Click to expand...
Click to collapse
The root method should work the same as with ICS and JB.
Basically need an 700 ICS and JB boot.img. to do the mod. Takes about 10 minutes. Fastboot the boot image, download SU and BB. Should be good to go.
MD
I've posted a full A700 JellyBean ROM in the general section - http://forum.xda-developers.com/showthread.php?t=1946415
I extracted the boot.img and made the required changes but it didn't seem to work.
Either it failed to boot (tested using fastboot boot) or "adb remount" failed.
I will have another try later today once I get time on the laptop again.
Sent from my A700 using Tapatalk HD
Vorbeth said:
I've posted a full A700 JellyBean ROM in the general section - http://forum.xda-developers.com/showthread.php?t=1946415
I extracted the boot.img and made the required changes but it didn't seem to work.
Either it failed to boot (tested using fastboot boot) or "adb remount" failed.
I will have another try later today once I get time on the laptop again.
Sent from my A700 using Tapatalk HD
Click to expand...
Click to collapse
Should have a modded boot image in a day or so. Seems the boot images are the same for all builds for 700 JB.
It's the weekend, so some family time is on order.
Thanks for the GB full update rom.
MD
Hi,
I was one of the first people who updated their A701 with the unrooted JB ROM which was posted on XDA forums. The update was flawless and smooth using the external SD card and normal recovery method. Last night I tried to unlock my device and root it using step by step instructions given on OP. Device has unlocked but it is still not rooted. I checked using Root Checker app. Have I missed any steps in performing the root operation? Please help.
Additionally after doing all the steps in the OP I reinstalled the original JB update ROM using external SD card and recovery method. Bootloader is still unlocked and device is still not rooted. Device is working fine as far as I can tell.
Awaiting expert advice and help!
Best regards,
So how can I revert back to the original locked boot image as the current boot image cannot be locked using "fastboot oem lock"?
farazjk said:
So how can I revert back to the original locked boot image as the current boot image cannot be locked using "fastboot oem lock"?
Click to expand...
Click to collapse
Did you try updating your superuser binaries after you completed? Start Superuser, select the "i" icon at the top, and tap the "update binaries" from the menu.
Did you install BusyBox?
I haven't had a lot of feedback on the JB stock alternative root.
The alternative "root" process was reported successful by one member who did 2 tabs. However, it doesn't mean it works on all it seems. The original intent, was to fix the inability to update binaries (/system remount) when using the "image flash" of the pre-rooted JB image andlommy provided us in his thread. Which it does indeed fix.
As for reinstalling the locked bootloader, there is only one way to do it. And that is, to install a full rom, not an update. The patch update probably sees the unlocked bootloader, and just ignores it. EDIT: Seems Acer hasn't released a FULL JB Rom for the 701 yet.
Or, you can fastboot install the pre-rooted JB image that andlommy posted. It's what I used after I took the OTA.
Or, you can install the German JB CWM, and use zero-nulls CWM root install Option 3 from HERE. I have it (German JB CWM) installed, but personally only use it for flashing an install, and NOT for making a recovery backup or doing wipes. So far, the Germans haven't had any issues with it. (this is probably the method I would use).
The working version of JB CWM can be found HERE
Also, you can use the Superuser CWM install from HERE
Until Acer gives us the SBK (secure bootloader key), we can't use NVFlash to flash an unlocked bootloader back unfortunately.
Understand though, the 51x and 70x are extremely temperamental. Some of us already found out the hard way a few months ago. They are not so forgiving as the 50x tabs were.
So I would be very careful about major changes.
MD
Moscow Desire said:
Did you try updating your superuser binaries after you completed? Start Superuser, select the "i" icon at the top, and tap the "update binaries" from the menu.
Did you install BusyBox?
I haven't had a lot of feedback on the JB stock alternative root.
The alternative "root" process was reported successful by one member who did 2 tabs. However, it doesn't mean it works on all it seems. The original intent, was to fix the inability to update binaries (/system remount) when using the "image flash" of the pre-rooted JB image andlommy provided us in his thread. Which it does indeed fix.
As for reinstalling the locked bootloader, there is only one way to do it. And that is, to install a full rom, not an update. The patch update probably sees the unlocked bootloader, and just ignores it. EDIT: Seems Acer hasn't released a FULL JB Rom for the 701 yet.
Or, you can fastboot install the pre-rooted JB image that andlommy posted. It's what I used after I took the OTA.
Or, you can install the German JB CWM, and use zero-nulls CWM root install Option 3 from HERE. I have it (German JB CWM) installed, but personally only use it for flashing an install, and NOT for making a recovery backup or doing wipes. So far, the Germans haven't had any issues with it. (this is probably the method I would use).
The working version of JB CWM can be found HERE
Also, you can use the Superuser CWM install from HERE
Until Acer gives us the SBK (secure bootloader key), we can't use NVFlash to flash an unlocked bootloader back unfortunately.
Understand though, the 51x and 70x are extremely temperamental. Some of us already found out the hard way a few months ago. They are not so forgiving as the 50x tabs were.
So I would be very careful about major changes.
MD
Click to expand...
Click to collapse
Thanks MD for your informative reply. I tried to update SU binaries but there was no option to do it. superuser app only states su binaries not found. Busybox cannot start because it does not get all the required permissions.
I could flash rooted JB ROM by andlommy but that would wipe all my apps and data. As you have suggested that only full stock ROM can restore bootloader so till Acer releases this getting back to original state is not possible.
I guess if the unlocked boot image is not harmful in anyway and if any future updates pushed by Acer will still be receivable and applicable then best thing to do would be to let the device stay with unlocked boot loader.
Once again thank you for your help and support.
Best regards,
Faraz
farazjk said:
Thanks MD for your informative reply. I tried to update SU binaries but there was no option to do it. superuser app only states su binaries not found. Busybox cannot start because it does not get all the required permissions.
I could flash rooted JB ROM by andlommy but that would wipe all my apps and data. As you have suggested that only full stock ROM can restore bootloader so till Acer releases this getting back to original state is not possible.
I guess if the unlocked boot image is not harmful in anyway and if any future updates pushed by Acer will still be receivable and applicable then best thing to do would be to let the device stay with unlocked boot loader.
Once again thank you for your help and support.
Best regards,
Faraz
Click to expand...
Click to collapse
The unlocked bootloader will have no effect on normal day to day operations.
I'll try and get a 700 or 701 stock user to run a couple of things to get the SU issue sorted out. Shouldn't take that long. Probably a matter of using adb to push it through.
The 700 already has a JB Full rom update package, so hopefully the 701 will get one soon as soon as somebody locates it
Think it's time to bother Acer, and see about a SBK......
MD