Idiot's guide to flashing the Xoom (for fun and profit)

[pingvinen]

I'll retry being more precise. I do get into Recovery and I flash the file mentioned. It seems it flashes correctly but when I boot into the OS, there's no signs of root anywhere.

I'll update in a few. Thanks!

Sent from my T-Mobile G2 using Tapatalk

There are no error messages or anything weird happening during step 5, is there?

 

[rmcsc]

There are no error messages or anything weird happening during step 5, is there?

No, none. That's the thing. It flashes perfectly. Anybody would believe it works.

What build do you have? I'm just curious now.

Sent from my T-Mobile G2 using Tapatalk

 

[pingvinen]

No, none. That's the thing. It flashes perfectly. Anybody would believe it works.

What build do you have? I'm just curious now.

Sent from my T-Mobile G2 using Tapatalk

Build HMJ37

 

[rmcsc]

Build HMJ37

Okay, so the build isn't the difference...

[Edit] I do note, however, that I have a kernel installed without having started step 6. It says it's Tiamat 1.4.2 BDRizzled. Was this installed with the recovery?

Sent from my T-Mobile G2 using Tapatalk

 

[cam30era]

If you flash the recovery, without a rooted boot.img and happen to boot into honeycomb, it will erase your recovery and load stock.

 

[drdoja]

hey if someone could help me out im really new to adb in general but i can follow decent directions. i got the bootloader unlocked and i cant seem to install the tiamat recovery when i try the command line listed in number 4 i get a access denied error i have tried unlocking bootloader but cant seem to get it working...any help would be awesome

 

[pingvinen]

hey if someone could help me out im really new to adb in general but i can follow decent directions. i got the bootloader unlocked and i cant seem to install the tiamat recovery when i try the command line listed in number 4 i get a access denied error i have tried unlocking bootloader but cant seem to get it working...any help would be awesome

Well if the unlocking does not give any error message, then it is indeed strange. What software and hardware version do you have?

 

[drdoja]

ok so I seemed to get bootloader unlocked and root access cause I'm able to set up setcpu and few other SU required programs no my problem seems to be rebooting into bootloader. when I try and do so i get the Droid and explination point screen I have been able to access cwm once or twice by what seems to accident. I am turning unit on waiting 3-5 seconds power button down and boot into booloader and everytime it gives me that green Droid screen....any help? btw I'm on 3.1 hmj37

Sent from my PG86100 using the XDA mobile application powered by Tapatalk

 

[drdoja]

also this just crossed my mind is it possible either the boot image I flashed or the modded recovery image somehow got messed up? could I just look around for correct files and try to reflash again?

Sent from my PG86100 using the XDA mobile application powered by Tapatalk

 

[pingvinen]

also this just crossed my mind is it possible either the boot image I flashed or the modded recovery image somehow got messed up? could I just look around for correct files and try to reflash again?

Sent from my PG86100 using the XDA mobile application powered by Tapatalk

Try to download the ones that I link to in my original post. If they are outdated, try to find newer of the same "brand". And remember, the 3-second count-down is not a joke, not even an approximation. It need to be 3 seconds, not 2 or 5 ...

 

[drdoja]

u understand the timing I have gotten many devices into bootloader although when i try this one I get that described screen of the Droid with the explunation point I am working few another hour then will be on my way home to try this. any idea where I.cab find up to date download Links btw that ka for all help and quick repkys

also this just crossed my mind is it possible either the boot image I flashed or the modded recovery image somehow got messed up? could I just look around for correct files and try to reflash again?

Sent from my PG86100 using the XDA mobile application powered by Tapatalk

Try to download the ones that I link to in my original post. If they are outdated, try to find newer of the same "brand". And remember, the 3-second count-down is not a joke, not even an approximation. It need to be 3 seconds, not 2 or 5 ...

Sent from my PG86100 using the XDA mobile application powered by Tapatalk

 

[joejens]

hey all,

I have a problem maybe someone can help. So I have been following the guide step-by-step, and now I am up to the part where I have to enter into CWM, but I cannot seem to get it right, I get options for fastboot, RSD and Nvflash. Am I doing something wrong? My 3 sec count is pretty accurate I'd say, but I cant seen to get into CWM.. Any help is much appreciated.

 

[Gordon1M]

I've flashed recovery-Tiamat-R4c-100611-1150-cwm.img into recovery and this seemed to go well. I then rebooted, waited for the three seconds after the "M", pressed Vol down and all seemed still to be correct. After pressing Vol up, CWM started, but there are error messages:
E:Can't open /dev/block/mmcblk1p3
(No such file or directory)
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log

