Database Info

Stuck at Motorola Dual-Core? [Wifi-Only]

Hiya,
After dealing with a half-bricked Xoom, I did some research on this problem and found a solution.
If in any case, you happen to get stuck on the "Motorola Dual-Core Technology"
Solution to this (For the MZ604, One-Click rooted):
MZ604 Stock .imgs Download: http://developer.motorola.com/products/software/
*Make sure you have fastboot in the same directory as your adb for easy access*
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:
Code:
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
-or-
Code:
fastboot flash boot <path to boot.img>
fastboot flash system <path to system.img>
fastboot flash recovery <path torecovery.img>
fastboot flash userdata <path userdata.img>
fastboot erase cache
fastboot oem lock
5. Reboot the Xoom
Code:
fastboot reboot
6. There you go, back to stock!

On the real though, if you can get to Fastboot (or even the Moto "Android Recovery" state), you're not THAT bricked you've got to relock and go back to out-of-box; just keep a known-good boot.img around somewhere.

You just saved my life!

Thanks for sharing OP.
I take it this method is the same for 3.1?

I hope this works. Although, I can't turn my xoom off. It also appears that my computer will not recognize my device when it is plugged in. In addition, I can't turn off my Xoom? It just reboots... so I can't enter fastboot mode.
I just posted this in a new thread.
Lcsglvr said:
I tried reverting back to stock using the "one click" root/unroot tool that was the first to come out for the Xoom.
Anyway, I tried the unroot process and everything was going fine, until something occurred. Now, it tries to boot up and says at the Moto Dual Core Technology screen, "Failed to boot LNX 0x0004 // Starting RSD mode 2".
Can someone help
Click to expand...
Click to collapse
Can anyone help!

