Database Users

[Q] fastboot - no boot or img file

hey guys i'm having some trouble. i just got the nexus (it's my first smartphone, ever) and i've tried to hit the ground running. here's what i've done to the phone so far.
i got all the drivers running on my win7 machine and also installed the android SDK folder onto C: as was described in this thread: http://forum.xda-developers.com/showthread.php?t=878786
i then unlocked the bootloader using the above guide as well. when I power on the phone using UP+POWER it says UNLOCKED.
I then proceeded to follow this guide: http://forum.xda-developers.com/showthread.php?t=875875
i used ADB to flash the clockwork crespo recovery. i then used fastboot to install Superuser.
at that point i had an unlocked bootloader, clockword recovery image and superuser permissions.
i then saw that the 2.3.1 update had been released. i wanted to learn how to tackle that so i started reading up. i noticed that people were using ROM Manager and Titanium. I got titanium and installed the BusyBox addon and it allowed me to do a full Batch Backup of all my programs, etc. i've got the 50MB or so backup folder on my PC now.
anyway, i then messed with Rom Manager. I installed the 3.0.0.0 ClockworkMod Recovery and everything went smoothly. now this is where my troubles begin.
when i go to Download ROM all i get is a Free Stuff area.
when i go to Check for ROM Updates it tells me my device isnt set up for OTA updates.
those are just minor issues.
this is the big and scary issue i have:
when i click on reboot to recovery, it takes me to the same screen that i go to when i power on with VOLUME UP+POWER. it doesnt take me to the recovery screen that i see in various youtube videos. instead, i'm at the main screen where it says UNLOCKED and i have 4 choices (reboot bootloader, recovery, reboot, power off). and on the very top in RED letters it says fastboot - no boot or img file. <-- this is the part that makes me nervous. If i manually power down the phone and boot to fastboot and click recovery, it just goes back to this same screen and says fastboot - no boot or img file. when i first rooted the phone, clicking recovery actually took me to a different screen where i was able to load up superuser.zip and install it.
did i accidetnally delete something that i wasnt supposed to? did installing ROM manager mess something up? i typically dont do anything until i confirm that i am supposed to. i think the problem is that i dont yet know how one thing i do on the phone affects another. i'm guessing when i used rom manager to update the CWmod it changed some folders/files? i dunno!
otherwise, the phone works fine and there are no glitches or hiccups or crashes. So if someone can please take a moment to just explain to me what i did wrong or what i failed to do i'd really, really appreciate it.

you don't have a recovery partition. Either flash one over manually using fastboot, or boot up and try to use ROM Manager to flash CWR.

when you say flash one over using fastboot, do you mean put my phone using VOLUME UP + POWER, connect usb cable, then use command line to do this:
fastboot flash recovery recovery-clockwork-crespo.img
?

kramer987 said:
when you say flash one over using fastboot, do you mean put my phone using VOLUME UP + POWER, connect usb cable, then use command line to do this:
fastboot flash recovery recovery-clockwork-crespo.img
?
Click to expand...
Click to collapse
yes, just follow the examples in http://forum.xda-developers.com/showthread.php?t=875875

kramer987 said:
when you say flash one over using fastboot, do you mean put my phone using VOLUME UP + POWER, connect usb cable, then use command line to do this:
fastboot flash recovery recovery-clockwork-crespo.img
?
Click to expand...
Click to collapse
Yes, 'cept it will be "fastboot flash recoveryrecovery-clockwork-3.0.0.0-crespo.img" without the quotes now.
But does it say that you're missing a boot.img or recovery.img?
Also, the "not set up for OTA" thing isn't for official OTAs. Some developers have made their custom ROMs capable of being updated that way.

unremarked said:
Yes, 'cept it will be "fastboot flash recoveryrecovery-clockwork-3.0.0.0-crespo.img" without the quotes now.
But does it say that you're missing a boot.img or recovery.img?
Also, the "not set up for OTA" thing isn't for official OTAs. Some developers have made their custom ROMs capable of being updated that way.
Click to expand...
Click to collapse
thank you luxferro and unremarked. i did it and it works perfectly. i am now able to access clockworkmod recovery 3.0.0.0. next step is backup my existing ROM and also to figure out how to put the OTA 2.3.1 on and restore all my data
oh and unremarked: it basically said no boot or img file and thats it after i would click on recovery or reboot to recovery trhough rom manager. it was just in red at the top. but now it takes me to the ClockworkMod Recovery

