Database Info

ADB Shell doesnt recognize phone in Fastboot mode only fully powered on

I was always able to ADB shell into my phone after i installed the proper USB drivers as well as Pull up ADB DEVICES no problem and i SAW ADB DEVICE in my device manager
Ok i have finally got to the steps where i have flashed my sappimag.zip file to my Mytouch successfully. that ROM has been flashed and now when i boot the phone up it says VODAFONE and i can get intot he phone fully
I have turned the device off and hold the BACK and POWER button and the FASTBOOT screen comes up. i plug in the USB cable an FASTBOOT changes to FASTBOOT USB ok great.
i pull up CMD and type in ADB SHELL and it says DEVICE NOT FOUND. i type in ADB DEVICES and its blank.
I power down and power back up fully and same thing (but it was working before the flash of sappimg.zip)
i downloaded and installed HTC SYNC which supopsedly has updated XP drivers and it did.
i power down phone and power back up as normal and pull up CMD ADB SHELL works fine and ADB DEVICES shows my serial number. ok making progress.
I have turned the device off and hold the BACK and POWER button and the FASTBOOT screen comes up. i plug in the USB cable an FASTBOOT changes to FASTBOOT USB ok great.
i pull up CMD and type in ADB SHELL and it says DEVICE NOT FOUND. i type in ADB DEVICES and its blank still again.
what gives? why does this only work now with phone fully booted and not in fastboot mode?
also note my device manager no longer has ADB DEVICE anymore its gone.

adb doesn't work in fastboot mode.
edit for clarity: When you boot the phone in fastboot mode, adb isn't supposed to work. You have to boot fully, or boot into one of the recovery images that supports adb for it to work, fastboot doesn't support adb at all.

Deicist said:
adb doesn't work in fastboot mode.
edit for clarity: When you boot the phone in fastboot mode, adb isn't supposed to work. You have to boot fully, or boot into one of the recovery images that supports adb for it to work, fastboot doesn't support adb at all.
Click to expand...
Click to collapse
ok so what does this mean in the directions then? how am i supposed to perform the below directions in red then?
FLASH your T-Mobile myTouch 3G
Make sure are using fastboot from the latest SDK (release 3) !
- Power-off your device
- Insert the goldcard
- Power on while holding volume down (of fastboot your device and then press volume down)
- It should pick up the sappimg.zip and you should be able to flash it.
- Once the flashing is FULLY finished power off your device.
- Remove the goldcard and insert the SD (with update.zip)
- Power on while holding back (=fastboot) and connect the USB cable
- Download my RAv1.2.0H recovery and fastboot it :
Code:
fastboot boot recovery-RAv1.2.0H.img

it means exactly what it says:
Download the recovery image to your computer then, from your computer, run the command:
"fastboot boot recovery-image-name.img"
fastboot is a command line utility that comes with the android sdk. It allows you to push recovery images to the phone while it's in fastboot mode and boot them.
adb is used to communicate with the phone while it's running an android image, NOT while it's in fastboot mode.

Deicist said:
it means exactly what it says:
Download the recovery image to your computer then, from your computer, run the command:
"fastboot boot recovery-image-name.img"
fastboot is a command line utility that comes with the android sdk. It allows you to push recovery images to the phone while it's in fastboot mode and boot them.
adb is used to communicate with the phone while it's running an android image, NOT while it's in fastboot mode.
Click to expand...
Click to collapse
ok i understand what you mean and say BUT look at the directions and it clearly says:
POWER ON WHILE HOLDING BACK (FASTBOOT) and then CONNECT USB
when i read that it makes me thnk think literal and to hold the Back button my my device and hold power and watch it come into fas boot mode and then when itmentions connect USB it makes me think im supposed to go into ADB shell commadn and then type that command in.
so im definately not trying to argue with you just trying to get you to se my point of view on why i am confused thats all.
i really apreciate your help on this.

