Database Info

[Q] Need Fix To Green Bot of ! Problem

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.

A701 4.1.1 [JB] OTA Firmware. UPDATE: FULL 4.1.1 and ROOT

Apparently A701 has now got a JB update.
That's the file that i'm snitching now:
Acer_A701_AV043.RV08RC01_AV051.RV03RC02_WW_GEN1_1348812627085_4fb53b48.zip
Grab here:
http://www.multiupload.nl/YFJ8SRR4W5
UPDATE
Now there is a way to fully upgrade ANY 4.0.4 device to 4.1.1
!!!! WARNING !!!!
THIS METHOD WILL WIPE ALL DATA FROM YOUR TABLET, INCLUDING INTERNAL MEMORY CARD (unless you carefully read all instructions)
You have been warned
Prerequisites: Acer A701 running 4.0.4 with unlocked bootloader and CWM recovery 6.0.1.1
Steps:
1) Download
1.1) Image for 4.0.4 http://www.multiupload.nl/L8GPOS9KLQ
1.2) Patch for 4.1.1 http://www.multiupload.nl/54LUR8HYHV
1.3) Image for 4.1.1 http://www.multiupload.nl/IEWOOJMHX0
2) Put patch 4.1.1 to an external SD card (not required, but helps a lot)
3) Boot to fastboot (adb reboot bootloader)
4) Install new image via running flash-ics.bat (that will give us a 4.0.4 image that will definitely upgrade to 4.1.1)
5) Rebooting to CWM (adb reboot recovery)
6) From within CWM install patch downloaded in 1.2
7) Reboot the device. 4.1.1 will start. Reboot it again to fastboot (adb reboot bootloader).
8) Unlock the bootloader (fastboot oem unlock)
9) Install the 4.1.1 image (flash-JBRoot.bat)
Reboot. Task complete.
To revert to 4.0.4 once 4.1.1 has been installed
1) Boot to fastboot (adb reboot bootloader)
2) From fastboot boot to CWM (fastboot boot Recovery6011-411Compatible.img)
3) From CWM install the original 4.0.4 image
If you have 4.1.1 and need ROOT
Start with step 7
THIS WILL STILL WIPE ALL DATA FROM YOUR TABLET UNLESS YOU KEEP READING
IF YOU WANT TO KEEP THE DATA ON YOUR DEVICE
Edit both .bat files and delete the -w parameter from the 'fastboot -w flash boot boot.img' command

So what now?
Can I just use this zip and install via CWM? If i'm not on V 028 can I safely install?
Gesendet von meinem Galaxy Nexus mit Tapatalk 2

doanb555 said:
So what now?
Can I just use this zip and install via CWM? If i'm not on V 028 can I safely install?
Gesendet von meinem Galaxy Nexus mit Tapatalk 2
Click to expand...
Click to collapse
Current CWM doesn't have the "getprop" command for whatever reason causing this update to fail. Also CWM we all have is for "A700" causing update to fail. Suggested installation type is to
1) Download
2) Format a micro-SD card as FAT32
3) Rename downloaded file to update.zip
4) Put to root of the sdcard
5) Start tablet with "VolDown (button with 2 dots)" pressed down
6) Update "should" happen.
Potentially a "Stock" recovery is required but i'm investigating

Geeez... So sorry, I didn't properly read the title, therefore didn't see that it is for the a701... -.-
Gesendet von meinem Galaxy Nexus mit Tapatalk 2

I also want to know A700 can use it it not.

casper326 said:
I also want to know A700 can use it it not.
Click to expand...
Click to collapse
A700 should get their own 4.1.1 update.

it's possible to adapt the update.zip file but battery life would not be as good (as the GSM layer is enabled so)

I have try to flash the A701 version to A700, but fail...
have any update file for A700?

Anybody have stock recovery from A701 0015 firmware (recovery.img)?
I can't update - i have cwm recovery A700.
PS. CWM recovery 6.0 not correct work on A701 - can't restore backups on my tablet.

casper326 said:
I have try to flash the A701 version to A700, but fail...
have any update file for A700?
Click to expand...
Click to collapse
I downloaded it, and it's an update and not a full rom so there's no way to use it on a A700.
Some nformations from this update:
ro.build.pandora.id=Acer_AV051_A701_RV03RC02_WW_GEN1
ro.build.flexrom.id=Acer_AV051_A701_1.021.00_WW_GEN1
ro.build.img_pn.id=FM.S1MA0.030

alx5962 said:
I downloaded it, and it's an update and not a full rom so there's so way to use it on a A700.
Some nformations from this update:
ro.build.pandora.id=Acer_AV051_A701_RV03RC02_WW_GEN1
ro.build.flexrom.id=Acer_AV051_A701_1.021.00_WW_GEN1
ro.build.img_pn.id=FM.S1MA0.030
Click to expand...
Click to collapse
I see~
So I need to wait for the FR version...
90% Hong Kong User also flashed to FR version. It's because Hong Kong version update too slow...
They just release the "Power Management" update....