Lcsglvr said:
I hope this works. Although, I can't turn my xoom off. It also appears that my computer will not recognize my device when it is plugged in. In addition, I can't turn off my Xoom? It just reboots... so I can't enter fastboot mode.
I just posted this in a new thread.
Can anyone help!
Click to expand...
Click to collapse
same here, anyone help ((

Lcsglvr said:
I hope this works. Although, I can't turn my xoom off. It also appears that my computer will not recognize my device when it is plugged in. In addition, I can't turn off my Xoom? It just reboots... so I can't enter fastboot mode.
I just posted this in a new thread.
Can anyone help!
Click to expand...
Click to collapse
You can still enter fastboot if you xoom won't shut off. Just hold the appropria oncete buttons as it reboot. Happened to me last night upgrading to 3.1. It. Wouldn't shut down at all. Once I got into fastboot my computer saw it and I was able to fix

Honestly, I almost went through all of this last night when my WIFI Xoom got stuck in a boot loop.
However, I noticed that when my recovery went to flash the new 3.1 file, I felt like it didn't take as long as it should have. The file was the right size and all and it even said that everything installed successfully, but it just kept boot looping regardless of trying over and over. So I went ahead and re-downloaded the 3.1 file and repeated the steps to flash it and everything worked.
So, before you spend a whole lot of time restoring your Xoom, simply re-download the files and try it one more time. It worked for me.

rebill said:
You can still enter fastboot if you xoom won't shut off. Just hold the appropria oncete buttons as it reboot. Happened to me last night upgrading to 3.1. It. Wouldn't shut down at all. Once I got into fastboot my computer saw it and I was able to fix
Click to expand...
Click to collapse
Thanks! Finally have some hope to recovering. I'll post steps I took later once I get this damn thing fixed.

hmmm... I'm in fastboot supposedly and tried to flash boot.img but it seems to be stuck at <waiting for device>
This happen to anyone else?
After search seems like a driver issue, but I have installed the drivers... I was previous rooted, so I know I have the drivers. Just to be sure, I ran the MotoHelper again. I don't understand. It's just seeing my device on the "Starting Fastboot protocol support."
help?

Lcsglvr said:
hmmm... I'm in fastboot supposedly and tried to flash boot.img but it seems to be stuck at <waiting for device>
This happen to anyone else?
After search seems like a driver issue, but I have installed the drivers... I was previous rooted, so I know I have the drivers. Just to be sure, I ran the MotoHelper again. I don't understand. It's just seeing my device on the "Starting Fastboot protocol support."
help?
Click to expand...
Click to collapse
Yes. How did I fix it? I returned the xoom and had a new one two days later.
If the screen says something like "Entering RSD 2" then you're boned. The xoom won't be recognized in either the current state or in fastboot state by the computer, so no amount of commands will help. Even having the stock images doesn't help with that. Even RSDLite can't see the xoom in that state.
There have been several reports of people just being honest to Motorola and them fixing the device under the warranty.

Hmm honesty. I'll give it a shot.
Sent from my ADR6300 using XDA App

Is the final OEM lock necessary? It's quite a pain as your userdata gets wiped if you unlock it...

I was stuck on bootloop, with unrecognised device, through adb was able to get back into clockwork recovery somehow at first boot, think twice down volume? Could be wrong.
I was able tto rreflash zip 3.1 over thet top again.
sry if this is different and unhelpful, bu imagine things are pretty desperate if you are considering returning the device

zerin said:
Yes. How did I fix it? I returned the xoom and had a new one two days later.
If the screen says something like "Entering RSD 2" then you're boned. The xoom won't be recognized in either the current state or in fastboot state by the computer, so no amount of commands will help. Even having the stock images doesn't help with that. Even RSDLite can't see the xoom in that state.
There have been several reports of people just being honest to Motorola and them fixing the device under the warranty.
Click to expand...
Click to collapse
You're not boned at all. I had that happen to me so I just got back into fastboot, downloaded the files in the OP put ADB, Fastboot and the adb extensions into the file I downloaded then ran the commands and got me XOOM back up and running fine.

jbartcaps said:
You're not boned at all. I had that happen to me so I just got back into fastboot, downloaded the files in the OP put ADB, Fastboot and the adb extensions into the file I downloaded then ran the commands and got me XOOM back up and running fine.
Click to expand...
Click to collapse
You were likely in RSD 3, which is recognized by the computer. RSD 2 means adb and fastboot cannot see the device at all, so no flashing images is possible.
There's several states that all look very similar. Because some success was had with one doesn't mean it works for all. Motorola recognizes and is telling users that, in this state, the device needs to be sent back to them.

Can someone help us wifi xoom. Im stuck on the motorola screen and have a lil experience. I can fast boot reboot/fastboot device and it work but cant get the files from the hwi69 to fastboot on to it. I think im entering the commands wrong. Any advice would be appreciated

TheRedDroid said:
Hiya,
After dealing with a half-bricked Xoom, I did some research on this problem and found a solution.
If in any case, you happen to get stuck on the "Motorola Dual-Core Technology"
Solution to this (For the MZ604, One-Click rooted):
MZ604 Stock .imgs Download: http://developer.motorola.com/products/software/
*Make sure you have fastboot in the same directory as your adb for easy access*
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:
Code:
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
-or-
Code:
fastboot flash boot <path to boot.img>
fastboot flash system <path to system.img>
fastboot flash recovery <path torecovery.img>
fastboot flash userdata <path userdata.img>
fastboot erase cache
fastboot oem lock
5. Reboot the Xoom
Code:
fastboot reboot
6. There you go, back to stock!
Click to expand...
Click to collapse
Very good info to get into fastboot protocol:

Much thanks for the info. Worked like a champ. On an updated 3.2.1 XOOM I did an unlock, re-locked the wrong way, soft bricked, unbricked back to locked state. Finally followed your steps applied stock files and XOOM is re-locked and stock rocking back at 3.01. I needed to do all this to make sure I could get it back to stock in case it goes back to BB in 2 weeks. I was lucky enough to find one at a BB just not sure if I'll keep it. I plan on trying out some roms plus I heard Motorola is planning on doing an ICS push to the XOOM. ICS is very nice. It runs great on my unlocked Verizon G-Nex.. Again Thanks..

This post not only saved my half-bricked non-rooted Xoom, but also let me flash it from the Singapore firmware (bought if from Amazon, don't ask lol) to the regular USA firmware so that I can properly root it!
Thank you so very much!!

[Q] Stuck on Google logo. Unable to push image file to phone... Please help.

Tried various possible solutions and still can't get past the Google logo. Installed adb and Samsung driver but when executing commands such as "abd remount" or "adb push file.zip \sdcard\" in cmd I get an error saying "device not found".
Does anyone know how I could resolve this issue?
I tried clearing the cache and wiping the data from the phone, and even heating the phone with a hair dryer. I'd very much appreciate any help.

looks like you still be able to get in reovery ? if so , then nothing you should worry , just flash a new ROM

Do you mean like a boot image or a recovery image?
If so then you need to put phone in fastboot mode, hold volume up and power til it comes up on screen, then on command prompt on your computer type in fastboot flash recovery xxxxxxx.img (xxxxx is the name of the file like cwm5.0.2.0.img or whatever)
That should give you a working recovery to flash roms from.
Is your boot loader unlocked?
If you wanna mount then just go to mounts and storage and mount USB storage and it will show up on your computer!

nodstuff said:
Do you mean like a boot image or a recovery image?
If so then you need to put phone in fastboot mode, hold volume up and power til it comes up on screen, then on command prompt on your computer type in fastboot flash recovery xxxxxxx.img (xxxxx is the name of the file like cwm5.0.2.0.img or whatever)
That should give you a working recovery to flash roms from.
Is your boot loader unlocked?
If you wanna mount then just go to mounts and storage and mount USB storage and it will show up on your computer!
Click to expand...
Click to collapse
Thanks for your reply, seems to be hanging on waiting for device. Fastboot appears to be locked and it just hangs on "waiting for device" when I enter the command fastboot oem unlock... Not sure where to go from here.

leeroy88 said:
Thanks for your reply, seems to be hanging on waiting for device. Fastboot appears to be locked and it just hangs on "waiting for device" when I enter the command fastboot oem unlock... Not sure where to go from here.
Click to expand...
Click to collapse
It was a recovery image file by the way. Tried fastboot flash recovery xxxxx.img like you had said but same problem...

leeroy88 said:
It was a recovery image file by the way. Tried fastboot flash recovery xxxxx.img like you had said but same problem...
Click to expand...
Click to collapse
Hmmm try going to cmd prompt and typing in adb devices, if you get nothing then your adb isn't set up properly and you need to go into setting and change the path on your computer.
I know the details are sketchy but gimme a min and I will find you a link
---------- Post added at 03:05 AM ---------- Previous post was at 03:00 AM ----------
http://forum.xda-developers.com/showthread.php?t=1161776
Find the Android sdk folder in your computer, move it to the root of C.
I don't think adb is where this guide says it is, there is a read me in the folder where it was saying it has moved to the platform tools folder.
So anyway find the path to the file and put it where the guide says and you should be on the ball.

Forget adb. You need to use fastboot.
Open a command prompt in the directory with fastboot or cd into it.
Put phone in fastboot mode.
On the command prompt type fastboot devices.
You will see your serial number. If you don't recheck and make sure you did everything. Sdk PDA drivers if need be etc.
Fastboot flash recovery custom recovery img name.img
Boot into recovery
Mounts and storage.
Mount SD card
Put a rom for you device on there.
Unmount
Wipe everything but sdcard from recovery.
Flash the rom by going to install zip from SD card......

Okay still stuck trying to connect to my phone. I haven't been able to get my serial number show when typing fastboot devices in cmd. adb is set up and seems to be working but the list of devices is blank when I type in adb devices. The phone was put into fastboot mode both times. I get <waiting for device> when I try
fastboot flash recovery clockwork-5.0.2-crespo.img
I think the bootloader may be locked as it does say LOCKED under lock state, which is probably the reason why I can't get the recovery image to work. I couldn't install PDANet as it wanted to connect to my phone while in debugging mode at the end of the installation. Would it be possible that fastboot oem unlock won't work with without having PDANet installed? I'd really appreciate any further help on this topic.

You need the drivers.

albundy2010 said:
You need the drivers.
Click to expand...
Click to collapse
I have the Google USB driver package installed from SDK Manager. I had tried to install some other Samsung driver found on another post but it wouldn't install.

Turns out drivers weren't fully installed, managed to get PDANet installed and could connect to the phone with fastboot devices. Serial number was displayed in cmd. Only problems lies with unlocking the bootloader. fastboot oem unlock fails giving an error: too many links. Anyone have a solution to this?

leeroy88 said:
Turns out drivers weren't fully installed, managed to get PDANet installed and could connect to the phone with fastboot devices. Serial number was displayed in cmd. Only problems lies with unlocking the bootloader. fastboot oem unlock fails giving an error: too many links. Anyone have a solution to this?
Click to expand...
Click to collapse
Did you try booting into bootloader in the first place? Volume up+Power
Then you can use fastboot. Forget PDAnet. Just install SDK and ADB
Use this:
http://forum.xda-developers.com/showthread.php?t=1007782

ismailham said:
Did you try booting into bootloader in the first place? Volume up+Power
Then you can use fastboot. Forget PDAnet. Just install SDK and ADB
Use this:
http://forum.xda-developers.com/showthread.php?t=1007782
Click to expand...
Click to collapse
Yeah I was in bootloader at the time, but I noticed that the Lock-State said locked. So I figured I must first use fastboot oem unlock. If I was to try flash with a stock recovery image would I still need to unlock the bootloader? Like I said I was able to use fastboot devices and get my phones serial number to show up, so I think SDK and ADB is properly installed, path set correctly etc.

leeroy88 said:
Yeah I was in bootloader at the time, but I noticed that the Lock-State said locked. So I figured I must first use fastboot oem unlock. If I was to try flash with a stock recovery image would I still need to unlock the bootloader? Like I said I was able to use fastboot devices and get my phones serial number to show up, so I think SDK and ADB is properly installed, path set correctly etc.
Click to expand...
Click to collapse
I don't think you need to unlock the boot loader to flash a recovery image.
I may be wrong but I remember someone saying that once. I had mine unlocked before I had the chance to try it out. What happens when you type in fastboot oem unlock?

nodstuff said:
I don't think you need to unlock the boot loader to flash a recovery image.
I may be wrong but I remember someone saying that once. I had mine unlocked before I had the chance to try it out. What happens when you type in fastboot oem unlock?
Click to expand...
Click to collapse
After typing fastboot oem unlock I get three dots ...
Pretty much straight away it fails and says something about "too many links".

Did you do all the steps from here http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ ?

kvaju said:
Did you do all the steps from here http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ ?
Click to expand...
Click to collapse
Thanks for your reply, I followed the steps just now and got the exact same error. Before I was trying fastboot oem unlock while in platform-tools but this time I had downloaded the nexussrootICS.zip file, and extracted it to the root of C. I tried fastboot devices and my serial shows up and after fastboot oem unlock I get "status read failed: too many links."
The only difference I seem to have is that in my device manager I have Android Device > ADB Interface, as opposed to SAMSUNG Android Device > ADB Interface.
Not a big difference but that's all I can think of.

the same issue for me. is there any working solution for that?

I recently had success in recovering from this issue.
Here is the link, read the last comment
http://forum.xda-developers.com/showthread.php?t=1894147

GnubbyaBush said:
I recently had success in recovering from this issue.
Here is the link, read the last comment
http://forum.xda-developers.com/showthread.php?t=1894147
Click to expand...
Click to collapse
Thanks! I'll try to do this fancy dancing

[Q] help, i think i bricked my tablet

hi, first of all, i'd like to tell you i'm quite a noob
i have a tf300tg and i tried to flash the jb 4.2.2 that's only available for the 300t.. i'm dumb, i know.. and now in stead of booting it goes directly to the cwm menu and i can't do anything.. i keep getting the error E:Can't mount /cache/recovery/command , .../log and .../last_log
is there anything i can do or should i just throw it in the trashbin ?

iostu said:
hi, first of all, i'd like to tell you i'm quite a noob
i have a tf300tg and i tried to flash the jb 4.2.2 that's only available for the 300t.. i'm dumb, i know.. and now in stead of booting it goes directly to the cwm menu and i can't do anything.. i keep getting the error E:Can't mount /cache/recovery/command , .../log and .../last_log
is there anything i can do or should i just throw it in the trashbin ?
Click to expand...
Click to collapse
Unless you can go into fastboot (Power + volume down) there isn't much to do but to sign a petition & wait...
XDA member HAZARD17 has been running a petition
Sign NVflash petition for Transformer TF300T, Prime & Infinity!
https://www.change.org/petitions/asus-nvidia-revert-changes-in-jb-bootloader-that-prevent-nvflash

vconceicao said:
Unless you can go into fastboot (Power + volume down) there isn't much to doo but to wait...
Click to expand...
Click to collapse
i can't do that either.. it just loads the CWM menu..
wait ? wait for what ? :silly:

iostu said:
i can't do that either.. it just loads the CWM menu..
wait ? wait for what ? :silly:
Click to expand...
Click to collapse
For someone to come up with a solution, Like a NVflash utility for Tf300...

Yeah, but if you want add NVflash support to your tablet, it can't be bricked I'm not quite sure, but you try unpack blob from offical update, and flash all files from unpacked blob (LNX etc.).

Hazard17 said:
Yeah, but if you want add NVflash support to your tablet, it can't be bricked I'm not quite sure, but you try unpack blob from offical update, and flash all files from unpacked blob (LNX etc.).
Click to expand...
Click to collapse
i can't flash anything :| in adb it sais <waiting for device> i've tried everything and i can't get it to work.. can you pleeeeeease help me ?

ok, i reinstalled the adb drivers for the transformer, and it goes into bootloader but there is no usb icon.. only RCK, the android and wipe data.. when i type adb devices i get 123456789ABCDEF recovery. although i can't do much else, i can't do anything in adb shell, i can't even flash the twrp.. any suggestions ? plese please please

iostu said:
ok, i reinstalled the adb drivers for the transformer, and it goes into bootloader but there is no usb icon.. only RCK, the android and wipe data.. when i type adb devices i get 123456789ABCDEF recovery. although i can't do much else, i can't do anything in adb shell, i can't even flash the twrp.. any suggestions ? plese please please
Click to expand...
Click to collapse
The USB icon is gone. I sugguest downloading the correct firmware and flashing it with fastboot.
fastboot flash system blob
Download the correct system firmware, open the zip, open the zip, extract the blob to the same directory as fast boot.

iostu said:
ok, i reinstalled the adb drivers for the transformer, and it goes into bootloader but there is no usb icon.. only RCK, the android and wipe data.. when i type adb devices i get 123456789ABCDEF recovery. although i can't do much else, i can't do anything in adb shell, i can't even flash the twrp.. any suggestions ? plese please please
Click to expand...
Click to collapse
4.2 bootloader does not have USB icon, just plug in USB..

i can get to the bootloader menu but only after typing adb reboot bootloader. and then i tryed flashing the blob using adb fastboot -i 0x0b05 flash system blob and then i get "sending 'system' <799764 KB>..." and it's stuck there.. i left it over 30 mins and still nothing
edit: i somehow managed to flash teh system blob (i tried with te 4.1.1 and the 4.2.2) but after flashing it did the exact same thing.. went to CWM ! i even managed to flash the TWRP.blob, and still the CWM showed up.. i can't figure out how is this even possible :| and from the bootloader menu if i go to boot the android firmware, it almost boots (it goes to the lockscreen for about 2 secs) and then reboots again.. am i wasting my time or should i throw it in the garbage ?
thanks again for trying to help me on this one i really appreciate it !

iostu said:
i can get to the bootloader menu but only after typing adb reboot bootloader. and then i tryed flashing the blob using adb fastboot -i 0x0b05 flash system blob and then i get "sending 'system' <799764 KB>..." and it's stuck there.. i left it over 30 mins and still nothing
edit: i somehow managed to flash teh system blob (i tried with te 4.1.1 and the 4.2.2) but after flashing it did the exact same thing.. went to CWM ! i even managed to flash the TWRP.blob, and still the CWM showed up.. i can't figure out how is this even possible :| and from the bootloader menu if i go to boot the android firmware, it almost boots (it goes to the lockscreen for about 2 secs) and then reboots again.. am i wasting my time or should i throw it in the garbage ?
thanks again for trying to help me on this one i really appreciate it !
Click to expand...
Click to collapse
Sounds like you're in the same boat as the rest of us...
http://forum.xda-developers.com/showthread.php?t=2179874

iostu said:
ok, i reinstalled the adb drivers for the transformer, and it goes into bootloader but there is no usb icon.. only RCK, the android and wipe data.. when i type adb devices i get 123456789ABCDEF recovery. although i can't do much else, i can't do anything in adb shell, i can't even flash the twrp.. any suggestions ? plese please please
Click to expand...
Click to collapse
OK. The bootloader menu you now are seeing is the new 4.2 version. RCK - Android - Wipe Data(do not use wipe data).
When you get into this menu if you leave everything alone your tablet should auto into fastboot - watch the screen - upper left.
With fastboot flash the latest (proper) JB blob for your unit.
Good Luck!

iostu said:
i can get to the bootloader menu but only after typing adb reboot bootloader. and then i tryed flashing the blob using adb fastboot -i 0x0b05 flash system blob and then i get "sending 'system' <799764 KB>..." and it's stuck there.. i left it over 30 mins and still nothing
edit: i somehow managed to flash teh system blob (i tried with te 4.1.1 and the 4.2.2) but after flashing it did the exact same thing.. went to CWM ! i even managed to flash the TWRP.blob, and still the CWM showed up.. i can't figure out how is this even possible :| and from the bootloader menu if i go to boot the android firmware, it almost boots (it goes to the lockscreen for about 2 secs) and then reboots again.. am i wasting my time or should i throw it in the garbage ?
thanks again for trying to help me on this one i really appreciate it !
Click to expand...
Click to collapse
You can't flash anything using adb commands. You need to use fastboot. Look in the forum for the proper procedure and follow the instructions.
Nowhere does it say type "adb fastboot ... anything...."

hgoldner said:
You can't flash anything using adb commands. You need to use fastboot. Look in the forum for the proper procedure and follow the instructions.
Nowhere does it say type "adb fastboot ... anything...."
Click to expand...
Click to collapse
Here is an example of an adb command that does work to flash twrp with slight modification it will flash stock blob as well.
adb shell
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4 Then reboot to complete installation.
adb reboot
I don't know where you are getting your information but you need a new source.
No one said type adb fastboot they are two different things and each has a specific structure to follow.
If the op can get either fastboot or adb to work I'll gladly provide the proper commands.

then you have the same problem as me and a bunch of other people. The bootloader freezes on the flash command, even though it will show success and stuff. It never flashes.
I can push files with ADB and on reboot the files on gone. Since we can't flash with fastboot. We have to send it in to asus at this point. I got quoted $87 + shipping.

sorry, i meant to say just fastboot. i didn't write adb fastboot.. i've tried everything you guys said, but with no success my last resort is to send it to asus for re-softing. It costs about $80 + shipping. It doesn't sound like a lot of money, but it's a price to pay for stupidness or noobness i just hope they can repair it or otherwise i'll have a very expensive thing on whch to chop onions
thanks again guys for helping me

[Q] LG P500 stuck in fastboot - "waiting for device"

Hello.
Earlier today I wanted to try a new JB rom to replace ICS so I transfered it into SD card and tried to reboot into recovery.
Instead of getting to recovery, I got stuck in fastboot mode, so I'm assuming recovery has been damaged.
After a whole afternoon of researching this forum I tried for several times this tutorial in order to install a recovery and afterwards a ROM (http://forum.xda-developers.com/showthread.php?t=1088046) and similar ones in both Mac OS X and Windows 7 (tried both USB 2.0 and USB 3.0 so its not a problem from USB) and I didn't succeed at all.
When I am using Windows 7, when I use "fastboot erase recovery", I keep receiving this message "waiting device". If I write "fastboot devices", I don't get results.
When using Mac OS X, I can get via command line to the folder "platform-tools" where fastboot is located but if I write "fastboot erase recovery" or something, it says "command not found". I've read it could be because I have to set fastboot as an environmental variable, but I having trouble setting it (Mac OS Lion).
Thank you so much for reading. Please help me!!! Any clues would be really appreciated!
-----
UPDATE: I finally managed to communicate with the device.
I used the following commands from this tutorial http://androidforums.com/optimus-m-all-things-root/382525-guide-get-out-fastboot-mode-2.html
fastboot erase boot
fastboot erase recovery
fastboot erase system
fastboot flash recovery
The problem is, now I'm stuck at LG Logo, can't access fastboot... Please help, I think it's even worse now.

boot rom, pull out battery and boot normal, it does or not? if it does use terminal emulator or adb push to install custom recovery, adb will work in fastboot if you had checked android debugging
http://forum.xda-developers.com/showthread.php?t=1007244
http://forum.xda-developers.com/showthread.php?t=1146566

grigtm said:
boot rom, pull out battery and boot normal, it does or not? if it does use terminal emulator or adb push to install custom recovery, adb will work in fastboot if you had checked android debugging
http://forum.xda-developers.com/showthread.php?t=1007244
http://forum.xda-developers.com/showthread.php?t=1146566
Click to expand...
Click to collapse
I don't understand what you mean by boot rom. Every time I turn on the phone, (normal or as POWER+HOME+VOL DOWN) it goes into fastboot. When I pull out the battery, and power again it goes again into fastboot...

techdani said:
I don't understand what you mean by boot rom. Every time I turn on the phone, (normal or as POWER+HOME+VOL DOWN) it goes into fastboot. When I pull out the battery, and power again it goes again into fastboot...
Click to expand...
Click to collapse
ok, read here http://forum.xda-developers.com/showthread.php?t=1088046 do exactly what says in this thread

[Q] Can't flash recovery of Motorola Photon Q

Hi together,
I've got a Motorola Photon Q 4g LTE mobile phone and this afternoon I wanted to install CyanogemMod, but whatever I do, I stuck with the following problem:
I can't install any other Custom Recovery. I tried ClockworkMod and OpenRecovery, but I always get the s**t Motorola Bootloader, when I start in Recovery Mode. The Bootloader of my Phone is unlocked via Motorola Website, as told in many other threads.
I know that the users arrrghhh, shabbypenguin and Skrilax_CZ are great experts with firmware and such things, but I'm not allowed to write in developer's forums because I'm new here.
Has anybody got an idea for me, how to geht the Custom Recovery to work?
Btw: I tried to root the phone as well, but that wasn't posible. May be things come together or depend on each other.
Thanks for your help!

When you flash recovery (IE run the fastboot command) is it successful?
With the phone in fastboot/bootloader mode, type "fastboot devices" in the command prompt (where you run the fastboot flash command) and what does it output?
Also, try this.

arrrghhh said:
When you flash recovery (IE run the fastboot command) is it successful?
Click to expand...
Click to collapse
When I flash recovery, I just flash the Motorola given Recovery by Motoroloa Bootloader. The Phone restarts, a logo with the Android Man is shown (stomach opend with some engeniering tools in it) and after about 5-7 Minuten, the system starts normally.
I also managed it to change the "Unlocked Message" into a Motorola Logo by using fastboot flash logo xxxx.bin and I nearly destroyed the flash by flashing an unlikely file. So the phone was shortly out of order because oder "flash failure" (fastboot mode). After that, I managed to flash the "boot.img" file of an CyanogenMod, so the flash was rebuilt and I could use the phone normally.
arrrghhh said:
With the phone in fastboot/bootloader mode, type "fastboot devices" in the command prompt (where you run the fastboot flash command) and what does it output?
Click to expand...
Click to collapse
It shows the connected devices by showing a 8 or 9 ditigt number. It's almost the same view like I connected the phone without fastboot and use "adb devices".
arrrghhh said:
Also, try this.
Click to expand...
Click to collapse
This one I didn't tried yet, because I was so dissappointed of the mismatch with ClockworkMod & Open Recovery. Do you think, that trying this one will help, after two others failed?!
Thanks for you notice and your time. That's very helpful!

You need to boot to recovery after flashing it. There's a shell script that is re-flashing stock recovery - the dead Android dude with tools sticking out of him is stock recovery....

arrrghhh said:
You need to boot to recovery after flashing it. There's a shell script that is re-flashing stock recovery - the dead Android dude with tools sticking out of him is stock recovery....
Click to expand...
Click to collapse
Ah ja, now I'm one step closer. I did not know, that the dead Android dude is the sign for stock recovery.
I'll give it this afternoon another try and will report. A bunch of thanks to you at this time!

Hi, it's me again. I managed now the reboot to recovery, by holding the volume up button while doing the "fastboot reboot"-command with the command box. That worked and I could start Photon Q Open Recovery 2.06.
Unfortunately, I did something wrong or so and now the script re-flashed stock recovery again. Nevertheless, I now know how to operate and will do the rest by my own (hopefully).
@arrrghhh: Thank you very much for your help!

So, I finally did everyhting the right way (now with ClockworkMod Recovery), because I now have CyanogenMod running on my Motorola Photon Q
:victory:
@arrrghhh: Thank you very very much!