Deicist said:
it means exactly what it says:
Download the recovery image to your computer then, from your computer, run the command:
"fastboot boot recovery-image-name.img"
fastboot is a command line utility that comes with the android sdk. It allows you to push recovery images to the phone while it's in fastboot mode and boot them.
adb is used to communicate with the phone while it's running an android image, NOT while it's in fastboot mode.
Click to expand...
Click to collapse
ok one thing that again is confusing is that you say ADB can not recognize the phone while in fastboot mode but then you said i use the fastboot command line to push recovery images to the phone while its in fastboot mode.
how am i suppose to do that if the ADB shell (where i run the fastboot command line from) does not work if the phone is in fastboot mode (the mode it has to be in to accept recovery images)
see what i mean very confusing.
i just rebooted my phone normal. connected it to USB and went into CMD and ADB shell comes up fine
i typed in ADB SHELL
and then :
# fastboot boot recovery-RAv1.2.0H.img
and it says:
C:\>adb shell
# fastboot boot recovery-RAv1.2.0H.img
fastboot boot recovery-RAv1.2.0H.img
fastboot: not found

fastboot is different from adb........
2 different programs. adb.exe and fastboot.exe
just place the fastboot.exe file from the sdk into system32.
and try to put the recovery file in to the sdcard.
rename it to recovery.img to prevent misspelling .

Deicist said:
it means exactly what it says:
Download the recovery image to your computer then, from your computer, run the command:
"fastboot boot recovery-image-name.img"
fastboot is a command line utility that comes with the android sdk. It allows you to push recovery images to the phone while it's in fastboot mode and boot them.
adb is used to communicate with the phone while it's running an android image, NOT while it's in fastboot mode.
Click to expand...
Click to collapse
fadedmicrobe said:
fastboot is different from adb........
2 different programs. adb.exe and fastboot.exe
just place the fastboot.exe file from the sdk into system32.
and try to put the recovery file in to the sdcard.
rename it to recovery.img to prevent misspelling .
Click to expand...
Click to collapse
ok i see what it is now.
in my CMD prompt i typed in:
C:\fastboot boot recovery-RAv1.2.0H.img
and it says:
can not load 'recovery-RAv1.2.0H.img'
i have made sure that my recovery-RAv1.2.0H.img file is in C:\AndroidSDK folder where everythign else is.
currently i have my spare 4 GB card in my Device and it contains the 1.33.2005 hboot file renamed to UPDATE.ZIP
and im following the directions in red and it sjust not working
FLASH your T-Mobile myTouch 3G
Make sure are using fastboot from the latest SDK (release 3) !
- Power-off your device
- Insert the goldcard
- Power on while holding volume down (of fastboot your device and then press volume down)
- It should pick up the sappimg.zip and you should be able to flash it.
- Once the flashing is FULLY finished power off your device.
- Remove the goldcard and insert the SD (with update.zip)
- Power on while holding back (=fastboot) and connect the USB cable
- Download my RAv1.2.0H recovery and fastboot it :

copy "recovery-RAv1.2.0H.img" to C:\ (the same directory that you are running fastboot.exe from)

ok thanks everyone i got everything i wanted above.
I guess my Mytouch is now rooted? but wth a 32A radio?
i want to flash a 32B cyanogen 3.9.10 rom onto this device and using the directions below:
For Daredevils : Perform the following steps only if you want to revert to a 32B based radio and ROM.
Revert to 32B Radio and ROM :
- Download your favorite 32B ROM and copy it to your sdcard
- Download the Ion radio image from the HTC site.
- Extract radio.img from ota-radio-2_22_19_26I.zip using your favorite rar/zip program.
- Download my 32B RAv1.2.0G recovery.
- Fastboot your mobile and connect it via USB :
where it says copy your favorite ROM to your SD card well the ROM name i want is called "update-cm-3.9.10-signed.zip"
do i need to rename it to anything? or just leave it as it is?
do i literally just copy that file to my clean empty SD card no renaming to UPDATE or something like that?

Hi everybody, it's my first message here for a big promblem to solve.
First of all my Sapphire version is 32A SHIP S-ON H
I tried to install a Hero version on my Magic by following a recent tutorial.
- I tried to use ecovery-RAv1.2.0H.img (and older version) without success.
- After copying a JACxHERO version (and rename --> update.zip on the SD Card), I lauched the update with daldroid-recovery.img.
- The phone doesn't start (blocked with HTC Magic on the screen)
Problems:
- The backup I did with daldroid doesn't work
- My phone doesn't boot normally anymore
- I can't access the SD Card anymore (with Windows | Dos )
- The USB drivers are correctly installed
What is THE solution to reset the phone (by putting an original version of android on it)???
Thanks a lot for your help!
Fabrice