Can't downgrade MT4G?

Hi all, I am going to be as thorough as I can. I am rather new, and I'm stuck trying to downgrade my MT4G to froyo (PD15IMG). I have read the tutorials, and learned enough about adb to attempt this task, but I think by doing the HTC Bootloader unlocking update last week, it may be the reason I'm stuck. I follow the instructions on the tutorial, to gain temp root, until I get to the part where I should get a "#" in the command Window when I type "adb shell" but I keep getting "$" instead, although everything seems to be going ok until I get to that point.
*Also, I put the PD15IMG.zip on the root of my sd card, and start my phone in bootloader mode, and it finds the PD15IMG.zip, and a blue progress bar appears in the top right corner of my phone for about 90 seconds, it then displays "parsing PD15IMG.zip" then stops at the hboot screen and does nothing. I just select power down, then power on my phone and nothing will have been done to my phone. I guess what I need to know is, by doing the HTC bootloader unlock update (which I did before I read that it was a bad idea), can I still downgrade and root with normal methods, or will I have to do something different?
Sent from my HTC Glacier using Tapatalk

You can start differently. Since you've unlocked the bootloader, try to flash recovery directly, by downloading recovery image directly from Clockworkmod site, rebooting to FASTBOOT (adb reboot bootloader) and using the command "fastboot flash recovery your_just_downloaded_recovery.img".
If recovery flash doesn't work for you - download the 2.2.1 PD15IMG, unzip it, and flash the following 2 files from it:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase userdata
Then reboot. You should end up on 2.2.1, which is perm-rootable using the guide (Visionary for temp-root, gfree for S-OFF, and then perm-root if you want).
Then flash the recovery and the engineering bootloader.

Here is what I did, I am giving a link to pastebin as instructed, it seems to go perfectly until I try to flash the StockRom. In the meantime I will attempt what was just posted above^^^^^^^ http://pastebin.com/fYrC6tAZ

One last thing before i have to throw away my phone. I couldnt leave well enough alone. I did this "fastboot flash boot boot.img" as you stated in the post above. It was successful. I then entered this one "fastboot flash system system.img", and it failed (said the img was too big or something) so I did the "fastboot-windows reboot" command and it is now stuck on the white HTC MyTouch 4g splashscreen. Is my phone toast? My PC no longer recognizes that my phone is connected to the USB port, however I can hold the volume dwn & power button and it comes on in the hboot mode.Is there any hope?
Also, when I boot it up by vol/dwn & pwr, the Hboot screen comes up and finds the PD15IMG that is on my sd card, goes through a 1 minute or so process (a blue status bar loads in top right corner), then it just stays on the hboot. It did that before it stuck on the splash screen, but never actually wrote anything i dont beleive.
OK its letting me use FASTBOOT and here is exactly what I got when i tried to flash the 2nd file in your post above. It came from the PD15IMG.zip as you instructed:
C:\adb>fastboot flash system system.img
sending 'system' (571388 KB)... FAILED (remote: data length is too large)
finished. total time: 0.016s

Can someone please let me know if there is hope for my phone? I can communicate with it through Fastboot (on my PC) and it will boot up in hboot mode. But it WON'T go past the Tmobile/MyTouch splash screen. If I get it fixed, I promise to never touch it again until I study! I truly feel there is hope, but I think don't know enough to figure it out. I loaded the PD15IMG on my SD, and it attempts to flash it, (a blue status bar appears in top right corner and fills up in about 90 seconds), but afterwards, it still sticks on splashscreen. Is there anything I can do to fix it? Anything I can flash it with in Fastboot? Please anyone?

