Database Info

[DEV HELP!] My Canadian Xoom Wifi fails to boot on HRI39.

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!

[Q] Need Fix To Green Bot of ! Problem

A problem currently exists with newer Xooms when attempts are made to flash ClockworkMod 3.2.0.0 (R4c) (CMW) into the Recovery partition. This issue has been mentioned in several threads with no resolution to date.
This is what the problem seems to be:
- Fact: There was no problem flashing ClockWorkMod (CWM) to older (earlier versions than 3.2.1).
- Fact: The problem occurred with attempts to flash later versions of Android, e.g., 3.2.1 following update via OTA.
- Fact: The OTA has an incompatibility with CWM. Joe Ferreira identified the problem as one of the following files being present that will prevent CWM from working:
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
- Fact: The proposed fix involves reverting to an earlier version, i.e., 3.0 and updating to 3.2.1 via OTA. This fix is yet unproven.
- Fact: Owners of newer Xooms are being prevented from achieving root because of this problem (including myself)
To summarize:
1) Recent OTAs which bring the Xoom to 3.2.1 are incompatible with the ClockworkMod 3.2.0.0 (R4c) image (CWM)
2) Once flashed CWM is inaccessible.
This is the problem that needs to be resolved.
Note: Epic118 has suggested reverting to 3.0; updating via OTA to 3.2.1; and rerunning Xoot. I don't understand this since attempting to flash CWM on 3.2.1 updated via OTA will repeat the same issue. Perhaps EPIC118 can provide clarification.
Does anyone have a solution/fix to this problem?

microi said:
A problem currently exists with newer Xooms when attempts are made to flash ClockworkMod 3.2.0.0 (R4c) (CMW) into the Recovery partition. This issue has been mentioned in several threads with no resolution to date.
This is what the problem seems to be:
- Fact: There was no problem flashing ClockWorkMod (CWM) to older (earlier versions than 3.2.1).
- Fact: The problem occurred with attempts to flash later versions of Android, e.g., 3.2.1 following update via OTA.
- Fact: The OTA has an incompatibility with CWM. Joe Ferreira identified the problem as one of the following files being present that will prevent CWM from working:
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
- Fact: The proposed fix involves reverting to an earlier version, i.e., 3.0 and updating to 3.2.1 via OTA. This fix is yet unproven.
- Fact: Owners of newer Xooms are being prevented from achieving root because of this problem (including myself)
To summarize:
1) Recent OTAs which bring the Xoom to 3.2.1 are incompatible with the ClockworkMod 3.2.0.0 (R4c) image (CWM)
2) Once flashed CWM is inaccessible.
This is the problem that needs to be resolved.
Note: Epic118 has suggested reverting to 3.0; updating via OTA to 3.2.1; and rerunning Xoot. I don't understand this since attempting to flash CWM on 3.2.1 updated via OTA will repeat the same issue. Perhaps EPIC118 can provide clarification.
Does anyone have a solution/fix to this problem?
Click to expand...
Click to collapse
How about reverting to stock 3.0.1, then OTA updating to 3.2 and then rooting/flashing recovery and custom rom/kernel. I would think the issue is with the 3.2.1 OTA update itself.

I'm not completely sure I understand but if u can try this,
Download the universal root update zip and put it on your xoom
Flash clockwork through fastboot and then reboot into recovery, don't let it boot or the install recovery.sh will delete clockwork!
Flash the universal root.zip and boot up and use a root file manager to delete those two file and clockwork should stick through a reboot
Sent from my ADR6400L using Tapatalk

Hi
I have a UK Xoom and I am interested in putting a custom ICS on it. I have read through all of the pages of the excellent guide to unlocking and rooting etc started by okantomi. Fair play to all involved, its a great source of information.
My Xoom is showing 3.2 as the current version. When I bought it a few months ago it had 3.0 installed. I updated OTA to 3.1 and more recently to 3.2. I then got a small update a few weeks back but Android version is still showing as 3.2. Am I good to go ahead?

bandit197 said:
Hi
I have a UK Xoom and I am interested in putting a custom ICS on it. I have read through all of the pages of the excellent guide to unlocking and rooting etc started by okantomi. Fair play to all involved, its a great source of information.
My Xoom is showing 3.2 as the current version. When I bought it a few months ago it had 3.0 installed. I updated OTA to 3.1 and more recently to 3.2. I then got a small update a few weeks back but Android version is still showing as 3.2. Am I good to go ahead?
Click to expand...
Click to collapse
I'm not sure what update (after the 3.2 update) added the security "fix" that seems to cause the problem, but you might as well try to root. If it doesn't work, at least you have a potential work-around, but hopefully it will be fine.
Good luck.