nextelbuddy said:
ok thanks everyone i got everything i wanted above.
I guess my Mytouch is now rooted? but wth a 32A radio?
i want to flash a 32B cyanogen 3.9.10 rom onto this device and using the directions below:
For Daredevils : Perform the following steps only if you want to revert to a 32B based radio and ROM.
Revert to 32B Radio and ROM :
- Download your favorite 32B ROM and copy it to your sdcard
- Download the Ion radio image from the HTC site.
- Extract radio.img from ota-radio-2_22_19_26I.zip using your favorite rar/zip program.
- Download my 32B RAv1.2.0G recovery.
- Fastboot your mobile and connect it via USB :
where it says copy your favorite ROM to your SD card well the ROM name i want is called "update-cm-3.9.10-signed.zip"
do i need to rename it to anything? or just leave it as it is?
do i literally just copy that file to my clean empty SD card no renaming to UPDATE or something like that?
Click to expand...
Click to collapse
"update-cm-3.9.10-signed.zip" is perfect. Copy it to the SD, but rename to update.zip JIC.

wdelisi said:
"update-cm-3.9.10-signed.zip" is perfect. Copy it to the SD, but rename to update.zip JIC.
Click to expand...
Click to collapse
thank you

With Amon_RA's RAv1.2.0 recovery you don't need to rename . I keep my favourite roms in my sd card and switch back and forth all the time
You just select (when fastbooted into recovery) Flash - Choose .zip, and you get a list with all .zip files on sd card root Sweeeet

Start asking your questions in the right sub-forum (Q&A) (Theme) or even in (General), or i will be forced to ban you for 3 days or till you learn.
Thanks
Thread Trashed!!

Help tf101g

hello peopleI need your help without any information someone deleted all my files tf101g
TF101G entering recovery mode with cwm
cwm 5.5.0.4 but this does not allow me to upgrade from external sd card. I tried to flash from w7 with some programs, wheelie, nvflash, tubuntu, oneclickrecovery among others.
adb shell
exec ' system bin sh' failed no such file or directory 2
pushing something. permission denied
NVFLASH
rcm version 0x4 command send failed (usb write failed)
can someone help me