You mixed 2 ways, and did it completely wrong way. And you didn't attempt to flash the recovery at all.
The first part, that went well (till ./flashgc), already prepared your phone for downgrading, and you should have recognized and understood it. You don't need anything else, no flashes from bootloader or anything. All you needed was to continue - put PD15IMG.ZIP on the SD card, reboot into bootloader, and let it downgrade.
You can still do it, so please do.
---------- Post added at 06:16 PM ---------- Previous post was at 06:13 PM ----------
Once you end up on 2.2.1, please follow the "Ultimate rooting guide" from Development section, and flash Engineering bootloader.

Jack_R1 said:
You mixed 2 ways, and did it completely wrong way. And you didn't attempt to flash the recovery at all.
The first part, that went well (till ./flashgc), already prepared your phone for downgrading, and you should have recognized and understood it. You don't need anything else, no flashes from bootloader or anything. All you needed was to continue - put PD15IMG.ZIP on the SD card, reboot into bootloader, and let it downgrade.
You can still do it, so please do.
---------- Post added at 06:16 PM ---------- Previous post was at 06:13 PM ----------
Once you end up on 2.2.1, please follow the "Ultimate rooting guide" from Development section, and flash Engineering bootloader.
Click to expand...
Click to collapse
Thank for your response. I have tried doing the PD15IMG.zip by booting my phone in bootloader mode. It finds the PD15IMG.zip and then a blue progress bar appears in the top right corner of the phone, finishes in about 90 seconds, the a message appears that says "wrong zip file". I would be happy just to get my phone back on with the gingerbread 2.3.4 on it, and simply leave it alone until I know what Im doing. Is there a way to just flash the original s/w back on it? If so if you could tell me how I will not mess with it again until I study alot more. But flashing the PD15IMG doesnt appear to be working for me.

Download the file again, and check MD5SUM on it before you use it.
If it responds "wrong ZIP" - it's because the ZIP is corrupted. When you'll download a good ZIP, it'll work.

Jack_R1 said:
Download the file again, and check MD5SUM on it before you use it.
If it responds "wrong ZIP" - it's because the ZIP is corrupted. When you'll download a good ZIP, it'll work.
Click to expand...
Click to collapse
Ok you were right, the one I had the wrong MD5SUM, but i d/l the correct one, it had the correct MD5SUM, but it still gave me the "wrong zip file error". I feel like there is hope, but I cant figure this out!! Thank you for trying, is there anything else I can do? I also tried going into recovery and doing factory reset/ data wipe etc...but it continues to get stuck on the splash screen....

How did you copy the correct one to the phone's SD card, and where did you put it? You either didn't copy it to your SD card, or named it wrong, or put it in wrong location, not overwriting the older file.
In any case, if flashing PD15IMG fails for you:
Download CWM recovery from here:
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-glacier.img
Boot to bootloader.
Enter FASTBOOT.
Execute:
fastboot flash recovery recovery-clockwork-5.0.2.0-glacier.img
Boot to recovery. You should have Clockworkmod.
Download a stock rooted 2.2.1 ROM from Development section.
Flash it in Clockworkmod recovery.
Extract boot.img from this ROM.
Flash it in fastboot, using "fastboot flash boot boot.img".
Boot into the ROM.
Proceed with gfree.

OK!! I got it fixed and it all makes sense to me now! I flashed the 2.2.1 boot.img to my phone, when it still had the 2.3.4 on it. It was as simple as that. I hadnt flashed the downgrade on it when I flashed the boot.img and I guess it was a mismatch. I read your last post to extract the "boot.img" from the rom and then it clicked! Yesterday I wrote the 2.2.1 boot img. to a phone that had 2.3.4...so I found a stock 2.3.4 rom, extracted the boot.img from it a BAM! its rolling again....thank you so much....

Yes, indeed, you flashed a mismatched, older kernel to your ROM. I was suggesting that you install custom recovery and change the ROM to match your boot.img, but the other way around also works - as long as you don't need to root your phone, that is.