okantomi said:
I'm not sure what update (after the 3.2 update) added the security "fix" that seems to cause the problem, but you might as well try to root. If it doesn't work, at least you have a potential work-around, but hopefully it will be fine.
Good luck.
Click to expand...
Click to collapse
Cheers, I went ahead with it and it worked out no problems, unlocked, rooted and I can access recovery. Ill post the details in the guide thread to keep everything in the one place.

Superchilpil,
Thank you for your reply.
There are a few points I don't fully understand.
You indicate,
Flash clockwork through fastboot and then reboot into recovery, don't let it boot or the install recovery.sh will delete clockwork!
Click to expand...
Click to collapse
1) Should I reboot into recovery using fastboot or simply reboot the Xoom using "Vol+ and Power"?
2) You indicate, "Don't let it boot". I don't understand; if I initiate a 'reboot', it reboots. How can I prevent it from rebooting???
This is the code I will use to flash Clockwork:
adb reboot bootloader
fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
Click to expand...
Click to collapse
What code should I use to effect your suggested approach?
One last question. The objective of this question is to understand if I can simply flash the "Universal Root Update Zip" to obtain root using the stock Recovery Mode, then install ClockworkMod Recovery; then remove one or the other of two problematic security files which are currently causing a problem. This will theoretically resolve the "Green Bot of !" issue Xoom users with 3.2.1 are currently experiencing.
After unlocking the bootloader, is it possible to:
1) Flash Update.zip (from the MicroSD card) using the stock Recovery Mode
2) Flash ClockworkMod Recovery through fastboot
3) Obtain root from this procedure
Thank you in advance.
Microi

microi said:
Superchilpil,
Thank you for your reply.
There are a few points I don't fully understand.
You indicate,
1) Should I reboot into recovery using fastboot or simply reboot the Xoom using "Vol+ and Power"?
2) You indicate, "Don't let it boot". I don't understand; if I initiate a 'reboot', it reboots. How can I prevent it from rebooting???
This is the code I will use to flash Clockwork:
What code should I use to effect your suggested approach?
One last question. The objective of this question is to understand if I can simply flash the "Universal Root Update Zip" to obtain root using the stock Recovery Mode, then install ClockworkMod Recovery; then remove one or the other of two problematic security files which are currently causing a problem. This will theoretically resolve the "Green Bot of !" issue Xoom users with 3.2.1 are currently experiencing.
After unlocking the bootloader, is it possible to:
1) Flash Update.zip (from the MicroSD card) using the stock Recovery Mode
2) Flash ClockworkMod Recovery through fastboot
3) Obtain root from this procedure
Thank you in advance.
Microi
Click to expand...
Click to collapse
by not letting it boot I mean don't let it boot into the rom, and both of those methods u stated will work just fine to reboot
And flash it using whatever method you desire, but I forgot to mention that you may need to flash clockwork again after you boot and delete those files because the install recovery.sh obviously flashes the stock recovery and the point of my method is to keep a custom recovery on your device
I know for a fact that the stock recovery mode won't flash anything you will find here in the forums that I know of
Sent from my Xoom using Tapatalk

superchilpil said:
I know for a fact that the stock recovery mode won't flash anything you will find here in the forums that I know of
Click to expand...
Click to collapse
Correct, the stock recovery requires that the zip files be signed with keys that only the manufacturers have access to. This is the whole reason why we have to flash a third party recovery to begin with.

teameos said:
Correct, the stock recovery requires that the zip files be signed with keys that only the manufacturers have access to. This is the whole reason why we have to flash a third party recovery to begin with.
Click to expand...
Click to collapse
I'm getting more and more confused the more times I read this.!!
I have done the update then unlocked to find I now have the green bot!!!!!
Someone please send a simple step by step with some file links to revert back to stock 3.2!
Thanks

I was HC stock, locked, unrooted, had accepted all OTA's - and therefore had the problem with the 2 files mentioned in the OP. I updated to ICS just fine. In order to root, I did the following (the differences from the standard instructions are underlined)
unlock
flash recovery
boot into recovery
root
then while still in CWM, no reboot, but instead:
adb remount
adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
reboot with CWM
Only had to flash CWM once.

