Database Develop

Help!!..i lost my recovery(i think) and i don't have a rom!!!!

hi
i need help on getting a rom on my g1(any rom at all)
i lost my recovery or i think i did..wot happened was i was changing recovery and i was moving from RA's to Cyanogen's recovery...i moved from RA's to RA's b4 and i did it by going to console in recovery then typing "mount -a" then "flash_image recovery /sdcard/(the name of the recovery)" so i tryed to get cm recovery by doing the same thing(btw it was a .zip if thats any help)but i got the "error no space on device" or something like that...then i removed the battery to get out of console (like i always do coz i don't know any other any) but then when i tryed to go to recovery mode again i just get the T-Mobile G1 screen then a black screen comes but no recovery...what now i need a new recovery to get a rom...i searched and got something called fastboot but i don't know wot it is when i press power n back i go to screen with 3 lil androids on the bottom(i believe this is fastboot mode)...can i use that to get a new recovery?any help pls

mazinxd said:
hi
i need help on getting a rom on my g1(any rom at all)
i lost my recovery or i think i did..wot happened was i was changing recovery and i was moving from RA's to Cyanogen's recovery...i moved from RA's to RA's b4 and i did it by going to console in recovery then typing "mount -a" then "flash_image recovery /sdcard/(the name of the recovery)" so i tryed to get cm recovery by doing the same thing(btw it was a .zip if thats any help)but i got the "error no space on device" or something like that...then i removed the battery to get out of console (like i always do coz i don't know any other any) but then when i tryed to go to recovery mode again i just get the T-Mobile G1 screen then a black screen comes but no recovery...what now i need a new recovery to get a rom...i searched and got something called fastboot but i don't know wot it is when i press power n back i go to screen with 3 lil androids on the bottom(i believe this is fastboot mode)...can i use that to get a new recovery?any help pls
Click to expand...
Click to collapse
You obiously don't know what the Q&A section is either.
But anyways, it was a zip? If it was then that wasn't the recovery image, the recovery image is a .img file. Did you try extracting the zip?

no...but now i just wana get a recovery..any so i can flash a rom

mazinxd said:
no...but now i just wana get a recovery..any so i can flash a rom
Click to expand...
Click to collapse
even if you borked your recovery you should still be able to get into SPL. reboot your phone with camera+power, after it finishes checking, press "back" button to go into hboot, then connect your phone, and fastboot flash recovery recovery.img (make sure you already extracted it). You should be good to go

when i connect my mobile to the pc its not recognize,setup wizard come's up and i can't install the software drives(did i tell u i'm a noop and all i know is how to flash roms using my g1 mainly)

how do i make it reconzie my g1? and were do i typ flash recovery recovery.img

Have you installed the android sdk on your pc? If not, search the developement forum for it or do a google search for android sdk.

mazinxd said:
hi
i need help on getting a rom on my g1(any rom at all)
i lost my recovery or i think i did..wot happened was i was changing recovery and i was moving from RA's to Cyanogen's recovery...i moved from RA's to RA's b4 and i did it by going to console in recovery then typing "mount -a" then "flash_image recovery /sdcard/(the name of the recovery)" so i tryed to get cm recovery by doing the same thing(btw it was a .zip if thats any help)but i got the "error no space on device" or something like that...then i removed the battery to get out of console (like i always do coz i don't know any other any) but then when i tryed to go to recovery mode again i just get the T-Mobile G1 screen then a black screen comes but no recovery...what now i need a new recovery to get a rom...i searched and got something called fastboot but i don't know wot it is when i press power n back i go to screen with 3 lil androids on the bottom(i believe this is fastboot mode)...can i use that to get a new recovery?any help pls
Click to expand...
Click to collapse
This is excatly the reason you should read,research and always follow the directions.
There are plenty of tutorials on how to use fastboot here on xda so research.read and follow the directions and you will be fine

Here is what you need to do.
1) Follow these instructions word for word, step by step
http://forum.xda-developers.com/showthread.php?t=502010
2) Now you should have adb installed. With adb you can plug your phone into your pc through USB and use command lines to manipulate your phone. To use commands in windows go to start, run and type cmd, enter
3) Now if it worked correctly you should have your phone plugged in and type adb remount. If it successfully mounted then adb is working.
4) now unzip Ra's recovery image and rename it to recovery.img (for simplicity) and place it on your desktop
5) now with your phone plugged into the pc power down the phone and reboot, before it starts up hold the camera button. You should see some droids on skateboards.
6) Now press the back button
7) now go to the cmd as I mentioned earlier and type: cd desktop
8) now type fastboot flash recovery recovery.img when it is done type adb shell reboot and your phone will reboot.
9)before it boots up hold the home button and if you did everything correctly you should be in Ra's recovery.
from the recovery you can always hold call, menu, end to reboot instead of pulling the battery.
Good luck. I suggest you flash a rom to get back up and going, and then spend a few weeks reading about everything android that you can find on xda before you mess with it anymore. In the future you probably won't find anyone else willing to give you instructions like this, so I would search and read ALOT before posting a bunch of how to messages....

