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.
Related
Hi All!
I would like to convert my completely stock non-rooted Canadian Wifi Xoom (MZ604) into a US xoom so that I can install the 3.1 software on it, as well as root, sdcard capable kernel, and CWM recovery.
Unfortunately, after reading many many of the threads here, I am totally confused as to what order to follow. Here is what I'm thinking, but please please correct me if I am wrong:
[steps removed]
Is that it? I feel like I'm missing something or that I may brick my device since it is not a US-rom that I am using as a base.
Thanks for the help!
[update 28th May]: The steps that I followed to get 3.1 with CWM & Tiamat on my Canadian Xoom are below, in post #7.
1. boot the device into fastboot and unlock it. Erase all cache and wipe the userdata.
2. Flash the complete US 3.0.1 HWI69 ROM. (yes, do this)
2.1 Root the 3.0.1 Rom
3. Install CWM recovery from http://forum.xda-developers.com/show....php?t=1074979 using the fastboot method.
4. Install the 3.1 update from http://forum.xda-developers.com/show....php?t=1074609, skipping the 3G step since I only have Wifi.
5. Install Tiamat 1.4.2 from http://forum.xda-developers.com/showthread.php?t=978013. (update to one of the newest kernels)
6. Install International Language Pack from http://forum.xda-developers.com/show....php?t=1083612 to get back all languages from 3.0.1 ROM.
Click to expand...
Click to collapse
Note the comments and you should be fine. Good luck.
jase33 said:
Note the comments and you should be fine. Good luck.
Click to expand...
Click to collapse
For your suggested step "2.1 Root the 3.0.1 Rom", would the thread at http://forum.xda-developers.com/showthread.php?t=1010568 be the suggested strategy?
that will work
So did you do all that you said ? Did it work ?
i'm about to do my candian wifi xoom !
Thanks
I was hesitant to do that since I am reading a lot of bricking stories lately, I have a canadian MZ604 stock too, will do the same if you succeed!
Alright folks, It's been a few days now since I've updated my Xoom, so here's the process that I used. Note that it is different from the steps I listed in the original post:
1. Unlock the device via fastboot. Instructions here. DO NOT RE-LOCK EVER!!
2. Flash the Official & complete US 3.0.1 HWI69 ROM. Links here. Every time I tried to download the "does not require login" version from mediafire I got a corrupted zip, so instead I downloaded from the Motorola developer site (with instructions) here.
3. Once the 3.0.1 Rom was up and running, and I had an internet connection, I got the OTA notification for the 3.1 update and installed it. It took about 10 minutes to notify me once I had connection, probably because it had to download it before notifying me. After the install and reboot process, I had a stock 3.1 install, but still didn't have sdcard access. So, I kept going.
4. Install CWM 3.0.2.8 recovery, using the fastboot method. Instructions here.
Once CWM was installed and I had the ability to backup the rom, I immediately made a backup before EACH of the following steps was performed. I know it is overkill to make that many backups, but I wanted to be sure I wasn't going to screw up my device at any given step and have to start over again.
5. Root the 3.1 rom from here. After rooting I had sdcard access within honeycomb at /sdcard/external.
6. Installed Tiamat 1.4.2 kernel. Instructions here.
7. Installed the Language Pack from here, but when I rebooted the system it went into a loop on the purple animated honeycomb logo. So, I rebooted into recovery again, and did a "wipe data / factory reset" - this allowed my machine to reboot normally, but I had to reconfigure all my settings and reinstall all my apps.
So as of right now I'm on 3.1 HMJ37, rooted, with CWM recovery, Tiamat kernel, and have international languages! It's great!!
Mike.
Thanks for the detailed info... I flashed the complete US 3.0.1 ROM on my canadian xoom and got the 3.1 OTA update as well. So now my canadian wifi xoom is on US 3.1 !
I will not root it for now since i don't really need the external SDcard for now.
When you say Flash US 3.0.1 ...do you have steps to do that? I'm just wondering how to do it...since I don't have a functional SD Card I guess its not the flash update.zip method...
Can't wait to be running the US rom and not care for motorola Canada anymore!!!
Just saw that the steps to flash the rom are on moto website! Sorry!
How to flash
I've spent hours on this and I guess I must be stupid, but I can NOT figure out how to flash a ROM! I've tried the ADB commands, I've download the ROM manager, etc, etc, etc...I cannot find any instructions on how to do this! It must be very simple because every time I look for instructions, they always just say "flash the ROM" like it's nothing. But HOW???
Very frustrating...there appears to be no single place that outlines all the steps in one place - it takes a dozen web pages to do the simplest things...
I also want to update my Canadian ROM to a US ROM. I'm unlocked, I'm running Tiamat 1.3.0 but I don't know what to do now...?
It seems as though having an external micro SD card supported is a prerequisite, but I cannot figure out how to get that to work either. The frustrating part of all this is that I do (Windows) computer support - I'm not new to technology in any way, but I have seldom been more frustrated than this trying to find one set of clear instructions...!
HELP!
Thanks.
after flashing using the instructions on post number 7 with the HRI39 bin images and fastboot my tablet doesnt boot. it just sits at the motorla logo for ages and ages and ages...
do I maybe have to wait like an hour or something?
Converted my MZ604 Singapore version to US & OTA update to 3.1
I managed to reflash International images to US and OTA update to 3.1 using a mod microUSB cable. I didn't need to root my xoom to do it rather a hardwired method.
2. Flash the Official & complete US 3.0.1 HWI69 ROM. Links here. Every time I tried to download the "does not require login" version from mediafire I got a corrupted zip, so instead I downloaded from the Motorola developer site (with instructions) here.
Click to expand...
Click to collapse
Can you please elaborate on how we do this? How do we flash a ROM? I only know how to do it in CWM Recovery, but not elsewhere.
Enhanced said:
Can you please elaborate on how we do this? How do we flash a ROM? I only know how to do it in CWM Recovery, but not elsewhere.
Click to expand...
Click to collapse
Ok, hook your xoom up to your computer and open up a command line. Then CD to your tools directory of the android sdk and input these commands.
adb reboot fastboot
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot reboot
And your good to go..... continue from the next step just be carefully to input the commands exactly, and for the love of Pete DONT UNPLUG your xoom while flashing
And do NOT relock!!
Sent from my Xoom using XDA Premium App
I will be attempting this in the next day or so but had a few newbie questions (coming over from the apple world):
1) For step two, the img files all come from HWI69.zip?
2) For step four, do I want to do it with CWM or without? Is there more risk to one vs. the other?
3) For step six, to boot into recovery mode, is the following sequence correct?
Turn your XOOM off
Press Power to turn your XOOM back on
When the Motorola Dual Core boot screen appears tap Volume Down repeatedly until "Android Recovery" is displayed
Press Volume Up to enter Recovery
Thanks,
masterslacker said:
Alright folks, It's been a few days now since I've updated my Xoom, so here's the process that I used. Note that it is different from the steps I listed in the original post:
1. Unlock the device via fastboot. Instructions here. DO NOT RE-LOCK EVER!!
2. Flash the Official & complete US 3.0.1 HWI69 ROM. Links here. Every time I tried to download the "does not require login" version from mediafire I got a corrupted zip, so instead I downloaded from the Motorola developer site (with instructions) here.
3. Once the 3.0.1 Rom was up and running, and I had an internet connection, I got the OTA notification for the 3.1 update and installed it. It took about 10 minutes to notify me once I had connection, probably because it had to download it before notifying me. After the install and reboot process, I had a stock 3.1 install, but still didn't have sdcard access. So, I kept going.
4. Install CWM 3.0.2.8 recovery, using the fastboot method. Instructions here.
Once CWM was installed and I had the ability to backup the rom, I immediately made a backup before EACH of the following steps was performed. I know it is overkill to make that many backups, but I wanted to be sure I wasn't going to screw up my device at any given step and have to start over again.
5. Root the 3.1 rom from here. After rooting I had sdcard access within honeycomb at /sdcard/external.
6. Installed Tiamat 1.4.2 kernel. Instructions here.
7. Installed the Language Pack from here, but when I rebooted the system it went into a loop on the purple animated honeycomb logo. So, I rebooted into recovery again, and did a "wipe data / factory reset" - this allowed my machine to reboot normally, but I had to reconfigure all my settings and reinstall all my apps.
So as of right now I'm on 3.1 HMJ37, rooted, with CWM recovery, Tiamat kernel, and have international languages! It's great!!
Mike.
Click to expand...
Click to collapse
rezadue said:
I will be attempting this in the next day or so but had a few newbie questions (coming over from the apple world):
1) For step two, the img files all come from HWI69.zip?
2) For step four, do I want to do it with CWM or without? Is there more risk to one vs. the other?
3) For step six, to boot into recovery mode, is the following sequence correct?
Turn your XOOM off
Press Power to turn your XOOM back on
When the Motorola Dual Core boot screen appears tap Volume Down repeatedly until "Android Recovery" is displayed
Press Volume Up to enter Recovery
Thanks,
Click to expand...
Click to collapse
1) Correct - also, I know I keep saying this, but on the Moto site instructions for flashing they tell you to relock. Don't!!
2) I used the fastboot method (without). Make sure to download the img and not the zip.
3) I tend to wait on the Moto logo for about 3 secs then just press down once. Then up once you get the recovery option. Never fails.
Good luck.
Great. Thanks for the quick response. One additional question. This procedure seems a fair bit shorter in length than this one:
http://forum.xda-developers.com/showthread.php?t=1073884
Is there a reason? Is there a place where I can read some sort of a beginner's guide to rooting so I can understand the steps I am going to be following better?
Thanks again.
burden010 said:
1) Correct - also, I know I keep saying this, but on the Moto site instructions for flashing they tell you to relock. Don't!!
2) I used the fastboot method (without). Make sure to download the img and not the zip.
3) I tend to wait on the Moto logo for about 3 secs then just press down once. Then up once you get the recovery option. Never fails.
Good luck.
Click to expand...
Click to collapse
Relock
masterslacker said:
1. Unlock the device via fastboot. Instructions here. DO NOT RE-LOCK EVER!!
Click to expand...
Click to collapse
Question : why shouldn't we "RE-LOCK EVER" ?
I ask because I've relocked mine after flashing Europe stock on my US Xoom (I [stupidly] did what I saw on motorola dev instructions...).
Hey there guys
So I flashed my device as per these instructions:
1. Unlock the device via fastboot. Instructions here. DO NOT RE-LOCK EVER!!
2. Flash the Official & complete US 3.0.1 HWI69 ROM. Links here. Every time I tried to download the "does not require login" version from mediafire I got a corrupted zip, so instead I downloaded from the Motorola developer site (with instructions) here.
3. Once the 3.0.1 Rom was up and running, and I had an internet connection, I got the OTA notification for the 3.1 update and installed it. It took about 10 minutes to notify me once I had connection, probably because it had to download it before notifying me. After the install and reboot process, I had a stock 3.1 install, but still didn't have sdcard access. So, I kept going.
4. Install CWM 3.0.2.8 recovery, using the fastboot method. Instructions here.
Once CWM was installed and I had the ability to backup the rom, I immediately made a backup before EACH of the following steps was performed. I know it is overkill to make that many backups, but I wanted to be sure I wasn't going to screw up my device at any given step and have to start over again.
5. Root the 3.1 rom from here. After rooting I had sdcard access within honeycomb at /sdcard/external.
6. Installed Tiamat 1.4.2 kernel. Instructions here.
7. Installed the Language Pack from here, but when I rebooted the system it went into a loop on the purple animated honeycomb logo. So, I rebooted into recovery again, and did a "wipe data / factory reset" - this allowed my machine to reboot normally, but I had to reconfigure all my settings and reinstall all my apps.
Click to expand...
Click to collapse
After flashing the images from the HRI39 zip from MotoDEV it did not work. My device wont boot. I have reflashed back to stock for the Canadian Xoom and that works just fine again, But I'd like to know why it wont boot with the other one since MANY people have done it without a problem.
I have executed these commands:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
Then manual reboot... simply sits at the motorola logo.
This is my 3rd attempt. Still nothing.
If anyone can provide some solid support it would be greatly appreciated.
Not sure, as i don't have that model, but i would recommend posting in Q&A.
Sent From My Evo
I believe you're trying to use the vzw version on a wifi only xoom, that'll fail everytime. Find your version at the link.
http://forum.xda-developers.com/showthread.php?t=1049485
davidsos said:
I believe you're trying to use the vzw version on a wifi only xoom, that'll fail everytime. Find your version at the link.
http://forum.xda-developers.com/showthread.php?t=1049485
Click to expand...
Click to collapse
Thank you!!
I just realized your right. HRI39 is VZ. I need US WIFI which according to moto is HW69
seven2099 said:
Thank you!!
I just realized your right. HRI39 is VZ. I need US WIFI which according to moto is HW69
Click to expand...
Click to collapse
Glad you figured it out!
Hi there everyone,
I have a huge problem. Last night i bricked my xoom. I was following a tutorial on this forum. and after unlocking the bootloader it told to flash a file called boot.img after doing so and typing fastboot reboot, the device wouldnt start behind the motorola logo. i tried allot of thing and also did flash some other stock android 4.0.4 boot.img files now with the last one mentioned i managed to get the xoom (wifi) to boot a little further. because the ripple movie with the motorola logo is shown. but it stucks at that movie.
Does anyone know if i can flash an image on the xoom that will atleast fix the problem of not rebooting so i can try another tutorial.
I have searched the internet for solutions, many of them linked to threads on this forum. but almost all download links in these tutorials are old and broken.
Can someone please help me unbrick my device? And maybe a link to a good working unroot tutorial for my xoom wifi with android 4.0.4.
Try get back to Stock.
Download from HERE
and do some OTA updates afterwards so everything will be up to date.
Then wipe and try again from scratch..
Worked for me perfectly just a few days ago.
If you can still get into fastboot, then its not bricked.
Get some stock images and flash them via fastboot and you'll be fine.
Cubanluke88 said:
If you can still get into fastboot, then its not bricked.
Get some stock images and flash them via fastboot and you'll be fine.
Click to expand...
Click to collapse
Indeed it worked. i downloaded the official images and flashed them im on android 3.0.1 again and all seems to work just fine now.
Next problem is i cant find a descent tutorial on this forum how to root the xoom. all download links are either removed due to copyright issues or the links are just broken.
How does it work actually?
1. I unlocked the boot loader wich is very easy.
but then? Do i need to flash a rooted image over the existing? i dont really understand how this works. I rooted my Desire HD with a good tutorial in minutes. Not many people seems to really know how to root the Xoom.
Also i would like to know if the different tutorials are for different android versions or can i aply all tutorials of rooting when i stay on android 3.0.1?
I also tried to flash a recovery.img to the recovery partition and press volume down 3 seconds after the moto logo apears but when i do i get an android robot with a big " ! " on his belly and it takes 5 minutes to load the menu. when im in it tells me there is no sdcard present when i try to flash a rooted rom (zip file).
Is there someone reading this thats willin to explain to me how to do a root the easiest way? Please if links are posted be sure everything on that thread is working. Im pretty sure i will pull it off with some push in the right direction.
Thank you!
(edit) omg im stupid, offcourse the sdcard wont work... it never worked at 3.0.1. on the xoom. can i follow this tutorial:
http://rootzwiki.com/topic/451-how-to-root-the-wifi-only-xoom-301/
Could someone read over it and see if this is a good tutorial? last time i flashed a boot.img the whole xoom got stuck... is that because i had the wrong boot.img on the wrong android version? or should boot.img always work?
Do you plan on flashing to a custom rom after rooting? If so, you can just skip rooting altogether.
I say this because I'm not particularly familiar with that rooting method you linked (though reading through it, it makes sense, all its doing is pushing the necessary files for root access to the xoom via adb). I used a rooting script flashed through a custom recovery over a year ago - unfortunately the download link seems to be broken (I might have a copy at home).
So there's a few things you can do:
1. If you just want a custom rom - download the rom zip file and store on your device. Flash TWRP (my preferred recovery) in fastboot. Boot into TWRP and flash the rom zip file.
2. If you want stock OS root access -
a) Follow those steps you linked and see what happens. If things go wrong, you should be able to just flash those stock images again.
b) Wait for me to get home and see if I have the root script. You'll need to flash a custom recovery though in order to use it.
Cubanluke88 said:
Do you plan on flashing to a custom rom after rooting? If so, you can just skip rooting altogether.
I say this because I'm not particularly familiar with that rooting method you linked (though reading through it, it makes sense, all its doing is pushing the necessary files for root access to the xoom via adb). I used a rooting script flashed through a custom recovery over a year ago - unfortunately the download link seems to be broken (I might have a copy at home).
So there's a few things you can do:
1. If you just want a custom rom - download the rom zip file and store on your device. Flash TWRP (my preferred recovery) in fastboot. Boot into TWRP and flash the rom zip file.
2. If you want stock OS root access -
a) Follow those steps you linked and see what happens. If things go wrong, you should be able to just flash those stock images again.
b) Wait for me to get home and see if I have the root script. You'll need to flash a custom recovery though in order to use it.
Click to expand...
Click to collapse
Ok thanks for your answer. Ill try to unroot with that method flashing directly to the recovery.img i also know now what i did wrong. i flashed the recovery.img not to the recovery partition but to the boot partition LOL. thats why the xoom didnt boot anymore
I see allot about Nightlies Eos, 4.1.1. is that a good rom? Does it look like the stock version?
eos 4.1.1 is simply awesome and its also pre rooted' so your bootloader is unlocked, all you gotta do now is install twrp recovery via fastboot ( my preffered recovery) then flash eos via recovery
Sent from my Xoom using XDA Premium App
sygys said:
Ok thanks for your answer. Ill try to unroot with that method flashing directly to the recovery.img i also know now what i did wrong. i flashed the recovery.img not to the recovery partition but to the boot partition LOL. thats why the xoom didnt boot anymore
I see allot about Nightlies Eos, 4.1.1. is that a good rom? Does it look like the stock version?
Click to expand...
Click to collapse
EOS is a pretty AOSP rom. No theme, though you can apply one if you like and change a few colors. There are various toggle additions you can add that make the user experience much better. It also comes with an overclockable kernel and is very very stable (despite being a nightly) The team has been supporting the Xoom for over a year and is very committed to the Xoom.
---------- Post added at 01:15 PM ---------- Previous post was at 01:11 PM ----------
sygys said:
Ok thanks for your answer. Ill try to unroot with that method flashing directly to the recovery.img i also know now what i did wrong. i flashed the recovery.img not to the recovery partition but to the boot partition LOL. thats why the xoom didnt boot anymore
I see allot about Nightlies Eos, 4.1.1. is that a good rom? Does it look like the stock version?
Click to expand...
Click to collapse
As for flashing, just gotta make sure your text is good before hitting the enter key. Recovery flash should look something like this:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Some instructions for flashing can be found here
While that page is specifically for locking and flashing to return to stock, the commands are universal for fastboot. Hell, if you wanted to, you could manually restore a nandroid backup via fastboot and flashing images.
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
Now this makes absolutely zero sense. Here are the steps I followed during the short time (~3 weeks) I have had my TF700:
- Root Tablet
- Use Root Apps
- Unlock Bootloader
- Use Root Apps
- Set Up NvFlash
- Use Root Apps
- Install TWRP Via GooManager
- Use Root Apps
- Update TWRP Via GooManager (using the exact same method used on first install, maybe I did this wrong?)
- Flash US Sku JB via TWRP
- Use Root Apps (actually one of the things I did was try to apply a max CPU value and use the performance Governor via ROM Toolbox Pro)
I included the times I know for a fact that I used applications that require root access. I flashed JB on Monday night, then let the ROM break in overnight and was used very lightly since. Then just a few minutes ago I go into Voodoo to backup and protect my root before applying the minor update and it's telling me that I don't have root access. Then I fire up SuperSU to confirm and low and behold it informs me that there is no root binary present and that it can not install it. So then I reboot to recovery to see if I can just flash su from TWRP and I get the stock Andy laying on his back with his case open and a red exclamation point screen.
How in the hell could this have happened? Can I just re-root using the new JB method then re-install TWRP?
This really concerns me, it baffles me how this could have happened... Any help is greatly appreciated.
Sent from my unlocked Transformer Infinity
Would I be able to just download the newest TWRP, rename it recovery.blob, boot into fastboot, then execute the following commands:
fastboot -i 0x0B05 flash recovery recovery.img
fastboot -i 0x0B05 reboot
then flash SuperSU from there? Sorry if this is an obvious question.
Sent from my unlocked Transformer Infinity
Issue resolved, but I would still like to find out exactly what happened so I can potentially avoid this situation in the future.
Sent from my unlocked Transformer Infinity
I_EAT_BABIES said:
- Flash US Sku JB via TWRP
Click to expand...
Click to collapse
The stock firmware contains the stock recovery, so installing it overwrites your custom one.
_that said:
The stock firmware contains the stock recovery, so installing it overwrites your custom one.
Click to expand...
Click to collapse
^^this
_that said:
The stock firmware contains the stock recovery, so installing it overwrites your custom one.
Click to expand...
Click to collapse
Ah that makes sense. I'm glad it was supposed to happen; what had me worried was the possibility that something odd happened. Thanks!
Sent from my unlocked Transformer Infinity