[Edit] A bit more information. This is a record of the commands that I sent to the Xoom:
C:\Program Files (x86)\Android\android-sdk\tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
0288418643413457 device
C:\Program Files (x86)\Android\android-sdk\tools>adb reboot bootloader
C:\Program Files (x86)\Android\android-sdk\tools>fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
sending 'recovery' (3998 KB)...
OKAY [ 0.462s]
writing 'recovery'...
OKAY [ 1.939s]
finished. total time: 2.403s
C:\Program Files (x86)\Android\android-sdk\tools>fastboot reboot
rebooting...

The bootloader is unlocked, of course, and the device is rooted (checked with Root Check).

So far as I can see, the Xoom is still behaving correctly with a normal boot.
[Edit}

Any ideas?

Thank you
GordonM

 

[pingvinen]

I've flashed recovery-Tiamat-R4c-100611-1150-cwm.img into recovery and this seemed to go well. I then rebooted, waited for the three seconds after the "M", pressed Vol down and all seemed still to be correct. After pressing Vol up, CWM started, but there are error messages:
E:Can't open /dev/block/mmcblk1p3
(No such file or directory)
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log

[Edit] A bit more information. This is a record of the commands that I sent to the Xoom:
C:\Program Files (x86)\Android\android-sdk\tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
0288418643413457 device
C:\Program Files (x86)\Android\android-sdk\tools>adb reboot bootloader
C:\Program Files (x86)\Android\android-sdk\tools>fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
sending 'recovery' (3998 KB)...
OKAY [ 0.462s]
writing 'recovery'...
OKAY [ 1.939s]
finished. total time: 2.403s
C:\Program Files (x86)\Android\android-sdk\tools>fastboot reboot
rebooting...

The bootloader is unlocked, of course, and the device is rooted (checked with Root Check).

So far as I can see, the Xoom is still behaving correctly with a normal boot.
[Edit}

Any ideas?

Thank you
GordonM

I am no expert on cwm, but it looks like a corruption. Try to reflash from start.

 

[Gordon1M]

I wondered about curruption, but then I found a thread related to an earlier version of CWM, which referred to the same errors, i.e. http://forum.xda-developers.com/showthread.php?t=1038870&page=10. This is a long thread (33 pages) and I haven't been through everything yet. However, it ends up with the thread being closed and the issue transferred to http://forum.xda-developers.com/showthread.php?t=1074979, which refers to the newest version of CWM, which is the one that I flashed. So, I am not sure where to go from here.

Gordon

 

[Gordon1M]

Still puzzling over what to do with regard to these error messages. When I flashed, through fastboot, I had no external SD card installed. I didn't think that this was necessary. Is this correct?

I am wondering whether to reflash CWM again, though suspect that the result will be the same. Maybe I should go back to HC 3.0.1 and start again, though I don't see why this should be necessary.

This is a Canadian-purchased WiFi Xoom that I am using, but the update to stock US 3.2 went without a hitch.

From what I have read, I think that the error:
E:Can't open /dev/block/mmcblk1p3
refers to a partition. If so, does the CWM install set this up? Cerrtainly, I I look with ES File Explorer there is nothing with that name.

If anyone can offer any suggestions, I would be keen to hear from them.

Thank you
Gordon

 

[rmarquez1974]

I am also in a quandary, I have followed the OP step for step and it worked great. Got root, got CWM, and then went through CWM to flash manta ray...it updated the recovery image to 4.0.0 and I don't have access to my sdcard...
Is there a way to get the original image back without having to go through all those steps? Does CWM have an earlier version with sdcard support?
Can I download fastboot to my xoom and run the command from terminal on the xoom?

Sent from my SGH-T959 using Tapatalk

 

[Gordon1M]

Marquez - You are further ahead than I am. I haven't got a fully functional CWM yet. Was the recovery that you flashed "recovery-Tiamat-R4c-100611-1150-cwm.img"? Did you have to rename it to just recovery.img before flashing?

I seem to have read somewhere that the mount-point of the external SD card has been changed, but I don't know where I saw this. Also, I am not sure whether you have to give a mount instruction before the SD card shows up.

Gordon

 

[rmarquez1974]

Marquez - You are further ahead than I am. I haven't got a fully functional CWM yet. Was the recovery that you flashed "recovery-Tiamat-R4c-100611-1150-cwm.img"? Did you have to rename it to just recovery.img before flashing?

I seem to have read somewhere that the mount-point of the external SD card has been changed, but I don't know where I saw this. Also, I am not sure whether you have to give a mount instruction before the SD card shows up.

Gordon

Gordon, the name was the full name of the recovery I found in the thread "idiots guide to rooting and flashing your xoom for fun and profit". I did rename it the first time but it doesn't seem to matter.
I reflashed it and was able to see the sdcard in recovery.
Where are u stuck?

Sent from my SGH-T959 using Tapatalk

 

[Gordon1M]

Marquez - I seem to have split my problem over two threads, so I am going to focus on http://forum.xda-developers.com/showthread.php?t=1170774&page=3. As you may see from there, I have reflashed the recovery image and the result is the same ... error messages when CWM starts.

Gordon