willysp said:
I was HC stock, locked, unrooted, had accepted all OTA's - and therefore had the problem with the 2 files mentioned in the OP. I updated to ICS just fine. In order to root, I did the following (the differences from the standard instructions are underlined)
unlock
flash recovery
boot into recovery
root
then while still in CWM, no reboot, but instead:
adb remount
adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
reboot with CWM
Only had to flash CWM once.
Click to expand...
Click to collapse
Thanks. This makes a lot of sense. I would like to edit my rooting guide and give this procedure as the preferred approach. Is there anything you would want to add to it?

Just as a Fyi, these files are on all Android os, not something new. You can also flash an insecure boot image, and it will stop these from running.
adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
Sent from my Nexus S 4G

okantomi said:
Thanks. This makes a lot of sense. I would like to edit my rooting guide and give this procedure as the preferred approach. Is there anything you would want to add to it?
Click to expand...
Click to collapse
Hi,
First - thanks for your rooting guide - I used it with the exception of my underlined steps which were a synthesis of what I saw in a few other places.
Nothing to add - except perhaps really emphasize to keep the USB cable connected, and after rooting, do not reboot, stay in CWM, and use adb to run the 3 commands. You wrote a very detailed guide, so know you'll do a great job writing the expanded version of my short underlined additions. As you obviously know, many of the less technical users need a more detailed explanation of my underlined changes.
Thanks again for the help your guide gave me!
---------- Post added at 07:19 AM ---------- Previous post was at 07:14 AM ----------
bwcorvus said:
Just as a Fyi, these files are on all Android os, not something new. You can also flash an insecure boot image, and it will stop these from running.
adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
Sent from my Nexus S 4G
Click to expand...
Click to collapse
Yes, I saw them mentioned re several devices as I googled.
But - are you saying they were present in stock Xoom HC? Everything I've read says they were added in the 3.2 OTA, since people who are on 3.1 don't have these files to deal with.

willysp said:
But - are you saying they were present in stock Xoom HC? Everything I've read says they were added in the 3.2 OTA, since people who are on 3.1 don't have these files to deal with.
Click to expand...
Click to collapse
These are a _function_ of the OTA process. When there are kernel or recovery updates required, the stock recovery partition requires patching, hence these files.