thanx
bhilgeman said:
Here is what you need to do.
1) Follow these instructions word for word, step by step
http://forum.xda-developers.com/showthread.php?t=502010
2) Now you should have adb installed. With adb you can plug your phone into your pc through USB and use command lines to manipulate your phone. To use commands in windows go to start, run and type cmd, enter
3) Now if it worked correctly you should have your phone plugged in and type adb remount. If it successfully mounted then adb is working.
4) now unzip Ra's recovery image and rename it to recovery.img (for simplicity) and place it on your desktop
5) now with your phone plugged into the pc power down the phone and reboot, before it starts up hold the camera button. You should see some droids on skateboards.
6) Now press the back button
7) now go to the cmd as I mentioned earlier and type: cd desktop
8) now type fastboot flash recovery recovery.img when it is done type adb shell reboot and your phone will reboot.
9)before it boots up hold the home button and if you did everything correctly you should be in Ra's recovery.
from the recovery you can always hold call, menu, end to reboot instead of pulling the battery.
Good luck. I suggest you flash a rom to get back up and going, and then spend a few weeks reading about everything android that you can find on xda before you mess with it anymore. In the future you probably won't find anyone else willing to give you instructions like this, so I would search and read ALOT before posting a bunch of how to messages....
Click to expand...
Click to collapse
thanx alot man ryt now its late here so i'll do it 2moro...thanx again..btw i love ur moto
edit:wait i can't turn on my g1 so i can't turn on debug mode...will that be a prob

mazinxd said:
thanx alot man ryt now its late here so i'll do it 2moro...thanx again..btw i love ur moto
edit:wait i can't turn on my g1 so i can't turn on debug mode...will that be a prob
Click to expand...
Click to collapse
no that wont be a problem

wots
mv ~/Desktop/sdk/tools/adb /usr/bin/adb abd
and
cd ~/Phone/tools/android-sdk/tools ???? sorry don't speak codes?

flash update.zip using adb?

So, my captivate is bricked.. but I'm in the mood to try and fix it. So, I was wondering if it is possible to flash 3buttonfix.zip(I renamed to update.zip) using adb. I pushed update.zip to the sd card using adb but I cant reboot into recovery to apply it and I got to thinking that I might be able to flash the update.zip file using adb.. does anyone know how to do it? if so please share.

How is your phone bricked if you can get into it with adb? And, what's preventing you from issuing 'adb reboot recovery' or 'adb reboot download' to fix it?

modest_mandroid said:
How is your phone bricked if you can get into it with adb? And, what's preventing you from issuing 'adb reboot recovery' or 'adb reboot download' to fix it?
Click to expand...
Click to collapse
I can get into adb believe it or not.. I tried flashing CM7 and completely missed the 3 button combo part. Now I have a captivate that is stuck at cyanogenmod screen. I have been trying both recovery and download, all it does is reboots the phone. thats why I wanted to flash update.zip(3buttonfix.zip) and it might fix it. everytime I turn it on and try to get into recovery it just skips it.. I have tried download mode and recovery several, and I mean several times. I bought a jig to put it into DL mode, just gotta wait for the Jig to get here. That's why I have been trying to fix it because I have no backup phone to use.

