Hi I just received my xoom
I bought it off craigslist
I live in canada
the xoom has 4.0.3
what should I do first?
I am reading about gedify xoom
because I cannot get jelly bean ota
gedify the xoom will let it get jelly bean is that correct?
is that the right first step?
thanks
any sticky I should read first?
looking forward to the new forum
Thanks
I am thinking to try OTA jelly bean first before going into custom rom
valent|n0 said:
Hi I just received my xoom
I bought it off craigslist
I live in canada
the xoom has 4.0.3
what should I do first?
I am reading about gedify xoom
because I cannot get jelly bean ota
gedify the xoom will let it get jelly bean is that correct?
is that the right first step?
thanks
any sticky I should read first?
looking forward to the new forum
Thanks
I am thinking to try OTA jelly bean first before going into custom rom
Click to expand...
Click to collapse
Assuming you have a MZ604 Wifi Xoom:
1) You will need the Android SDK installed and working on a computer.
2) Download HWI69 for the Moto site (http://developer.motorola.com/products/software/) you may need to register first
3) Unlock the bootloader (will wipe all data)
adb reboot bootloader (wait for boot into bootloader)
fastboot oem unlock
4) Extract and run the following commands:
adb reboot bootloader (wait for the Tablet to reboot)
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Warning: Immediately re-lock your bootloader if you want to. Doing so after an OTA update will prevent the Xoom from booting.
5) When the Tablet reboots, let it go through the OTA process
HWI69 (HC 3.0.1) ->
HMJ37 (HC 3.1) ->
HTJ85B (HC 3.2) ->
HTK55D (HC 3.2.1) ->
HTK75D (HC 3.2.1) ->
IML77 (ICS 4.0.3) ->
IMM76D (ICS 4.0.4) ->
JRO03H (JB 4.1.1)
Thanks I like your list of the image name and the version
I follow this link www.simonjstuart.com for the tutorial, I now have Jelly bean OTA. I don't think I can last too long here. I already wanted a volume slider on the notification panel, and no app can do that as it seems only on custom rom??
Now I want to root
what is the step?
is it installing custom recovery first?
to do so I need to follow this http://forum.xda-developers.com/showthread.php?t=1074979
and download the recovery Recovery Image (solarnz-R4c-100611-1150)
and use Method 2 Without CWM
Quote:
Download the recovery image (not the zip file)
Pull up your command prompt, then
Code:
adb reboot bootloader
fastboot flash recovery recovery-solarnz-XXXXXX-XXXX.img
fastboot rebootLet your Xoom boot up. Then to check out your shiny new recovery,
Code:
adb reboot recovery
Related
Well I tried to install ICS, and right after the reboot, within 10 sec. the adroid w/ a exclamation mark came up and I cannot do anything. I can adb into it, but I do not know what to do after that.
I tried to do a fastboot reboot command, but it only says waiting for device.
I have unlocked and rooted the xoom, but I have not done anything else custom to it was was running stock honeycomb. Thanks for any help!
I was able to get it back up and working on honeycomb, however, it says the software is up to date... where did the ICS update go? Thanks.
I also took the ICS OTA update while my Xoom was 'rooted'.
- Wanted to see what would happen... and I also got the 'sick' android with '!'. Was more/less expecting it to fail though.
Workaround is to go back to stock/locked and then let the Xoom update itself into ICS (via OTA). Takes a few updates getting there.
Here's what I did:
Going back to stock:
--------------------------
1. Plug in your USB cord
2. Turn off your Xoom (Vol-Up + Power)
3. Boot into fastboot (Vol-Down + Power)
4. On your computer, open up a command prompt, and type the following:
fastboot flash boot <path to boot.img>
fastboot flash system <path to system.img>
fastboot flash recovery <path to recovery.img>
fastboot flash userdata <path userdata.img>
fastboot erase cache
fastboot oem lock
fastboot reboot
NOTE: The images came direct from Xoom (motodev)
An easier way... (for me at least) was to jump over to a custom ROM - from xda.
- I also 'wiped' the Xoom prior to loading the new ROM (per instructions).
Now running EOS IML74K Nightly 61 and getting better battery life as a result.
Thanks, and is the following:
http://forum.xda-developers.com/showthread.php?t=1049485
the right place for the stock images?
My xoom being a wifi only, I think the HWI69 should be right? Thanks.
I got mine direct:
http://developer.motorola.com/products/software/
MZ604_HWI69.zip
Build HWI69 for US Retail
MD5 Sum: 3f52762e56474070fa71bdf34ba9afd1
Requires that you sign-up to "motodev"
Assuming you already have the toolkit and USB drivers (since you rooted).
It'll take a few updates before you get to ICS. And, I think Xoom (stock) still has some issue with SDCards. I had to go back to original just to get CWM re-loaded - though I think CWM has an update that doesn't require SDCard access (it's late).
- I have a US Xoom, wifi only (refurb deal from NewEgg).
If you have unlocked your device then don't do the OTA updates as they have a chance of bricking your device...
I would recommend you to flash a recovery image (which you might have already done) then flash TeamEOS's rom onto your xoom. It works wonders on mine.
Hey all,
I read through quite a few threads here and am a bit confused.
I updated my UK Xoom 3G (MZ601) via OTA to 3.2 (H.6.5-17-3) a good while ago.
Recently, I got interested into rooting the device. So I launched the recovery mode on my Xoom (just to see if it works before I start flashing anything) and sadly, I get the green bot of ! there.
edit: solution in this thread!
So for now:
From my understanding here, there's only one way to fix this using ADB:
1) unlock bootloader
2) flash stock xoom dev rom (that would be H.6.1-38-1)
3) flash cwm
4) root
Even if all these steps were correct, wouldn't that mean I can impossibly OTA update to 3.2 as the device is already rooted (read somewhere it will cause issues when trying to update a rooted device)?
Even if I updated via OTA anyway it would overwrite CWM, wouldn't it?
I'd prefer to have a latest stock ROM + root as end result without a green bot interfering. Any advice is appreciated!
If I'm not mistaken you can root your device, using one of the Universal Root Tools on xda's xoom android development section.
I also rooted mine, using Xoot, I think it was called. Which will convert it into a GED device (wifi-only)
Or you can use Lord AIO's tool, which also worked fine, and then you can flash Team Eos' 2.0 Umts-everest (EU 3G) ROM over it.
Both have worked well for me.
Good luck! And let me know if you have any questions left!
found this that would do the trick for sure. As always, you're not the only one
Originally Posted by okantomi
"The green bot of !
there is one problem that exists with all xoom roots/cwm hacks. I had this problem as well as a bunch of other people when trying to flash CWM. If these files are present after an OTA update, then your xoom when entering recovery will show the green android robot with a exclaimation point instead of CWM.
If you have applied an official ota update.zip then you have a file like this on your xoom that will prevent CWM from working:
/system/recovery-from-boot.p /system/etc/install-recovery.sh
From the command window, type
adb remount adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
Or, if you do not already have root on your xoom when you get the green bot of ! then you have to do the following with the stock moto files for your device (from moto dev).
(This Wipes your Xoom )
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot -w
fastboot reboot
Do not relock! After your Xoom boots back up and goes into the setup screens skip setup and enable usb debugging.
Proceed to Step 4.1, above.
Click to expand...
Click to collapse
reference post: CWM + rooting issue solved here (no downgrading was needed):
http://forum.xda-developers.com/showthread.php?p=25998728
ACTUALLY I GOT THE ANSWER TO THESE QUESTIONS (ignore this thread)
I've been reading through this guide: http://forum.xda-developers.com/showthread.php?t=1249798
Question 1: When they say wipe everything, do they mean media too? (like music and such) Because when I had a samsung vibrant, they also said that but it never wiped media.
Question 2: Will I have to run a nandroid backup if this is my first time rooting, or will it be unnecessary?
Question 3: After finishing doing everything (unlocking and rooting)
do I just directly flash this http://forum.xda-developers.com/showthread.php?t=1484770 or is there something I need to do beforehand?
Also, in the guide, it says something about green android of ! if you have received an OTA. Which I have received many from Moto before. Will I have to download the original motorola files (HC or ICS, I'm currently on ICS)? If so, where do I put it? I'm confused
okantomi said:
"The green bot of !
there is one problem that exists with all xoom roots/cwm hacks. I had this problem as well as a bunch of other people when trying to flash CWM. If these files are present after an OTA update, then your xoom when entering recovery will show the green android robot with a exclaimation point instead of CWM.
If you have applied an official ota update.zip then you have a file like this on your xoom that will prevent CWM from working:
/system/recovery-from-boot.p /system/etc/install-recovery.sh
From the command window, type
adb remount adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
Or, if you do not already have root on your xoom when you get the green bot of ! then you have to do the following with the stock moto files for your device (from moto dev).
(This Wipes your Xoom )
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot -w
fastboot reboot
Do not relock! After your Xoom boots back up and goes into the setup screens skip setup and enable usb debugging.
Proceed to Step 4.1, above.
Click to expand...
Click to collapse
Thanks so much! I'm new to this, it's so much different from rooting my Samsung Vibrant phone
cmd hangs
"Or, if you do not already have root on your xoom when you get the green bot of ! then you have to do the following with the stock moto files for your device (from moto dev).
(This Wipes your Xoom )
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot -w
fastboot reboot
Do not relock! After your Xoom boots back up and goes into the setup screens skip setup and enable usb debugging.
Proceed to Step 4.1, above. "
I did the above steps. All my command prompt does is hang...waiting for the xoom to respond.
rosystreasures said:
"Or, if you do not already have root on your xoom when you get the green bot of ! then you have to do the following with the stock moto files for your device (from moto dev).
(This Wipes your Xoom )
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot -w
fastboot reboot
Do not relock! After your Xoom boots back up and goes into the setup screens skip setup and enable usb debugging.
Proceed to Step 4.1, above. "
I did the above steps. All my command prompt does is hang...waiting for the xoom to respond.
Click to expand...
Click to collapse
There may be something wrong with my instructions...they've gotten convoluted over time. Try one of the other guides in General..there are a couple of newer ones that might work better. Mine still gives a lot of information but I think I'll retire it 'cause I don't want to cause issues.
I recently rooted and flashed a rom on my xoom. I'm a simple point and click windows user and I didn't have much trouble, so it's not that hard to do.
[HOW TO][UPDATED GUIDE] Unlocking & Rooting your XOOM!
http://forum.xda-developers.com/showthread.php?t=1477024
is the thread I used. Follow the instructions exactly and read the entire thread before you start, it'll save you a few headaches. This'll get you in (I think) ICS with superuser and all that jazz. If you want a rom, like me, then you'll have to head over to the development forum and take your pick. I'm running EOS 2.0, still deciding what to do with my xoom atm.
I wish I'd known of this thread last night. I struggled for several hours to root. It finally did. I also got the rom installed.
rosystreasures said:
I wish I'd known of this thread last night. I struggled for several hours to root. It finally did. I also got the rom installed.
Click to expand...
Click to collapse
I'm glad you got it rooted. That newer guide skips some steps that were needed earlier but are no longer needed. Like I said, I will retire my guide as too confusing now.
Quickboot vs. ROM manager
okantomi said:
I'm glad you got it rooted. That newer guide skips some steps that were needed earlier but are no longer needed. Like I said, I will retire my guide as too confusing now.
Click to expand...
Click to collapse
I started out with the standard 3.2 on my Xoom Wifi
with a nagging system message to update (I am guessing 3.2.2)
So I followed thread 1249798 and now am unlocke & rooted!
I am also using Recovery: Eos Recovery R6
I still get the nagging system message to update.
I would like to load a custom ROM, probably Moray.
My questions are this:
1. Will the Nagging system update message cause a
problem loading a custom ROM?
2. I could use the process as described in thread 1249798
to load the ROM, but I have read that since I am rooted
I could use Quick Boot app. Is this true? What about the
ROM Manager app, could I use this to load Moray? What is
the difference?
3. Since my base is 3.2 I am guessing I cannot load any
EOS ICS Rom's, is this correct? I need to bring my base
to 4.0 right?
4. Both Hammerhead and Moray state that they are both:
"Pre rooted with su and Superuser". Does this mean I did
not have to root my Xoom, I could have just loaded either
of these Roms and become rooted?
5. I have read some comments about:
/system/etc/install-recovery.sh
If I remove this file, will this stop the nagging System Update message?
6. Do I need to back anything up prior to loading a ROM?
Thanks!
Still with that, you can flash TEAM EOS ROM ICS. just boot into recovery and flash the TEAM EOS ROM. Mine was 3.2.1 as well. GOOD LUCK
I originally followed the steps below to unlock and root my stock TF300 (had already updated to Jelly Bean prior to unlocking). Now that there is a new Jelly Bean update file, how do update my system (have TWRP). I'm a noob and don't want to screw it up. Thanks!!
1) Download these 2 files:
- Jellybean recovery with fastboot files: Fastboot files + JB recovery
- Root files: Root Files
- You can also download the new CWM Touch recovery if you don't like TWRP: CWM Touch recovery thread
2) Extract the recovery with fastboot files zip and open a command prompt in the same folder of the adb and fastboot files (Shift + Right mouse)
3) Reboot into the bootloader of your tablet, type: adb reboot bootloader
4) When your tablet has reached the bootloader navigate with volume down to the usb icon and press volume up to confirm.
5) To flash the recovery type:
- TWRP: fastboot -i 0x0b05 flash recovery tf300t-jb.blob
- CWM: fastboot -i 0x0b05 flash recovery CWM-Touch.blob
6) A blue bar will appear and the recovery will be installed, when the blue bar is filled press volume up + power button to reboot into the tablet.
Now we will root the tablet
7) Copy Superuser-3.2-RC3-arm-signed to the internal storage of your tablet. then reboot into the bootloader again.
8) This time you need to select the RCK icon with volume up to enter the recovery image.
9) In recovery flash Superuser-3.2-RC3-arm-signed and reboot into the system
10) Install Supersu from Google Play
11) Open up Supersu, it will ask you to update the binary, choose yes.
12) Now your tablet should be rooted
I'm in the same boat, I installed JB then unlocked bootloader and installed TWRP. 100% stock just rooted and need some help installing the new JB update without wiping.
With my Samsung S3 it was easy to do just download the full firmware and flash it and it would just update the system and I would not loose any apps or settings. I hope this is the case with TF300 as well.
I have downloaded the full firmware off Asus website and just need to flash it, I remember reading a thread that this can be done using recovery and does not wipe. I'm not a noob with flashing I just don't want to wipe and want to make sure.
So please if someone can confirm flashing the full firmware from Asus site using TWRP will not wipe the device?
I don't care about root since i can flash the root zip file using TWRP later I just don't want the tablet to wipe.
EDIT:
Based on this it would seem its simple just flash the full firmware from Asus website and then flash TWRP again and then root it.
Thanks, I went ahead and did the flash and root and it worked just fine!
EDIT:
Based on this it would seem its simple just flash the full firmware from Asus website and then flash TWRP again and then root it.[/QUOTE]
Well my dumb fast moving self has backfired once again. While using chain fire 3D I have now got myself stuck in a boot loop. I have tried wipe data both from menu and from paperclip. I have tried getting latest firmware from asus site and using RCK but for some reason it just shows me a dead DROID. So any tips would be great I can't send it back because it's unlocked and rooted. So if anyone knows of a way to get RCK or the wipe data's to work I would be forever in your debt
Sevyth said:
Well my dumb fast moving self has backfired once again. While using chain fire 3D I have now got myself stuck in a boot loop. I have tried wipe data both from menu and from paperclip. I have tried getting latest firmware from asus site and using RCK but for some reason it just shows me a dead DROID. So any tips would be great I can't send it back because it's unlocked and rooted. So if anyone knows of a way to get RCK or the wipe data's to work I would be forever in your debt
Click to expand...
Click to collapse
You have to flash TWRP recovery via fastboot. BUT, be sure to flash the correct version of TWRP. Flashing the wrong TWRP recovery blob can brick your tablet.
Since, you did not mention the firmware version running on your tablet, we can only guess...
If you were on Android 4.0.x (also known as Ice Cream Sandwich or ICS), you need to flash TWRP blob with "-ICS" suffix. For example, openrecovery-twrp-2.4.4.0-tf300t-ICS.blob.
If you were on Android 4.1.x (also known as JellyBean or JB) before ASUS firmware version 10.6.1.8, you need to flash TWRP blob with "-JB" suffix. For example, openrecovery-twrp-2.4.4.0-tf300t-JB.blob.
If you were on ASUS firmware version 10.6.1.8 (Android 4.2.1) you need to flash openrecovery-twrp-2.4.4.0-tf300t-4.2.blob.
If you were on ASUS firmware version 10.6.1.15.3 (Android 4.2.1) you need to flash openrecovery-twrp-2.5.0.0-tf300t-4.2.blob.
And, if you have TF300TG model, get the TWRP blob with -tf300tg-. Once again, flashing the incorrect TWRP can brick your tablet. So, please be extra careful.
To download the necessary TWRP recovery blob files, and for the instructions on how to flash it to your tablet, visit the TWRP official website for TF300T(G) here: http://www.teamw.in/project/twrp2/97
After flashing the correct TWRP recovery, you can now launch the TWRP recovery via RCK. From there, you can flash ASUS stock firmware to fix your bootloop. I would recommend following method 3 outlined in the GUIDE found here: http://forum.xda-developers.com/showthread.php?t=2187982
How is this supose to work if my RCK always shows a dead DROID. And how do I get fast boot to work when fast boot freeze when I click the usb icon
"If you were on Android 4.1.x (also known as JellyBean or JB) before ASUS firmware version 10.6.1.8, you need to flash TWRP blob with "-JB" suffix. For example, openrecovery-twrp-2.4.4.0-tf300t-JB.blob."
I believeThis is the Firmware i was On but im still not sure how to get fastboot to work. or RCK
EDIT: Seems that Link you provided to learn how to put the recovery on is out of date,
EDIT II: "You will need fastboot for this method. Download the above file, check the md5, rename to twrp.blob and put the file in the same directory as your fastboot.exe (unless you have /platform-tools in PATH then you can flash from anywhere). Turn off your device and boot to fastboot (power on while holding volume down, then select the usb icon and hit volume up to confirm). The device will now be in fastboot mode. Plug the device into your computer. Run the following command via the command line:
fastboot -i 0x0B05 flash recovery twrp.blob" - Will ya translate to english , And as I said when i go into fastboot mode and click the USB icon it freezes.
EDIT III: 10.4.2.20 is my model # i belive
EDIT IIII : Downloaded fastboot But cant run it . i open fastboot and it just closes. Any ideas?