Since you have a TF101G, NVFlash is not an option.
Does your device show up as an ADB device in windows when you boot to recovery?
Another thought- if you hold VOL DOWN and POWER for 12-15 seconds and release when you see the white text (and don't hit vol up to enter RCK), does it boot up?
If so, you just have a recovery bootloop and can boot using this method until we fix it.
If not, back to my first thought - if it shows in the device manager, update the drivers using the naked drivers 0.72.
Then try typing "adb devices" at a command prompt and see if it is recognized via USB.
If so, push your firmware using the following:
adb push firmware.zip /sdcard/
If that succeeds, you should be able to flash the firmware from recovery.

frederuco said:
Since you have a TF101G, NVFlash is not an option.
Does your device show up as an ADB device in windows when you boot to recovery?
Another thought- if you hold VOL DOWN and POWER for 12-15 seconds and release when you see the white text (and don't hit vol up to enter RCK), does it boot up?
If so, you just have a recovery bootloop and can boot using this method until we fix it.
If not, back to my first thought - if it shows in the device manager, update the drivers using the naked drivers 0.72.
Then try typing "adb devices" at a command prompt and see if it is recognized via USB.
If so, push your firmware using the following:
adb push firmware.zip /sdcard/
If that succeeds, you should be able to flash the firmware from recovery.
Click to expand...
Click to collapse
when i try
adb push firmware.zip /sdcard/
adb push firmware.zip /sdcard/ permission denied

Try fixing permissions in CWM. I think it is under advanced.

stuck with bootloop and no alternative rom

i have a slight problem. i grabbed the ubuntu touch alpha and went in to recovery, loaded it (according to thread instructions) but ended up with a bootloop.
in the end i thought "lets just put another rom back on for now" and then realised i had deleted the other rom from the sdcard! so i'm stuck with it not booting in to ubuntu, and not able to get another rom on as it doesn't boot in.
can i connect to the internal sdcard area myself by plugging the usb in to the pc or something?
i have twrp loaded as recovery
thanks

ah, TWRP adb sideload to the rescue!

problem
my problem is stuck in boot screen after i did super wipe full what should i do? i have cwm 5.5.0.4. i try flash from sd put it says no files found

partti86 said:
my problem is stuck in boot screen after i did super wipe full what should i do? i have cwm 5.5.0.4. i try flash from sd put it says no files found
Click to expand...
Click to collapse
The issue, Superwipe wipes the internal /sdcard/ and also this is where it flashes from.
You need to boot to recovery and then use ADB to push files to the sdcard.
If you have never used ADB, it can be a bit daunting.
First, you need adb from the Android SDK. It is a big file for the few you need. I have a copy of the relevant ADB files here: https://db.tt/b9dQ6xzp
Unzip this to c:\adb folder on windows. If you are using Linux, it should already have adb in the /usr/bin/ folder.
Next, you need the Universal Naked Drivers: http://forum.xda-developers.com/attachment.php?attachmentid=1934814&d=1367674531
Unzip these to c:\universal_naked_drivers
Boot to CWM and then plug in your USB cable. It should show a new device found. It may find 2, an MTP and then there should be another either Unknown device or an Android ADB device. Right click and update the driver. Be sure to search for driver, then tell it you want to pick from a list. Hit the Have Disk button and then hit the browse button and browse to c:\universal_naked_drivers and hit OK. It should show you a driver to select and hit OK. If you are using Win 8, there is an additional step that is required to used non-signed drivers.
Once the driver is updated, download the zip file you want to flash on your PC. I assume it is a ROM.zip file for this example. Place this file in the c:\adb folder and call it ROM.zip (can be named something else, but this is what we will use for this example).
Now, open a command prompt and execute the following:
Code:
> [B]c:[/B]
c:\> [B]cd c:\adb[/B]
c:\adb> [B]adb devices[/B]
It will probably say some messages about the daemon is not running, restarting adb.
Then it should show a list. There should be some numbers followed by "recovery"
If no devices are shown, check that your ADB device is showing in the Device Manager.
Once you see it in the adb devices list, continue:
Code:
c:\adb> [B]adb push ROM.zip /sdcard/[/B]
successfully pushed xxx bytes
c:\adb>
At this point you should now see the ROM.zip file on the internal storage in CWM to allow you to install it.
Choose to install the file then reboot (not to recovery). You have to let it flash the file (progress bar will show). Once the screen goes black and the progress bar disappears, it should now boot to your ROM..
If your ROM requires a custom kernel and/or GAPPS to be flashed, use the same procedure to push your kernel.zip and GAPPS.zip to the /sdcard/ directory.

mk2media said:
ah, TWRP adb sideload to the rescue!
Click to expand...
Click to collapse
Can you explain what you did please? what is adb sideload?

Droid ultra kitkat update not installing

Recently I found out there was a kit kat update for my droid ultra it downloaded the update using 4G LTE and now and decided to install it then the phone shuts down and powers back up on its on I thought it was part of the update but this is the 100th time it's done it ive been waiting 8 hours for it to stop but it just keeps going it's not even showing any sign that it is updating!!!
I tried booting into recovery to factory reset it but whenever I select recovery it just boots up the phone normally HELP PLEASE!!!

response
droidusr2014 said:
Recently I found out there was a kit kat update for my droid ultra it downloaded the update using 4G LTE and now and decided to install it then the phone shuts down and powers back up on its on I thought it was part of the update but this is the 100th time it's done it ive been waiting 8 hours for it to stop but it just keeps going it's not even showing any sign that it is updating!!!
I tried booting into recovery to factory reset it but whenever I select recovery it just boots up the phone normally HELP PLEASE!!!
Click to expand...
Click to collapse
It appears as if you have installed some kind of rooting tool. The reason why the phone boots up normally after you choosing Recovery is because you don't have a custom recovery tool installed.
To solve this same problem, I factory reset my phone. (this is assuming that you have windows) To do this, install the Motorola Device Manager (google it and find the motorola support page, you can download it there) and reboot your computer.
Then connect the usb cable to your computer and download the android SDK platform tools from here -
ht tp://developer.android.com/sdk/index.html#download
^remove the space in ht tp because i can't post links
Extract the /sdk/platform-tools folder to a location which you can easily access.
Then, open command prompt and type
Code:
cd [mydirectory]
for example, if i stored the platform-tools folder on my desktop, i would type
Code:
cd C:\Users\[myusername]\Desktop\platform-tools
then open the bootloader (fastboot) by holding POWER and VOLUME-DOWN instead of just the power button when trying to boot.
OR type this into command prompt (your phone has to be turned on for this)
Code:
adb reboot bootloader
then, once your phone is in the bootloader (do not press anything on your phone at this point), type this in command prompt
Code:
fastboot -w
Remember, this will wipe all your user data / cache but it should make your phone work again. I'm not sure how to do this without factory resetting so if there are any users who are more experienced, feel free to post your better solution. thank you.

Thanks
Thank you so much currently I can't try out your method but it looks like it could work THANK YOU SO MUCH I'm going to try tonight and I'll tell you how it went. I really don't mind factory resetting as long as it saves my phone im all right thanks again :laugh:!!!
Pacnet_ said:
It appears as if you have installed some kind of rooting tool. The reason why the phone boots up normally after you choosing Recovery is because you don't have a custom recovery tool installed.
To solve this same problem, I factory reset my phone. (this is assuming that you have windows) To do this, install the Motorola Device Manager (google it and find the motorola support page, you can download it there) and reboot your computer.
Then connect the usb cable to your computer and download the android SDK platform tools from here -
ht tp://developer.android.com/sdk/index.html#download
^remove the space in ht tp because i can't post links
Extract the /sdk/platform-tools folder to a location which you can easily access.
Then, open command prompt and type
Code:
cd [mydirectory]
for example, if i stored the platform-tools folder on my desktop, i would type
Code:
cd C:\Users\[myusername]\Desktop\platform-tools
then open the bootloader (fastboot) by holding POWER and VOLUME-DOWN instead of just the power button when trying to boot.
OR type this into command prompt (your phone has to be turned on for this)
Code:
adb reboot bootloader
then, once your phone is in the bootloader (do not press anything on your phone at this point), type this in command prompt
Code:
fastboot -w
Remember, this will wipe all your user data / cache but it should make your phone work again. I'm not sure how to do this without factory resetting so if there are any users who are more experienced, feel free to post your better solution. thank you.
Click to expand...
Click to collapse

Will factory reset erase root??
One more thing I actually am currently rooted by using RockMyMoto so I think that is why the update didn't work but 1 last question when I factory reset will it erase root? I don't mind if it erases root but my main concern is that if root somehow stays I won't be able to do the software update.
Pacnet_ said:
It appears as if you have installed some kind of rooting tool. The reason why the phone boots up normally after you choosing Recovery is because you don't have a custom recovery tool installed.
To solve this same problem, I factory reset my phone. (this is assuming that you have windows) To do this, install the Motorola Device Manager (google it and find the motorola support page, you can download it there) and reboot your computer.
Then connect the usb cable to your computer and download the android SDK platform tools from here -
ht tp://developer.android.com/sdk/index.html#download
^remove the space in ht tp because i can't post links
Extract the /sdk/platform-tools folder to a location which you can easily access.
Then, open command prompt and type
Code:
cd [mydirectory]
for example, if i stored the platform-tools folder on my desktop, i would type
Code:
cd C:\Users\[myusername]\Desktop\platform-tools
then open the bootloader (fastboot) by holding POWER and VOLUME-DOWN instead of just the power button when trying to boot.
OR type this into command prompt (your phone has to be turned on for this)
Code:
adb reboot bootloader
then, once your phone is in the bootloader (do not press anything on your phone at this point), type this in command prompt
Code:
fastboot -w
Remember, this will wipe all your user data / cache but it should make your phone work again. I'm not sure how to do this without factory resetting so if there are any users who are more experienced, feel free to post your better solution. thank you.
Click to expand...
Click to collapse

Tried the method and it worked!!
I tried what you said and it worked perfectly but it still remembers my Wifi, wallpaper and all it showed the setup screen and I set it up so hopefully im in the clear the phone is downloading the update right now.

It will not allow the update and you will still end in boot loop. Need to remove root first: http://forum.xda-developers.com/showthread.php?t=2577029

Install TWRP and root LG v10 H901 T-Mobile

Download
Search for TWRP recovery for LG V10 H901 (File: twrp-2.8.7.0-h901.img (31.7 MB))
Backup Apps and Data
While this process should not wipe any of your data, a backup is highly recommended. Once you install a custom recovery like TWRP, make sure you backup your system, data,etc. from the recovery. It will be helpful in case anything goes wrong.
Prerequisites
This guide is compatible with LG V10 H901 only. Do not try it on any other devices or variants.
Unlocked bootloader is required to install a custom recovery like TWRP on your device. Click here.
Set up ADB and Fastboot on your computer. You can download the minimal ADB and fastboot tool from here (unzip it) or get the quick ADB and fastboot installer from here.
Install Motorola USB Drivers on your computer.
Open Settings> Developer options and enable USB Debugging on your device.
Go to Developer options and enable Allow oem unlock.
How to Install TWRP Recovery on LG V10 H901
Download the recovery image file. Extract if in case a zip file. Now transfer the file to your PC where you can easily locate it.
Make sure you have setup ADB and fastboot on your PC. Also accept Always allow from this computer when you plug in the device for first time to enable USB Debugging.
Now power off your device and unplug it from your PC.
Boot into the bootloader or fastboot mode. To do so, press and hold volume down and the power button simultaneously for 5-6 seconds. When you see the bootloader screen, connect your device to the PC using a USB cable.(Choose fasboot if option is available) Alternatively, you can also issue the following command through your cmd or terminal, while connected to the PC in order to boot into the bootloader.
"adb reboot bootloader"
Navigate to the location where you have placed the recovery file. Rename the recovery file to a simple one, like recovery.img. While the folder with recovery.img file is open, hold shift key on keyboard and right-click on an empty space and select “Open command window here” option to launch a cmd window.
Now issue the following command in the command prompt to check your device connectivity
"fastboot devices"
Now flash custom recovery. Issue the following command for that.
"fastboot flash recovery recovery.img"
Custom recovery will now be installed on your device. Now boot your phone in recovery mode. You can do this by turning your device off and then press and hold volume down and power keys at the same time. Or you can simply enter the following command.
"fastboot boot recovery.img"
Once into the recovery, you can backup your current ROM, data, EFS and more.
Once you have installed TWRP, you are all set to install custom packages onto the device’s system. Alternatively, while on Linux or Mac OS, you can issue “./fastboot flash recovery recovery.img” command to flash the TWRP recovery.
Root
As you already have TWRP, simply flash the SuperSU file (version 2.56) to gain root access

@TheJesus @KAsp3rd, thanks guys for everything you've done over the past few days. no shade to @joe01gun but if people are going to use these instructions make sure you search the rest of the forum for what thejesus and kasp3rd put together to get us to this point - definitely appreciated. thanks @joe01gun for putting these additional instructions together.

Your post says the following:
Set up ADB and Fastboot on your computer. You can download the minimal ADB and fastboot tool from here (unzip it) or get the quick ADB and fastboot installer from here.
yet, there's no link to the necessary files to "unzip" them. Any suggestions?
Thank you for the help, but where do we get fastboot set up on our PCs? Yes, this is getting confusing with the steps outlined above. I followed the first step and had to take out the battery because I was stuck in fastboot screen with small tiny text in the top left that didn't respond to any manipulation with the volume keys on the back of the device and wouldn't restart any way until I took out the battery.

sanjsrik said:
Your post says the following:
Set up ADB and Fastboot on your computer. You can download the minimal ADB and fastboot tool from here (unzip it) or get the quick ADB and fastboot installer from here.
yet, there's no link to the necessary files to "unzip" them. Any suggestions?
Click to expand...
Click to collapse
I think it's cause he's not allowed to post links yet cause he's too new. I followed this guide http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
You can get twrp from the development forum.

Why
Intended to put the information condensed....
Yep....new
Links could not be uploaded.

joe01gun said:
Intended to put the information condensed....
Yep....new
Links could not be uploaded.
Click to expand...
Click to collapse
Your condensed thread is more convoluted than the actual development thread which also includes the links to everything.
I'm still wondering why you have install Motorola USB drivers for an LG phone..

Understood
Understood

The one on development is straightforward and I managed to make it done.
If you don't lock the bootloader back, you will see bootloader unlocked when starting up.
If you have root enabled file explorer, you should remove /system/priv-app/adaptclient folder to avoid annoying root request from adapt.

Please use the main dev thread for instructions on what to do, found below. Having duplicates for what is essentially the same thing can cause confusion and just takes up unnecessary space. So I have closed the thread.
[Recovery][LG-H901] Unofficial TWRP
Forum moderator,
matt4321