Try this.
Find the modified recovery file in this forum, push it to /system/bin, check execute permissions, and try 'adb reboot recovery' then.
What files are in the 3button fix.zip? Push them manually with adb also.

another one bites the dust...
Let us know how did it go.

can we have a big sticky:
if you can see things on your screen, it's not bricked. use the search.

ibrutalfatei said:
So, my captivate is bricked.. but I'm in the mood to try and fix it. So, I was wondering if it is possible to flash 3buttonfix.zip(I renamed to update.zip) using adb. I pushed update.zip to the sd card using adb but I cant reboot into recovery to apply it and I got to thinking that I might be able to flash the update.zip file using adb.. does anyone know how to do it? if so please share.
Click to expand...
Click to collapse
Did you try adb reboot recovery command? You don't need 3 button fix if you can connect adb.

gibson3659 said:
Try this.
Find the modified recovery file in this forum, push it to /system/bin, check execute permissions, and try 'adb reboot recovery' then.
What files are in the 3button fix.zip? Push them manually with adb also.
Click to expand...
Click to collapse
Can you explain how to do that? I'm not very good with ADB

foxbat121 said:
Did you try adb reboot recovery command? You don't need 3 button fix if you can connect adb.
Click to expand...
Click to collapse
I have tried that multiple times. I can connect ADB, when I enter "adb reboot recovery" the phone just restarts and goes to the Galaxy S Cyanogenmod Screen.

ibrutalfatei said:
I have tried that multiple times. I can connect ADB, when I enter "adb reboot recovery" the phone just restarts and goes to the Galaxy S Cyanogenmod Screen.
Click to expand...
Click to collapse
Sounds like your recovery mode has been screwed by whatever ROM you have used. Your problem is no long 3e recovery fix. That no longer exists.
You need to get into download mode instead and use OneClick ODIN to flash back to stock.

foxbat121 said:
Sounds like your recovery mode has been screwed by whatever ROM you have used. Your problem is no long 3e recovery fix. That no longer exists.
You need to get into download mode instead and use OneClick ODIN to flash back to stock.
Click to expand...
Click to collapse
I can't get into Download mode either.

ibrutalfatei said:
I can't get into Download mode either.
Click to expand...
Click to collapse
Have to ask, did you try the manual method to get into download?
Open Odin
Verify not connected to usb
Pull battery
Insert battery
While holding both up and down volume button, insert usb
BTW, many people have and will continue to say, you should always verify you can access download and recovery before attempting to apply any ROM.

If you still can't get into download mode using above method, it's time for you to make a jig that will force the phone into download mode. Search for the thread here about how to make such hardware jig.

xcaliburinhand said:
Have to ask, did you try the manual method to get into download?
Open Odin
Verify not connected to usb
Pull battery
Insert battery
While holding both up and down volume button, insert usb
BTW, many people have and will continue to say, you should always verify you can access download and recovery before attempting to apply any ROM.
Click to expand...
Click to collapse
Yeah, It was ridiculous of me not to. Oh well, we all make mistakes.
I tried that also and I still can't get into download mode. I really wanted to get into recovery so I could install the initial package for CM7, then apply the 3buttonfix.zip

ibrutalfatei said:
Can you explain how to do that? I'm not very good with ADB
Click to expand...
Click to collapse
adb push \source\file /target/dir/on/device
I have know idea if this will get you anywhere, but it may be worth a try until your jig arrives.

Get a jig.
Sent from my Captivate using XDA Premium App

I couldn't wait any longer.. went up to Radioshack, ask for a pack of 100K resistors. Now I have fixed my phone and I have Cyanogenmod 7 Running on it. One question, it says "Emergency Calls Only" anyway to fix that?

ibrutalfatei said:
I couldn't wait any longer.. went up to Radioshack, ask for a pack of 100K resistors. Now I have fixed my phone and I have Cyanogenmod 7 Running on it. One question, it says "Emergency Calls Only" anyway to fix that?
Click to expand...
Click to collapse
IIRC, that's the known issue on CM7. You need perform something on the phone everytime you reboot the phone. It pays to read them before you flash

