Base on the image (image not so clear) above you try to flash tiamat recovery? If yes:
- Double check your spelling. If im not wrong, the tiamat spelling something not rite.
Correct me if im wrong cause the image nit clear.
If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed.
This is a discussion on [How To] Return To Stock (3G/4G HR166) within the Motorola Xoom Hacking Guides forums, part of the Motorola Xoom Hacks category; Base on the image (image not so clear) above you try to flash tiamat recovery? If yes: - Double check your spelling. If im not ...
Base on the image (image not so clear) above you try to flash tiamat recovery? If yes:
- Double check your spelling. If im not wrong, the tiamat spelling something not rite.
Correct me if im wrong cause the image nit clear.
yes i tried to flash timat recovery,i just pulled the whole recovery name and copy pasted into terminal,so i doubt if it's wrong
could it be a problem with how android sdk is setup on my system,though adb is working,while fastboot is not
the image is still not coming out clear,idk why
Screenshot from 2012-07-01 17:51:27.jpg
Rename your image to recovery.imag, less chance for a typing erroe.
fastboot flash recovery recovery.img
Could be something to do with Linux? I've always used a Window box for fastboot.
http://wiki.cyanogenmod.com/wiki/Fastboot
Last edited by ggrant3876; 07-01-2012 at 07:31 AM.
SGS-IV-Stock_Rooted
Nexus 4 - CyanMod 10.1
SGS-II - Rooted - Jedi Mind Trick VX3
Samsung Note II - Jedi Master 13
Motorola Xoom - WiFi - Rooted - EOS 4.2.1 Nightlies
Great..you going to root, flashing..etc?
Feel free to check our thread: [HOW] Rookie Rooting, Flashing And UnRooting Under One Roof
Hope it help and keep us posted![]()
(old thread but posting in case others need this)
I have the same problem with my xoom and fast boot under linux (Mint 12). Checking around it seems that ADB will happily find the device and has the correct permissions but FASTBOOT requires more.
Apparently the USB id for a device is different in fastboot mode.
One answer was to try logging in as ROOT while carrying out the rooting etc. Or try "sudo fastboot".
Have a look at this thread for the longer answer:
Android fastboot waiting for devices - Stack Overflow