Jack_R1 said:
Yes, indeed, you flashed a mismatched, older kernel to your ROM. I was suggesting that you install custom recovery and change the ROM to match your boot.img, but the other way around also works - as long as you don't need to root your phone, that is.
Click to expand...
Click to collapse
Well I will soon attempt it again, however I think I need to read a little more so I can understand the concept of what I am doing. I learned a ton by making that mistake. But as soo as I got it fixed, I couldnt resist, I used revovery and flashed [ROM]:: ProjectMIUI 2.2.17 [R6]- UPDATED 2/21/12 - [Stable + Smooth from the DEV section and I have never been happier with my phones performance! I will soon try the cyanmod, but I want to chill with this rom for a week or so. Again, I appreciate your help, I learned alot.

As long as you don't mind flashing kernels separately using fastboot for each ROM you flash, you can go indefinitely and flash ROMs as much as you like with your current setup, not needing anything else. The only good reason for you to go for S-OFF would be to flash Engineering HBOOT, to be able to flash kernels from recovery directly, avoiding extra fastboot step.
Also, thanks for finally confirming that you can flash recovery using fastboot on HTC-Dev-unlocked device. There was one device that didn't allow it (I think Incredible S, but not sure), so it's good to know that on MT4G it works as it should.

I'm bricked .. Getting worries. (Yes I've read the forums ...)

Attempted to flash Liquid Jelly Bean, then got stuck on the animation boot screen. I've tried Root tool kit for unbricking and setting it back to stock. Tell me it's successful but stays stuck on the animation screen.
I've also tried to unbrick manually however even though I have the correct files placed in my Platform Tools folder of Android SDK ... I constantly get stuck at the CMD prompt steps. Any time I type in "ADB reboot loader" or ..."fastboot flash bootloader bootloader-grouper-3.34.img" or anything similar I get the error message in CMD saying "___ Is not recognized as an internal or external command"
I'm not sure what to do. The bootloader does say that my device is locked, I just can't get passed the splash screen!

Rovon said:
Attempted to flash Liquid Jelly Bean, then got stuck on the animation boot screen. I've tried Root tool kit for unbricking and setting it back to stock. Tell me it's successful but stays stuck on the animation screen.
I've also tried to unbrick manually however even though I have the correct files placed in my Platform Tools folder of Android SDK ... I constantly get stuck at the CMD prompt steps. Any time I type in "fastboot flash bootloader bootloader-grouper-3.34.img" or anything similar I get the error message in CMD saying "___ Is not recognized as an internal or external command"
I'm not sure what to do. The bootloader does say that my device is locked, I just can't get passed the splash screen!
Click to expand...
Click to collapse
Use Wugfresh's toolkit and press "return to stock"

rohan32 said:
Use Wugfresh's toolkit and press "return to stock"
Click to expand...
Click to collapse
"I've tried Root tool kit for unbricking and setting it back to stock. Tell me it's successful but stays stuck on the animation screen. "

Here's an update:
I think I've made it worse ...
Nothing will boot now and it's currently locked. Any time I hit "Start" it says "Booting Failed"
My CMD now says; Error: Cannot Load "Bootloader Grouper-3.34.img"
I'm seriously lost. I've been working on this for about 6 hours now ....

Can you get into bootloader and then recovery by holding the power and volume down buttons? Was ADB actually working before all of this??

markj338 said:
Can you get into bootloader and then recovery by holding the power and volume down buttons? Was ADB actually working before all of this??
Click to expand...
Click to collapse
Nope. Nothing is allowing me to get into recovery. At first it was just stuck on the google screen now it says "boot failed"

Rovon said:
Nope. Nothing is allowing me to get into recovery. At first it was just stuck on the google screen now it says "boot failed"
Click to expand...
Click to collapse
Where does it say boot failed? On the device?

markj338 said:
Where does it say boot failed? On the device?
Click to expand...
Click to collapse
Yes. Top left hand corner.

Rovon said:
Yes. Top left hand corner.
Click to expand...
Click to collapse
I know I have asked this before but I don't know if I was clear
You can't go to bootloader, and press the volume buttons to go to recovery?