If I flash my a700 with Acer_A701_AV043.RV00RB00_AV043.RV09RB01_WW_GEN1.zip
Can I then flash this update

moom999 said:
If I flash my a700 with Acer_A701_AV043.RV00RB00_AV043.RV09RB01_WW_GEN1.zip
Can I then flash this update
Click to expand...
Click to collapse
Why do you want to update A700 with A701 ROM? And then after you brick your device, you gonna start whinging and begging everyone in the forum for their help to recover your unit.
Are you so desperate for JB? Do you even know the difference between JB and ICS?

Now waiting for the respected modders to pick this up and give us a custom JB ROM

Can someone who has updated this successfully and is rooted provide a system dump?
Code:
busybox tar cvf /sdcard/system.tar /system
And upload system.tar from your /sdcard

Vache - we need you!
Requires professionals to do over this update to a full castom. For installation on devices with unlocked bootloader :silly:

Gigabyte0 said:
Anybody have stock recovery from A701 0015 firmware (recovery.img)?
I can't update - i have cwm recovery A700.
PS. CWM recovery 6.0 not correct work on A701 - can't restore backups on my tablet.
Click to expand...
Click to collapse
Which CWM recovery version? 6.0.???
And did you make your backup with the original CWM version 5.xxxxx? Because if you did, it probably isn't going to work, and your tab will need to go to the service center for a mainboard replacement.
A sure sign is to go into CWM, and try to do your Data wipes. IF you can't do your Data wipes, she be bricked Matey.
If you can do your user data, data and system wipes, then you just have a bad backup file.
I would do all your wipes, and try the restore function again. Sometimes I have to do this on my 501 when restoring. Shouldn't have to tho.
MD

RiceDie said:
Now waiting for the respected modders to pick this up and give us a custom JB ROM
Click to expand...
Click to collapse
I will get my new tab on monday. Acer Service has finally given up on it.
MD

Moscow Desire said:
I will get my new tab on monday. Acer Service has finally given up on it.
MD
Click to expand...
Click to collapse
Good to hear MD!

I NEED A700 FIRMWARE!

[701] /System RW JB Boot image-Full Root UPDATED

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

[N7100 4.3]N7100 XXUEMJ2_XXUEMJ2_LBEMJ2 PreRooted-Deodexed

MUST READ BEFORE PROCEED
- This ROM is AP N7100 XXUEMJ2 CP XXUEMJ2 CSC LBEMJ2 and beleved to be PreOfficial
- This ROM have KNOX security effect on bootloader
- I have flashed this ROM with bootloader and even after that I was able to downgrade MG1 ROM as well reflash this ROM again.
- Pre and post flashing EFS backup highly recommended
- This ROM have bootloader and you have to flash separately (Edit : Now you can use this ROM without bootloader too, read installation instruction)
- Recommend to wipe data (factory reset) before flashing ROM
- No one here on XDA is responsible for any bad effect on your device, You are flashing this at your own risk.
Installation Instruction
- Download Prerooted,Deodexed,Zip aligned N7100XXEMJ2 Here Direct MIRROR (Thanks to @MojoManagement ) here is other MIRROR (thank to @kunals.shah for mirror)
- Download Philz recovery if you don't have already. (you can use other but I have tested this one only)
- Copy ROM zip file to SD card and flash it with CWM.
- After Installation of this ROM, you want have WIFI working, You have to Download This Patch and extract to get patch.tar.md5 and flash with PDA tab of Odin to get wifi working. (remember this patch I have tested on MJ2 and using on other ROM may cause serious issue.)
PS : Who have already flashed bootloader and want to get rid of bootloader follow this steps
Downgrade to 4.1.2 (I have tested MG1 My prerooted)
Flash Philz latest recovery
Flash MJ2 from above said link
Flash above said patch
- Reboot normally
Special Notes
- SuperSu zp won't work to root this ROM, though you need not to do it, as This rom is already prerooted.
- If you restore app with Titanium backup, many of applications may not work, but need not to worry, follow this to make it work.
Install terminal emulator from Play store. open it, execute superSu permission and follow below said command
Code:
su
restorecon -R -v /data/data
After this you can close terminal and you will have working app which you have restored with titanium.
Remember you have to follow this everytime you restore data from titanium backup.
To All My Dr.Ketan ROM users, If you can't hold your horse, proceed with this and you will be able to flash my update based on this ROM most probable without wipe, Can't promise but may be before week end.
Reports coming Note3 packages from titoo doesn't working
Click to expand...
Click to collapse
Enjoy latest preofficial ROM

