flashing an image

[MonKENy]

I downloaded the CWR touch image but am not sure what the command is to flash it. Can someone tell me por favor?

 

[cupfulloflol]

I downloaded the CWR touch image but am not sure what the command is to flash it. Can someone tell me por favor?

fastboot flash recovery *name of CWRtouch*.img

replacing *name of CWRtouch with whatever the img filename may be.

 

[MonKENy]

then how do I use it when its flashed? I dont see anything different in my recovery

 

[cupfulloflol]

then how do I use it when its flashed? I dont see anything different in my recovery

Is the stock recovery coming back? If so, you probably haven't deleted or removed the /system/recovery-from-boot.p file.

 

[MonKENy]

I searched, I dont see a recovery-from-boot.p anywhere on my phone

 

[cupfulloflol]

Did you rename/move/delete the file (a lot of unlocking/root methods will get you to do something with this file in their guide)?

Have you installed a custom recovery already? Does it work?

E2A: If you have adb working, you can type adb shell ls /system/ and see if you see the file that way.

 

[MonKENy]

I dont think I have adb. Do you mean like the old adb interface we used w/the older droids? I could never get that to work after the first time a few years back.

 

[cupfulloflol]

I dont think I have adb. Do you mean like the old adb interface we used w/the older droids? I could never get that to work after the first time a few years back.

That is the one and only adb. Quite a few unlock/root methods will get you to setup and use adb along with fastboot (both are part of the sdk). It isn't necessary to use adb to verify if the file has been renamed/removed/or whatever. I just know some folks aren't too keen on installing apps, and since a lot of root methods should have you install/setup the SDK, I figured adb would be available for you. A file explorer (like https://play.google.com/store/apps/details?id=pl.solidexplorer ) or a terminal emulator ( like https://play.google.com/store/apps/details?id=jackpal.androidterm ) can also accomplish this same task.

If you already have a sticking custom recovery, the file is gone and it doesn't matter about anything I said in the previous paragraph. The recovery-from-boot.p file on boot verifies if you have a stock recovery, and if not, puts the stock recovery back. So you can flash a recovery in fastboot, reboot, and then still manage to have the stock recovery. This is a semi-common problem for folks, so I just kinda took a guess that this could be your problem too. Just a guess, with limited information known.