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.
I've installed Nvflash and have grabbed the files intended for restore per the instructions. Now I'd like to restore my tablet. I'm on .26 with TRWP installed and am having issues restoring stock recovery. I want to upgrade to .30, then jb. My only known alternative is to use Nvflash. So, can someone point me in the direction of instructions for this process?
devlop said:
I've installed Nvflash and have grabbed the files intended for restore per the instructions. Now I'd like to restore my tablet. I'm on .26 with TRWP installed and am having issues restoring stock recovery. I want to upgrade to .30, then jb. My only known alternative is to use Nvflash. So, can someone point me in the direction of instructions for this process?
Click to expand...
Click to collapse
You do have unlocked boot loader right?
http://forum.xda-developers.com/showthread.php?t=1803343
Yep, unlocked bootloader. The link you provided is what I've been trying to do. Just like the other person at the end of the thread, I get a signature error during boot and my recovery remains custom with TWRP. I'm not sure what the problem is, this is why I am considering nvflash.
devlop said:
Yep, unlocked bootloader. The link you provided is what I've been trying to do. Just like the other person at the end of the thread, I get a signature error during boot and my recovery remains custom with TWRP. I'm not sure what the problem is, this is why I am considering nvflash.
Click to expand...
Click to collapse
If it's not working for you, you could try to downgrade to .22. Basically, download full .22 version, extract, renamed and copy to your SDcard then use twrp to flash.
How to downgrade.
http://forum.xda-developers.com/showpost.php?p=30223822&postcount=1
EDIT: On a second note, why you want to restore back to "stock recovery"??
devlop said:
I've installed Nvflash and have grabbed the files intended for restore per the instructions. Now I'd like to restore my tablet. I'm on .26 with TRWP installed and am having issues restoring stock recovery. I want to upgrade to .30, then jb. My only known alternative is to use Nvflash. So, can someone point me in the direction of instructions for this process?
Click to expand...
Click to collapse
you don't have to use nvflash for this,just download JB from Asus site and install with TWRP,done.Why you need o complicate your life?
Hmmm, I thought the process for getting to jb was to first upgrade to .30. From what I've searched through, I've only found instructions to upgrade to .30 by means of stock recovery. Is it possible to jump straight to jb from .26?
devlop said:
Hmmm, I thought the process for getting to jb was to first upgrade to .30. From what I've searched through, I've only found instructions to upgrade to .30 by means of stock recovery. Is it possible to jump straight to jb from .26?
Click to expand...
Click to collapse
haha, I doubt that anyone here have tried to go directly from .26 to JB, You probably the first if you try. Why don't you twrp to .30 and let the OTA to JB? based on my knowledge, OTA upgrade one version at a time.
Perhaps I have some info wrong. I can install the factory updates with TWRP? I don't need stock recovery?
devlop said:
Perhaps I have some info wrong. I can install the factory updates with TWRP? I don't need stock recovery?
Click to expand...
Click to collapse
OK let start over. This is how i would do this:
1. Downloaded .26 from Asus site.
2. Unzip and moved the zipfile inside to root of internal sd card.( /mnt/sdcard)
3. Rebooted, your device should found the update and prompt you to update, flashed the update. You should be back on .26 with stock recovery and unrooted.
4. Reroot and download OTA root keeper to save root. Run root keeper to save root
5. OTA to .30. (if OTA is not working, let me know).
buhohitr said:
OK let start over. This is how i would do this:
1. Downloaded .26 from Asus site.
2. Unzip and moved the zipfile inside to root of internal sd card.( /mnt/sdcard)
3. Rebooted, your device should found the update and prompt you to update, flashed the update. You should be back on .26 with stock recovery and unrooted.
4. Reroot and download OTA root keeper to save root. Run root keeper to save root
5. OTA to .30. (if OTA is not working, let me know).
Click to expand...
Click to collapse
I'm already on .26. Should I be downloading .30? Also, even though I have TWRP installed, the tablet should still pick up the fact that there is an update on the memory? Just a side note, I'm unlocked, so ota's will not work for me.
devlop said:
I'm already on .26. Should I be downloading .30? Also, even though I have TWRP installed, the tablet should still pick up the fact that there is an update on the memory? Just a side note, I'm unlocked, so ota's will not work for me.
Click to expand...
Click to collapse
Sure if you want to, download .30. Tablet should pick it up, make sure you unzip it first. Yes, you're correct you have to upgrade using manual process. Every methods here on XDA are not 100% work for everyone (you already knew that). But it should work for most ppl.
Great. I appreciate your help. I'm at work, tablet's at home. I'll give this a go tonight and report back.
buhohitr said:
haha, I doubt that anyone here have tried to go directly from .26 to JB, You probably the first if you try. Why don't you twrp to .30 and let the OTA to JB? based on my knowledge, OTA upgrade one version at a time.
Click to expand...
Click to collapse
Mate do you actually know what you are saying? The JB firmware from Asus site it's a full rom not just an OTA (incremental) update, this means you can update from any version (do you see any word from Asus saying you must be on. 30 before installing?) because everything will be updated (BL, Kernel, etc) so installing this with TWRP will get you Full Stock JB (yes, you will loose twrp too).
Pretoriano80 said:
Mate do you actually know what you are saying? The JB firmware from Asus site it's a full rom not just an OTA (incremental) update, this means you can update from any version (do you see any word from Asus saying you must be on. 30 before installing?) because everything will be updated (BL, Kernel, etc) so installing this with TWRP will get you Full Stock JB (yes, you will loose twrp too).
Click to expand...
Click to collapse
I'm not disagree with you! just saying no one here have tried to go straight before. The only question here is the bootloader between .26 and JB is different and why Asus pre upgrade to .30 before JB? IDK, maybe there is a reason, maybe not. Some how I think they need to prep the bootloader on .30 to be ready for JB? again I don't know.
buhohitr said:
I'm not disagree with you! just saying no one here have tried to go straight before. The only question here is the bootloader between .26 and JB is different and why Asus pre upgrade to .30 before JB? IDK, maybe there is a reason, maybe not. Some how I think they need to prep the bootloader on .30 to be ready for JB? again I don't know.
Click to expand...
Click to collapse
My personal opinion on that is that Asus did this because they made a mess by letting people install TF300T Jelly Bean on TF700T (that should never be possible with locked bootloader and official firmware) so they updated the bootloader on .30 update so ppl could downgrade from that tf300t Jelly Bean rom.Maybe i'm wrong,but it does make sense and if i'm not wrong TF700T is the only transformer device that can downgrade from JB to ICS so easily.
Good news, I was able to flash .30 and now jb. I had no idea it was that simple. I thought I had to be back on stock recovery. Thanks for the help guys.
devlop said:
Good news, I was able to flash .30 and now jb. I had no idea it was that simple. I thought I had to be back on stock recovery. Thanks for the help guys.
Click to expand...
Click to collapse
Guys you can just install the JB firmware from asus. Unzip, flash that file in twrp and boom straight from .26 to JB with no issues. It even keeps all your data.
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
Hello, I am confused. I have heard some people have issues after installing nvflash and then installing a custom recovery. I notice that they are both flashed to the address "0x0b05". Will this cause a problem? For instance, recovery overwrites NVflash or vice versa.
Thanks. Any guidance appreciated
ostar2 said:
Hello, I am confused. I have heard some people have issues after installing nvflash and then installing a custom recovery. I notice that they are both flashed to the address "0x0b05". Will this cause a problem? For instance, recovery overwrites NVflash or vice versa.
Click to expand...
Click to collapse
You do not "install" nvflash. nvflash is a tool that runs on a PC. For using it with the TF700, you first need to flash a hacked bootloader and run a tool to extract a blob file from your tablet. Then you save this blob on your PC and keep it safe. This blob is used with the "wheelie" tool, which prepares the communication with the tablet, so that you finally can use nvflash.
And 0x0b05 is not an address, it is the vendor part of the Transformer's USB ID.
You should read the nvflash-related threads thoroughly, this should clean up some of your confusion. Do not try the procedure before you know what you are doing!
thankyou for clarifying that for me. In this case I have one other question, what are the chances that flashing the bootloader would fail and brick the device?
ostar2 said:
what are the chances that flashing the bootloader would fail and brick the device?
Click to expand...
Click to collapse
It worked fine for me, but for a well-founded answer, we would need some statistical data.
I'd say the chances are greater than 0, but not much, if you know what you are doing. At least I do not know any reports of bricking by flashing the bootloader - all recent bricks I read about in this forum were a result of using some inappropriate way to flash a custom recovery and then trying to wipe data.
_that said:
It worked fine for me, but for a well-founded answer, we would need some statistical data.
I'd say the chances are greater than 0, but not much, if you know what you are doing. At least I do not know any reports of bricking by flashing the bootloader - all recent bricks I read about in this forum were a result of using some inappropriate way to flash a custom recovery and then trying to wipe data.
Click to expand...
Click to collapse
Well, if thats the case poll or survey should be done. Also, I have been back and forth about nvflash and what happens if I flash the Asus jb update after installing the custom bootloader? Will it overwrite the custom bootloader? Thanks.
ostar2 said:
Well, if thats the case poll or survey should be done. Also, I have been back and forth about nvflash and what happens if I flash the Asus jb update after installing the custom bootloader? Will it overwrite the custom bootloader? Thanks.
Click to expand...
Click to collapse
Yes, it will overwrite the custom bootloader. But at that time you should already have pulled your blob and stored it safely on your PC and backed it up multiple times, so you don't need the custom bootloader anymore - it is only required for extracting the blob, not for running nvflash.
Ok, thanks. I just needed to be sure of what would happen. I will install the custom bootloader and recovery, generate blobs and preform nvflash backup. I am still unsure if I want to use the stock ROM with a custom recovery or if I want to use cm10 with a custom recovery.
I am definitly going to use cm10 or cm10.1, custom bootloader with twrp recovery after here that Asus spies on what you do with your tablet.
ostar2 said:
I am definitly going to use cm10 or cm10.1, custom bootloader with twrp recovery after here that Asus spies on what you do with your tablet.
Click to expand...
Click to collapse
Just FYI: CleanROM does not include CMClient and DMClient.
Thanks, I still think I am going to go with cyanogenmod 10.1 when it comes out.
At this point I don't want create $499.99 paper weight.
I have read that nvflash can cause a bootloop. Is this true?
ostar2 said:
I have read that nvflash can cause a bootloop. Is this true?
Click to expand...
Click to collapse
Where did you read that?
Improper use of nvflash can cause all kinds of malfunction, however proper use of nvflash should always be able to repair that (if you have backups).
I read this
d14b0ll0s said:
-----------------------------------------------------------------------------------+
Apps to avoid (causing bootloops etc.)
Beats Audio - see why
Wallpaper Wizardrii - see why
Transformer reboot to recovery - see why
NVFlash = softbrick
CMClient (stock) - see why you should probably
disable it (unless you desire constant surveillance)
LCD Density - see why
Click to expand...
Click to collapse
Here: http://forum.xda-developers.com/showthread.php?t=1764480
_that said:
Where did you read that?
Improper use of nvflash can cause all kinds of malfunction, however proper use of nvflash should always be able to repair that (if you have backups).
Click to expand...
Click to collapse
Also, are there any detailed guides on how install nvflash?
ostar2 said:
Also, are there any detailed guides on how install nvflash?
Click to expand...
Click to collapse
This is the guide: http://androidroot.mobi/t3_nvflash/
Make sure you understand exactly what you are doing before you begin. It's easier to do on a Linux PC because of fewer driver issues.
_that said:
This is the guide: http://androidroot.mobi/t3_nvflash/
Make sure you understand exactly what you are doing before you begin. It's easier to do on a Linux PC because of fewer driver issues.
Click to expand...
Click to collapse
Mainly what I am confused about is this: Do I need any extra blob files to install nvflash other than the ones listed?
I understand that you need to backup the "generated" blob files. If so, where would I get them?
Read the guide again. You do not "install" nvflash, the guide describes the procedure of using a hacked bootloader to extract data (the blob) needed to run nvflash.
_that said:
Read the guide again. You do not "install" nvflash, the guide describes the procedure of using a hacked bootloader to extract data (the blob) needed to run nvflash.
Click to expand...
Click to collapse
I know. When I said install nvflash I was referring to the "AndroidRoot" bootloader.
ostar2 said:
I know. When I said install nvflash I was referring to the "AndroidRoot" bootloader.
Click to expand...
Click to collapse
To install that, you need only the files available on the AndroidRoot site and a working fastboot setup.
Hello all, yes, this are going to be a very noob questions, but I do not want to end up with bricked device, so lets start.
1. After OTA upgrading TF300T from 4.0.x to 4.2.1, it made my device absolutely useless, well I am gamer and lot of my games just start lagging, extremely lagging, i have made factorial, reinstal, but not helps at all, so I decided to make it hard way.
2.I have never edited Android, so after studying lot of threats I have install adb, asus drivers and made a root via motochopper, which allows you root access but your bootloader will remain lock.
3.But what now??? (next steps is only my theory)
Can i just unlock bootloader via Unlock Device App: Unlock boot loader from ASUS support site (after success it will reboot or something) and then flash ClockworkMod recovery via ROM Manager? And then I just download CleanRom and put it on sd and just flash it and it will be all?
As I said, I have no idea, no idea which rom is the best fo gaming, which ClockworkMod recovery is the best for my device and if that Unlock Device App will working ... or even if my theory is right. Also I have som knowledge about fastboot but every quide was for 4.1 non rooted only. This is my very first post, so please be permissive.
Thank you for answers.
ASUS Transformer TF300T 4.2.1 stock but rooted with locked bootloader, WW sku
You will want to unlock your device with the Asus tool first.
Then you will want to install TWRP, I don't think CWM is working right on 4.2. Twrp works flawlessly. You will want to make sure you get the correct version of TWRP for 4.2, or you may brick your device. It will be called twrp-2.5.0.0-tf300t-4.2.blob . the important part of the filename is the -4.2
This is the link for it. http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.5.0.0-tf300t-4.2.blob
You will want to use that on the Asus 10.6.1.15.3 firmware.
rename the .blob file to twrp.blob
You will need to flash through command prompt while device is in fastboot mode with the command:
fastboot -i 0x0B05 flash recovery twrp.blob
Then put you desired rom on your SD card and flash away. I recommend trying CROMI, very fast, stable, and polished.
There are excellent tutorials in the general section. this one is particularly good: http://forum.xda-developers.com/showthread.php?t=2187982
You will want to read, read and read again. You could build a house with all of the bricks here. Don't rush into anything or you will join the club.
Sent from my SCH-I510 using xda app-developers app
Reilly1812 said:
You will want to read, read and read again. You could build a house with all of the bricks here. Don't rush into anything or you will join the club.
Sent from my SCH-I510 using xda app-developers app
Click to expand...
Click to collapse
That would be some house. +1 to this sentiment though. It's not hard, but there are risks to consider.
CBank said:
You will want to unlock your device with the Asus tool first.
Then you will want to install TWRP, I don't think CWM is working right on 4.2. Twrp works flawlessly. You will want to make sure you get the correct version of TWRP for 4.2, or you may brick your device. It will be called twrp-2.5.0.0-tf300t-4.2.blob . the important part of the filename is the -4.2
This is the link for it. http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.5.0.0-tf300t-4.2.blob
You will want to use that on the Asus 10.6.1.15.3 firmware.
rename the .blob file to twrp.blob
You will need to flash through command prompt while device is in fastboot mode with the command:
fastboot -i 0x0B05 flash recovery twrp.blob
Then put you desired rom on your SD card and flash away. I recommend trying CROMI, very fast, stable, and polished.
There are excellent tutorials in the general section. this one is particularly good: http://forum.xda-developers.com/showthread.php?t=2187982
Click to expand...
Click to collapse
thank you very much for the guide, of course, I will asking about every step I do not understand well. I will start next week (because school) but now I can safety unlock bootloader via Asus App. thx
Reilly1812 said:
You will want to read, read and read again. You could build a house with all of the bricks here. Don't rush into anything or you will join the club.
Sent from my SCH-I510 using xda app-developers app
Click to expand...
Click to collapse
I couldn't have said it better myself.
Read, read, and read some more. If you have questions, ask.
Sent from my C525c using Xparent SkyBlue Tapatalk 2
Success
I just did all of this on my TF300T today and can confirm that it works without issues. I just did them in a slightly different order... I'll explain the entire process. First, I downloaded the newest official firmware listed on Asus's website, put that shizzy on my MicroSD, plugged it into my device, booted, and waited. If you do not automatically receive an update notification, head to your settings and press, "Check for Updates" (that is what I had to do). Once you finally get the message to update to the firmware on your SD Card, accept and wait for the process to finish. Next, I rooted my tablet with motochopper. Then, I downloaded the correct version of twrp from the site. If you update your TF300T to the latest official firmware on Asus's website, you will need to downloaded the .blob ending in -4.2 (and place it in the root of your, "sdcard," directory). Finally, I installed the custom recovery through terminal. SUCCESS! Best of luck, man!