markj338 said:
I know I have asked this before but I don't know if I was clear
You can't go to bootloader, and press the volume buttons to go to recovery?
Click to expand...
Click to collapse
No I can't get into the recovery at all. When I turn on the device I don't even need to use the rocker keys to get into bootloader either. Actually my bootloader is a bit different now too. I have the 'Google' logo and at the top the regular options for Start, Recovery, Power Off, etc.
In simple terms: I can't even get to the animated splash screen anymore

Open the command prompt IN the directly WITH fastboot
Fastboot oem unlock
Then wipe / flash factory images. Fastboot -w update image whatever the image name is.
Then uninstall / delete that stupid toolkit and never use them stupid craps again.

Are you still able to communicate with the device via fastboot? If you issue the command 'fastboot devices' does it return a serial number?
Edit: I'm going to bed so if you are able to use fastboot, download the factory image pack from https://dl.google.com/dl/android/aosp/nakasi-jro03d-factory-e102ba72.tgz
Extract the archive. Inside are there will be an install script, manually issue the commands contained in the script in fastboot. The only thing you need to add is the location of the .img and .zip files from the archive you extracted e.g. 'fastboot flash recovery c:/Users/name/desktop/recovery.IMG'
There is no reason this will not get you up and running again.
Sent from my Nexus 7 using xda app-developers app

Alkaloid said:
Are you still able to communicate with the device via fastboot? If you issue the command 'fastboot devices' does it return a serial number?
Edit: I'm going to bed so if you are able to use fastboot, download the factory image pack from https://dl.google.com/dl/android/aosp/nakasi-jro03d-factory-e102ba72.tgz
Extract the archive. Inside are there will be an install script, manually issue the commands contained in the script in fastboot. The only thing you need to add is the location of the .img and .zip files from the archive you extracted e.g. 'fastboot flash recovery c:/Users/name/desktop/recovery.IMG'
There is no reason this will not get you up and running again.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks for your response.
I've followed the instructions in the file. From previous research, I've had these files. My device does communicate with Fastboot. When I give the command for Devices it gives me my serial. Also, when I ask it to reboot-bootloader in CMD it does.
My issue is when I get to "Fastboot flash bootloader-grouper-3.34.img". CMD states "Error: Cannot load bootloader-grouper-3.34.img"
I've followed the commands previous to that. (Erase boot, cache, recovery, system, userdata)
Open the command prompt IN the directly WITH fastboot
Fastboot oem unlock
Then wipe / flash factory images. Fastboot -w update image whatever the image name is.
Then uninstall / delete that stupid toolkit and never use them stupid craps again.
Click to expand...
Click to collapse
Yes my device is unlocked again, but I still can't get into recovery mode. It just tells me "Recovery Failed" in small text in the upper left hand corner of my N7.

UPDATE:
After unlocking the device again. I used the Nexus Root Toolkit to restore to factory settings and it worked
The Problem: My device was no responding correctly to the toolkit when locked.
Cheers for the help. I'll attempt to root again, hopefully no problems this time If there are I'll be sure to post again!
Thanks to everyone that replied.

Rovon said:
UPDATE:
After unlocking the device again. I used the Nexus Root Toolkit to restore to factory settings and it worked
The Problem: My device was no responding correctly to the toolkit when locked.
Cheers for the help. I'll attempt to root again, hopefully no problems this time If there are I'll be sure to post again!
Thanks to everyone that replied.
Click to expand...
Click to collapse
For the love of God..stop using the toolkit from here on out.. learn how to use ADB and Fastboot so you can avoid these issues.
Sent from my Galaxy Nexus using Tapatalk 2

So you erased the recovery then wonder why you could not boot into recovery....
You flashed or tried to flash the bootloader. You already had the same bootloader installed and there was no need to do so to try and fix your issue.
You still don't know what you're doing and are back using the tool that lead you to this issues. A toolkit. Learn what you're doing and you wont face this type of silly issue again.

Rovon said:
UPDATE:
After unlocking the device again. I used the Nexus Root Toolkit to restore to factory settings and it worked
The Problem: My device was no responding correctly to the toolkit when locked.
Cheers for the help. I'll attempt to root again, hopefully no problems this time If there are I'll be sure to post again!
Thanks to everyone that replied.
Click to expand...
Click to collapse
I think you should reread this post and hit the thanks button of everyone who took the time to help you out of this mess - its good manners. Oh, and learn how to use adb & fastboot
Sent from my Nexus 7 using xda premium