AOSP Theme for this ROM
Flash with CWM.

reserved too

two more

last

Thank you for all your work mate, I know how anoying is to upload 1.6 GB every time

Should we wait for this or continue with your custom rom since it has all N3 stuff and features..since its new so i guess it wont have all features and especially air command.
I am asking this because my bandwidth wont allow me to download after 15gb and i've already used 13gb(dr.ketan's custom rom is already in downlaoding queue)

#Respect
We will reading OP very clearly Before flash it. We understand the risk factor.. Heartfelt thanks bro.. No words to express our feeling .

Seems way too risky with KNOX integrated into this.

if you get cold feet after flashing mj2 rom before entering download mode to flash the new bootloader you can just get back into phillz recovery and restore your last nan i guess,....you have time to decide till then

Mj2? There was a leak I missed?

Thx u very much! Our team still w8 for u @namfat

this is kind of scary. never happen to me before. i was excited to try out the new leak, but having read dr's instruction. i felt uneasy...feels like having an icrap device which can't be downgraded either...

My only mumbling in my head now is..."will the current Note 3 mods work on this pre-release?

There is no reason for not to work

When Samsung will release Kernel Source for this 4.3?

SandeepEmekar said:
When Samsung will release Kernel Source for this 4.3?
Click to expand...
Click to collapse
They need to release 4.3 first ^^
Sent from my GT-N7100 using XDA Premium 4 mobile app

Moe5508 said:
My only mumbling in my head now is..."will the current Note 3 mods work on this pre-release?
Click to expand...
Click to collapse
its working fine. i have already test it

63%

edan1979 said:
its working fine. i have already test it
Click to expand...
Click to collapse
Any difference way to install with MI6 version ? or the same ?
And u try to take some mod with xposed modules, these work well or not :good:
And @dr.ketan what's about ur mod for MI6, it still working well ?

[Q] How to upgrade my device? (unknown root / unlock)

so i've recently picked up my asus tf700 again (after about 6 months of no use) and i know i rooted, upgraded to 4.1.1, and unlocked the device but just don't remember how i did it all. and i'm 90% sure i deleted the stock recovery
what i want to know is how can i upgrade to 4.2.1 ?
can i just follow this guide? http://forum.xda-developers.com/showthread.php?t=2481892
current stats:
android 4.1.1
kernal version 3.1.10
build number jro03c.USepad-10.4.4.23-20121127

gen1mx6 said:
so i've recently picked up my asus tf700 again (after about 6 months of no use) and i know i rooted, upgraded to 4.1.1, and unlocked the device but just don't remember how i did it all. and i'm 90% sure i deleted the stock recovery
what i want to know is how can i upgrade to 4.2.1 ?
can i just follow this guide? http://forum.xda-developers.com/showthread.php?t=2481892
current stats:
android 4.1.1
kernal version 3.1.10
build number jro03c.USepad-10.4.4.23-20121127
Click to expand...
Click to collapse
Yep should be good to go

gen1mx6 said:
so i've recently picked up my asus tf700 again (after about 6 months of no use) and i know i rooted, upgraded to 4.1.1, and unlocked the device but just don't remember how i did it all. and i'm 90% sure i deleted the stock recovery
what i want to know is how can i upgrade to 4.2.1 ?
can i just follow this guide? http://forum.xda-developers.com/showthread.php?t=2481892
current stats:
android 4.1.1
kernal version 3.1.10
build number jro03c.USepad-10.4.4.23-20121127
Click to expand...
Click to collapse
Yes, you can... It is a good guide if you can follow it.. You must make sure that you have the latest bootloader and compatible TWRP.. Those are very important so you are not brick your device... Good luck and ask all the questions that you have before trying to install the TWRP and bootloader...:fingers-crossed:

gen1mx6 said:
so i've recently picked up my asus tf700 again (after about 6 months of no use) and i know i rooted, upgraded to 4.1.1, and unlocked the device but just don't remember how i did it all. and i'm 90% sure i deleted the stock recovery
what i want to know is how can i upgrade to 4.2.1 ?
can i just follow this guide? http://forum.xda-developers.com/showthread.php?t=2481892
current stats:
android 4.1.1
kernal version 3.1.10
build number jro03c.USepad-10.4.4.23-20121127
Click to expand...
Click to collapse
Hallo,
could you send me a complete manual how did you root it and updated it for 4.1.1. with all of links for tools? I have a problem with my TF700 and I checked a lot of forums and tried a lot of things but it doesnt help.
Thank you very much

andre776655 said:
Hallo,
could you send me a complete manual how did you root it and updated it for 4.1.1. with all of links for tools? I have a problem with my TF700 and I checked a lot of forums and tried a lot of things but it doesnt help.
Thank you very much
Click to expand...
Click to collapse
you should probably create your own post so someone can help you, they need to know information like what version your currently running