How can't anybody give a simply adb command to flash an update.zip into a broke device???
Instead of that all of you are trying to make the user do thing alternatively!
There is command (adb or fastboot) for that or not?

ibrutalfatei said:
I couldn't wait any longer.. went up to Radioshack, ask for a pack of 100K resistors. Now I have fixed my phone and I have Cyanogenmod 7 Running on it. One question, it says "Emergency Calls Only" anyway to fix that?
Click to expand...
Click to collapse
No - ill give you 50$ for your bricked phone.
Sent from my SAMSUNG-SGH-I896 using XDA App

RevoToolkit...clockwork install?

tried to install clockwork recovery and Im getting a FATAL ERROR The MD5sum of the installed recovery and the stored MD5sum do not match! DO NOT REBOOT YOUR PHONE Please contact TheCubed ASAP! So any help here would be appreciated.
I used the new one click root for ginger bread which included the Revo toolkit and i tried to install clockwork recovery using 4.0.0.2-pr1, after it failed with the aboved message i tried the revostock option and got the same message, so what do i do now?
please help me TheCubed!

leppricon said:
tried to install clockwork recovery and Im getting a FATAL ERROR The MD5sum of the installed recovery and the stored MD5sum do not match! DO NOT REBOOT YOUR PHONE Please contact TheCubed ASAP! So any help here would be appreciated.
I used the new one click root for ginger bread which included the Revo toolkit and i tried to install clockwork recovery using 4.0.0.2-pr1, after it failed with the aboved message i tried the revostock option and got the same message, so what do i do now?
please help me TheCubed!
Click to expand...
Click to collapse
Try the 4.0.0.2-pr1 again and again until it goes through. DO NOT REBOOT YOUR PHONE UNTIL IT SUCCEEDS, IT WILL RESULT IN YOU BEING STUCK IN FASTBOOT!!!!!

Try deleting mlk file and reinstalling recovery
Sent from my VS910 4G using XDA App

Installed rom manager
I installed rom manager to use to back up phone it rebooted to run the back up and it got stuck in fast boot, so i did some searching and found the page on fixing that. i used the second posters method instead of thecubed (because he said it was easier and thecubed agreed) and now all i get is an lg start screen. do not follow the other guys post it is for another phone completely i had to find it out the hard way. so any ideas on how i can get back to working phone?

The file you deleted was the mmcbik0p8 backup found on your ext card. When reinstalling the recovery CWM should have rewritten it with the correct version.
Try removing your card and mounting it on a pc go in and manually delete file and try to boot the phone. I had to do this to make my revolution boot.

This is how i fixed it
adrenaline_rush said:
Its not hard to fix at all, you will have to install the Java JDK, Android SDK, and three files AdbWinApi.dll, fastboot.exe, and CWMrecoveryrevolution.img which is the clockwork recovery for our phone.
Here are the files in .rar format.
http://www.mediafire.com/?eb3219cy0lbc71m
Android SDK
Java JDK
The first version should work
1. Install the Android SDK to your C: drive. Make sure the SDK and all the files are in C:\androidSDK. This will make things easier later.
2. Open the SDK and install the additional AndroidSDK platform tools package
3. Install the Java JDK
4. Unzip the .rar to c:/androidSDK/tools
5. Open command prompt, start> type "cmd"> press enter
6. Plug in phone
6. Assuming you placed everything in the right folders, type the following into the command prompt
Code:
cd c:/androidSDK/tools
7. You should now be in the correct folder, paste this command next:
Code:
fastboot erase recovery
then:
Code:
fastboot flash recovery CWMrecoveryrevolution.img
If that succeeds then type the final command:
Code:
fastboot reboot
Hopefully this works and is understandable
Click to expand...
Click to collapse

Don't work
Yeah this method don't work any more I tried yesterday and today with the revolution file. Fast boot does not find the phone. Cmd is <waiting for device>. Going to Verizon tomorrow to get new phone.
Edit: why it doesn't work is because I used the easy method that the other user posted, i did not check the phone version of the flash file, so now my phone has the wrong firmware on it and wont boot. Also it does not get recognized by my pc.