ydaraishy said:
These are a _function_ of the OTA process. When there are kernel or recovery updates required, the stock recovery partition requires patching, hence these files.
Click to expand...
Click to collapse
Thanks, that helps explain what they are. So, if an OTA (like 3.2 apparently) wants to patch/replace stock recovery, those are the files that do it on next boot. Would be nice if they deleted themselves when done (from a hacker's POV), but for people running stock, I guess it makes sense for the OS to check the recovery partition at each boot and overwrite it with stock recovery if needed.

willysp said:
Hi,
First - thanks for your rooting guide - I used it with the exception of my underlined steps which were a synthesis of what I saw in a few other places.
Nothing to add - except perhaps really emphasize to keep the USB cable connected, and after rooting, do not reboot, stay in CWM, and use adb to run the 3 commands. You wrote a very detailed guide, so know you'll do a great job writing the expanded version of my short underlined additions. As you obviously know, many of the less technical users need a more detailed explanation of my underlined changes.
Thanks again for the help your guide gave me!
---------- Post added at 07:19 AM ---------- Previous post was at 07:14 AM ----------
Yes, I saw them mentioned re several devices as I googled.
But - are you saying they were present in stock Xoom HC? Everything I've read says they were added in the 3.2 OTA, since people who are on 3.1 don't have these files to deal with.
Click to expand...
Click to collapse
I'm no expert, but I will try to put it together based on the info in this thread, but please correct me if I'm wrong.

okantomi said:
I'm no expert, but I will try to put it together based on the info in this thread, but please correct me if I'm wrong.
Click to expand...
Click to collapse
Sure - glad to.

Yes these files were on the stock Xoom. Infact it helped us get some of the dumps. We would flash cwm, then dump, then let the OS rebuild the recovery. We then flashed cwm to boot and dumped the stock recovery.
Sent from my Nexus S 4G

bwcorvus said:
Yes these files were on the stock Xoom. Infact it helped us get some of the dumps. We would flash cwm, then dump, then let the OS rebuild the recovery. We then flashed cwm to boot and dumped the stock recovery.
Sent from my Nexus S 4G
Click to expand...
Click to collapse
Thanks for the info.

How to root Xoom with Android 4.1.1?

I have looked all over the forums and I can not find it. All the forums show how to root a Xoom with Honeycomb or Ice Cream Sandwich TO Jellybean, but what if i already have JellyBean? I just want to get superuser access onto the stock Jellybean ROM and Kernel.
This Link:
http://forum.xda-developers.com/showthread.php?t=1796335
Has been the most useful so far, but even it only roots Ice Cream Sandwich.
How do I root Android 4.1.1 on my Motorola Xoom with 4.1.1.

This should work! Flash it in recovery

What do I need?
matt4321 said:
This should work! Flash it in recovery
Click to expand...
Click to collapse
Do I need to have clockwork mod installed or anything, i have done NOTHING root to my xoom. I rooted my HTC EVO 4G. But i havent flashed a recovery, installed a ROM, No SU, NOTHING. So what exactly should i do with your zip?

Use instructions and tools in http://forum.xda-developers.com/showthread.php?t=1468298 to get Clockwork installed, and then use the modded zip that matt4321 posted (I think that should work... )

Yeah use the AIO tool to unlock your bootloader, then you want to install CWM recovery, then boot into recovery and flash the zip I uploaded

I used this exact process (ended up just GEDify'ing it after sending it back to stock), but before I did that everything worked fine.

Thank you!
I'm too junior to get a Thanks button, so thank you to matt4321 for the JB universal XOOM root, to airesch for leading me too XxLordxX's link and of course to XxLordxX for the tools and instructions to get my XOOM rooted! Worked perfect on my XOOM WIFI JRO03H with no problems. You guys are the best!:good:

stuck on Starting Fastboot Protocol Support - Xoom Android 4.1
I'm trying to follow the directions to install ClockworkMod Recovery
http://forum.xda-developers.com/showthread.php?t=1074979
I'm using Recovery Image (solarnz-R4c-100611-1150) FLASHED THROUGH FASTBOOT
MD5: 20575d4b62bf697f77abca9093877ea3
and following the procedure for "Method 2 Without CWM"
I got as far as entering the code: adb reboot bootloader
The Xoom rebooted and the Motorola logo appears with the message "Starting Fastboot Protocol Support"
It's just stuck there.
The volume up/down buttons don't do anything at this point.
Any ideas?
thanks!

themonman said:
I'm trying to follow the directions to install ClockworkMod Recovery
http://forum.xda-developers.com/showthread.php?t=1074979
I'm using Recovery Image (solarnz-R4c-100611-1150) FLASHED THROUGH FASTBOOT
MD5: 20575d4b62bf697f77abca9093877ea3
and following the procedure for "Method 2 Without CWM"
I got as far as entering the code: adb reboot bootloader
The Xoom rebooted and the Motorola logo appears with the message "Starting Fastboot Protocol Support"
It's just stuck there.
The volume up/down buttons don't do anything at this point.
Any ideas?
thanks!
Click to expand...
Click to collapse
Here, detailed procedure with snapshots.
http://forum.xda-developers.com/showthread.php?p=29733454

N00b tutorial: Flashing EOS3 to MZ604 Xoom (Wifi)
Hi,
thanks for the url.
One problem.
And the most important, download EOS-RECOVERY-V6, the "recovery software" that will allow you to work without the need of the PC:
Recovery Image: http://goo.im/devs/teameos/recoveries/wingray/eos-recovery-r6.img
This link goes to a file not found page.
Any update on where I can get that file?
thanks!
wesamothman said:
Here, detailed procedure with snapshots.
http://forum.xda-developers.com/showthread.php?p=29733454
Click to expand...
Click to collapse

themonman said:
Hi,
thanks for the url.
One problem.
And the most important, download EOS-RECOVERY-V6, the "recovery software" that will allow you to work without the need of the PC:
Recovery Image: http://goo.im/devs/teameos/recoveries/wingray/eos-recovery-r6.img
This link goes to a file not found page.
Any update on where I can get that file?
thanks!
Click to expand...
Click to collapse
You have to use another recovery. Eos-r6 was abandoned and another recovery came in as the perfect one. TWRP recovery
http://forum.xda-developers.com/showthread.php?p=28988754

matt4321 said:
This should work! Flash it in recovery
Click to expand...
Click to collapse
Matt,
Is this file appropriate for the WiFi only Xoom?
I installed TWRPv2.8.0.0-Wingray-Non-BigPart on my Xoom. That process went flawlessly.
I used TWRP to install "vanilla" Xoom-Universal-Root.zip. This also appeared to go flawlessly.
However, various root checker apps tell me I do NOT have root.
Please, any suggestions? I ultimately want to get to BigPart but I'm stuck at this point.
thanks,
Dave

vronp said:
Matt,
Is this file appropriate for the WiFi only Xoom?
I installed TWRPv2.8.0.0-Wingray-Non-BigPart on my Xoom. That process went flawlessly.
I used TWRP to install "vanilla" Xoom-Universal-Root.zip. This also appeared to go flawlessly.
However, various root checker apps tell me I do NOT have root.
Please, any suggestions? I ultimately want to get to BigPart but I'm stuck at this point.
thanks,
Dave
Click to expand...
Click to collapse
Yeah, that zip should be good to root any Xoom on 4.1. I wouldn't bother sorting root if you want to go to bigpart as it wipes everything anyway.
Jump straight to bigpart, read read and read again this thread: https://forum.xda-developers.com/showthread.php?t=2506997
Once that is all sorted and booted, I think you should be good to just flash whatever root tool you want (SuperSU, phh superuser etc)
My memory is rusty on all this though, I haven't messed with my xoom in a long time and you quoted a post over 4 years old lol

Xoom bricked

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.

[Solved] Bricked TF300T?

Hello all,
Greetings and let me get straight to the point. First, sorry for being a noob. Basically, I was trying to install this "[ROM][LP 5.0.0_r2] [ KatKiss-Lollipop #003 ] [F2FS] [Beta]" on the TF300T US version on the latest bootloader. I entered TWRP and did a full wipe like I would always do to install a new rom. My last rom was the Omnirom Nightlies, which I have been using for some time now. The problem comes in here, I performed the usual procedures, but now, after installing the new rom ([ROM][LP 5.0.0_r2] [ KatKiss-Lollipop #003 ] [F2FS] [Beta]), it wouldn't boot (stuck at Katkiss logo) for a full hour, so I went back to the recovery and tried to reinstall the Omnirom and gapps that were always in my SD card. However, the log says it couldn't mount the system and data. I clicked the "Mount" button in TWRP and it says my storage is 0 mb! Now, I couldn't install anything or get it to boot. Is there a way to fix this?
Thanks in advance.

golddragon97 said:
Hello all,
Greetings and let me get straight to the point. First, sorry for being a noob. Basically, I was trying to install this "[ROM][LP 5.0.0_r2] [ KatKiss-Lollipop #003 ] [F2FS] [Beta]" on the TF300T US version on the latest bootloader. I entered TWRP and did a full wipe like I would always do to install a new rom. My last rom was the Omnirom Nightlies, which I have been using for some time now. The problem comes in here, I performed the usual procedures, but now, after installing the new rom ([ROM][LP 5.0.0_r2] [ KatKiss-Lollipop #003 ] [F2FS] [Beta]), it wouldn't boot (stuck at Katkiss logo) for a full hour, so I went back to the recovery and tried to reinstall the Omnirom and gapps that were always in my SD card. However, the log says it couldn't mount the system and data. I clicked the "Mount" button in TWRP and it says my storage is 0 mb! Now, I couldn't install anything or get it to boot. Is there a way to fix this?
Thanks in advance.
Click to expand...
Click to collapse
I have exactly the same problem.
My system storage is 0mb and doesnt boot the operating system
I can only boot to twrp.
Any help will be welcome.

Try reinstalling the stock ROM.

Berend de Boer said:
Try reinstalling the stock ROM.
Click to expand...
Click to collapse
I've tried, but fastboot won't open on my computer (I open it and it closes) and the only accessible place on my tablet is the TWRP recovery.

KenshiInukawa said:
I have exactly the same problem.
My system storage is 0mb and doesnt boot the operating system
I can only boot to twrp.
Any help will be welcome.
Click to expand...
Click to collapse
I finally had time to fix my tablet today and this time it worked, but much patience was needed. In summary, it wasn't the rom that screwed me up, it was me being stupid by wiping the data and then flashing a new version of TWRP without a rom installed, which leads to bricking.
I highly recommend that you revert the tablet back to the stock rom before trying to install another custom rom. To revert back to the stock rom, first download the firmware from Asus' website (http://support.asus.com/Download.aspx?SLanguage=en&m=ASUS+Transformer+Pad+TF300T&p=28&s=1) no parentheses. This is for the TF300T only, not the TL or TG models; if you have the other two models, just Google your tablet's model number+firmware and it is better if you download it off Asus' website and also beware of which countries' SKU you are downloading (Mine is the US version, so it is like this: "Version US_V10.6.1.27.5". Extract the zip file until you get a 'blob' file of around 800 MB.
Instructions:
First of all, get your TF300T into Fastboot Mode by pressing the VOL- and POWER buttons and you will see three icons labeled 'RCK', the android robot, and the "Wipe Data" icon.
Second, download Java JDK and Android SDK and... Follow the instructions from this website: (http://www.teamandroid.com/2012/07/30/how-to-set-up-adb-fastboot-with-android-sdk/) no parentheses.
Note: Even though the instructions are for entering fastboot on a Galaxy Nexus, it should also work for the TF300T as it did for me. Once again, be patient and follow instructions step-by-step to set up Fastboot on your computer (assuming it runs on Windows).
Third, in the folder where you have the system 'blob' file, look at steps 10-12 on this website (http://www.android.gs/restore-asus-transformer-pad-tf300t-to-stock-android-4-0-3-ics-firmware/) no parentheses.
Lastly, reboot and there you have a working TF300T and you become a happy tablet owner!
EXTRA: If you want to install a custom rom, follow these instructions: (http://forum.xda-developers.com/showthread.php?t=2579922) no parentheses.
Sorry if my guide was bad; it was brief and this is basically what a 17-year-old inexperienced noob myself could do and explain. If you followed all the instructions on the websites above, you should be able to fix your dilemma.
Good luck and happy Thanksgiving!

golddragon97 said:
I finally had time to fix my tablet today and this time it worked, but much patience was needed. In summary, it wasn't the rom that screwed me up, it was me being stupid by wiping the data and then flashing a new version of TWRP without a rom installed, which leads to bricking.
I highly recommend that you revert the tablet back to the stock rom before trying to install another custom rom. To revert back to the stock rom, first download the firmware from Asus' website (http://support.asus.com/Download.aspx?SLanguage=en&m=ASUS+Transformer+Pad+TF300T&p=28&s=1) no parentheses. This is for the TF300T only, not the TL or TG models; if you have the other two models, just Google your tablet's model number+firmware and it is better if you download it off Asus' website and also beware of which countries' SKU you are downloading (Mine is the US version, so it is like this: "Version US_V10.6.1.27.5". Extract the zip file until you get a 'blob' file of around 800 MB.
Instructions:
First of all, get your TF300T into Fastboot Mode by pressing the VOL- and POWER buttons and you will see three icons labeled 'RCK', the android robot, and the "Wipe Data" icon.
Second, download Java JDK and Android SDK and... Follow the instructions from this website: (http://www.teamandroid.com/2012/07/30/how-to-set-up-adb-fastboot-with-android-sdk/) no parentheses.
Note: Even though the instructions are for entering fastboot on a Galaxy Nexus, it should also work for the TF300T as it did for me. Once again, be patient and follow instructions step-by-step to set up Fastboot on your computer (assuming it runs on Windows).
Third, in the folder where you have the system 'blob' file, look at steps 10-12 on this website (http://www.android.gs/restore-asus-transformer-pad-tf300t-to-stock-android-4-0-3-ics-firmware/) no parentheses.
Lastly, reboot and there you have a working TF300T and you become a happy tablet owner!
EXTRA: If you want to install a custom rom, follow these instructions: (http://forum.xda-developers.com/showthread.php?t=2579922) no parentheses.
Sorry if my guide was bad; it was brief and this is basically what a 17-year-old inexperienced noob myself could do and explain. If you followed all the instructions on the websites above, you should be able to fix your dilemma.
Good luck and happy Thanksgiving!
Click to expand...
Click to collapse
Hey great to see you up and running.....
Can you add "SOLVED' to the thread title.....
Thx Josh

lj50036 said:
Hey great to see you up and running.....
Can you add "SOLVED' to the thread title.....
Thx Josh
Click to expand...
Click to collapse
how do i do that?

golddragon97 said:
how do i do that?
Click to expand...
Click to collapse
Go to your first post and say you want to edit it then choose adv edit ....
Thx Josh