LetMeKnow said:
Yes, you can... It is a good guide if you can follow it.. You must make sure that you have the latest bootloader and compatible TWRP.. Those are very important so you are not brick your device... Good luck and ask all the questions that you have before trying to install the TWRP and bootloader...:fingers-crossed:
Click to expand...
Click to collapse
ok so i'm having a bit of trouble following this guide...
1) I installed TWRP (with the help of this page) http://www.teamw.in/project/twrp2/105 I had to use the Download - Recovery Image / Fastboot Method because the app method wouldn't download the blob file
2) Now, when I power + volume down boot I can see my bootloader isn't the correct version. how can I update the bootloader? I have the files from the original link i posted (http://forum.xda-developers.com/showthread.php?t=2481892) so there is the correct bootloader i just don't know how to install it.
is there a more detailed guide with actual step by steps?

Congrats on getting TWRP installed! The rest is easy.
In TWRP select 'Install' and navigate to wherever you have the zip file with the bootloader/TWRP package, select it (if it has xxx signed.zip in the file name you need to check the "verify zip signature" option. sbdags usually signs his zips - don't know if he did with this one).
Swipe the button to flash the file.
When it finished, boot back to system. Do not flash a rom at this point! That would cancel the bootloader flash. Boot back into system first, then back into TWRP and then flash the rom.
BTW - flashing the modified Asus stock rom is perfectly fine, but I wonder why you don't flash CROMi-X 5.2.2?
That rom is from the same developer, based on this stock rom and miles improved since sbdags debloated the stock version.
sbdags stock rom is not really supported whereas he puts out a better version of CROMi-X about every 10 days! It's exhausting to keep up! LOL
You'll find it here: http://forum.xda-developers.com/showthread.php?t=2425383
You can still flash the BL/TWRP package you downloaded already. It's the same as the one for CROMi-X.

LetMeKnow said:
Yes, you can... It is a good guide if you can follow it.. You must make sure that you have the latest bootloader and compatible TWRP.. Those are very important so you are not brick your device... Good luck and ask all the questions that you have before trying to install the TWRP and bootloader...:fingers-crossed:
Click to expand...
Click to collapse
berndblb said:
Congrats on getting TWRP installed! The rest is easy.
In TWRP select 'Install' and navigate to wherever you have the zip file with the bootloader/TWRP package, select it (if it has xxx signed.zip in the file name you need to check the "verify zip signature" option. sbdags usually signs his zips - don't know if he did with this one).
Swipe the button to flash the file.
When it finished, boot back to system. Do not flash a rom at this point! That would cancel the bootloader flash. Boot back into system first, then back into TWRP and then flash the rom.
BTW - flashing the modified Asus stock rom is perfectly fine, but I wonder why you don't flash CROMi-X 5.2.2?
That rom is from the same developer, based on this stock rom and miles improved since sbdags debloated the stock version.
sbdags stock rom is not really supported whereas he puts out a better version of CROMi-X about every 10 days! It's exhausting to keep up! LOL
You'll find it here: http://forum.xda-developers.com/showthread.php?t=2425383
You can still flash the BL/TWRP package you downloaded already. It's the same as the one for CROMi-X.
Click to expand...
Click to collapse
Thanks, Honestly whatever custom rom I have now can randomly reboot and i think is giving me touch screen issues so was just going to hit up a stock install and see if that fixes any problems.
gonna try out the rom you suggested and i can always go back if necessary.
one thing, when i installed theTWRP the blue bar filled up completely and i left it for about 10 minutes and it was still there. so i powered down and everything booted back up correctly (and i can get into the recovery mode).
does everything sound ok to proceed?

gen1mx6 said:
Thanks, Honestly whatever custom rom I have now can randomly reboot and i think is giving me touch screen issues so was just going to hit up a stock install and see if that fixes any problems.
gonna try out the rom you suggested and i can always go back if necessary.
one thing, when i installed theTWRP the blue bar filled up completely and i left it for about 10 minutes and it was still there. so i powered down and everything booted back up correctly (and i can get into the recovery mode).
does everything sound ok to proceed?
Click to expand...
Click to collapse
You have to kick it out when it is completed by using the fastboot command or just using your power button.. So you are good to go...
You have to try out all the rom and kernels that are available then choose the best one that fit your need...Good luck...

LetMeKnow said:
You have to kick it out when it is completed by using the fastboot command or just using your power button.. So you are good to go...
You have to try out all the rom and kernels that are available then choose the best one that fit your need...Good luck...
Click to expand...
Click to collapse
thanks for the help, everything is complete and running correctly.