leppricon said:
Yeah this method don't work any more I tried yesterday and today with the revolution file. Fast boot does not find the phone. Cmd is <waiting for device>. Going to Verizon tomorrow to get new phone.
Edit: why it doesn't work is because I used the easy method that the other user posted, i did not check the phone version of the flash file, so now my phone has the wrong firmware on it and wont boot. Also it does not get recognized by my pc.
Click to expand...
Click to collapse
You tried the volume up + power to get to the recovery?

Tried that too.
The only way the Vol. up and power button works if I have the battery out and the usb hooked up, and then the screen says do not detach download in progress. I left it this way for about two hours thinking it would magically fix it self but it didn't. Called Verizon about an hour ago and I going to get my new phone in the afternoon tomorrow. they over-nighting it to me, they said any new tech with 4g they try to get it fixed as fast as possible. I then asked when 4g would be coming to my area he said spring of 2013... lol

Oh, you could have flashed the .tot system file over, but I guess it does take some time to get the program set up, and they're already replacing it..

Tried
I had all the above programs installed and working properly, that is how i got to a non-working phone, I flashed it with the wrong firmware which bricked it. Its not detected in any of the programs because all the programs are looking for a revo and i flashed to something else.
This was posted in the revo fastboot fix thread, I followed it and it bricked my phone.
hello everyone, im pretty sure i was the first one to run into this issue since it happened twice on two different phones. but for an extremely easy fix just look here, believe me it doesn't get any easier than this. this is another way it was explained, but both are pretty much the same. im only posting this in case someone doesn't understand the directions posted by thecubed, not saying the ones i post it are better, just explained differently, not trying to step on anyone's shoes here http://forum.xda-developers.com/show....php?t=1088046
Last edited by zr0ko0l; 23rd June 2011 at 03:03 AM.
this is the reply from thecubed: Dont' worry about my toes
If you've got a better explanation, go for it! I'm not the best at writing instructions.

Still no CWM
I rooted my Revo using adb and zergrush. I'm running v6 and cannot get CWM to work using adb, RevoToolKit or even on a command line on the phone itself. So far all I've done is reload my phone. It stays rooted, but no CWM. Md5's all check out on mmcblk0p14 before I restart, using adb and a terminal on the phone. The checksum is right when I dl the recovery-cwm-pr1.img in the zip, also.
I did do an OTA update after I rooted. Could that be the problem? Should I unroot and reroot?

meandmine said:
I rooted my Revo using adb and zergrush. I'm running v6 and cannot get CWM to work using adb, RevoToolKit or even on a command line on the phone itself. So far all I've done is reload my phone. It stays rooted, but no CWM. Md5's all check out on mmcblk0p14 before I restart, using adb and a terminal on the phone. The checksum is right when I dl the recovery-cwm-pr1.img in the zip, also.
I did do an OTA update after I rooted. Could that be the problem? Should I unroot and reroot?
Click to expand...
Click to collapse
Why run V6 when V7 (aka GingerBread) is out?

meandmine said:
I rooted my Revo using adb and zergrush. I'm running v6 and cannot get CWM to work using adb, RevoToolKit or even on a command line on the phone itself. So far all I've done is reload my phone. It stays rooted, but no CWM. Md5's all check out on mmcblk0p14 before I restart, using adb and a terminal on the phone. The checksum is right when I dl the recovery-cwm-pr1.img in the zip, also.
I did do an OTA update after I rooted. Could that be the problem? Should I unroot and reroot?
Click to expand...
Click to collapse
DId you manually use adb and Zergrush or use a different method? Did you use my all in one package with the root.bat? More info would be greatly appreciated.

Issues activating 4G LTE
Hello all,
First post so woot! but, kind of bad news at the same time. My friend and I were rooting/CWM'ing/ROM'ing his phone and we hit this road block. Everything went find up to the flashing of Gingervolt. It boots up and starts the initial setup sequence, but after the step where it ask for language, it sits and spins it's wheels for a while before saying that it cannot find the SIM card. There is also a small SIM card icon with a question mark next to the signal bar meter. This step is keeping us from being able to move forward and was wondering if there is any hope to get this thing to activate.
Things we've tried:
1) Reboot, restore, wiped all the caches
2) Did a nandroid restore of before we flashed it with Gingervolt
3) Downloaded a stock/rooted ROM (and received the same results)
4) Calling Verizon's activation hotline (told us nothing)
5) Taking out/Putting back the SIM card and seeing if that maybe would reset something. (I guess not)
It would be really cool if I could figure this out so he doesn't have to bring it in to big red :3
Thanks and you all rock!
canti-sama

