[Huawei Y625 ROMs, Kernels, Recoveries, & Other Dev] shevtak:
adb is the "Android Debug Bridge" which is used to send commands directly to Android OS. It is part of the official Android sources. Using it should not void your warranty. Rooting, flashing custom ROMs or Recovery images is what voids the warranty.

You can run TWRP without flashing it. That was actually part of the explanation provided by AkaruiTenshi which BatDroid had included in the first post on this thread. But that may already require some advance knowledge to follow, so I'll explain in a little more detail:

Before we go, you need to have adb and fastboot installed (For Windows, you'll find a great explanation here. On Linux you can simply look for adb and fastboot in the package manager of your distro and install from there - if you can't find them by their own names, look for android-tools or something similar). If you're on Windows, you'll also need to install the necessary drivers for your phone.

Then what you need to do is:

On your phone, go to "Settings -> Developer Options" and activate "USB debugging"

Connect your phone to your PC

Open a terminal window (cmd on windows) and cd to where you have adb and fastboot installed (unless they were included in the system PATH variable at installation, then you should be able to execute them from anywhere).

Now check if adb can actually detect your phone by entering

adb devices

. This should bring up something like this:

List of devices attached
1234567890123456	device

(The number will be different in your case, it is the serial number of your phone)

If no device shows up beneath the "List of devices attached" prompt, then there's most likely a problem with your drivers (on Windows) or with device permissions (on Linux) that you need to fix first.

Now you can tell your phone to reboot in bootloader mode:

adb reboot bootloader

(if you have a stock Huawei y625-u51 then this should mean it will restart and then stop at the logo splash screen).

Now we'll use fastboot, another command that's part of the official Android sources. It's used to interact with the boot process and modify system images. Again, check to see if it can detect your phone first, this time by entering

fastboot devices

If you're device doesn't show up, then driver and permission problems need to be fixed first before you can continue. Different drivers and permissions apply for fastboot than for adb, so the fact you got the one working doesn't necessarily mean the other will be fly. :rolleyes:

Now you can use fastboot to make the phone boot the recovery image without having it flashed to ROM. Make sure that the recovery.img file is in your current directory, then enter

fastboot boot recovery.img

fastboot will send the image to the phone where it will be run solely within the volatile RAM memory - there will be no traces on the phone when you've finished (unless you use TWRP to manipulate the filesystem, flash ROMs etc. of course ;) ). The phone will need some time to decompress the image and start it, so be patient (mine took 10-20 seconds).

If you do want to have TWRP available permanently at a later time, you would run

fastboot flash recovery recovery.img

instead. That would write the image to ROM, which is non-volatile memory, meaning it will remain persistent even after powering off.

Ok, I hope this helps. Like I said, problems are usually related to drivers (Windows) or permissions (Linux) which can be a drag because it stops you before you really started. But once you have drivers and permissions settled, the fun starts ;)

Greetings,

shevtak