Inaccessible boot loader :/
If you try to fastboot flash all you get nothing?
Sent from my Nexus 7 using xda app-developers app
---------
nvm you fixed it, good job
Don't use toolkits. Most people don't have a clue what the toolkit is actually doing so if something goes wrong they aren't in a good position

Its always nice to see threads like these where the N7 in the face of death but in the end with cutting edge medical technology it is brought back to life and healthy.

[Q] Huge Problem!!! Please help...

Hello everyone!!! I have a huge problem and i need help... I own a Nexus 4 and about 3-4 days ago I unlocked/rooted/intalled custom recovery using the nexus 4 toolkit... Everything was going well until today that I decided to flash the "touch" version of Clockworkmod Recovery but in the wrong way (as it prooved).So I downloaded the latest image file and decided to install it through the toolkit. I put the .img file in the "recovery folder of the toolkit (C:\Google Nexus 4 ToolKit\recovery) but the program didn't see it so i tried to put it here (C:\Google Nexus 4 ToolKit\put_img_files_to_flash_here) and make the toolkit steps for "Boot or flash .img files to device". I pluggeg my phone and followed these excact steps:
1. Boot or flash .img files to device
2.Wrote the excact name of the img.file as the toolkit asked me (the file was found by the toolkit
3.Asked me if i want to 1.boot or 2.flash. I selected 2.flash
4.Asked to which partition i wanted to flash the file and i selected 5.Recovery
After these steps and after the installation was succesfull i selected "recovery mode" from fastboot menu to see if it was installed and I'm stuck there with a black screen and the backlight on!
I'm really begging you don't try to make me feel worst by telling me what I should have done to do things right... Just try to help me in some way (If there is any) so i can make things right!!!
Thank you very much!

ΛKIS.DΛL said:
Hello everyone!!! I have a huge problem and i need help... I own a Nexus 4 and about 3-4 days ago I unlocked/rooted/intalled custom recovery using the nexus 4 toolkit... Everything was going well until today that I decided to flash the "touch" version of Clockworkmod Recovery but in the wrong way (as it prooved).So I downloaded the latest image file and decided to install it through the toolkit. I put the .img file in the "recovery folder of the toolkit (C:\Google Nexus 4 ToolKit\recovery) but the program didn't see it so i tried to put it here (C:\Google Nexus 4 ToolKit\put_img_files_to_flash_here) and make the toolkit steps for "Boot or flash .img files to device". I pluggeg my phone and followed these excact steps:
1. Boot or flash .img files to device
2.Wrote the excact name of the img.file as the toolkit asked me (the file was found by the toolkit
3.Asked me if i want to 1.boot or 2.flash. I selected 2.flash
4.Asked to which partition i wanted to flash the file and i selected 5.Recovery
After these steps and after the installation was succesfull i selected "recovery mode" from fastboot menu to see if it was installed and I'm stuck there with a black screen and the backlight on! Fastboot mode by turning off the phone and press volume down and then the power button.
I'm really begging you don't try to make me feel worst by telling me what I should have done to do things right... Just try to help me in some way (If there is any) so i can make things right!!!
Thank you very much!
Click to expand...
Click to collapse
Install adb (platform-tools) and flash the recovery again in fastboot. Command: fastboot flash recovery namerecovery.img. To get into fastboot mode turn the phone off, then press volume down and power button.

Flash the recovery via fastboot.
If you don't have the required drivers/software on your cpu, install it. This is the best, easiest way to do it and it can save your ass in any number of ways to have the right stuff.

Pffff...
I actually did something and solve my "problem"...
I pushed & Hold the power button and the phone actually shut down... :laugh:
So I turned it on again and installed clockworkmod from rom manager... :silly:
It seems that i was just too scared to do anything...
Anyway...Was that something that accidently happen or I used the wrong way to flash the recovery?
Thanks for the response & help! :good:

ΛKIS.DΛL said:
I actually did something and solve my "problem"...
I pushed & Hold the power button and the phone actually shut down... :laugh:
So I turned it on again and installed clockworkmod from rom manager... :silly:
It seems that i was just too scared to do anything...
Anyway...Was that something that accidently happen or I used the wrong way to flash the recovery?
Thanks for the response & help! :good:
Click to expand...
Click to collapse
Not sure; I don't know the steps the toolkit takes. Might have been as simple as it not erasing cache after flashing the img.
Regardless, I highly recommend you install the Android SDK.

CMNein said:
Not sure; I don't know the steps the toolkit takes. Might have been as simple as it not erasing cache after flashing the img.
Regardless, I highly recommend you install the Android SDK.
Click to expand...
Click to collapse
Ok! I'll make a search on what it is and how to install it and I will... Thanks again for helping!

ΛKIS.DΛL said:
Ok! I'll make a search on what it is and how to install it and I will... Thanks again for helping!
Click to expand...
Click to collapse
Look here for adb installation http://forum.xda-developers.com/showthread.php?t=1474956, even includes video tutorial.

Can't boot or flash to TWRP or CMW

Today I tried booting up to recovery (power+vol down), after choosing Recovery Mode from the menu and hitting Power button, it gets to a screen with the green Android guy with a red triangle and just stays there.
So I rebooted the phone. Launch Nexus Root Toolkit, I tried to install CWM or TWRP, neither works. It gets to the same recovery mode and gets stuck there, only this time, it gets stuck on the Google logo instead of the Android guy with red triangle. I even try to flash stock recovery, and it also doesn't work.
Why can't I get into CWM or TWRP nor can I flash them?
Thanks for any help.

bebopblues said:
Today I tried booting up to recovery (power+vol down), after choosing Recovery Mode from the menu and hitting Power button, it gets to a screen with the green Android guy with a red triangle and just stays there.
So I rebooted the phone. Launch Nexus Root Toolkit, I tried to install CWM or TWRP, neither works. It gets to the same recovery mode and gets stuck there, only this time, it gets stuck on the Google logo instead of the Android guy with red triangle. I even try to flash stock recovery, and it also doesn't work.
Why can't I get into CWM or TWRP nor can I flash them?
Thanks for any help.
Click to expand...
Click to collapse
Be sure u are bootloader unlocked.
Android guy is normal... Is a safety step before entering on stock recovery, to pass that: hold power and hit once volume +
Probably u cant flash images cuz fastboot isnt working(old fastboot.exe file), wrong recovery file,...
sent from my NEXUS 4 tasting a revamped cooking recipe of Jellybeans (stock 4.3).

C4SCA said:
Be sure u are bootloader unlocked.
Android guy is normal... Is a safety step before entering on stock recovery, to pass that: hold power and hit once volume +
Probably u cant flash images cuz fastboot isnt working(old fastboot.exe file), wrong recovery file,...
sent from my NEXUS 4 tasting a revamped cooking recipe of Jellybeans (stock 4.3).
Click to expand...
Click to collapse
Bootloader was unlocked. I launched the CMD Prompt from Nexus Root Toolkit and ran the fastboot command to manually flash the downloaded CWM and it worked.
Code:
adb reboot bootloader
fastboot flash recovery recovery-clockwork-x.x.x.x-mako.img
So maybe something's odd about the simple one-click utilities in Nexus Root Toolkit that is not working.
Thanks for the help nonetheless. :good:

bebopblues said:
Bootloader was unlocked. I launched the CMD Prompt from Nexus Root Toolkit and ran the fastboot command to manually flash the downloaded CWM and it worked.
Code:
adb reboot bootloader
fastboot flash recovery recovery-clockwork-x.x.x.x-mako.img
So maybe something's odd about the simple one-click utilities in Nexus Root Toolkit that is not working.
Thanks for the help nonetheless. :good:
Click to expand...
Click to collapse
well ui never used tollkits... i like to know what im doing, and IMO doing it urself is better wich turned out to be true in ur case
im glad u got it working