cantibot said:
Hello all,
First post so woot! but, kind of bad news at the same time. My friend and I were rooting/CWM'ing/ROM'ing his phone and we hit this road block. Everything went find up to the flashing of Gingervolt. It boots up and starts the initial setup sequence, but after the step where it ask for language, it sits and spins it's wheels for a while before saying that it cannot find the SIM card. There is also a small SIM card icon with a question mark next to the signal bar meter. This step is keeping us from being able to move forward and was wondering if there is any hope to get this thing to activate.
Things we've tried:
1) Reboot, restore, wiped all the caches
2) Did a nandroid restore of before we flashed it with Gingervolt
3) Downloaded a stock/rooted ROM (and received the same results)
4) Calling Verizon's activation hotline (told us nothing)
5) Taking out/Putting back the SIM card and seeing if that maybe would reset something. (I guess not)
It would be really cool if I could figure this out so he doesn't have to bring it in to big red :3
Thanks and you all rock!
canti-sama
Click to expand...
Click to collapse
Was 4g turned on when you flashed? If nothing else you can flash the zv7 tot file through lgnspt.

Thanks so much for your quick reply,
I think that is going to be my next option. Thanks for reassuring me that is the right direction! And yes, I did have 4g (It was called LTE, I think it's the same thing.) enabled before flash.

cantibot said:
Thanks so much for your quick reply,
I think that is going to be my next option. Thanks for reassuring me that is the right direction! And yes, I did have 4g (It was called LTE, I think it's the same thing.) enabled before flash.
Click to expand...
Click to collapse
What version were you on before you flashed Gingervolt? If you were on v4 or v6 it will do that.
Sent from my Gingervolt-ed VS910 4G using xda premium

I rooted it with adb following root.bat. I run linux and am a terminal junkie. The rooting went fine. I then dl'ed recovery-cwm-pr1.img and adb'ed it over to the sdcard, ran all the checksums, from adb and on a root terminal on the phone. Then from adb, moved the image file to block mmcblk0p14, ran checksums again from both adb and the terminal on the phone. They both checked out fine, again.
After reboot, it just wiped, no CWM. It might be a permissions problem. I see no execute bit set. Should it be?
This is a response to post #14. I meant to post this with a quote. Instead, I posted a quick reply. Sorry.

meandmine said:
I rooted it with adb following root.bat. I run linux and am a terminal junkie. The rooting went fine. I then dl'ed recovery-cwm-pr1.img and adb'ed it over to the sdcard, ran all the checksums, from adb and on a root terminal on the phone. Then from adb, moved the image file to block mmcblk0p14, ran checksums again from both adb and the terminal on the phone. They both checked out fine, again.
After reboot, it just wiped, no CWM. It might be a permissions problem. I see no execute bit set. Should it be?
Click to expand...
Click to collapse
Not a permission problem, there are a couple of files in there that have to be removed otherwise it blocks it from booting into cwm with the key press combo. You have to boot into cwm using quick boot or the reboot into recovery option in the revotoolkit menu. If you flash GingerVolt you will then have reboot and recovery in the power menu, but also will be able to enter recovery through the button combo.
You will have to push the recovery image again first though.

Down vol rocker broke, can't enter nvflash/smartflash/recovery?

Great, i tried to flash Hellfire's ICS rom, and for some freakin' reason, the phone got stuck at the hellfire loading screen and won't boot.
The problem is, my down vol button broke quite some time ago, and i can't use the power+vol down in order to save my phone. any ideas?

SoloSkull said:
Great, i tried to flash Hellfire's ICS rom, and for some freakin' reason, the phone got stuck at the hellfire loading screen and won't boot.
The problem is, my down vol button broke quite some time ago, and i can't use the power+vol down in order to save my phone. any ideas?
Click to expand...
Click to collapse
If you're lucky then it boots up enough to load adb.
Attach the usb cable, boot, open cmd and try if you find a device with adb devices
If yes you can easily tell it to reboot to recovery with reboot recovery and flash a new ROM.
Edit: As Hellfire is an ICS ROM you might need to use my modded adb drivers: http://forum.xda-developers.com/showthread.php?t=1752074

From what i know smathflash needs VOL UP to be used.

tonyp said:
If you're lucky then it boots up enough to load adb.
Attach the usb cable, boot, open cmd and try if you find a device with adb devices
If yes you can easily tell it to reboot to recovery with reboot recovery and flash a new ROM.
Edit: As Hellfire is an ICS ROM you might need to use my modded adb drivers: http://forum.xda-developers.com/showthread.php?t=1752074
Click to expand...
Click to collapse
I'm sorry, but i'm not really familiar on how ADB works..
Can you help me out? I'm not sure what am i supposed to do to tell it to reboot to recovery.
P.S. Well, i tried booting up my phone today and it's now stuck at the second LG logo (the one with a blue hue).

Man, if you really can't use adb why are you modding your phone?
I will supply you with adb when I come from work.
Sent from LG 2X using Tapatalk 3 Beta
EDit: I am not sure than this is all needed files to run, but you should be able to do your things by runnig CMD line in folder with adb tools unpacked from this archieve.

[Q] Moto x flashing recovery snafu - please help

RESOLVED!
so I just got my moto x dev edition, unlocked the bootloader, and then screwed it up...
i tried flashing the recovery as described here, http://forum.xda-developers.com/showthread.php?t=2458451 but didn't realize/understand that fastboot and mfastboot were not interchangeable. it looked like it went ok, but I wasn't able to reboot into recovery. so, now on boot to recovery i get the little android on his back with a red triangle. i'm pretty sure that the stock recovery is gone, but cwm is not installed either. which brings me to my next little problem...
so i did some reading and got mfastboot installed and thought ok I just need to reflash cwm on phone again. problem is, now the phone won't stay in usb debug mode so that i can see it when fastbooted. that is, when i reboot the phone into fastboot by holding the power/vol down I can't see the phone when doing 'adb devices', and whem I let it boot up i see usb debug is switched off. when i switch it on, then i can see the phone from adb again, but when i try to 'reboot bootloader' it gives me a not allowed error.
at this point i'm just sick and afraid i bricked it. i am coming from a galaxy nexus and never had anything like this happen before. i truly appreciate any help here, at this point i feel like puking and dreading telling the wife i just blew 450.... :-/
ps i'm on mac 10.7 so if i need rsd it will be via a virtual machine....

herrdrchili said:
so I just got my moto x dev edition, unlocked the bootloader, and then screwed it up...
i tried flashing the recovery as described here, http://forum.xda-developers.com/showthread.php?t=2458451 but didn't realize/understand that fastboot and mfastboot were not interchangeable. it looked like it went ok, but I wasn't able to reboot into recovery. so, now on boot to recovery i get the little android on his back with a red triangle. i'm pretty sure that the stock recovery is gone, but cwm is not installed either. which brings me to my next little problem...
so i did some reading and got mfastboot installed and thought ok I just need to reflash cwm on phone again. problem is, now the phone won't stay in usb debug mode so that i can see it when fastbooted. that is, when i reboot the phone into fastboot by holding the power/vol down I can't see the phone when doing 'adb devices', and whem I let it boot up i see usb debug is switched off. when i switch it on, then i can see the phone from adb again, but when i try to 'reboot bootloader' it gives me a not allowed error.
at this point i'm just sick and afraid i bricked it. i am coming from a galaxy nexus and never had anything like this happen before. i truly appreciate any help here, at this point i feel like puking and dreading telling the wife i just blew 450.... :-/
ps i'm on mac 10.7 so if i need rsd it will be via a virtual machine....
Click to expand...
Click to collapse
so, if i understand you correctly, u've held down the volume down button and power button? becasue that's your fastboot. That's where you need to be to use RSD, and that's what i'd do.

ADB commands aren't used in fastboot mode. You should be able to see the device in fastboot mode with the command fastboot devices. Also, remember that the stock rom will try to restore the stock recovery when it is booted so if you flash recovery in fastboot mode then let the stock rom boot it will reflash the stock recovery which shows you the little droid and the red triangle.
You should still be okay though. Shut the phone off and boot into fastboot manually with power and volume down. Reflash the recovery. I know there are warnings about using mfastboot but I used standard fastboot before I saw those and didn't have an issue. From the fastboot screen after flashing the recovery, use volume down to get to highlight recovery and then press volume up to select, not power. Power will just do a standard reboot.
If you flashed twrp recovery then rebooting system will prompt you to install su. I think clockwork does the same thing. Letting the recovery install su will also prevent the stock recovery from getting restored and from there you should be good.
herrdrchili said:
so I just got my moto x dev edition, unlocked the bootloader, and then screwed it up...
i tried flashing the recovery as described here, http://forum.xda-developers.com/showthread.php?t=2458451 but didn't realize/understand that fastboot and mfastboot were not interchangeable. it looked like it went ok, but I wasn't able to reboot into recovery. so, now on boot to recovery i get the little android on his back with a red triangle. i'm pretty sure that the stock recovery is gone, but cwm is not installed either. which brings me to my next little problem...
so i did some reading and got mfastboot installed and thought ok I just need to reflash cwm on phone again. problem is, now the phone won't stay in usb debug mode so that i can see it when fastbooted. that is, when i reboot the phone into fastboot by holding the power/vol down I can't see the phone when doing 'adb devices', and whem I let it boot up i see usb debug is switched off. when i switch it on, then i can see the phone from adb again, but when i try to 'reboot bootloader' it gives me a not allowed error.
at this point i'm just sick and afraid i bricked it. i am coming from a galaxy nexus and never had anything like this happen before. i truly appreciate any help here, at this point i feel like puking and dreading telling the wife i just blew 450.... :-/
ps i'm on mac 10.7 so if i need rsd it will be via a virtual machine....
Click to expand...
Click to collapse

ok then - i guess rsd has potential?
xpsychox said:
so, if i understand you correctly, u've held down the volume down button and power button? becasue that's your fastboot. That's where you need to be to use RSD, and that's what i'd do.
Click to expand...
Click to collapse
i can reboot into fastboot, but adb can't see the phone. I'll start trying to setup rsd and and see if it can do any better. any good links you know to get up to speed on that would be appreciated. if you know how to simply reflash the recovery via rsd that would be helpful too - thanks in advance!

herrdrchili said:
i can reboot into fastboot, but adb can't see the phone. I'll start trying to setup rsd and and see if it can do any better. any good links you know to get up to speed on that would be appreciated. if you know how to simply reflash the recovery via rsd that would be helpful too - thanks in advance!
Click to expand...
Click to collapse
the sites that I know of are for the device I have, a non devliper edition... I don't know if it makes a difference, I don't wanna make anything worse.

thanks for the sanity check,,,
btdonovan said:
ADB commands aren't used in fastboot mode. You should be able to see the device in fastboot mode with the command fastboot devices. Also, remember that the stock rom will try to restore the stock recovery when it is booted so if you flash recovery in fastboot mode then let the stock rom boot it will reflash the stock recovery which shows you the little droid and the red triangle.
You should still be okay though. Shut the phone off and boot into fastboot manually with power and volume down. Reflash the recovery. I know there are warnings about using mfastboot but I used standard fastboot before I saw those and didn't have an issue. From the fastboot screen after flashing the recovery, use volume down to get to highlight recovery and then press volume up to select, not power. Power will just do a standard reboot.
If you flashed twrp recovery then rebooting system will prompt you to install su. I think clockwork does the same thing. Letting the recovery install su will also prevent the stock recovery from getting restored and from there you should be good.
Click to expand...
Click to collapse
THANKS! just needed another set of eyes - man i need to not try doing this after a long day again i really appreciate your help. i got it now!

herrdrchili said:
THANKS! just needed another set of eyes - man i need to not try doing this after a long day again i really appreciate your help. i got it now!
Click to expand...
Click to collapse
Glad I could help!